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

JamesnetGroup/leagueoflegends-wpf

Measured 16 November 2026, 17:37 UTC, at code version f1610d6

First survey, so nothing to compare with yet Code coverage: not measuredBus factor: not measured

Code coverage is not measured: Tests deferred to the consumer.

Bus factor is not measured: No living knowledge left to concentrate.

CAI score 60.2out of 100 Strong
CriticalWeakAdequateStrongExemplary

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 small codebase: 13,999 lines of product code in 54 projects, tests not counted · Estimated rebuild effort: under 0.1 person-years · Weakest lens: Maturity, 52.6

Findings by how serious they are

5 critical 182 serious 155 minor

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

This survey was produced by

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

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

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

42of 42 dimensions measured by tools.
337of 342 findings point to an exact file and line, so you can open each one in the code. The other 5 concern the repository as a whole, such as missing documentation.
42dimensions across 5 lenses, read from 13,999 lines of product code in 54 projects.
Chapters

Executive summary

JamesnetGroup/leagueoflegends-wpf meets our standard for a template or a sample. It scores 60.2 out of 100 and is rated Strong, and two of its five critical findings are leaked passwords or keys.

Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is having someone learn and document the 29 files no active contributor knows, worth about 8.2 points. Fixing the 92 comments that repeat the code, or contradict it comes next, worth about 7.9 points.

Two passwords or keys are open to anyone who can read the repository. Replacing each exposed password or key would close this risk. The two data fields that are written but never read need removing.

The product code is 13,999 lines, about €11,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.
Maturity 52.6 · counts for 47%Code Health 60.3 · counts for 26%Security and Compliance 66.7 · counts for 14%Architecture 71.2 · counts for 8%Production Readiness 100.0 · counts for 4%

Every lens already scores high enough to be rated Strong, so no single lens holds the score back.

Code composition: what the lines of code are Most of the hand-written code is supporting code, such as wiring, settings and declarations, and business logic is 7% of it. That is normal for a service that mainly connects other systems or stores and fetches records, and worth a look if this product is meant to hold complex business rules.
Business logic 7%Supporting code 93%
Rebuild cost: about €11,000 · Estimate
Cost to rebuild€3,700 to €18,000, for 61 to 185 hours of work, under 0.1 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.8 at a score of 60. 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.
SizeSmall: 13,999 lines of product code, of which 59% is declarations and boilerplate, 34% straight logic and 7% logic with branches
Comment linesThe estimate prices 13,627 lines. Comment lines count towards the size of 13,999 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
Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with Container.cs (2), ChampionsViewModel.cs (2), MenuContentViewModel.cs.
Raises the score by about 8.2 points · Medium effort · Knowledge Freshness
2
Resolve the 92 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (92).
Raises the score by about 7.9 points · Medium effort · Comment Value
3
Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with WPFLayer.cs.
Raises the score by about 3.0 points · Low effort · Explicit Debt

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €11,000 to build again, under 0.1 person-years of work. Its weakest lens is Maturity, at 52.6 (Adequate). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 29 Orphaned file finding(s) in Knowledge Freshness. Of all the actions in this report, it raises the score most for the work it takes: about 8.2 points for medium effort, because it clears the 29 Knowledge Freshness findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch Leagueoflegends (_backup/obsolate/Leagueoflegends) Leagueoflegends) Lol.Foundation Foundation Leagueoflegends (_backup/obsolate/Leagueoflegends)->Lol.Foundation Lol.Main Main Leagueoflegends (_backup/obsolate/Leagueoflegends)->Lol.Main Lol.Resources Resources Leagueoflegends (_backup/obsolate/Leagueoflegends)->Lol.Resources Leagueoflegends (src/Leagueoflegends) Leagueoflegends) Leagueoflegends.Support Support Lol.Clash Clash Lol.Database Database Lol.Clash->Lol.Database Lol.Clash->Lol.Resources Lol.Collection Collection Lol.Data Data Lol.Collection->Lol.Data Lol.Collection->Lol.Database Lol.Support Support Lol.Collection->Lol.Support Lol.Devices Devices Lol.Devices->Lol.Data Lol.Foundation->Lol.Data Lol.Friends Friends Lol.Friends->Lol.Database Lol.Friends->Lol.Support Lol.GameRoom GameRoom Lol.GameRoom->Lol.Database Lol.GameRoom->Lol.Support Lol.Main->Lol.Clash Lol.Main->Lol.Collection Lol.Main->Lol.Data Lol.Main->Lol.Foundation Lol.Main->Lol.Friends Lol.Main->Lol.GameRoom Lol.Settings Settings Lol.Main->Lol.Settings Lol.Store Store Lol.Main->Lol.Store Lol.Main->Lol.Support Lol.TeamFight TeamFight Lol.Main->Lol.TeamFight Lol.Settings->Lol.Database Lol.Settings.Client Client Lol.Settings->Lol.Settings.Client Lol.Settings.InGame InGame Lol.Settings->Lol.Settings.InGame Lol.Settings->Lol.Support Lol.Settings.Client->Lol.Database Lol.Settings.Client->Lol.Devices Lol.Settings.Client->Lol.Foundation Lol.Settings.InGame->Lol.Data Lol.Settings.InGame->Lol.Database Lol.Settings.InGame->Lol.Foundation Lol.Store->Lol.Data Lol.Store->Lol.Database Lol.TeamFight->Lol.Data Lol.TeamFight->Lol.Database Lol.TeamFight->Lol.Foundation PreviewDesign PreviewDesign PreviewDesign->Lol.Clash PreviewDesign->Lol.Collection PreviewDesign->Lol.Data PreviewDesign->Lol.Database PreviewDesign->Lol.Devices PreviewDesign->Lol.Foundation PreviewDesign->Lol.Friends PreviewDesign->Lol.GameRoom PreviewDesign->Lol.Main PreviewDesign->Lol.Resources PreviewDesign->Lol.Settings PreviewDesign->Lol.Settings.Client PreviewDesign->Lol.Settings.InGame PreviewDesign->Lol.Store PreviewDesign->Lol.TeamFight __more__ +34 more projects

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.

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

The table shows the 40 modules with the most connections; 79 more are left out to keep it readable.

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 Jamesnet.Foundation2 Lol.Data.Codes3 Lol.Data.Setting.Clients4 Lol.Data.Setting.InGame5 Lol.Data.Store6 Lol.Database.Entites.Schema7 Lol.Support.Local.Models8 Leagueoflegends.Support.Local.Models9 Lol.Data.Setting10 Lol.Database.Collection11 Lol.Database.Entites.Statics12 Lol.Friends.Local.Collection13 Lol.Settings.Client.Local.ViewModels14 Lol.Support.Local.Helpers15 Leagueoflegends.Support.Local.Datas16 Leagueoflegends.Support.Local.Services17 Lol.Collection.Local.ViewModel18 Lol.Data.Config19 Lol.Database.Entites.Core20 Lol.Friends.Local.ViewModel21 Lol.GameRoom.Local.ViewModels22 Lol.Main.Local.ViewModels23 Lol.Menus.Local.ViewModels24 Leagueoflegends.Clash.Local.Datas25 Leagueoflegends.Clash.Local.ViewModels26 Leagueoflegends.Collection.Local.Datas27 Leagueoflegends.Collection.Local.ViewModels28 Leagueoflegends.Main.Local.ViewModels29 Leagueoflegends.Navigate.Local.Datas30 Leagueoflegends.Navigate.Local.Services31 Leagueoflegends.Navigate.Local.ViewModels32 Leagueoflegends.Profile.Local.Datas33 Leagueoflegends.Profile.Local.ViewModels34 Leagueoflegends.Social.Local.Datas35 Leagueoflegends.Social.Local.ViewModels36 Leagueoflegends.Store.Local.Datas37 Leagueoflegends.Tft.Local.Datas38 Leagueoflegends.Tft.Local.ViewModels39 Lol.Database.Controller40 Lol.Foundation.Riotbase
1 Jamesnet.Foundation
2 Lol.Data.Codes
3 Lol.Data.Setting.Clients
4 Lol.Data.Setting.InGame
5 Lol.Data.Store
6 Lol.Database.Entites.Schema
7 Lol.Support.Local.Models
8 Leagueoflegends.Support.Local.Models2
9 Lol.Data.Setting54
10 Lol.Database.Collection2
11 Lol.Database.Entites.Statics39
12 Lol.Friends.Local.Collection1
13 Lol.Settings.Client.Local.ViewModels152
14 Lol.Support.Local.Helpers4
15 Leagueoflegends.Support.Local.Datas13
16 Leagueoflegends.Support.Local.Services2
17 Lol.Collection.Local.ViewModel81
18 Lol.Data.Config1
19 Lol.Database.Entites.Core1
20 Lol.Friends.Local.ViewModel11
21 Lol.GameRoom.Local.ViewModels77
22 Lol.Main.Local.ViewModels212
23 Lol.Menus.Local.ViewModels31
24 Leagueoflegends.Clash.Local.Datas211
25 Leagueoflegends.Clash.Local.ViewModels1211
26 Leagueoflegends.Collection.Local.Datas844
27 Leagueoflegends.Collection.Local.ViewModels899
28 Leagueoflegends.Main.Local.ViewModels32
29 Leagueoflegends.Navigate.Local.Datas422
30 Leagueoflegends.Navigate.Local.Services4222
31 Leagueoflegends.Navigate.Local.ViewModels312
32 Leagueoflegends.Profile.Local.Datas633
33 Leagueoflegends.Profile.Local.ViewModels133
34 Leagueoflegends.Social.Local.Datas221
35 Leagueoflegends.Social.Local.ViewModels111
36 Leagueoflegends.Store.Local.Datas211
37 Leagueoflegends.Tft.Local.Datas211
38 Leagueoflegends.Tft.Local.ViewModels111
39 Lol.Database.Controller3415
40 Lol.Foundation.Riotbase11
Uses a module listed above itPart of a loopThe module itself
1 Jamesnet.Foundation2 Lol.Data.Codes3 Lol.Data.Setting.Clients4 Lol.Data.Setting.InGame5 Lol.Data.Store6 Lol.Database.Entites.Schema7 Lol.Support.Local.Models8 Leagueoflegends.Support.Local.Models9 Lol.Data.Setting10 Lol.Database.Collection11 Lol.Database.Entites.Statics12 Lol.Friends.Local.Collection13 Lol.Settings.Client.Local.ViewModels14 Lol.Support.Local.Helpers15 Leagueoflegends.Support.Local.Datas16 Leagueoflegends.Support.Local.Services17 Lol.Collection.Local.ViewModel18 Lol.Data.Config19 Lol.Database.Entites.Core20 Lol.Friends.Local.ViewModel21 Lol.GameRoom.Local.ViewModels22 Lol.Main.Local.ViewModels23 Lol.Menus.Local.ViewModels24 Leagueoflegends.Clash.Local.Datas25 Leagueoflegends.Clash.Local.ViewModels26 Leagueoflegends.Collection.Local.Datas27 Leagueoflegends.Collection.Local.ViewModels28 Leagueoflegends.Main.Local.ViewModels29 Leagueoflegends.Navigate.Local.Datas30 Leagueoflegends.Navigate.Local.Services31 Leagueoflegends.Navigate.Local.ViewModels32 Leagueoflegends.Profile.Local.Datas33 Leagueoflegends.Profile.Local.ViewModels34 Leagueoflegends.Social.Local.Datas35 Leagueoflegends.Social.Local.ViewModels36 Leagueoflegends.Store.Local.Datas37 Leagueoflegends.Tft.Local.Datas38 Leagueoflegends.Tft.Local.ViewModels39 Lol.Database.Controller40 Lol.Foundation.RiotbaseJamesnet.Foundation1Lol.Data.Codes2Lol.Data.Setting.Clients3Lol.Data.Setting.InGame4Lol.Data.Store5Lol.Database.Entites.Schema6Lol.Support.Local.Models7Leagueoflegends.Support.Local.Models8Lol.Data.Setting9Lol.Database.Collection10Lol.Database.Entites.Statics11Lol.Friends.Local.Collection12Lol.Settings.Client.Local.ViewModels13Lol.Support.Local.Helpers14Leagueoflegends.Support.Local.Datas15Leagueoflegends.Support.Local.Services16Lol.Collection.Local.ViewModel17Lol.Data.Config18Lol.Database.Entites.Core19Lol.Friends.Local.ViewModel20Lol.GameRoom.Local.ViewModels21Lol.Main.Local.ViewModels22Lol.Menus.Local.ViewModels23Leagueoflegends.Clash.Local.Datas24Leagueoflegends.Clash.Local.ViewModels25Leagueoflegends.Collection.Local.Datas26Leagueoflegends.Collection.Local.ViewModels27Leagueoflegends.Main.Local.ViewModels28Leagueoflegends.Navigate.Local.Datas29Leagueoflegends.Navigate.Local.Services30Leagueoflegends.Navigate.Local.ViewModels31Leagueoflegends.Profile.Local.Datas32Leagueoflegends.Profile.Local.ViewModels33Leagueoflegends.Social.Local.Datas34Leagueoflegends.Social.Local.ViewModels35Leagueoflegends.Store.Local.Datas36Leagueoflegends.Tft.Local.Datas37Leagueoflegends.Tft.Local.ViewModels38Lol.Database.Controller39Lol.Foundation.Riotbase402542391152413281111177212312111211844899324224222312633133221111211211111341511+79 more modules (most-connected shown)

At a glance — Code Health · 60.3 · Adequate · gated by X5 ·

At a glance — Architecture · 71.2 · Adequate · gated by AX2 ·

At a glance — Maturity · 52.6 · Adequate · gated by D34, M2 ·

At a glance — Readiness · 100.0 · Exemplary ·

At a glance — Security · 66.7 · Adequate · gated by D44 ·

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
A07:2025 — Authentication Failures3High / Critical

Roadmap

Top priorities: Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with Container.cs (2), ChampionsViewModel.cs (2), MenuContentViewModel.cs; Resolve the 92 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (92); Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

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

Do thisHelpsEffortDimension
Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with Container.cs (2), ChampionsViewModel.cs (2), MenuContentViewModel.cs.+8.2 ptsMediumKnowledge Freshness
Resolve the 92 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (92).+7.9 ptsMediumComment Value
Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with WPFLayer.cs.+3.0 ptsLowExplicit Debt
Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RiotHorizontalProgress.cs, RiotVerticalProgress.cs.+3.0 ptsLowExplicit Debt
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.+6.0 ptsMediumArchitecture documentation
Resolve the 4 Shell project finding(s) in Solution Shape — start with Lol.Converter.csproj, Lol.DBEntity.csproj, Lol.ExampleData.csproj.+1.6 ptsLowSolution Shape
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.+2.5 ptsMediumNullable reference types
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.+2.4 ptsMediumDocumentation (README)

File quality

Per-file score 0–10 — a quality signature. Of 114 files carrying findings, judged against the Template bar: 0% slop · 0% mixed · 100% near-clean.

FileScoreBandWorst signal
src/Leagueoflegends.Support/UI/Units/RiotHorizontalProgress.cs6.1Near-cleanExplicit Debt: WriteOnlyPrivateField
_backup/obsolate/Lol.Main/Lol.Main.csproj6.4Near-cleanPlatform End-of-Life: End-of-life runtime: .NET net7.0
_backup/obsolate/Lol.Home/Lol.Home.csproj6.4Near-cleanPlatform End-of-Life: End-of-life runtime: .NET net7.0
_backup/obsolate/Lol.MyShop/Lol.MyShop.csproj6.4Near-cleanPlatform End-of-Life: End-of-life runtime: .NET net7.0
_backup/obsolate/Lol.Settings.About/Lol.Settings.About.csproj6.4Near-cleanPlatform End-of-Life: End-of-life runtime: .NET net7.0
_backup/obsolate/Lol.Support/Lol.Support.csproj6.4Near-cleanPlatform End-of-Life: End-of-life runtime: .NET net7.0
_backup/obsolate/Lol.Database/Lol.Database.csproj6.4Near-cleanPlatform End-of-Life: End-of-life runtime: .NET net7.0
_backup/obsolate/Lol.Data/Lol.Data.csproj6.4Near-cleanPlatform End-of-Life: End-of-life runtime: .NET net7.0
_backup/obsolate/Lol.Foundation/Lol.Foundation.csproj6.4Near-cleanPlatform End-of-Life: End-of-life runtime: .NET net7.0
_backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs6.9Near-cleanExplicit Debt: TodoComment
src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs7.1Near-cleanCode Duplication: Edited copy of a member (8 corresponding lines)
src/Jamesnet.Core/AppBootstrapper.cs7.2Near-cleanCode Duplication: Edited copy of a member (6 corresponding lines)
src/Jamesnet.Core/Container.cs7.2Near-cleanCode Duplication: Edited copy of a member (4 corresponding lines)
REDACTED7.2Near-cleanSecrets (history): High secret: REDACTED
REDACTED7.2Near-cleanSecrets (history): High secret: REDACTED
_backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs7.3Near-cleanExplicit Debt: CommentedOutCode
_backup/obsolate/Lol.Database/Controller/StoreApi.cs7.3Near-cleanExplicit Debt: TodoComment
src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs7.4Near-cleanCode Duplication: Members sharing a duplicated core (6 members, 50+ identical tokens)
_backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.cs7.4Near-cleanCode Duplication: Edited copies of one member (4 members, 14+ corresponding lines)
src/Jamesnet.Core/DefaultViewModelInitializer.cs7.4Near-cleanCode Duplication: Edited copy of a member (11 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 — 5

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

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

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

Could not be resolved — 8

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 42 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

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

What we checked — 42 dimensions across the health lenses
D1D2D3D4D5D6D13D14D15D17D18D19D24D26D27D28D29D34D35D43D44AX10AX2AX3AX4AX5AX6GD1IC1M1M2M3M4X12X13X16X18X20X27X29X3X5

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, 337 of 342 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 01a1e56f-aa82-7957-bd45-b399a7b5993e.

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.

  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: /usr/share/dotnet/sdk/10.0.400/NuGet.targets(521,5): error MSB3202: The project file "_backup/obsolate/DevNcore.LayoutSupport.Leagueoflegends/DevNcore.LayoutSupport.Leagueoflegends.csproj" was not found. [/tmp/codehealth-iso-28c864ef87d24d508c4f51….
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 30 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 30 of the 619 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
  • D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Project file not found: '_backup/obsolate/DevNcore.LayoutSupport.Leagueoflegends/DevNcore.LayoutSupport.Leagueoflegends.csproj'.
  • D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
  • D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A scan loads every live solution in the repository into one workspace. Every score, lens, and finding here reflects the projects of `_backup/obsolate/Leagueoflegends.sln`, `src/leagueoflegends.WPF.sln`; 1 further solution(s) found in this tree (`src/Leagueoflegends.Wpf/Leagueoflegends.Wpf.sln`) could not be added to it — their project list could not be read, or none of their projects opened — so their code is not represented in the headline. (This is a count of the solutions discovery found and could not show to be covered by the analyzed ones — not a claim about how many solution files the repository contains.) If one of them is an archived or vendored tree, declaring it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — excludes it from discovery the same way generated code is. You can widen what we reach: if one of these solutions is live code, check that it opens on its own (`dotnet build <solution>`); if it is archived or vendored, declare it so.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
  • AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: a native UI project (src/Leagueoflegends.Tft/Themes/Generic.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
  • 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.
  • SC1 Supply-chain hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 7 further occurrence(s) are not listed individually; the score already reflects all 47.

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.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • 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").
  • 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.

Dimensions

D1 · Cyclomatic Complexity10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 1 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 SettingViewModel.SettingMenuChanged at 16 — 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: _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs (SettingViewModel.SettingMenuChanged 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.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

D2 · Cognitive Complexity10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cognitive complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d2_recommendation.md.

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

1 god class(es) detected.

ClassTooLong: LolDataPack_backup/obsolate/Lol.Database/Entites/Statics/LolDataPack.cs

What to do

  1. Resolve the 1 ClassTooLong finding(s) in God Classes — start with LolDataPack.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D4 · Code Duplication7.8 / 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 7.8 / 10 · rule-coverage 100% · ceiling Verified

27 duplicated block group(s) detected. 5.5 % of the production lines (771 of 13,999) are in a reported copy. A further 20 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (6 lines × 2) · ×5_backup/obsolate/Lol.Database/Entites/Schema/History.cs:23
Edited copy of a member (7 corresponding lines) · ×4src/Jamesnet.Core/StringExtensions.cs:8
Edited copy of a member (8 corresponding lines) · ×3src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:86
Duplicated block (13 lines × 2) · ×3src/Jamesnet.Core/Container.cs:83
Duplicated block (7 lines × 2) · ×3_backup/obsolate/Lol.Database/Entites/Schema/TeamFights.cs:5

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

What to do

  1. Resolve the 5 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with History.cs, FriendsApi.cs, MenuManager.cs. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 4 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with StringExtensions.cs, MenuManager.cs, AppBootstrapper.cs. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 3 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with MenuManager.cs (2), YamlConverter.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 · Coupling8.6 / 10Strong✓ 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 8.6 / 10 · rule-coverage 100% · ceiling Prevented

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

Off the main sequence: Lol.Home · ×8_backup/obsolate/Lol.Home/Lol.Home.csproj:1
Unstable project Lol.Main_backup/obsolate/Lol.Main/Lol.Main.csproj:1

What to do

  1. Resolve the 8 Off the main sequence finding(s) in Coupling — start with Lol.Home.csproj, Lol.MyShop.csproj, Lol.Settings.About.csproj. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 1 Unstable project Lol.Main finding(s) in Coupling — start with Lol.Main.csproj. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.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 49 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.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 369 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 11 direct `PackageReference`(s), and 157 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.

D17 · Explicit Debt9.3 / 10Adequategated by 3 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 9.3 / 10 · rule-coverage 100% · ceiling Prevented

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

WriteOnlyPrivateField · ×2src/Leagueoflegends.Support/UI/Units/RiotHorizontalProgress.cs:25
EmptyCatchBlocksrc/Jamesnet.Platform.WPF/WPFLayer.cs:39
TodoComment · ×15_backup/obsolate/Lol.Clash/UI/Units/PositionButton.cs:22
CommentedOutCode · ×3_backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:74

What to do

  1. Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RiotHorizontalProgress.cs, RiotVerticalProgress.cs. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with WPFLayer.cs. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 15 TodoComment finding(s) in Explicit Debt — start with StoreApi.cs (2), PositionButton.cs, ItemViewModel.cs. — One of this dimension's main actionable groups (15 warning-level).

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

D18 · Solution Shape4.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 4.0 / 10 · rule-coverage 100% · ceiling Documented

54 projects, 754 source files, 13999 hand-written lines of code (13999 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), 106 inter-project edges (build status unknown — did not finish). Measured across 2 solutions loaded as one workspace: `_backup/obsolate/Leagueoflegends.sln`, `src/leagueoflegends.WPF.sln`.

Solution references a project that does not exist · ×2_backup/obsolate/Leagueoflegends.sln
Shell project: Lol.Converter · ×4_backup/obsolate/Lol.Converter/Lol.Converter.csproj
Thin analysable surface across projects: Lol - Backup.Devices · ×2_backup/obsolate/Lol.Devices/Lol - Backup.Devices.csproj

What to do

  1. Resolve the 4 Shell project finding(s) in Solution Shape — start with Lol.Converter.csproj, Lol.DBEntity.csproj, Lol.ExampleData.csproj. — One of this dimension's main actionable groups (4 recommendation-level).
  2. Resolve the 2 Solution references a project that does not exist finding(s) in Solution Shape — start with Leagueoflegends.sln, leagueoflegends.WPF.sln. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Thin analysable surface across projects finding(s) in Solution Shape — start with Lol - Backup.Devices.csproj, PreviewDesign.csproj. — One of this dimension's main actionable groups (2 recommendation-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D24 · Comment Value0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 86% · ceiling Documented

92 of 94 judged comments only repeat the code they sit on (97.9 %). 17 comment(s) in another language or script were not judged.

redundant comment · ×92_backup/obsolate/Leagueoflegends/Properties/AssemblyInfo.cs:4

What to do

  1. Resolve the 92 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (92). — One of this dimension's main actionable groups (92 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

0 of 54 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)8.0 / 10Adequategated by 2 critical findings✓ Tool-verified

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

2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

semgrep found no security issues. semgrep hit a parse error in 48 file(s) — `_backup/obsolate/Lol.Database/Datas/Items.yml`, `_backup/obsolate/Lol.Database/Datas/Runes.yml`, `_backup/obsolate/Lol.Database/Datas/activities.yml`, `_backup/obsolate/Lol.Database/Datas/champFilter.yml`, `_backup/obsolate/Lol.Database/Datas/champTreeItem.yml`, … (+43 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

D34 · Knowledge Freshness0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

30 of 30 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is _backup/obsolate/Lol.Database/Entites/Statics/LolDataPack.cs. Counted over 30 of the 619 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×29_backup/obsolate/Lol.Menus/Local/ViewModels/MenuContentViewModel.cs:1
Dormant codebase
Most significant orphaned file_backup/obsolate/Lol.Database/Entites/Statics/LolDataPack.cs:1

What to do

  1. Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with Container.cs (2), ChampionsViewModel.cs (2), MenuContentViewModel.cs. — One of this dimension's main actionable groups (29 recommendation-level).
  2. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with LolDataPack.cs. — 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 Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

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-Life2.0 / 10Critical✓ 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 2.0 / 10 · rule-coverage 100% · ceiling Documented

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

End-of-life runtime: .NET net6.0 · ×38_backup/obsolate/Lol.Controls/Lol.Controls.csproj:4

What to do

  1. Resolve the 38 End-of-life runtime finding(s) in Platform End-of-Life — start with Lol.Controls.csproj, Lol.Converter.csproj, Lol.DBEntity.csproj. — One of this dimension's main actionable groups (38 warning-level).

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

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.7 / 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.

  • `ContainerProvider` 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 11). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. (×2) — src/Jamesnet.Core/ContainerProvider.cs:5, src/Jamesnet.Foundation/ContainerProvider.cs:5

What to do

  • 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.

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 & structure10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

GD1 · Unfinished & placeholder code9.8 / 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. (×21) — src/Leagueoflegends.Support/Local/Converters/BooleanToInverseConverter.cs:17, src/Leagueoflegends.Support/Local/Converters/BooleanToVisibilityConverter.cs:13, src/Leagueoflegends.Support/Local/Converters/BoolToPlayStopConverter.cs:13, …

What to do

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

  • `FilterChanged` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — _backup/obsolate/Lol.Collection/Local/ViewModel/ChampionsViewModel.cs:131
  • `Test1` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:70
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×17) — _backup/obsolate/Lol.Collection/Local/ViewModel/ChampionsViewModel.cs:137, _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:72, _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:84, …
  • `Loaded` has an empty body — confirm it's an intentional no-op and not an unfinished method. — src/Leagueoflegends.Social/Local/ViewModels/SocialContentViewModel.cs:23

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)6.7 / 10Strong✓ Tool-verified

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

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

What to do

  • 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 documentation2.0 / 10Weak✓ Tool-verified

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

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

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

What to do

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

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

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

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

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

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

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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 correctness2.7 / 10Weak✓ 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.

  • `folderBrowser` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 43). Every use of it in `ChangePath` 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 folderBrowser = …;`), which releases it at the end of the scope on every path including a throw. — _backup/obsolate/Lol.Settings.InGame/Local/ViewModels/ReplayViewModel.cs:43
  • `enumerator` is a `MMDeviceEnumerator`, which implements `IDisposable`, and it is created here (line 12). Every use of it in `GetDevices` 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 enumerator = …;`), which releases it at the end of the scope on every path including a throw. — _backup/obsolate/Lol.Devices/Audio/AudioDeviceInfo.cs:12

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

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.

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

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

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

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

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — src/Jamesnet.Platform.WPF/WPFLayer.cs:39

What to do

  • Swallowed exception (empty catch)
X5 · Nullable reference types3.9 / 10Weak✓ 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.

  • 12/52 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

What to do

  • 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 Health60.3Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture71.2Adequate — gated by AX2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity52.6Adequate — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness100.0ExemplaryStrongest area.
Security66.7Adequate — gated by D44Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 2 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 — 40 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.
Not evidenced — 6 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 66 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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — This is a dotnet-new template — at-rest encryption and key-vaulting are deferred to the application you build from it. Add ASP.NET Data Protection / column encryption + a key vault for your real data store when you productionise.
  • C2 Access Controls — This is a dotnet-new template — authorization is deferred to the application you build from it. Add [Authorize]/policies (or imperative guards) when you wire up real users; until then there are no real endpoints to protect.
  • D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
  • D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
  • D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
  • D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 3 candidate(s) found and not reported.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — small single-context codebase (13,999 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — no ADRs to check
  • D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — This repo declares itself a template / kata / sample; tests are deferred to the application built from it, so coverage is not scored here.
  • 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
  • P1 CI/CD gates — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. Automated CI/CD gates are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
  • P12 CI test-gate honesty — no CI workflow found
  • P2 Observability — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. Structured logging, tracing/metrics and health checks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
  • P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • X1 Async correctness — 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
  • X2 Cancellation propagation — no async method does work a token could cancel
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 5 finding(s)
D17 · Explicit Debt · WriteOnlyPrivateField · ×2
  • WriteOnlyPrivateField src/Leagueoflegends.Support/UI/Units/RiotHorizontalProgress.cs:25 — private Rectangle _backgroundRect — 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 src/Leagueoflegends.Support/UI/Units/RiotVerticalProgress.cs:18 — private Rectangle _backgroundRect — 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.
D28 · Secrets (history) · High secret · ×2
  • REDACTED
  • REDACTED
D17 · Explicit Debt · EmptyCatchBlock · ×1
  • EmptyCatchBlock src/Jamesnet.Platform.WPF/WPFLayer.cs:39 — 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.
Serious — 182 finding(s)
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×40
  • NuGet dependencies are not locked _backup/obsolate/Leagueoflegends/Leagueoflegends.csproj:15 — _backup/obsolate/Leagueoflegends/Leagueoflegends.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Clash/Lol - Backup.Clash.csproj:9 — _backup/obsolate/Lol.Clash/Lol - Backup.Clash.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Clash/Lol.Clash.csproj:9 — _backup/obsolate/Lol.Clash/Lol.Clash.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Collection/Lol - Backup.Collection.csproj:19 — _backup/obsolate/Lol.Collection/Lol - Backup.Collection.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Collection/Lol.Collection.csproj:19 — _backup/obsolate/Lol.Collection/Lol.Collection.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Controls/Lol.Controls.csproj:9 — _backup/obsolate/Lol.Controls/Lol.Controls.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Converter/Lol.Converter.csproj:24 — _backup/obsolate/Lol.Converter/Lol.Converter.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Data/Lol.Data.csproj:16 — _backup/obsolate/Lol.Data/Lol.Data.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Database/Lol.Database.csproj:10 — _backup/obsolate/Lol.Database/Lol.Database.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Devices/Lol - Backup.Devices.csproj:7 — _backup/obsolate/Lol.Devices/Lol - Backup.Devices.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Devices/Lol.Devices.csproj:7 — _backup/obsolate/Lol.Devices/Lol.Devices.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.ExampleData/Lol.ExampleData.csproj:9 — _backup/obsolate/Lol.ExampleData/Lol.ExampleData.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Forms/Lol.Forms.csproj:10 — _backup/obsolate/Lol.Forms/Lol.Forms.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Foundation/Lol.Foundation.csproj:20 — _backup/obsolate/Lol.Foundation/Lol.Foundation.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Friends/Lol - Backup.Friends.csproj:9 — _backup/obsolate/Lol.Friends/Lol - Backup.Friends.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Friends/Lol.Friends.csproj:9 — _backup/obsolate/Lol.Friends/Lol.Friends.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.GameRoom/Lol - Backup.GameRoom.csproj:9 — _backup/obsolate/Lol.GameRoom/Lol - Backup.GameRoom.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.GameRoom/Lol.GameRoom.csproj:9 — _backup/obsolate/Lol.GameRoom/Lol.GameRoom.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Home/Lol.Home.csproj:9 — _backup/obsolate/Lol.Home/Lol.Home.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.LayoutSupport/Lol.LayoutSupport.csproj:9 — _backup/obsolate/Lol.LayoutSupport/Lol.LayoutSupport.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Loot/Lol.Loot.csproj:10 — _backup/obsolate/Lol.Loot/Lol.Loot.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Main/Lol.Main.csproj:10 — _backup/obsolate/Lol.Main/Lol.Main.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Menus/Lol.Menus.csproj:14 — _backup/obsolate/Lol.Menus/Lol.Menus.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.MyShop/Lol.MyShop.csproj:9 — _backup/obsolate/Lol.MyShop/Lol.MyShop.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked _backup/obsolate/Lol.Profile/Lol.Profile.csproj:15 — _backup/obsolate/Lol.Profile/Lol.Profile.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • + 15 more in this group — see findings.md.
D44 · Platform End-of-Life · End-of-life runtime · ×38
  • End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.Controls/Lol.Controls.csproj:4 — _backup/obsolate/Lol.Controls/Lol.Controls.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.Converter/Lol.Converter.csproj:4 — _backup/obsolate/Lol.Converter/Lol.Converter.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.DBEntity/Lol.DBEntity.csproj:4 — _backup/obsolate/Lol.DBEntity/Lol.DBEntity.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.ExampleData/Lol.ExampleData.csproj:4 — _backup/obsolate/Lol.ExampleData/Lol.ExampleData.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.LayoutSupport/Lol.LayoutSupport.csproj:4 — _backup/obsolate/Lol.LayoutSupport/Lol.LayoutSupport.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.Resources/Lol - Backup.Resources.csproj:4 — _backup/obsolate/Lol.Resources/Lol - Backup.Resources.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.Settings/Lol - Backup.Settings.csproj:4 — _backup/obsolate/Lol.Settings/Lol - Backup.Settings.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.Store/Lol - Backup.Store.csproj:4 — _backup/obsolate/Lol.Store/Lol - Backup.Store.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net6.0 _backup/obsolate/PreviewDesign/PreviewDesign.csproj:4 — _backup/obsolate/PreviewDesign/PreviewDesign.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Leagueoflegends/Leagueoflegends.csproj:4 — _backup/obsolate/Leagueoflegends/Leagueoflegends.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Clash/Lol - Backup.Clash.csproj:4 — _backup/obsolate/Lol.Clash/Lol - Backup.Clash.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Clash/Lol.Clash.csproj:4 — _backup/obsolate/Lol.Clash/Lol.Clash.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Collection/Lol - Backup.Collection.csproj:5 — _backup/obsolate/Lol.Collection/Lol - Backup.Collection.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Collection/Lol.Collection.csproj:5 — _backup/obsolate/Lol.Collection/Lol.Collection.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Data/Lol.Data.csproj:4 — _backup/obsolate/Lol.Data/Lol.Data.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Database/Lol.Database.csproj:4 — _backup/obsolate/Lol.Database/Lol.Database.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Devices/Lol - Backup.Devices.csproj:3 — _backup/obsolate/Lol.Devices/Lol - Backup.Devices.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Devices/Lol.Devices.csproj:3 — _backup/obsolate/Lol.Devices/Lol.Devices.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Forms/Lol.Forms.csproj:4 — _backup/obsolate/Lol.Forms/Lol.Forms.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Foundation/Lol.Foundation.csproj:3 — _backup/obsolate/Lol.Foundation/Lol.Foundation.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Friends/Lol - Backup.Friends.csproj:4 — _backup/obsolate/Lol.Friends/Lol - Backup.Friends.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Friends/Lol.Friends.csproj:4 — _backup/obsolate/Lol.Friends/Lol.Friends.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.GameRoom/Lol - Backup.GameRoom.csproj:4 — _backup/obsolate/Lol.GameRoom/Lol - Backup.GameRoom.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.GameRoom/Lol.GameRoom.csproj:4 — _backup/obsolate/Lol.GameRoom/Lol.GameRoom.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Home/Lol.Home.csproj:4 — _backup/obsolate/Lol.Home/Lol.Home.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • + 13 more in this group — see findings.md.
GD1 · Unfinished & placeholder code · Unfinished stub · ×21
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/BooleanToInverseConverter.cs:17 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/BooleanToVisibilityConverter.cs:13 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/BoolToPlayStopConverter.cs:13 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/ChampionNameToThumbnailConverter.cs:19 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/ConceptToImageConverter.cs:16 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/CooldownConverter.cs:16 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/DiscountRateConverter.cs:16 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/FromNullToValueConverter.cs:17 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/IconTypeToStatusIndicatorConverter.cs:25 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/ItemNameToImageConverter.cs:52 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/MatchResultToColorConverter.cs:22 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/MenuIconToGeometryConverter.cs:26 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/NumberFormatConverter.cs:16 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/PercentToBadgeConverter.cs:18 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/ScheduleDateConverter.cs:17 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/ScheduleDayConverter.cs:16 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/SpellNameToImageConverter.cs:20 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/SummonerLevelConverter.cs:17 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/UserToThumbnailConverter.cs:12 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Clash/Local/Converters/ShowMenuConverter.cs:15 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Leagueoflegends.Settings/Local/Converters/InputModeToVisibilityConverter.cs:22 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
D17 · Explicit Debt · TodoComment · ×15
  • TodoComment _backup/obsolate/Lol.Clash/UI/Units/PositionButton.cs:22 — // TODO: [Kevin] 이 방법이 최선인가 추후 수정??? — 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 _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:69 — //TODO: [Lucas] 추후 Button Event 작업 — 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 _backup/obsolate/Lol.Collection/Local/ViewModel/SpellsViewModel.cs:35 — // TODO: [Lucas] 임시로 배경화면 변경 부분 처리 — 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 _backup/obsolate/Lol.Database/Collection/FriendsCollection.cs:5 — //TODO: [Kevin] Lol.Main.Local.Collection 에서 변경 방생성 할 때 FriendsCollection 데이터가 필요 — 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 _backup/obsolate/Lol.Database/Controller/SpellApi.cs:29 — // TODO: [James] 임시 Foreach Linq문 참고용. — 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 _backup/obsolate/Lol.Database/Controller/StoreApi.cs:7 — // TODO: [Kevin] StoreItems 데이터 병합 작업 예정 — 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 _backup/obsolate/Lol.Database/Controller/StoreApi.cs:12 — //TODO: [Kevin] Store Category merge > 조회시 임시 TypeSeq 인자 넘김 — 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 _backup/obsolate/Lol.Home/Local/ViewModels/AvatarViewModel.cs:15 — //TODO:[Lucas] — 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 _backup/obsolate/Lol.Settings.InGame/Local/ViewModels/ReplayViewModel.cs:42 — // TODO: [James] 윈폼 DLL을 사용하지 않고도 해결 방법이 있는지 확인 필요. — 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 _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:60 — // TODO : 각 컨텐츠의 모델 데이터 불러오는 기능 구현해야함 2023/09/15 — 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 src/Leagueoflegends.Support/Themes/Units/RiotChampSummary.xaml:9 — <!-- TODO: Use this brush for text when Uno Platform supports gradients on TextBlock --> — 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 _backup/obsolate/Lol.Clash/Themes/Units/CupToggleButton.xaml:57 — <!-- TODO: [Kevin] 임시작업 변경예정--> — 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 _backup/obsolate/Lol.Profile/Themes/Units/History/PlayedChampList.xaml:34 — <!-- TODO: [Kevin] 임시작업 변경예정--> — 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 _backup/obsolate/Lol.GameRoom/Themes/Units/Summoners/UserDetail.xaml:17 — <!--TODO: [Kevin] Blend Path 작업 예정--> — 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 _backup/obsolate/Lol.Profile/Themes/Units/History/RecentActivity.xaml:43 — <!-- TODO: [Kevin] 이미지 추후 교체예정 --> — 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.
D5 · Coupling · Off the main sequence · ×8
  • Off the main sequence: Lol.Home _backup/obsolate/Lol.Home/Lol.Home.csproj:1 — Lol.Home: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: Lol.MyShop _backup/obsolate/Lol.MyShop/Lol.MyShop.csproj:1 — Lol.MyShop: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: Lol.Settings.About _backup/obsolate/Lol.Settings.About/Lol.Settings.About.csproj:1 — Lol.Settings.About: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: Lol.Support _backup/obsolate/Lol.Support/Lol.Support.csproj:1 — Lol.Support: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
  • Off the main sequence: Lol.Database _backup/obsolate/Lol.Database/Lol.Database.csproj:1 — Lol.Database: abstractness 0.02, instability 0.00, distance 0.98 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
  • Off the main sequence: Lol.Data _backup/obsolate/Lol.Data/Lol.Data.csproj:1 — Lol.Data: abstractness 0.03, instability 0.00, distance 0.97 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
  • Off the main sequence: Lol.Foundation _backup/obsolate/Lol.Foundation/Lol.Foundation.csproj:1 — Lol.Foundation: abstractness 0.00, instability 0.11, distance 0.89 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
  • Off the main sequence: Leagueoflegends.Support src/Leagueoflegends.Support/Leagueoflegends.Support.csproj:1 — Leagueoflegends.Support: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 11 project(s), so it's rigid to change.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×5
  • Duplicated block (6 lines × 2) _backup/obsolate/Lol.Database/Entites/Schema/History.cs:23 — _backup/obsolate/Lol.Database/Entites/Schema/History.cs:23-28 | src/Leagueoflegends.Support/Local/Models/MatchHistory.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.
  • Duplicated block (6 lines × 2) _backup/obsolate/Lol.Database/Controller/FriendsApi.cs:12 — _backup/obsolate/Lol.Database/Controller/FriendsApi.cs:12-17 | _backup/obsolate/Lol.Database/Controller/FriendsApi.cs:37-42 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:78 — src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:78-83 | src/Leagueoflegends.Navigate/Local/Services/SubMenuNavigator.cs:54-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) src/Jamesnet.Core/AppBootstrapper.cs:11 — src/Jamesnet.Core/AppBootstrapper.cs:11-16 | src/Jamesnet.Foundation/AppBootstrapper.cs:11-16 — 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) src/Jamesnet.Core/StringExtensions.cs:9 — src/Jamesnet.Core/StringExtensions.cs:9-14 | src/Jamesnet.Foundation/StringExtensions.cs:9-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×4
  • Edited copy of a member (7 corresponding lines) src/Jamesnet.Core/StringExtensions.cs:8 — src/Jamesnet.Core/StringExtensions.cs:8-14 | src/Jamesnet.Foundation/StringExtensions.cs:8-14 — 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) src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:77 — src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:77-83 | src/Leagueoflegends.Navigate/Local/Services/SubMenuNavigator.cs:53-59 — 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) src/Jamesnet.Core/AppBootstrapper.cs:10 — src/Jamesnet.Core/AppBootstrapper.cs:10-16 | src/Jamesnet.Foundation/AppBootstrapper.cs:10-16 — 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) src/Leagueoflegends.Support/UI/Units/RiotHorizontalProgress.cs:34 — src/Leagueoflegends.Support/UI/Units/RiotHorizontalProgress.cs:34-40 | src/Leagueoflegends.Support/UI/Units/RiotVerticalProgress.cs:27-35 — 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.
D17 · Explicit Debt · CommentedOutCode · ×3
  • CommentedOutCode _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:74 — 9 consecutive commented-code lines
  • CommentedOutCode _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:62 — 9 consecutive commented-code lines
  • CommentedOutCode _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:86 — 4 consecutive commented-code lines
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×3
  • Edited copy of a member (8 corresponding lines) src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:86 — src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:86-93 | src/Leagueoflegends.Navigate/Local/Services/SubMenuNavigator.cs:43-50 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:38 — src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:38-45 | src/Leagueoflegends.Navigate/Local/Services/SubMenuNavigator.cs:33-40 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) src/Jamesnet.Core/YamlConverter.cs:23 — src/Jamesnet.Core/YamlConverter.cs:23-30 | src/Jamesnet.Foundation/YamlConverter.cs:23-30 — 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 · Duplicated block (13 lines × 2) · ×3
  • Duplicated block (13 lines × 2) src/Jamesnet.Core/Container.cs:83 — src/Jamesnet.Core/Container.cs:83-95 | src/Jamesnet.Foundation/Container.cs:83-95 — `src/Jamesnet.Core/Container.cs` and `src/Jamesnet.Foundation/Container.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 23 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (13 lines × 2) src/Jamesnet.Core/YamlItem.cs:8 — src/Jamesnet.Core/YamlItem.cs:8-20 | src/Jamesnet.Foundation/YamlItem.cs:8-20 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) src/Jamesnet.Core/YamlExtensions.cs:10 — src/Jamesnet.Core/YamlExtensions.cs:10-22 | src/Jamesnet.Foundation/YamlExtensions.cs:10-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) _backup/obsolate/Lol.Database/Entites/Schema/TeamFights.cs:5 — _backup/obsolate/Lol.Database/Entites/Schema/TeamFights.cs:5-11 | src/Leagueoflegends.Support/Local/Models/TeamFight.cs:5-11 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:87 — src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:87-93 | src/Leagueoflegends.Navigate/Local/Services/SubMenuNavigator.cs:44-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `subMenuItem` to `MenuModel` in one and `SubMenuItem` 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.
  • Duplicated block (7 lines × 2) src/Jamesnet.Core/YamlConverter.cs:24 — src/Jamesnet.Core/YamlConverter.cs:24-30 | src/Jamesnet.Foundation/YamlConverter.cs:24-30 — `src/Jamesnet.Core/YamlConverter.cs` and `src/Jamesnet.Foundation/YamlConverter.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 36 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) src/Jamesnet.Core/LayerManager.cs:6 — src/Jamesnet.Core/LayerManager.cs:6-10 | src/Jamesnet.Foundation/LayerManager.cs:7-11 — `src/Jamesnet.Core/LayerManager.cs` and `src/Jamesnet.Foundation/LayerManager.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 17 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Jamesnet.Core/LayerManager.cs:6` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) src/Jamesnet.Core/AppBootstrapper.cs:20 — src/Jamesnet.Core/AppBootstrapper.cs:20-24 | src/Jamesnet.Foundation/AppBootstrapper.cs:20-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. 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 (5 lines × 2) src/Jamesnet.Core/BaseResourceLoader.cs:16 — src/Jamesnet.Core/BaseResourceLoader.cs:16-20 | src/Jamesnet.Foundation/BaseResourceLoader.cs:16-20 — 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.
AX2 · Stateful singletons · Process-global static state · ×2
  • Process-global static state: ContainerProvider src/Jamesnet.Core/ContainerProvider.cs:5 — `ContainerProvider` 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 11). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ContainerProvider src/Jamesnet.Foundation/ContainerProvider.cs:5 — `ContainerProvider` 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 11). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
D18 · Solution Shape · Solution references a project that does not exist · ×2
  • Solution references a project that does not exist _backup/obsolate/Leagueoflegends.sln — `_backup/obsolate/Leagueoflegends.sln` declares 1 project file(s) that are missing from the tree (`_backup/obsolate/DevNcore.LayoutSupport.Leagueoflegends/DevNcore.LayoutSupport.Leagueoflegends.csproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
  • Solution references a project that does not exist src/leagueoflegends.WPF.sln — `src/leagueoflegends.WPF.sln` declares 1 project file(s) that are missing from the tree (`src/leagueoflegends/leagueoflegends.csproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) src/Jamesnet.Core/DefaultViewModelInitializer.cs:30 — src/Jamesnet.Core/DefaultViewModelInitializer.cs:30-47 | src/Jamesnet.Foundation/DefaultViewModelInitializer.cs:30-40 — 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.
  • Edited copy of a member (11 corresponding lines) _backup/obsolate/Lol.Main/Local/ViewModels/MainContentViewModel.cs:58 — _backup/obsolate/Lol.Main/Local/ViewModels/MainContentViewModel.cs:58-71 | _backup/obsolate/Lol.Forms/Local/ViewModels/RiotViewModel.cs:20-30 — 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 copy of a member (9 corresponding lines) · ×2
  • Edited copy of a member (9 corresponding lines) src/Leagueoflegends.Collection/Local/Datas/ChampStatsDataLoader.cs:15 — src/Leagueoflegends.Collection/Local/Datas/ChampStatsDataLoader.cs:15-23 | src/Leagueoflegends.Collection/Local/Datas/SkinsDataLoader.cs:15-23 — 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) src/Jamesnet.Core/ViewModelBase.cs:18 — src/Jamesnet.Core/ViewModelBase.cs:18-26 | src/Jamesnet.Foundation/ViewModelBase.cs:31-39 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×2
  • Edited copy of a member (6 corresponding lines) src/Jamesnet.Core/AppBootstrapper.cs:19 — src/Jamesnet.Core/AppBootstrapper.cs:19-24 | src/Jamesnet.Foundation/AppBootstrapper.cs:19-24 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) src/Jamesnet.Core/BaseResourceLoader.cs:15 — src/Jamesnet.Core/BaseResourceLoader.cs:15-20 | src/Jamesnet.Foundation/BaseResourceLoader.cs:15-20 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×2
  • Edited copy of a member (4 corresponding lines) src/Jamesnet.Core/Container.cs:27 — src/Jamesnet.Core/Container.cs:27-30 | src/Jamesnet.Foundation/Container.cs:27-30 — 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.
  • Edited copy of a member (4 corresponding lines) src/Jamesnet.Core/Container.cs:33 — src/Jamesnet.Core/Container.cs:33-36 | src/Jamesnet.Foundation/Container.cs:33-36 — 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 · Duplicated block (10 lines × 2) · ×2
  • Duplicated block (10 lines × 2) src/Jamesnet.Core/DefaultViewModelInitializer.cs:33 — src/Jamesnet.Core/DefaultViewModelInitializer.cs:33-42 | src/Jamesnet.Foundation/DefaultViewModelInitializer.cs:31-40 — `src/Jamesnet.Core/DefaultViewModelInitializer.cs` and `src/Jamesnet.Foundation/DefaultViewModelInitializer.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 10 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (10 lines × 2) src/Jamesnet.Core/Container.cs:65 — src/Jamesnet.Core/Container.cs:65-74 | src/Jamesnet.Foundation/Container.cs:65-74 — `src/Jamesnet.Core/Container.cs` and `src/Jamesnet.Foundation/Container.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 23 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2
  • Duplicated block (8 lines × 2) src/Jamesnet.Core/ViewModelMapper.cs:11 — src/Jamesnet.Core/ViewModelMapper.cs:11-18 | src/Jamesnet.Foundation/ViewModelMapper.cs:11-18 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) src/Jamesnet.Core/ViewModelBase.cs:19 — src/Jamesnet.Core/ViewModelBase.cs:19-26 | src/Jamesnet.Foundation/ViewModelBase.cs:32-39 — `src/Jamesnet.Core/ViewModelBase.cs` and `src/Jamesnet.Foundation/ViewModelBase.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 8 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×2
  • Duplicated block (7 lines × 4) _backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.cs:72 — _backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.cs:72-78 | _backup/obsolate/Lol.Store/Local/ViewModels/EtcViewModel.cs:95-102 | _backup/obsolate/Lol.Store/Local/ViewModels/SkinViewModel.cs:68-75 | _backup/obsolate/Lol.Store/Local/ViewModels/TFTViewModel.cs:95-102 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
  • Duplicated block (7 lines × 4) _backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.cs:72 — _backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.cs:72-78 | _backup/obsolate/Lol.Store/Local/ViewModels/EtcViewModel.cs:95-102 | _backup/obsolate/Lol.Store/Local/ViewModels/SkinViewModel.cs:68-75 | _backup/obsolate/Lol.Store/Local/ViewModels/TFTViewModel.cs:95-102 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
IC1 · Incompleteness & stubs · Empty method body · ×2
  • Empty method body — does nothing with its inputs _backup/obsolate/Lol.Collection/Local/ViewModel/ChampionsViewModel.cs:131 — `FilterChanged` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:70 — `Test1` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×2
  • Disposable created and abandoned in the method that made it _backup/obsolate/Lol.Settings.InGame/Local/ViewModels/ReplayViewModel.cs:43 — `folderBrowser` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 43). Every use of it in `ChangePath` 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 folderBrowser = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it _backup/obsolate/Lol.Devices/Audio/AudioDeviceInfo.cs:12 — `enumerator` is a `MMDeviceEnumerator`, which implements `IDisposable`, and it is created here (line 12). Every use of it in `GetDevices` 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 enumerator = …;`), which releases it at the end of the scope on every path including a throw.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: LolDataPack _backup/obsolate/Lol.Database/Entites/Statics/LolDataPack.cs — ClassTooLong — 470 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 70 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs:14 — src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs:14-30 | src/Leagueoflegends.Support/UI/Units/RiotMatchHistoryListBox.cs:16-32 | src/Leagueoflegends.Support/UI/Units/RiotScheduleListBox.cs:16-32 | src/Leagueoflegends.Support/UI/Units/RiotStageListBox.cs:15-31 | src/Leagueoflegends.Support/UI/Units/RiotStoreChampListBox.cs:15-31 | src/Leagueoflegends.Support/UI/Units/RiotTabMenu.cs:25-42 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 14+ corresponding lines) _backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.cs:103 — _backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.cs:103-116 | _backup/obsolate/Lol.Store/Local/ViewModels/EtcViewModel.cs:114-127 | _backup/obsolate/Lol.Store/Local/ViewModels/SkinViewModel.cs:89-102 | _backup/obsolate/Lol.Store/Local/ViewModels/TFTViewModel.cs:115-128 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 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 (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) src/Jamesnet.Core/LayerManager.cs:49 — src/Jamesnet.Core/LayerManager.cs:49-64 | src/Jamesnet.Foundation/LayerManager.cs:74-89 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) src/Jamesnet.Core/DefaultViewModelInitializer.cs:18 — src/Jamesnet.Core/DefaultViewModelInitializer.cs:18-27 | src/Jamesnet.Foundation/DefaultViewModelInitializer.cs:18-27 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) src/Jamesnet.Core/YamlConverter.cs:34 — src/Jamesnet.Core/YamlConverter.cs:34-62 | src/Jamesnet.Foundation/YamlConverter.cs:34-62 — `src/Jamesnet.Core/YamlConverter.cs` and `src/Jamesnet.Foundation/YamlConverter.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 36 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) _backup/obsolate/Lol.Database/Controller/ChampApi.cs:63 — _backup/obsolate/Lol.Database/Controller/ChampApi.cs:63-78 | _backup/obsolate/Lol.Database/Controller/ChampApi.cs:82-97 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (16 lines × 5) · ×1
  • Duplicated block (16 lines × 5) src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs:15 — src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs:15-30 | src/Leagueoflegends.Support/UI/Units/RiotMatchHistoryListBox.cs:17-32 | src/Leagueoflegends.Support/UI/Units/RiotScheduleListBox.cs:17-32 | src/Leagueoflegends.Support/UI/Units/RiotStageListBox.cs:16-31 | src/Leagueoflegends.Support/UI/Units/RiotStoreChampListBox.cs:16-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) src/Jamesnet.Core/IContainer.cs:5 — src/Jamesnet.Core/IContainer.cs:5-19 | src/Jamesnet.Foundation/IContainer.cs:5-19 — `src/Jamesnet.Core/IContainer.cs` and `src/Jamesnet.Foundation/IContainer.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 15 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Jamesnet.Core/IContainer.cs:5` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 6) · ×1
  • Duplicated block (13 lines × 6) src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs:15 — src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs:15-27 | src/Leagueoflegends.Support/UI/Units/RiotMatchHistoryListBox.cs:17-29 | src/Leagueoflegends.Support/UI/Units/RiotScheduleListBox.cs:17-29 | src/Leagueoflegends.Support/UI/Units/RiotStageListBox.cs:16-28 | src/Leagueoflegends.Support/UI/Units/RiotStoreChampListBox.cs:16-28 | src/Leagueoflegends.Support/UI/Units/RiotTabMenu.cs:26-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs:15` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Leagueoflegends.Support/UI/Units/RiotTabMenu.cs:39` calls `Execute` and `src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs:28` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) src/Jamesnet.Core/LayerManager.cs:14 — src/Jamesnet.Core/LayerManager.cs:14-25 | src/Jamesnet.Foundation/LayerManager.cs:15-26 — `src/Jamesnet.Core/LayerManager.cs` and `src/Jamesnet.Foundation/LayerManager.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 17 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Jamesnet.Foundation/LayerManager.cs:30` calls `WriteLine` and `src/Jamesnet.Core/LayerManager.cs:29` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (45 lines × 2) · ×1
  • Duplicated block (45 lines × 2) src/Jamesnet.Core/RelayCommand.cs:17 — src/Jamesnet.Core/RelayCommand.cs:17-61 | src/Jamesnet.Foundation/RelayCommand.cs:17-61 — `src/Jamesnet.Core/RelayCommand.cs` and `src/Jamesnet.Foundation/RelayCommand.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 45 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Jamesnet.Core/RelayCommand.cs:17` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D5 · Coupling · Unstable project Lol.Main · ×1
  • Unstable project Lol.Main _backup/obsolate/Lol.Main/Lol.Main.csproj:1 — Lol.Main has instability 0.88 with 2 dependents.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) src/Jamesnet.Platform.WPF/WPFLayer.cs:39 — 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.
Minor — 155 finding(s)
D24 · Comment Value · redundant comment · ×92
  • redundant comment _backup/obsolate/Leagueoflegends/Properties/AssemblyInfo.cs:4 — "where theme specific resource dictionaries are located" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Leagueoflegends/Properties/AssemblyInfo.cs:5 — "(used if a resource is not found in the page, or application resource dictionaries)" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Leagueoflegends/Properties/AssemblyInfo.cs:7 — "where the generic resource dictionary is located" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Leagueoflegends/Properties/AssemblyInfo.cs:8 — "(used if a resource is not found in the page, app, or any theme specific resource dictionaries)" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Clash/Properties/AssemblyInfo.cs:11 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Clash/Properties/AssemblyInfo.cs:17 — "The following GUID is for the ID of the typelib if this project is exposed to COM." is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Friends/Properties/AssemblyInfo.cs:11 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Friends/Properties/AssemblyInfo.cs:17 — "The following GUID is for the ID of the typelib if this project is exposed to COM." is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.GameRoom/Properties/AssemblyInfo.cs:4 — "where theme specific resource dictionaries are located" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.GameRoom/Properties/AssemblyInfo.cs:5 — "(used if a resource is not found in the page, or application resource dictionaries)" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.GameRoom/Properties/AssemblyInfo.cs:7 — "where the generic resource dictionary is located" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.GameRoom/Properties/AssemblyInfo.cs:8 — "(used if a resource is not found in the page, app, or any theme specific resource dictionaries)" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Home/Properties/AssemblyInfo.cs:11 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Home/Properties/AssemblyInfo.cs:17 — "The following GUID is for the ID of the typelib if this project is exposed to COM." is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.LayoutSupport/Properties/AssemblyInfo.cs:11 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.LayoutSupport/Properties/AssemblyInfo.cs:17 — "The following GUID is for the ID of the typelib if this project is exposed to COM." is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Loot/Properties/AssemblyInfo.cs:4 — "where theme specific resource dictionaries are located" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Loot/Properties/AssemblyInfo.cs:5 — "(used if a resource is not found in the page, or application resource dictionaries)" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Loot/Properties/AssemblyInfo.cs:7 — "where the generic resource dictionary is located" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Loot/Properties/AssemblyInfo.cs:8 — "(used if a resource is not found in the page, app, or any theme specific resource dictionaries)" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Main/Properties/AssemblyInfo.cs:11 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Main/Properties/AssemblyInfo.cs:17 — "The following GUID is for the ID of the typelib if this project is exposed to COM." is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Menus/Properties/AssemblyInfo.cs:4 — "where theme specific resource dictionaries are located" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Menus/Properties/AssemblyInfo.cs:5 — "(used if a resource is not found in the page, or application resource dictionaries)" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment _backup/obsolate/Lol.Menus/Properties/AssemblyInfo.cs:7 — "where the generic resource dictionary is located" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • + 67 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×29
  • Orphaned file _backup/obsolate/Lol.Menus/Local/ViewModels/MenuContentViewModel.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 src/Leagueoflegends/LeagueoflegendsBootstrapper.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 _backup/obsolate/Lol.Database/Controller/StoreApi.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 src/Jamesnet.Foundation/Container.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 _backup/obsolate/Leagueoflegends/Properties/ViewModules.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 _backup/obsolate/Lol.Support/Local/Helpers/MenuService.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 src/Jamesnet.Foundation/LayerManager.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 _backup/obsolate/Lol.Collection/Local/ViewModel/ChampionsViewModel.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 _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.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 _backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.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 _backup/obsolate/Leagueoflegends/Properties/WireDataContext.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 src/Jamesnet.Platform.WPF/RecursiveControl.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 _backup/obsolate/Lol.Store/Local/ViewModels/TFTViewModel.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 _backup/obsolate/Lol.Store/Local/ViewModels/EtcViewModel.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 _backup/obsolate/Lol.Store/Local/ViewModels/SkinViewModel.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 _backup/obsolate/Lol.Database/Controller/ChampApi.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 _backup/obsolate/Lol.GameRoom/Local/ViewModels/CreateCustomViewModel.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 src/Jamesnet.Core/Container.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 _backup/obsolate/Lol.Data/Setting/InGame/InterfaceModel.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 _backup/obsolate/Lol.Clash/Local/ViewModel/WinnersViewModel.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 _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.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 _backup/obsolate/Lol.Database/Controller/HistoryApi.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 src/Leagueoflegends.Navigate/Local/Services/MenuManager.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 _backup/obsolate/Lol.Main/Local/ViewModels/MainContentViewModel.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 src/Leagueoflegends.Collection/Local/ViewModels/ChampionsContentViewModel.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.
  • + 4 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Commented-out code · ×17
  • Commented-out code _backup/obsolate/Lol.Collection/Local/ViewModel/ChampionsViewModel.cs:137 — 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 _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:72 — 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 _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:84 — 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 _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:88 — 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 _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:91 — 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 _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.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 _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:100 — 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 _backup/obsolate/Lol.Database/Controller/SpellApi.cs:30 — 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 _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:62 — 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 _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:63 — 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 _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:64 — 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 _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:65 — 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 _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:66 — 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 _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:67 — 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 _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:68 — 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 _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:69 — 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 _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:70 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
D18 · Solution Shape · Shell project · ×4
  • Shell project: Lol.Converter _backup/obsolate/Lol.Converter/Lol.Converter.csproj — `Lol.Converter` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
  • Shell project: Lol.DBEntity _backup/obsolate/Lol.DBEntity/Lol.DBEntity.csproj — `Lol.DBEntity` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
  • Shell project: Lol.ExampleData _backup/obsolate/Lol.ExampleData/Lol.ExampleData.csproj — `Lol.ExampleData` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
  • Shell project: Lol.LayoutSupport _backup/obsolate/Lol.LayoutSupport/Lol.LayoutSupport.csproj — `Lol.LayoutSupport` contributes only 4 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
X10 · Duplicated predicate · Duplicated predicate · ×4
  • Duplicated predicate src/Jamesnet.Core/YamlConverter.cs:35 — `!string.IsNullOrWhiteSpace(line) && !line.TrimStart().StartsWith("#")` appears character-identically in 2 files — src/Jamesnet.Core/YamlConverter.cs, src/Jamesnet.Foundation/YamlConverter.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 src/Jamesnet.Core/Container.cs:88 — `!typeof(T).IsAbstract && !typeof(T).IsInterface` appears character-identically in 2 files — src/Jamesnet.Core/Container.cs, src/Jamesnet.Foundation/Container.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 src/Jamesnet.Core/RelayCommand.cs:21 — `_canExecute == null || _canExecute((T)parameter)` appears character-identically in 2 files — src/Jamesnet.Core/RelayCommand.cs, src/Jamesnet.Foundation/RelayCommand.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 src/Leagueoflegends.Support/Local/Converters/ChampionNameToThumbnailConverter.cs:12 — `value is string itemName && !string.IsNullOrEmpty(itemName)` appears character-identically in 2 files — src/Leagueoflegends.Support/Local/Converters/ChampionNameToThumbnailConverter.cs, src/Leagueoflegends.Support/Local/Converters/ItemNameToImageConverter.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.
D18 · Solution Shape · Thin analysable surface across projects · ×2
  • Thin analysable surface across projects: Lol - Backup.Devices _backup/obsolate/Lol.Devices/Lol - Backup.Devices.csproj — 2 project(s) carry only a thin slice of real code; `Lol - Backup.Devices` has 19 significant line(s). The mean analysable-surface weight is 90 %; this project lowers Solution Shape by about 0.11 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
  • Thin analysable surface across projects: PreviewDesign _backup/obsolate/PreviewDesign/PreviewDesign.csproj — 2 project(s) carry only a thin slice of real code; `PreviewDesign` has 26 significant line(s). The mean analysable-surface weight is 90 %; this project lowers Solution Shape by about 0.09 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 30 of 30 significant files have no living knowledge — the codebase as a whole is dormant, not 30 separate risks. Counted over 30 of the 619 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D34 · Knowledge Freshness · Most significant orphaned file · ×1
  • Most significant orphaned file _backup/obsolate/Lol.Database/Entites/Statics/LolDataPack.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D8 · Code Coverage · No tests · ×1
  • No tests — template/sample — This repo declares itself a template / kata / sample; tests are deferred to the application built from it, so coverage is not scored here.
IC1 · Incompleteness & stubs · Empty method body · ×1
  • Empty method body src/Leagueoflegends.Social/Local/ViewModels/SocialContentViewModel.cs:23 — `Loaded` has an empty body — confirm it's an intentional no-op and not an unfinished method.
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.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 12/52 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

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-4b3bc045fb664581b93a709c04806c4f/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-4b3bc045fb664581b93a709c04806c4f/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=420" --report-format json --report-path /tmp/watchdog-gitleaks-4b3bc045fb664581b93a709c04806c4f/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-4b3bc045fb664581b93a709c04806c4f/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 .0artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan0—
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—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.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-30db1ac04f9344538518b4666055ac840artifacts/raw/osv-scanner.json

Run 01a1e56f-aa82-7957-bd45-b399a7b5993e · 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