Executive summary
BeatLeader/beatleader-mod has a provisional result, because the code didn't build. Its score is held back in part because we found no access checks on the code's endpoints or handlers. It scores 35.2 out of 100, and the ratings may change once the code builds. 11 of its 44 critical findings are security problems. We judged it as a preview release, against a lower bar.
Security and Compliance, at 26.3, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 7.8 points. Fixing the eight comments that repeat the code, or contradict it comes next, worth about 2.4 points. Raising Security and Compliance to 68 would lift the score to about 43.4.
Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline, and six errors are caught and ignored, so failures can go unnoticed. Pinning each tool to an exact version, limiting each secret to its own step and handling or logging the ignored errors would close these risks. Fixing the weaknesses the scanner points to would fix the two security weaknesses in the code, and updating the vulnerable packages would deal with the package with a known security hole. The 14 analysis rules switched off in the settings need switching back on in the settings file.
The product code is 42,862 lines, about €51,000 to rebuild.
If Security and Compliance rose from 26.3 to 68, the lowest score rated Strong, the score would rise from 35.2 to about 43.4.
Rebuild cost: about €51,000 · Estimate
| Cost to rebuild | €17,000 to €85,000, for 280 to 890 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the 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.7 at a score of 35. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 42,862 lines of product code, of which 36% is declarations and boilerplate, 38% straight logic and 26% logic with branches |
| Comment lines | The estimate prices 42,066 lines. Comment lines count towards the size of 42,862 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: which parts of the code depend on which
| uses → | 1 B83.Image.GIF | 2 BeatLeader.Attributes | 3 BeatLeader.BeatSaverAPI | 4 BeatLeader.Models.BeatSaver | 5 BeatLeader.SteamVR | 6 BeatLeader.UI.Reactive | 7 BeatLeader.UI.Reactive.Components | 8 BeatLeader.UI.Rendering | 9 System.Runtime.CompilerServices | 10 BeatLeader.Models.AbstractReplay | 11 BeatLeader.Models.Replay | 12 BeatLeader.Themes | 13 BeatLeader.UI | 14 BeatLeader.Core.Managers.NoteEnhancer | 15 BeatLeader.Core.Managers.ReplayEnhancer | 16 BeatLeader.Replayer | 17 BeatLeader.UI.Replayer | 18 BeatLeader.Models | 19 BeatLeader.Installers | 20 BeatLeader.Replayer.Emulation | 21 BeatLeader.Results | 22 BeatLeader.UI.Replayer.Desktop | 23 BeatLeader.WebRequests | 24 BeatLeader.DataManager | 25 BeatLeader.Replayer.Binding | 26 BeatLeader.UI.Hub | 27 BeatLeader.UI.MainMenu | 28 BeatLeader.Manager | 29 BeatLeader.Components | 30 BeatLeader.ViewControllers | 31 BeatLeader | 32 BeatLeader.UIPatches | 33 BeatLeader.API | 34 BeatLeader.Interop | 35 BeatLeader.Replayer.Tweaking | 36 BeatLeader.Utils |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 B83.Image.GIF | ||||||||||||||||||||||||||||||||||||
| 2 BeatLeader.Attributes | ||||||||||||||||||||||||||||||||||||
| 3 BeatLeader.BeatSaverAPI | ||||||||||||||||||||||||||||||||||||
| 4 BeatLeader.Models.BeatSaver | ||||||||||||||||||||||||||||||||||||
| 5 BeatLeader.SteamVR | ||||||||||||||||||||||||||||||||||||
| 6 BeatLeader.UI.Reactive | ||||||||||||||||||||||||||||||||||||
| 7 BeatLeader.UI.Reactive.Components | ||||||||||||||||||||||||||||||||||||
| 8 BeatLeader.UI.Rendering | ||||||||||||||||||||||||||||||||||||
| 9 System.Runtime.CompilerServices | ||||||||||||||||||||||||||||||||||||
| 10 BeatLeader.Models.AbstractReplay | 3 | |||||||||||||||||||||||||||||||||||
| 11 BeatLeader.Models.Replay | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 12 BeatLeader.Themes | 1 | |||||||||||||||||||||||||||||||||||
| 13 BeatLeader.UI | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 14 BeatLeader.Core.Managers.NoteEnhancer | 1 | |||||||||||||||||||||||||||||||||||
| 15 BeatLeader.Core.Managers.ReplayEnhancer | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 16 BeatLeader.Replayer | 7 | 3 | 37 | 5 | ||||||||||||||||||||||||||||||||
| 17 BeatLeader.UI.Replayer | 1 | 7 | 6 | 4 | 67 | 10 | ||||||||||||||||||||||||||||||
| 18 BeatLeader.Models | 1 | 10 | 4 | 4 | 1 | 1 | 4 | |||||||||||||||||||||||||||||
| 19 BeatLeader.Installers | 3 | |||||||||||||||||||||||||||||||||||
| 20 BeatLeader.Replayer.Emulation | 18 | 1 | 46 | 8 | ||||||||||||||||||||||||||||||||
| 21 BeatLeader.Results | 1 | |||||||||||||||||||||||||||||||||||
| 22 BeatLeader.UI.Replayer.Desktop | 4 | 7 | ||||||||||||||||||||||||||||||||||
| 23 BeatLeader.WebRequests | 2 | |||||||||||||||||||||||||||||||||||
| 24 BeatLeader.DataManager | 35 | 18 | 2 | |||||||||||||||||||||||||||||||||
| 25 BeatLeader.Replayer.Binding | 8 | 1 | ||||||||||||||||||||||||||||||||||
| 26 BeatLeader.UI.Hub | 2 | 5 | 2 | 1 | 2 | 3 | 57 | 4 | 11 | 19 | ||||||||||||||||||||||||||
| 27 BeatLeader.UI.MainMenu | 20 | 8 | 3 | |||||||||||||||||||||||||||||||||
| 28 BeatLeader.Manager | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 29 BeatLeader.Components | 2 | 3 | 2 | 70 | 33 | 3 | 1 | 1 | 73 | |||||||||||||||||||||||||||
| 30 BeatLeader.ViewControllers | 3 | 1 | 1 | 17 | 3 | |||||||||||||||||||||||||||||||
| 31 BeatLeader | 11 | 1 | 1 | 2 | 48 | 4 | 1 | 2 | 3 | |||||||||||||||||||||||||||
| 32 BeatLeader.UIPatches | 1 | |||||||||||||||||||||||||||||||||||
| 33 BeatLeader.API | 1 | 3 | 16 | 62 | 4 | |||||||||||||||||||||||||||||||
| 34 BeatLeader.Interop | 6 | 1 | 6 | |||||||||||||||||||||||||||||||||
| 35 BeatLeader.Replayer.Tweaking | 10 | 11 | ||||||||||||||||||||||||||||||||||
| 36 BeatLeader.Utils | 1 | 8 | 10 | 21 | 2 |
10→18 BeatLeader.Models.AbstractReplay uses BeatLeader.Models part of a loop✕
- Connections
- 3 pairs of types, where a type in BeatLeader.Models.AbstractReplay uses a type in BeatLeader.Models.
- The types involved
BeatLeader.Models.AbstractReplay.GenericReplayData→BeatLeader.Models.IPlayerBeatLeader.Models.AbstractReplay.IReplayData→BeatLeader.Models.IPlayerBeatLeader.Models.AbstractReplay.PlayerMovementFrame→BeatLeader.Models.SerializablePose
- Direction
- BeatLeader.Models.AbstractReplay uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Models.AbstractReplay, while a change to BeatLeader.Models.AbstractReplay can't break BeatLeader.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→18 BeatLeader.Models.Replay uses BeatLeader.Models part of a loop✕
- Connections
- 2 pairs of types, where a type in BeatLeader.Models.Replay uses a type in BeatLeader.Models.
- The types involved
BeatLeader.Models.Replay.ReplayInfo→BeatLeader.Models.IReplayInfoBeatLeader.Models.Replay.ReplayInfo→BeatLeader.Models.LevelEndType
- Direction
- BeatLeader.Models.Replay uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Models.Replay, while a change to BeatLeader.Models.Replay can't break BeatLeader.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→31 BeatLeader.Models.Replay uses BeatLeader part of a loop✕
- Connections
- 1 pair of types, where a type in BeatLeader.Models.Replay uses a type in BeatLeader.
- The types involved
BeatLeader.Models.Replay.StreamReplayDecoder→BeatLeader.UnmanagedFileReader
- Direction
- BeatLeader.Models.Replay uses BeatLeader, so a change to BeatLeader can break BeatLeader.Models.Replay, while a change to BeatLeader.Models.Replay can't break BeatLeader.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→18 BeatLeader.Themes uses BeatLeader.Models part of a loop✕
- Connections
- 1 pair of types, where a type in BeatLeader.Themes uses a type in BeatLeader.Models.
- The types involved
BeatLeader.Themes.ThemesUtils→BeatLeader.Models.IPlayerProfileSettings
- Direction
- BeatLeader.Themes uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Themes, while a change to BeatLeader.Themes can't break BeatLeader.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→18 BeatLeader.UI uses BeatLeader.Models part of a loop✕
- Connections
- 1 pair of types, where a type in BeatLeader.UI uses a type in BeatLeader.Models.
- The types involved
BeatLeader.UI.QuickMiniProfile→BeatLeader.Models.IPlayer
- Direction
- BeatLeader.UI uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.UI, while a change to BeatLeader.UI can't break BeatLeader.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→29 BeatLeader.UI uses BeatLeader.Components part of a loop✕
- Connections
- 2 pairs of types, where a type in BeatLeader.UI uses a type in BeatLeader.Components.
- The types involved
BeatLeader.UI.QuickMiniProfile→BeatLeader.Components.CountryFlagBeatLeader.UI.QuickMiniProfile→BeatLeader.Components.PlayerAvatar
- Direction
- BeatLeader.UI uses BeatLeader.Components, so a change to BeatLeader.Components can break BeatLeader.UI, while a change to BeatLeader.UI can't break BeatLeader.Components.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→11 BeatLeader.Core.Managers.NoteEnhancer uses BeatLeader.Models.Replay✕
- Connections
- 1 pair of types, where a type in BeatLeader.Core.Managers.NoteEnhancer uses a type in BeatLeader.Models.Replay.
- The types involved
BeatLeader.Core.Managers.NoteEnhancer.SwingRatingEnhancer→BeatLeader.Models.Replay.NoteCutInfo
- Direction
- BeatLeader.Core.Managers.NoteEnhancer uses BeatLeader.Models.Replay, so a change to BeatLeader.Models.Replay can break BeatLeader.Core.Managers.NoteEnhancer, while a change to BeatLeader.Core.Managers.NoteEnhancer can't break BeatLeader.Models.Replay.
- Position
- Below the diagonal: BeatLeader.Core.Managers.NoteEnhancer uses a module listed above it, which is the healthy direction.
15→5 BeatLeader.Core.Managers.ReplayEnhancer uses BeatLeader.SteamVR✕
- Connections
- 1 pair of types, where a type in BeatLeader.Core.Managers.ReplayEnhancer uses a type in BeatLeader.SteamVR.
- The types involved
BeatLeader.Core.Managers.ReplayEnhancer.TrackingDeviceEnhancer→BeatLeader.SteamVR.Headset
- Direction
- BeatLeader.Core.Managers.ReplayEnhancer uses BeatLeader.SteamVR, so a change to BeatLeader.SteamVR can break BeatLeader.Core.Managers.ReplayEnhancer, while a change to BeatLeader.Core.Managers.ReplayEnhancer can't break BeatLeader.SteamVR.
- Position
- Below the diagonal: BeatLeader.Core.Managers.ReplayEnhancer uses a module listed above it, which is the healthy direction.
15→11 BeatLeader.Core.Managers.ReplayEnhancer uses BeatLeader.Models.Replay✕
- Connections
- 3 pairs of types, where a type in BeatLeader.Core.Managers.ReplayEnhancer uses a type in BeatLeader.Models.Replay.
- The types involved
BeatLeader.Core.Managers.ReplayEnhancer.MapEnhancer→BeatLeader.Models.Replay.ReplayBeatLeader.Core.Managers.ReplayEnhancer.TrackingDeviceEnhancer→BeatLeader.Models.Replay.ReplayBeatLeader.Core.Managers.ReplayEnhancer.UserEnhancer→BeatLeader.Models.Replay.Replay
- Direction
- BeatLeader.Core.Managers.ReplayEnhancer uses BeatLeader.Models.Replay, so a change to BeatLeader.Models.Replay can break BeatLeader.Core.Managers.ReplayEnhancer, while a change to BeatLeader.Core.Managers.ReplayEnhancer can't break BeatLeader.Models.Replay.
- Position
- Below the diagonal: BeatLeader.Core.Managers.ReplayEnhancer uses a module listed above it, which is the healthy direction.
16→10 BeatLeader.Replayer uses BeatLeader.Models.AbstractReplay✕
- Connections
- 7 pairs of types, where a type in BeatLeader.Replayer uses a type in BeatLeader.Models.AbstractReplay.
- The types involved
BeatLeader.Replayer.BeatmapVisualsController→BeatLeader.Models.AbstractReplay.IReplayNoteComparatorBeatLeader.Replayer.BeatmapVisualsController→BeatLeader.Models.AbstractReplay.NoteEventBeatLeader.Replayer.PlayerViewCameraView→BeatLeader.Models.AbstractReplay.IReplayBeatLeader.Replayer.ReplayBeatmapData→BeatLeader.Models.AbstractReplay.IReplayNoteComparatorBeatLeader.Replayer.ReplayBeatmapData→BeatLeader.Models.AbstractReplay.NoteEventBeatLeader.Replayer.ReplayData→BeatLeader.Models.AbstractReplay.BattleRoyaleReplayDataBeatLeader.Replayer.ReplayerMenuLoader→BeatLeader.Models.AbstractReplay.BattleRoyaleReplayData
- Direction
- BeatLeader.Replayer uses BeatLeader.Models.AbstractReplay, so a change to BeatLeader.Models.AbstractReplay can break BeatLeader.Replayer, while a change to BeatLeader.Replayer can't break BeatLeader.Models.AbstractReplay.
- Position
- Below the diagonal: BeatLeader.Replayer uses a module listed above it, which is the healthy direction.
16→11 BeatLeader.Replayer uses BeatLeader.Models.Replay✕
- Connections
- 3 pairs of types, where a type in BeatLeader.Replayer uses a type in BeatLeader.Models.Replay.
- The types involved
BeatLeader.Replayer.ReplayData→BeatLeader.Models.Replay.ReplayBeatLeader.Replayer.ReplayerMenuLoader→BeatLeader.Models.Replay.ReplayBeatLeader.Replayer.ReplayerMenuLoader→BeatLeader.Models.Replay.ReplayInfo
- Direction
- BeatLeader.Replayer uses BeatLeader.Models.Replay, so a change to BeatLeader.Models.Replay can break BeatLeader.Replayer, while a change to BeatLeader.Replayer can't break BeatLeader.Models.Replay.
- Position
- Below the diagonal: BeatLeader.Replayer uses a module listed above it, which is the healthy direction.
16→18 BeatLeader.Replayer uses BeatLeader.Models part of a loop✕
- Connections
- 37 pairs of types, where a type in BeatLeader.Replayer uses a type in BeatLeader.Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BeatLeader.Replayer.BeatmapTimeController→BeatLeader.Models.IBeatmapTimeControllerBeatLeader.Replayer.BeatmapVisualsController→BeatLeader.Models.IBeatmapTimeControllerBeatLeader.Replayer.BeatmapVisualsController→BeatLeader.Models.IReplayBeatmapEventsProcessorBeatLeader.Replayer.BeatmapVisualsController→BeatLeader.Models.IReplayPauseControllerBeatLeader.Replayer.FlyingCameraView→BeatLeader.Models.CameraViewBeatLeader.Replayer.FlyingCameraView→BeatLeader.Models.SerializableVector2BeatLeader.Replayer.FlyingCameraView→BeatLeader.Models.SerializableVector3BeatLeader.Replayer.ManualCameraView→BeatLeader.Models.CameraViewBeatLeader.Replayer.ManualCameraView→BeatLeader.Models.SerializableVector3BeatLeader.Replayer.PlayerViewCameraView→BeatLeader.Models.CameraViewBeatLeader.Replayer.PlayerViewCameraView→BeatLeader.Models.IVirtualPlayerBodySpawnerBeatLeader.Replayer.PlayerViewCameraView→BeatLeader.Models.IVirtualPlayersManagerBeatLeader.Replayer.PlayerViewCameraView→BeatLeader.Models.SerializableVector3BeatLeader.Replayer.ReplayBeatmapData→BeatLeader.Models.IReplayBeatmapDataBeatLeader.Replayer.ReplayData→BeatLeader.Models.IPlayerBeatLeader.Replayer.ReplayFinishController→BeatLeader.Models.IReplayFinishControllerBeatLeader.Replayer.ReplayFinishController→BeatLeader.Models.IReplayTimeControllerBeatLeader.Replayer.ReplayFinishController→BeatLeader.Models.ReplayLaunchDataBeatLeader.Replayer.ReplayPauseController→BeatLeader.Models.IReplayPauseControllerBeatLeader.Replayer.ReplayTimeController→BeatLeader.Models.IReplayTimeControllerBeatLeader.Replayer.ReplayTimeController→BeatLeader.Models.ReplayLaunchDataBeatLeader.Replayer.ReplayerCameraController→BeatLeader.Models.ICameraControllerBeatLeader.Replayer.ReplayerCameraController→BeatLeader.Models.ICameraViewBeatLeader.Replayer.ReplayerCameraController→BeatLeader.Models.IVirtualPlayerBeatLeader.Replayer.ReplayerCameraController→BeatLeader.Models.IVirtualPlayersManager
- Direction
- BeatLeader.Replayer uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Replayer, while a change to BeatLeader.Replayer can't break BeatLeader.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→31 BeatLeader.Replayer uses BeatLeader part of a loop✕
- Connections
- 5 pairs of types, where a type in BeatLeader.Replayer uses a type in BeatLeader.
- The types involved
BeatLeader.Replayer.BeatmapTimeController→BeatLeader.HarmonyAutoPatchBeatLeader.Replayer.BeatmapTimeController→BeatLeader.HarmonySilencerBeatLeader.Replayer.BeatmapVisualsController→BeatLeader.HarmonySilencerBeatLeader.Replayer.ReplayPauseController→BeatLeader.HarmonyAutoPatchBeatLeader.Replayer.ReplayPauseController→BeatLeader.HarmonyPatchDescriptor
- Direction
- BeatLeader.Replayer uses BeatLeader, so a change to BeatLeader can break BeatLeader.Replayer, while a change to BeatLeader.Replayer can't break BeatLeader.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→6 BeatLeader.UI.Replayer uses BeatLeader.UI.Reactive✕
- Connections
- 1 pair of types, where a type in BeatLeader.UI.Replayer uses a type in BeatLeader.UI.Reactive.
- The types involved
BeatLeader.UI.Replayer.ReplayerFloatingPanelResetController→BeatLeader.UI.Reactive.ValueAnimator
- Direction
- BeatLeader.UI.Replayer uses BeatLeader.UI.Reactive, so a change to BeatLeader.UI.Reactive can break BeatLeader.UI.Replayer, while a change to BeatLeader.UI.Replayer can't break BeatLeader.UI.Reactive.
- Position
- Below the diagonal: BeatLeader.UI.Replayer uses a module listed above it, which is the healthy direction.
17→10 BeatLeader.UI.Replayer uses BeatLeader.Models.AbstractReplay✕
- Connections
- 7 pairs of types, where a type in BeatLeader.UI.Replayer uses a type in BeatLeader.Models.AbstractReplay.
- The types involved
BeatLeader.UI.Replayer.MarkerData→BeatLeader.Models.AbstractReplay.IReplayBeatLeader.UI.Replayer.PlayerListCell→BeatLeader.Models.AbstractReplay.IReplayBeatLeader.UI.Replayer.PlayerListCell→BeatLeader.Models.AbstractReplay.IReplayNoteComparatorBeatLeader.UI.Replayer.PlayerListCell→BeatLeader.Models.AbstractReplay.NoteEventBeatLeader.UI.Replayer.PlayerListCell→BeatLeader.Models.AbstractReplay.ScoreEventBeatLeader.UI.Replayer.QuickReplayOverview→BeatLeader.Models.AbstractReplay.IReplayBeatLeader.UI.Replayer.QuickReplayOverview→BeatLeader.Models.AbstractReplay.ReplayFinishType
- Direction
- BeatLeader.UI.Replayer uses BeatLeader.Models.AbstractReplay, so a change to BeatLeader.Models.AbstractReplay can break BeatLeader.UI.Replayer, while a change to BeatLeader.UI.Replayer can't break BeatLeader.Models.AbstractReplay.
- Position
- Below the diagonal: BeatLeader.UI.Replayer uses a module listed above it, which is the healthy direction.
17→13 BeatLeader.UI.Replayer uses BeatLeader.UI✕
- Connections
- 6 pairs of types, where a type in BeatLeader.UI.Replayer uses a type in BeatLeader.UI.
- The types involved
BeatLeader.UI.Replayer.PlayerListCell→BeatLeader.UI.QuickMiniProfileBeatLeader.UI.Replayer.PlayerProfileEditorComponent→BeatLeader.UI.QuickMiniProfileBeatLeader.UI.Replayer.ReplayerFloatingPanelControls→BeatLeader.UI.FloatingHandleBeatLeader.UI.Replayer.ReplayerFloatingPanelControls→BeatLeader.UI.FloatingScreenBeatLeader.UI.Replayer.ReplayerFloatingPanelCurvatureSettings→BeatLeader.UI.FloatingScreenBeatLeader.UI.Replayer.ReplayerFloatingViewController→BeatLeader.UI.FloatingScreen
- Direction
- BeatLeader.UI.Replayer uses BeatLeader.UI, so a change to BeatLeader.UI can break BeatLeader.UI.Replayer, while a change to BeatLeader.UI.Replayer can't break BeatLeader.UI.
- Position
- Below the diagonal: BeatLeader.UI.Replayer uses a module listed above it, which is the healthy direction.
17→16 BeatLeader.UI.Replayer uses BeatLeader.Replayer✕
- Connections
- 4 pairs of types, where a type in BeatLeader.UI.Replayer uses a type in BeatLeader.Replayer.
- The types involved
BeatLeader.UI.Replayer.FlyingViewCameraParams→BeatLeader.Replayer.FlyingCameraViewBeatLeader.UI.Replayer.ManualViewCameraParams→BeatLeader.Replayer.ManualCameraViewBeatLeader.UI.Replayer.PlayerViewCameraParams→BeatLeader.Replayer.PlayerViewCameraViewBeatLeader.UI.Replayer.ReplayerUIBinder→BeatLeader.Replayer.ReplayerExtraObjectsProvider
- Direction
- BeatLeader.UI.Replayer uses BeatLeader.Replayer, so a change to BeatLeader.Replayer can break BeatLeader.UI.Replayer, while a change to BeatLeader.UI.Replayer can't break BeatLeader.Replayer.
- Position
- Below the diagonal: BeatLeader.UI.Replayer uses a module listed above it, which is the healthy direction.
17→18 BeatLeader.UI.Replayer uses BeatLeader.Models part of a loop✕
- Connections
- 67 pairs of types, where a type in BeatLeader.UI.Replayer uses a type in BeatLeader.Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BeatLeader.UI.Replayer.BasicAvatarSettingsView→BeatLeader.Models.BasicBodySettingsBeatLeader.UI.Replayer.BasicAvatarSettingsView→BeatLeader.Models.BattleRoyaleBodySettingsBeatLeader.UI.Replayer.BasicAvatarSettingsView→BeatLeader.Models.BodySettingsBeatLeader.UI.Replayer.BasicAvatarSettingsViewFactory→BeatLeader.Models.ReplayLaunchDataBeatLeader.UI.Replayer.CellComparator→BeatLeader.Models.IVirtualPlayerBeatLeader.UI.Replayer.FlyingViewCameraParams→BeatLeader.Models.ICameraViewBeatLeader.UI.Replayer.ICameraViewParams→BeatLeader.Models.ICameraViewBeatLeader.UI.Replayer.ManualViewCameraParams→BeatLeader.Models.ICameraViewBeatLeader.UI.Replayer.PlayerList→BeatLeader.Models.IBeatmapTimeControllerBeatLeader.UI.Replayer.PlayerList→BeatLeader.Models.IVirtualPlayerBeatLeader.UI.Replayer.PlayerList→BeatLeader.Models.IVirtualPlayersManagerBeatLeader.UI.Replayer.PlayerListCell→BeatLeader.Models.IBeatmapTimeControllerBeatLeader.UI.Replayer.PlayerListCell→BeatLeader.Models.IReplayBeatmapEventsProcessorBeatLeader.UI.Replayer.PlayerListCell→BeatLeader.Models.IReplayScoreEventsProcessorBeatLeader.UI.Replayer.PlayerListCell→BeatLeader.Models.IVirtualPlayerBeatLeader.UI.Replayer.PlayerProfileEditorComponent→BeatLeader.Models.IPlayerBeatLeader.UI.Replayer.PlayerViewCameraParams→BeatLeader.Models.ICameraViewBeatLeader.UI.Replayer.QuickSettingsPanel→BeatLeader.Models.IBeatmapTimeControllerBeatLeader.UI.Replayer.ReplayerFloatingPanelControls→BeatLeader.Models.ReplayerFloatingUISettingsBeatLeader.UI.Replayer.ReplayerFloatingPanelCurvatureSettings→BeatLeader.Models.ReplayerFloatingUISettingsBeatLeader.UI.Replayer.ReplayerFloatingViewController→BeatLeader.Models.ICameraControllerBeatLeader.UI.Replayer.ReplayerFloatingViewController→BeatLeader.Models.IReplayFinishControllerBeatLeader.UI.Replayer.ReplayerFloatingViewController→BeatLeader.Models.IReplayPauseControllerBeatLeader.UI.Replayer.ReplayerFloatingViewController→BeatLeader.Models.IReplayTimeControllerBeatLeader.UI.Replayer.ReplayerFloatingViewController→BeatLeader.Models.IVirtualPlayersManager
- Direction
- BeatLeader.UI.Replayer uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.UI.Replayer, while a change to BeatLeader.UI.Replayer can't break BeatLeader.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→29 BeatLeader.UI.Replayer uses BeatLeader.Components part of a loop✕
- Connections
- 10 pairs of types, where a type in BeatLeader.UI.Replayer uses a type in BeatLeader.Components.
- The types involved
BeatLeader.UI.Replayer.BeatmapLevelPreviewEditorComponent→BeatLeader.Components.LayoutEditorComponentBeatLeader.UI.Replayer.PlayerProfileEditorComponent→BeatLeader.Components.LayoutEditorComponentBeatLeader.UI.Replayer.ReplayerSettingsPanel→BeatLeader.Components.ILayoutEditorBeatLeader.UI.Replayer.ReplayerUIPanel→BeatLeader.Components.LayoutEditorBeatLeader.UI.Replayer.ReplayerUIPanel→BeatLeader.Components.LayoutEditorModeBeatLeader.UI.Replayer.ReplayerUIPanel→BeatLeader.Components.PlayerListEditorComponentBeatLeader.UI.Replayer.SettingsUIView→BeatLeader.Components.ILayoutEditorBeatLeader.UI.Replayer.ToolbarEditorComponent→BeatLeader.Components.ILayoutEditorBeatLeader.UI.Replayer.ToolbarEditorComponent→BeatLeader.Components.LayoutEditorComponentBeatLeader.UI.Replayer.ToolbarWithSettings→BeatLeader.Components.ILayoutEditor
- Direction
- BeatLeader.UI.Replayer uses BeatLeader.Components, so a change to BeatLeader.Components can break BeatLeader.UI.Replayer, while a change to BeatLeader.UI.Replayer can't break BeatLeader.Components.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→1 BeatLeader.Models uses B83.Image.GIF✕
- Connections
- 1 pair of types, where a type in BeatLeader.Models uses a type in B83.Image.GIF.
- The types involved
BeatLeader.Models.AvatarImage→B83.Image.GIF.GIFImage
- Direction
- BeatLeader.Models uses B83.Image.GIF, so a change to B83.Image.GIF can break BeatLeader.Models, while a change to BeatLeader.Models can't break B83.Image.GIF.
- Position
- Below the diagonal: BeatLeader.Models uses a module listed above it, which is the healthy direction.
18→10 BeatLeader.Models uses BeatLeader.Models.AbstractReplay✕
- Connections
- 10 pairs of types, where a type in BeatLeader.Models uses a type in BeatLeader.Models.AbstractReplay.
- The types involved
BeatLeader.Models.IBattleRoyaleReplay→BeatLeader.Models.AbstractReplay.BattleRoyaleReplayDataBeatLeader.Models.IReplayBeatmapData→BeatLeader.Models.AbstractReplay.IReplayNoteComparatorBeatLeader.Models.IReplayBeatmapData→BeatLeader.Models.AbstractReplay.NoteEventBeatLeader.Models.IReplayBeatmapEventsProcessor→BeatLeader.Models.AbstractReplay.IReplayNoteComparatorBeatLeader.Models.IReplayBeatmapEventsProcessor→BeatLeader.Models.AbstractReplay.NoteEventBeatLeader.Models.IReplayBeatmapEventsProcessor→BeatLeader.Models.AbstractReplay.WallEventBeatLeader.Models.IReplayScoreEventsProcessor→BeatLeader.Models.AbstractReplay.ScoreEventBeatLeader.Models.IVirtualPlayer→BeatLeader.Models.AbstractReplay.IReplayBeatLeader.Models.IVirtualPlayerMovementProcessor→BeatLeader.Models.AbstractReplay.PlayerMovementFrameBeatLeader.Models.ReplayLaunchData→BeatLeader.Models.AbstractReplay.IReplay
- Direction
- BeatLeader.Models uses BeatLeader.Models.AbstractReplay, so a change to BeatLeader.Models.AbstractReplay can break BeatLeader.Models, while a change to BeatLeader.Models can't break BeatLeader.Models.AbstractReplay.
- Position
- Below the diagonal: BeatLeader.Models uses a module listed above it, which is the healthy direction.
18→11 BeatLeader.Models uses BeatLeader.Models.Replay✕
- Connections
- 4 pairs of types, where a type in BeatLeader.Models uses a type in BeatLeader.Models.Replay.
- The types involved
BeatLeader.Models.IReplayHeader→BeatLeader.Models.Replay.ReplayBeatLeader.Models.PhysicalReplayHeader→BeatLeader.Models.Replay.ReplayBeatLeader.Models.TempReplayHeader→BeatLeader.Models.Replay.ReplayBeatLeader.Models.WinTracker→BeatLeader.Models.Replay.Vector3
- Direction
- BeatLeader.Models uses BeatLeader.Models.Replay, so a change to BeatLeader.Models.Replay can break BeatLeader.Models, while a change to BeatLeader.Models can't break BeatLeader.Models.Replay.
- Position
- Below the diagonal: BeatLeader.Models uses a module listed above it, which is the healthy direction.
18→12 BeatLeader.Models uses BeatLeader.Themes✕
- Connections
- 4 pairs of types, where a type in BeatLeader.Models uses a type in BeatLeader.Themes.
- The types involved
BeatLeader.Models.IPlayerProfileSettings→BeatLeader.Themes.ThemeTierBeatLeader.Models.IPlayerProfileSettings→BeatLeader.Themes.ThemeTypeBeatLeader.Models.ProfileSettings→BeatLeader.Themes.ThemeTierBeatLeader.Models.ProfileSettings→BeatLeader.Themes.ThemeType
- Direction
- BeatLeader.Models uses BeatLeader.Themes, so a change to BeatLeader.Themes can break BeatLeader.Models, while a change to BeatLeader.Models can't break BeatLeader.Themes.
- Position
- Below the diagonal: BeatLeader.Models uses a module listed above it, which is the healthy direction.
18→17 BeatLeader.Models uses BeatLeader.UI.Replayer✕
- Connections
- 1 pair of types, where a type in BeatLeader.Models uses a type in BeatLeader.UI.Replayer.
- The types involved
BeatLeader.Models.ReplayerBindings→BeatLeader.UI.Replayer.IBodySettingsViewFactory
- Direction
- BeatLeader.Models uses BeatLeader.UI.Replayer, so a change to BeatLeader.UI.Replayer can break BeatLeader.Models, while a change to BeatLeader.Models can't break BeatLeader.UI.Replayer.
- Position
- Below the diagonal: BeatLeader.Models uses a module listed above it, which is the healthy direction.
18→29 BeatLeader.Models uses BeatLeader.Components part of a loop✕
- Connections
- 1 pair of types, where a type in BeatLeader.Models uses a type in BeatLeader.Components.
- The types involved
BeatLeader.Models.LayoutEditorSettings→BeatLeader.Components.LayoutData
- Direction
- BeatLeader.Models uses BeatLeader.Components, so a change to BeatLeader.Components can break BeatLeader.Models, while a change to BeatLeader.Models can't break BeatLeader.Components.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→31 BeatLeader.Models uses BeatLeader part of a loop✕
- Connections
- 4 pairs of types, where a type in BeatLeader.Models uses a type in BeatLeader.
- The types involved
BeatLeader.Models.ClanPlayer→BeatLeader.IScoreRowContentBeatLeader.Models.ClanScore→BeatLeader.IScoreRowContentBeatLeader.Models.ReplayerBindings→BeatLeader.OptionalBeatLeader.Models.Score→BeatLeader.IScoreRowContent
- Direction
- BeatLeader.Models uses BeatLeader, so a change to BeatLeader can break BeatLeader.Models, while a change to BeatLeader.Models can't break BeatLeader.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→18 BeatLeader.Installers uses BeatLeader.Models✕
- Connections
- 3 pairs of types, where a type in BeatLeader.Installers uses a type in BeatLeader.Models.
- The types involved
BeatLeader.Installers.OnGameplayCoreInstaller→BeatLeader.Models.LazyBindingBeatLeader.Installers.OnGameplayCoreInstaller→BeatLeader.Models.ReplayLaunchDataBeatLeader.Installers.OnGameplayCoreInstaller→BeatLeader.Models.ReplayerBindings
- Direction
- BeatLeader.Installers uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Installers, while a change to BeatLeader.Installers can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.Installers uses a module listed above it, which is the healthy direction.
20→10 BeatLeader.Replayer.Emulation uses BeatLeader.Models.AbstractReplay✕
- Connections
- 18 pairs of types, where a type in BeatLeader.Replayer.Emulation uses a type in BeatLeader.Models.AbstractReplay.
- The types involved
BeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessor→BeatLeader.Models.AbstractReplay.IReplayBeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessor→BeatLeader.Models.AbstractReplay.IReplayNoteComparatorBeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessor→BeatLeader.Models.AbstractReplay.NoteEventBeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessor→BeatLeader.Models.AbstractReplay.WallEventBeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessorProxy→BeatLeader.Models.AbstractReplay.IReplayNoteComparatorBeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessorProxy→BeatLeader.Models.AbstractReplay.NoteEventBeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessorProxy→BeatLeader.Models.AbstractReplay.WallEventBeatLeader.Replayer.Emulation.ReplayHeightsProcessor→BeatLeader.Models.AbstractReplay.HeightEventBeatLeader.Replayer.Emulation.ReplayScoreEventsProcessor→BeatLeader.Models.AbstractReplay.IReplayBeatLeader.Replayer.Emulation.ReplayScoreEventsProcessor→BeatLeader.Models.AbstractReplay.ScoreEventBeatLeader.Replayer.Emulation.ReplayerNotesCutter→BeatLeader.Models.AbstractReplay.IReplayNoteComparatorBeatLeader.Replayer.Emulation.ReplayerNotesCutter→BeatLeader.Models.AbstractReplay.NoteEventBeatLeader.Replayer.Emulation.ReplayerScoreProcessor→BeatLeader.Models.AbstractReplay.IReplayNoteComparatorBeatLeader.Replayer.Emulation.ReplayerScoreProcessor→BeatLeader.Models.AbstractReplay.NoteEventBeatLeader.Replayer.Emulation.ReplayerScoreProcessor→BeatLeader.Models.AbstractReplay.WallEventBeatLeader.Replayer.Emulation.VirtualPlayer→BeatLeader.Models.AbstractReplay.IReplayBeatLeader.Replayer.Emulation.VirtualPlayer→BeatLeader.Models.AbstractReplay.PlayerMovementFrameBeatLeader.Replayer.Emulation.VirtualPlayersManager→BeatLeader.Models.AbstractReplay.IReplay
- Direction
- BeatLeader.Replayer.Emulation uses BeatLeader.Models.AbstractReplay, so a change to BeatLeader.Models.AbstractReplay can break BeatLeader.Replayer.Emulation, while a change to BeatLeader.Replayer.Emulation can't break BeatLeader.Models.AbstractReplay.
- Position
- Below the diagonal: BeatLeader.Replayer.Emulation uses a module listed above it, which is the healthy direction.
20→16 BeatLeader.Replayer.Emulation uses BeatLeader.Replayer✕
- Connections
- 1 pair of types, where a type in BeatLeader.Replayer.Emulation uses a type in BeatLeader.Replayer.
- The types involved
BeatLeader.Replayer.Emulation.VirtualPlayerAvatarBody→BeatLeader.Replayer.ReplayerExtraObjectsProvider
- Direction
- BeatLeader.Replayer.Emulation uses BeatLeader.Replayer, so a change to BeatLeader.Replayer can break BeatLeader.Replayer.Emulation, while a change to BeatLeader.Replayer.Emulation can't break BeatLeader.Replayer.
- Position
- Below the diagonal: BeatLeader.Replayer.Emulation uses a module listed above it, which is the healthy direction.
20→18 BeatLeader.Replayer.Emulation uses BeatLeader.Models✕
- Connections
- 46 pairs of types, where a type in BeatLeader.Replayer.Emulation uses a type in BeatLeader.Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BeatLeader.Replayer.Emulation.Pool→BeatLeader.Models.IVirtualPlayerBeatLeader.Replayer.Emulation.PoseApplicator→BeatLeader.Models.IVirtualPlayerPoseReceiverBeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessor→BeatLeader.Models.IBeatmapTimeControllerBeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessor→BeatLeader.Models.IReplayBeatmapEventsProcessorBeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessor→BeatLeader.Models.TickablePoolItemBeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessorProxy→BeatLeader.Models.IReplayBeatmapEventsProcessorBeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessorProxy→BeatLeader.Models.IVirtualPlayerBeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessorProxy→BeatLeader.Models.IVirtualPlayersManagerBeatLeader.Replayer.Emulation.ReplayHeightsProcessor→BeatLeader.Models.IBeatmapTimeControllerBeatLeader.Replayer.Emulation.ReplayHeightsProcessor→BeatLeader.Models.IVirtualPlayerBeatLeader.Replayer.Emulation.ReplayHeightsProcessor→BeatLeader.Models.IVirtualPlayersManagerBeatLeader.Replayer.Emulation.ReplayScoreEventsProcessor→BeatLeader.Models.IBeatmapTimeControllerBeatLeader.Replayer.Emulation.ReplayScoreEventsProcessor→BeatLeader.Models.IReplayBeatmapDataBeatLeader.Replayer.Emulation.ReplayScoreEventsProcessor→BeatLeader.Models.IReplayScoreEventsProcessorBeatLeader.Replayer.Emulation.ReplayScoreEventsProcessor→BeatLeader.Models.TickablePoolItemBeatLeader.Replayer.Emulation.ReplayerNotesCutter→BeatLeader.Models.IReplayBeatmapEventsProcessorBeatLeader.Replayer.Emulation.ReplayerScoreProcessor→BeatLeader.Models.IReplayBeatmapDataBeatLeader.Replayer.Emulation.ReplayerScoreProcessor→BeatLeader.Models.IReplayBeatmapEventsProcessorBeatLeader.Replayer.Emulation.VirtualPlayer→BeatLeader.Models.IBeatmapTimeControllerBeatLeader.Replayer.Emulation.VirtualPlayer→BeatLeader.Models.IReplayBeatmapEventsProcessorBeatLeader.Replayer.Emulation.VirtualPlayer→BeatLeader.Models.IReplayScoreEventsProcessorBeatLeader.Replayer.Emulation.VirtualPlayer→BeatLeader.Models.IVirtualPlayerBeatLeader.Replayer.Emulation.VirtualPlayer→BeatLeader.Models.IVirtualPlayerBodyBeatLeader.Replayer.Emulation.VirtualPlayer→BeatLeader.Models.IVirtualPlayerMovementProcessorBeatLeader.Replayer.Emulation.VirtualPlayer→BeatLeader.Models.IVirtualPlayerPoseReceiver
- Direction
- BeatLeader.Replayer.Emulation uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Replayer.Emulation, while a change to BeatLeader.Replayer.Emulation can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.Replayer.Emulation uses a module listed above it, which is the healthy direction.
20→31 BeatLeader.Replayer.Emulation uses BeatLeader part of a loop✕
- Connections
- 8 pairs of types, where a type in BeatLeader.Replayer.Emulation uses a type in BeatLeader.
- The types involved
BeatLeader.Replayer.Emulation.ReplayBeatmapEventsProcessor→BeatLeader.EventsProcessorBeatLeader.Replayer.Emulation.ReplayHeightsProcessor→BeatLeader.HarmonySilencerBeatLeader.Replayer.Emulation.ReplayScoreEventsProcessor→BeatLeader.EventsProcessorBeatLeader.Replayer.Emulation.ReplayerScoreProcessor→BeatLeader.HarmonyAutoPatchBeatLeader.Replayer.Emulation.ReplayerScoreProcessor→BeatLeader.HarmonyMultisilencerBeatLeader.Replayer.Emulation.ReplayerScoreProcessor→BeatLeader.HarmonyPatchDescriptorBeatLeader.Replayer.Emulation.VirtualPlayerAvatarBody→BeatLeader.ZenjectMenuResolverBeatLeader.Replayer.Emulation.VirtualPlayerBattleRoyaleSabers→BeatLeader.BattleRoyaleVRController
- Direction
- BeatLeader.Replayer.Emulation uses BeatLeader, so a change to BeatLeader can break BeatLeader.Replayer.Emulation, while a change to BeatLeader.Replayer.Emulation can't break BeatLeader.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→18 BeatLeader.Results uses BeatLeader.Models✕
- Connections
- 1 pair of types, where a type in BeatLeader.Results uses a type in BeatLeader.Models.
- The types involved
BeatLeader.Results.SpecialEventResultsPanel→BeatLeader.Models.PlatformEventStatus
- Direction
- BeatLeader.Results uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Results, while a change to BeatLeader.Results can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.Results uses a module listed above it, which is the healthy direction.
22→17 BeatLeader.UI.Replayer.Desktop uses BeatLeader.UI.Replayer✕
- Connections
- 4 pairs of types, where a type in BeatLeader.UI.Replayer.Desktop uses a type in BeatLeader.UI.Replayer.
- The types involved
BeatLeader.UI.Replayer.Desktop.ReplayerDesktopUIBinder→BeatLeader.UI.Replayer.ReplayerUIBinderBeatLeader.UI.Replayer.Desktop.ReplayerDesktopViewController→BeatLeader.UI.Replayer.IBodySettingsViewFactoryBeatLeader.UI.Replayer.Desktop.ReplayerDesktopViewController→BeatLeader.UI.Replayer.IReplayWatermarkBeatLeader.UI.Replayer.Desktop.ReplayerDesktopViewController→BeatLeader.UI.Replayer.ReplayerUIPanel
- Direction
- BeatLeader.UI.Replayer.Desktop uses BeatLeader.UI.Replayer, so a change to BeatLeader.UI.Replayer can break BeatLeader.UI.Replayer.Desktop, while a change to BeatLeader.UI.Replayer.Desktop can't break BeatLeader.UI.Replayer.
- Position
- Below the diagonal: BeatLeader.UI.Replayer.Desktop uses a module listed above it, which is the healthy direction.
22→18 BeatLeader.UI.Replayer.Desktop uses BeatLeader.Models✕
- Connections
- 7 pairs of types, where a type in BeatLeader.UI.Replayer.Desktop uses a type in BeatLeader.Models.
- The types involved
BeatLeader.UI.Replayer.Desktop.ReplayerDesktopUIBinder→BeatLeader.Models.ReplayLaunchDataBeatLeader.UI.Replayer.Desktop.ReplayerDesktopViewController→BeatLeader.Models.ICameraControllerBeatLeader.UI.Replayer.Desktop.ReplayerDesktopViewController→BeatLeader.Models.IReplayFinishControllerBeatLeader.UI.Replayer.Desktop.ReplayerDesktopViewController→BeatLeader.Models.IReplayPauseControllerBeatLeader.UI.Replayer.Desktop.ReplayerDesktopViewController→BeatLeader.Models.IReplayTimeControllerBeatLeader.UI.Replayer.Desktop.ReplayerDesktopViewController→BeatLeader.Models.IVirtualPlayersManagerBeatLeader.UI.Replayer.Desktop.ReplayerDesktopViewController→BeatLeader.Models.ReplayLaunchData
- Direction
- BeatLeader.UI.Replayer.Desktop uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.UI.Replayer.Desktop, while a change to BeatLeader.UI.Replayer.Desktop can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.UI.Replayer.Desktop uses a module listed above it, which is the healthy direction.
23→18 BeatLeader.WebRequests uses BeatLeader.Models✕
- Connections
- 2 pairs of types, where a type in BeatLeader.WebRequests uses a type in BeatLeader.Models.
- The types involved
BeatLeader.WebRequests.HttpContentWithProgress→BeatLeader.Models.IIoOperationDescriptorBeatLeader.WebRequests.WebRequestProcessor→BeatLeader.Models.IIoOperationDescriptor
- Direction
- BeatLeader.WebRequests uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.WebRequests, while a change to BeatLeader.WebRequests can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.WebRequests uses a module listed above it, which is the healthy direction.
24→18 BeatLeader.DataManager uses BeatLeader.Models✕
- Connections
- 35 pairs of types, where a type in BeatLeader.DataManager uses a type in BeatLeader.Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BeatLeader.DataManager.HiddenPlayersCache→BeatLeader.Models.PlayerBeatLeader.DataManager.LeaderboardCacheEntry→BeatLeader.Models.ClanBeatLeader.DataManager.LeaderboardCacheEntry→BeatLeader.Models.DiffInfoBeatLeader.DataManager.LeaderboardCacheEntry→BeatLeader.Models.QualificationInfoBeatLeader.DataManager.LeaderboardCacheEntry→BeatLeader.Models.SongInfoBeatLeader.DataManager.LeaderboardContextsManager→BeatLeader.Models.ScoresContextBeatLeader.DataManager.LeaderboardContextsManager→BeatLeader.Models.ServerScoresContextBeatLeader.DataManager.LeaderboardInfoManager→BeatLeader.Models.HashLeaderboardsInfoResponseBeatLeader.DataManager.LeaderboardInfoManager→BeatLeader.Models.LeaderboardKeyBeatLeader.DataManager.LeaderboardManager→BeatLeader.Models.LeaderboardKeyBeatLeader.DataManager.LeaderboardManager→BeatLeader.Models.PlayerBeatLeader.DataManager.LeaderboardManager→BeatLeader.Models.ScoreUploadResponseBeatLeader.DataManager.LeaderboardManager→BeatLeader.Models.ScoresScopeBeatLeader.DataManager.LeaderboardsCache→BeatLeader.Models.ClanBeatLeader.DataManager.LeaderboardsCache→BeatLeader.Models.DiffInfoBeatLeader.DataManager.LeaderboardsCache→BeatLeader.Models.LeaderboardKeyBeatLeader.DataManager.LeaderboardsCache→BeatLeader.Models.QualificationInfoBeatLeader.DataManager.LeaderboardsCache→BeatLeader.Models.SongInfoBeatLeader.DataManager.MapTypesManager→BeatLeader.Models.MapsTypeDescriptionBeatLeader.DataManager.ModVersionChecker→BeatLeader.Models.LatestReleasesBeatLeader.DataManager.ModVersionChecker→BeatLeader.Models.ReleaseInfoBeatLeader.DataManager.ModifiersManager→BeatLeader.Models.LeaderboardKeyBeatLeader.DataManager.ModifiersManager→BeatLeader.Models.ModifiersMapBeatLeader.DataManager.ModifiersManager→BeatLeader.Models.ModifiersRatingBeatLeader.DataManager.OculusMigrationManager→BeatLeader.Models.OculusUserInfo
- Direction
- BeatLeader.DataManager uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.DataManager, while a change to BeatLeader.DataManager can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.DataManager uses a module listed above it, which is the healthy direction.
24→23 BeatLeader.DataManager uses BeatLeader.WebRequests✕
- Connections
- 18 pairs of types, where a type in BeatLeader.DataManager uses a type in BeatLeader.WebRequests.
- The types involved
BeatLeader.DataManager.LeaderboardContextsManager→BeatLeader.WebRequests.IWebRequestBeatLeader.DataManager.LeaderboardContextsManager→BeatLeader.WebRequests.RequestStateBeatLeader.DataManager.LeaderboardInfoManager→BeatLeader.WebRequests.IWebRequestBeatLeader.DataManager.LeaderboardInfoManager→BeatLeader.WebRequests.RequestStateBeatLeader.DataManager.LeaderboardManager→BeatLeader.WebRequests.IWebRequestBeatLeader.DataManager.LeaderboardManager→BeatLeader.WebRequests.RequestStateBeatLeader.DataManager.MapTypesManager→BeatLeader.WebRequests.IWebRequestBeatLeader.DataManager.MapTypesManager→BeatLeader.WebRequests.RequestStateBeatLeader.DataManager.ModVersionChecker→BeatLeader.WebRequests.IWebRequestBeatLeader.DataManager.ModVersionChecker→BeatLeader.WebRequests.RequestStateBeatLeader.DataManager.OculusMigrationManager→BeatLeader.WebRequests.IWebRequestBeatLeader.DataManager.OculusMigrationManager→BeatLeader.WebRequests.RequestStateBeatLeader.DataManager.PrestigeLevelsManager→BeatLeader.WebRequests.IWebRequestBeatLeader.DataManager.PrestigeLevelsManager→BeatLeader.WebRequests.RequestStateBeatLeader.DataManager.ProfileManager→BeatLeader.WebRequests.IWebRequestBeatLeader.DataManager.ProfileManager→BeatLeader.WebRequests.RequestStateBeatLeader.DataManager.VotingManager→BeatLeader.WebRequests.IWebRequestBeatLeader.DataManager.VotingManager→BeatLeader.WebRequests.RequestState
- Direction
- BeatLeader.DataManager uses BeatLeader.WebRequests, so a change to BeatLeader.WebRequests can break BeatLeader.DataManager, while a change to BeatLeader.DataManager can't break BeatLeader.WebRequests.
- Position
- Below the diagonal: BeatLeader.DataManager uses a module listed above it, which is the healthy direction.
24→31 BeatLeader.DataManager uses BeatLeader part of a loop✕
- Connections
- 2 pairs of types, where a type in BeatLeader.DataManager uses a type in BeatLeader.
- The types involved
BeatLeader.DataManager.LeaderboardManager→BeatLeader.ScoresTableContentBeatLeader.DataManager.LeaderboardsCache→BeatLeader.AppCache
- Direction
- BeatLeader.DataManager uses BeatLeader, so a change to BeatLeader can break BeatLeader.DataManager, while a change to BeatLeader.DataManager can't break BeatLeader.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→18 BeatLeader.Replayer.Binding uses BeatLeader.Models✕
- Connections
- 8 pairs of types, where a type in BeatLeader.Replayer.Binding uses a type in BeatLeader.Models.
- The types involved
BeatLeader.Replayer.Binding.HideCursorHotkey→BeatLeader.Models.ReplayLaunchDataBeatLeader.Replayer.Binding.LayoutEditorModeHotkey→BeatLeader.Models.ReplayLaunchDataBeatLeader.Replayer.Binding.PauseHotkey→BeatLeader.Models.IReplayPauseControllerBeatLeader.Replayer.Binding.PauseHotkey→BeatLeader.Models.ReplayLaunchDataBeatLeader.Replayer.Binding.RewindBackwardHotkey→BeatLeader.Models.IBeatmapTimeControllerBeatLeader.Replayer.Binding.RewindBackwardHotkey→BeatLeader.Models.ReplayLaunchDataBeatLeader.Replayer.Binding.RewindForwardHotkey→BeatLeader.Models.IBeatmapTimeControllerBeatLeader.Replayer.Binding.RewindForwardHotkey→BeatLeader.Models.ReplayLaunchData
- Direction
- BeatLeader.Replayer.Binding uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Replayer.Binding, while a change to BeatLeader.Replayer.Binding can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.Replayer.Binding uses a module listed above it, which is the healthy direction.
25→22 BeatLeader.Replayer.Binding uses BeatLeader.UI.Replayer.Desktop✕
- Connections
- 1 pair of types, where a type in BeatLeader.Replayer.Binding uses a type in BeatLeader.UI.Replayer.Desktop.
- The types involved
BeatLeader.Replayer.Binding.LayoutEditorModeHotkey→BeatLeader.UI.Replayer.Desktop.ReplayerDesktopViewController
- Direction
- BeatLeader.Replayer.Binding uses BeatLeader.UI.Replayer.Desktop, so a change to BeatLeader.UI.Replayer.Desktop can break BeatLeader.Replayer.Binding, while a change to BeatLeader.Replayer.Binding can't break BeatLeader.UI.Replayer.Desktop.
- Position
- Below the diagonal: BeatLeader.Replayer.Binding uses a module listed above it, which is the healthy direction.
26→4 BeatLeader.UI.Hub uses BeatLeader.Models.BeatSaver✕
- Connections
- 2 pairs of types, where a type in BeatLeader.UI.Hub uses a type in BeatLeader.Models.BeatSaver.
- The types involved
BeatLeader.UI.Hub.BeatmapDownloadDialog→BeatLeader.Models.BeatSaver.MapDetailBeatLeader.UI.Hub.MapDetailPreviewPanel→BeatLeader.Models.BeatSaver.MapDetail
- Direction
- BeatLeader.UI.Hub uses BeatLeader.Models.BeatSaver, so a change to BeatLeader.Models.BeatSaver can break BeatLeader.UI.Hub, while a change to BeatLeader.UI.Hub can't break BeatLeader.Models.BeatSaver.
- Position
- Below the diagonal: BeatLeader.UI.Hub uses a module listed above it, which is the healthy direction.
26→6 BeatLeader.UI.Hub uses BeatLeader.UI.Reactive✕
- Connections
- 5 pairs of types, where a type in BeatLeader.UI.Hub uses a type in BeatLeader.UI.Reactive.
- The types involved
BeatLeader.UI.Hub.BasicReplayDetailPanel→BeatLeader.UI.Reactive.ValueAnimatorBeatLeader.UI.Hub.BattleRoyaleFloatingMenuText→BeatLeader.UI.Reactive.ValueAnimatorBeatLeader.UI.Hub.BattleRoyaleOpponentsViewController→BeatLeader.UI.Reactive.ValueAnimatorBeatLeader.UI.Hub.Cell→BeatLeader.UI.Reactive.ValueAnimatorBeatLeader.UI.Hub.EditAvatarFloatingButton→BeatLeader.UI.Reactive.ValueAnimator
- Direction
- BeatLeader.UI.Hub uses BeatLeader.UI.Reactive, so a change to BeatLeader.UI.Reactive can break BeatLeader.UI.Hub, while a change to BeatLeader.UI.Hub can't break BeatLeader.UI.Reactive.
- Position
- Below the diagonal: BeatLeader.UI.Hub uses a module listed above it, which is the healthy direction.
26→7 BeatLeader.UI.Hub uses BeatLeader.UI.Reactive.Components✕
- Connections
- 2 pairs of types, where a type in BeatLeader.UI.Hub uses a type in BeatLeader.UI.Reactive.Components.
- The types involved
BeatLeader.UI.Hub.Avatar→BeatLeader.UI.Reactive.Components.ReeWrapperV2BeatLeader.UI.Hub.FilterContainer→BeatLeader.UI.Reactive.Components.CheckCircle
- Direction
- BeatLeader.UI.Hub uses BeatLeader.UI.Reactive.Components, so a change to BeatLeader.UI.Reactive.Components can break BeatLeader.UI.Hub, while a change to BeatLeader.UI.Hub can't break BeatLeader.UI.Reactive.Components.
- Position
- Below the diagonal: BeatLeader.UI.Hub uses a module listed above it, which is the healthy direction.
26→10 BeatLeader.UI.Hub uses BeatLeader.Models.AbstractReplay✕
- Connections
- 1 pair of types, where a type in BeatLeader.UI.Hub uses a type in BeatLeader.Models.AbstractReplay.
- The types involved
BeatLeader.UI.Hub.BattleRoyaleReplay→BeatLeader.Models.AbstractReplay.BattleRoyaleReplayData
- Direction
- BeatLeader.UI.Hub uses BeatLeader.Models.AbstractReplay, so a change to BeatLeader.Models.AbstractReplay can break BeatLeader.UI.Hub, while a change to BeatLeader.UI.Hub can't break BeatLeader.Models.AbstractReplay.
- Position
- Below the diagonal: BeatLeader.UI.Hub uses a module listed above it, which is the healthy direction.
26→13 BeatLeader.UI.Hub uses BeatLeader.UI✕
- Connections
- 2 pairs of types, where a type in BeatLeader.UI.Hub uses a type in BeatLeader.UI.
- The types involved
BeatLeader.UI.Hub.BasicReplayDetailPanel→BeatLeader.UI.QuickMiniProfileBeatLeader.UI.Hub.BeatLeaderHubMainViewController→BeatLeader.UI.QuickMiniProfile
- Direction
- BeatLeader.UI.Hub uses BeatLeader.UI, so a change to BeatLeader.UI can break BeatLeader.UI.Hub, while a change to BeatLeader.UI.Hub can't break BeatLeader.UI.
- Position
- Below the diagonal: BeatLeader.UI.Hub uses a module listed above it, which is the healthy direction.
26→16 BeatLeader.UI.Hub uses BeatLeader.Replayer✕
- Connections
- 3 pairs of types, where a type in BeatLeader.UI.Hub uses a type in BeatLeader.Replayer.
- The types involved
BeatLeader.UI.Hub.BattleRoyaleFlowCoordinator→BeatLeader.Replayer.ReplayerMenuLoaderBeatLeader.UI.Hub.ReplayDetailPanel→BeatLeader.Replayer.ReplayerMenuLoaderBeatLeader.UI.Hub.ReplayManagerViewController→BeatLeader.Replayer.ReplayerMenuLoader
- Direction
- BeatLeader.UI.Hub uses BeatLeader.Replayer, so a change to BeatLeader.Replayer can break BeatLeader.UI.Hub, while a change to BeatLeader.UI.Hub can't break BeatLeader.Replayer.
- Position
- Below the diagonal: BeatLeader.UI.Hub uses a module listed above it, which is the healthy direction.
26→18 BeatLeader.UI.Hub uses BeatLeader.Models✕
- Connections
- 57 pairs of types, where a type in BeatLeader.UI.Hub uses a type in BeatLeader.Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BeatLeader.UI.Hub.Avatar→BeatLeader.Models.IReplayHeaderBeatLeader.UI.Hub.BasicReplayDetailPanel→BeatLeader.Models.IReplayHeaderBeatLeader.UI.Hub.BattleRoyaleAvatarsController→BeatLeader.Models.IReplayHeaderBeatLeader.UI.Hub.BattleRoyaleDetailPanel→BeatLeader.Models.IReplayHeaderBeatLeader.UI.Hub.BattleRoyaleFlowCoordinator→BeatLeader.Models.BeatmapLevelWithKeyBeatLeader.UI.Hub.BattleRoyaleFlowCoordinator→BeatLeader.Models.IReplayHeaderBeatLeader.UI.Hub.BattleRoyaleGreetingsViewController→BeatLeader.Models.BeatmapLevelWithKeyBeatLeader.UI.Hub.BattleRoyaleGreetingsViewController→BeatLeader.Models.IBattleRoyaleReplayBeatLeader.UI.Hub.BattleRoyaleReplay→BeatLeader.Models.IBattleRoyaleReplayBeatLeader.UI.Hub.BattleRoyaleReplay→BeatLeader.Models.IReplayHeaderBeatLeader.UI.Hub.BattleRoyaleReplay→BeatLeader.Models.IReplayInfoBeatLeader.UI.Hub.BattleRoyaleReplaySelectionViewController→BeatLeader.Models.BeatmapLevelWithKeyBeatLeader.UI.Hub.BattleRoyaleReplaySelectionViewController→BeatLeader.Models.IBattleRoyaleReplayBeatLeader.UI.Hub.BattleRoyaleReplaySelectionViewController→BeatLeader.Models.IReplayHeaderBeatLeader.UI.Hub.BeatLeaderHubAvatarController→BeatLeader.Models.IPlayerBeatLeader.UI.Hub.BeatmapFilterHost→BeatLeader.Models.BeatmapLevelWithKeyBeatLeader.UI.Hub.BeatmapFilterHost→BeatLeader.Models.IReplayHeaderBeatLeader.UI.Hub.BeatmapFilterPanel→BeatLeader.Models.BeatmapLevelWithKeyBeatLeader.UI.Hub.BeatmapFilterPanel→BeatLeader.Models.IReplayHeaderBeatLeader.UI.Hub.BeatmapPreviewPanel→BeatLeader.Models.BeatmapLevelWithKeyBeatLeader.UI.Hub.BeatmapReplayFilter→BeatLeader.Models.BeatmapLevelWithKeyBeatLeader.UI.Hub.BeatmapReplayFilter→BeatLeader.Models.IReplayHeaderBeatLeader.UI.Hub.BeatmapReplayLaunchPanel→BeatLeader.Models.IReplayHeaderBeatLeader.UI.Hub.Cell→BeatLeader.Models.IBattleRoyaleReplayBeatLeader.UI.Hub.CharacteristicFilterPanel→BeatLeader.Models.IReplayHeader
- Direction
- BeatLeader.UI.Hub uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.UI.Hub, while a change to BeatLeader.UI.Hub can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.UI.Hub uses a module listed above it, which is the healthy direction.
26→20 BeatLeader.UI.Hub uses BeatLeader.Replayer.Emulation✕
- Connections
- 4 pairs of types, where a type in BeatLeader.UI.Hub uses a type in BeatLeader.Replayer.Emulation.
- The types involved
BeatLeader.UI.Hub.BattleRoyaleAvatar→BeatLeader.Replayer.Emulation.BeatAvatarLoaderBeatLeader.UI.Hub.BattleRoyaleAvatar→BeatLeader.Replayer.Emulation.MenuBeatAvatarControllerBeatLeader.UI.Hub.BeatLeaderHubAvatarController→BeatLeader.Replayer.Emulation.BeatAvatarLoaderBeatLeader.UI.Hub.BeatLeaderHubAvatarController→BeatLeader.Replayer.Emulation.MenuBeatAvatarController
- Direction
- BeatLeader.UI.Hub uses BeatLeader.Replayer.Emulation, so a change to BeatLeader.Replayer.Emulation can break BeatLeader.UI.Hub, while a change to BeatLeader.UI.Hub can't break BeatLeader.Replayer.Emulation.
- Position
- Below the diagonal: BeatLeader.UI.Hub uses a module listed above it, which is the healthy direction.
26→29 BeatLeader.UI.Hub uses BeatLeader.Components part of a loop✕
- Connections
- 11 pairs of types, where a type in BeatLeader.UI.Hub uses a type in BeatLeader.Components.
- The types involved
BeatLeader.UI.Hub.BattleRoyaleReplayBadge→BeatLeader.Components.PlayerAvatarBeatLeader.UI.Hub.Cell→BeatLeader.Components.PlayerAvatarBeatLeader.UI.Hub.LevelSelectionViewController→BeatLeader.Components.DummyViewControllerBeatLeader.UI.Hub.ReplayStatisticsPanel→BeatLeader.Components.AccuracyDetailsBeatLeader.UI.Hub.ReplayStatisticsPanel→BeatLeader.Components.AccuracyGraphPanelBeatLeader.UI.Hub.ReplayStatisticsPanel→BeatLeader.Components.AccuracyGridBeatLeader.UI.Hub.ReplayStatisticsPanel→BeatLeader.Components.ReplayerSettingsPanelBeatLeader.UI.Hub.ReplayStatisticsPanel→BeatLeader.Components.ScoreInfoPanelControlsBeatLeader.UI.Hub.ReplayStatisticsPanel→BeatLeader.Components.ScoreOverviewPage1BeatLeader.UI.Hub.ReplayStatisticsPanel→BeatLeader.Components.ScoreOverviewPage2BeatLeader.UI.Hub.ReplayStatisticsPanel→BeatLeader.Components.ScoreStatsLoadingScreen
- Direction
- BeatLeader.UI.Hub uses BeatLeader.Components, so a change to BeatLeader.Components can break BeatLeader.UI.Hub, while a change to BeatLeader.UI.Hub can't break BeatLeader.Components.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→31 BeatLeader.UI.Hub uses BeatLeader part of a loop✕
- Connections
- 19 pairs of types, where a type in BeatLeader.UI.Hub uses a type in BeatLeader.
- The types involved
BeatLeader.UI.Hub.BattleRoyaleReplaySelectionViewController→BeatLeader.BeatLeaderHubThemeBeatLeader.UI.Hub.BeatLeaderHubAvatarController→BeatLeader.BeatLeaderHubFlowCoordinatorBeatLeader.UI.Hub.BeatLeaderHubAvatarController→BeatLeader.BeatLeaderHubThemeBeatLeader.UI.Hub.BeatLeaderHubMainViewController→BeatLeader.BeatLeaderHubFlowCoordinatorBeatLeader.UI.Hub.BeatLeaderHubMainViewController→BeatLeader.BeatLeaderHubThemeBeatLeader.UI.Hub.BeatLeaderSettingsFlowCoordinator→BeatLeader.BeatLeaderHubFlowCoordinatorBeatLeader.UI.Hub.BeatLeaderSettingsView→BeatLeader.BeatLeaderHubThemeBeatLeader.UI.Hub.BeatLeaderSettingsViewController→BeatLeader.BeatLeaderHubThemeBeatLeader.UI.Hub.EditAvatarFloatingButton→BeatLeader.BeatLeaderHubMenuButtonsThemeBeatLeader.UI.Hub.GlobalSettingsView→BeatLeader.BLLanguageBeatLeader.UI.Hub.ListFiltersPanel→BeatLeader.ObservableCollectionAdapterBeatLeader.UI.Hub.ReplayDetailPanel→BeatLeader.ReplayerViewNavigatorWrapperBeatLeader.UI.Hub.ReplayManagerViewController→BeatLeader.BeatLeaderHubThemeBeatLeader.UI.Hub.ReplayManagerViewController→BeatLeader.IReplayerViewNavigatorBeatLeader.UI.Hub.ReplaysList→BeatLeader.ReplayManagerSearchThemeBeatLeader.UI.Hub.ReplaysPreviewPanel→BeatLeader.ObservableSetBeatLeader.UI.Hub.UISettingsView→BeatLeader.BeatLeaderHubMenuButtonsThemeBeatLeader.UI.Hub.UISettingsView→BeatLeader.BeatLeaderHubThemeBeatLeader.UI.Hub.UISettingsView→BeatLeader.ReplayManagerSearchTheme
- Direction
- BeatLeader.UI.Hub uses BeatLeader, so a change to BeatLeader can break BeatLeader.UI.Hub, while a change to BeatLeader.UI.Hub can't break BeatLeader.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→18 BeatLeader.UI.MainMenu uses BeatLeader.Models✕
- Connections
- 20 pairs of types, where a type in BeatLeader.UI.MainMenu uses a type in BeatLeader.Models.
- The types involved
BeatLeader.UI.MainMenu.BeatLeaderNewsViewController→BeatLeader.Models.PlatformEventStatusBeatLeader.UI.MainMenu.EventCalendar→BeatLeader.Models.PlatformEventMapBeatLeader.UI.MainMenu.EventCalendar→BeatLeader.Models.PlatformEventStatusBeatLeader.UI.MainMenu.EventNewsPanel→BeatLeader.Models.PlatformEventBeatLeader.UI.MainMenu.EventPreviewPanel→BeatLeader.Models.PlatformEventBeatLeader.UI.MainMenu.MapDownloadDialog→BeatLeader.Models.MapDetailBeatLeader.UI.MainMenu.MapNewsPanel→BeatLeader.Models.PagedBeatLeader.UI.MainMenu.MapNewsPanel→BeatLeader.Models.TrendingMapDataBeatLeader.UI.MainMenu.MapPreviewDialog→BeatLeader.Models.MapDetailBeatLeader.UI.MainMenu.MapPreviewDialog→BeatLeader.Models.TrendingMapDataBeatLeader.UI.MainMenu.MapPreviewPanel→BeatLeader.Models.TrendingMapDataBeatLeader.UI.MainMenu.NewsViewPanel→BeatLeader.Models.PlatformEventBeatLeader.UI.MainMenu.NewsViewPanel→BeatLeader.Models.PlatformEventStatusBeatLeader.UI.MainMenu.SpecialEventBar→BeatLeader.Models.PlatformEventMapBeatLeader.UI.MainMenu.SpecialEventBar→BeatLeader.Models.PlatformEventStatusBeatLeader.UI.MainMenu.SpecialEventMapPanel→BeatLeader.Models.MapDetailBeatLeader.UI.MainMenu.SpecialEventMapPanel→BeatLeader.Models.PlatformEventMapBeatLeader.UI.MainMenu.SpecialEventPanel→BeatLeader.Models.PlatformEventStatusBeatLeader.UI.MainMenu.TextNewsPanel→BeatLeader.Models.NewsPostBeatLeader.UI.MainMenu.TextNewsPanel→BeatLeader.Models.Paged
- Direction
- BeatLeader.UI.MainMenu uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.UI.MainMenu, while a change to BeatLeader.UI.MainMenu can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.UI.MainMenu uses a module listed above it, which is the healthy direction.
27→23 BeatLeader.UI.MainMenu uses BeatLeader.WebRequests✕
- Connections
- 8 pairs of types, where a type in BeatLeader.UI.MainMenu uses a type in BeatLeader.WebRequests.
- The types involved
BeatLeader.UI.MainMenu.EventNewsPanel→BeatLeader.WebRequests.RequestStateBeatLeader.UI.MainMenu.MapNewsPanel→BeatLeader.WebRequests.IWebRequestBeatLeader.UI.MainMenu.MapNewsPanel→BeatLeader.WebRequests.RequestStateBeatLeader.UI.MainMenu.NewsPanel→BeatLeader.WebRequests.RequestStateBeatLeader.UI.MainMenu.NewsViewPanel→BeatLeader.WebRequests.IWebRequestBeatLeader.UI.MainMenu.NewsViewPanel→BeatLeader.WebRequests.RequestStateBeatLeader.UI.MainMenu.TextNewsPanel→BeatLeader.WebRequests.IWebRequestBeatLeader.UI.MainMenu.TextNewsPanel→BeatLeader.WebRequests.RequestState
- Direction
- BeatLeader.UI.MainMenu uses BeatLeader.WebRequests, so a change to BeatLeader.WebRequests can break BeatLeader.UI.MainMenu, while a change to BeatLeader.UI.MainMenu can't break BeatLeader.WebRequests.
- Position
- Below the diagonal: BeatLeader.UI.MainMenu uses a module listed above it, which is the healthy direction.
27→31 BeatLeader.UI.MainMenu uses BeatLeader part of a loop✕
- Connections
- 3 pairs of types, where a type in BeatLeader.UI.MainMenu uses a type in BeatLeader.
- The types involved
BeatLeader.UI.MainMenu.EventDetailsDialog→BeatLeader.AbstractReeModalBeatLeader.UI.MainMenu.MapDownloadDialog→BeatLeader.AbstractReeModalBeatLeader.UI.MainMenu.MapPreviewDialog→BeatLeader.AbstractReeModal
- Direction
- BeatLeader.UI.MainMenu uses BeatLeader, so a change to BeatLeader can break BeatLeader.UI.MainMenu, while a change to BeatLeader.UI.MainMenu can't break BeatLeader.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→18 BeatLeader.Manager uses BeatLeader.Models✕
- Connections
- 4 pairs of types, where a type in BeatLeader.Manager uses a type in BeatLeader.Models.
- The types involved
BeatLeader.Manager.LeaderboardEvents→BeatLeader.Models.ClanScoreBeatLeader.Manager.LeaderboardEvents→BeatLeader.Models.PlayerBeatLeader.Manager.LeaderboardEvents→BeatLeader.Models.ScoreBeatLeader.Manager.LeaderboardEvents→BeatLeader.Models.Vote
- Direction
- BeatLeader.Manager uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Manager, while a change to BeatLeader.Manager can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.Manager uses a module listed above it, which is the healthy direction.
28→24 BeatLeader.Manager uses BeatLeader.DataManager✕
- Connections
- 1 pair of types, where a type in BeatLeader.Manager uses a type in BeatLeader.DataManager.
- The types involved
BeatLeader.Manager.LeaderboardEvents→BeatLeader.DataManager.PlaylistType
- Direction
- BeatLeader.Manager uses BeatLeader.DataManager, so a change to BeatLeader.DataManager can break BeatLeader.Manager, while a change to BeatLeader.Manager can't break BeatLeader.DataManager.
- Position
- Below the diagonal: BeatLeader.Manager uses a module listed above it, which is the healthy direction.
29→7 BeatLeader.Components uses BeatLeader.UI.Reactive.Components✕
- Connections
- 2 pairs of types, where a type in BeatLeader.Components uses a type in BeatLeader.UI.Reactive.Components.
- The types involved
BeatLeader.Components.DownloadScoresModal→BeatLeader.UI.Reactive.Components.ProgressBarBeatLeader.Components.LeaderboardInfoPanel→BeatLeader.UI.Reactive.Components.ReeWrapperV2
- Direction
- BeatLeader.Components uses BeatLeader.UI.Reactive.Components, so a change to BeatLeader.UI.Reactive.Components can break BeatLeader.Components, while a change to BeatLeader.Components can't break BeatLeader.UI.Reactive.Components.
- Position
- Below the diagonal: BeatLeader.Components uses a module listed above it, which is the healthy direction.
29→11 BeatLeader.Components uses BeatLeader.Models.Replay✕
- Connections
- 3 pairs of types, where a type in BeatLeader.Components uses a type in BeatLeader.Models.Replay.
- The types involved
BeatLeader.Components.DownloadScoresModal→BeatLeader.Models.Replay.ReplayBeatLeader.Components.ReplayPanel→BeatLeader.Models.Replay.ReplayBeatLeader.Components.UploadProgressBar→BeatLeader.Models.Replay.Replay
- Direction
- BeatLeader.Components uses BeatLeader.Models.Replay, so a change to BeatLeader.Models.Replay can break BeatLeader.Components, while a change to BeatLeader.Components can't break BeatLeader.Models.Replay.
- Position
- Below the diagonal: BeatLeader.Components uses a module listed above it, which is the healthy direction.
29→17 BeatLeader.Components uses BeatLeader.UI.Replayer✕
- Connections
- 2 pairs of types, where a type in BeatLeader.Components uses a type in BeatLeader.UI.Replayer.
- The types involved
BeatLeader.Components.PlayerListEditorComponent→BeatLeader.UI.Replayer.PlayerListBeatLeader.Components.ReplayWatermark→BeatLeader.UI.Replayer.IReplayWatermark
- Direction
- BeatLeader.Components uses BeatLeader.UI.Replayer, so a change to BeatLeader.UI.Replayer can break BeatLeader.Components, while a change to BeatLeader.Components can't break BeatLeader.UI.Replayer.
- Position
- Below the diagonal: BeatLeader.Components uses a module listed above it, which is the healthy direction.
29→18 BeatLeader.Components uses BeatLeader.Models✕
- Connections
- 70 pairs of types, where a type in BeatLeader.Components uses a type in BeatLeader.Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BeatLeader.Components.AbstractScoreRow→BeatLeader.Models.PlayerRoleBeatLeader.Components.AbstractScoreRow→BeatLeader.Models.ScoreRowCellTypeBeatLeader.Components.AbstractScoresTable→BeatLeader.Models.ScoreRowCellTypeBeatLeader.Components.AccuracyDetails→BeatLeader.Models.ScoreStatsBeatLeader.Components.AccuracyGraphPanel→BeatLeader.Models.ScoreStatsBeatLeader.Components.AccuracyGrid→BeatLeader.Models.ScoreStatsBeatLeader.Components.ClanMiniProfile→BeatLeader.Models.ClanBeatLeader.Components.ClanScorePanelContext→BeatLeader.Models.ClanScoreBeatLeader.Components.ClanScorePanelContext→BeatLeader.Models.PlayerBeatLeader.Components.ClanScoresTable→BeatLeader.Models.ScoreRowCellTypeBeatLeader.Components.ClanTag→BeatLeader.Models.ClanBeatLeader.Components.ClanTags→BeatLeader.Models.ClanBeatLeader.Components.ContextsModal→BeatLeader.Models.ScoresContextBeatLeader.Components.ContextsModalOption→BeatLeader.Models.ScoresContextBeatLeader.Components.Data→BeatLeader.Models.ProfileSettingsBeatLeader.Components.DownloadScoresModal→BeatLeader.Models.IReplayHeaderBeatLeader.Components.DownloadScoresModal→BeatLeader.Models.ScoreBeatLeader.Components.ExperienceBar→BeatLeader.Models.PlayerBeatLeader.Components.ExperienceBar→BeatLeader.Models.ScoreUploadResponseBeatLeader.Components.LayoutData→BeatLeader.Models.SerializableVector2BeatLeader.Components.LayoutEditor→BeatLeader.Models.LayoutEditorSettingsBeatLeader.Components.LeaderboardInfoPanel→BeatLeader.Models.DiffInfoBeatLeader.Components.LeaderboardInfoPanel→BeatLeader.Models.LeaderboardDisplaySettingsBeatLeader.Components.LeaderboardInfoPanel→BeatLeader.Models.LeaderboardKeyBeatLeader.Components.LeaderboardInfoPanel→BeatLeader.Models.PlayerRole
- Direction
- BeatLeader.Components uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Components, while a change to BeatLeader.Components can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.Components uses a module listed above it, which is the healthy direction.
29→23 BeatLeader.Components uses BeatLeader.WebRequests✕
- Connections
- 33 pairs of types, where a type in BeatLeader.Components uses a type in BeatLeader.WebRequests. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BeatLeader.Components.ClanScorePanel→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.ClanScorePanel→BeatLeader.WebRequests.RequestStateBeatLeader.Components.ClanScoresTable→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.ClanScoresTable→BeatLeader.WebRequests.RequestStateBeatLeader.Components.DownloadScoresModal→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.EmptyBoardMessage→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.EmptyBoardMessage→BeatLeader.WebRequests.RequestStateBeatLeader.Components.ExperienceBar→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.ExperienceBar→BeatLeader.WebRequests.RequestStateBeatLeader.Components.Logo→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.Logo→BeatLeader.WebRequests.RequestStateBeatLeader.Components.MainScoresTable→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.MainScoresTable→BeatLeader.WebRequests.RequestStateBeatLeader.Components.MiniProfileButtons→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.MiniProfileButtons→BeatLeader.WebRequests.RequestStateBeatLeader.Components.Pagination→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.Pagination→BeatLeader.WebRequests.RequestStateBeatLeader.Components.PlayerInfo→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.PlayerInfo→BeatLeader.WebRequests.RequestStateBeatLeader.Components.PrestigePanel→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.PrestigePanel→BeatLeader.WebRequests.RequestStateBeatLeader.Components.ReplayPanel→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.ReplayPanel→BeatLeader.WebRequests.RequestStateBeatLeader.Components.ScoreInfoPanel→BeatLeader.WebRequests.IWebRequestBeatLeader.Components.ScoreInfoPanel→BeatLeader.WebRequests.RequestState
- Direction
- BeatLeader.Components uses BeatLeader.WebRequests, so a change to BeatLeader.WebRequests can break BeatLeader.Components, while a change to BeatLeader.Components can't break BeatLeader.WebRequests.
- Position
- Below the diagonal: BeatLeader.Components uses a module listed above it, which is the healthy direction.
29→24 BeatLeader.Components uses BeatLeader.DataManager✕
- Connections
- 3 pairs of types, where a type in BeatLeader.Components uses a type in BeatLeader.DataManager.
- The types involved
BeatLeader.Components.BeatLeaderInfo→BeatLeader.DataManager.PlaylistStateBeatLeader.Components.BeatLeaderInfo→BeatLeader.DataManager.PlaylistTypeBeatLeader.Components.CaptorClan→BeatLeader.DataManager.LeaderboardCacheEntry
- Direction
- BeatLeader.Components uses BeatLeader.DataManager, so a change to BeatLeader.DataManager can break BeatLeader.Components, while a change to BeatLeader.Components can't break BeatLeader.DataManager.
- Position
- Below the diagonal: BeatLeader.Components uses a module listed above it, which is the healthy direction.
29→26 BeatLeader.Components uses BeatLeader.UI.Hub✕
- Connections
- 1 pair of types, where a type in BeatLeader.Components uses a type in BeatLeader.UI.Hub.
- The types involved
BeatLeader.Components.LeaderboardInfoPanel→BeatLeader.UI.Hub.PushContainer
- Direction
- BeatLeader.Components uses BeatLeader.UI.Hub, so a change to BeatLeader.UI.Hub can break BeatLeader.Components, while a change to BeatLeader.Components can't break BeatLeader.UI.Hub.
- Position
- Below the diagonal: BeatLeader.Components uses a module listed above it, which is the healthy direction.
29→28 BeatLeader.Components uses BeatLeader.Manager✕
- Connections
- 1 pair of types, where a type in BeatLeader.Components uses a type in BeatLeader.Manager.
- The types involved
BeatLeader.Components.StatusBar→BeatLeader.Manager.StatusMessageType
- Direction
- BeatLeader.Components uses BeatLeader.Manager, so a change to BeatLeader.Manager can break BeatLeader.Components, while a change to BeatLeader.Components can't break BeatLeader.Manager.
- Position
- Below the diagonal: BeatLeader.Components uses a module listed above it, which is the healthy direction.
29→31 BeatLeader.Components uses BeatLeader part of a loop✕
- Connections
- 73 pairs of types, where a type in BeatLeader.Components uses a type in BeatLeader. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BeatLeader.Components.AbstractScoreRow→BeatLeader.IScoreRowContentBeatLeader.Components.AbstractScoreRow→BeatLeader.ReeUIComponentV2BeatLeader.Components.AbstractScoreRow→BeatLeader.ScoresTableLayoutHelperBeatLeader.Components.AbstractScoreRowCell→BeatLeader.ReeUIComponentV2BeatLeader.Components.AbstractScoresTable→BeatLeader.ReeUIComponentV2BeatLeader.Components.AbstractScoresTable→BeatLeader.ScoresTableContentBeatLeader.Components.AbstractScoresTable→BeatLeader.ScoresTableLayoutHelperBeatLeader.Components.AccuracyDetails→BeatLeader.ReeUIComponentV2BeatLeader.Components.AccuracyDetailsAverages→BeatLeader.ReeUIComponentV2BeatLeader.Components.AccuracyDetailsRow→BeatLeader.ReeUIComponentV2BeatLeader.Components.AccuracyGraphPanel→BeatLeader.AccuracyGraphBeatLeader.Components.AccuracyGraphPanel→BeatLeader.ReeUIComponentV2BeatLeader.Components.AccuracyGrid→BeatLeader.RangeBeatLeader.Components.AccuracyGrid→BeatLeader.ReeUIComponentV2BeatLeader.Components.AccuracyGridCell→BeatLeader.ReeUIComponentV2BeatLeader.Components.AccuracyPieChart→BeatLeader.ReeUIComponentV2BeatLeader.Components.BeatLeaderInfo→BeatLeader.AbstractReeModalBeatLeader.Components.CaptorClan→BeatLeader.ReeUIComponentV2BeatLeader.Components.ClanMiniProfile→BeatLeader.ReeUIComponentV2BeatLeader.Components.ClanScorePanel→BeatLeader.AbstractReeModalBeatLeader.Components.ClanScorePanel→BeatLeader.ScoresTableContentBeatLeader.Components.ClanScoresTable→BeatLeader.ScoresTableContentBeatLeader.Components.ClanTag→BeatLeader.ReeUIComponentV2BeatLeader.Components.ClanTags→BeatLeader.ReeUIComponentV2BeatLeader.Components.ContextSelector→BeatLeader.ReeUIComponentV2
- Direction
- BeatLeader.Components uses BeatLeader, so a change to BeatLeader can break BeatLeader.Components, while a change to BeatLeader.Components can't break BeatLeader.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→18 BeatLeader.ViewControllers uses BeatLeader.Models✕
- Connections
- 3 pairs of types, where a type in BeatLeader.ViewControllers uses a type in BeatLeader.Models.
- The types involved
BeatLeader.ViewControllers.LeaderboardView→BeatLeader.Models.ClanScoreBeatLeader.ViewControllers.LeaderboardView→BeatLeader.Models.ScoreBeatLeader.ViewControllers.ResultsScreenUI→BeatLeader.Models.PlatformEventStatus
- Direction
- BeatLeader.ViewControllers uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.ViewControllers, while a change to BeatLeader.ViewControllers can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.ViewControllers uses a module listed above it, which is the healthy direction.
30→21 BeatLeader.ViewControllers uses BeatLeader.Results✕
- Connections
- 1 pair of types, where a type in BeatLeader.ViewControllers uses a type in BeatLeader.Results.
- The types involved
BeatLeader.ViewControllers.ResultsScreenUI→BeatLeader.Results.SpecialEventResultsPanel
- Direction
- BeatLeader.ViewControllers uses BeatLeader.Results, so a change to BeatLeader.Results can break BeatLeader.ViewControllers, while a change to BeatLeader.ViewControllers can't break BeatLeader.Results.
- Position
- Below the diagonal: BeatLeader.ViewControllers uses a module listed above it, which is the healthy direction.
30→27 BeatLeader.ViewControllers uses BeatLeader.UI.MainMenu✕
- Connections
- 1 pair of types, where a type in BeatLeader.ViewControllers uses a type in BeatLeader.UI.MainMenu.
- The types involved
BeatLeader.ViewControllers.ResultsScreenUI→BeatLeader.UI.MainMenu.BeatLeaderNewsViewController
- Direction
- BeatLeader.ViewControllers uses BeatLeader.UI.MainMenu, so a change to BeatLeader.UI.MainMenu can break BeatLeader.ViewControllers, while a change to BeatLeader.ViewControllers can't break BeatLeader.UI.MainMenu.
- Position
- Below the diagonal: BeatLeader.ViewControllers uses a module listed above it, which is the healthy direction.
30→29 BeatLeader.ViewControllers uses BeatLeader.Components✕
- Connections
- 17 pairs of types, where a type in BeatLeader.ViewControllers uses a type in BeatLeader.Components.
- The types involved
BeatLeader.ViewControllers.LeaderboardPanel→BeatLeader.Components.ExperienceBarBeatLeader.ViewControllers.LeaderboardPanel→BeatLeader.Components.LogoBeatLeader.ViewControllers.LeaderboardPanel→BeatLeader.Components.PlayerInfoBeatLeader.ViewControllers.LeaderboardPanel→BeatLeader.Components.StatusBarBeatLeader.ViewControllers.LeaderboardView→BeatLeader.Components.ContextSelectorBeatLeader.ViewControllers.LeaderboardView→BeatLeader.Components.EmptyBoardMessageBeatLeader.ViewControllers.LeaderboardView→BeatLeader.Components.MainScoresTableBeatLeader.ViewControllers.LeaderboardView→BeatLeader.Components.MapDifficultyPanelBeatLeader.ViewControllers.LeaderboardView→BeatLeader.Components.PaginationBeatLeader.ViewControllers.LeaderboardView→BeatLeader.Components.ScopeSelectorBeatLeader.ViewControllers.LeaderboardView→BeatLeader.Components.VotingButtonBeatLeader.ViewControllers.PreParser→BeatLeader.Components.ExperienceBarBeatLeader.ViewControllers.PreParser→BeatLeader.Components.LogoBeatLeader.ViewControllers.PreParser→BeatLeader.Components.PlayerInfoBeatLeader.ViewControllers.PreParser→BeatLeader.Components.StatusBarBeatLeader.ViewControllers.ResultsScreenUI→BeatLeader.Components.ReplayButtonBeatLeader.ViewControllers.ResultsScreenUI→BeatLeader.Components.VotingButton
- Direction
- BeatLeader.ViewControllers uses BeatLeader.Components, so a change to BeatLeader.Components can break BeatLeader.ViewControllers, while a change to BeatLeader.ViewControllers can't break BeatLeader.Components.
- Position
- Below the diagonal: BeatLeader.ViewControllers uses a module listed above it, which is the healthy direction.
30→31 BeatLeader.ViewControllers uses BeatLeader part of a loop✕
- Connections
- 3 pairs of types, where a type in BeatLeader.ViewControllers uses a type in BeatLeader.
- The types involved
BeatLeader.ViewControllers.LeaderboardView→BeatLeader.IReplayerViewNavigatorBeatLeader.ViewControllers.LeaderboardView→BeatLeader.ReplayerViewNavigatorWrapperBeatLeader.ViewControllers.ResultsScreenUI→BeatLeader.ReeUIComponentV2
- Direction
- BeatLeader.ViewControllers uses BeatLeader, so a change to BeatLeader can break BeatLeader.ViewControllers, while a change to BeatLeader.ViewControllers can't break BeatLeader.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→11 BeatLeader uses BeatLeader.Models.Replay✕
- Connections
- 11 pairs of types, where a type in BeatLeader uses a type in BeatLeader.Models.Replay.
- The types involved
BeatLeader.HeckNavigationController→BeatLeader.Models.Replay.ReplayBeatLeader.IReplayerViewNavigator→BeatLeader.Models.Replay.ReplayBeatLeader.ReplayRecorder→BeatLeader.Models.Replay.NoteCutInfoBeatLeader.ReplayRecorder→BeatLeader.Models.Replay.NoteEventBeatLeader.ReplayRecorder→BeatLeader.Models.Replay.PauseBeatLeader.ReplayRecorder→BeatLeader.Models.Replay.QuaternionBeatLeader.ReplayRecorder→BeatLeader.Models.Replay.ReplayBeatLeader.ReplayRecorder→BeatLeader.Models.Replay.Vector3BeatLeader.ReplayRecorder→BeatLeader.Models.Replay.WallEventBeatLeader.ReplayerViewNavigator→BeatLeader.Models.Replay.ReplayBeatLeader.ReplayerViewNavigatorWrapper→BeatLeader.Models.Replay.Replay
- Direction
- BeatLeader uses BeatLeader.Models.Replay, so a change to BeatLeader.Models.Replay can break BeatLeader, while a change to BeatLeader can't break BeatLeader.Models.Replay.
- Position
- Below the diagonal: BeatLeader uses a module listed above it, which is the healthy direction.
31→12 BeatLeader uses BeatLeader.Themes✕
- Connections
- 1 pair of types, where a type in BeatLeader uses a type in BeatLeader.Themes.
- The types involved
BeatLeader.BundleLoader→BeatLeader.Themes.ThemesCollection
- Direction
- BeatLeader uses BeatLeader.Themes, so a change to BeatLeader.Themes can break BeatLeader, while a change to BeatLeader can't break BeatLeader.Themes.
- Position
- Below the diagonal: BeatLeader uses a module listed above it, which is the healthy direction.
31→15 BeatLeader uses BeatLeader.Core.Managers.ReplayEnhancer✕
- Connections
- 1 pair of types, where a type in BeatLeader uses a type in BeatLeader.Core.Managers.ReplayEnhancer.
- The types involved
BeatLeader.ReplayRecorder→BeatLeader.Core.Managers.ReplayEnhancer.TrackingDeviceEnhancer
- Direction
- BeatLeader uses BeatLeader.Core.Managers.ReplayEnhancer, so a change to BeatLeader.Core.Managers.ReplayEnhancer can break BeatLeader, while a change to BeatLeader can't break BeatLeader.Core.Managers.ReplayEnhancer.
- Position
- Below the diagonal: BeatLeader uses a module listed above it, which is the healthy direction.
31→16 BeatLeader uses BeatLeader.Replayer✕
- Connections
- 2 pairs of types, where a type in BeatLeader uses a type in BeatLeader.Replayer.
- The types involved
BeatLeader.HeckNavigationController→BeatLeader.Replayer.ReplayerMenuLoaderBeatLeader.ReplayerViewNavigator→BeatLeader.Replayer.ReplayerMenuLoader
- Direction
- BeatLeader uses BeatLeader.Replayer, so a change to BeatLeader.Replayer can break BeatLeader, while a change to BeatLeader can't break BeatLeader.Replayer.
- Position
- Below the diagonal: BeatLeader uses a module listed above it, which is the healthy direction.
31→18 BeatLeader uses BeatLeader.Models✕
- Connections
- 48 pairs of types, where a type in BeatLeader uses a type in BeatLeader.Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BeatLeader.AvatarStorage→BeatLeader.Models.AvatarImageBeatLeader.ConfigDefaults→BeatLeader.Models.BeatLeaderServerBeatLeader.ConfigDefaults→BeatLeader.Models.LeaderboardDisplaySettingsBeatLeader.ConfigDefaults→BeatLeader.Models.ReplaySaveOptionBeatLeader.ConfigDefaults→BeatLeader.Models.ReplayerSettingsBeatLeader.ConfigDefaults→BeatLeader.Models.ScoreRowCellTypeBeatLeader.ConfigFileData→BeatLeader.Models.BeatLeaderServerBeatLeader.ConfigFileData→BeatLeader.Models.LeaderboardDisplaySettingsBeatLeader.ConfigFileData→BeatLeader.Models.ReplaySaveOptionBeatLeader.ConfigFileData→BeatLeader.Models.ReplayerSettingsBeatLeader.ConfigFileData→BeatLeader.Models.ScoreRowCellTypeBeatLeader.EventsProcessor→BeatLeader.Models.IEventsProcessorBeatLeader.FormatUtils→BeatLeader.Models.DiffInfoBeatLeader.FormatUtils→BeatLeader.Models.PlayerRoleBeatLeader.FormatUtils→BeatLeader.Models.RankedStatusBeatLeader.GameplayModifiersPanelPatch→BeatLeader.Models.ModifiersMapBeatLeader.GameplayModifiersPanelPatch→BeatLeader.Models.ModifiersRatingBeatLeader.HeckNavigationController→BeatLeader.Models.BeatmapLevelWithKeyBeatLeader.HeckNavigationController→BeatLeader.Models.IReplayHeaderBeatLeader.HeckNavigationController→BeatLeader.Models.PlayerBeatLeader.IReplayerViewNavigator→BeatLeader.Models.BeatmapLevelWithKeyBeatLeader.IReplayerViewNavigator→BeatLeader.Models.IReplayHeaderBeatLeader.IReplayerViewNavigator→BeatLeader.Models.PlayerBeatLeader.IScoreRowContent→BeatLeader.Models.ScoreRowCellTypeBeatLeader.LeaderboardState→BeatLeader.Models.LeaderboardKey
- Direction
- BeatLeader uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader, while a change to BeatLeader can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader uses a module listed above it, which is the healthy direction.
31→26 BeatLeader uses BeatLeader.UI.Hub✕
- Connections
- 4 pairs of types, where a type in BeatLeader uses a type in BeatLeader.UI.Hub.
- The types involved
BeatLeader.BeatLeaderHubFlowCoordinator→BeatLeader.UI.Hub.BeatLeaderHubMainViewControllerBeatLeader.ReplayerViewNavigator→BeatLeader.UI.Hub.BattleRoyaleFlowCoordinatorBeatLeader.ReplayerViewNavigator→BeatLeader.UI.Hub.ReplayManagerFlowCoordinatorBeatLeader.SettingsPanelUI→BeatLeader.UI.Hub.BeatLeaderSettingsView
- Direction
- BeatLeader uses BeatLeader.UI.Hub, so a change to BeatLeader.UI.Hub can break BeatLeader, while a change to BeatLeader can't break BeatLeader.UI.Hub.
- Position
- Below the diagonal: BeatLeader uses a module listed above it, which is the healthy direction.
31→27 BeatLeader uses BeatLeader.UI.MainMenu✕
- Connections
- 1 pair of types, where a type in BeatLeader uses a type in BeatLeader.UI.MainMenu.
- The types involved
BeatLeader.MainFlowCoordinatorDidActivatePatch→BeatLeader.UI.MainMenu.BeatLeaderNewsViewController
- Direction
- BeatLeader uses BeatLeader.UI.MainMenu, so a change to BeatLeader.UI.MainMenu can break BeatLeader, while a change to BeatLeader can't break BeatLeader.UI.MainMenu.
- Position
- Below the diagonal: BeatLeader uses a module listed above it, which is the healthy direction.
31→29 BeatLeader uses BeatLeader.Components✕
- Connections
- 2 pairs of types, where a type in BeatLeader uses a type in BeatLeader.Components.
- The types involved
BeatLeader.LeaderboardHeaderManager→BeatLeader.Components.LeaderboardInfoPanelBeatLeader.ScoresTableLayoutHelper→BeatLeader.Components.AbstractScoreRowCell
- Direction
- BeatLeader uses BeatLeader.Components, so a change to BeatLeader.Components can break BeatLeader, while a change to BeatLeader can't break BeatLeader.Components.
- Position
- Below the diagonal: BeatLeader uses a module listed above it, which is the healthy direction.
31→30 BeatLeader uses BeatLeader.ViewControllers✕
- Connections
- 3 pairs of types, where a type in BeatLeader uses a type in BeatLeader.ViewControllers.
- The types involved
BeatLeader.BeatLeaderCustomLeaderboard→BeatLeader.ViewControllers.LeaderboardPanelBeatLeader.BeatLeaderCustomLeaderboard→BeatLeader.ViewControllers.LeaderboardViewBeatLeader.LeaderboardHeaderManager→BeatLeader.ViewControllers.LeaderboardView
- Direction
- BeatLeader uses BeatLeader.ViewControllers, so a change to BeatLeader.ViewControllers can break BeatLeader, while a change to BeatLeader can't break BeatLeader.ViewControllers.
- Position
- Below the diagonal: BeatLeader uses a module listed above it, which is the healthy direction.
32→30 BeatLeader.UIPatches uses BeatLeader.ViewControllers✕
- Connections
- 1 pair of types, where a type in BeatLeader.UIPatches uses a type in BeatLeader.ViewControllers.
- The types involved
BeatLeader.UIPatches.ResultsViewControllerPatches→BeatLeader.ViewControllers.ResultsScreenUI
- Direction
- BeatLeader.UIPatches uses BeatLeader.ViewControllers, so a change to BeatLeader.ViewControllers can break BeatLeader.UIPatches, while a change to BeatLeader.UIPatches can't break BeatLeader.ViewControllers.
- Position
- Below the diagonal: BeatLeader.UIPatches uses a module listed above it, which is the healthy direction.
33→4 BeatLeader.API uses BeatLeader.Models.BeatSaver✕
- Connections
- 1 pair of types, where a type in BeatLeader.API uses a type in BeatLeader.Models.BeatSaver.
- The types involved
BeatLeader.API.MapDetailRequest→BeatLeader.Models.BeatSaver.MapDetail
- Direction
- BeatLeader.API uses BeatLeader.Models.BeatSaver, so a change to BeatLeader.Models.BeatSaver can break BeatLeader.API, while a change to BeatLeader.API can't break BeatLeader.Models.BeatSaver.
- Position
- Below the diagonal: BeatLeader.API uses a module listed above it, which is the healthy direction.
33→11 BeatLeader.API uses BeatLeader.Models.Replay✕
- Connections
- 3 pairs of types, where a type in BeatLeader.API uses a type in BeatLeader.Models.Replay.
- The types involved
BeatLeader.API.DownloadReplayRequest→BeatLeader.Models.Replay.ReplayBeatLeader.API.ReplayResponseParser→BeatLeader.Models.Replay.ReplayBeatLeader.API.UploadReplayRequest→BeatLeader.Models.Replay.Replay
- Direction
- BeatLeader.API uses BeatLeader.Models.Replay, so a change to BeatLeader.Models.Replay can break BeatLeader.API, while a change to BeatLeader.API can't break BeatLeader.Models.Replay.
- Position
- Below the diagonal: BeatLeader.API uses a module listed above it, which is the healthy direction.
33→18 BeatLeader.API uses BeatLeader.Models✕
- Connections
- 16 pairs of types, where a type in BeatLeader.API uses a type in BeatLeader.Models.
- The types involved
BeatLeader.API.AddFriendRequest→BeatLeader.Models.PlayerBeatLeader.API.AddFriendRequestCustomParser→BeatLeader.Models.PlayerBeatLeader.API.ContextsRequest→BeatLeader.Models.ServerScoresContextBeatLeader.API.GetAvatarRequest→BeatLeader.Models.AvatarSettingsBeatLeader.API.LeaderboardsRequest→BeatLeader.Models.MassLeaderboardsInfoResponseBeatLeader.API.LeaderboardsRequest→BeatLeader.Models.PagedBeatLeader.API.MapTypesRequest→BeatLeader.Models.MapsTypeDescriptionBeatLeader.API.PlatformEventStatusRequest→BeatLeader.Models.PlatformEventStatusBeatLeader.API.PlatformEventsRequest→BeatLeader.Models.PagedBeatLeader.API.PlatformEventsRequest→BeatLeader.Models.PlatformEventBeatLeader.API.PlayerRequest→BeatLeader.Models.PlayerBeatLeader.API.RemoveFriendRequest→BeatLeader.Models.PlayerBeatLeader.API.RemoveFriendRequestCustomParser→BeatLeader.Models.PlayerBeatLeader.API.UpdateAvatarRequest→BeatLeader.Models.AvatarSettingsBeatLeader.API.UploadReplayRequest→BeatLeader.Models.PlayEndDataBeatLeader.API.VoteRequest→BeatLeader.Models.Vote
- Direction
- BeatLeader.API uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.API, while a change to BeatLeader.API can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.API uses a module listed above it, which is the healthy direction.
33→23 BeatLeader.API uses BeatLeader.WebRequests✕
- Connections
- 62 pairs of types, where a type in BeatLeader.API uses a type in BeatLeader.WebRequests. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BeatLeader.API.AddFriendRequest→BeatLeader.WebRequests.PersistentSingletonWebRequestBaseBeatLeader.API.AddFriendRequestCustomParser→BeatLeader.WebRequests.IWebRequestResponseParserBeatLeader.API.AuthRequest→BeatLeader.WebRequests.IWebRequestBeatLeader.API.AuthRequest→BeatLeader.WebRequests.PersistentWebRequestBaseBeatLeader.API.ClanPlayersRequest→BeatLeader.WebRequests.PersistentSingletonWebRequestBaseBeatLeader.API.ClanPlayersResponseParser→BeatLeader.WebRequests.IWebRequestResponseParserBeatLeader.API.ClanPlayersResponseParser→BeatLeader.WebRequests.JsonResponseParserBeatLeader.API.ClanScoreResponseParser→BeatLeader.WebRequests.IWebRequestResponseParserBeatLeader.API.ClanScoreResponseParser→BeatLeader.WebRequests.JsonResponseParserBeatLeader.API.ClanScoresRequest→BeatLeader.WebRequests.PersistentSingletonWebRequestBaseBeatLeader.API.ContextsRequest→BeatLeader.WebRequests.IWebRequestBeatLeader.API.ContextsRequest→BeatLeader.WebRequests.PersistentWebRequestBaseBeatLeader.API.DownloadMapRequest→BeatLeader.WebRequests.IWebRequestBeatLeader.API.DownloadMapRequest→BeatLeader.WebRequests.PersistentWebRequestBaseBeatLeader.API.DownloadMapRequest→BeatLeader.WebRequests.WebRequestParamsBeatLeader.API.DownloadReplayRequest→BeatLeader.WebRequests.IWebRequestBeatLeader.API.DownloadReplayRequest→BeatLeader.WebRequests.PersistentWebRequestBaseBeatLeader.API.GetAvatarRequest→BeatLeader.WebRequests.IWebRequestBeatLeader.API.GetAvatarRequest→BeatLeader.WebRequests.PersistentWebRequestBaseBeatLeader.API.GetOculusUserRequest→BeatLeader.WebRequests.PersistentSingletonWebRequestBaseBeatLeader.API.LatestReleasesRequest→BeatLeader.WebRequests.PersistentSingletonWebRequestBaseBeatLeader.API.LeaderboardRequest→BeatLeader.WebRequests.PersistentSingletonWebRequestBaseBeatLeader.API.LeaderboardsRequest→BeatLeader.WebRequests.IWebRequestBeatLeader.API.LeaderboardsRequest→BeatLeader.WebRequests.PersistentWebRequestBaseBeatLeader.API.MapDetailRequest→BeatLeader.WebRequests.IWebRequest
- Direction
- BeatLeader.API uses BeatLeader.WebRequests, so a change to BeatLeader.WebRequests can break BeatLeader.API, while a change to BeatLeader.API can't break BeatLeader.WebRequests.
- Position
- Below the diagonal: BeatLeader.API uses a module listed above it, which is the healthy direction.
33→31 BeatLeader.API uses BeatLeader✕
- Connections
- 4 pairs of types, where a type in BeatLeader.API uses a type in BeatLeader.
- The types involved
BeatLeader.API.ClanPlayersResponseParser→BeatLeader.ScoresTableContentBeatLeader.API.ClanScoreResponseParser→BeatLeader.ScoresTableContentBeatLeader.API.ScoreResponseParser→BeatLeader.ScoresTableContentBeatLeader.API.ScoresOfClanResponseParser→BeatLeader.ScoresTableContent
- Direction
- BeatLeader.API uses BeatLeader, so a change to BeatLeader can break BeatLeader.API, while a change to BeatLeader.API can't break BeatLeader.
- Position
- Below the diagonal: BeatLeader.API uses a module listed above it, which is the healthy direction.
34→18 BeatLeader.Interop uses BeatLeader.Models✕
- Connections
- 6 pairs of types, where a type in BeatLeader.Interop uses a type in BeatLeader.Models.
- The types involved
BeatLeader.Interop.BeatSaviorInterop→BeatLeader.Models.ReplayLaunchDataBeatLeader.Interop.Cam2Interop→BeatLeader.Models.IVirtualPlayerMovementProcessorBeatLeader.Interop.Cam2Interop→BeatLeader.Models.ReplayLaunchDataBeatLeader.Interop.PoseReceiver→BeatLeader.Models.IVirtualPlayerPoseReceiverBeatLeader.Interop.ScoreSaberInterop→BeatLeader.Models.ReplayLaunchDataBeatLeader.Interop.SongCoreInterop→BeatLeader.Models.BeatmapLevelWithKey
- Direction
- BeatLeader.Interop uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Interop, while a change to BeatLeader.Interop can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.Interop uses a module listed above it, which is the healthy direction.
34→24 BeatLeader.Interop uses BeatLeader.DataManager✕
- Connections
- 1 pair of types, where a type in BeatLeader.Interop uses a type in BeatLeader.DataManager.
- The types involved
BeatLeader.Interop.BetterSongListInterop→BeatLeader.DataManager.SortEntry
- Direction
- BeatLeader.Interop uses BeatLeader.DataManager, so a change to BeatLeader.DataManager can break BeatLeader.Interop, while a change to BeatLeader.Interop can't break BeatLeader.DataManager.
- Position
- Below the diagonal: BeatLeader.Interop uses a module listed above it, which is the healthy direction.
34→31 BeatLeader.Interop uses BeatLeader✕
- Connections
- 6 pairs of types, where a type in BeatLeader.Interop uses a type in BeatLeader.
- The types involved
BeatLeader.Interop.BeatSaviorInterop→BeatLeader.HarmonyAutoPatchBeatLeader.Interop.Cam2Interop→BeatLeader.HarmonyAutoPatchBeatLeader.Interop.CountersPlusInterop→BeatLeader.HarmonyAutoPatchBeatLeader.Interop.CountersPlusInterop→BeatLeader.HarmonyPatchDescriptorBeatLeader.Interop.NoodleExtensionsInterop→BeatLeader.HarmonyAutoPatchBeatLeader.Interop.ScoreSaberInterop→BeatLeader.HarmonyMultisilencer
- Direction
- BeatLeader.Interop uses BeatLeader, so a change to BeatLeader can break BeatLeader.Interop, while a change to BeatLeader.Interop can't break BeatLeader.
- Position
- Below the diagonal: BeatLeader.Interop uses a module listed above it, which is the healthy direction.
35→18 BeatLeader.Replayer.Tweaking uses BeatLeader.Models✕
- Connections
- 10 pairs of types, where a type in BeatLeader.Replayer.Tweaking uses a type in BeatLeader.Models.
- The types involved
BeatLeader.Replayer.Tweaking.GameTweak→BeatLeader.Models.ZenjectComponentModelBeatLeader.Replayer.Tweaking.InteropsLoaderTweak→BeatLeader.Models.IBeatmapTimeControllerBeatLeader.Replayer.Tweaking.InteropsLoaderTweak→BeatLeader.Models.IVirtualPlayerBeatLeader.Replayer.Tweaking.InteropsLoaderTweak→BeatLeader.Models.IVirtualPlayersManagerBeatLeader.Replayer.Tweaking.JumpDistanceTweak→BeatLeader.Models.ReplayLaunchDataBeatLeader.Replayer.Tweaking.ReplayFailTweak→BeatLeader.Models.IReplayTimeControllerBeatLeader.Replayer.Tweaking.ReplayFailTweak→BeatLeader.Models.ReplayLaunchDataBeatLeader.Replayer.Tweaking.ReplayFinishTweak→BeatLeader.Models.IReplayFinishControllerBeatLeader.Replayer.Tweaking.ReplayFinishTweak→BeatLeader.Models.IReplayPauseControllerBeatLeader.Replayer.Tweaking.ReplayFinishTweak→BeatLeader.Models.IReplayTimeController
- Direction
- BeatLeader.Replayer.Tweaking uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Replayer.Tweaking, while a change to BeatLeader.Replayer.Tweaking can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.Replayer.Tweaking uses a module listed above it, which is the healthy direction.
35→31 BeatLeader.Replayer.Tweaking uses BeatLeader✕
- Connections
- 11 pairs of types, where a type in BeatLeader.Replayer.Tweaking uses a type in BeatLeader.
- The types involved
BeatLeader.Replayer.Tweaking.AudioTimeSyncControllerTweak→BeatLeader.HarmonyAutoPatchBeatLeader.Replayer.Tweaking.AudioTimeSyncControllerTweak→BeatLeader.HarmonyPatchDescriptorBeatLeader.Replayer.Tweaking.JumpDistanceTweak→BeatLeader.HarmonyAutoPatchBeatLeader.Replayer.Tweaking.JumpDistanceTweak→BeatLeader.HarmonyPatchDescriptorBeatLeader.Replayer.Tweaking.MethodsSilencerTweak→BeatLeader.HarmonyMultisilencerBeatLeader.Replayer.Tweaking.RaycastBlockerTweak→BeatLeader.HarmonyAutoPatchBeatLeader.Replayer.Tweaking.RaycastBlockerTweak→BeatLeader.HarmonyPatchDescriptorBeatLeader.Replayer.Tweaking.ScoringTweak→BeatLeader.HarmonyAutoPatchBeatLeader.Replayer.Tweaking.ScoringTweak→BeatLeader.HarmonyPatchDescriptorBeatLeader.Replayer.Tweaking.SiraFPFCTweak→BeatLeader.HarmonyAutoPatchBeatLeader.Replayer.Tweaking.SiraFPFCTweak→BeatLeader.HarmonySilencer
- Direction
- BeatLeader.Replayer.Tweaking uses BeatLeader, so a change to BeatLeader can break BeatLeader.Replayer.Tweaking, while a change to BeatLeader.Replayer.Tweaking can't break BeatLeader.
- Position
- Below the diagonal: BeatLeader.Replayer.Tweaking uses a module listed above it, which is the healthy direction.
36→2 BeatLeader.Utils uses BeatLeader.Attributes✕
- Connections
- 1 pair of types, where a type in BeatLeader.Utils uses a type in BeatLeader.Attributes.
- The types involved
BeatLeader.Utils.InteropLoader→BeatLeader.Attributes.PluginInteropAttribute
- Direction
- BeatLeader.Utils uses BeatLeader.Attributes, so a change to BeatLeader.Attributes can break BeatLeader.Utils, while a change to BeatLeader.Utils can't break BeatLeader.Attributes.
- Position
- Below the diagonal: BeatLeader.Utils uses a module listed above it, which is the healthy direction.
36→10 BeatLeader.Utils uses BeatLeader.Models.AbstractReplay✕
- Connections
- 8 pairs of types, where a type in BeatLeader.Utils uses a type in BeatLeader.Models.AbstractReplay.
- The types involved
BeatLeader.Utils.AbstractReplayUtils→BeatLeader.Models.AbstractReplay.IReplayBeatLeader.Utils.AbstractReplayUtils→BeatLeader.Models.AbstractReplay.NoteEventBeatLeader.Utils.MirroredReplayNoteComparator→BeatLeader.Models.AbstractReplay.NoteEventBeatLeader.Utils.ReplayDataUtils→BeatLeader.Models.AbstractReplay.BattleRoyaleReplayDataBeatLeader.Utils.ReplayDataUtils→BeatLeader.Models.AbstractReplay.IReplayBeatLeader.Utils.ReplayDataUtils→BeatLeader.Models.AbstractReplay.IReplayNoteComparatorBeatLeader.Utils.ReplayNoteComparator→BeatLeader.Models.AbstractReplay.IReplayNoteComparatorBeatLeader.Utils.ReplayNoteComparator→BeatLeader.Models.AbstractReplay.NoteEvent
- Direction
- BeatLeader.Utils uses BeatLeader.Models.AbstractReplay, so a change to BeatLeader.Models.AbstractReplay can break BeatLeader.Utils, while a change to BeatLeader.Utils can't break BeatLeader.Models.AbstractReplay.
- Position
- Below the diagonal: BeatLeader.Utils uses a module listed above it, which is the healthy direction.
36→11 BeatLeader.Utils uses BeatLeader.Models.Replay✕
- Connections
- 10 pairs of types, where a type in BeatLeader.Utils uses a type in BeatLeader.Models.Replay.
- The types involved
BeatLeader.Utils.FileManager→BeatLeader.Models.Replay.ReplayBeatLeader.Utils.FileManager→BeatLeader.Models.Replay.ReplayInfoBeatLeader.Utils.ReplayDataUtils→BeatLeader.Models.Replay.ReplayBeatLeader.Utils.ReplayDataUtils→BeatLeader.Models.Replay.ReplayInfoBeatLeader.Utils.ReplayManager→BeatLeader.Models.Replay.ReplayBeatLeader.Utils.ReplayManager→BeatLeader.Models.Replay.ReplayInfoBeatLeader.Utils.ReplayStatisticUtils→BeatLeader.Models.Replay.NoteEventBeatLeader.Utils.ReplayStatisticUtils→BeatLeader.Models.Replay.ReplayBeatLeader.Utils.ReplayUtils→BeatLeader.Models.Replay.ReplayBeatLeader.Utils.ScoreUtil→BeatLeader.Models.Replay.Replay
- Direction
- BeatLeader.Utils uses BeatLeader.Models.Replay, so a change to BeatLeader.Models.Replay can break BeatLeader.Utils, while a change to BeatLeader.Utils can't break BeatLeader.Models.Replay.
- Position
- Below the diagonal: BeatLeader.Utils uses a module listed above it, which is the healthy direction.
36→18 BeatLeader.Utils uses BeatLeader.Models✕
- Connections
- 21 pairs of types, where a type in BeatLeader.Utils uses a type in BeatLeader.Models.
- The types involved
BeatLeader.Utils.ModifiersUtils→BeatLeader.Models.ModifiersMapBeatLeader.Utils.ReplayDataUtils→BeatLeader.Models.IPlayerBeatLeader.Utils.ReplayManager→BeatLeader.Models.IReplayHashProviderBeatLeader.Utils.ReplayManager→BeatLeader.Models.IReplayHeaderBeatLeader.Utils.ReplayManager→BeatLeader.Models.IReplayInfoBeatLeader.Utils.ReplayManager→BeatLeader.Models.PhysicalReplayHeaderBeatLeader.Utils.ReplayManager→BeatLeader.Models.PlayEndDataBeatLeader.Utils.ReplayManager→BeatLeader.Models.PlayerBeatLeader.Utils.ReplayManager→BeatLeader.Models.ReplaySavingResultBeatLeader.Utils.ReplayManagerCache→BeatLeader.Models.PlayerBeatLeader.Utils.ReplayMetadataManager→BeatLeader.Models.ReplayMetadataBeatLeader.Utils.ReplayMetadataManager→BeatLeader.Models.ReplayTagBeatLeader.Utils.ReplayMetadataManager→BeatLeader.Models.ReplayTagValidationResultBeatLeader.Utils.ReplayStatisticUtils→BeatLeader.Models.AccuracyTrackerBeatLeader.Utils.ReplayStatisticUtils→BeatLeader.Models.ScoreGraphTrackerBeatLeader.Utils.ReplayStatisticUtils→BeatLeader.Models.ScoreStatsBeatLeader.Utils.ReplayUtils→BeatLeader.Models.ModifiersMapBeatLeader.Utils.ReplayUtils→BeatLeader.Models.ScoreBeatLeader.Utils.ScoreUtil→BeatLeader.Models.PlayEndDataBeatLeader.Utils.StreamUtils→BeatLeader.Models.IIoOperationDescriptorBeatLeader.Utils.UnityExtensions→BeatLeader.Models.SerializablePose
- Direction
- BeatLeader.Utils uses BeatLeader.Models, so a change to BeatLeader.Models can break BeatLeader.Utils, while a change to BeatLeader.Utils can't break BeatLeader.Models.
- Position
- Below the diagonal: BeatLeader.Utils uses a module listed above it, which is the healthy direction.
36→31 BeatLeader.Utils uses BeatLeader✕
- Connections
- 2 pairs of types, where a type in BeatLeader.Utils uses a type in BeatLeader.
- The types involved
BeatLeader.Utils.ReplayMetadataManager→BeatLeader.AppCacheBeatLeader.Utils.UnityResourcesHelper→BeatLeader.FirstResourceAttribute
- Direction
- BeatLeader.Utils uses BeatLeader, so a change to BeatLeader can break BeatLeader.Utils, while a change to BeatLeader.Utils can't break BeatLeader.
- Position
- Below the diagonal: BeatLeader.Utils 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
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 29 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | High / Critical |
Roadmap
Top priorities: Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler; Resolve the 1 No automated tests finding(s) in Code Coverage; Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. | +7.8 pts | Medium | Access Controls |
| Resolve the 8 redundant comment finding(s) in Comment Value — start with RecorderMultiplayerUtilPatch.cs (4), AddFriendRequest.cs, RemoveFriendRequest.cs. | +2.4 pts | Low | Comment Value |
| Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them. | +4.8 pts | Medium | Web-Security Posture |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +7.4 pts | High | Code Coverage |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +3.2 pts | Medium | Security & performance tooling |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.5 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.5 | Slop | Static Analysis (SAST): High: REDACTED |
| Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs | 3.0 | Slop | Explicit Debt: WriteOnlyPrivateField |
| Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs | 3.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| Source/.editorconfig | 5.2 | Mixed | Explicit Debt: AnalyzerSeverityNone |
| REDACTED | 5.7 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs | 6.0 | Mixed | Explicit Debt: Dead code: GetPositiveMultiplier |
| Source/7_Utils/FormatUtils.cs | 6.0 | Mixed | Explicit Debt: ObsoleteWithCallers |
| Source/8_UI/MainMenu/OtherNews/EventNewsPanel.cs | 6.3 | Mixed | Code Duplication: Duplicated block (26 lines × 2) |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| Source/7_Utils/Interop/Interops/Cam2Interop.cs | 6.4 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| Source/2_Core/API/PersistentWebRequest.cs | 6.6 | Mixed | Explicit Debt: ObsoleteWithCallers |
| Source/8_UI/Components/Reactive/Native/ValueAnimator.cs | 6.7 | Mixed | Explicit Debt: ObsoleteWithCallers |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| Source/7_Utils/UtilityClasses/GifLoader.cs | 7.1 | Near-clean | Cyclomatic Complexity: GIFImageBlock.DrawTo (cyclomatic 18) |
| Source/7_Utils/Interop/Interops/BetterSongListInterop.cs | 7.1 | Near-clean | Code Duplication: Edited copy of a member (31 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 62 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 62 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, 441 of 467 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
- D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `Source/manifest.json`, `Source/9_Resources/Localization.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- AX2 Stateful singletons — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 28 further occurrence(s) are not listed individually; the score already reflects all 68.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ReplayUtils.HMDFromName at 71. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ReplayUtils.HMDToName at 35 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Source/2_Core/Localization/BLLocalization.cs (BLLocalization.GetLanguageName at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ReplayUtils.HMDFromName (cyclomatic 71), ReplayUtils.ControllerFromName (cyclomatic 43), ReplayStatisticUtils.Accuracy (cyclomatic 38). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 8.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
10 method(s) exceeded the cognitive complexity threshold of 15; the worst was ReplayStatisticUtils.Accuracy at 72.
What to do
- Bring the 10 bodies over 15 down to 15 or less in Cognitive Complexity — start with ReplayStatisticUtils.Accuracy (cognitive 72), ReplayUtils.HMDFromName (cognitive 70), ReplayUtils.ControllerFromName (cognitive 41). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 10 together lifts Cognitive Complexity from 7.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
7 god class(es) detected.
What to do
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with ReplayStatisticUtils.cs, SpecialEventBar.cs, BeatmapPreviewPanel.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with TimeLocalizationUtils.cs, FormatUtils.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with Replay.cs, GifLoader.cs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
17 duplicated block group(s) detected. 2.8 % of the production lines (1,192 of 42,862) are in a reported copy. A further 30 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 4 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with ReflectionUtils.cs, ValueAnimator.cs, ReplayStatisticsPanel.cs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication — start with Score.cs (2), BeatmapCharacteristicPanel.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with BetterSongListInterop.cs, WebRequestFactory.cs, LayoutEditorWindow.cs. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 252 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
3 outdated, 0 vulnerable, 0 deprecated, 1 prerelease packages.
What to do
- Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 100 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 4 direct `PackageReference`(s), and 96 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
22 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Source/8_UI/Replayer/Components/Toolbar/Timeline.cs. Counted over 252 of the 618 production source files in this repository: 362 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
D17 · Explicit Debt
51 deducted debt markers + 23 dead symbols across 42862 LoC in the .NET projects (0.9/KLoC) → score 8.2.
What to do
- Resolve the 14 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (14). — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 7 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Cam2Interop.cs (2), BeatSaviorInterop.cs, CountersPlusInterop.cs. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with MapPreviewDialog.cs (3), SteamVRWebConsoleSession.cs, FileManager.cs. — One of this dimension's main actionable groups (6 issue-level).
D18 · Solution Shape
1 projects, 619 source files, 42862 hand-written lines of code (42862 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 0 inter-project edges (build failed).
What to do
- Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
D24 · Comment Value
8 of 135 judged comments only repeat the code they sit on (5.9 %). 12 comment(s) in another language or script were not judged.
What to do
- Resolve the 8 redundant comment finding(s) in Comment Value — start with RecorderMultiplayerUtilPatch.cs (4), AddFriendRequest.cs, RemoveFriendRequest.cs. — One of this dimension's main actionable groups (8 recommendation-level).
D26 · Project Cohesion
One project, `BeatLeader` (42862 LoC, 338 public types across 25 namespaces): over its size bounds, but its parts reference each other, so it reads as one coherent unit.
D27 · Navigability
38 % of calls cross a namespace and 3 % go through an interface, but 64 % of collaborators are co-located — so following a call takes several hops. Baseline: medium — clean/modular boundaries expected.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
29 finding(s): 0 critical, 10 high, 19 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
39 of 256 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Source/2_Core/Localization/TimeLocalizationUtils.cs. Counted over 256 of the 618 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with TimeLocalizationUtils.cs, ReplayRecorder.cs. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 37 Orphaned file finding(s) in Knowledge Freshness — start with BetterSongListInterop.cs, ReplayUtils.cs, MiniProfileButtons.cs. — One of this dimension's main actionable groups (37 recommendation-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: EventNewsPanel.cs↔MapNewsPanel.cs 82%; ReplayerNotesCutter.cs↔ReplayerScoreProcessor.cs 60%; EventNewsPanel.cs↔MapPreviewPanel.cs 57%
What to do
- Resolve the 6 Change coupling finding(s) in Change Coupling — start with EventNewsPanel.cs (2), REDACTED (2), ReplayerNotesCutter.cs. — One of this dimension's main actionable groups (6 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX2 · Stateful singletons
- `AppCache` is not registered, but `ReplayHeadersCache` creates it and keeps it in the static `infoCache`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_loadTask, _cache, _initialized, _saveTask; e.g. `_loadTask` at line 41). — Source/7_Utils/UtilityClasses/AppCache.cs:9
- `WebRequestParams` is not registered, but `DownloadMapRequest` creates it and keeps it in the static `RequestParams`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (UploadTrackingPrecision, DownloadTrackingPrecision; e.g. `UploadTrackingPrecision` at line 14). — Source/2_Core/API/Models/WebRequestParams.cs:5
- `ReplayLaunchData` is not registered, but `ReplayerMenuLoader` creates it and keeps it in the static `ReplayerLauncher.LaunchData`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_replays, _beatmapLevel, _settings, EnvironmentInfo, ReplayerBindings; e.g. `_replays` at line 18). — Source/2_Core/Models/Replayer/ReplayLaunchData.cs:10
- `PoseReceiver` is not registered, but `Cam2Interop` creates it and keeps it in the static `poseReceiver`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Position, Rotation; e.g. `Position` at line 67). — Source/7_Utils/Interop/Interops/Cam2Interop.cs:62
- `HarmonyMultisilencer` is not registered, but `ScoreSaberInterop` creates it and keeps it in the static `_installatorsSilencer`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_atLeastOneSilencerIsEnabled; e.g. `_atLeastOneSilencerIsEnabled` at line 20). — Source/0_Harmony/HarmonyMultisilencer.cs:9
- `ReplayManagerSearchTheme` is not registered, but the singleton `BeatLeaderHubTheme` creates it and keeps it in `ReplayManagerSearchTheme`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_searchHighlightColor, _searchHighlightStyle; e.g. `_searchHighlightColor` at line 10). — Source/8_UI/Models/Style/ReplayManagerSearchTheme.cs:6
- `BodySettings` is not registered, but the singleton `ReplayerSettings` creates it and keeps it in `BodySettings`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (Configs, _serializedConfigs; e.g. `Configs` at line 23). — Source/2_Core/Models/Replayer/BodySettings.cs:13
- `SerializableColorSet` is not registered, but the singleton `BeatLeaderHubMenuButtonsTheme` creates it and keeps it in `ReplayManagerButtonColors`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_activeColor, _hoveredColor, _notInteractableColor, _color; e.g. `_activeColor` at line 14). — Source/8_UI/Models/Style/SerializableColorSet.cs:10
- `HarmonyHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_harmony, _initialized; e.g. `_harmony` at line 13). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/HarmonyHelper.cs:6
- `HarmonySilencer` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (silencersRegistry; e.g. `silencersRegistry` at line 23). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/HarmonySilencer.cs:8
- `PlayerActiveStateChangedEventPatch` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (spectator; e.g. `spectator` at line 51). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:43
- `MainFlowCoordinatorDidActivatePatch` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_viewController; e.g. `_viewController` at line 18). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/UIPatches/MainFlowCoordinatorPatch.cs:8
- `MainFlowCoordinatorWillChangePatch` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (mainCoordinator, changingToMain; e.g. `mainCoordinator` at line 32). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/UIPatches/MainFlowCoordinatorPatch.cs:24
- `ConfigFileData` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Instance; e.g. `Instance` at line 25). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/1_Config/ConfigFileData.cs:13
- `BLLocalization` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_baseGameLanguage, _blLanguageAnalog, translations, _lastUsedLanguage; e.g. `_baseGameLanguage` at line 14). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Localization/BLLocalization.cs:8
- `LeaderboardState` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_selectedBeatmapKey, IsAnyBeatmapSelected, SelectedLeaderboardKey, _selectedBeatmapLevel, _isVisible, _scoresScope; e.g. `_selectedBeatmapKey` at line 30). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/Leaderboard/LeaderboardState.cs:6
- `ModifiersMapManager` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (CurrentModifiersMap; e.g. `CurrentModifiersMap` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/ModifiersMapManager.cs:11
- `ReplayRecorder` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_instance; e.g. `_instance` at line 191). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/ReplayRecorder.cs:20
- `BundleLoader` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_ready, MonkeyPrefab, AccuracyGraphPrefab, ThemesCollection, SaberPrefab, HeadPrefab; e.g. `_ready` at line 34). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/3_AssetBundle/BundleLoader.cs:12
- `ReeModalSystem` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ActiveModals; e.g. `ActiveModals` at line 36). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/8_UI/Abstract/ReeModalSystem.cs:12
- `AvatarStorage` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Cache; e.g. `Cache` at line 22). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/8_UI/AvatarStorage.cs:16
- `HeckNavigationController` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_playViewManagerStartMethod, _playViewManagerEarlyDismissMethod, _playViewManagerInitMethod, _playViewManagerActivateMethod, _playViewManagerFlowCoordinatorField, _playViewManagerViewControllersField; e.g. `_playViewManagerStartMethod` at line 91). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:15
- `ModPanelUI` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_tabActive; e.g. `_tabActive` at line 17). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/8_UI/ModPanel/ModPanelUI.cs:7
- `ReeUIComponentV2` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (BsmlCache; e.g. `BsmlCache` at line 23). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/8_UI/ReeUIComponentV2.cs:15
- `StatsStorage` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (cachedReplayStats; e.g. `cachedReplayStats` at line 9). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/8_UI/StatsStorage.cs:5
- `Plugin` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (UserAgent; e.g. `UserAgent` at line 53). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Plugin.cs:13
- `EnvironmentManagerPatch` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_environmentType; e.g. `_environmentType` at line 11). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/MiscellaneousPatches/EnvironmentManagerPatch.cs:6
- `ResultsViewControllerPatches` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_resultsScreen; e.g. `_resultsScreen` at line 14). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/0_Harmony/UIPatches/ResultsViewControllerPatch.cs:6
- `Authentication` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Platform, _signedIn, _taskSource; e.g. `Platform` at line 26). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/API/Authentication.cs:14
- `PersistentSingletonWebRequestBase` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (tokenSource, Instance; e.g. `tokenSource` at line 87). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/API/PersistentWebRequest.cs:66
- `OnGameplayCoreInstaller` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_submissionTicket; e.g. `_submissionTicket` at line 160). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Installers/OnGameplayCoreInstaller.cs:24
- `OnMenuInstaller` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_container; e.g. `_container` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Installers/OnMenuInstaller.cs:16
- `HiddenPlayersCache` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (HiddenPlayers; e.g. `HiddenPlayers` at line 48). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/HiddenPlayersCache.cs:10
- `LeaderboardInfoManager` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_taskSource; e.g. `_taskSource` at line 20). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/LeaderboardInfoManager.cs:10
- `LeaderboardsCache` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (LeaderboardInfoCache, SortingCache, LastCheckTime; e.g. `LeaderboardInfoCache` at line 39). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/LeaderboardsCache.cs:12
- `MapTypesManager` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_mapTypes, _sprites; e.g. `_mapTypes` at line 30). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/MapTypesManager.cs:13
- `ModVersionChecker` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_latestReleaseInfo, _isUpToDate; e.g. `_latestReleaseInfo` at line 29). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/ModVersionChecker.cs:8
- `OculusMigrationManager` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_isMigrationRequired; e.g. `_isMigrationRequired` at line 20). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/OculusMigrationManager.cs:9
- `PrestigeLevelsManager` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_mainThreadSynchronizationContext, _loading, _totalLevels, _processedLevels, _lastSyncTime, _icons; e.g. `_mainThreadSynchronizationContext` at line 39). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/PrestigeLevelsManager.cs:15
- `ProfileManager` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_profile, HasProfile, _profileLoadTaskCompletionSource, friends, _initialized, Roles; e.g. `_profile` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/2_Core/Managers/DataManager/ProfileManager.cs:12
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- The namespaces BeatLeader ↔ BeatLeader.Components ↔ BeatLeader.Core.Managers.ReplayEnhancer ↔ BeatLeader.DataManager ↔ BeatLeader.Manager ↔ BeatLeader.Models ↔ BeatLeader.Models.AbstractReplay ↔ BeatLeader.Models.Replay ↔ BeatLeader.Replayer ↔ BeatLeader.Replayer.Emulation ↔ BeatLeader.Results ↔ BeatLeader.Themes ↔ BeatLeader.UI ↔ BeatLeader.UI.Hub ↔ BeatLeader.UI.MainMenu ↔ BeatLeader.UI.Replayer ↔ BeatLeader.ViewControllers ↔ BeatLeader.WebRequests depend on each other. The lightest dependency in the cycle is BeatLeader → BeatLeader.Core.Managers.ReplayEnhancer (BeatLeader.ReplayRecorder → BeatLeader.Core.Managers.ReplayEnhancer.TrackingDeviceEnhancer, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Source/2_Core/Managers/ReplayRecorder.cs:5
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
- ~42.9k production LoC (853 types) across 1 project(s) / 39 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
What to do
- Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
AX6 · Interface segregation
C2 · Access Controls
- No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
- `BeatmapTimeController.Rewind` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:86
- `BeatmapTimeController.SetSpeedMultiplier` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:134
- `BeatmapVisualsController.PauseCutScoreSpawner` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/2_Core/Replayer/BeatmapVisualsController.cs:101
- `BeatmapVisualsController.PauseSabersSparkles` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/2_Core/Replayer/BeatmapVisualsController.cs:105
- `BeatmapVisualsController.ModifyLevelFailedTextEffect` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/2_Core/Replayer/BeatmapVisualsController.cs:116
- `BeatmapVisualsController.ModifyComboPanel` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/2_Core/Replayer/BeatmapVisualsController.cs:120
- `BeatmapVisualsController.ModifyEnergyPanel` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/2_Core/Replayer/BeatmapVisualsController.cs:131
- `BeatmapVisualsController.ModifyDebrisPhysics` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/2_Core/Replayer/BeatmapVisualsController.cs:154
- `ReplayerCameraController.SetFov` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:35
- `ReplayerCameraController.SetView` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:48
- `BeatAvatarController.SetVisuals` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/2_Core/Replayer/Emulation/Players/Avatar/BeatAvatarController.cs:18
- `MenuBeatAvatarController.SetLoading` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:45
- `MenuBeatAvatarController.Present` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:55
- `MenuBeatAvatarController.Hide` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:67
- `NoteControllerEmulator.Setup` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/2_Core/Replayer/Emulation/Scoring/NoteControllerEmulator.cs:19
- `ReplayFinishController.Exit` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:53
- `ReplayPauseController.Pause` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:68
- `ReplayPauseController.Resume` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:81
- `DummyViewController.Init` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:15
- `LevelSelectionViewController.Dismiss` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:216
- `ReplayManagerViewController.NavigateToReplay` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:35
- `HeckNavigationController.NavigateToReplayAsync` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:31
- `HeckNavigationController.Initialize` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:88
- `HeckNavigationController.Dispose` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:120
- `HeckNavigationController.NavigateToReplayManager` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:170
- `HeckNavigationController.NavigateToBattleRoyale` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:174
- `SmoothHoverController.AddStateListener` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:35
- `SmoothHoverController.RemoveStateListener` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:40
- `SmoothHoverController.OnPointerEnter` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:84
- `SmoothHoverController.OnPointerExit` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:90
- `BeatLeaderNewsViewController.RefreshEventsCache` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:51
- `ReplayerDesktopViewController.SwitchViewMode` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:50
- `ReplayerFloatingPanelResetController.Setup` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Source/8_UI/Replayer/VR/ReplayerFloatingPanelResetController.cs:13
- `ReplayerFloatingViewController.Setup` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:29
What to do
- Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — Source/7_Utils/UtilityClasses/GifLoader.cs:346, Source/7_Utils/UtilityClasses/GifLoader.cs:350
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `DrawTo` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Source/7_Utils/UtilityClasses/GifLoader.cs:346
- `Dispose` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Source/7_Utils/UtilityClasses/GifLoader.cs:350
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×10) — Source/2_Core/Installers/OnGameplayCoreInstaller.cs:60, Source/3_AssetBundle/BundleLoader.cs:93, Source/7_Utils/Interop/Interops/CustomNotesInterop.cs:53, …
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
- The root README is 116 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:7
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:365
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — REDACTED:44
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `new(httpClientHandler)` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out. — Source/2_Core/API/WebRequestFactory.cs:14
What to do
- Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
PF3 · Async & latency hygiene
- 2 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `_loadTask.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — Source/7_Utils/UtilityClasses/AppCache.cs:46
- `_saveTask.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — Source/7_Utils/UtilityClasses/AppCache.cs:80
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
- No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
- `BeatmapTimeController.Rewind` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:86
- `BeatmapTimeController.SetSpeedMultiplier` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:134
- `BeatmapVisualsController.PauseCutScoreSpawner` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/BeatmapVisualsController.cs:101
- `BeatmapVisualsController.PauseSabersSparkles` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/BeatmapVisualsController.cs:105
- `BeatmapVisualsController.ModifyLevelFailedTextEffect` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/BeatmapVisualsController.cs:116
- `BeatmapVisualsController.ModifyComboPanel` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/BeatmapVisualsController.cs:120
- `BeatmapVisualsController.ModifyEnergyPanel` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/BeatmapVisualsController.cs:131
- `BeatmapVisualsController.ModifyDebrisPhysics` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/BeatmapVisualsController.cs:154
- `ReplayerCameraController.SetFov` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:35
- `ReplayerCameraController.SetView` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:48
- `BeatAvatarController.SetVisuals` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/Emulation/Players/Avatar/BeatAvatarController.cs:18
- `MenuBeatAvatarController.SetLoading` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:45
- `MenuBeatAvatarController.Present` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:55
- `NoteControllerEmulator.Setup` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/2_Core/Replayer/Emulation/Scoring/NoteControllerEmulator.cs:19
- `ReplayPauseController.Pause` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:68
- `ReplayPauseController.Resume` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:81
- `DummyViewController.Init` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:15
- `LevelSelectionViewController.Dismiss` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:216
- `ReplayManagerViewController.NavigateToReplay` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:35
- `HeckNavigationController.NavigateToReplayAsync` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:31
- `HeckNavigationController.NavigateToReplayManager` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:170
- `HeckNavigationController.NavigateToBattleRoyale` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:174
- `SmoothHoverController.AddStateListener` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:35
- `SmoothHoverController.RemoveStateListener` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:40
- `SmoothHoverController.OnPointerEnter` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:84
- `SmoothHoverController.OnPointerExit` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:90
- `ReplayerFloatingPanelResetController.Setup` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — Source/8_UI/Replayer/VR/ReplayerFloatingPanelResetController.cs:13
- `ReplayerFloatingViewController.Setup` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:29
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
- Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
- Validate inbound models (ModelState/[ApiController]/FluentValidation) to reduce injection and bad-data risk.
X1 · Async correctness
- Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. — Source/2_Core/Managers/DataManager/OculusMigrationManager.cs:74
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×2) — Source/7_Utils/UtilityClasses/AppCache.cs:46, Source/7_Utils/UtilityClasses/AppCache.cs:80
- `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×11) — Source/8_UI/FlowCoordinator/BeatLeaderHubAvatarController.cs:40, Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/BattleRoyaleFlowCoordinator.cs:189, REDACTED:35, …
What to do
- Sync-over-async (deadlock risk) through `.Result`
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `WebRequestProcessor` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_requestMessage` itself (line 236), which makes that instance its own. But `_requestMessage` is named in none of the methods the disposal search covered: `Dispose` (line 361), `ReleaseBufferIfNeeded` (line 353) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_requestMessage?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Source/2_Core/API/WebRequestProcessor.cs:236
- `WebRequestProcessor` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_cancellationTokenSource` itself (line 243), which makes that instance its own. But `_cancellationTokenSource` is named in none of the methods the disposal search covered: `Dispose` (line 361), `ReleaseBufferIfNeeded` (line 353) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_cancellationTokenSource?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Source/2_Core/API/WebRequestProcessor.cs:243
- `cts` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 44). Every use of it in `UpdateAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cts = …;`), which releases it at the end of the scope on every path including a throw. — Source/2_Core/Managers/SteamVR/SteamVRSettings.cs:44
- `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 50) a new instance is written over it — but `Refresh` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `Refresh` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Avatars/BattleRoyaleAvatar.cs:50
- `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 41) a new instance is written over it — but `SetAvatar` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `SetAvatar` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/GreetingsView/ReplaysPreviewPanel.cs:41
- `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 183) a new instance is written over it — but `OnInit` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `OnInit` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/OpponentsView/BattleRoyaleOpponentsList.cs:183
- `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 110) a new instance is written over it — but `SetData` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `SetData` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/BeatmapReplayLaunchPanel/BasicReplayDetailPanel.cs:110
- `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 242) a new instance is written over it — but `OnClose` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `OnClose` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/ReplayDetail/BeatmapDownloadDialog.cs:242
- `tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 125) a new instance is written over it — but `UpdateAvatar` itself reads through `tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `UpdateAvatar` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/Leaderboard/Components/Basic/PlayerAvatar.cs:125
- `_tokenSource` is a `CancellationTokenSource` this type creates itself, and here (line 59) a new instance is written over it — but `CancelDownloading` itself reads through `_tokenSource` before replacing it, so it expects an instance to be there, and nothing earlier in `CancelDownloading` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_tokenSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/Leaderboard/Components/Header/DownloadScoresModal.cs:59
- `_downloadCancellationSource` is a `CancellationTokenSource` this type creates itself, and here (line 212) a new instance is written over it — but `OnResume` itself reads through `_downloadCancellationSource` before replacing it, so it expects an instance to be there, and nothing earlier in `OnResume` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_downloadCancellationSource?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:212
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X2 · Cancellation propagation
- Only 41/89 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×38) — Source/2_Core/API/Authentication.cs:29, Source/2_Core/API/Authentication.cs:34, Source/2_Core/API/Authentication.cs:76, …
- No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. — Source/2_Core/API/WebRequestProcessor.cs:310
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×3) — Source/2_Core/Managers/DataManager/LeaderboardManager.cs:82, Source/8_UI/Leaderboard/Components/ScoreInfoPanel/MiniProfile.cs:79, Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:253
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — Source/2_Core/Managers/SteamVR/SteamVRWebConsoleSession.cs:108, Source/7_Utils/FileManager.cs:162, Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:102, …
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- This method contradicts itself about `player`: line 47 assigns it with `as IPlayer`, which hands back null rather than throwing when the value is not a `IPlayer`, but line 53 then dereferences it directly as `player.AvatarUrl` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `player` once before the first use and handle the null case, or cast with `(IPlayer)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/GreetingsView/ReplaysPreviewPanel.cs:53
- This method contradicts itself about `player`: line 217 assigns it with `as IPlayer`, which hands back null rather than throwing when the value is not a `IPlayer`, but line 224 then dereferences it directly as `player.Name` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `player` once before the first use and handle the null case, or cast with `(IPlayer)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/OpponentsView/BattleRoyaleOpponentsList.cs:224
- This method contradicts itself about `player`: line 151 assigns it with `as IPlayer`, which hands back null rather than throwing when the value is not a `IPlayer`, but line 154 then dereferences it directly as `player.Id` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `player` once before the first use and handle the null case, or cast with `(IPlayer)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/BeatmapReplayLaunchPanel/BasicReplayDetailPanel.cs:154
- ~4.7 `!` suppressions per 1k syntax nodes — 1000 suppression(s) across the 212494 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 61.8 | Adequate — gated by D18 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 55.6 | Adequate — gated by AX2, AX5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 49.4 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 29.8 | Weak — gated by D8, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 26.3 | Weak — gated by D29, D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 70.0 | Strong | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 50 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D19 Documentation Quality — D19 withholds "XML-doc coverage": 1 candidate(s) (1 of them low-coverage Warnings on library projects) were measured and not published.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 9 candidate(s) found and not reported.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's C# was read, and every log call in it goes through a logger that takes one finished message — its own wrapper, log4net, Console or Debug — so an interpolated message there loses nothing the API could have kept. Calls through Microsoft.Extensions.Logging, Serilog, NLog or ZLogger, or any logger with a message-template overload, would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 44 finding(s)
- AnalyzerSeverityNone Source/.editorconfig:142
- AnalyzerSeverityNone Source/.editorconfig:143
- AnalyzerSeverityNone Source/.editorconfig:144
- AnalyzerSeverityNone Source/.editorconfig:145
- AnalyzerSeverityNone Source/.editorconfig:146
- AnalyzerSeverityNone Source/.editorconfig:148
- AnalyzerSeverityNone Source/.editorconfig:149
- AnalyzerSeverityNone Source/.editorconfig:150
- AnalyzerSeverityNone Source/.editorconfig:151
- AnalyzerSeverityNone Source/.editorconfig:152
- AnalyzerSeverityNone Source/.editorconfig:153
- AnalyzerSeverityNone Source/.editorconfig:154
- AnalyzerSeverityNone Source/.editorconfig:155
- AnalyzerSeverityNone Source/.editorconfig:158
- WriteOnlyPrivateField Source/7_Utils/Interop/Interops/BeatSaviorInterop.cs:20
- WriteOnlyPrivateField Source/7_Utils/Interop/Interops/Cam2Interop.cs:93
- WriteOnlyPrivateField Source/7_Utils/Interop/Interops/Cam2Interop.cs:94
- WriteOnlyPrivateField Source/7_Utils/Interop/Interops/CountersPlusInterop.cs:18
- WriteOnlyPrivateField Source/7_Utils/Interop/Interops/NoodleExtensionsInterop.cs:15
- WriteOnlyPrivateField Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:80
- WriteOnlyPrivateField Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:92
- EmptyCatchBlock Source/2_Core/Managers/SteamVR/SteamVRWebConsoleSession.cs:108
- EmptyCatchBlock Source/7_Utils/FileManager.cs:162
- EmptyCatchBlock Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:102
- EmptyCatchBlock Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:170
- EmptyCatchBlock Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:197
- EmptyCatchBlock Source/8_UI/MainMenu/SpecialEvent/SpecialEventMapPanel.cs:165
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileScopedPragmaDisable Source/8_UI/MainMenu/OtherNews/MapNewsPanel.cs:11
- FileScopedPragmaDisable Source/8_UI/MainMenu/TextNews/TextNewsPanel.cs:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge Source/2_Core/Localization/TimeLocalizationUtils.cs:1
- Orphaned knowledge Source/2_Core/Managers/ReplayRecorder.cs:1
- Namespace dependency cycle Source/2_Core/Managers/ReplayRecorder.cs:5
- REDACTED
- No automated tests
Serious — 303 finding(s)
- Async method without CancellationToken: PlatformTicket Source/2_Core/API/Authentication.cs:29
- Async method without CancellationToken: PlatformTicketInternal Source/2_Core/API/Authentication.cs:34
- Async method without CancellationToken: Login Source/2_Core/API/Authentication.cs:76
- Async method without CancellationToken: Send Source/2_Core/API/Methods/GetOculusUserRequest.cs:14
- Async method without CancellationToken: LoadIconAsync Source/2_Core/Managers/DataManager/LeaderboardContextsManager.cs:47
- Async method without CancellationToken: LoadIconAsync Source/2_Core/Managers/DataManager/MapTypesManager.cs:44
- Async method without CancellationToken: LoadIconAsync Source/2_Core/Managers/DataManager/PrestigeLevelsManager.cs:73
- Async method without CancellationToken: DetectAsync Source/2_Core/Managers/SteamVR/SteamVRControllerDetector.cs:14
- Async method without CancellationToken: DetectAsync Source/2_Core/Managers/SteamVR/SteamVRHeadsetDetector.cs:23
- Async method without CancellationToken: CreateEditorFlowCoordinator Source/2_Core/Replayer/Emulation/Players/Avatar/BeatAvatarLoader.cs:93
- Async method without CancellationToken: StartReplayFromLeaderboardAsync Source/2_Core/Replayer/ReplayerMenuLoader.cs:54
- Async method without CancellationToken: LoadBeatmapForLeaderboardAsync Source/2_Core/Replayer/ReplayerMenuLoader.cs:77
- Async method without CancellationToken: LoadAndAppendReplay Source/2_Core/Replayer/ReplayerMenuLoader.cs:160
- Async method without CancellationToken: StartLastReplayAsync Source/2_Core/Replayer/ReplayerMenuLoader.cs:263
- Async method without CancellationToken: CanLaunchReplay Source/2_Core/Replayer/ReplayerMenuLoader.cs:290
- Async method without CancellationToken: LoadOptionalDataAsync Source/2_Core/Replayer/ReplayerMenuLoader.cs:393
- Async method without CancellationToken: InstallBeatmap Source/7_Utils/FileManager.cs:19
- Async method without CancellationToken: ExtractFiles Source/7_Utils/FileManager.cs:34
- Async method without CancellationToken: Awake Source/8_UI/FlowCoordinator/BeatLeaderHubAvatarController.cs:40
- Async method without CancellationToken: UploadAvatar Source/8_UI/FlowCoordinator/BeatLeaderHubAvatarController.cs:70
- Async method without CancellationToken: LoadAvatar Source/8_UI/FlowCoordinator/BeatLeaderHubAvatarController.cs:89
- Async method without CancellationToken: LoadAvatarFromPlayerAsync Source/8_UI/FlowCoordinator/BeatLeaderHubAvatarController.cs:103
- Async method without CancellationToken: SetData Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Avatars/BattleRoyaleReplayBadge.cs:15
- Async method without CancellationToken: LaunchBattle Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/BattleRoyaleFlowCoordinator.cs:189
- Async method without CancellationToken: SetBeatmap Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/GreetingsView/BeatmapPreviewPanel.cs:45
- No authorization
- No authorization REDACTED:86
- No authorization REDACTED:134
- No authorization Source/2_Core/Replayer/BeatmapVisualsController.cs:101
- No authorization Source/2_Core/Replayer/BeatmapVisualsController.cs:105
- No authorization Source/2_Core/Replayer/BeatmapVisualsController.cs:116
- No authorization Source/2_Core/Replayer/BeatmapVisualsController.cs:120
- No authorization Source/2_Core/Replayer/BeatmapVisualsController.cs:131
- No authorization Source/2_Core/Replayer/BeatmapVisualsController.cs:154
- No authorization REDACTED:35
- No authorization REDACTED:48
- No authorization Source/2_Core/Replayer/Emulation/Players/Avatar/BeatAvatarController.cs:18
- No authorization REDACTED:45
- No authorization REDACTED:55
- No authorization REDACTED:67
- No authorization Source/2_Core/Replayer/Emulation/Scoring/NoteControllerEmulator.cs:19
- No authorization REDACTED:53
- No authorization REDACTED:68
- No authorization REDACTED:81
- No authorization REDACTED:15
- No authorization REDACTED:216
- No authorization REDACTED:35
- No authorization Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:31
- No authorization Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:88
- No authorization Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:120
- Process-global static state: HarmonyHelper Source/0_Harmony/HarmonyHelper.cs:6
- Process-global static state: HarmonySilencer Source/0_Harmony/HarmonySilencer.cs:8
- Process-global static state: PlayerActiveStateChangedEventPatch Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:43
- Process-global static state: MainFlowCoordinatorDidActivatePatch Source/0_Harmony/UIPatches/MainFlowCoordinatorPatch.cs:8
- Process-global static state: MainFlowCoordinatorWillChangePatch Source/0_Harmony/UIPatches/MainFlowCoordinatorPatch.cs:24
- Process-global static state: ConfigFileData Source/1_Config/ConfigFileData.cs:13
- Process-global static state: BLLocalization Source/2_Core/Localization/BLLocalization.cs:8
- Process-global static state: LeaderboardState Source/2_Core/Managers/Leaderboard/LeaderboardState.cs:6
- Process-global static state: ModifiersMapManager Source/2_Core/Managers/ModifiersMapManager.cs:11
- Process-global static state: ReplayRecorder Source/2_Core/Managers/ReplayRecorder.cs:20
- Process-global static state: BundleLoader Source/3_AssetBundle/BundleLoader.cs:12
- Process-global static state: ReeModalSystem Source/8_UI/Abstract/ReeModalSystem.cs:12
- Process-global static state: AvatarStorage Source/8_UI/AvatarStorage.cs:16
- Process-global static state: HeckNavigationController Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:15
- Process-global static state: ModPanelUI Source/8_UI/ModPanel/ModPanelUI.cs:7
- Process-global static state: ReeUIComponentV2 Source/8_UI/ReeUIComponentV2.cs:15
- Process-global static state: StatsStorage Source/8_UI/StatsStorage.cs:5
- Process-global static state: Plugin Source/Plugin.cs:13
- Process-global static state: EnvironmentManagerPatch Source/0_Harmony/MiscellaneousPatches/EnvironmentManagerPatch.cs:6
- Process-global static state: ResultsViewControllerPatches Source/0_Harmony/UIPatches/ResultsViewControllerPatch.cs:6
- Process-global static state: Authentication Source/2_Core/API/Authentication.cs:14
- Process-global static state: PersistentSingletonWebRequestBase Source/2_Core/API/PersistentWebRequest.cs:66
- Process-global static state: OnGameplayCoreInstaller Source/2_Core/Installers/OnGameplayCoreInstaller.cs:24
- Process-global static state: OnMenuInstaller Source/2_Core/Installers/OnMenuInstaller.cs:16
- Process-global static state: HiddenPlayersCache Source/2_Core/Managers/DataManager/HiddenPlayersCache.cs:10
- Dead code: Postfix Source/0_Harmony/InstallersPatches/MultiplayerLevelDataEnhancerPatch.cs:8
- Dead code: Postfix Source/0_Harmony/InstallersPatches/PostSwingRatingEnhancerPatch.cs:26
- Dead code: Postfix Source/0_Harmony/InstallersPatches/PreSwingRatingEnhancerPatch.cs:12
- Dead code: ImplicitTypeConverter Source/1_Config/Json/ImplicitTypeConverter.cs:6
- Dead code: OnMainServerChanged Source/2_Core/Managers/DataManager/ProfileManager.cs:136
- Dead code: ExMachinaBasicResponse Source/2_Core/Models/API/BeatLeader/ExMachinaResponse.cs:2
- Dead code: LateTickablePoolItem Source/2_Core/Models/Zenject/LateTickablePoolItem.cs:4
- Dead code: BattleRoyaleHeadVRController Source/3_AssetBundle/Replayer/BattleRoyale/BattleRoyaleHeadVRController.cs:4
- Dead code: BattleRoyaleSaberVRController Source/3_AssetBundle/Replayer/BattleRoyale/BattleRoyaleSaberVRController.cs:4
- Dead code: OnValidate Source/3_AssetBundle/Replayer/BattleRoyale/BattleRoyaleVRController.cs:29
- Dead code: MaterialDuplicator Source/3_AssetBundle/Replayer/BattleRoyale/MaterialDuplicator.cs:4
- Dead code: DespawnCustomBomb Source/7_Utils/Interop/Interops/CustomNotesInterop.cs:71
- Dead code: ScoreSaberInterop Source/7_Utils/Interop/Interops/ScoreSaberInterop.cs:10
- Dead code: GetPositiveMultiplier Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:305
- Dead code: GetNegativeMultiplier Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:313
- Dead code: ReplayFilePattern Source/7_Utils/Replays/ReplayManager.cs:22
- Dead code: ObservableDictionary Source/7_Utils/UtilityClasses/ObservableDictionary.cs:6
- Dead code: SliderValuesApplier Source/7_Utils/UtilityClasses/SliderValuesApplier.cs:6
- Dead code: ExMachinaVisibleToRole Source/8_UI/Leaderboard/Components/Header/LeaderboardInfoPanel.cs:383
- Dead code: RtToolsVisibleToRole Source/8_UI/Leaderboard/Components/Header/LeaderboardInfoPanel.cs:387
- Dead code: StarSymbol Source/8_UI/Leaderboard/Components/Header/SkillTriangle.cs:37
- Dead code: ContextsModalOption Source/8_UI/Leaderboard/Components/MainPanel/Contexts/ContextsModalOption.cs:10
- Dead code: HandlePositionOffsetChanged Source/8_UI/Replayer/Components/Settings/Views/CameraView/ViewParams/PlayerViewCameraParams.cs:130
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment Source/0_Harmony/HarmonyMultisilencer.cs:8
- TodoComment Source/2_Core/Managers/ModifiersMapManager.cs:10
- TodoComment Source/2_Core/Models/API/BeatLeader/LeaderboardsInfoResponse.cs:107
- TodoComment Source/2_Core/Installers/OnGameplayCoreInstaller.cs:205
- TodoComment REDACTED:177
- TodoComment Source/2_Core/Replayer/Emulation/Players/Avatar/BeatAvatarLoader.cs:50
- TodoComment Source/2_Core/Replayer/ReplayBeatmapData.cs:31
- TodoComment Source/2_Core/Replayer/Tweaking/Tweaks/JumpDistanceTweak.cs:23
- TodoComment Source/2_Core/Replayer/Tweaking/Tweaks/ReplayFailTweak.cs:19
- TodoComment Source/7_Utils/Replays/ReplayManager.cs:465
- TodoComment Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:96
- TodoComment Source/8_UI/MainMenu/NewsViewPanel.cs:16
- async void method: Awake Source/8_UI/FlowCoordinator/BeatLeaderHubAvatarController.cs:40
- async void method: LaunchBattle Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/BattleRoyaleFlowCoordinator.cs:189
- async void method: NavigateToReplay REDACTED:35
- async void method: LoadPreview Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/ReplayPreviewLoader.cs:19
- async void method: OnInitialize Source/8_UI/FlowCoordinator/HubViews/BeatLeaderHubMainViewController.cs:132
- async void method: OpenSongOrDownloadDialog Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:43
- async void method: Download Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:111
- async void method: OpenSongOrDownloadDialog Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:98
- async void method: HandlePlayButtonClicked Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:217
- async void method: ParseSelfIfNeeded Source/8_UI/ReeUIComponentV2.cs:205
- async void method: LoadAndAssignImage Source/8_UI/Replayer/Components/BeatmapLevelPreview.cs:98
- ObsoleteWithCallers Source/2_Core/API/PersistentWebRequest.cs:116
- ObsoleteWithCallers Source/2_Core/API/PersistentWebRequest.cs:122
- ObsoleteWithCallers Source/2_Core/API/PersistentWebRequest.cs:136
- ObsoleteWithCallers Source/2_Core/API/PersistentWebRequest.cs:156
- ObsoleteWithCallers Source/2_Core/Replayer/ReplayerCache.cs:6
- ObsoleteWithCallers Source/7_Utils/FormatUtils.cs:147
- ObsoleteWithCallers Source/7_Utils/FormatUtils.cs:153
- ObsoleteWithCallers Source/8_UI/Abstract/ReeModalSystem.cs:12
- ObsoleteWithCallers Source/8_UI/Components/Reactive/Native/ValueAnimator.cs:5
- Stateful shared instance: AppCache Source/7_Utils/UtilityClasses/AppCache.cs:9
- Stateful shared instance: WebRequestParams Source/2_Core/API/Models/WebRequestParams.cs:5
- Stateful shared instance: ReplayLaunchData Source/2_Core/Models/Replayer/ReplayLaunchData.cs:10
- Stateful shared instance: PoseReceiver Source/7_Utils/Interop/Interops/Cam2Interop.cs:62
- Stateful shared instance: HarmonyMultisilencer Source/0_Harmony/HarmonyMultisilencer.cs:9
- Stateful shared instance: ReplayManagerSearchTheme Source/8_UI/Models/Style/ReplayManagerSearchTheme.cs:6
- Stateful shared instance: BodySettings Source/2_Core/Models/Replayer/BodySettings.cs:13
- Stateful shared instance: SerializableColorSet Source/8_UI/Models/Style/SerializableColorSet.cs:10
- Owned disposable field overwritten without releasing the previous instance Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Avatars/BattleRoyaleAvatar.cs:50
- Owned disposable field overwritten without releasing the previous instance Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/GreetingsView/ReplaysPreviewPanel.cs:41
- Owned disposable field overwritten without releasing the previous instance Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/OpponentsView/BattleRoyaleOpponentsList.cs:183
- Owned disposable field overwritten without releasing the previous instance Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/BeatmapReplayLaunchPanel/BasicReplayDetailPanel.cs:110
- Owned disposable field overwritten without releasing the previous instance Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/ReplayDetail/BeatmapDownloadDialog.cs:242
- Owned disposable field overwritten without releasing the previous instance Source/8_UI/Leaderboard/Components/Basic/PlayerAvatar.cs:125
- Owned disposable field overwritten without releasing the previous instance Source/8_UI/Leaderboard/Components/Header/DownloadScoresModal.cs:59
- Owned disposable field overwritten without releasing the previous instance Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:212
- Change coupling: EventNewsPanel.cs ↔ MapNewsPanel.cs Source/8_UI/MainMenu/OtherNews/EventNewsPanel.cs:1
- Change coupling: ReplayerNotesCutter.cs ↔ ReplayerScoreProcessor.cs Source/2_Core/Replayer/Emulation/ReplayerNotesCutter.cs:1
- Change coupling: EventNewsPanel.cs ↔ MapPreviewPanel.cs Source/8_UI/MainMenu/OtherNews/EventNewsPanel.cs:1
- Change coupling: REDACTED ↔ MapNewsPanel.cs REDACTED:1
- Change coupling: REDACTED ↔ ReplayTimeController.cs REDACTED:1
- Change coupling: REDACTED ↔ SpecialEventPanel.cs REDACTED:1
- Swallowed exception (empty catch) Source/2_Core/Managers/SteamVR/SteamVRWebConsoleSession.cs:108
- Swallowed exception (empty catch) Source/7_Utils/FileManager.cs:162
- Swallowed exception (empty catch) Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:102
- Swallowed exception (empty catch) Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:170
- Swallowed exception (empty catch) Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:197
- Swallowed exception (empty catch) Source/8_UI/MainMenu/SpecialEvent/SpecialEventMapPanel.cs:165
- Edited copy of a member (9 corresponding lines) Source/7_Utils/ReflectionUtils.cs:64
- Edited copy of a member (9 corresponding lines) Source/8_UI/Components/Reactive/Native/ValueAnimator.cs:44
- Edited copy of a member (9 corresponding lines) Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/BeatmapReplayLaunchPanel/ReplayStatisticsPanel.cs:158
- Edited copy of a member (9 corresponding lines) Source/2_Core/API/Methods/ClanPlayersRequest.cs:81
- MethodTooLong: ReplayStatisticUtils.Accuracy Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:192
- MethodTooLong: SpecialEventBar.Construct Source/8_UI/MainMenu/SpecialEvent/SpecialEventBar.cs:35
- MethodTooLong: BeatmapPreviewPanel.Construct Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/GreetingsView/BeatmapPreviewPanel.cs:92
- Edited copy of a member (17 corresponding lines) Source/2_Core/Models/API/BeatLeader/Score.cs:61
- Edited copy of a member (17 corresponding lines) Source/2_Core/Models/API/BeatLeader/Score.cs:43
- Edited copy of a member (17 corresponding lines) Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/FiltersPanel/BeatmapFilter/BeatmapCharacteristicPanel.cs:55
- Edited copy of a member (7 corresponding lines) Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:349
- Edited copy of a member (7 corresponding lines) Source/2_Core/API/WebRequestFactory.cs:26
- Edited copy of a member (7 corresponding lines) Source/8_UI/Replayer/Components/LayoutEditor/EditorWindow/LayoutEditorWindow.cs:328
- Duplicated block (13 lines × 2) Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:250
- Duplicated block (13 lines × 2) Source/7_Utils/UtilityClasses/GifLoader.cs:579
- Duplicated block (13 lines × 2) Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:53
- Sync-over-async blocking
- Sync-over-async blocking Source/7_Utils/UtilityClasses/AppCache.cs:46
- Sync-over-async blocking Source/7_Utils/UtilityClasses/AppCache.cs:80
- Swallowed exception (caught, then discarded) Source/2_Core/Managers/DataManager/LeaderboardManager.cs:82
- Swallowed exception (caught, then discarded) Source/8_UI/Leaderboard/Components/ScoreInfoPanel/MiniProfile.cs:79
- Swallowed exception (caught, then discarded) Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:253
- Symbol treated as nullable, then dereferenced unguarded Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/GreetingsView/ReplaysPreviewPanel.cs:53
- Symbol treated as nullable, then dereferenced unguarded Source/8_UI/FlowCoordinator/Flows/BattleRoyaleFlow/Views/OpponentsView/BattleRoyaleOpponentsList.cs:224
- Symbol treated as nullable, then dereferenced unguarded Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/BeatmapReplayLaunchPanel/BasicReplayDetailPanel.cs:154
- REDACTED
- REDACTED
- TooManyMethods: TimeLocalizationUtils Source/2_Core/Localization/TimeLocalizationUtils.cs
- TooManyMethods: FormatUtils Source/7_Utils/FormatUtils.cs
- FileTooLong: BeatLeaderReplay/Replay.cs Source/2_Core/Models/Replays/BeatLeaderReplay/Replay.cs
- FileTooLong: UtilityClasses/GifLoader.cs Source/7_Utils/UtilityClasses/GifLoader.cs
- Edited copy of a member (26 corresponding lines) Source/7_Utils/Replays/AbstractReplayUtils.cs:62
- Edited copy of a member (26 corresponding lines) Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:175
- Edited copy of a member (21 corresponding lines) Source/2_Core/Managers/SteamVR/SteamVRControllerDetector.cs:18
- Edited copy of a member (21 corresponding lines) Source/8_UI/Leaderboard/Components/ClanScoreDetails/ClanScorePanel.cs:185
- Duplicated block (9 lines × 2) Source/2_Core/API/Methods/ScoresOfClanRequest.cs:11
- Duplicated block (9 lines × 2) Source/8_UI/Leaderboard/Components/ClanScoreDetails/ClanScorePanel.cs:259
- Duplicated block (6 lines × 2) Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:350
- Duplicated block (6 lines × 2) Source/7_Utils/Interop/Interops/PlaylistsLibInterop.cs:10
- Unfinished stub — throws NotImplementedException Source/7_Utils/UtilityClasses/GifLoader.cs:346
- Unfinished stub — throws NotImplementedException Source/7_Utils/UtilityClasses/GifLoader.cs:350
- Unfinished stub — throws NotImplementedException Source/7_Utils/UtilityClasses/GifLoader.cs:346
- Unfinished stub — throws NotImplementedException Source/7_Utils/UtilityClasses/GifLoader.cs:350
- Sync-over-async (deadlock risk) Source/7_Utils/UtilityClasses/AppCache.cs:46
- Sync-over-async (deadlock risk) Source/7_Utils/UtilityClasses/AppCache.cs:80
- Owned disposable field is never released Source/2_Core/API/WebRequestProcessor.cs:236
- Owned disposable field is never released Source/2_Core/API/WebRequestProcessor.cs:243
- Appears unstructured (no recognised architecture)
- ReplayUtils.HMDFromName (cyclomatic 71) Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:190
- ReplayUtils.ControllerFromName (cyclomatic 43) Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:260
- ReplayStatisticUtils.Accuracy (cyclomatic 38) Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:192
- GIFImageBlock.DrawTo (cyclomatic 18) Source/7_Utils/UtilityClasses/GifLoader.cs:262
- MapEnhancer.modifiers (cyclomatic 17) Source/2_Core/Managers/ReplayEnhancer/MapEnhancer.cs:40
- Prerelease dependency: BeatSaberModdingTools.Tasks
- BarePragmaDisable Source/2_Core/Models/Replayer/ReplayerCameraSettings.cs:73
- Build failed
- ReplayStatisticUtils.Accuracy (cognitive 72) Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:192
- ReplayUtils.HMDFromName (cognitive 70) Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:190
- ReplayUtils.ControllerFromName (cognitive 41) Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:260
- ExperienceBar.Update (cognitive 34) Source/8_UI/Leaderboard/Components/TopPanel/ExperienceBar.cs:45
- GIFImageBlock.DrawTo (cognitive 23) Source/7_Utils/UtilityClasses/GifLoader.cs:262
- ReplayStatisticUtils.ComputeScoreStats (cognitive 20) Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:112
- DownloadScoresModal.StartDownloadingInternal (cognitive 19) Source/8_UI/Leaderboard/Components/Header/DownloadScoresModal.cs:68
- AbstractScoresTable.UpdateLayout (cognitive 18) Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoresTable.cs:77
- MapEnhancer.modifiers (cognitive 16) Source/2_Core/Managers/ReplayEnhancer/MapEnhancer.cs:40
- VRPointerEventsHandler.Update (cognitive 16) Source/8_UI/Components/VRPointerEventsHandler.cs:35
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (31 corresponding lines) Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:232
- Edited copy of a member (30 corresponding lines) Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:111
- Edited copy of a member (15 corresponding lines) Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:317
- Edited copy of a member (11 corresponding lines) Source/7_Utils/FormatUtils.cs:135
- Edited copies of one member (3 members, 17+ corresponding lines) Source/7_Utils/UtilityClasses/GifLoader.cs:521
- Edited copies of one member (3 members, 12+ corresponding lines) Source/2_Core/Models/Replays/BeatLeaderReplay/Replay.cs:680
- Edited copies of one member (3 members, 20+ corresponding lines) Source/2_Core/Models/Replays/BeatLeaderReplay/Replay.cs:150
- Edited copies of one member (3 members, 9+ corresponding lines) Source/2_Core/API/Methods/ClanPlayersRequest.cs:51
- Edited copy of a member (68 corresponding lines) Source/8_UI/MainMenu/OtherNews/EventPreviewPanel.cs:18
- Edited copies of one member (3 members, 7+ corresponding lines) Source/0_Harmony/InstallersPatches/AppInstallerPatch.cs:12
- Edited copy of a member (8 corresponding lines) Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/FiltersPanel/TagFilter/TagSelector.cs:89
- Edited copies of one member (3 members, 4+ corresponding lines) Source/2_Core/API/Methods/ClanPlayersRequest.cs:70
- Edited copy of a member (6 corresponding lines) Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/ReplayDetail/BeatmapDownloadDialog.cs:153
- Edited copies of one member (4 members, 4+ corresponding lines) Source/2_Core/API/Methods/ClanPlayersRequest.cs:39
- Edited copy of a member (4 corresponding lines) Source/2_Core/API/Methods/AddFriendRequest.cs:24
- Edited copy of a member (5 corresponding lines) Source/8_UI/Leaderboard/Components/ScoreInfoPanel/MiniProfile.cs:24
- Duplicated block (22 lines × 2) Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:179
- Duplicated block (19 lines × 2) Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:68
- Duplicated block (17 lines × 2) Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:232
- Duplicated block (14 lines × 2) REDACTED:10
- Duplicated block (12 lines × 2) Source/7_Utils/UtilityClasses/GifLoader.cs:528
- Duplicated block (8 lines × 2) Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoreRow.cs:202
- Duplicated block (7–8 lines × 2) Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:119
- Duplicated block (31 lines × 2) Source/8_UI/FlowCoordinator/Flows/ReplayManagerFlow/Components/FiltersPanel/BeatmapFilter/BeatmapCharacteristicPanel.cs:19
- Duplicated block (5 lines × 2) Source/8_UI/Leaderboard/Components/MainPanel/EmptyBoardMessage.cs:102
- Duplicated block (26 lines × 2) Source/8_UI/MainMenu/OtherNews/EventNewsPanel.cs:26
- Outbound HTTP without resilience Source/2_Core/API/WebRequestFactory.cs:14
- NuGet dependencies are not locked REDACTED:365
- Sync-over-async (deadlock risk) through `.Result` Source/2_Core/Managers/DataManager/OculusMigrationManager.cs:74
- Disposable created and abandoned in the method that made it Source/2_Core/Managers/SteamVR/SteamVRSettings.cs:44
Minor — 116 finding(s)
- Orphaned file Source/7_Utils/Interop/Interops/BetterSongListInterop.cs:1
- Orphaned file Source/7_Utils/Replays/BeatLeaderReplay/ReplayUtils.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/ScoreInfoPanel/MiniProfileButtons.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoreRow.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/AbstractScoresTable.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/ClanScoreDetails/ClanScorePanel.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/BeatLeaderInfo.cs:1
- Orphaned file Source/8_UI/Abstract/ReeModalSystem.cs:1
- Orphaned file Source/2_Core/Localization/BLLocalization.cs:1
- Orphaned file Source/2_Core/Managers/DataManager/PlaylistsManager.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/Basic/PlayerAvatar.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/MainScoresTable.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/LeaderboardSettings.cs:1
- Orphaned file Source/8_UI/MainMenu/Modals/MapDownloadDialog.cs:1
- Orphaned file Source/7_Utils/UtilityClasses/ScoresTableLayoutHelper.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/Basic/MiniProfileButton.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/Pagination.cs:1
- Orphaned file Source/2_Core/Managers/SteamVR/SteamVRSettings.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/ScoreInfoPanel/ScoreOverviewPage2.cs:1
- Orphaned file Source/2_Core/Managers/Leaderboard/LeaderboardState.cs:1
- Orphaned file Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:1
- Orphaned file Source/7_Utils/Interop/Interops/CustomNotesInterop.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/MainPanel/ScoreRow.cs:1
- Orphaned file Source/8_UI/Leaderboard/Components/Basic/HintField.cs:1
- Orphaned file Source/7_Utils/Replays/ModifiersUtils.cs:1
- No inbound model validation detected
- No inbound model validation detected REDACTED:86
- No inbound model validation detected REDACTED:134
- No inbound model validation detected Source/2_Core/Replayer/BeatmapVisualsController.cs:101
- No inbound model validation detected Source/2_Core/Replayer/BeatmapVisualsController.cs:105
- No inbound model validation detected Source/2_Core/Replayer/BeatmapVisualsController.cs:116
- No inbound model validation detected Source/2_Core/Replayer/BeatmapVisualsController.cs:120
- No inbound model validation detected Source/2_Core/Replayer/BeatmapVisualsController.cs:131
- No inbound model validation detected Source/2_Core/Replayer/BeatmapVisualsController.cs:154
- No inbound model validation detected REDACTED:35
- No inbound model validation detected REDACTED:48
- No inbound model validation detected Source/2_Core/Replayer/Emulation/Players/Avatar/BeatAvatarController.cs:18
- No inbound model validation detected REDACTED:45
- No inbound model validation detected REDACTED:55
- No inbound model validation detected Source/2_Core/Replayer/Emulation/Scoring/NoteControllerEmulator.cs:19
- No inbound model validation detected REDACTED:68
- No inbound model validation detected REDACTED:81
- No inbound model validation detected REDACTED:15
- No inbound model validation detected REDACTED:216
- No inbound model validation detected REDACTED:35
- No inbound model validation detected Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:31
- No inbound model validation detected Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:170
- No inbound model validation detected Source/8_UI/FlowCoordinator/Navigation/HeckNavigationController.cs:174
- No inbound model validation detected Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:35
- No inbound model validation detected Source/8_UI/Leaderboard/Components/Basic/SmoothHoverController.cs:40
- Commented-out code Source/2_Core/Installers/OnGameplayCoreInstaller.cs:60
- Commented-out code Source/3_AssetBundle/BundleLoader.cs:93
- Commented-out code Source/7_Utils/Interop/Interops/CustomNotesInterop.cs:53
- Commented-out code Source/7_Utils/UtilityClasses/GifLoader.cs:291
- Commented-out code Source/7_Utils/UtilityClasses/GifLoader.cs:299
- Commented-out code Source/7_Utils/UtilityClasses/GifLoader.cs:447
- Commented-out code Source/7_Utils/UtilityClasses/GifLoader.cs:452
- Commented-out code Source/7_Utils/UtilityClasses/GifLoader.cs:486
- Commented-out code Source/7_Utils/UtilityClasses/GifLoader.cs:514
- Commented-out code Source/Plugin.cs:68
- redundant comment Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:23
- redundant comment Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:33
- redundant comment Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:63
- redundant comment Source/0_Harmony/RecorderPatches/RecorderMultiplayerUtilPatch.cs:73
- redundant comment Source/2_Core/API/Methods/AddFriendRequest.cs:21
- redundant comment Source/2_Core/API/Methods/RemoveFriendRequest.cs:20
- redundant comment Source/8_UI/Components/Rendering/BlurPostProcessCanvasRenderer.cs:52
- redundant comment Source/8_UI/FlowCoordinator/HubViews/BeatLeaderHubMainViewController.cs:135
- Silent fallback default in catch Source/2_Core/Installers/OnGameplayCoreInstaller.cs:191
- Silent fallback default in catch Source/2_Core/Installers/OnGameplayCoreInstaller.cs:198
- Silent fallback default in catch Source/2_Core/Managers/DataManager/LeaderboardManager.cs:82
- Silent fallback default in catch Source/2_Core/Managers/SteamVR/SteamVRControllerDetector.cs:45
- Silent fallback default in catch Source/8_UI/AvatarStorage.cs:68
- Silent fallback default in catch Source/8_UI/Leaderboard/Components/ScoreInfoPanel/MiniProfile.cs:79
- Silent fallback default in catch Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:253
- Duplicated predicate Source/8_UI/MainMenu/Modals/MapPreviewDialog.cs:192
- Duplicated predicate Source/7_Utils/Replays/BeatLeaderReplay/ReplayStatisticUtils.cs:118
- Duplicated predicate Source/2_Core/API/Methods/ClanPlayersRequest.cs:14
- Duplicated predicate Source/2_Core/Managers/DataManager/ProfileManager.cs:182
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Silent fallback default on parse failure Source/2_Core/Replayer/ReplayerMenuLoader.cs:341
- Silent fallback default on parse failure Source/7_Utils/Interop/InteropLoader.cs:46
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:7
- No dependency-update automation REDACTED:365
- No release approval gate REDACTED:44
- No changelog
- No security response headers detected
- No app-layer HTTPS enforcement detected
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions override nullable warnings
Minor — 4 finding(s)
- Outdated: BepInEx.AssemblyPublicizer.MSBuild
- Outdated: Meziantou.Analyzer
- Outdated: PolySharp
- doc comments repeat the names Source/2_Core/Models/Replayer/Players/IVirtualPlayerBodySpawner.cs:17
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-f8bca6ade0d446c5a3672b9f07ec3770/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-f8bca6ade0d446c5a3672b9f07ec3770/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=868" --report-format json --report-path /tmp/watchdog-gitleaks-f8bca6ade0d446c5a3672b9f07ec3770/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-f8bca6ade0d446c5a3672b9f07ec3770/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 . | 29 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list BeatLeader.sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| 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 | — |
| 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-66419ece7a9041d993ac0872cd1f52e3 | 0 | artifacts/raw/osv-scanner.json |