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.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
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 problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.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. |
| Size | Small: 13,999 lines of product code, of which 59% is declarations and boilerplate, 34% straight logic and 7% logic with branches |
| Comment lines | The estimate prices 13,627 lines. Comment lines count towards the size of 13,999 lines but aren't priced as work. |
| What it is not | Not 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. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 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.Models | 9 Lol.Data.Setting | 10 Lol.Database.Collection | 11 Lol.Database.Entites.Statics | 12 Lol.Friends.Local.Collection | 13 Lol.Settings.Client.Local.ViewModels | 14 Lol.Support.Local.Helpers | 15 Leagueoflegends.Support.Local.Datas | 16 Leagueoflegends.Support.Local.Services | 17 Lol.Collection.Local.ViewModel | 18 Lol.Data.Config | 19 Lol.Database.Entites.Core | 20 Lol.Friends.Local.ViewModel | 21 Lol.GameRoom.Local.ViewModels | 22 Lol.Main.Local.ViewModels | 23 Lol.Menus.Local.ViewModels | 24 Leagueoflegends.Clash.Local.Datas | 25 Leagueoflegends.Clash.Local.ViewModels | 26 Leagueoflegends.Collection.Local.Datas | 27 Leagueoflegends.Collection.Local.ViewModels | 28 Leagueoflegends.Main.Local.ViewModels | 29 Leagueoflegends.Navigate.Local.Datas | 30 Leagueoflegends.Navigate.Local.Services | 31 Leagueoflegends.Navigate.Local.ViewModels | 32 Leagueoflegends.Profile.Local.Datas | 33 Leagueoflegends.Profile.Local.ViewModels | 34 Leagueoflegends.Social.Local.Datas | 35 Leagueoflegends.Social.Local.ViewModels | 36 Leagueoflegends.Store.Local.Datas | 37 Leagueoflegends.Tft.Local.Datas | 38 Leagueoflegends.Tft.Local.ViewModels | 39 Lol.Database.Controller | 40 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.Models | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 Lol.Data.Setting | 5 | 4 | ||||||||||||||||||||||||||||||||||||||
| 10 Lol.Database.Collection | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 Lol.Database.Entites.Statics | 39 | |||||||||||||||||||||||||||||||||||||||
| 12 Lol.Friends.Local.Collection | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Lol.Settings.Client.Local.ViewModels | 1 | 5 | 2 | |||||||||||||||||||||||||||||||||||||
| 14 Lol.Support.Local.Helpers | 4 | |||||||||||||||||||||||||||||||||||||||
| 15 Leagueoflegends.Support.Local.Datas | 13 | |||||||||||||||||||||||||||||||||||||||
| 16 Leagueoflegends.Support.Local.Services | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 Lol.Collection.Local.ViewModel | 8 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 Lol.Data.Config | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Lol.Database.Entites.Core | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Lol.Friends.Local.ViewModel | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Lol.GameRoom.Local.ViewModels | 7 | 7 | ||||||||||||||||||||||||||||||||||||||
| 22 Lol.Main.Local.ViewModels | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 Lol.Menus.Local.ViewModels | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 Leagueoflegends.Clash.Local.Datas | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 Leagueoflegends.Clash.Local.ViewModels | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 Leagueoflegends.Collection.Local.Datas | 8 | 4 | 4 | |||||||||||||||||||||||||||||||||||||
| 27 Leagueoflegends.Collection.Local.ViewModels | 8 | 9 | 9 | |||||||||||||||||||||||||||||||||||||
| 28 Leagueoflegends.Main.Local.ViewModels | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 Leagueoflegends.Navigate.Local.Datas | 4 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 30 Leagueoflegends.Navigate.Local.Services | 4 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 31 Leagueoflegends.Navigate.Local.ViewModels | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 32 Leagueoflegends.Profile.Local.Datas | 6 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 33 Leagueoflegends.Profile.Local.ViewModels | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 34 Leagueoflegends.Social.Local.Datas | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 Leagueoflegends.Social.Local.ViewModels | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 Leagueoflegends.Store.Local.Datas | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 Leagueoflegends.Tft.Local.Datas | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 Leagueoflegends.Tft.Local.ViewModels | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 Lol.Database.Controller | 34 | 15 | ||||||||||||||||||||||||||||||||||||||
| 40 Lol.Foundation.Riotbase | 1 | 1 |
8→1 Leagueoflegends.Support.Local.Models uses Jamesnet.Foundation✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Support.Local.Models uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Support.Local.Models.MenuModel→Jamesnet.Foundation.ViewModelBaseLeagueoflegends.Support.Local.Models.SubMenuItem→Jamesnet.Foundation.ViewModelBase
- Direction
- Leagueoflegends.Support.Local.Models uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Support.Local.Models, while a change to Leagueoflegends.Support.Local.Models can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Support.Local.Models uses a module listed above it, which is the healthy direction.
9→3 Lol.Data.Setting uses Lol.Data.Setting.Clients✕
- Connections
- 5 pairs of types, where a type in Lol.Data.Setting uses a type in Lol.Data.Setting.Clients.
- The types involved
Lol.Data.Setting.SettingModel→Lol.Data.Setting.Clients.AlarmModelLol.Data.Setting.SettingModel→Lol.Data.Setting.Clients.ChatModelLol.Data.Setting.SettingModel→Lol.Data.Setting.Clients.GeneralModelLol.Data.Setting.SettingModel→Lol.Data.Setting.Clients.SoundModelLol.Data.Setting.SettingModel→Lol.Data.Setting.Clients.VoiceModel
- Direction
- Lol.Data.Setting uses Lol.Data.Setting.Clients, so a change to Lol.Data.Setting.Clients can break Lol.Data.Setting, while a change to Lol.Data.Setting can't break Lol.Data.Setting.Clients.
- Position
- Below the diagonal: Lol.Data.Setting uses a module listed above it, which is the healthy direction.
9→4 Lol.Data.Setting uses Lol.Data.Setting.InGame✕
- Connections
- 4 pairs of types, where a type in Lol.Data.Setting uses a type in Lol.Data.Setting.InGame.
- The types involved
Lol.Data.Setting.SettingModel→Lol.Data.Setting.InGame.GameModelLol.Data.Setting.SettingModel→Lol.Data.Setting.InGame.GameSoundModelLol.Data.Setting.SettingModel→Lol.Data.Setting.InGame.HotKeyModelLol.Data.Setting.SettingModel→Lol.Data.Setting.InGame.InterfaceModel
- Direction
- Lol.Data.Setting uses Lol.Data.Setting.InGame, so a change to Lol.Data.Setting.InGame can break Lol.Data.Setting, while a change to Lol.Data.Setting can't break Lol.Data.Setting.InGame.
- Position
- Below the diagonal: Lol.Data.Setting uses a module listed above it, which is the healthy direction.
10→6 Lol.Database.Collection uses Lol.Database.Entites.Schema✕
- Connections
- 2 pairs of types, where a type in Lol.Database.Collection uses a type in Lol.Database.Entites.Schema.
- The types involved
Lol.Database.Collection.FriendsCollection→Lol.Database.Entites.Schema.FriendsHeaderLol.Database.Collection.FriendsCollection→Lol.Database.Entites.Schema.IFriendsList
- Direction
- Lol.Database.Collection uses Lol.Database.Entites.Schema, so a change to Lol.Database.Entites.Schema can break Lol.Database.Collection, while a change to Lol.Database.Collection can't break Lol.Database.Entites.Schema.
- Position
- Below the diagonal: Lol.Database.Collection uses a module listed above it, which is the healthy direction.
11→6 Lol.Database.Entites.Statics uses Lol.Database.Entites.Schema✕
- Connections
- 39 pairs of types, where a type in Lol.Database.Entites.Statics uses a type in Lol.Database.Entites.Schema. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Lol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.ChampFilterLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.ChampTreeItemLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.ChampionsLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.ClashCupsLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.ClashSchedulesLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.ClashTabsLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.ClashTierDetailsLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.ClashTiersLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.CodeItemsLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.FriendsLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.GameRoomsLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.GameRoomsCustomLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.HistoryLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.ItemsLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.LobbyListLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.LootItemSortingsLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.LootsLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.MapTypesLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.MyItemInfosLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.NewSkinsLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.PlantHeadersLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.PlantItemsLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.PlayTypesLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.PopularitiesLol.Database.Entites.Statics.LolDataPack→Lol.Database.Entites.Schema.PopularityDetails
- Direction
- Lol.Database.Entites.Statics uses Lol.Database.Entites.Schema, so a change to Lol.Database.Entites.Schema can break Lol.Database.Entites.Statics, while a change to Lol.Database.Entites.Statics can't break Lol.Database.Entites.Schema.
- Position
- Below the diagonal: Lol.Database.Entites.Statics uses a module listed above it, which is the healthy direction.
12→6 Lol.Friends.Local.Collection uses Lol.Database.Entites.Schema✕
- Connections
- 1 pair of types, where a type in Lol.Friends.Local.Collection uses a type in Lol.Database.Entites.Schema.
- The types involved
Lol.Friends.Local.Collection.FriendsCollection→Lol.Database.Entites.Schema.RequestUsers
- Direction
- Lol.Friends.Local.Collection uses Lol.Database.Entites.Schema, so a change to Lol.Database.Entites.Schema can break Lol.Friends.Local.Collection, while a change to Lol.Friends.Local.Collection can't break Lol.Database.Entites.Schema.
- Position
- Below the diagonal: Lol.Friends.Local.Collection uses a module listed above it, which is the healthy direction.
13→2 Lol.Settings.Client.Local.ViewModels uses Lol.Data.Codes✕
- Connections
- 1 pair of types, where a type in Lol.Settings.Client.Local.ViewModels uses a type in Lol.Data.Codes.
- The types involved
Lol.Settings.Client.Local.ViewModels.VoiceViewModel→Lol.Data.Codes.AudioDevice
- Direction
- Lol.Settings.Client.Local.ViewModels uses Lol.Data.Codes, so a change to Lol.Data.Codes can break Lol.Settings.Client.Local.ViewModels, while a change to Lol.Settings.Client.Local.ViewModels can't break Lol.Data.Codes.
- Position
- Below the diagonal: Lol.Settings.Client.Local.ViewModels uses a module listed above it, which is the healthy direction.
13→3 Lol.Settings.Client.Local.ViewModels uses Lol.Data.Setting.Clients✕
- Connections
- 5 pairs of types, where a type in Lol.Settings.Client.Local.ViewModels uses a type in Lol.Data.Setting.Clients.
- The types involved
Lol.Settings.Client.Local.ViewModels.AlarmViewModel→Lol.Data.Setting.Clients.AlarmModelLol.Settings.Client.Local.ViewModels.ChatViewModel→Lol.Data.Setting.Clients.ChatModelLol.Settings.Client.Local.ViewModels.GeneralViewModel→Lol.Data.Setting.Clients.GeneralModelLol.Settings.Client.Local.ViewModels.SoundViewModel→Lol.Data.Setting.Clients.SoundModelLol.Settings.Client.Local.ViewModels.VoiceViewModel→Lol.Data.Setting.Clients.VoiceModel
- Direction
- Lol.Settings.Client.Local.ViewModels uses Lol.Data.Setting.Clients, so a change to Lol.Data.Setting.Clients can break Lol.Settings.Client.Local.ViewModels, while a change to Lol.Settings.Client.Local.ViewModels can't break Lol.Data.Setting.Clients.
- Position
- Below the diagonal: Lol.Settings.Client.Local.ViewModels uses a module listed above it, which is the healthy direction.
13→6 Lol.Settings.Client.Local.ViewModels uses Lol.Database.Entites.Schema✕
- Connections
- 2 pairs of types, where a type in Lol.Settings.Client.Local.ViewModels uses a type in Lol.Database.Entites.Schema.
- The types involved
Lol.Settings.Client.Local.ViewModels.GeneralViewModel→Lol.Database.Entites.Schema.ResolutionsLol.Settings.Client.Local.ViewModels.VoiceViewModel→Lol.Database.Entites.Schema.UsualCodes
- Direction
- Lol.Settings.Client.Local.ViewModels uses Lol.Database.Entites.Schema, so a change to Lol.Database.Entites.Schema can break Lol.Settings.Client.Local.ViewModels, while a change to Lol.Settings.Client.Local.ViewModels can't break Lol.Database.Entites.Schema.
- Position
- Below the diagonal: Lol.Settings.Client.Local.ViewModels uses a module listed above it, which is the healthy direction.
14→7 Lol.Support.Local.Helpers uses Lol.Support.Local.Models✕
- Connections
- 4 pairs of types, where a type in Lol.Support.Local.Helpers uses a type in Lol.Support.Local.Models.
- The types involved
Lol.Support.Local.Helpers.MenuService→Lol.Support.Local.Models.BackgroundChangedEventArgsLol.Support.Local.Helpers.MenuService→Lol.Support.Local.Models.MainMenuInfoLol.Support.Local.Helpers.MenuService→Lol.Support.Local.Models.MenuChangedEventArgsLol.Support.Local.Helpers.MenuService→Lol.Support.Local.Models.SubMenuInfo
- Direction
- Lol.Support.Local.Helpers uses Lol.Support.Local.Models, so a change to Lol.Support.Local.Models can break Lol.Support.Local.Helpers, while a change to Lol.Support.Local.Helpers can't break Lol.Support.Local.Models.
- Position
- Below the diagonal: Lol.Support.Local.Helpers uses a module listed above it, which is the healthy direction.
15→8 Leagueoflegends.Support.Local.Datas uses Leagueoflegends.Support.Local.Models✕
- Connections
- 13 pairs of types, where a type in Leagueoflegends.Support.Local.Datas uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Support.Local.Datas.IChampStatsDataLoader→Leagueoflegends.Support.Local.Models.ChampionStatsLeagueoflegends.Support.Local.Datas.IFriendDataLoader→Leagueoflegends.Support.Local.Models.FriendCategoryLeagueoflegends.Support.Local.Datas.IMatchHistoryDataLoader→Leagueoflegends.Support.Local.Models.MatchHistoryLeagueoflegends.Support.Local.Datas.IMenuDataLoader→Leagueoflegends.Support.Local.Models.MenuModelLeagueoflegends.Support.Local.Datas.IOptionDataLoader→Leagueoflegends.Support.Local.Models.OptionLeagueoflegends.Support.Local.Datas.IPlayChampDataLoader→Leagueoflegends.Support.Local.Models.PlayChampLeagueoflegends.Support.Local.Datas.IRecentDataLoader→Leagueoflegends.Support.Local.Models.RecentLeagueoflegends.Support.Local.Datas.IScheduleDataLoader→Leagueoflegends.Support.Local.Models.ScheduleLeagueoflegends.Support.Local.Datas.ISkinsDataLoader→Leagueoflegends.Support.Local.Models.SkinLeagueoflegends.Support.Local.Datas.ISpellsDataLoader→Leagueoflegends.Support.Local.Models.SpellLeagueoflegends.Support.Local.Datas.IStoreChampDataLoader→Leagueoflegends.Support.Local.Models.StoreChampLeagueoflegends.Support.Local.Datas.ISubMenuDataLoader→Leagueoflegends.Support.Local.Models.SubMenuItemLeagueoflegends.Support.Local.Datas.ITeamFightsDataLoader→Leagueoflegends.Support.Local.Models.TeamFight
- Direction
- Leagueoflegends.Support.Local.Datas uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Support.Local.Datas, while a change to Leagueoflegends.Support.Local.Datas can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Support.Local.Datas uses a module listed above it, which is the healthy direction.
16→8 Leagueoflegends.Support.Local.Services uses Leagueoflegends.Support.Local.Models✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Support.Local.Services uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Support.Local.Services.IMenuManager→Leagueoflegends.Support.Local.Models.MenuModelLeagueoflegends.Support.Local.Services.ISubMenuNavigator→Leagueoflegends.Support.Local.Models.SubMenuItem
- Direction
- Leagueoflegends.Support.Local.Services uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Support.Local.Services, while a change to Leagueoflegends.Support.Local.Services can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Support.Local.Services uses a module listed above it, which is the healthy direction.
17→6 Lol.Collection.Local.ViewModel uses Lol.Database.Entites.Schema✕
- Connections
- 8 pairs of types, where a type in Lol.Collection.Local.ViewModel uses a type in Lol.Database.Entites.Schema.
- The types involved
Lol.Collection.Local.ViewModel.ChampionsViewModel→Lol.Database.Entites.Schema.ChampFilterLol.Collection.Local.ViewModel.ChampionsViewModel→Lol.Database.Entites.Schema.ChampTreeItemLol.Collection.Local.ViewModel.ChampionsViewModel→Lol.Database.Entites.Schema.ChampionsLol.Collection.Local.ViewModel.ItemViewModel→Lol.Database.Entites.Schema.ItemsLol.Collection.Local.ViewModel.RuneViewModel→Lol.Database.Entites.Schema.RuneDetailLol.Collection.Local.ViewModel.RuneViewModel→Lol.Database.Entites.Schema.RunesLol.Collection.Local.ViewModel.SkinsViewModel→Lol.Database.Entites.Schema.SkinFilterLol.Collection.Local.ViewModel.SpellsViewModel→Lol.Database.Entites.Schema.Spells
- Direction
- Lol.Collection.Local.ViewModel uses Lol.Database.Entites.Schema, so a change to Lol.Database.Entites.Schema can break Lol.Collection.Local.ViewModel, while a change to Lol.Collection.Local.ViewModel can't break Lol.Database.Entites.Schema.
- Position
- Below the diagonal: Lol.Collection.Local.ViewModel uses a module listed above it, which is the healthy direction.
17→14 Lol.Collection.Local.ViewModel uses Lol.Support.Local.Helpers✕
- Connections
- 1 pair of types, where a type in Lol.Collection.Local.ViewModel uses a type in Lol.Support.Local.Helpers.
- The types involved
Lol.Collection.Local.ViewModel.SpellsViewModel→Lol.Support.Local.Helpers.MenuService
- Direction
- Lol.Collection.Local.ViewModel uses Lol.Support.Local.Helpers, so a change to Lol.Support.Local.Helpers can break Lol.Collection.Local.ViewModel, while a change to Lol.Collection.Local.ViewModel can't break Lol.Support.Local.Helpers.
- Position
- Below the diagonal: Lol.Collection.Local.ViewModel uses a module listed above it, which is the healthy direction.
18→9 Lol.Data.Config uses Lol.Data.Setting✕
- Connections
- 1 pair of types, where a type in Lol.Data.Config uses a type in Lol.Data.Setting.
- The types involved
Lol.Data.Config.ConfigModel→Lol.Data.Setting.SettingModel
- Direction
- Lol.Data.Config uses Lol.Data.Setting, so a change to Lol.Data.Setting can break Lol.Data.Config, while a change to Lol.Data.Config can't break Lol.Data.Setting.
- Position
- Below the diagonal: Lol.Data.Config uses a module listed above it, which is the healthy direction.
19→11 Lol.Database.Entites.Core uses Lol.Database.Entites.Statics✕
- Connections
- 1 pair of types, where a type in Lol.Database.Entites.Core uses a type in Lol.Database.Entites.Statics.
- The types involved
Lol.Database.Entites.Core.LolDbContext→Lol.Database.Entites.Statics.LolDataPack
- Direction
- Lol.Database.Entites.Core uses Lol.Database.Entites.Statics, so a change to Lol.Database.Entites.Statics can break Lol.Database.Entites.Core, while a change to Lol.Database.Entites.Core can't break Lol.Database.Entites.Statics.
- Position
- Below the diagonal: Lol.Database.Entites.Core uses a module listed above it, which is the healthy direction.
20→12 Lol.Friends.Local.ViewModel uses Lol.Friends.Local.Collection✕
- Connections
- 1 pair of types, where a type in Lol.Friends.Local.ViewModel uses a type in Lol.Friends.Local.Collection.
- The types involved
Lol.Friends.Local.ViewModel.AddFriendsViewModel→Lol.Friends.Local.Collection.FriendsCollection
- Direction
- Lol.Friends.Local.ViewModel uses Lol.Friends.Local.Collection, so a change to Lol.Friends.Local.Collection can break Lol.Friends.Local.ViewModel, while a change to Lol.Friends.Local.ViewModel can't break Lol.Friends.Local.Collection.
- Position
- Below the diagonal: Lol.Friends.Local.ViewModel uses a module listed above it, which is the healthy direction.
20→14 Lol.Friends.Local.ViewModel uses Lol.Support.Local.Helpers✕
- Connections
- 1 pair of types, where a type in Lol.Friends.Local.ViewModel uses a type in Lol.Support.Local.Helpers.
- The types involved
Lol.Friends.Local.ViewModel.AddFriendsViewModel→Lol.Support.Local.Helpers.MenuService
- Direction
- Lol.Friends.Local.ViewModel uses Lol.Support.Local.Helpers, so a change to Lol.Support.Local.Helpers can break Lol.Friends.Local.ViewModel, while a change to Lol.Friends.Local.ViewModel can't break Lol.Support.Local.Helpers.
- Position
- Below the diagonal: Lol.Friends.Local.ViewModel uses a module listed above it, which is the healthy direction.
21→6 Lol.GameRoom.Local.ViewModels uses Lol.Database.Entites.Schema✕
- Connections
- 7 pairs of types, where a type in Lol.GameRoom.Local.ViewModels uses a type in Lol.Database.Entites.Schema.
- The types involved
Lol.GameRoom.Local.ViewModels.CreateCustomViewModel→Lol.Database.Entites.Schema.CodeItemsLol.GameRoom.Local.ViewModels.CreateCustomViewModel→Lol.Database.Entites.Schema.GameRoomsCustomLol.GameRoom.Local.ViewModels.CreateCustomViewModel→Lol.Database.Entites.Schema.UserCountLol.GameRoom.Local.ViewModels.CustomGameRoomViewModel→Lol.Database.Entites.Schema.MyFriendsLol.GameRoom.Local.ViewModels.JoinCustomViewModel→Lol.Database.Entites.Schema.LobbyListLol.GameRoom.Local.ViewModels.PVPViewModel→Lol.Database.Entites.Schema.GameRoomsLol.GameRoom.Local.ViewModels.SummonersRiftViewModel→Lol.Database.Entites.Schema.MyFriends
- Direction
- Lol.GameRoom.Local.ViewModels uses Lol.Database.Entites.Schema, so a change to Lol.Database.Entites.Schema can break Lol.GameRoom.Local.ViewModels, while a change to Lol.GameRoom.Local.ViewModels can't break Lol.Database.Entites.Schema.
- Position
- Below the diagonal: Lol.GameRoom.Local.ViewModels uses a module listed above it, which is the healthy direction.
21→14 Lol.GameRoom.Local.ViewModels uses Lol.Support.Local.Helpers✕
- Connections
- 7 pairs of types, where a type in Lol.GameRoom.Local.ViewModels uses a type in Lol.Support.Local.Helpers.
- The types involved
Lol.GameRoom.Local.ViewModels.CreateCustomViewModel→Lol.Support.Local.Helpers.MenuServiceLol.GameRoom.Local.ViewModels.CustomGameRoomViewModel→Lol.Support.Local.Helpers.FriendsServiceLol.GameRoom.Local.ViewModels.CustomGameRoomViewModel→Lol.Support.Local.Helpers.MenuServiceLol.GameRoom.Local.ViewModels.JoinCustomViewModel→Lol.Support.Local.Helpers.MenuServiceLol.GameRoom.Local.ViewModels.PVPViewModel→Lol.Support.Local.Helpers.MenuServiceLol.GameRoom.Local.ViewModels.SummonersRiftViewModel→Lol.Support.Local.Helpers.FriendsServiceLol.GameRoom.Local.ViewModels.SummonersRiftViewModel→Lol.Support.Local.Helpers.MenuService
- Direction
- Lol.GameRoom.Local.ViewModels uses Lol.Support.Local.Helpers, so a change to Lol.Support.Local.Helpers can break Lol.GameRoom.Local.ViewModels, while a change to Lol.GameRoom.Local.ViewModels can't break Lol.Support.Local.Helpers.
- Position
- Below the diagonal: Lol.GameRoom.Local.ViewModels uses a module listed above it, which is the healthy direction.
22→7 Lol.Main.Local.ViewModels uses Lol.Support.Local.Models✕
- Connections
- 2 pairs of types, where a type in Lol.Main.Local.ViewModels uses a type in Lol.Support.Local.Models.
- The types involved
Lol.Main.Local.ViewModels.MainContentViewModel→Lol.Support.Local.Models.BackgroundChangedEventArgsLol.Main.Local.ViewModels.MainContentViewModel→Lol.Support.Local.Models.MenuChangedEventArgs
- Direction
- Lol.Main.Local.ViewModels uses Lol.Support.Local.Models, so a change to Lol.Support.Local.Models can break Lol.Main.Local.ViewModels, while a change to Lol.Main.Local.ViewModels can't break Lol.Support.Local.Models.
- Position
- Below the diagonal: Lol.Main.Local.ViewModels uses a module listed above it, which is the healthy direction.
22→10 Lol.Main.Local.ViewModels uses Lol.Database.Collection✕
- Connections
- 1 pair of types, where a type in Lol.Main.Local.ViewModels uses a type in Lol.Database.Collection.
- The types involved
Lol.Main.Local.ViewModels.MainContentViewModel→Lol.Database.Collection.FriendsCollection
- Direction
- Lol.Main.Local.ViewModels uses Lol.Database.Collection, so a change to Lol.Database.Collection can break Lol.Main.Local.ViewModels, while a change to Lol.Main.Local.ViewModels can't break Lol.Database.Collection.
- Position
- Below the diagonal: Lol.Main.Local.ViewModels uses a module listed above it, which is the healthy direction.
22→14 Lol.Main.Local.ViewModels uses Lol.Support.Local.Helpers✕
- Connections
- 2 pairs of types, where a type in Lol.Main.Local.ViewModels uses a type in Lol.Support.Local.Helpers.
- The types involved
Lol.Main.Local.ViewModels.MainContentViewModel→Lol.Support.Local.Helpers.FriendsServiceLol.Main.Local.ViewModels.MainContentViewModel→Lol.Support.Local.Helpers.MenuService
- Direction
- Lol.Main.Local.ViewModels uses Lol.Support.Local.Helpers, so a change to Lol.Support.Local.Helpers can break Lol.Main.Local.ViewModels, while a change to Lol.Main.Local.ViewModels can't break Lol.Support.Local.Helpers.
- Position
- Below the diagonal: Lol.Main.Local.ViewModels uses a module listed above it, which is the healthy direction.
23→7 Lol.Menus.Local.ViewModels uses Lol.Support.Local.Models✕
- Connections
- 3 pairs of types, where a type in Lol.Menus.Local.ViewModels uses a type in Lol.Support.Local.Models.
- The types involved
Lol.Menus.Local.ViewModels.MenuContentViewModel→Lol.Support.Local.Models.MainMenuInfoLol.Menus.Local.ViewModels.MenuContentViewModel→Lol.Support.Local.Models.MenuChangedEventArgsLol.Menus.Local.ViewModels.MenuContentViewModel→Lol.Support.Local.Models.SubMenuInfo
- Direction
- Lol.Menus.Local.ViewModels uses Lol.Support.Local.Models, so a change to Lol.Support.Local.Models can break Lol.Menus.Local.ViewModels, while a change to Lol.Menus.Local.ViewModels can't break Lol.Support.Local.Models.
- Position
- Below the diagonal: Lol.Menus.Local.ViewModels uses a module listed above it, which is the healthy direction.
23→14 Lol.Menus.Local.ViewModels uses Lol.Support.Local.Helpers✕
- Connections
- 1 pair of types, where a type in Lol.Menus.Local.ViewModels uses a type in Lol.Support.Local.Helpers.
- The types involved
Lol.Menus.Local.ViewModels.MenuContentViewModel→Lol.Support.Local.Helpers.MenuService
- Direction
- Lol.Menus.Local.ViewModels uses Lol.Support.Local.Helpers, so a change to Lol.Support.Local.Helpers can break Lol.Menus.Local.ViewModels, while a change to Lol.Menus.Local.ViewModels can't break Lol.Support.Local.Helpers.
- Position
- Below the diagonal: Lol.Menus.Local.ViewModels uses a module listed above it, which is the healthy direction.
24→1 Leagueoflegends.Clash.Local.Datas uses Jamesnet.Foundation✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Clash.Local.Datas uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Clash.Local.Datas.ScheduleDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Clash.Local.Datas.ScheduleDataLoader→Jamesnet.Foundation.YamlData
- Direction
- Leagueoflegends.Clash.Local.Datas uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Clash.Local.Datas, while a change to Leagueoflegends.Clash.Local.Datas can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Clash.Local.Datas uses a module listed above it, which is the healthy direction.
24→8 Leagueoflegends.Clash.Local.Datas uses Leagueoflegends.Support.Local.Models✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Clash.Local.Datas uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Clash.Local.Datas.ScheduleDataLoader→Leagueoflegends.Support.Local.Models.Schedule
- Direction
- Leagueoflegends.Clash.Local.Datas uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Clash.Local.Datas, while a change to Leagueoflegends.Clash.Local.Datas can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Clash.Local.Datas uses a module listed above it, which is the healthy direction.
24→15 Leagueoflegends.Clash.Local.Datas uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Clash.Local.Datas uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Clash.Local.Datas.ScheduleDataLoader→Leagueoflegends.Support.Local.Datas.IScheduleDataLoader
- Direction
- Leagueoflegends.Clash.Local.Datas uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Clash.Local.Datas, while a change to Leagueoflegends.Clash.Local.Datas can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Clash.Local.Datas uses a module listed above it, which is the healthy direction.
25→1 Leagueoflegends.Clash.Local.ViewModels uses Jamesnet.Foundation✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Clash.Local.ViewModels uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Clash.Local.ViewModels.HubContentViewModel→Jamesnet.Foundation.ViewModelBase
- Direction
- Leagueoflegends.Clash.Local.ViewModels uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Clash.Local.ViewModels, while a change to Leagueoflegends.Clash.Local.ViewModels can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Clash.Local.ViewModels uses a module listed above it, which is the healthy direction.
25→8 Leagueoflegends.Clash.Local.ViewModels uses Leagueoflegends.Support.Local.Models✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Clash.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Clash.Local.ViewModels.HubContentViewModel→Leagueoflegends.Support.Local.Models.MenuModelLeagueoflegends.Clash.Local.ViewModels.HubContentViewModel→Leagueoflegends.Support.Local.Models.Schedule
- Direction
- Leagueoflegends.Clash.Local.ViewModels uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Clash.Local.ViewModels, while a change to Leagueoflegends.Clash.Local.ViewModels can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Clash.Local.ViewModels uses a module listed above it, which is the healthy direction.
25→15 Leagueoflegends.Clash.Local.ViewModels uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Clash.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Clash.Local.ViewModels.HubContentViewModel→Leagueoflegends.Support.Local.Datas.IScheduleDataLoader
- Direction
- Leagueoflegends.Clash.Local.ViewModels uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Clash.Local.ViewModels, while a change to Leagueoflegends.Clash.Local.ViewModels can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Clash.Local.ViewModels uses a module listed above it, which is the healthy direction.
25→16 Leagueoflegends.Clash.Local.ViewModels uses Leagueoflegends.Support.Local.Services✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Clash.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Services.
- The types involved
Leagueoflegends.Clash.Local.ViewModels.HubContentViewModel→Leagueoflegends.Support.Local.Services.IMenuManager
- Direction
- Leagueoflegends.Clash.Local.ViewModels uses Leagueoflegends.Support.Local.Services, so a change to Leagueoflegends.Support.Local.Services can break Leagueoflegends.Clash.Local.ViewModels, while a change to Leagueoflegends.Clash.Local.ViewModels can't break Leagueoflegends.Support.Local.Services.
- Position
- Below the diagonal: Leagueoflegends.Clash.Local.ViewModels uses a module listed above it, which is the healthy direction.
26→1 Leagueoflegends.Collection.Local.Datas uses Jamesnet.Foundation✕
- Connections
- 8 pairs of types, where a type in Leagueoflegends.Collection.Local.Datas uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Collection.Local.Datas.ChampStatsDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Collection.Local.Datas.ChampStatsDataLoader→Jamesnet.Foundation.YamlDataLeagueoflegends.Collection.Local.Datas.OptionDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Collection.Local.Datas.OptionDataLoader→Jamesnet.Foundation.YamlDataLeagueoflegends.Collection.Local.Datas.SkinsDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Collection.Local.Datas.SkinsDataLoader→Jamesnet.Foundation.YamlDataLeagueoflegends.Collection.Local.Datas.SpellsDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Collection.Local.Datas.SpellsDataLoader→Jamesnet.Foundation.YamlData
- Direction
- Leagueoflegends.Collection.Local.Datas uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Collection.Local.Datas, while a change to Leagueoflegends.Collection.Local.Datas can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Collection.Local.Datas uses a module listed above it, which is the healthy direction.
26→8 Leagueoflegends.Collection.Local.Datas uses Leagueoflegends.Support.Local.Models✕
- Connections
- 4 pairs of types, where a type in Leagueoflegends.Collection.Local.Datas uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Collection.Local.Datas.ChampStatsDataLoader→Leagueoflegends.Support.Local.Models.ChampionStatsLeagueoflegends.Collection.Local.Datas.OptionDataLoader→Leagueoflegends.Support.Local.Models.OptionLeagueoflegends.Collection.Local.Datas.SkinsDataLoader→Leagueoflegends.Support.Local.Models.SkinLeagueoflegends.Collection.Local.Datas.SpellsDataLoader→Leagueoflegends.Support.Local.Models.Spell
- Direction
- Leagueoflegends.Collection.Local.Datas uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Collection.Local.Datas, while a change to Leagueoflegends.Collection.Local.Datas can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Collection.Local.Datas uses a module listed above it, which is the healthy direction.
26→15 Leagueoflegends.Collection.Local.Datas uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 4 pairs of types, where a type in Leagueoflegends.Collection.Local.Datas uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Collection.Local.Datas.ChampStatsDataLoader→Leagueoflegends.Support.Local.Datas.IChampStatsDataLoaderLeagueoflegends.Collection.Local.Datas.OptionDataLoader→Leagueoflegends.Support.Local.Datas.IOptionDataLoaderLeagueoflegends.Collection.Local.Datas.SkinsDataLoader→Leagueoflegends.Support.Local.Datas.ISkinsDataLoaderLeagueoflegends.Collection.Local.Datas.SpellsDataLoader→Leagueoflegends.Support.Local.Datas.ISpellsDataLoader
- Direction
- Leagueoflegends.Collection.Local.Datas uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Collection.Local.Datas, while a change to Leagueoflegends.Collection.Local.Datas can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Collection.Local.Datas uses a module listed above it, which is the healthy direction.
27→1 Leagueoflegends.Collection.Local.ViewModels uses Jamesnet.Foundation✕
- Connections
- 8 pairs of types, where a type in Leagueoflegends.Collection.Local.ViewModels uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Collection.Local.ViewModels.ChampionsContentViewModel→Jamesnet.Foundation.ViewModelBaseLeagueoflegends.Collection.Local.ViewModels.GeneralContentViewModel→Jamesnet.Foundation.IViewLoadableLeagueoflegends.Collection.Local.ViewModels.GeneralContentViewModel→Jamesnet.Foundation.ViewModelBaseLeagueoflegends.Collection.Local.ViewModels.SkinsContentViewModel→Jamesnet.Foundation.ViewModelBaseLeagueoflegends.Collection.Local.ViewModels.SpellsContentViewModel→Jamesnet.Foundation.ViewModelBaseLeagueoflegends.Collection.Local.ViewModels.StoreChampContentViewModel→Jamesnet.Foundation.ViewModelBaseLeagueoflegends.Collection.Local.ViewModels.VoiceContentViewModel→Jamesnet.Foundation.IViewLoadableLeagueoflegends.Collection.Local.ViewModels.VoiceContentViewModel→Jamesnet.Foundation.ViewModelBase
- Direction
- Leagueoflegends.Collection.Local.ViewModels uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Collection.Local.ViewModels, while a change to Leagueoflegends.Collection.Local.ViewModels can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Collection.Local.ViewModels uses a module listed above it, which is the healthy direction.
27→8 Leagueoflegends.Collection.Local.ViewModels uses Leagueoflegends.Support.Local.Models✕
- Connections
- 9 pairs of types, where a type in Leagueoflegends.Collection.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Collection.Local.ViewModels.ChampionsContentViewModel→Leagueoflegends.Support.Local.Models.ChampionGroupLeagueoflegends.Collection.Local.ViewModels.ChampionsContentViewModel→Leagueoflegends.Support.Local.Models.OptionLeagueoflegends.Collection.Local.ViewModels.GeneralContentViewModel→Leagueoflegends.Support.Local.Models.OptionLeagueoflegends.Collection.Local.ViewModels.SkinsContentViewModel→Leagueoflegends.Support.Local.Models.OptionLeagueoflegends.Collection.Local.ViewModels.SkinsContentViewModel→Leagueoflegends.Support.Local.Models.SkinGroupLeagueoflegends.Collection.Local.ViewModels.SpellsContentViewModel→Leagueoflegends.Support.Local.Models.SpellLeagueoflegends.Collection.Local.ViewModels.StoreChampContentViewModel→Leagueoflegends.Support.Local.Models.OptionLeagueoflegends.Collection.Local.ViewModels.StoreChampContentViewModel→Leagueoflegends.Support.Local.Models.StoreChampLeagueoflegends.Collection.Local.ViewModels.VoiceContentViewModel→Leagueoflegends.Support.Local.Models.Option
- Direction
- Leagueoflegends.Collection.Local.ViewModels uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Collection.Local.ViewModels, while a change to Leagueoflegends.Collection.Local.ViewModels can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Collection.Local.ViewModels uses a module listed above it, which is the healthy direction.
27→15 Leagueoflegends.Collection.Local.ViewModels uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 9 pairs of types, where a type in Leagueoflegends.Collection.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Collection.Local.ViewModels.ChampionsContentViewModel→Leagueoflegends.Support.Local.Datas.IChampStatsDataLoaderLeagueoflegends.Collection.Local.ViewModels.ChampionsContentViewModel→Leagueoflegends.Support.Local.Datas.IOptionDataLoaderLeagueoflegends.Collection.Local.ViewModels.GeneralContentViewModel→Leagueoflegends.Support.Local.Datas.IOptionDataLoaderLeagueoflegends.Collection.Local.ViewModels.SkinsContentViewModel→Leagueoflegends.Support.Local.Datas.IOptionDataLoaderLeagueoflegends.Collection.Local.ViewModels.SkinsContentViewModel→Leagueoflegends.Support.Local.Datas.ISkinsDataLoaderLeagueoflegends.Collection.Local.ViewModels.SpellsContentViewModel→Leagueoflegends.Support.Local.Datas.ISpellsDataLoaderLeagueoflegends.Collection.Local.ViewModels.StoreChampContentViewModel→Leagueoflegends.Support.Local.Datas.IOptionDataLoaderLeagueoflegends.Collection.Local.ViewModels.StoreChampContentViewModel→Leagueoflegends.Support.Local.Datas.IStoreChampDataLoaderLeagueoflegends.Collection.Local.ViewModels.VoiceContentViewModel→Leagueoflegends.Support.Local.Datas.IOptionDataLoader
- Direction
- Leagueoflegends.Collection.Local.ViewModels uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Collection.Local.ViewModels, while a change to Leagueoflegends.Collection.Local.ViewModels can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Collection.Local.ViewModels uses a module listed above it, which is the healthy direction.
28→1 Leagueoflegends.Main.Local.ViewModels uses Jamesnet.Foundation✕
- Connections
- 3 pairs of types, where a type in Leagueoflegends.Main.Local.ViewModels uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Main.Local.ViewModels.MainContentViewModel→Jamesnet.Foundation.IViewLoadableLeagueoflegends.Main.Local.ViewModels.MainContentViewModel→Jamesnet.Foundation.ViewModelBaseLeagueoflegends.Main.Local.ViewModels.OptionContentViewModel→Jamesnet.Foundation.ViewModelBase
- Direction
- Leagueoflegends.Main.Local.ViewModels uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Main.Local.ViewModels, while a change to Leagueoflegends.Main.Local.ViewModels can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Main.Local.ViewModels uses a module listed above it, which is the healthy direction.
28→16 Leagueoflegends.Main.Local.ViewModels uses Leagueoflegends.Support.Local.Services✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Main.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Services.
- The types involved
Leagueoflegends.Main.Local.ViewModels.MainContentViewModel→Leagueoflegends.Support.Local.Services.IMenuManagerLeagueoflegends.Main.Local.ViewModels.OptionContentViewModel→Leagueoflegends.Support.Local.Services.IMenuManager
- Direction
- Leagueoflegends.Main.Local.ViewModels uses Leagueoflegends.Support.Local.Services, so a change to Leagueoflegends.Support.Local.Services can break Leagueoflegends.Main.Local.ViewModels, while a change to Leagueoflegends.Main.Local.ViewModels can't break Leagueoflegends.Support.Local.Services.
- Position
- Below the diagonal: Leagueoflegends.Main.Local.ViewModels uses a module listed above it, which is the healthy direction.
29→1 Leagueoflegends.Navigate.Local.Datas uses Jamesnet.Foundation✕
- Connections
- 4 pairs of types, where a type in Leagueoflegends.Navigate.Local.Datas uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Navigate.Local.Datas.MenuDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Navigate.Local.Datas.MenuDataLoader→Jamesnet.Foundation.YamlDataLeagueoflegends.Navigate.Local.Datas.SubMenuDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Navigate.Local.Datas.SubMenuDataLoader→Jamesnet.Foundation.YamlData
- Direction
- Leagueoflegends.Navigate.Local.Datas uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Navigate.Local.Datas, while a change to Leagueoflegends.Navigate.Local.Datas can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Navigate.Local.Datas uses a module listed above it, which is the healthy direction.
29→8 Leagueoflegends.Navigate.Local.Datas uses Leagueoflegends.Support.Local.Models✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Navigate.Local.Datas uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Navigate.Local.Datas.MenuDataLoader→Leagueoflegends.Support.Local.Models.MenuModelLeagueoflegends.Navigate.Local.Datas.SubMenuDataLoader→Leagueoflegends.Support.Local.Models.SubMenuItem
- Direction
- Leagueoflegends.Navigate.Local.Datas uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Navigate.Local.Datas, while a change to Leagueoflegends.Navigate.Local.Datas can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Navigate.Local.Datas uses a module listed above it, which is the healthy direction.
29→15 Leagueoflegends.Navigate.Local.Datas uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Navigate.Local.Datas uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Navigate.Local.Datas.MenuDataLoader→Leagueoflegends.Support.Local.Datas.IMenuDataLoaderLeagueoflegends.Navigate.Local.Datas.SubMenuDataLoader→Leagueoflegends.Support.Local.Datas.ISubMenuDataLoader
- Direction
- Leagueoflegends.Navigate.Local.Datas uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Navigate.Local.Datas, while a change to Leagueoflegends.Navigate.Local.Datas can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Navigate.Local.Datas uses a module listed above it, which is the healthy direction.
30→1 Leagueoflegends.Navigate.Local.Services uses Jamesnet.Foundation✕
- Connections
- 4 pairs of types, where a type in Leagueoflegends.Navigate.Local.Services uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Navigate.Local.Services.MenuManager→Jamesnet.Foundation.IContainerLeagueoflegends.Navigate.Local.Services.MenuManager→Jamesnet.Foundation.ILayerManagerLeagueoflegends.Navigate.Local.Services.SubMenuNavigator→Jamesnet.Foundation.IContainerLeagueoflegends.Navigate.Local.Services.SubMenuNavigator→Jamesnet.Foundation.ILayerManager
- Direction
- Leagueoflegends.Navigate.Local.Services uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Navigate.Local.Services, while a change to Leagueoflegends.Navigate.Local.Services can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Navigate.Local.Services uses a module listed above it, which is the healthy direction.
30→8 Leagueoflegends.Navigate.Local.Services uses Leagueoflegends.Support.Local.Models✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Navigate.Local.Services uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Navigate.Local.Services.MenuManager→Leagueoflegends.Support.Local.Models.MenuModelLeagueoflegends.Navigate.Local.Services.SubMenuNavigator→Leagueoflegends.Support.Local.Models.SubMenuItem
- Direction
- Leagueoflegends.Navigate.Local.Services uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Navigate.Local.Services, while a change to Leagueoflegends.Navigate.Local.Services can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Navigate.Local.Services uses a module listed above it, which is the healthy direction.
30→15 Leagueoflegends.Navigate.Local.Services uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Navigate.Local.Services uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Navigate.Local.Services.MenuManager→Leagueoflegends.Support.Local.Datas.IMenuDataLoaderLeagueoflegends.Navigate.Local.Services.SubMenuNavigator→Leagueoflegends.Support.Local.Datas.ISubMenuDataLoader
- Direction
- Leagueoflegends.Navigate.Local.Services uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Navigate.Local.Services, while a change to Leagueoflegends.Navigate.Local.Services can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Navigate.Local.Services uses a module listed above it, which is the healthy direction.
30→16 Leagueoflegends.Navigate.Local.Services uses Leagueoflegends.Support.Local.Services✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Navigate.Local.Services uses a type in Leagueoflegends.Support.Local.Services.
- The types involved
Leagueoflegends.Navigate.Local.Services.MenuManager→Leagueoflegends.Support.Local.Services.IMenuManagerLeagueoflegends.Navigate.Local.Services.SubMenuNavigator→Leagueoflegends.Support.Local.Services.ISubMenuNavigator
- Direction
- Leagueoflegends.Navigate.Local.Services uses Leagueoflegends.Support.Local.Services, so a change to Leagueoflegends.Support.Local.Services can break Leagueoflegends.Navigate.Local.Services, while a change to Leagueoflegends.Navigate.Local.Services can't break Leagueoflegends.Support.Local.Services.
- Position
- Below the diagonal: Leagueoflegends.Navigate.Local.Services uses a module listed above it, which is the healthy direction.
31→1 Leagueoflegends.Navigate.Local.ViewModels uses Jamesnet.Foundation✕
- Connections
- 3 pairs of types, where a type in Leagueoflegends.Navigate.Local.ViewModels uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Navigate.Local.ViewModels.OptionMenuContentViewModel→Jamesnet.Foundation.IViewLoadableLeagueoflegends.Navigate.Local.ViewModels.OptionMenuContentViewModel→Jamesnet.Foundation.ViewModelBaseLeagueoflegends.Navigate.Local.ViewModels.SubMenuContentViewModel→Jamesnet.Foundation.ViewModelBase
- Direction
- Leagueoflegends.Navigate.Local.ViewModels uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Navigate.Local.ViewModels, while a change to Leagueoflegends.Navigate.Local.ViewModels can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Navigate.Local.ViewModels uses a module listed above it, which is the healthy direction.
31→8 Leagueoflegends.Navigate.Local.ViewModels uses Leagueoflegends.Support.Local.Models✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Navigate.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Navigate.Local.ViewModels.SubMenuContentViewModel→Leagueoflegends.Support.Local.Models.MenuModel
- Direction
- Leagueoflegends.Navigate.Local.ViewModels uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Navigate.Local.ViewModels, while a change to Leagueoflegends.Navigate.Local.ViewModels can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Navigate.Local.ViewModels uses a module listed above it, which is the healthy direction.
31→16 Leagueoflegends.Navigate.Local.ViewModels uses Leagueoflegends.Support.Local.Services✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Navigate.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Services.
- The types involved
Leagueoflegends.Navigate.Local.ViewModels.OptionMenuContentViewModel→Leagueoflegends.Support.Local.Services.IMenuManagerLeagueoflegends.Navigate.Local.ViewModels.SubMenuContentViewModel→Leagueoflegends.Support.Local.Services.IMenuManager
- Direction
- Leagueoflegends.Navigate.Local.ViewModels uses Leagueoflegends.Support.Local.Services, so a change to Leagueoflegends.Support.Local.Services can break Leagueoflegends.Navigate.Local.ViewModels, while a change to Leagueoflegends.Navigate.Local.ViewModels can't break Leagueoflegends.Support.Local.Services.
- Position
- Below the diagonal: Leagueoflegends.Navigate.Local.ViewModels uses a module listed above it, which is the healthy direction.
32→1 Leagueoflegends.Profile.Local.Datas uses Jamesnet.Foundation✕
- Connections
- 6 pairs of types, where a type in Leagueoflegends.Profile.Local.Datas uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Profile.Local.Datas.MatchHistoryDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Profile.Local.Datas.MatchHistoryDataLoader→Jamesnet.Foundation.YamlDataLeagueoflegends.Profile.Local.Datas.PlayChampDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Profile.Local.Datas.PlayChampDataLoader→Jamesnet.Foundation.YamlDataLeagueoflegends.Profile.Local.Datas.RecentDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Profile.Local.Datas.RecentDataLoader→Jamesnet.Foundation.YamlData
- Direction
- Leagueoflegends.Profile.Local.Datas uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Profile.Local.Datas, while a change to Leagueoflegends.Profile.Local.Datas can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Profile.Local.Datas uses a module listed above it, which is the healthy direction.
32→8 Leagueoflegends.Profile.Local.Datas uses Leagueoflegends.Support.Local.Models✕
- Connections
- 3 pairs of types, where a type in Leagueoflegends.Profile.Local.Datas uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Profile.Local.Datas.MatchHistoryDataLoader→Leagueoflegends.Support.Local.Models.MatchHistoryLeagueoflegends.Profile.Local.Datas.PlayChampDataLoader→Leagueoflegends.Support.Local.Models.PlayChampLeagueoflegends.Profile.Local.Datas.RecentDataLoader→Leagueoflegends.Support.Local.Models.Recent
- Direction
- Leagueoflegends.Profile.Local.Datas uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Profile.Local.Datas, while a change to Leagueoflegends.Profile.Local.Datas can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Profile.Local.Datas uses a module listed above it, which is the healthy direction.
32→15 Leagueoflegends.Profile.Local.Datas uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 3 pairs of types, where a type in Leagueoflegends.Profile.Local.Datas uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Profile.Local.Datas.MatchHistoryDataLoader→Leagueoflegends.Support.Local.Datas.IMatchHistoryDataLoaderLeagueoflegends.Profile.Local.Datas.PlayChampDataLoader→Leagueoflegends.Support.Local.Datas.IPlayChampDataLoaderLeagueoflegends.Profile.Local.Datas.RecentDataLoader→Leagueoflegends.Support.Local.Datas.IRecentDataLoader
- Direction
- Leagueoflegends.Profile.Local.Datas uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Profile.Local.Datas, while a change to Leagueoflegends.Profile.Local.Datas can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Profile.Local.Datas uses a module listed above it, which is the healthy direction.
33→1 Leagueoflegends.Profile.Local.ViewModels uses Jamesnet.Foundation✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Profile.Local.ViewModels uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Profile.Local.ViewModels.HistoryContentViewModel→Jamesnet.Foundation.ViewModelBase
- Direction
- Leagueoflegends.Profile.Local.ViewModels uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Profile.Local.ViewModels, while a change to Leagueoflegends.Profile.Local.ViewModels can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Profile.Local.ViewModels uses a module listed above it, which is the healthy direction.
33→8 Leagueoflegends.Profile.Local.ViewModels uses Leagueoflegends.Support.Local.Models✕
- Connections
- 3 pairs of types, where a type in Leagueoflegends.Profile.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Profile.Local.ViewModels.HistoryContentViewModel→Leagueoflegends.Support.Local.Models.MatchHistoryLeagueoflegends.Profile.Local.ViewModels.HistoryContentViewModel→Leagueoflegends.Support.Local.Models.PlayChampLeagueoflegends.Profile.Local.ViewModels.HistoryContentViewModel→Leagueoflegends.Support.Local.Models.Recent
- Direction
- Leagueoflegends.Profile.Local.ViewModels uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Profile.Local.ViewModels, while a change to Leagueoflegends.Profile.Local.ViewModels can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Profile.Local.ViewModels uses a module listed above it, which is the healthy direction.
33→15 Leagueoflegends.Profile.Local.ViewModels uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 3 pairs of types, where a type in Leagueoflegends.Profile.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Profile.Local.ViewModels.HistoryContentViewModel→Leagueoflegends.Support.Local.Datas.IMatchHistoryDataLoaderLeagueoflegends.Profile.Local.ViewModels.HistoryContentViewModel→Leagueoflegends.Support.Local.Datas.IPlayChampDataLoaderLeagueoflegends.Profile.Local.ViewModels.HistoryContentViewModel→Leagueoflegends.Support.Local.Datas.IRecentDataLoader
- Direction
- Leagueoflegends.Profile.Local.ViewModels uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Profile.Local.ViewModels, while a change to Leagueoflegends.Profile.Local.ViewModels can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Profile.Local.ViewModels uses a module listed above it, which is the healthy direction.
34→1 Leagueoflegends.Social.Local.Datas uses Jamesnet.Foundation✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Social.Local.Datas uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Social.Local.Datas.FriendDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Social.Local.Datas.FriendDataLoader→Jamesnet.Foundation.YamlData
- Direction
- Leagueoflegends.Social.Local.Datas uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Social.Local.Datas, while a change to Leagueoflegends.Social.Local.Datas can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Social.Local.Datas uses a module listed above it, which is the healthy direction.
34→8 Leagueoflegends.Social.Local.Datas uses Leagueoflegends.Support.Local.Models✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Social.Local.Datas uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Social.Local.Datas.FriendDataLoader→Leagueoflegends.Support.Local.Models.FriendLeagueoflegends.Social.Local.Datas.FriendDataLoader→Leagueoflegends.Support.Local.Models.FriendCategory
- Direction
- Leagueoflegends.Social.Local.Datas uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Social.Local.Datas, while a change to Leagueoflegends.Social.Local.Datas can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Social.Local.Datas uses a module listed above it, which is the healthy direction.
34→15 Leagueoflegends.Social.Local.Datas uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Social.Local.Datas uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Social.Local.Datas.FriendDataLoader→Leagueoflegends.Support.Local.Datas.IFriendDataLoader
- Direction
- Leagueoflegends.Social.Local.Datas uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Social.Local.Datas, while a change to Leagueoflegends.Social.Local.Datas can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Social.Local.Datas uses a module listed above it, which is the healthy direction.
35→1 Leagueoflegends.Social.Local.ViewModels uses Jamesnet.Foundation✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Social.Local.ViewModels uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Social.Local.ViewModels.SocialContentViewModel→Jamesnet.Foundation.ViewModelBase
- Direction
- Leagueoflegends.Social.Local.ViewModels uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Social.Local.ViewModels, while a change to Leagueoflegends.Social.Local.ViewModels can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Social.Local.ViewModels uses a module listed above it, which is the healthy direction.
35→8 Leagueoflegends.Social.Local.ViewModels uses Leagueoflegends.Support.Local.Models✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Social.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Social.Local.ViewModels.SocialContentViewModel→Leagueoflegends.Support.Local.Models.FriendCategory
- Direction
- Leagueoflegends.Social.Local.ViewModels uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Social.Local.ViewModels, while a change to Leagueoflegends.Social.Local.ViewModels can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Social.Local.ViewModels uses a module listed above it, which is the healthy direction.
35→15 Leagueoflegends.Social.Local.ViewModels uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Social.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Social.Local.ViewModels.SocialContentViewModel→Leagueoflegends.Support.Local.Datas.IFriendDataLoader
- Direction
- Leagueoflegends.Social.Local.ViewModels uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Social.Local.ViewModels, while a change to Leagueoflegends.Social.Local.ViewModels can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Social.Local.ViewModels uses a module listed above it, which is the healthy direction.
36→1 Leagueoflegends.Store.Local.Datas uses Jamesnet.Foundation✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Store.Local.Datas uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Store.Local.Datas.StoreChampDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Store.Local.Datas.StoreChampDataLoader→Jamesnet.Foundation.YamlData
- Direction
- Leagueoflegends.Store.Local.Datas uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Store.Local.Datas, while a change to Leagueoflegends.Store.Local.Datas can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Store.Local.Datas uses a module listed above it, which is the healthy direction.
36→8 Leagueoflegends.Store.Local.Datas uses Leagueoflegends.Support.Local.Models✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Store.Local.Datas uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Store.Local.Datas.StoreChampDataLoader→Leagueoflegends.Support.Local.Models.StoreChamp
- Direction
- Leagueoflegends.Store.Local.Datas uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Store.Local.Datas, while a change to Leagueoflegends.Store.Local.Datas can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Store.Local.Datas uses a module listed above it, which is the healthy direction.
36→15 Leagueoflegends.Store.Local.Datas uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Store.Local.Datas uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Store.Local.Datas.StoreChampDataLoader→Leagueoflegends.Support.Local.Datas.IStoreChampDataLoader
- Direction
- Leagueoflegends.Store.Local.Datas uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Store.Local.Datas, while a change to Leagueoflegends.Store.Local.Datas can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Store.Local.Datas uses a module listed above it, which is the healthy direction.
37→1 Leagueoflegends.Tft.Local.Datas uses Jamesnet.Foundation✕
- Connections
- 2 pairs of types, where a type in Leagueoflegends.Tft.Local.Datas uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Tft.Local.Datas.TeamFightsDataLoader→Jamesnet.Foundation.BaseResourceLoaderLeagueoflegends.Tft.Local.Datas.TeamFightsDataLoader→Jamesnet.Foundation.YamlData
- Direction
- Leagueoflegends.Tft.Local.Datas uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Tft.Local.Datas, while a change to Leagueoflegends.Tft.Local.Datas can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Tft.Local.Datas uses a module listed above it, which is the healthy direction.
37→8 Leagueoflegends.Tft.Local.Datas uses Leagueoflegends.Support.Local.Models✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Tft.Local.Datas uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Tft.Local.Datas.TeamFightsDataLoader→Leagueoflegends.Support.Local.Models.TeamFight
- Direction
- Leagueoflegends.Tft.Local.Datas uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Tft.Local.Datas, while a change to Leagueoflegends.Tft.Local.Datas can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Tft.Local.Datas uses a module listed above it, which is the healthy direction.
37→15 Leagueoflegends.Tft.Local.Datas uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Tft.Local.Datas uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Tft.Local.Datas.TeamFightsDataLoader→Leagueoflegends.Support.Local.Datas.ITeamFightsDataLoader
- Direction
- Leagueoflegends.Tft.Local.Datas uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Tft.Local.Datas, while a change to Leagueoflegends.Tft.Local.Datas can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Tft.Local.Datas uses a module listed above it, which is the healthy direction.
38→1 Leagueoflegends.Tft.Local.ViewModels uses Jamesnet.Foundation✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Tft.Local.ViewModels uses a type in Jamesnet.Foundation.
- The types involved
Leagueoflegends.Tft.Local.ViewModels.TftContentViewModel→Jamesnet.Foundation.ViewModelBase
- Direction
- Leagueoflegends.Tft.Local.ViewModels uses Jamesnet.Foundation, so a change to Jamesnet.Foundation can break Leagueoflegends.Tft.Local.ViewModels, while a change to Leagueoflegends.Tft.Local.ViewModels can't break Jamesnet.Foundation.
- Position
- Below the diagonal: Leagueoflegends.Tft.Local.ViewModels uses a module listed above it, which is the healthy direction.
38→8 Leagueoflegends.Tft.Local.ViewModels uses Leagueoflegends.Support.Local.Models✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Tft.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Models.
- The types involved
Leagueoflegends.Tft.Local.ViewModels.TftContentViewModel→Leagueoflegends.Support.Local.Models.TeamFight
- Direction
- Leagueoflegends.Tft.Local.ViewModels uses Leagueoflegends.Support.Local.Models, so a change to Leagueoflegends.Support.Local.Models can break Leagueoflegends.Tft.Local.ViewModels, while a change to Leagueoflegends.Tft.Local.ViewModels can't break Leagueoflegends.Support.Local.Models.
- Position
- Below the diagonal: Leagueoflegends.Tft.Local.ViewModels uses a module listed above it, which is the healthy direction.
38→15 Leagueoflegends.Tft.Local.ViewModels uses Leagueoflegends.Support.Local.Datas✕
- Connections
- 1 pair of types, where a type in Leagueoflegends.Tft.Local.ViewModels uses a type in Leagueoflegends.Support.Local.Datas.
- The types involved
Leagueoflegends.Tft.Local.ViewModels.TftContentViewModel→Leagueoflegends.Support.Local.Datas.ITeamFightsDataLoader
- Direction
- Leagueoflegends.Tft.Local.ViewModels uses Leagueoflegends.Support.Local.Datas, so a change to Leagueoflegends.Support.Local.Datas can break Leagueoflegends.Tft.Local.ViewModels, while a change to Leagueoflegends.Tft.Local.ViewModels can't break Leagueoflegends.Support.Local.Datas.
- Position
- Below the diagonal: Leagueoflegends.Tft.Local.ViewModels uses a module listed above it, which is the healthy direction.
39→6 Lol.Database.Controller uses Lol.Database.Entites.Schema✕
- Connections
- 34 pairs of types, where a type in Lol.Database.Controller uses a type in Lol.Database.Entites.Schema. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Lol.Database.Controller.ChampApi→Lol.Database.Entites.Schema.ChampFilterLol.Database.Controller.ChampApi→Lol.Database.Entites.Schema.ChampTreeItemLol.Database.Controller.ChampApi→Lol.Database.Entites.Schema.ChampionsLol.Database.Controller.ClashCupApi→Lol.Database.Entites.Schema.ClashCupsLol.Database.Controller.ClashCupApi→Lol.Database.Entites.Schema.ClashSchedulesLol.Database.Controller.ClashCupApi→Lol.Database.Entites.Schema.ClashTabsLol.Database.Controller.ClashCupApi→Lol.Database.Entites.Schema.ClashTierDetailsLol.Database.Controller.ClashCupApi→Lol.Database.Entites.Schema.ClashTiersLol.Database.Controller.CodesApi→Lol.Database.Entites.Schema.UsualCodesLol.Database.Controller.FriendsApi→Lol.Database.Entites.Schema.IFriendsListLol.Database.Controller.FriendsApi→Lol.Database.Entites.Schema.RequestUsersLol.Database.Controller.GameRoomApi→Lol.Database.Entites.Schema.GameRoomsLol.Database.Controller.GameRoomApi→Lol.Database.Entites.Schema.GameRoomsCustomLol.Database.Controller.GameRoomApi→Lol.Database.Entites.Schema.LobbyListLol.Database.Controller.GameRoomApi→Lol.Database.Entites.Schema.UserCountLol.Database.Controller.HistoryApi→Lol.Database.Entites.Schema.HistoryLol.Database.Controller.ItemApi→Lol.Database.Entites.Schema.ItemsLol.Database.Controller.LootApi→Lol.Database.Entites.Schema.LootItemSortingsLol.Database.Controller.LootApi→Lol.Database.Entites.Schema.LootsLol.Database.Controller.LootApi→Lol.Database.Entites.Schema.PlantHeadersLol.Database.Controller.ProfileApi→Lol.Database.Entites.Schema.MyItemInfosLol.Database.Controller.RuneApi→Lol.Database.Entites.Schema.RuneDetailLol.Database.Controller.RuneApi→Lol.Database.Entites.Schema.RunesLol.Database.Controller.SettingsApi→Lol.Database.Entites.Schema.ResolutionsLol.Database.Controller.SettingsApi→Lol.Database.Entites.Schema.SettingMenus
- Direction
- Lol.Database.Controller uses Lol.Database.Entites.Schema, so a change to Lol.Database.Entites.Schema can break Lol.Database.Controller, while a change to Lol.Database.Controller can't break Lol.Database.Entites.Schema.
- Position
- Below the diagonal: Lol.Database.Controller uses a module listed above it, which is the healthy direction.
39→19 Lol.Database.Controller uses Lol.Database.Entites.Core✕
- Connections
- 15 pairs of types, where a type in Lol.Database.Controller uses a type in Lol.Database.Entites.Core.
- The types involved
Lol.Database.Controller.ChampApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.ClashCupApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.CodesApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.FriendsApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.GameRoomApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.HistoryApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.ItemApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.LootApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.ProfileApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.RuneApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.SettingsApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.SkinApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.SpellApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.StoreApi→Lol.Database.Entites.Core.LolDbContextLol.Database.Controller.TeamFightApi→Lol.Database.Entites.Core.LolDbContext
- Direction
- Lol.Database.Controller uses Lol.Database.Entites.Core, so a change to Lol.Database.Entites.Core can break Lol.Database.Controller, while a change to Lol.Database.Controller can't break Lol.Database.Entites.Core.
- Position
- Below the diagonal: Lol.Database.Controller uses a module listed above it, which is the healthy direction.
40→9 Lol.Foundation.Riotbase uses Lol.Data.Setting✕
- Connections
- 1 pair of types, where a type in Lol.Foundation.Riotbase uses a type in Lol.Data.Setting.
- The types involved
Lol.Foundation.Riotbase.RiotConfig→Lol.Data.Setting.SettingModel
- Direction
- Lol.Foundation.Riotbase uses Lol.Data.Setting, so a change to Lol.Data.Setting can break Lol.Foundation.Riotbase, while a change to Lol.Foundation.Riotbase can't break Lol.Data.Setting.
- Position
- Below the diagonal: Lol.Foundation.Riotbase uses a module listed above it, which is the healthy direction.
40→18 Lol.Foundation.Riotbase uses Lol.Data.Config✕
- Connections
- 1 pair of types, where a type in Lol.Foundation.Riotbase uses a type in Lol.Data.Config.
- The types involved
Lol.Foundation.Riotbase.RiotConfig→Lol.Data.Config.ConfigModel
- Direction
- Lol.Foundation.Riotbase uses Lol.Data.Config, so a change to Lol.Data.Config can break Lol.Foundation.Riotbase, while a change to Lol.Foundation.Riotbase can't break Lol.Data.Config.
- Position
- Below the diagonal: Lol.Foundation.Riotbase uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 3 | High / 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with Container.cs (2), ChampionsViewModel.cs (2), MenuContentViewModel.cs. | +8.2 pts | Medium | Knowledge Freshness |
| Resolve the 92 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (92). | +7.9 pts | Medium | Comment Value |
| Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with WPFLayer.cs. | +3.0 pts | Low | Explicit Debt |
| Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RiotHorizontalProgress.cs, RiotVerticalProgress.cs. | +3.0 pts | Low | Explicit 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 pts | Medium | Architecture documentation |
| Resolve the 4 Shell project finding(s) in Solution Shape — start with Lol.Converter.csproj, Lol.DBEntity.csproj, Lol.ExampleData.csproj. | +1.6 pts | Low | Solution Shape |
| Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`. | +2.5 pts | Medium | Nullable 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 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/Leagueoflegends.Support/UI/Units/RiotHorizontalProgress.cs | 6.1 | Near-clean | Explicit Debt: WriteOnlyPrivateField |
| _backup/obsolate/Lol.Main/Lol.Main.csproj | 6.4 | Near-clean | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| _backup/obsolate/Lol.Home/Lol.Home.csproj | 6.4 | Near-clean | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| _backup/obsolate/Lol.MyShop/Lol.MyShop.csproj | 6.4 | Near-clean | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| _backup/obsolate/Lol.Settings.About/Lol.Settings.About.csproj | 6.4 | Near-clean | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| _backup/obsolate/Lol.Support/Lol.Support.csproj | 6.4 | Near-clean | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| _backup/obsolate/Lol.Database/Lol.Database.csproj | 6.4 | Near-clean | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| _backup/obsolate/Lol.Data/Lol.Data.csproj | 6.4 | Near-clean | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| _backup/obsolate/Lol.Foundation/Lol.Foundation.csproj | 6.4 | Near-clean | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs | 6.9 | Near-clean | Explicit Debt: TodoComment |
| src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs | 7.1 | Near-clean | Code Duplication: Edited copy of a member (8 corresponding lines) |
| src/Jamesnet.Core/AppBootstrapper.cs | 7.2 | Near-clean | Code Duplication: Edited copy of a member (6 corresponding lines) |
| src/Jamesnet.Core/Container.cs | 7.2 | Near-clean | Code Duplication: Edited copy of a member (4 corresponding lines) |
| REDACTED | 7.2 | Near-clean | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): High secret: REDACTED |
| _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs | 7.3 | Near-clean | Explicit Debt: CommentedOutCode |
| _backup/obsolate/Lol.Database/Controller/StoreApi.cs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs | 7.4 | Near-clean | Code Duplication: Members sharing a duplicated core (6 members, 50+ identical tokens) |
| _backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.cs | 7.4 | Near-clean | Code Duplication: Edited copies of one member (4 members, 14+ corresponding lines) |
| src/Jamesnet.Core/DefaultViewModelInitializer.cs | 7.4 | Near-clean | Code Duplication: Edited copy of a member (11 corresponding lines) |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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.
What we checked — 42 dimensions across the health lenses
- 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.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- 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.
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
- 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 Complexity
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.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with LolDataPack.cs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
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.
What to do
- 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).
- 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).
- 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).
D5 · Coupling
54 projects, 0 dependency cycle(s), 1 unstable depended-on project(s).
What to do
- 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).
- 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).
D6 · Cohesion (LCOM4)
0 of 49 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
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.
What to do
- 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).
- Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with WPFLayer.cs. — One of this dimension's main actionable groups (1 issue-level).
- 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).
D18 · Solution Shape
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`.
What to do
- 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).
- 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).
- 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).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 3 document(s) read across 47 unit(s).
D24 · Comment Value
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.
What to do
- 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).
D26 · Project Cohesion
0 of 54 projects flagged as possibly oversized/incoherent.
D27 · Navigability
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.
D28 · Secrets (history)
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.
What to do
- 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).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
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.
D34 · Knowledge Freshness
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.
What to do
- 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).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- 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).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
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.
What to do
- 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).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX2 · Stateful singletons
- `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 cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
- 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 & stubs
- `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)
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 documentation
- 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 structure
M4 · Documentation accuracy
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `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 guard
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- 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 types
- 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
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 60.3 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 71.2 | Adequate — gated by AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 52.6 | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 100.0 | Exemplary | Strongest area. |
| Security | 66.7 | Adequate — gated by D44 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 2 check(s) recorded observations but carry no score
- 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
- 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
- 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)
Critical — 5 finding(s)
- WriteOnlyPrivateField src/Leagueoflegends.Support/UI/Units/RiotHorizontalProgress.cs:25
- WriteOnlyPrivateField src/Leagueoflegends.Support/UI/Units/RiotVerticalProgress.cs:18
- REDACTED
- REDACTED
- EmptyCatchBlock src/Jamesnet.Platform.WPF/WPFLayer.cs:39
Serious — 182 finding(s)
- NuGet dependencies are not locked _backup/obsolate/Leagueoflegends/Leagueoflegends.csproj:15
- NuGet dependencies are not locked _backup/obsolate/Lol.Clash/Lol - Backup.Clash.csproj:9
- NuGet dependencies are not locked _backup/obsolate/Lol.Clash/Lol.Clash.csproj:9
- NuGet dependencies are not locked _backup/obsolate/Lol.Collection/Lol - Backup.Collection.csproj:19
- NuGet dependencies are not locked _backup/obsolate/Lol.Collection/Lol.Collection.csproj:19
- NuGet dependencies are not locked _backup/obsolate/Lol.Controls/Lol.Controls.csproj:9
- NuGet dependencies are not locked _backup/obsolate/Lol.Converter/Lol.Converter.csproj:24
- NuGet dependencies are not locked _backup/obsolate/Lol.Data/Lol.Data.csproj:16
- NuGet dependencies are not locked _backup/obsolate/Lol.Database/Lol.Database.csproj:10
- NuGet dependencies are not locked _backup/obsolate/Lol.Devices/Lol - Backup.Devices.csproj:7
- NuGet dependencies are not locked _backup/obsolate/Lol.Devices/Lol.Devices.csproj:7
- NuGet dependencies are not locked _backup/obsolate/Lol.ExampleData/Lol.ExampleData.csproj:9
- NuGet dependencies are not locked _backup/obsolate/Lol.Forms/Lol.Forms.csproj:10
- NuGet dependencies are not locked _backup/obsolate/Lol.Foundation/Lol.Foundation.csproj:20
- NuGet dependencies are not locked _backup/obsolate/Lol.Friends/Lol - Backup.Friends.csproj:9
- NuGet dependencies are not locked _backup/obsolate/Lol.Friends/Lol.Friends.csproj:9
- NuGet dependencies are not locked _backup/obsolate/Lol.GameRoom/Lol - Backup.GameRoom.csproj:9
- NuGet dependencies are not locked _backup/obsolate/Lol.GameRoom/Lol.GameRoom.csproj:9
- NuGet dependencies are not locked _backup/obsolate/Lol.Home/Lol.Home.csproj:9
- NuGet dependencies are not locked _backup/obsolate/Lol.LayoutSupport/Lol.LayoutSupport.csproj:9
- NuGet dependencies are not locked _backup/obsolate/Lol.Loot/Lol.Loot.csproj:10
- NuGet dependencies are not locked _backup/obsolate/Lol.Main/Lol.Main.csproj:10
- NuGet dependencies are not locked _backup/obsolate/Lol.Menus/Lol.Menus.csproj:14
- NuGet dependencies are not locked _backup/obsolate/Lol.MyShop/Lol.MyShop.csproj:9
- NuGet dependencies are not locked _backup/obsolate/Lol.Profile/Lol.Profile.csproj:15
- End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.Controls/Lol.Controls.csproj:4
- End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.Converter/Lol.Converter.csproj:4
- End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.DBEntity/Lol.DBEntity.csproj:4
- End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.ExampleData/Lol.ExampleData.csproj:4
- End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.LayoutSupport/Lol.LayoutSupport.csproj:4
- End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.Resources/Lol - Backup.Resources.csproj:4
- End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.Settings/Lol - Backup.Settings.csproj:4
- End-of-life runtime: .NET net6.0 _backup/obsolate/Lol.Store/Lol - Backup.Store.csproj:4
- End-of-life runtime: .NET net6.0 _backup/obsolate/PreviewDesign/PreviewDesign.csproj:4
- End-of-life runtime: .NET net7.0 _backup/obsolate/Leagueoflegends/Leagueoflegends.csproj:4
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Clash/Lol - Backup.Clash.csproj:4
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Clash/Lol.Clash.csproj:4
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Collection/Lol - Backup.Collection.csproj:5
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Collection/Lol.Collection.csproj:5
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Data/Lol.Data.csproj:4
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Database/Lol.Database.csproj:4
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Devices/Lol - Backup.Devices.csproj:3
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Devices/Lol.Devices.csproj:3
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Forms/Lol.Forms.csproj:4
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Foundation/Lol.Foundation.csproj:3
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Friends/Lol - Backup.Friends.csproj:4
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Friends/Lol.Friends.csproj:4
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.GameRoom/Lol - Backup.GameRoom.csproj:4
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.GameRoom/Lol.GameRoom.csproj:4
- End-of-life runtime: .NET net7.0 _backup/obsolate/Lol.Home/Lol.Home.csproj:4
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/BooleanToInverseConverter.cs:17
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/BooleanToVisibilityConverter.cs:13
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/BoolToPlayStopConverter.cs:13
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/ChampionNameToThumbnailConverter.cs:19
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/ConceptToImageConverter.cs:16
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/CooldownConverter.cs:16
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/DiscountRateConverter.cs:16
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/FromNullToValueConverter.cs:17
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/IconTypeToStatusIndicatorConverter.cs:25
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/ItemNameToImageConverter.cs:52
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/MatchResultToColorConverter.cs:22
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/MenuIconToGeometryConverter.cs:26
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/NumberFormatConverter.cs:16
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/PercentToBadgeConverter.cs:18
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/ScheduleDateConverter.cs:17
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/ScheduleDayConverter.cs:16
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/SpellNameToImageConverter.cs:20
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/SummonerLevelConverter.cs:17
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Support/Local/Converters/UserToThumbnailConverter.cs:12
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Clash/Local/Converters/ShowMenuConverter.cs:15
- Unfinished stub — throws NotImplementedException src/Leagueoflegends.Settings/Local/Converters/InputModeToVisibilityConverter.cs:22
- TodoComment _backup/obsolate/Lol.Clash/UI/Units/PositionButton.cs:22
- TodoComment _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:69
- TodoComment _backup/obsolate/Lol.Collection/Local/ViewModel/SpellsViewModel.cs:35
- TodoComment _backup/obsolate/Lol.Database/Collection/FriendsCollection.cs:5
- TodoComment _backup/obsolate/Lol.Database/Controller/SpellApi.cs:29
- TodoComment _backup/obsolate/Lol.Database/Controller/StoreApi.cs:7
- TodoComment _backup/obsolate/Lol.Database/Controller/StoreApi.cs:12
- TodoComment _backup/obsolate/Lol.Home/Local/ViewModels/AvatarViewModel.cs:15
- TodoComment _backup/obsolate/Lol.Settings.InGame/Local/ViewModels/ReplayViewModel.cs:42
- TodoComment _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:60
- TodoComment src/Leagueoflegends.Support/Themes/Units/RiotChampSummary.xaml:9
- TodoComment _backup/obsolate/Lol.Clash/Themes/Units/CupToggleButton.xaml:57
- TodoComment _backup/obsolate/Lol.Profile/Themes/Units/History/PlayedChampList.xaml:34
- TodoComment _backup/obsolate/Lol.GameRoom/Themes/Units/Summoners/UserDetail.xaml:17
- TodoComment _backup/obsolate/Lol.Profile/Themes/Units/History/RecentActivity.xaml:43
- Off the main sequence: Lol.Home _backup/obsolate/Lol.Home/Lol.Home.csproj:1
- Off the main sequence: Lol.MyShop _backup/obsolate/Lol.MyShop/Lol.MyShop.csproj:1
- Off the main sequence: Lol.Settings.About _backup/obsolate/Lol.Settings.About/Lol.Settings.About.csproj:1
- Off the main sequence: Lol.Support _backup/obsolate/Lol.Support/Lol.Support.csproj:1
- Off the main sequence: Lol.Database _backup/obsolate/Lol.Database/Lol.Database.csproj:1
- Off the main sequence: Lol.Data _backup/obsolate/Lol.Data/Lol.Data.csproj:1
- Off the main sequence: Lol.Foundation _backup/obsolate/Lol.Foundation/Lol.Foundation.csproj:1
- Off the main sequence: Leagueoflegends.Support src/Leagueoflegends.Support/Leagueoflegends.Support.csproj:1
- Duplicated block (6 lines × 2) _backup/obsolate/Lol.Database/Entites/Schema/History.cs:23
- Duplicated block (6 lines × 2) _backup/obsolate/Lol.Database/Controller/FriendsApi.cs:12
- Duplicated block (6 lines × 2) src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:78
- Duplicated block (6 lines × 2) src/Jamesnet.Core/AppBootstrapper.cs:11
- Duplicated block (6 lines × 2) src/Jamesnet.Core/StringExtensions.cs:9
- Edited copy of a member (7 corresponding lines) src/Jamesnet.Core/StringExtensions.cs:8
- Edited copy of a member (7 corresponding lines) src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:77
- Edited copy of a member (7 corresponding lines) src/Jamesnet.Core/AppBootstrapper.cs:10
- Edited copy of a member (7 corresponding lines) src/Leagueoflegends.Support/UI/Units/RiotHorizontalProgress.cs:34
- CommentedOutCode _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:74
- CommentedOutCode _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:62
- CommentedOutCode _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:86
- Edited copy of a member (8 corresponding lines) src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:86
- Edited copy of a member (8 corresponding lines) src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:38
- Edited copy of a member (8 corresponding lines) src/Jamesnet.Core/YamlConverter.cs:23
- Duplicated block (13 lines × 2) src/Jamesnet.Core/Container.cs:83
- Duplicated block (13 lines × 2) src/Jamesnet.Core/YamlItem.cs:8
- Duplicated block (13 lines × 2) src/Jamesnet.Core/YamlExtensions.cs:10
- Duplicated block (7 lines × 2) _backup/obsolate/Lol.Database/Entites/Schema/TeamFights.cs:5
- Duplicated block (7 lines × 2) src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:87
- Duplicated block (7 lines × 2) src/Jamesnet.Core/YamlConverter.cs:24
- Duplicated block (5 lines × 2) src/Jamesnet.Core/LayerManager.cs:6
- Duplicated block (5 lines × 2) src/Jamesnet.Core/AppBootstrapper.cs:20
- Duplicated block (5 lines × 2) src/Jamesnet.Core/BaseResourceLoader.cs:16
- Process-global static state: ContainerProvider src/Jamesnet.Core/ContainerProvider.cs:5
- Process-global static state: ContainerProvider src/Jamesnet.Foundation/ContainerProvider.cs:5
- Solution references a project that does not exist _backup/obsolate/Leagueoflegends.sln
- Solution references a project that does not exist src/leagueoflegends.WPF.sln
- Edited copy of a member (11 corresponding lines) src/Jamesnet.Core/DefaultViewModelInitializer.cs:30
- Edited copy of a member (11 corresponding lines) _backup/obsolate/Lol.Main/Local/ViewModels/MainContentViewModel.cs:58
- Edited copy of a member (9 corresponding lines) src/Leagueoflegends.Collection/Local/Datas/ChampStatsDataLoader.cs:15
- Edited copy of a member (9 corresponding lines) src/Jamesnet.Core/ViewModelBase.cs:18
- Edited copy of a member (6 corresponding lines) src/Jamesnet.Core/AppBootstrapper.cs:19
- Edited copy of a member (6 corresponding lines) src/Jamesnet.Core/BaseResourceLoader.cs:15
- Edited copy of a member (4 corresponding lines) src/Jamesnet.Core/Container.cs:27
- Edited copy of a member (4 corresponding lines) src/Jamesnet.Core/Container.cs:33
- Duplicated block (10 lines × 2) src/Jamesnet.Core/DefaultViewModelInitializer.cs:33
- Duplicated block (10 lines × 2) src/Jamesnet.Core/Container.cs:65
- Duplicated block (8 lines × 2) src/Jamesnet.Core/ViewModelMapper.cs:11
- Duplicated block (8 lines × 2) src/Jamesnet.Core/ViewModelBase.cs:19
- Duplicated block (7 lines × 4) _backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.cs:72
- Duplicated block (7 lines × 4) _backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.cs:72
- Empty method body — does nothing with its inputs _backup/obsolate/Lol.Collection/Local/ViewModel/ChampionsViewModel.cs:131
- Empty method body — does nothing with its inputs _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:70
- Disposable created and abandoned in the method that made it _backup/obsolate/Lol.Settings.InGame/Local/ViewModels/ReplayViewModel.cs:43
- Disposable created and abandoned in the method that made it _backup/obsolate/Lol.Devices/Audio/AudioDeviceInfo.cs:12
- ClassTooLong: LolDataPack _backup/obsolate/Lol.Database/Entites/Statics/LolDataPack.cs
- Members sharing a duplicated core (6 members, 50+ identical tokens) src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs:14
- Edited copies of one member (4 members, 14+ corresponding lines) _backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.cs:103
- Edited copy of a member (16 corresponding lines) src/Jamesnet.Core/LayerManager.cs:49
- Edited copy of a member (10 corresponding lines) src/Jamesnet.Core/DefaultViewModelInitializer.cs:18
- Duplicated block (29 lines × 2) src/Jamesnet.Core/YamlConverter.cs:34
- Duplicated block (16 lines × 2) _backup/obsolate/Lol.Database/Controller/ChampApi.cs:63
- Duplicated block (16 lines × 5) src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs:15
- Duplicated block (15 lines × 2) src/Jamesnet.Core/IContainer.cs:5
- Duplicated block (13 lines × 6) src/Leagueoflegends.Support/UI/Units/RiotHorizMenuListBox.cs:15
- Duplicated block (12 lines × 2) src/Jamesnet.Core/LayerManager.cs:14
- Duplicated block (45 lines × 2) src/Jamesnet.Core/RelayCommand.cs:17
- Unstable project Lol.Main _backup/obsolate/Lol.Main/Lol.Main.csproj:1
- Swallowed exception (empty catch) src/Jamesnet.Platform.WPF/WPFLayer.cs:39
Minor — 155 finding(s)
- redundant comment _backup/obsolate/Leagueoflegends/Properties/AssemblyInfo.cs:4
- redundant comment _backup/obsolate/Leagueoflegends/Properties/AssemblyInfo.cs:5
- redundant comment _backup/obsolate/Leagueoflegends/Properties/AssemblyInfo.cs:7
- redundant comment _backup/obsolate/Leagueoflegends/Properties/AssemblyInfo.cs:8
- redundant comment _backup/obsolate/Lol.Clash/Properties/AssemblyInfo.cs:11
- redundant comment _backup/obsolate/Lol.Clash/Properties/AssemblyInfo.cs:17
- redundant comment _backup/obsolate/Lol.Friends/Properties/AssemblyInfo.cs:11
- redundant comment _backup/obsolate/Lol.Friends/Properties/AssemblyInfo.cs:17
- redundant comment _backup/obsolate/Lol.GameRoom/Properties/AssemblyInfo.cs:4
- redundant comment _backup/obsolate/Lol.GameRoom/Properties/AssemblyInfo.cs:5
- redundant comment _backup/obsolate/Lol.GameRoom/Properties/AssemblyInfo.cs:7
- redundant comment _backup/obsolate/Lol.GameRoom/Properties/AssemblyInfo.cs:8
- redundant comment _backup/obsolate/Lol.Home/Properties/AssemblyInfo.cs:11
- redundant comment _backup/obsolate/Lol.Home/Properties/AssemblyInfo.cs:17
- redundant comment _backup/obsolate/Lol.LayoutSupport/Properties/AssemblyInfo.cs:11
- redundant comment _backup/obsolate/Lol.LayoutSupport/Properties/AssemblyInfo.cs:17
- redundant comment _backup/obsolate/Lol.Loot/Properties/AssemblyInfo.cs:4
- redundant comment _backup/obsolate/Lol.Loot/Properties/AssemblyInfo.cs:5
- redundant comment _backup/obsolate/Lol.Loot/Properties/AssemblyInfo.cs:7
- redundant comment _backup/obsolate/Lol.Loot/Properties/AssemblyInfo.cs:8
- redundant comment _backup/obsolate/Lol.Main/Properties/AssemblyInfo.cs:11
- redundant comment _backup/obsolate/Lol.Main/Properties/AssemblyInfo.cs:17
- redundant comment _backup/obsolate/Lol.Menus/Properties/AssemblyInfo.cs:4
- redundant comment _backup/obsolate/Lol.Menus/Properties/AssemblyInfo.cs:5
- redundant comment _backup/obsolate/Lol.Menus/Properties/AssemblyInfo.cs:7
- Orphaned file _backup/obsolate/Lol.Menus/Local/ViewModels/MenuContentViewModel.cs:1
- Orphaned file src/Leagueoflegends/LeagueoflegendsBootstrapper.cs:1
- Orphaned file _backup/obsolate/Lol.Database/Controller/StoreApi.cs:1
- Orphaned file src/Jamesnet.Foundation/Container.cs:1
- Orphaned file _backup/obsolate/Leagueoflegends/Properties/ViewModules.cs:1
- Orphaned file _backup/obsolate/Lol.Support/Local/Helpers/MenuService.cs:1
- Orphaned file src/Jamesnet.Foundation/LayerManager.cs:1
- Orphaned file _backup/obsolate/Lol.Collection/Local/ViewModel/ChampionsViewModel.cs:1
- Orphaned file _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:1
- Orphaned file _backup/obsolate/Lol.Store/Local/ViewModels/ChampionsViewModel.cs:1
- Orphaned file _backup/obsolate/Leagueoflegends/Properties/WireDataContext.cs:1
- Orphaned file src/Jamesnet.Platform.WPF/RecursiveControl.cs:1
- Orphaned file _backup/obsolate/Lol.Store/Local/ViewModels/TFTViewModel.cs:1
- Orphaned file _backup/obsolate/Lol.Store/Local/ViewModels/EtcViewModel.cs:1
- Orphaned file _backup/obsolate/Lol.Store/Local/ViewModels/SkinViewModel.cs:1
- Orphaned file _backup/obsolate/Lol.Database/Controller/ChampApi.cs:1
- Orphaned file _backup/obsolate/Lol.GameRoom/Local/ViewModels/CreateCustomViewModel.cs:1
- Orphaned file src/Jamesnet.Core/Container.cs:1
- Orphaned file _backup/obsolate/Lol.Data/Setting/InGame/InterfaceModel.cs:1
- Orphaned file _backup/obsolate/Lol.Clash/Local/ViewModel/WinnersViewModel.cs:1
- Orphaned file _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:1
- Orphaned file _backup/obsolate/Lol.Database/Controller/HistoryApi.cs:1
- Orphaned file src/Leagueoflegends.Navigate/Local/Services/MenuManager.cs:1
- Orphaned file _backup/obsolate/Lol.Main/Local/ViewModels/MainContentViewModel.cs:1
- Orphaned file src/Leagueoflegends.Collection/Local/ViewModels/ChampionsContentViewModel.cs:1
- Commented-out code _backup/obsolate/Lol.Collection/Local/ViewModel/ChampionsViewModel.cs:137
- Commented-out code _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:72
- Commented-out code _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:84
- Commented-out code _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:88
- Commented-out code _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:91
- Commented-out code _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:93
- Commented-out code _backup/obsolate/Lol.Collection/Local/ViewModel/ItemViewModel.cs:100
- Commented-out code _backup/obsolate/Lol.Database/Controller/SpellApi.cs:30
- Commented-out code _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:62
- Commented-out code _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:63
- Commented-out code _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:64
- Commented-out code _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:65
- Commented-out code _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:66
- Commented-out code _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:67
- Commented-out code _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:68
- Commented-out code _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:69
- Commented-out code _backup/obsolate/Lol.Settings/Local/ViewModel/SettingViewModel.cs:70
- Shell project: Lol.Converter _backup/obsolate/Lol.Converter/Lol.Converter.csproj
- Shell project: Lol.DBEntity _backup/obsolate/Lol.DBEntity/Lol.DBEntity.csproj
- Shell project: Lol.ExampleData _backup/obsolate/Lol.ExampleData/Lol.ExampleData.csproj
- Shell project: Lol.LayoutSupport _backup/obsolate/Lol.LayoutSupport/Lol.LayoutSupport.csproj
- Duplicated predicate src/Jamesnet.Core/YamlConverter.cs:35
- Duplicated predicate src/Jamesnet.Core/Container.cs:88
- Duplicated predicate src/Jamesnet.Core/RelayCommand.cs:21
- Duplicated predicate src/Leagueoflegends.Support/Local/Converters/ChampionNameToThumbnailConverter.cs:12
- Thin analysable surface across projects: Lol - Backup.Devices _backup/obsolate/Lol.Devices/Lol - Backup.Devices.csproj
- Thin analysable surface across projects: PreviewDesign _backup/obsolate/PreviewDesign/PreviewDesign.csproj
- REDACTED
- Dormant codebase
- Most significant orphaned file _backup/obsolate/Lol.Database/Entites/Statics/LolDataPack.cs:1
- No tests — template/sample
- Empty method body src/Leagueoflegends.Social/Local/ViewModels/SocialContentViewModel.cs:23
- No ADRs
- Nullable reference types not enabled everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw 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 . | 0 | artifacts/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 . | 0 | artifacts/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 . | 0 | artifacts/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 . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 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 & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-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-30db1ac04f9344538518b4666055ac84 | 0 | artifacts/raw/osv-scanner.json |