Public report of BeatLeader/beatleader-mod, published 17 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, 17 November 2026, 22:31 UTC · Survey ID cd_2b6362c0b53f49b0bd4324fe8e573630

BeatLeader/beatleader-mod

Measured 17 November 2026, 22:31 UTC, at code version c26af12

First survey, so nothing to compare with yet
CAI score 35.2out of 100 Provisional

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: 42,862 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Security and Compliance, 26.3

Findings by how serious they are

44 critical 303 serious 120 minor

1 dimension is left out of the score. 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. It counts neither for nor against the score, and Limitations lists it 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
17 November 2026, 22:31 UTC

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

The code didn't build, so the score is provisional
We couldn't build the code: the build stopped with 6001 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: CS0246: The type or namespace name 'HarmonyLib' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'BGLib' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'JetBrains' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'IPA' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'UnityEngine' could not be found (are you missing a using directive or an assembly reference?)

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 ▸

62of 62 dimensions measured by tools.
441of 467 findings point to an exact file and line, so you can open each one in the code. The other 26 concern the repository as a whole, such as missing documentation.
62dimensions across 6 lenses, read from 42,862 lines of product code in 1 project.
Chapters

Executive summary

BeatLeader/beatleader-mod has a provisional result, because the code didn't build. Its score is held back in part because we found no access checks on the code's endpoints or handlers. It scores 35.2 out of 100, and the ratings may change once the code builds. 11 of its 44 critical findings are security problems. We judged it as a preview release, against a lower bar.

Security and Compliance, at 26.3, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 7.8 points. Fixing the eight comments that repeat the code, or contradict it comes next, worth about 2.4 points. Raising Security and Compliance to 68 would lift the score to about 43.4.

Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline, and six errors are caught and ignored, so failures can go unnoticed. Pinning each tool to an exact version, limiting each secret to its own step and handling or logging the ignored errors would close these risks. Fixing the weaknesses the scanner points to would fix the two security weaknesses in the code, and updating the vulnerable packages would deal with the package with a known security hole. The 14 analysis rules switched off in the settings need switching back on in the settings file.

The product code is 42,862 lines, about €51,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 26.3 · counts for 46%Production Readiness 29.8 · counts for 25%Maturity 49.4 · counts for 14%Architecture 55.6 · counts for 8%Code Health 61.8 · counts for 4%Performance 70.0 · counts for 2%

If Security and Compliance rose from 26.3 to 68, the lowest score rated Strong, the score would rise from 35.2 to about 43.4.

Code composition: what the lines of code are
Business logic 26%Supporting code 74%
Rebuild cost: about €51,000 · Estimate
Cost to rebuild€17,000 to €85,000, for 280 to 890 hours of work, about 0.3 person-years for one engineer
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: 42,862 lines of product code, of which 36% is declarations and boilerplate, 38% straight logic and 26% logic with branches
Comment linesThe estimate prices 42,066 lines. Comment lines count towards the size of 42,862 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 7.8 points · Medium effort · Access Controls
2
Resolve the 8 redundant comment finding(s) in Comment Value — start with RecorderMultiplayerUtilPatch.cs (4), AddFriendRequest.cs, RemoveFriendRequest.cs.
Raises the score by about 2.4 points · Low effort · Comment Value
3
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 4.8 points · Medium effort · Web-Security Posture

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.

If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: CS0246: The type or namespace name 'HarmonyLib' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'BGLib' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'JetBrains' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'IPA' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'UnityEngine' could not be found (are you missing a using directive or an assembly reference?)
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €51,000 to build again, about 0.3 person-years of work. Its weakest lens is Security and Compliance, at 26.3 (Weak). 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.

Architecture: which parts of the code depend on which

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

36 modules, with 94 dependencies between them. One loop runs through 18 of the modules, marked above the diagonal.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 B83.Image.GIF2 BeatLeader.Attributes3 BeatLeader.BeatSaverAPI4 BeatLeader.Models.BeatSaver5 BeatLeader.SteamVR6 BeatLeader.UI.Reactive7 BeatLeader.UI.Reactive.Components8 BeatLeader.UI.Rendering9 System.Runtime.CompilerServices10 BeatLeader.Models.AbstractReplay11 BeatLeader.Models.Replay12 BeatLeader.Themes13 BeatLeader.UI14 BeatLeader.Core.Managers.NoteEnhancer15 BeatLeader.Core.Managers.ReplayEnhancer16 BeatLeader.Replayer17 BeatLeader.UI.Replayer18 BeatLeader.Models19 BeatLeader.Installers20 BeatLeader.Replayer.Emulation21 BeatLeader.Results22 BeatLeader.UI.Replayer.Desktop23 BeatLeader.WebRequests24 BeatLeader.DataManager25 BeatLeader.Replayer.Binding26 BeatLeader.UI.Hub27 BeatLeader.UI.MainMenu28 BeatLeader.Manager29 BeatLeader.Components30 BeatLeader.ViewControllers31 BeatLeader32 BeatLeader.UIPatches33 BeatLeader.API34 BeatLeader.Interop35 BeatLeader.Replayer.Tweaking36 BeatLeader.Utils
1 B83.Image.GIF
2 BeatLeader.Attributes
3 BeatLeader.BeatSaverAPI
4 BeatLeader.Models.BeatSaver
5 BeatLeader.SteamVR
6 BeatLeader.UI.Reactive
7 BeatLeader.UI.Reactive.Components
8 BeatLeader.UI.Rendering
9 System.Runtime.CompilerServices
10 BeatLeader.Models.AbstractReplay3
11 BeatLeader.Models.Replay21
12 BeatLeader.Themes1
13 BeatLeader.UI12
14 BeatLeader.Core.Managers.NoteEnhancer1
15 BeatLeader.Core.Managers.ReplayEnhancer13
16 BeatLeader.Replayer73375
17 BeatLeader.UI.Replayer17646710
18 BeatLeader.Models11044114
19 BeatLeader.Installers3
20 BeatLeader.Replayer.Emulation181468
21 BeatLeader.Results1
22 BeatLeader.UI.Replayer.Desktop47
23 BeatLeader.WebRequests2
24 BeatLeader.DataManager35182
25 BeatLeader.Replayer.Binding81
26 BeatLeader.UI.Hub2521235741119
27 BeatLeader.UI.MainMenu2083
28 BeatLeader.Manager41
29 BeatLeader.Components232703331173
30 BeatLeader.ViewControllers311173
31 BeatLeader11112484123
32 BeatLeader.UIPatches1
33 BeatLeader.API1316624
34 BeatLeader.Interop616
35 BeatLeader.Replayer.Tweaking1011
36 BeatLeader.Utils1810212
Uses a module listed above itPart of a loopThe module itself
1 B83.Image.GIF2 BeatLeader.Attributes3 BeatLeader.BeatSaverAPI4 BeatLeader.Models.BeatSaver5 BeatLeader.SteamVR6 BeatLeader.UI.Reactive7 BeatLeader.UI.Reactive.Components8 BeatLeader.UI.Rendering9 System.Runtime.CompilerServices10 BeatLeader.Models.AbstractReplay11 BeatLeader.Models.Replay12 BeatLeader.Themes13 BeatLeader.UI14 BeatLeader.Core.Managers.NoteEnhancer15 BeatLeader.Core.Managers.ReplayEnhancer16 BeatLeader.Replayer17 BeatLeader.UI.Replayer18 BeatLeader.Models19 BeatLeader.Installers20 BeatLeader.Replayer.Emulation21 BeatLeader.Results22 BeatLeader.UI.Replayer.Desktop23 BeatLeader.WebRequests24 BeatLeader.DataManager25 BeatLeader.Replayer.Binding26 BeatLeader.UI.Hub27 BeatLeader.UI.MainMenu28 BeatLeader.Manager29 BeatLeader.Components30 BeatLeader.ViewControllers31 BeatLeader32 BeatLeader.UIPatches33 BeatLeader.API34 BeatLeader.Interop35 BeatLeader.Replayer.Tweaking36 BeatLeader.UtilsB83.Image.GIF1BeatLeader.Attributes2BeatLeader.BeatSaverAPI3BeatLeader.Models.BeatSaver4BeatLeader.SteamVR5BeatLeader.UI.Reactive6BeatLeader.UI.Reactive.Components7BeatLeader.UI.Rendering8System.Runtime.CompilerServices9BeatLeader.Models.AbstractReplay10BeatLeader.Models.Replay11BeatLeader.Themes12BeatLeader.UI13BeatLeader.Core.Managers.NoteEnhancer14BeatLeader.Core.Managers.ReplayEnhancer15BeatLeader.Replayer16BeatLeader.UI.Replayer17BeatLeader.Models18BeatLeader.Installers19BeatLeader.Replayer.Emulation20BeatLeader.Results21BeatLeader.UI.Replayer.Desktop22BeatLeader.WebRequests23BeatLeader.DataManager24BeatLeader.Replayer.Binding25BeatLeader.UI.Hub26BeatLeader.UI.MainMenu27BeatLeader.Manager28BeatLeader.Components29BeatLeader.ViewControllers30BeatLeader31BeatLeader.UIPatches32BeatLeader.API33BeatLeader.Interop34BeatLeader.Replayer.Tweaking35BeatLeader.Utils363211121137337517646710110441143181468147235182812521235741119208341232703331173311173111124841231131662461610111810212

At a glance — Code Health · 61.8 · Adequate · gated by D18 ·

At a glance — Architecture · 55.6 · Adequate · gated by AX2, AX5 ·

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

At a glance — Readiness · 29.8 · Weak · gated by D8, P3, P7 ·

At a glance — Security · 26.3 · Weak · gated by D29, D36, C2 ·

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 — Injection29High / Critical
A03:2025 — Software Supply Chain Failures8High / Critical

Roadmap

Top priorities: Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler; Resolve the 1 No automated tests finding(s) in Code Coverage; 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.

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.+7.8 ptsMediumAccess Controls
Resolve the 8 redundant comment finding(s) in Comment Value — start with RecorderMultiplayerUtilPatch.cs (4), AddFriendRequest.cs, RemoveFriendRequest.cs.+2.4 ptsLowComment Value
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.+4.8 ptsMediumWeb-Security Posture
Resolve the 1 No automated tests finding(s) in Code Coverage.+7.4 ptsHighCode Coverage
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.+3.2 ptsMediumSecurity & performance tooling
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2).+1.5 ptsLowStatic Analysis (SAST)
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2).+1.5 ptsLowStatic Analysis (SAST)
Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED.+1.5 ptsLowDependency Vulnerabilities

File quality

Per-file score 0–10 — a quality signature. Of 101 files carrying findings, judged against the Preview bar: 2% slop · 16% mixed · 82% near-clean.

FileScoreBandWorst signal
REDACTED0.5SlopStatic Analysis (SAST): High: REDACTED
Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs3.0SlopExplicit Debt: WriteOnlyPrivateField
Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs3.6MixedExplicit Debt: EmptyCatchBlock
REDACTED5.1MixedStatic Analysis (SAST): Medium: REDACTED
Source/.editorconfig5.2MixedExplicit Debt: AnalyzerSeverityNone
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs6.0MixedExplicit Debt: Dead code: GetPositiveMultiplier
Source/7_Utils/FormatUtils.cs6.0MixedExplicit Debt: ObsoleteWithCallers
Source/8_UI/MainMenu/OtherNews/EventNewsPanel.cs6.3MixedCode Duplication: Duplicated block (26 lines × 2)
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
Source/7_Utils/Interop/Interops/Cam2Interop.cs6.4MixedExplicit Debt: WriteOnlyPrivateField
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
Source/2_Core/API/PersistentWebRequest.cs6.6MixedExplicit Debt: ObsoleteWithCallers
Source/8_UI/Components/Reactive/Native/ValueAnimator.cs6.7MixedExplicit Debt: ObsoleteWithCallers
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
Source/7_Utils/UtilityClasses/GifLoader.cs7.1Near-cleanCyclomatic Complexity: GIFImageBlock.DrawTo (cyclomatic 18)
Source/7_Utils/Interop/Interops/BetterSongListInterop.cs7.1Near-cleanCode Duplication: Edited copy of a member (31 corresponding lines)

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

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

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

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

Could not be resolved — 1

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 62 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 — 62 dimensions across the health lenses
D1D2D3D4D5D6D8D12D13D14D15D16D17D18D24D26D27D28D29D30D34D35D36D43D44AX10AX2AX3AX4AX5AX6C2GD1IC1M1M2M3M4P1P2P3P4P6P7PF3S1X1X12X16X18X2X20X21X22X23X24X27X28X29X3X30X5

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, 441 of 467 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 01a1eba2-aa0c-7932-8350-207d5e82c633.

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.

  • D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `Source/manifest.json`, `Source/9_Resources/Localization.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
  • AX2 Stateful singletons — 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. 28 further occurrence(s) are not listed individually; the score already reflects all 68.
  • P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • 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. 9 further occurrence(s) are not listed individually; the score already reflects all 49.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • 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.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • 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.
  • 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 Complexity8.0 / 10Strong✓ 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 8.0 / 10 · rule-coverage 100% · ceiling Prevented

5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ReplayUtils.HMDFromName at 71. A further 2 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 ReplayUtils.HMDToName at 35 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Source/2_Core/Localization/BLLocalization.cs (BLLocalization.GetLanguageName at 16). 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.

ReplayUtils.HMDFromName (cyclomatic 71)Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:190
ReplayUtils.ControllerFromName (cyclomatic 43)Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:260
ReplayStatisticUtils.Accuracy (cyclomatic 38)Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:192
GIFImageBlock.DrawTo (cyclomatic 18)Source/7_Utils/UtilityClasses/GifLoader.cs:262
MapEnhancer.modifiers (cyclomatic 17)Source/2_Core/Managers/ReplayEnhancer/MapEnhancer.cs:40

What to do

  1. Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ReplayUtils.HMDFromName (cyclomatic 71), ReplayUtils.ControllerFromName (cyclomatic 43), ReplayStatisticUtils.Accuracy (cyclomatic 38). — 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 5 together lifts Cyclomatic Complexity from 8.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D2 · Cognitive Complexity7.6 / 10Strong✓ 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 7.6 / 10 · rule-coverage 100% · ceiling Prevented

10 method(s) exceeded the cognitive complexity threshold of 15; the worst was ReplayStatisticUtils.Accuracy at 72.

ReplayStatisticUtils.Accuracy (cognitive 72)Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:192
ReplayUtils.HMDFromName (cognitive 70)Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:190
ReplayUtils.ControllerFromName (cognitive 41)Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:260
ExperienceBar.Update (cognitive 34)Source/8_UI/Leaderboard/Components/TopPanel/ExperienceBar.cs:45
GIFImageBlock.DrawTo (cognitive 23)Source/7_Utils/UtilityClasses/GifLoader.cs:262

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

What to do

  1. Bring the 10 bodies over 15 down to 15 or less in Cognitive Complexity — start with ReplayStatisticUtils.Accuracy (cognitive 72), ReplayUtils.HMDFromName (cognitive 70), ReplayUtils.ControllerFromName (cognitive 41). — 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 10 together lifts Cognitive Complexity from 7.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D3 · God Classes9.2 / 10Stronggated by 7 serious findings✓ 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 9.2 / 10 · rule-coverage 100% · ceiling Prevented

7 god class(es) detected.

MethodTooLong: ReplayStatisticUtils.Accuracy · ×3Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:192
TooManyMethods: TimeLocalizationUtils · ×2Source/2_Core/Localization/TimeLocalizationUtils.cs
FileTooLong: BeatLeaderReplay/Replay.cs · ×2Source/2_Core/Models/Replays/BeatLeaderReplay/Replay.cs

What to do

  1. Resolve the 3 MethodTooLong finding(s) in God Classes — start with ReplayStatisticUtils.cs, SpecialEventBar.cs, BeatmapPreviewPanel.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 TooManyMethods finding(s) in God Classes — start with TimeLocalizationUtils.cs, FormatUtils.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 FileTooLong finding(s) in God Classes — start with Replay.cs, GifLoader.cs. — One of this dimension's main actionable groups (2 warning-level).

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

D4 · Code Duplication8.9 / 10Strong✓ 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 8.9 / 10 · rule-coverage 100% · ceiling Verified

17 duplicated block group(s) detected. 2.8 % of the production lines (1,192 of 42,862) are in a reported copy. A further 30 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Edited copy of a member (9 corresponding lines) · ×4Source/7_Utils/ReflectionUtils.cs:64
Edited copy of a member (17 corresponding lines) · ×3Source/2_Core/Models/API/BeatLeader/Score.cs:61
Edited copy of a member (7 corresponding lines) · ×3Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:349
Duplicated block (13 lines × 2) · ×3Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:250
Edited copy of a member (26 corresponding lines) · ×2Source/7_Utils/Replays/AbstractReplayUtils.cs:62

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

What to do

  1. Resolve the 4 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with ReflectionUtils.cs, ValueAnimator.cs, ReplayStatisticsPanel.cs. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 3 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication — start with Score.cs (2), BeatmapCharacteristicPanel.cs. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 3 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with BetterSongListInterop.cs, WebRequestFactory.cs, LayoutEditorWindow.cs. — One of this dimension's main actionable groups (3 warning-level).

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

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 252 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D8 · Code Coverage0.0 / 10Critical✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

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

No automated tests

What to do

  1. Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).

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

D12 · Dependency Hygiene9.6 / 10Stronggated by 1 serious finding✓ 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 9.6 / 10 · rule-coverage 100% · ceiling Verified

3 outdated, 0 vulnerable, 0 deprecated, 1 prerelease packages.

Prerelease dependency: BeatSaberModdingTools.Tasks
Outdated: BepInEx.AssemblyPublicizer.MSBuild · ×3

What to do

  1. Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 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 100 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 4 direct `PackageReference`(s), and 96 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D16 · Bus Factor9.1 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

22 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Source/8_UI/Replayer/Components/Toolbar/Timeline.cs. Counted over 252 of the 618 production source files in this repository: 362 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.

Off-boarding risk: anonymized user #1 · ×2

✓ On the Gold path — maintain.

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

D17 · Explicit Debt8.2 / 10Adequategated by 29 critical findings✓ 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 8.2 / 10 · rule-coverage 100% · ceiling Prevented

51 deducted debt markers + 23 dead symbols across 42862 LoC in the .NET projects (0.9/KLoC) → score 8.2.

AnalyzerSeverityNone · ×14Source/.editorconfig:142
WriteOnlyPrivateField · ×7Source/7_Utils/Interop/Interops/BeatSaviorInterop.cs:20
EmptyCatchBlock · ×6Source/2_Core/Managers/SteamVR/SteamVRWebConsoleSession.cs:108
FileScopedPragmaDisable · ×2Source/8_UI/MainMenu/OtherNews/MapNewsPanel.cs:11
Dead code: Postfix · ×23Source/0_Harmony/InstallersPatches/MultiplayerLevelDataEnhancerPatch.cs:8

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

What to do

  1. Resolve the 14 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (14). — One of this dimension's main actionable groups (14 issue-level).
  2. Resolve the 7 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Cam2Interop.cs (2), BeatSaviorInterop.cs, CountersPlusInterop.cs. — One of this dimension's main actionable groups (7 issue-level).
  3. Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with MapPreviewDialog.cs (3), SteamVRWebConsoleSession.cs, FileManager.cs. — One of this dimension's main actionable groups (6 issue-level).

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

D18 · Solution Shape3.0 / 10Weak✓ 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 3.0 / 10 · rule-coverage 100% · ceiling Documented

1 projects, 619 source files, 42862 hand-written lines of code (42862 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 0 inter-project edges (build failed).

Build failed

What to do

  1. Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).

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

D24 · Comment Value4.1 4.0 / 10Weak✓ 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 4.0 / 10 · rule-coverage 97% · ceiling Documented

8 of 135 judged comments only repeat the code they sit on (5.9 %). 12 comment(s) in another language or script were not judged.

redundant comment · ×8Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:23
doc comments repeat the namesSource/2_Core/Models/Replayer/Players/IVirtualPlayerBodySpawner.cs:17

What to do

  1. Resolve the 8 redundant comment finding(s) in Comment Value — start with RecorderMultiplayerUtilPatch.cs (4), AddFriendRequest.cs, RemoveFriendRequest.cs. — One of this dimension's main actionable groups (8 recommendation-level).

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

D26 · Project Cohesion10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

One project, `BeatLeader` (42862 LoC, 338 public types across 25 namespaces): over its size bounds, but its parts reference each other, so it reads as one coherent unit.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability8.4 / 10Strong✓ 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 8.4 / 10 · rule-coverage 100% · ceiling Documented

38 % of calls cross a namespace and 3 % go through an interface, but 64 % of collaborators are co-located — so following a call takes several hops. Baseline: medium — clean/modular boundaries expected.

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)1.9 / 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 1.9 / 10 · rule-coverage 100% · ceiling Documented

29 finding(s): 0 critical, 10 high, 19 medium, 0 low. 6 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.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  3. No action in Static Analysis (SAST) — all 6 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 (6 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities9.4 / 10Adequategated by 1 critical finding✓ 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 9.4 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 1 high, 0 medium, 0 low.

REDACTED

What to do

  1. Resolve the 1 High 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 Freshness8.4 / 10Adequategated by 2 critical findings✓ 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 8.4 / 10 · rule-coverage 100% · ceiling Documented

39 of 256 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Source/2_Core/Localization/TimeLocalizationUtils.cs. Counted over 256 of the 618 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×2Source/2_Core/Localization/TimeLocalizationUtils.cs:1
Orphaned file · ×37Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:1
Further orphaned files (smaller)

What to do

  1. Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with TimeLocalizationUtils.cs, ReplayRecorder.cs. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 37 Orphaned file finding(s) in Knowledge Freshness — start with BetterSongListInterop.cs, ReplayUtils.cs, MiniProfileButtons.cs. — One of this dimension's main actionable groups (37 recommendation-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.9 / 10Stronggated by 6 serious findings✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: EventNewsPanel.cs↔MapNewsPanel.cs 82%; ReplayerNotesCutter.cs↔ReplayerScoreProcessor.cs 60%; EventNewsPanel.cs↔MapPreviewPanel.cs 57%

Change coupling: EventNewsPanel.cs ↔ MapNewsPanel.cs · ×6Source/8_UI/MainMenu/OtherNews/EventNewsPanel.cs:1

What to do

  1. Resolve the 6 Change coupling finding(s) in Change Coupling — start with EventNewsPanel.cs (2), REDACTED (2), ReplayerNotesCutter.cs. — One of this dimension's main actionable groups (6 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 recommendation-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-Life10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

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

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

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 singletons1.0 / 10Critical✓ 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.

  • `AppCache` is not registered, but `ReplayHeadersCache` creates it and keeps it in the static `infoCache`, 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 (_loadTask, _cache, _initialized, _saveTask; e.g. `_loadTask` at line 41). — Source/7_Utils/UtilityClasses/AppCache.cs:9
  • `WebRequestParams` is not registered, but `DownloadMapRequest` creates it and keeps it in the static `RequestParams`, 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 (UploadTrackingPrecision, DownloadTrackingPrecision; e.g. `UploadTrackingPrecision` at line 14). — Source/2_Core/API/Models/WebRequestParams.cs:5
  • `ReplayLaunchData` is not registered, but `ReplayerMenuLoader` creates it and keeps it in the static `ReplayerLauncher.LaunchData`, 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 (_replays, _beatmapLevel, _settings, EnvironmentInfo, ReplayerBindings; e.g. `_replays` at line 18). — Source/2_Core/Models/Replayer/ReplayLaunchData.cs:10
  • `PoseReceiver` is not registered, but `Cam2Interop` creates it and keeps it in the static `poseReceiver`, 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 (Position, Rotation; e.g. `Position` at line 67). — Source/7_Utils/Interop/Interops/Cam2Interop.cs:62
  • `HarmonyMultisilencer` is not registered, but `ScoreSaberInterop` creates it and keeps it in the static `_installatorsSilencer`, 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 (_atLeastOneSilencerIsEnabled; e.g. `_atLeastOneSilencerIsEnabled` at line 20). — Source/0_Harmony/HarmonyMultisilencer.cs:9
  • `ReplayManagerSearchTheme` is not registered, but the singleton `BeatLeaderHubTheme` creates it and keeps it in `ReplayManagerSearchTheme`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_searchHighlightColor, _searchHighlightStyle; e.g. `_searchHighlightColor` at line 10). — Source/8_UI/Models/Style/ReplayManagerSearchTheme.cs:6
  • `BodySettings` is not registered, but the singleton `ReplayerSettings` creates it and keeps it in `BodySettings`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (Configs, _serializedConfigs; e.g. `Configs` at line 23). — Source/2_Core/Models/Replayer/BodySettings.cs:13
  • `SerializableColorSet` is not registered, but the singleton `BeatLeaderHubMenuButtonsTheme` creates it and keeps it in `ReplayManagerButtonColors`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_activeColor, _hoveredColor, _notInteractableColor, _color; e.g. `_activeColor` at line 14). — Source/8_UI/Models/Style/SerializableColorSet.cs:10
  • `HarmonyHelper` 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 (_harmony, _initialized; e.g. `_harmony` at line 13). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/HarmonyHelper.cs:6
  • `HarmonySilencer` 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 (silencersRegistry; e.g. `silencersRegistry` at line 23). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/HarmonySilencer.cs:8
  • `PlayerActiveStateChangedEventPatch` 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 (spectator; e.g. `spectator` at line 51). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:43
  • `MainFlowCoordinatorDidActivatePatch` 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 (_viewController; e.g. `_viewController` at line 18). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/UIPatches/MainFlowCoordinatorPatch.cs:8
  • `MainFlowCoordinatorWillChangePatch` 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 (mainCoordinator, changingToMain; e.g. `mainCoordinator` at line 32). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/UIPatches/MainFlowCoordinatorPatch.cs:24
  • `ConfigFileData` 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 (Instance; e.g. `Instance` at line 25). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/1_Config/ConfigFileData.cs:13
  • `BLLocalization` 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 (_baseGameLanguage, _blLanguageAnalog, translations, _lastUsedLanguage; e.g. `_baseGameLanguage` at line 14). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Localization/BLLocalization.cs:8
  • `LeaderboardState` 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 (_selectedBeatmapKey, IsAnyBeatmapSelected, SelectedLeaderboardKey, _selectedBeatmapLevel, _isVisible, _scoresScope; e.g. `_selectedBeatmapKey` at line 30). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/Leaderboard/LeaderboardState.cs:6
  • `ModifiersMapManager` 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 (CurrentModifiersMap; e.g. `CurrentModifiersMap` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/ModifiersMapManager.cs:11
  • `ReplayRecorder` 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 (_instance; e.g. `_instance` at line 191). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/ReplayRecorder.cs:20
  • `BundleLoader` 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 (_ready, MonkeyPrefab, AccuracyGraphPrefab, ThemesCollection, SaberPrefab, HeadPrefab; e.g. `_ready` at line 34). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/3_AssetBundle/BundleLoader.cs:12
  • `ReeModalSystem` 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 (ActiveModals; e.g. `ActiveModals` at line 36). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/8_UI/Abstract/ReeModalSystem.cs:12
  • `AvatarStorage` 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 (Cache; e.g. `Cache` at line 22). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/8_UI/AvatarStorage.cs:16
  • `HeckNavigationController` 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 (_playViewManagerStartMethod, _playViewManagerEarlyDismissMethod, _playViewManagerInitMethod, _playViewManagerActivateMethod, _playViewManagerFlowCoordinatorField, _playViewManagerViewControllersField; e.g. `_playViewManagerStartMethod` at line 91). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:15
  • `ModPanelUI` 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 (_tabActive; e.g. `_tabActive` at line 17). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/8_UI/ModPanel/ModPanelUI.cs:7
  • `ReeUIComponentV2` 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 (BsmlCache; e.g. `BsmlCache` at line 23). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/8_UI/ReeUIComponentV2.cs:15
  • `StatsStorage` 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 (cachedReplayStats; e.g. `cachedReplayStats` at line 9). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/8_UI/StatsStorage.cs:5
  • `Plugin` 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 (UserAgent; e.g. `UserAgent` at line 53). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Plugin.cs:13
  • `EnvironmentManagerPatch` 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 (_environmentType; e.g. `_environmentType` at line 11). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/MiscellaneousPatches/EnvironmentManagerPatch.cs:6
  • `ResultsViewControllerPatches` 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 (_resultsScreen; e.g. `_resultsScreen` at line 14). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/UIPatches/ResultsViewControllerPatch.cs:6
  • `Authentication` 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 (Platform, _signedIn, _taskSource; e.g. `Platform` at line 26). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/API/Authentication.cs:14
  • `PersistentSingletonWebRequestBase` 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 (tokenSource, Instance; e.g. `tokenSource` at line 87). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/API/PersistentWebRequest.cs:66
  • `OnGameplayCoreInstaller` 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 (_submissionTicket; e.g. `_submissionTicket` at line 160). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Installers/OnGameplayCoreInstaller.cs:24
  • `OnMenuInstaller` 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 (_container; e.g. `_container` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Installers/OnMenuInstaller.cs:16
  • `HiddenPlayersCache` 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 (HiddenPlayers; e.g. `HiddenPlayers` at line 48). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/HiddenPlayersCache.cs:10
  • `LeaderboardInfoManager` 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 (_taskSource; e.g. `_taskSource` at line 20). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/LeaderboardInfoManager.cs:10
  • `LeaderboardsCache` 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 (LeaderboardInfoCache, SortingCache, LastCheckTime; e.g. `LeaderboardInfoCache` at line 39). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/LeaderboardsCache.cs:12
  • `MapTypesManager` 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 (_mapTypes, _sprites; e.g. `_mapTypes` at line 30). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/MapTypesManager.cs:13
  • `ModVersionChecker` 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 (_latestReleaseInfo, _isUpToDate; e.g. `_latestReleaseInfo` at line 29). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/ModVersionChecker.cs:8
  • `OculusMigrationManager` 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 (_isMigrationRequired; e.g. `_isMigrationRequired` at line 20). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/OculusMigrationManager.cs:9
  • `PrestigeLevelsManager` 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 (_mainThreadSynchronizationContext, _loading, _totalLevels, _processedLevels, _lastSyncTime, _icons; e.g. `_mainThreadSynchronizationContext` at line 39). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/PrestigeLevelsManager.cs:15
  • `ProfileManager` 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 (_profile, HasProfile, _profileLoadTaskCompletionSource, friends, _initialized, Roles; e.g. `_profile` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/ProfileManager.cs:12

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.

  • The namespaces BeatLeader ↔ BeatLeader.Components ↔ BeatLeader.Core.Managers.ReplayEnhancer ↔ BeatLeader.DataManager ↔ BeatLeader.Manager ↔ BeatLeader.Models ↔ BeatLeader.Models.AbstractReplay ↔ BeatLeader.Models.Replay ↔ BeatLeader.Replayer ↔ BeatLeader.Replayer.Emulation ↔ BeatLeader.Results ↔ BeatLeader.Themes ↔ BeatLeader.UI ↔ BeatLeader.UI.Hub ↔ BeatLeader.UI.MainMenu ↔ BeatLeader.UI.Replayer ↔ BeatLeader.ViewControllers ↔ BeatLeader.WebRequests depend on each other. The lightest dependency in the cycle is BeatLeader → BeatLeader.Core.Managers.ReplayEnhancer (BeatLeader.ReplayRecorder → BeatLeader.Core.Managers.ReplayEnhancer.TrackingDeviceEnhancer, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Source/2_Core/Managers/ReplayRecorder.cs:5

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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

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

AX5 · Architecture & structure3.0 / 10Weak✓ 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.

  • ~42.9k production LoC (853 types) across 1 project(s) / 39 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.

What to do

  • Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
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.

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.
  • `BeatmapTimeController.Rewind` 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:86
  • `BeatmapTimeController.SetSpeedMultiplier` 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:134
  • `BeatmapVisualsController.PauseCutScoreSpawner` 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. — Source/2_Core/Replayer/BeatmapVisualsController.cs:101
  • `BeatmapVisualsController.PauseSabersSparkles` 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. — Source/2_Core/Replayer/BeatmapVisualsController.cs:105
  • `BeatmapVisualsController.ModifyLevelFailedTextEffect` 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. — Source/2_Core/Replayer/BeatmapVisualsController.cs:116
  • `BeatmapVisualsController.ModifyComboPanel` 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. — Source/2_Core/Replayer/BeatmapVisualsController.cs:120
  • `BeatmapVisualsController.ModifyEnergyPanel` 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. — Source/2_Core/Replayer/BeatmapVisualsController.cs:131
  • `BeatmapVisualsController.ModifyDebrisPhysics` 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. — Source/2_Core/Replayer/BeatmapVisualsController.cs:154
  • `ReplayerCameraController.SetFov` 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
  • `ReplayerCameraController.SetView` 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:48
  • `BeatAvatarController.SetVisuals` 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. — Source/2_Core/Replayer/Emulation/Players/Avatar/BeatAvatarController.cs:18
  • `MenuBeatAvatarController.SetLoading` 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:45
  • `MenuBeatAvatarController.Present` 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
  • `MenuBeatAvatarController.Hide` 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
  • `NoteControllerEmulator.Setup` 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. — Source/2_Core/Replayer/Emulation/Scoring/NoteControllerEmulator.cs:19
  • `ReplayFinishController.Exit` 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:53
  • `ReplayPauseController.Pause` 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:68
  • `ReplayPauseController.Resume` 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:81
  • `DummyViewController.Init` 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:15
  • `LevelSelectionViewController.Dismiss` 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:216
  • `ReplayManagerViewController.NavigateToReplay` 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
  • `HeckNavigationController.NavigateToReplayAsync` 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. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:31
  • `HeckNavigationController.Initialize` 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. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:88
  • `HeckNavigationController.Dispose` 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. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:120
  • `HeckNavigationController.NavigateToReplayManager` 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. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:170
  • `HeckNavigationController.NavigateToBattleRoyale` 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. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:174
  • `SmoothHoverController.AddStateListener` 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. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:35
  • `SmoothHoverController.RemoveStateListener` 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. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:40
  • `SmoothHoverController.OnPointerEnter` 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. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:84
  • `SmoothHoverController.OnPointerExit` 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. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:90
  • `BeatLeaderNewsViewController.RefreshEventsCache` 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:51
  • `ReplayerDesktopViewController.SwitchViewMode` 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:50
  • `ReplayerFloatingPanelResetController.Setup` 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. — Source/8_UI/Replayer/VR/ReplayerFloatingPanelResetController.cs:13
  • `ReplayerFloatingViewController.Setup` 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:29

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✓ Tool-verified

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.

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — Source/7_Utils/UtilityClasses/GifLoader.cs:346, Source/7_Utils/UtilityClasses/GifLoader.cs:350

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs8.5 / 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.

  • `DrawTo` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Source/7_Utils/UtilityClasses/GifLoader.cs:346
  • `Dispose` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Source/7_Utils/UtilityClasses/GifLoader.cs:350
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×10) — Source/2_Core/Installers/OnGameplayCoreInstaller.cs:60, Source/3_AssetBundle/BundleLoader.cs:93, Source/7_Utils/Interop/Interops/CustomNotesInterop.cs:53, …

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)4.7 / 10Adequate✓ 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.

  • The root README is 116 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1

What to do

  • Expand the README with getting-started, architecture overview and a project map.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation0.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.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure8.0 / 10Strong✓ 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 gates8.5 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

What to do

  • Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability7.8 / 10Strong✓ Tool-verified

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

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

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 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:7
  • `REDACTED` 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`. — REDACTED:365

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 & Rollback5.0 / 10Adequate✓ 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.

  • The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — REDACTED:44

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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 resilience3.0 / 10Weak✓ Tool-verified

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.

  • `new(httpClientHandler)` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out. — Source/2_Core/API/WebRequestFactory.cs:14

What to do

  • Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
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).
  • `_loadTask.Wait()` 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). — Source/7_Utils/UtilityClasses/AppCache.cs:46
  • `_saveTask.Wait()` 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). — Source/7_Utils/UtilityClasses/AppCache.cs:80

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
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.)
  • No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
  • `BeatmapTimeController.Rewind` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:86
  • `BeatmapTimeController.SetSpeedMultiplier` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:134
  • `BeatmapVisualsController.PauseCutScoreSpawner` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/BeatmapVisualsController.cs:101
  • `BeatmapVisualsController.PauseSabersSparkles` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/BeatmapVisualsController.cs:105
  • `BeatmapVisualsController.ModifyLevelFailedTextEffect` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/BeatmapVisualsController.cs:116
  • `BeatmapVisualsController.ModifyComboPanel` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/BeatmapVisualsController.cs:120
  • `BeatmapVisualsController.ModifyEnergyPanel` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/BeatmapVisualsController.cs:131
  • `BeatmapVisualsController.ModifyDebrisPhysics` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/BeatmapVisualsController.cs:154
  • `ReplayerCameraController.SetFov` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:35
  • `ReplayerCameraController.SetView` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:48
  • `BeatAvatarController.SetVisuals` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/Emulation/Players/Avatar/BeatAvatarController.cs:18
  • `MenuBeatAvatarController.SetLoading` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:45
  • `MenuBeatAvatarController.Present` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:55
  • `NoteControllerEmulator.Setup` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/Emulation/Scoring/NoteControllerEmulator.cs:19
  • `ReplayPauseController.Pause` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:68
  • `ReplayPauseController.Resume` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:81
  • `DummyViewController.Init` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:15
  • `LevelSelectionViewController.Dismiss` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:216
  • `ReplayManagerViewController.NavigateToReplay` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:35
  • `HeckNavigationController.NavigateToReplayAsync` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:31
  • `HeckNavigationController.NavigateToReplayManager` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:170
  • `HeckNavigationController.NavigateToBattleRoyale` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:174
  • `SmoothHoverController.AddStateListener` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:35
  • `SmoothHoverController.RemoveStateListener` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:40
  • `SmoothHoverController.OnPointerEnter` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:84
  • `SmoothHoverController.OnPointerExit` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:90
  • `ReplayerFloatingPanelResetController.Setup` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/Replayer/VR/ReplayerFloatingPanelResetController.cs:13
  • `ReplayerFloatingViewController.Setup` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:29

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 correctness5.3 / 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.

  • Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. — Source/2_Core/Managers/DataManager/OculusMigrationManager.cs:74
  • 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) — Source/7_Utils/UtilityClasses/AppCache.cs:46, Source/7_Utils/UtilityClasses/AppCache.cs:80
  • `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×11) — Source/8_UI/FlowCoordinator/BeatLeaderHubAvatarController.cs:40, Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/BattleRoyaleFlowCoordinator.cs:189, REDACTED:35, …

What to do

  • Sync-over-async (deadlock risk) through `.Result`
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.

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 correctness4.9 / 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.

  • `WebRequestProcessor` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_requestMessage` itself (line 236), which makes that instance its own. But `_requestMessage` is named in none of the methods the disposal search covered: `Dispose` (line 361), `ReleaseBufferIfNeeded` (line 353) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_requestMessage?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Source/2_Core/API/WebRequestProcessor.cs:236
  • `WebRequestProcessor` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_cancellationTokenSource` itself (line 243), which makes that instance its own. But `_cancellationTokenSource` is named in none of the methods the disposal search covered: `Dispose` (line 361), `ReleaseBufferIfNeeded` (line 353) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_cancellationTokenSource?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Source/2_Core/API/WebRequestProcessor.cs:243
  • `cts` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 44). Every use of it in `UpdateAsync` 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 cts = …;`), which releases it at the end of the scope on every path including a throw. — Source/2_Core/Managers/SteamVR/SteamVRSettings.cs:44
  • `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 50) a new instance is written over it — but `Refresh` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `Refresh` 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 (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Avatars/BattleRoyaleAvatar.cs:50
  • `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 41) a new instance is written over it — but `SetAvatar` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `SetAvatar` 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 (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/GreetingsView/ReplaysPreviewPanel.cs:41
  • `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 183) a new instance is written over it — but `OnInit` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `OnInit` 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 (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/OpponentsView/BattleRoyaleOpponentsList.cs:183
  • `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 110) a new instance is written over it — but `SetData` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `SetData` 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 (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/BeatmapReplayLaunchPanel/BasicReplayDetailPanel.cs:110
  • `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 242) a new instance is written over it — but `OnClose` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `OnClose` 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 (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/ReplayDetail/BeatmapDownloadDialog.cs:242
  • `tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 125) a new instance is written over it — but `UpdateAvatar` itself reads through `tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `UpdateAvatar` 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 (`tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/Leaderboard/Components/Basic/PlayerAvatar.cs:125
  • `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 59) a new instance is written over it — but `CancelDownloading` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `CancelDownloading` 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 (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/Leaderboard/Components/Header/DownloadScoresModal.cs:59
  • `_downloadCancellationSource` is a `CancellationTokenSource` this type creates itself, and here (line 212) a new instance is written over it — but `OnResume` itself reads through `_downloadCancellationSource` before replacing it, so it expects an instance to be there, and nothing earlier in `OnResume` 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 (`_downloadCancellationSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:212

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 propagation6.8 / 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 41/89 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. (×38) — Source/2_Core/API/Authentication.cs:29, Source/2_Core/API/Authentication.cs:34, Source/2_Core/API/Authentication.cs:76, …
  • No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. — Source/2_Core/API/WebRequestProcessor.cs:310

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`. In Rust, where a guard or permit releases when it is dropped, whether a release written BY HAND — `add_permits` after a forgotten permit, `force_unlock` after a leaked guard, a raw lock's `unlock` — matches the state the function's own acquisitions put the primitive in: not after a try or timed acquire whose failure does not leave, not from a cleanup set up before an acquire that can fail, not skipped by a `?`, `return`, `break` or `continue`, and not on top of a guard that still releases itself.

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 unescaped10.0 / 10Exemplary○ Nothing flagged

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.

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.4 / 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.

  • `catch (Exception)` 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. (×3) — Source/2_Core/Managers/DataManager/LeaderboardManager.cs:82, Source/8_UI/Leaderboard/Components/ScoreInfoPanel/MiniProfile.cs:79, Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:253
  • 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. (×6) — Source/2_Core/Managers/SteamVR/SteamVRWebConsoleSession.cs:108, Source/7_Utils/FileManager.cs:162, Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:102, …

What to do

  • Swallowed exception (caught, then discarded)
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.

X5 · Nullable reference types6.2 / 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.

  • This method contradicts itself about `player`: line 47 assigns it with `as IPlayer`, which hands back null rather than throwing when the value is not a `IPlayer`, but line 53 then dereferences it directly as `player.AvatarUrl` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `player` once before the first use and handle the null case, or cast with `(IPlayer)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/GreetingsView/ReplaysPreviewPanel.cs:53
  • This method contradicts itself about `player`: line 217 assigns it with `as IPlayer`, which hands back null rather than throwing when the value is not a `IPlayer`, but line 224 then dereferences it directly as `player.Name` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `player` once before the first use and handle the null case, or cast with `(IPlayer)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/OpponentsView/BattleRoyaleOpponentsList.cs:224
  • This method contradicts itself about `player`: line 151 assigns it with `as IPlayer`, which hands back null rather than throwing when the value is not a `IPlayer`, but line 154 then dereferences it directly as `player.Id` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `player` once before the first use and handle the null case, or cast with `(IPlayer)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/BeatmapReplayLaunchPanel/BasicReplayDetailPanel.cs:154
  • ~4.7 `!` suppressions per 1k syntax nodes — 1000 suppression(s) across the 212494 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

  • Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

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 Health61.8Adequate — gated by D18Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture55.6Adequate — gated by AX2, AX5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity49.4Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness29.8Weak — gated by D8, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security26.3Weak — gated by D29, D36, C2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance70.0StrongStrongest area.
Unscored — 3 check(s) recorded observations but carry no score

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

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 9 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 — 50 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • C1 Data Protection — 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.
  • D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
  • D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
  • D19 Documentation Quality — D19 withholds "XML-doc coverage": 1 candidate(s) (1 of them low-coverage Warnings on library projects) were measured and not published.
  • 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.
  • D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 9 candidate(s) found and not reported.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • DM1 Domain Modelling — not scored — this repository shows 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 — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
  • 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.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's C# was read, and every log call in it goes through a logger that takes one finished message — its own wrapper, log4net, Console or Debug — so an interpolated message there loses nothing the API could have kept. Calls through Microsoft.Extensions.Logging, Serilog, NLog or ZLogger, or any logger with a message-template overload, would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 44 finding(s)
D17 · Explicit Debt · AnalyzerSeverityNone · ×14
  • AnalyzerSeverityNone Source/.editorconfig:142 — MA0002 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:143 — MA0004 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:144 — MA0006 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:145 — MA0011 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:146 — MA0021 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:148 — MA0048 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:149 — MA0046 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:150 — MA0049 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:151 — MA0051 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:152 — MA0055 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:153 — MA0069 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:154 — MA0074 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:155 — MA0099 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone Source/.editorconfig:158 — CS0436 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
D17 · Explicit Debt · WriteOnlyPrivateField · ×7
  • WriteOnlyPrivateField Source/7_Utils/Interop/Interops/BeatSaviorInterop.cs:20 — private HarmonyAutoPatch? _uploadScoreMethodPatch — 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 Source/7_Utils/Interop/Interops/Cam2Interop.cs:93 — private HarmonyAutoPatch? _headPositionPropertyPatch — 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 Source/7_Utils/Interop/Interops/Cam2Interop.cs:94 — private HarmonyAutoPatch? _headRotationPropertyPatch — 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 Source/7_Utils/Interop/Interops/CountersPlusInterop.cs:18 — private HarmonyAutoPatch _missedCounterInitPatch — assigned 2 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 Source/7_Utils/Interop/Interops/NoodleExtensionsInterop.cs:15 — private HarmonyAutoPatch _callbacksControllerPatch — 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 Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:80 — private HarmonyAutoPatch _playViewManagerActivatePatch — assigned 2 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 Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:92 — private string _websiteUrl — assigned 2 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 · EmptyCatchBlock · ×6
  • EmptyCatchBlock Source/2_Core/Managers/SteamVR/SteamVRWebConsoleSession.cs:108 — 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 Source/7_Utils/FileManager.cs:162 — 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 Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:102 — 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 Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:170 — 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 Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:197 — 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 Source/8_UI/MainMenu/SpecialEvent/SpecialEventMapPanel.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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · FileScopedPragmaDisable · ×2
  • FileScopedPragmaDisable Source/8_UI/MainMenu/OtherNews/MapNewsPanel.cs:11 — #pragma warning disable CS0618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable Source/8_UI/MainMenu/TextNews/TextNewsPanel.cs:8 — #pragma warning disable CS0618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×2
  • Orphaned knowledge Source/2_Core/Localization/TimeLocalizationUtils.cs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge Source/2_Core/Managers/ReplayRecorder.cs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle Source/2_Core/Managers/ReplayRecorder.cs:5 — The namespaces BeatLeader ↔ BeatLeader.Components ↔ BeatLeader.Core.Managers.ReplayEnhancer ↔ BeatLeader.DataManager ↔ BeatLeader.Manager ↔ BeatLeader.Models ↔ BeatLeader.Models.AbstractReplay ↔ BeatLeader.Models.Replay ↔ BeatLeader.Replayer ↔ BeatLeader.Replayer.Emulation ↔ BeatLeader.Results ↔ BeatLeader.Themes ↔ BeatLeader.UI ↔ BeatLeader.UI.Hub ↔ BeatLeader.UI.MainMenu ↔ BeatLeader.UI.Replayer ↔ BeatLeader.ViewControllers ↔ BeatLeader.WebRequests depend on each other. The lightest dependency in the cycle is BeatLeader → BeatLeader.Core.Managers.ReplayEnhancer (BeatLeader.ReplayRecorder → BeatLeader.Core.Managers.ReplayEnhancer.TrackingDeviceEnhancer, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D30 · Dependency Vulnerabilities · High CVE · ×1
  • REDACTED
D8 · Code Coverage · No automated tests · ×1
  • No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
Serious — 303 finding(s)
X2 · Cancellation propagation · Async method without CancellationToken · ×38
  • Async method without CancellationToken: PlatformTicket Source/2_Core/API/Authentication.cs:29 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: PlatformTicketInternal Source/2_Core/API/Authentication.cs:34 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Login Source/2_Core/API/Authentication.cs:76 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Send Source/2_Core/API/Methods/GetOculusUserRequest.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadIconAsync Source/2_Core/Managers/DataManager/LeaderboardContextsManager.cs:47 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadIconAsync Source/2_Core/Managers/DataManager/MapTypesManager.cs:44 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadIconAsync Source/2_Core/Managers/DataManager/PrestigeLevelsManager.cs:73 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DetectAsync Source/2_Core/Managers/SteamVR/SteamVRControllerDetector.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DetectAsync Source/2_Core/Managers/SteamVR/SteamVRHeadsetDetector.cs:23 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateEditorFlowCoordinator Source/2_Core/Replayer/Emulation/Players/Avatar/BeatAvatarLoader.cs:93 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: StartReplayFromLeaderboardAsync Source/2_Core/Replayer/ReplayerMenuLoader.cs:54 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadBeatmapForLeaderboardAsync Source/2_Core/Replayer/ReplayerMenuLoader.cs:77 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadAndAppendReplay Source/2_Core/Replayer/ReplayerMenuLoader.cs:160 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: StartLastReplayAsync Source/2_Core/Replayer/ReplayerMenuLoader.cs:263 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CanLaunchReplay Source/2_Core/Replayer/ReplayerMenuLoader.cs:290 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadOptionalDataAsync Source/2_Core/Replayer/ReplayerMenuLoader.cs:393 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: InstallBeatmap Source/7_Utils/FileManager.cs:19 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ExtractFiles Source/7_Utils/FileManager.cs:34 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Awake Source/8_UI/FlowCoordinator/BeatLeaderHubAvatarController.cs:40 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UploadAvatar Source/8_UI/FlowCoordinator/BeatLeaderHubAvatarController.cs:70 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadAvatar Source/8_UI/FlowCoordinator/BeatLeaderHubAvatarController.cs:89 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadAvatarFromPlayerAsync Source/8_UI/FlowCoordinator/BeatLeaderHubAvatarController.cs:103 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SetData Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Avatars/BattleRoyaleReplayBadge.cs:15 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LaunchBattle Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/BattleRoyaleFlowCoordinator.cs:189 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SetBeatmap Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/GreetingsView/BeatmapPreviewPanel.cs:45 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 13 more in this group — see findings.md.
C2 · Access Controls · No authorization · ×35
  • No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • No authorization REDACTED:86 — `BeatmapTimeController.Rewind` 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:134 — `BeatmapTimeController.SetSpeedMultiplier` 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 Source/2_Core/Replayer/BeatmapVisualsController.cs:101 — `BeatmapVisualsController.PauseCutScoreSpawner` 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 Source/2_Core/Replayer/BeatmapVisualsController.cs:105 — `BeatmapVisualsController.PauseSabersSparkles` 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 Source/2_Core/Replayer/BeatmapVisualsController.cs:116 — `BeatmapVisualsController.ModifyLevelFailedTextEffect` 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 Source/2_Core/Replayer/BeatmapVisualsController.cs:120 — `BeatmapVisualsController.ModifyComboPanel` 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 Source/2_Core/Replayer/BeatmapVisualsController.cs:131 — `BeatmapVisualsController.ModifyEnergyPanel` 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 Source/2_Core/Replayer/BeatmapVisualsController.cs:154 — `BeatmapVisualsController.ModifyDebrisPhysics` 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 — `ReplayerCameraController.SetFov` 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:48 — `ReplayerCameraController.SetView` 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 Source/2_Core/Replayer/Emulation/Players/Avatar/BeatAvatarController.cs:18 — `BeatAvatarController.SetVisuals` 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:45 — `MenuBeatAvatarController.SetLoading` 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 — `MenuBeatAvatarController.Present` 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:67 — `MenuBeatAvatarController.Hide` 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 Source/2_Core/Replayer/Emulation/Scoring/NoteControllerEmulator.cs:19 — `NoteControllerEmulator.Setup` 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:53 — `ReplayFinishController.Exit` 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:68 — `ReplayPauseController.Pause` 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:81 — `ReplayPauseController.Resume` 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:15 — `DummyViewController.Init` 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:216 — `LevelSelectionViewController.Dismiss` 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 — `ReplayManagerViewController.NavigateToReplay` 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 Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:31 — `HeckNavigationController.NavigateToReplayAsync` 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 Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:88 — `HeckNavigationController.Initialize` 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 Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:120 — `HeckNavigationController.Dispose` 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.
  • + 10 more in this group — see findings.md.
AX2 · Stateful singletons · Process-global static state · ×32
  • Process-global static state: HarmonyHelper Source/0_Harmony/HarmonyHelper.cs:6 — `HarmonyHelper` 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 (_harmony, _initialized; e.g. `_harmony` at line 13). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: HarmonySilencer Source/0_Harmony/HarmonySilencer.cs:8 — `HarmonySilencer` 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 (silencersRegistry; e.g. `silencersRegistry` at line 23). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: PlayerActiveStateChangedEventPatch Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:43 — `PlayerActiveStateChangedEventPatch` 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 (spectator; e.g. `spectator` at line 51). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: MainFlowCoordinatorDidActivatePatch Source/0_Harmony/UIPatches/MainFlowCoordinatorPatch.cs:8 — `MainFlowCoordinatorDidActivatePatch` 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 (_viewController; e.g. `_viewController` at line 18). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: MainFlowCoordinatorWillChangePatch Source/0_Harmony/UIPatches/MainFlowCoordinatorPatch.cs:24 — `MainFlowCoordinatorWillChangePatch` 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 (mainCoordinator, changingToMain; e.g. `mainCoordinator` at line 32). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ConfigFileData Source/1_Config/ConfigFileData.cs:13 — `ConfigFileData` 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 (Instance; e.g. `Instance` at line 25). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: BLLocalization Source/2_Core/Localization/BLLocalization.cs:8 — `BLLocalization` 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 (_baseGameLanguage, _blLanguageAnalog, translations, _lastUsedLanguage; e.g. `_baseGameLanguage` at line 14). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: LeaderboardState Source/2_Core/Managers/Leaderboard/LeaderboardState.cs:6 — `LeaderboardState` 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 (_selectedBeatmapKey, IsAnyBeatmapSelected, SelectedLeaderboardKey, _selectedBeatmapLevel, _isVisible, _scoresScope; e.g. `_selectedBeatmapKey` at line 30). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ModifiersMapManager Source/2_Core/Managers/ModifiersMapManager.cs:11 — `ModifiersMapManager` 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 (CurrentModifiersMap; e.g. `CurrentModifiersMap` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ReplayRecorder Source/2_Core/Managers/ReplayRecorder.cs:20 — `ReplayRecorder` 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 (_instance; e.g. `_instance` at line 191). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: BundleLoader Source/3_AssetBundle/BundleLoader.cs:12 — `BundleLoader` 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 (_ready, MonkeyPrefab, AccuracyGraphPrefab, ThemesCollection, SaberPrefab, HeadPrefab; e.g. `_ready` at line 34). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ReeModalSystem Source/8_UI/Abstract/ReeModalSystem.cs:12 — `ReeModalSystem` 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 (ActiveModals; e.g. `ActiveModals` at line 36). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AvatarStorage Source/8_UI/AvatarStorage.cs:16 — `AvatarStorage` 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 (Cache; e.g. `Cache` at line 22). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: HeckNavigationController Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:15 — `HeckNavigationController` 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 (_playViewManagerStartMethod, _playViewManagerEarlyDismissMethod, _playViewManagerInitMethod, _playViewManagerActivateMethod, _playViewManagerFlowCoordinatorField, _playViewManagerViewControllersField; e.g. `_playViewManagerStartMethod` at line 91). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ModPanelUI Source/8_UI/ModPanel/ModPanelUI.cs:7 — `ModPanelUI` 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 (_tabActive; e.g. `_tabActive` at line 17). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ReeUIComponentV2 Source/8_UI/ReeUIComponentV2.cs:15 — `ReeUIComponentV2` 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 (BsmlCache; e.g. `BsmlCache` at line 23). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: StatsStorage Source/8_UI/StatsStorage.cs:5 — `StatsStorage` 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 (cachedReplayStats; e.g. `cachedReplayStats` at line 9). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Plugin Source/Plugin.cs:13 — `Plugin` 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 (UserAgent; e.g. `UserAgent` at line 53). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: EnvironmentManagerPatch Source/0_Harmony/MiscellaneousPatches/EnvironmentManagerPatch.cs:6 — `EnvironmentManagerPatch` 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 (_environmentType; e.g. `_environmentType` at line 11). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ResultsViewControllerPatches Source/0_Harmony/UIPatches/ResultsViewControllerPatch.cs:6 — `ResultsViewControllerPatches` 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 (_resultsScreen; e.g. `_resultsScreen` at line 14). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Authentication Source/2_Core/API/Authentication.cs:14 — `Authentication` 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 (Platform, _signedIn, _taskSource; e.g. `Platform` at line 26). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: PersistentSingletonWebRequestBase Source/2_Core/API/PersistentWebRequest.cs:66 — `PersistentSingletonWebRequestBase` 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 (tokenSource, Instance; e.g. `tokenSource` at line 87). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: OnGameplayCoreInstaller Source/2_Core/Installers/OnGameplayCoreInstaller.cs:24 — `OnGameplayCoreInstaller` 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 (_submissionTicket; e.g. `_submissionTicket` at line 160). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: OnMenuInstaller Source/2_Core/Installers/OnMenuInstaller.cs:16 — `OnMenuInstaller` 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 (_container; e.g. `_container` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: HiddenPlayersCache Source/2_Core/Managers/DataManager/HiddenPlayersCache.cs:10 — `HiddenPlayersCache` 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 (HiddenPlayers; e.g. `HiddenPlayers` at line 48). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • + 7 more in this group — see findings.md.
D17 · Explicit Debt · Dead code · ×23
  • Dead code: Postfix Source/0_Harmony/InstallersPatches/MultiplayerLevelDataEnhancerPatch.cs:8 — Method Postfix — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: Postfix Source/0_Harmony/InstallersPatches/PostSwingRatingEnhancerPatch.cs:26 — Method Postfix — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: Postfix Source/0_Harmony/InstallersPatches/PreSwingRatingEnhancerPatch.cs:12 — Method Postfix — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ImplicitTypeConverter Source/1_Config/Json/ImplicitTypeConverter.cs:6 — NamedType ImplicitTypeConverter — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: OnMainServerChanged Source/2_Core/Managers/DataManager/ProfileManager.cs:136 — Method OnMainServerChanged — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ExMachinaBasicResponse Source/2_Core/Models/API/BeatLeader/ExMachinaResponse.cs:2 — NamedType ExMachinaBasicResponse — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: LateTickablePoolItem Source/2_Core/Models/Zenject/LateTickablePoolItem.cs:4 — NamedType LateTickablePoolItem — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: BattleRoyaleHeadVRController Source/3_AssetBundle/Replayer/BattleRoyale/BattleRoyaleHeadVRController.cs:4 — NamedType BattleRoyaleHeadVRController — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: BattleRoyaleSaberVRController Source/3_AssetBundle/Replayer/BattleRoyale/BattleRoyaleSaberVRController.cs:4 — NamedType BattleRoyaleSaberVRController — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: OnValidate Source/3_AssetBundle/Replayer/BattleRoyale/BattleRoyaleVRController.cs:29 — Method OnValidate — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: MaterialDuplicator Source/3_AssetBundle/Replayer/BattleRoyale/MaterialDuplicator.cs:4 — NamedType MaterialDuplicator — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: DespawnCustomBomb Source/7_Utils/Interop/Interops/CustomNotesInterop.cs:71 — Method DespawnCustomBomb — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ScoreSaberInterop Source/7_Utils/Interop/Interops/ScoreSaberInterop.cs:10 — NamedType ScoreSaberInterop — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: GetPositiveMultiplier Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:305 — Method GetPositiveMultiplier — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: GetNegativeMultiplier Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:313 — Method GetNegativeMultiplier — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ReplayFilePattern Source/7_Utils/Replays/ReplayManager.cs:22 — Field ReplayFilePattern — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ObservableDictionary Source/7_Utils/UtilityClasses/ObservableDictionary.cs:6 — NamedType ObservableDictionary — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: SliderValuesApplier Source/7_Utils/UtilityClasses/SliderValuesApplier.cs:6 — NamedType SliderValuesApplier — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ExMachinaVisibleToRole Source/8_UI/Leaderboard/Components/Header/LeaderboardInfoPanel.cs:383 — Method ExMachinaVisibleToRole — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: RtToolsVisibleToRole Source/8_UI/Leaderboard/Components/Header/LeaderboardInfoPanel.cs:387 — Method RtToolsVisibleToRole — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: StarSymbol Source/8_UI/Leaderboard/Components/Header/SkillTriangle.cs:37 — Field StarSymbol — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ContextsModalOption Source/8_UI/Leaderboard/Components/MainPanel/Contexts/ContextsModalOption.cs:10 — NamedType ContextsModalOption — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: HandlePositionOffsetChanged Source/8_UI/Replayer/Components/Settings/Views/CameraView/ViewParams/PlayerViewCameraParams.cs:130 — Method HandlePositionOffsetChanged — Roslyn's SymbolFinder walked every project the solution loads, including BeatLeader, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · TodoComment · ×12
  • TodoComment Source/0_Harmony/HarmonyMultisilencer.cs:8 — //TODO: rework — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/2_Core/Managers/ModifiersMapManager.cs:10 — //TODO: rework — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/2_Core/Models/API/BeatLeader/LeaderboardsInfoResponse.cs:107 — //TODO: rework — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/2_Core/Installers/OnGameplayCoreInstaller.cs:205 — // TODO: remove this after verifying of an "allowed flows" strategy — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:177 — //TODO: potential bug — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/2_Core/Replayer/Emulation/Players/Avatar/BeatAvatarLoader.cs:50 — //TODO: Potential bug: at least one BeatAvatarEditorFlowCoordinator must be instantiated first — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/2_Core/Replayer/ReplayBeatmapData.cs:31 — //TODO: current algorithm does not work properly. rework — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/2_Core/Replayer/Tweaking/Tweaks/JumpDistanceTweak.cs:23 — //TODO: add br (player switch) support — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/2_Core/Replayer/Tweaking/Tweaks/ReplayFailTweak.cs:19 — //TODO: add br support — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/7_Utils/Replays/ReplayManager.cs:465 — //TODO: remove after BSOR V2 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:96 — //TODO: Not used — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/8_UI/MainMenu/NewsViewPanel.cs:16 — //TODO: Oh my god please forgive me for this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
X1 · Async correctness · async void method · ×11
  • async void method: Awake Source/8_UI/FlowCoordinator/BeatLeaderHubAvatarController.cs:40 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: LaunchBattle Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/BattleRoyaleFlowCoordinator.cs:189 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: NavigateToReplay REDACTED:35 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: LoadPreview Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/ReplayPreviewLoader.cs:19 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: OnInitialize Source/8_UI/FlowCoordinator/HubViews/BeatLeaderHubMainViewController.cs:132 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: OpenSongOrDownloadDialog Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:43 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: Download Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:111 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: OpenSongOrDownloadDialog Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:98 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: HandlePlayButtonClicked Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:217 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ParseSelfIfNeeded Source/8_UI/ReeUIComponentV2.cs:205 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: LoadAndAssignImage Source/8_UI/Replayer/Components/BeatmapLevelPreview.cs:98 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
D17 · Explicit Debt · ObsoleteWithCallers · ×9
  • ObsoleteWithCallers Source/2_Core/API/PersistentWebRequest.cs:116 — [Obsolete] RequestState
  • ObsoleteWithCallers Source/2_Core/API/PersistentWebRequest.cs:122 — [Obsolete] FailReason
  • ObsoleteWithCallers Source/2_Core/API/PersistentWebRequest.cs:136 — [Obsolete] StateChangedEvent
  • ObsoleteWithCallers Source/2_Core/API/PersistentWebRequest.cs:156 — [Obsolete] ProgressChangedEvent
  • ObsoleteWithCallers Source/2_Core/Replayer/ReplayerCache.cs:6 — [Obsolete] ReplayerCache
  • ObsoleteWithCallers Source/7_Utils/FormatUtils.cs:147 — [Obsolete] GetRelativeTime
  • ObsoleteWithCallers Source/7_Utils/FormatUtils.cs:153 — [Obsolete] GetRelativeTime
  • ObsoleteWithCallers Source/8_UI/Abstract/ReeModalSystem.cs:12 — [Obsolete] ReeModalSystem
  • ObsoleteWithCallers Source/8_UI/Components/Reactive/Native/ValueAnimator.cs:5 — [Obsolete] ValueAnimator
AX2 · Stateful singletons · Stateful shared instance · ×8
  • Stateful shared instance: AppCache Source/7_Utils/UtilityClasses/AppCache.cs:9 — `AppCache` is not registered, but `ReplayHeadersCache` creates it and keeps it in the static `infoCache`, 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 (_loadTask, _cache, _initialized, _saveTask; e.g. `_loadTask` at line 41).
  • Stateful shared instance: WebRequestParams Source/2_Core/API/Models/WebRequestParams.cs:5 — `WebRequestParams` is not registered, but `DownloadMapRequest` creates it and keeps it in the static `RequestParams`, 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 (UploadTrackingPrecision, DownloadTrackingPrecision; e.g. `UploadTrackingPrecision` at line 14).
  • Stateful shared instance: ReplayLaunchData Source/2_Core/Models/Replayer/ReplayLaunchData.cs:10 — `ReplayLaunchData` is not registered, but `ReplayerMenuLoader` creates it and keeps it in the static `ReplayerLauncher.LaunchData`, 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 (_replays, _beatmapLevel, _settings, EnvironmentInfo, ReplayerBindings; e.g. `_replays` at line 18).
  • Stateful shared instance: PoseReceiver Source/7_Utils/Interop/Interops/Cam2Interop.cs:62 — `PoseReceiver` is not registered, but `Cam2Interop` creates it and keeps it in the static `poseReceiver`, 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 (Position, Rotation; e.g. `Position` at line 67).
  • Stateful shared instance: HarmonyMultisilencer Source/0_Harmony/HarmonyMultisilencer.cs:9 — `HarmonyMultisilencer` is not registered, but `ScoreSaberInterop` creates it and keeps it in the static `_installatorsSilencer`, 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 (_atLeastOneSilencerIsEnabled; e.g. `_atLeastOneSilencerIsEnabled` at line 20).
  • Stateful shared instance: ReplayManagerSearchTheme Source/8_UI/Models/Style/ReplayManagerSearchTheme.cs:6 — `ReplayManagerSearchTheme` is not registered, but the singleton `BeatLeaderHubTheme` creates it and keeps it in `ReplayManagerSearchTheme`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_searchHighlightColor, _searchHighlightStyle; e.g. `_searchHighlightColor` at line 10).
  • Stateful shared instance: BodySettings Source/2_Core/Models/Replayer/BodySettings.cs:13 — `BodySettings` is not registered, but the singleton `ReplayerSettings` creates it and keeps it in `BodySettings`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (Configs, _serializedConfigs; e.g. `Configs` at line 23).
  • Stateful shared instance: SerializableColorSet Source/8_UI/Models/Style/SerializableColorSet.cs:10 — `SerializableColorSet` is not registered, but the singleton `BeatLeaderHubMenuButtonsTheme` creates it and keeps it in `ReplayManagerButtonColors`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_activeColor, _hoveredColor, _notInteractableColor, _color; e.g. `_activeColor` at line 14).
X18 · Disposal-pattern correctness · Owned disposable field overwritten without releasing the previous instance · ×8
  • Owned disposable field overwritten without releasing the previous instance Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Avatars/BattleRoyaleAvatar.cs:50 — `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 50) a new instance is written over it — but `Refresh` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `Refresh` 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 (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
  • Owned disposable field overwritten without releasing the previous instance Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/GreetingsView/ReplaysPreviewPanel.cs:41 — `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 41) a new instance is written over it — but `SetAvatar` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `SetAvatar` 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 (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
  • Owned disposable field overwritten without releasing the previous instance Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/OpponentsView/BattleRoyaleOpponentsList.cs:183 — `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 183) a new instance is written over it — but `OnInit` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `OnInit` 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 (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
  • Owned disposable field overwritten without releasing the previous instance Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/BeatmapReplayLaunchPanel/BasicReplayDetailPanel.cs:110 — `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 110) a new instance is written over it — but `SetData` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `SetData` 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 (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
  • Owned disposable field overwritten without releasing the previous instance Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/ReplayDetail/BeatmapDownloadDialog.cs:242 — `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 242) a new instance is written over it — but `OnClose` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `OnClose` 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 (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
  • Owned disposable field overwritten without releasing the previous instance Source/8_UI/Leaderboard/Components/Basic/PlayerAvatar.cs:125 — `tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 125) a new instance is written over it — but `UpdateAvatar` itself reads through `tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `UpdateAvatar` 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 (`tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
  • Owned disposable field overwritten without releasing the previous instance Source/8_UI/Leaderboard/Components/Header/DownloadScoresModal.cs:59 — `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 59) a new instance is written over it — but `CancelDownloading` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `CancelDownloading` 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 (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
  • Owned disposable field overwritten without releasing the previous instance Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:212 — `_downloadCancellationSource` is a `CancellationTokenSource` this type creates itself, and here (line 212) a new instance is written over it — but `OnResume` itself reads through `_downloadCancellationSource` before replacing it, so it expects an instance to be there, and nothing earlier in `OnResume` 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 (`_downloadCancellationSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
D35 · Change Coupling · Change coupling · ×6
  • Change coupling: EventNewsPanel.cs ↔ MapNewsPanel.cs Source/8_UI/MainMenu/OtherNews/EventNewsPanel.cs:1 — `Source/8_UI/MainMenu/OtherNews/EventNewsPanel.cs` and `Source/8_UI/MainMenu/OtherNews/MapNewsPanel.cs` change together 82% of the time (9 of the 11 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; 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 `dfa7592b` Migrated PlatformEventsRequest to async. Added special event loading.; `19a7d0a2` Added selector for main/seasonal news.; `4828a4aa` Fixed after merging listview branch. — run `git show` on any of them.
  • Change coupling: ReplayerNotesCutter.cs ↔ ReplayerScoreProcessor.cs Source/2_Core/Replayer/Emulation/ReplayerNotesCutter.cs:1 — `Source/2_Core/Replayer/Emulation/ReplayerNotesCutter.cs` and `Source/2_Core/Replayer/Emulation/Scoring/ReplayerScoreProcessor.cs` change together 60% of the time (6 of the 10 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `7fa7781b` Finished support for left handed replays in battle royale replays; `71e0094f` fixed energy calculation; `2a55d718` Counters+ interop and a little reflector rewrite (at that commit the files were still `2_Core/Replayer/Emulation/ReplayerNotesCutter.cs` and `2_Core/Replayer/Emulation/Scoring/ReplayerScoreProcessor.cs`) — run `git show` on any of them.
  • Change coupling: EventNewsPanel.cs ↔ MapPreviewPanel.cs Source/8_UI/MainMenu/OtherNews/EventNewsPanel.cs:1 — `Source/8_UI/MainMenu/OtherNews/EventNewsPanel.cs` and `Source/8_UI/MainMenu/OtherNews/MapPreviewPanel.cs` change together 57% of the time (8 of the 14 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `a37c2faf` Fixed after reactive update. (at that commit the file was still `Source/8_UI/MainMenu/OtherNews/FeaturedPreviewPanel.cs`); `d078d994` Added trending maps preview popup and sound (at that commit the file was still `Source/8_UI/MainMenu/OtherNews/FeaturedPreviewPanel.cs`); `4950e4d5` Added event end time (at that commit the file was still `Source/8_UI/MainMenu/OtherNews/FeaturedPreviewPanel.cs`) — run `git show` on any of them.
  • Change coupling: REDACTED ↔ MapNewsPanel.cs REDACTED:1 — `REDACTED` and `Source/8_UI/MainMenu/OtherNews/MapNewsPanel.cs` change together 55% of the time (6 of the 11 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `dfa7592b` Migrated PlatformEventsRequest to async. Added special event loading.; `19a7d0a2` Added selector for main/seasonal news.; `5e2682af` Fixed various issues from testing with Debug Unity — run `git show` on any of them.
  • Change coupling: REDACTED ↔ ReplayTimeController.cs REDACTED:1 — `REDACTED` and `Source/2_Core/Replayer/ReplayTimeController.cs` change together 50% of the time (5 of the 10 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `b9bcb070` 1.37.5 initial changes + BSML 1.12.0; `ec4d5d12` fixed replay finish 0.2sec earlier (at that commit the files were still `REDACTED` and `2_Core/Replayer/ReplayTimeController.cs`); `6b88fec2` auto-exit nf replay fixes (at that commit the files were still `REDACTED` and `2_Core/Replayer/ReplayTimeController.cs`) — run `git show` on any of them.
  • Change coupling: REDACTED ↔ SpecialEventPanel.cs REDACTED:1 — `REDACTED` and `Source/8_UI/MainMenu/SpecialEvent/SpecialEventPanel.cs` change together 50% of the time (5 of the 10 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `6276122a` Made SpecialEventPanel open when an event cell is clicked.; `dfa7592b` Migrated PlatformEventsRequest to async. Added special event loading.; `7c833b6b` Renamed HappeningEvent to SpecialEvent. — run `git show` on any of them.
X3 · Exception handling · Swallowed exception (empty catch) · ×6
  • Swallowed exception (empty catch) Source/2_Core/Managers/SteamVR/SteamVRWebConsoleSession.cs:108 — 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) Source/7_Utils/FileManager.cs:162 — 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) Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:102 — 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) Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:170 — 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) Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:197 — 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) Source/8_UI/MainMenu/SpecialEvent/SpecialEventMapPanel.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.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×4
  • Edited copy of a member (9 corresponding lines) Source/7_Utils/ReflectionUtils.cs:64 — Source/7_Utils/ReflectionUtils.cs:64-72 | Source/7_Utils/ReflectionUtils.cs:74-82 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/8_UI/Components/Reactive/Native/ValueAnimator.cs:44 — Source/8_UI/Components/Reactive/Native/ValueAnimator.cs:44-52 | Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:67-78 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/BeatmapReplayLaunchPanel/ReplayStatisticsPanel.cs:158 — Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/BeatmapReplayLaunchPanel/ReplayStatisticsPanel.cs:158-166 | Source/8_UI/Leaderboard/Components/ScoreInfoPanel/ScoreInfoPanel.cs:124-158 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/2_Core/API/Methods/ClanPlayersRequest.cs:81 — Source/2_Core/API/Methods/ClanPlayersRequest.cs:81-90 | Source/2_Core/API/Methods/ScoresRequest.cs:74-82 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D3 · God Classes · MethodTooLong · ×3
  • MethodTooLong: ReplayStatisticUtils.Accuracy Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:192 — MethodTooLong — Accuracy runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× 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: SpecialEventBar.Construct Source/8_UI/MainMenu/SpecialEvent/SpecialEventBar.cs:35 — MethodTooLong — Construct runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: BeatmapPreviewPanel.Construct Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/GreetingsView/BeatmapPreviewPanel.cs:92 — MethodTooLong — Construct runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×3
  • Edited copy of a member (17 corresponding lines) Source/2_Core/Models/API/BeatLeader/Score.cs:61 — Source/2_Core/Models/API/BeatLeader/Score.cs:61-77 | Source/2_Core/Models/ClanPlayer.cs:37-53 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Source/2_Core/Models/API/BeatLeader/Score.cs:43 — Source/2_Core/Models/API/BeatLeader/Score.cs:43-59 | Source/2_Core/Models/ClanPlayer.cs:19-35 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/FiltersPanel/BeatmapFilter/BeatmapCharacteristicPanel.cs:55 — Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/FiltersPanel/BeatmapFilter/BeatmapCharacteristicPanel.cs:55-71 | Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/FiltersPanel/BeatmapFilter/BeatmapDifficultyPanel.cs:57-73 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×3
  • Edited copy of a member (7 corresponding lines) Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:349 — Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:349-355 | Source/7_Utils/ReflectionUtils.cs:20-26 — 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) Source/2_Core/API/WebRequestFactory.cs:26 — Source/2_Core/API/WebRequestFactory.cs:26-32 | Source/2_Core/API/WebRequestFactory.cs:40-46 — 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) Source/8_UI/Replayer/Components/LayoutEditor/EditorWindow/LayoutEditorWindow.cs:328 — Source/8_UI/Replayer/Components/LayoutEditor/EditorWindow/LayoutEditorWindow.cs:328-335 | Source/8_UI/Replayer/Components/LayoutEditor/LayoutComponent/LayoutEditorComponent.cs:162-168 — 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 (13 lines × 2) · ×3
  • Duplicated block (13 lines × 2) Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:250 — Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:250-262 | Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:299-311 — 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 `Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:250` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Source/7_Utils/UtilityClasses/GifLoader.cs:579 — Source/7_Utils/UtilityClasses/GifLoader.cs:579-591 | Source/7_Utils/UtilityClasses/GifLoader.cs:603-615 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (13 lines × 2) Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:53 — Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:53-65 | Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:111-123 — before extracting anything, compare `Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs` and `Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `mapDetail` to `MapDetail` in one and `TrendingMapData` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
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 Source/7_Utils/UtilityClasses/AppCache.cs:46 — `_loadTask.Wait()` 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 Source/7_Utils/UtilityClasses/AppCache.cs:80 — `_saveTask.Wait()` 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).
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×3
  • Swallowed exception (caught, then discarded) Source/2_Core/Managers/DataManager/LeaderboardManager.cs:82 — `catch (Exception)` 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.
  • Swallowed exception (caught, then discarded) Source/8_UI/Leaderboard/Components/ScoreInfoPanel/MiniProfile.cs:79 — `catch (Exception)` 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.
  • Swallowed exception (caught, then discarded) Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:253 — `catch (Exception)` 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.
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×3
  • Symbol treated as nullable, then dereferenced unguarded Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/GreetingsView/ReplaysPreviewPanel.cs:53 — This method contradicts itself about `player`: line 47 assigns it with `as IPlayer`, which hands back null rather than throwing when the value is not a `IPlayer`, but line 53 then dereferences it directly as `player.AvatarUrl` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `player` once before the first use and handle the null case, or cast with `(IPlayer)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/OpponentsView/BattleRoyaleOpponentsList.cs:224 — This method contradicts itself about `player`: line 217 assigns it with `as IPlayer`, which hands back null rather than throwing when the value is not a `IPlayer`, but line 224 then dereferences it directly as `player.Name` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `player` once before the first use and handle the null case, or cast with `(IPlayer)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/BeatmapReplayLaunchPanel/BasicReplayDetailPanel.cs:154 — This method contradicts itself about `player`: line 151 assigns it with `as IPlayer`, which hands back null rather than throwing when the value is not a `IPlayer`, but line 154 then dereferences it directly as `player.Id` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `player` once before the first use and handle the null case, or cast with `(IPlayer)` so the failure is reported where it happens — rather than leaving the two readings side by side.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · TooManyMethods · ×2
  • TooManyMethods: TimeLocalizationUtils Source/2_Core/Localization/TimeLocalizationUtils.cs — TooManyMethods — 341 significant lines (blank, comment-only and punctuation-only lines excluded), 74 methods. The bar is 30 methods; this is 44 over it, 2.47× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: FormatUtils Source/7_Utils/FormatUtils.cs — TooManyMethods — 183 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
D3 · God Classes · FileTooLong · ×2
  • FileTooLong: BeatLeaderReplay/Replay.cs Source/2_Core/Models/Replays/BeatLeaderReplay/Replay.cs — FileTooLong — 622 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 122 over it, 1.24× 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: UtilityClasses/GifLoader.cs Source/7_Utils/UtilityClasses/GifLoader.cs — FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×2
  • Edited copy of a member (26 corresponding lines) Source/7_Utils/Replays/AbstractReplayUtils.cs:62 — Source/7_Utils/Replays/AbstractReplayUtils.cs:62-87 | Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:417-442 — 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) Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:175 — Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:175-200 | Source/8_UI/MainMenu/SpecialEvent/SpecialEventMapPanel.cs:143-168 — 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) Source/2_Core/Managers/SteamVR/SteamVRControllerDetector.cs:18 — Source/2_Core/Managers/SteamVR/SteamVRControllerDetector.cs:18-40 | Source/2_Core/Managers/SteamVR/SteamVRHeadsetDetector.cs:27-47 — 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) Source/8_UI/Leaderboard/Components/ClanScoreDetails/ClanScorePanel.cs:185 — Source/8_UI/Leaderboard/Components/ClanScoreDetails/ClanScorePanel.cs:185-207 | Source/8_UI/Leaderboard/Components/ClanScoreDetails/ClanScorePanel.cs:209-229 — 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 · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) Source/2_Core/API/Methods/ScoresOfClanRequest.cs:11 — Source/2_Core/API/Methods/ScoresOfClanRequest.cs:11-19 | Source/2_Core/API/Methods/ScoresRequest.cs:11-19 — 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) Source/8_UI/Leaderboard/Components/ClanScoreDetails/ClanScorePanel.cs:259 — Source/8_UI/Leaderboard/Components/ClanScoreDetails/ClanScorePanel.cs:259-267 | Source/8_UI/Leaderboard/Components/MainPanel/Pagination.cs:91-99 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:350 — Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:350-355 | Source/7_Utils/ReflectionUtils.cs:21-26 — 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.
  • Duplicated block (6 lines × 2) Source/7_Utils/Interop/Interops/PlaylistsLibInterop.cs:10 — Source/7_Utils/Interop/Interops/PlaylistsLibInterop.cs:10-15 | Source/7_Utils/Interop/Interops/PlaylistsLibInterop.cs:30-37 — 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 `Source/7_Utils/Interop/Interops/PlaylistsLibInterop.cs:10` 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.
GD1 · Unfinished & placeholder code · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException Source/7_Utils/UtilityClasses/GifLoader.cs:346 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Source/7_Utils/UtilityClasses/GifLoader.cs:350 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException Source/7_Utils/UtilityClasses/GifLoader.cs:346 — `DrawTo` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Source/7_Utils/UtilityClasses/GifLoader.cs:350 — `Dispose` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
X1 · Async correctness · Sync-over-async (deadlock risk) · ×2
  • Sync-over-async (deadlock risk) Source/7_Utils/UtilityClasses/AppCache.cs:46 — 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) Source/7_Utils/UtilityClasses/AppCache.cs:80 — 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.
X18 · Disposal-pattern correctness · Owned disposable field is never released · ×2
  • Owned disposable field is never released Source/2_Core/API/WebRequestProcessor.cs:236 — `WebRequestProcessor` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_requestMessage` itself (line 236), which makes that instance its own. But `_requestMessage` is named in none of the methods the disposal search covered: `Dispose` (line 361), `ReleaseBufferIfNeeded` (line 353) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_requestMessage?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released Source/2_Core/API/WebRequestProcessor.cs:243 — `WebRequestProcessor` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_cancellationTokenSource` itself (line 243), which makes that instance its own. But `_cancellationTokenSource` is named in none of the methods the disposal search covered: `Dispose` (line 361), `ReleaseBufferIfNeeded` (line 353) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_cancellationTokenSource?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
AX5 · Architecture & structure · Appears unstructured (no recognised architecture) · ×1
  • Appears unstructured (no recognised architecture) — ~42.9k production LoC (853 types) across 1 project(s) / 39 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
D1 · Cyclomatic Complexity · ReplayUtils.HMDFromName (cyclomatic 71) · ×1
  • ReplayUtils.HMDFromName (cyclomatic 71) Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:190 — ReplayUtils.HMDFromName has cyclomatic complexity 71 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs holds 2 of the 5 methods over the threshold — including the worst — and 84 of the 112 points over it (75%), 3.7× the next-largest file (Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs at 23). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · ReplayUtils.ControllerFromName (cyclomatic 43) · ×1
  • ReplayUtils.ControllerFromName (cyclomatic 43) Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:260 — ReplayUtils.ControllerFromName has cyclomatic complexity 43 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs holds 2 of the 5 methods over the threshold — including the worst — and 84 of the 112 points over it (75%), 3.7× the next-largest file (Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs at 23). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · ReplayStatisticUtils.Accuracy (cyclomatic 38) · ×1
  • ReplayStatisticUtils.Accuracy (cyclomatic 38) Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:192 — ReplayStatisticUtils.Accuracy has cyclomatic complexity 38 (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 · GIFImageBlock.DrawTo (cyclomatic 18) · ×1
  • GIFImageBlock.DrawTo (cyclomatic 18) Source/7_Utils/UtilityClasses/GifLoader.cs:262 — GIFImageBlock.DrawTo 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 · MapEnhancer.modifiers (cyclomatic 17) · ×1
  • MapEnhancer.modifiers (cyclomatic 17) Source/2_Core/Managers/ReplayEnhancer/MapEnhancer.cs:40 — MapEnhancer.modifiers 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.
D12 · Dependency Hygiene · Prerelease dependency · ×1
  • Prerelease dependency: BeatSaberModdingTools.Tasks — BeatSaberModdingTools.Tasks resolves to 2.0.0-beta7, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
D17 · Explicit Debt · BarePragmaDisable · ×1
  • BarePragmaDisable Source/2_Core/Models/Replayer/ReplayerCameraSettings.cs:73 — #pragma warning disable MA0016 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
D18 · Solution Shape · Build failed · ×1
  • Build failed — The target solution did not build cleanly (errors: 6001), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS0246: The type or namespace name 'HarmonyLib' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'BGLib' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'JetBrains' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'IPA' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'UnityEngine' could not be found (are you missing a using directive or an assembly reference?).
D2 · Cognitive Complexity · ReplayStatisticUtils.Accuracy (cognitive 72) · ×1
  • ReplayStatisticUtils.Accuracy (cognitive 72) Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:192 — ReplayStatisticUtils.Accuracy has cognitive complexity 72 (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 · ReplayUtils.HMDFromName (cognitive 70) · ×1
  • ReplayUtils.HMDFromName (cognitive 70) Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:190 — ReplayUtils.HMDFromName has cognitive complexity 70 (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 · ReplayUtils.ControllerFromName (cognitive 41) · ×1
  • ReplayUtils.ControllerFromName (cognitive 41) Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:260 — ReplayUtils.ControllerFromName has cognitive complexity 41 (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 · ExperienceBar.Update (cognitive 34) · ×1
  • ExperienceBar.Update (cognitive 34) Source/8_UI/Leaderboard/Components/TopPanel/ExperienceBar.cs:45 — ExperienceBar.Update has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GIFImageBlock.DrawTo (cognitive 23) · ×1
  • GIFImageBlock.DrawTo (cognitive 23) Source/7_Utils/UtilityClasses/GifLoader.cs:262 — GIFImageBlock.DrawTo has cognitive complexity 23 (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 · ReplayStatisticUtils.ComputeScoreStats (cognitive 20) · ×1
  • ReplayStatisticUtils.ComputeScoreStats (cognitive 20) Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:112 — ReplayStatisticUtils.ComputeScoreStats has cognitive complexity 20 (threshold 15). Of this number, 19 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 · DownloadScoresModal.StartDownloadingInternal (cognitive 19) · ×1
  • DownloadScoresModal.StartDownloadingInternal (cognitive 19) Source/8_UI/Leaderboard/Components/Header/DownloadScoresModal.cs:68 — DownloadScoresModal.StartDownloadingInternal 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 · AbstractScoresTable.UpdateLayout (cognitive 18) · ×1
  • AbstractScoresTable.UpdateLayout (cognitive 18) Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoresTable.cs:77 — AbstractScoresTable.UpdateLayout 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 · MapEnhancer.modifiers (cognitive 16) · ×1
  • MapEnhancer.modifiers (cognitive 16) Source/2_Core/Managers/ReplayEnhancer/MapEnhancer.cs:40 — MapEnhancer.modifiers has cognitive complexity 16 (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 · VRPointerEventsHandler.Update (cognitive 16) · ×1
  • VRPointerEventsHandler.Update (cognitive 16) Source/8_UI/Components/VRPointerEventsHandler.cs:35 — VRPointerEventsHandler.Update has cognitive complexity 16 (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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:232 — Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:232-262 | Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:272-311 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:111 — Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:111-140 | Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:232-263 — 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 (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:317 — Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:317-331 | Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:333-347 — 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 (11 corresponding lines) · ×1
  • Edited copy of a member (11 corresponding lines) Source/7_Utils/FormatUtils.cs:135 — Source/7_Utils/FormatUtils.cs:135-145 | Source/8_UI/MainMenu/OtherNews/EventPreviewPanel.cs:128-139 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 17+ corresponding lines) Source/7_Utils/UtilityClasses/GifLoader.cs:521 — Source/7_Utils/UtilityClasses/GifLoader.cs:521-539 | Source/7_Utils/UtilityClasses/GifLoader.cs:542-563 | Source/7_Utils/UtilityClasses/GifLoader.cs:601-617 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 12+ corresponding lines) Source/2_Core/Models/Replays/BeatLeaderReplay/Replay.cs:680 — Source/2_Core/Models/Replays/BeatLeaderReplay/Replay.cs:680-693 | Source/2_Core/Models/Replays/BeatLeaderReplay/Replay.cs:696-707 | Source/2_Core/Models/Replays/BeatLeaderReplay/Replay.cs:710-721 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 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, 20+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 20+ corresponding lines) Source/2_Core/Models/Replays/BeatLeaderReplay/Replay.cs:150 — Source/2_Core/Models/Replays/BeatLeaderReplay/Replay.cs:150-169 | Source/2_Core/Models/Replays/BeatLeaderReplay/Replay.cs:171-190 | Source/7_Utils/Replays/AbstractReplayUtils.cs:20-42 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 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, 9+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/2_Core/API/Methods/ClanPlayersRequest.cs:51 — Source/2_Core/API/Methods/ClanPlayersRequest.cs:51-61 | Source/2_Core/API/Methods/ClanScoresRequest.cs:38-46 | Source/2_Core/API/Methods/ScoresRequest.cs:44-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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 (68 corresponding lines) · ×1
  • Edited copy of a member (68 corresponding lines) Source/8_UI/MainMenu/OtherNews/EventPreviewPanel.cs:18 — Source/8_UI/MainMenu/OtherNews/EventPreviewPanel.cs:18-85 | Source/8_UI/MainMenu/OtherNews/MapPreviewPanel.cs:16-90 — These two members are one piece of code written twice and then edited apart: 68 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, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) Source/0_Harmony/InstallersPatches/AppInstallerPatch.cs:12 — Source/0_Harmony/InstallersPatches/AppInstallerPatch.cs:12-18 | Source/0_Harmony/InstallersPatches/GameInstallerPatch.cs:11-17 | Source/0_Harmony/InstallersPatches/MenuInstallerPatch.cs:11-17 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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 (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/FiltersPanel/TagFilter/TagSelector.cs:89 — Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/FiltersPanel/TagFilter/TagSelector.cs:89-99 | Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/ReplayDetail/TagsStrip.cs:130-137 — 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 copies of one member (3 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 4+ corresponding lines) Source/2_Core/API/Methods/ClanPlayersRequest.cs:70 — Source/2_Core/API/Methods/ClanPlayersRequest.cs:70-73 | Source/2_Core/API/Methods/ScoresOfClanRequest.cs:67-70 | Source/2_Core/API/Methods/ScoresRequest.cs:62-65 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/ReplayDetail/BeatmapDownloadDialog.cs:153 — Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/ReplayDetail/BeatmapDownloadDialog.cs:153-158 | Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/ReplayDetail/ReplayDeletionDialog.cs:30-36 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 4+ corresponding lines) Source/2_Core/API/Methods/ClanPlayersRequest.cs:39 — Source/2_Core/API/Methods/ClanPlayersRequest.cs:39-42 | Source/2_Core/API/Methods/ClanScoresRequest.cs:28-31 | Source/2_Core/API/Methods/ScoresOfClanRequest.cs:34-37 | Source/2_Core/API/Methods/ScoresRequest.cs:34-37 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 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 copy of a member (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) Source/2_Core/API/Methods/AddFriendRequest.cs:24 — Source/2_Core/API/Methods/AddFriendRequest.cs:24-27 | Source/2_Core/API/Methods/RemoveFriendRequest.cs:23-26 — 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) Source/8_UI/Leaderboard/Components/ScoreInfoPanel/MiniProfile.cs:24 — Source/8_UI/Leaderboard/Components/ScoreInfoPanel/MiniProfile.cs:24-29 | Source/8_UI/Leaderboard/Components/TopPanel/PlayerInfo.cs:22-26 — 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 (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:179 — Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:179-200 | Source/8_UI/MainMenu/SpecialEvent/SpecialEventMapPanel.cs:147-168 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:179` 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 (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:68 — Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:68-86 | Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:126-144 — before extracting anything, compare `Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs` and `Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `dialog` to `MapDownloadDialog?` in one and `MapPreviewDialog?` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:232 — Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:232-248 | Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:272-288 — 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 `Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:232` 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 (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) REDACTED:10 — REDACTED:10-23 | REDACTED:11-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) Source/7_Utils/UtilityClasses/GifLoader.cs:528 — Source/7_Utils/UtilityClasses/GifLoader.cs:528-539 | Source/7_Utils/UtilityClasses/GifLoader.cs:552-563 — 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 `Source/7_Utils/UtilityClasses/GifLoader.cs:528` 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 (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoreRow.cs:202 — Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoreRow.cs:202-209 | Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoreRow.cs:212-219 — 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 `Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoreRow.cs:202` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:119 — Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:119-126 | Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:240-246 — before extracting anything, compare `Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs` and `Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×1
  • Duplicated block (31 lines × 2) Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/FiltersPanel/BeatmapFilter/BeatmapCharacteristicPanel.cs:19 — Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/FiltersPanel/BeatmapFilter/BeatmapCharacteristicPanel.cs:19-49 | Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/FiltersPanel/BeatmapFilter/BeatmapDifficultyPanel.cs:19-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) Source/8_UI/Leaderboard/Components/MainPanel/EmptyBoardMessage.cs:102 — Source/8_UI/Leaderboard/Components/MainPanel/EmptyBoardMessage.cs:102-106 | Source/8_UI/Leaderboard/Components/MainPanel/ScoreRowDivider.cs:35-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) Source/8_UI/MainMenu/OtherNews/EventNewsPanel.cs:26 — Source/8_UI/MainMenu/OtherNews/EventNewsPanel.cs:26-51 | Source/8_UI/MainMenu/OtherNews/MapNewsPanel.cs:44-70 — 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.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience Source/2_Core/API/WebRequestFactory.cs:14 — `new(httpClientHandler)` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked REDACTED:365 — REDACTED 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.
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×1
  • Sync-over-async (deadlock risk) through `.Result` Source/2_Core/Managers/DataManager/OculusMigrationManager.cs:74 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
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 Source/2_Core/Managers/SteamVR/SteamVRSettings.cs:44 — `cts` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 44). Every use of it in `UpdateAsync` 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 cts = …;`), which releases it at the end of the scope on every path including a throw.
Minor — 116 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×37
  • Orphaned file Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/ScoreInfoPanel/MiniProfileButtons.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoreRow.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoresTable.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/ClanScoreDetails/ClanScorePanel.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/BeatLeaderInfo.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Abstract/ReeModalSystem.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/2_Core/Localization/BLLocalization.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/2_Core/Managers/DataManager/PlaylistsManager.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/Basic/PlayerAvatar.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/MainScoresTable.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/LeaderboardSettings.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/7_Utils/UtilityClasses/ScoresTableLayoutHelper.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/Basic/MiniProfileButton.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/Pagination.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/2_Core/Managers/SteamVR/SteamVRSettings.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/ScoreInfoPanel/ScoreOverviewPage2.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/2_Core/Managers/Leaderboard/LeaderboardState.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/7_Utils/Interop/Interops/CustomNotesInterop.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/ScoreRow.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/8_UI/Leaderboard/Components/Basic/HintField.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Source/7_Utils/Replays/ModifiersUtils.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 12 more in this group — see findings.md.
S1 · Web-Security Posture · No inbound model validation detected · ×29
  • 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:86 — `BeatmapTimeController.Rewind` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:134 — `BeatmapTimeController.SetSpeedMultiplier` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/2_Core/Replayer/BeatmapVisualsController.cs:101 — `BeatmapVisualsController.PauseCutScoreSpawner` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/2_Core/Replayer/BeatmapVisualsController.cs:105 — `BeatmapVisualsController.PauseSabersSparkles` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/2_Core/Replayer/BeatmapVisualsController.cs:116 — `BeatmapVisualsController.ModifyLevelFailedTextEffect` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/2_Core/Replayer/BeatmapVisualsController.cs:120 — `BeatmapVisualsController.ModifyComboPanel` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/2_Core/Replayer/BeatmapVisualsController.cs:131 — `BeatmapVisualsController.ModifyEnergyPanel` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/2_Core/Replayer/BeatmapVisualsController.cs:154 — `BeatmapVisualsController.ModifyDebrisPhysics` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:35 — `ReplayerCameraController.SetFov` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:48 — `ReplayerCameraController.SetView` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/2_Core/Replayer/Emulation/Players/Avatar/BeatAvatarController.cs:18 — `BeatAvatarController.SetVisuals` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:45 — `MenuBeatAvatarController.SetLoading` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:55 — `MenuBeatAvatarController.Present` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/2_Core/Replayer/Emulation/Scoring/NoteControllerEmulator.cs:19 — `NoteControllerEmulator.Setup` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:68 — `ReplayPauseController.Pause` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:81 — `ReplayPauseController.Resume` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:15 — `DummyViewController.Init` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:216 — `LevelSelectionViewController.Dismiss` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:35 — `ReplayManagerViewController.NavigateToReplay` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:31 — `HeckNavigationController.NavigateToReplayAsync` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:170 — `HeckNavigationController.NavigateToReplayManager` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:174 — `HeckNavigationController.NavigateToBattleRoyale` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:35 — `SmoothHoverController.AddStateListener` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:40 — `SmoothHoverController.RemoveStateListener` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • + 4 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Commented-out code · ×10
  • Commented-out code Source/2_Core/Installers/OnGameplayCoreInstaller.cs:60 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Source/3_AssetBundle/BundleLoader.cs:93 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Source/7_Utils/Interop/Interops/CustomNotesInterop.cs:53 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Source/7_Utils/UtilityClasses/GifLoader.cs:291 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Source/7_Utils/UtilityClasses/GifLoader.cs:299 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Source/7_Utils/UtilityClasses/GifLoader.cs:447 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Source/7_Utils/UtilityClasses/GifLoader.cs:452 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Source/7_Utils/UtilityClasses/GifLoader.cs:486 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Source/7_Utils/UtilityClasses/GifLoader.cs:514 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Source/Plugin.cs:68 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
D24 · Comment Value · redundant comment · ×8
  • redundant comment Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:23 — "Start/Ready button from a setup lobby scene" repeats the code it sits on: 5 of its 6 words (start, ready, button, setup, lobby) are already in `[HarmonyPatch(typeof(GameServerLobbyFlowCoordinator), nameof(GameServerLobbyFlowCoordinator.HandleLobbySetupViewControll …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:33 — "Cancel/Unready button from a setup lobby scene" repeats the code it sits on: 5 of its 6 words (cancel, unready, button, setup, lobby) are already in `[HarmonyPatch(typeof(GameServerLobbyFlowCoordinator), nameof(GameServerLobbyFlowCoordinator.HandleLobbySetupViewControll …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:63 — "'Countdown started' event" repeats the code it sits on: 3 of its 3 words (countdown, started, event) are already in `[HarmonyPatch(typeof(GameServerLobbyFlowCoordinator), nameof(GameServerLobbyFlowCoordinator.HandleLobbyGameStateControll …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:73 — "'Countdown cancelled' event" repeats the code it sits on: 3 of its 3 words (countdown, cancelled, event) are already in `[HarmonyPatch(typeof(GameServerLobbyFlowCoordinator), nameof(GameServerLobbyFlowCoordinator.HandleLobbyGameStateControll …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/2_Core/API/Methods/AddFriendRequest.cs:21 — "user/friend?playerId={playerId}" repeats the code it sits on: 4 of its 4 words (user, friend, player, id) are already in `private static string Endpoint => BLConstants.BEATLEADER_API_URL + "/user/friend?playerId={0}";`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/2_Core/API/Methods/RemoveFriendRequest.cs:20 — "user/friend?playerId={playerId}" repeats the code it sits on: 4 of its 4 words (user, friend, player, id) are already in `private static string Endpoint => BLConstants.BEATLEADER_API_URL + "/user/friend?playerId={0}";`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/8_UI/Components/Rendering/BlurPostProcessCanvasRenderer.cs:52 — "release temporary RT" repeats the code it sits on: 3 of its 3 words (release, temporary, rt) are already in `commandBuffer.ReleaseTemporaryRT(blurTempRTPropertyId);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/8_UI/FlowCoordinator/HubViews/BeatLeaderHubMainViewController.cs:135 — "waiting for the profile load" repeats the code it sits on: 3 of its 3 words (waiting, profile, load) are already in `await ProfileManager.WaitUntilProfileLoad();`. 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 · Silent fallback default in catch · ×7
  • Silent fallback default in catch Source/2_Core/Installers/OnGameplayCoreInstaller.cs:191 — `GetStandardDataSO` 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 Source/2_Core/Installers/OnGameplayCoreInstaller.cs:198 — `GetMultiDataSO` 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 Source/2_Core/Managers/DataManager/LeaderboardManager.cs:82 — `SetFakeBloomProperty` swallows every exception and sets `enableFakeBloom = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/2_Core/Managers/SteamVR/SteamVRControllerDetector.cs:45 — `GetStartTime` swallows every exception into `return DateTime.MinValue;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/8_UI/AvatarStorage.cs:68 — `TryDownload` 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 Source/8_UI/Leaderboard/Components/ScoreInfoPanel/MiniProfile.cs:79 — `SetMessage` swallows every exception and sets `MessageText = "";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:253 — `Download` swallows every exception and sets `_mapDownloaded = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
X10 · Duplicated predicate · Duplicated predicate · ×4
  • Duplicated predicate Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:192 — `_previewClip != null && _songPreviewPlayer != null` appears character-identically in 2 files — Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs, Source/8_UI/MainMenu/SpecialEvent/SpecialEventMapPanel.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 Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:118 — `p.time >= firstNoteTime && p.time <= lastNoteTime` appears character-identically in 2 files — Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs, Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.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 Source/2_Core/API/Methods/ClanPlayersRequest.cs:14 — `result.selection != null && !result.data.Any(it => ProfileManager.IsCurrentPlayer(it.Player.id))` appears character-identically in 3 files — Source/2_Core/API/Methods/ClanPlayersRequest.cs, Source/2_Core/API/Methods/ScoresOfClanRequest.cs, Source/2_Core/API/Methods/ScoresRequest.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 Source/2_Core/Managers/DataManager/ProfileManager.cs:182 — `state is not WebRequests.RequestState.Finished || instance.Result.Status != ScoreUploadStatus.Uploaded` appears character-identically in 3 files — Source/2_Core/Managers/DataManager/ProfileManager.cs, Source/2_Core/Managers/DataManager/VotingManager.cs, Source/8_UI/Leaderboard/Components/TopPanel/PlayerInfo.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.
D16 · Bus Factor · Off-boarding risk · ×2
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 13 significant file(s) lose their only recent owner: Source/8_UI/Replayer/Components/Toolbar/Timeline.cs, Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/OpponentsView/BattleRoyaleOpponentsList.cs, Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/ReplayDetail/TagsStrip.cs, Source/8_UI/Replayer/Components/Settings/Views/AvatarView/BasicAvatarSettingsView.cs, Source/8_UI/Replayer/Components/Settings/ReplayerSettingsPanel.cs, Source/8_UI/Replayer/Components/PlayerList/PlayerList.cs, Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/BeatmapReplayLaunchPanel/BasicReplayDetailPanel.cs, Source/2_Core/Models/API/BeatLeader/Player.cs (+5 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 9 significant file(s) lose their only recent owner: Source/7_Utils/FileManager.cs, REDACTED, Source/2_Core/Managers/SteamVR/SteamVRWebConsoleSession.cs, Source/2_Core/Managers/SteamVR/SteamVRControllerDetector.cs, Source/2_Core/Managers/DataManager/PrestigeLevelsManager.cs, Source/2_Core/Managers/ReplayEnhancer/TrackingDeviceEnhancer.cs, Source/2_Core/Replayer/Emulation/ReplayHeightsProcessor.cs, Source/2_Core/Replayer/Camera/Views/PlayerViewCameraView.cs (+1 more). Pair on, review, or document these before any departure.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×2
  • Silent fallback default on parse failure Source/2_Core/Replayer/ReplayerMenuLoader.cs:341 — `LoadBeatmapAsync` returns `default` when `Enum.TryParse(difficulty, out BeatmapDifficulty cdifficulty)` 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 Source/7_Utils/Interop/InteropLoader.cs:46 — `IsVersionCorrect` returns `false` when `Version.TryParse(specifiedVersion, out var specPlugVer)` 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.
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 37 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: Source/7_Utils/Interop/Interops/BetterSongListInterop.cs, Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs, Source/8_UI/Leaderboard/Components/ScoreInfoPanel/MiniProfileButtons.cs, Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoreRow.cs, Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoresTable.cs, Source/8_UI/Leaderboard/Components/ClanScoreDetails/ClanScorePanel.cs, Source/8_UI/Leaderboard/Components/MainPanel/BeatLeaderInfo.cs, Source/8_UI/Abstract/ReeModalSystem.cs (and 29 more) (39 orphaned of 256 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 256 of the 618 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M1 · Documentation (README) · Thin README · ×1
  • Thin README README.md:1 — The root README is 116 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:7 — 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 1 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 REDACTED:365 — `REDACTED` 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`.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate REDACTED:44 — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
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.)
S1 · Web-Security Posture · No security response headers detected · ×1
  • 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.)
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×1
  • 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.)
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 41/89 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 · Null-forgiving operator (`!`) suppressions override nullable warnings · ×1
  • Null-forgiving operator (`!`) suppressions override nullable warnings — ~4.7 `!` suppressions per 1k syntax nodes — 1000 suppression(s) across the 212494 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.
Minor — 4 finding(s)
D12 · Dependency Hygiene · Outdated · ×3
  • Outdated: BepInEx.AssemblyPublicizer.MSBuild — BepInEx.AssemblyPublicizer.MSBuild 0.4.2 → 0.4.3 available (referenced by BeatLeader).
  • Outdated: Meziantou.Analyzer — Meziantou.Analyzer 2.0.264 → 3.0.341 available (referenced by BeatLeader).
  • Outdated: PolySharp — PolySharp 1.15.0 → 1.17.1 available (referenced by BeatLeader).
D24 · Comment Value · doc comments repeat the names · ×1
  • doc comments repeat the names Source/2_Core/Models/Replayer/Players/IVirtualPlayerBodySpawner.cs:17 — 1 of 22 documented parameters and 5 of 56 summaries in `BeatLeader` only repeat the member or parameter name (e.g. "Despawns the specified body." for `DespawnBody`). Delete the restating tags, or add what the name does not say.

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-f8bca6ade0d446c5a3672b9f07ec3770/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=800" --report-format json --report-path /tmp/watchdog-gitleaks-f8bca6ade0d446c5a3672b9f07ec3770/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=868" --report-format json --report-path /tmp/watchdog-gitleaks-f8bca6ade0d446c5a3672b9f07ec3770/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.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-f8bca6ade0d446c5a3672b9f07ec3770/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 .29artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list BeatLeader.sln package --vulnerable --include-transitive --format json1artifacts/raw/dotnet-vulnerable.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.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 Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-66419ece7a9041d993ac0872cd1f52e30artifacts/raw/osv-scanner.json

Run 01a1eba2-aa0c-7932-8350-207d5e82c633 · 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