Executive summary
Strilanc/Tinker falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 46 out of 100 and is rated Weak, and one of its eight critical findings is a leaked password or key.
Production Readiness, at 29, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 10 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 59.
One password or key is open to anyone who can read the repository. Seven errors are caught and ignored, so failures can go unnoticed. Replacing the exposed password or key and handling or logging the ignored errors would close both risks.
The product code is 24,123 lines, about €27,000 to rebuild.
If Production Readiness rose from 29 to 70, the lowest score rated Strong, the score would rise from 46 to about 59.
Fixed since the last survey: 1 finding
- Code Coverage · Coverage not measured — no coverage collector is wired up
Rebuild cost: about €27,000 · Estimate
| Cost to rebuild | €8,900 to €45,000, for 149 to 471 hours of work, about 0.2 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 46. 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: 24,123 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 My | 2 Commands | 3 Pickling | 4 Components | 5 WC3.Protocol | 6 WC3.Download | 7 WC3 | 8 Bot | 9 Bnet | 10 Bnet.Protocol | 11 Tinker | 12 Bnet.Commands | 13 Bot.Commands | 14 CKL | 15 Lan | 16 Plugins | 17 WC3.Replay | 18 WC3.ServerCommands | 19 Warden | 20 CKL.ServerCommands | 21 Lan.Commands |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 My | |||||||||||||||||||||
| 2 Commands | 11 | ||||||||||||||||||||
| 3 Pickling | 1 | ||||||||||||||||||||
| 4 Components | 3 | 1 | 7 | ||||||||||||||||||
| 5 WC3.Protocol | 30 | 12 | 10 | ||||||||||||||||||
| 6 WC3.Download | 8 | 4 | 3 | ||||||||||||||||||
| 7 WC3 | 52 | 8 | 3 | 45 | 5 | 2 | 3 | 61 | |||||||||||||
| 8 Bot | 8 | 2 | 3 | 9 | |||||||||||||||||
| 9 Bnet | 2 | 1 | 1 | 5 | 3 | 4 | 12 | ||||||||||||||
| 10 Bnet.Protocol | 17 | 2 | 3 | 6 | |||||||||||||||||
| 11 Tinker | 7 | 4 | 2 | ||||||||||||||||||
| 12 Bnet.Commands | 34 | 18 | 18 | ||||||||||||||||||
| 13 Bot.Commands | 22 | 12 | 1 | 12 | |||||||||||||||||
| 14 CKL | 2 | 2 | 3 | 2 | 8 | ||||||||||||||||
| 15 Lan | 2 | 1 | 1 | 2 | 1 | 7 | |||||||||||||||
| 16 Plugins | 3 | 1 | 2 | 6 | |||||||||||||||||
| 17 WC3.Replay | 5 | 6 | 6 | 2 | |||||||||||||||||
| 18 WC3.ServerCommands | 2 | 1 | 1 | ||||||||||||||||||
| 19 Warden | 3 | 2 | |||||||||||||||||||
| 20 CKL.ServerCommands | 4 | 2 | 2 | ||||||||||||||||||
| 21 Lan.Commands | 8 | 4 | 4 |
2→11 Commands uses Tinker part of a loop✕
- Connections
- 11 pairs of types, where a type in Commands uses a type in Tinker.
- The types involved
Tinker.Commands.BaseCommand→Tinker.BotUserTinker.Commands.CommandSet→Tinker.BotUserTinker.Commands.ContractClassBaseCommand→Tinker.BotUserTinker.Commands.ContractClassPartialCommand→Tinker.BotUserTinker.Commands.ContractClassTemplatedCommand→Tinker.BotUserTinker.Commands.HelpCommand→Tinker.BotUserTinker.Commands.ICommand→Tinker.BotUserTinker.Commands.ICommandContractClass→Tinker.BotUserTinker.Commands.PartialCommand→Tinker.BotUserTinker.Commands.ProjectedCommand→Tinker.BotUserTinker.Commands.TemplatedCommand→Tinker.BotUser
- Direction
- Commands uses Tinker, so a change to Tinker can break Commands, while a change to Commands can't break Tinker.
- 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.
3→11 Pickling uses Tinker part of a loop✕
- Connections
- 1 pair of types, where a type in Pickling uses a type in Tinker.
- The types involved
Tinker.Pickling.TupleJar→Tinker.NamedValueMap
- Direction
- Pickling uses Tinker, so a change to Tinker can break Pickling, while a change to Pickling can't break Tinker.
- 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.
4→2 Components uses Commands✕
- Connections
- 3 pairs of types, where a type in Components uses a type in Commands.
- The types involved
Tinker.Components.ContractClassIBotComponent→Tinker.Commands.ICommandTinker.Components.IBotComponent→Tinker.Commands.ICommandTinker.Components.IBotComponentExtensions→Tinker.Commands.ICommand
- Direction
- Components uses Commands, so a change to Commands can break Components, while a change to Components can't break Commands.
- Position
- Below the diagonal: Components uses a module listed above it, which is the healthy direction.
4→8 Components uses Bot part of a loop✕
- Connections
- 1 pair of types, where a type in Components uses a type in Bot.
- The types involved
Tinker.Components.TabControl→Tinker.Bot.MainBot
- Direction
- Components uses Bot, so a change to Bot can break Components, while a change to Components can't break Bot.
- 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.
4→11 Components uses Tinker part of a loop✕
- Connections
- 7 pairs of types, where a type in Components uses a type in Tinker.
- The types involved
Tinker.Components.ComponentSet→Tinker.ObservableCollectionTinker.Components.ContractClassIBotComponent→Tinker.BotUserTinker.Components.ContractClassIBotComponent→Tinker.LoggerTinker.Components.GenericBotComponentControl→Tinker.CommandControlTinker.Components.GenericBotComponentControl→Tinker.LoggerControlTinker.Components.IBotComponent→Tinker.BotUserTinker.Components.IBotComponent→Tinker.Logger
- Direction
- Components uses Tinker, so a change to Tinker can break Components, while a change to Components can't break Tinker.
- 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.
5→3 WC3.Protocol uses Pickling✕
- Connections
- 30 pairs of types, where a type in WC3.Protocol uses a type in Pickling. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tinker.WC3.Protocol.Definition→Tinker.Pickling.IJarTinker.WC3.Protocol.GameActionJar→Tinker.Pickling.BaseConversionJarTinker.WC3.Protocol.GameActionJar→Tinker.Pickling.IJarTinker.WC3.Protocol.GameActionJar→Tinker.Pickling.KeyPrefixedJarTinker.WC3.Protocol.GameActions→Tinker.Pickling.IJarTinker.WC3.Protocol.GameObjectIdJar→Tinker.Pickling.BaseJarTinker.WC3.Protocol.GameObjectIdJar→Tinker.Pickling.IValueEditorTinker.WC3.Protocol.GameObjectIdJar→Tinker.Pickling.ParsedValueTinker.WC3.Protocol.GameStatsJar→Tinker.Pickling.BaseJarTinker.WC3.Protocol.GameStatsJar→Tinker.Pickling.IValueEditorTinker.WC3.Protocol.GameStatsJar→Tinker.Pickling.ParsedValueTinker.WC3.Protocol.GameStatsJar→Tinker.Pickling.TupleJarTinker.WC3.Protocol.KnockDataJar→Tinker.Pickling.BaseConversionJarTinker.WC3.Protocol.KnockDataJar→Tinker.Pickling.IJarTinker.WC3.Protocol.KnockDataJar→Tinker.Pickling.TupleJarTinker.WC3.Protocol.ObjectTypeJar→Tinker.Pickling.BaseJarTinker.WC3.Protocol.ObjectTypeJar→Tinker.Pickling.IValueEditorTinker.WC3.Protocol.ObjectTypeJar→Tinker.Pickling.ParsedValueTinker.WC3.Protocol.ObjectTypeJar→Tinker.Pickling.UInt32JarTinker.WC3.Protocol.OrderIdJar→Tinker.Pickling.BaseJarTinker.WC3.Protocol.OrderIdJar→Tinker.Pickling.EnumUInt32JarTinker.WC3.Protocol.OrderIdJar→Tinker.Pickling.IValueEditorTinker.WC3.Protocol.OrderIdJar→Tinker.Pickling.ParsedValueTinker.WC3.Protocol.Packet→Tinker.Pickling.IPickleTinker.WC3.Protocol.Packets→Tinker.Pickling.IJar
- Direction
- WC3.Protocol uses Pickling, so a change to Pickling can break WC3.Protocol, while a change to WC3.Protocol can't break Pickling.
- Position
- Below the diagonal: WC3.Protocol uses a module listed above it, which is the healthy direction.
5→7 WC3.Protocol uses WC3 part of a loop✕
- Connections
- 12 pairs of types, where a type in WC3.Protocol uses a type in WC3.
- The types involved
Tinker.WC3.Protocol.GameStatsJar→Tinker.WC3.GameStatsTinker.WC3.Protocol.Packers→Tinker.WC3.GameDescriptionTinker.WC3.Protocol.Packers→Tinker.WC3.LocalGameDescriptionTinker.WC3.Protocol.Packers→Tinker.WC3.MapTinker.WC3.Protocol.Packers→Tinker.WC3.PlayerTinker.WC3.Protocol.Packers→Tinker.WC3.PlayerIdTinker.WC3.Protocol.Packers→Tinker.WC3.SlotTinker.WC3.Protocol.PlayerActionSet→Tinker.WC3.PlayerIdTinker.WC3.Protocol.ServerPackets→Tinker.WC3.PlayerIdTinker.WC3.Protocol.SlotJar→Tinker.WC3.PlayerTinker.WC3.Protocol.SlotJar→Tinker.WC3.SlotTinker.WC3.Protocol.SpecificPlayerActionSet→Tinker.WC3.Player
- Direction
- WC3.Protocol uses WC3, so a change to WC3 can break WC3.Protocol, while a change to WC3.Protocol can't break WC3.
- 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.
5→11 WC3.Protocol uses Tinker part of a loop✕
- Connections
- 10 pairs of types, where a type in WC3.Protocol uses a type in Tinker.
- The types involved
Tinker.WC3.Protocol.ClientPackets→Tinker.NamedValueMapTinker.WC3.Protocol.GameActions→Tinker.NamedValueMapTinker.WC3.Protocol.GameStatsJar→Tinker.NamedValueMapTinker.WC3.Protocol.KnockDataJar→Tinker.NamedValueMapTinker.WC3.Protocol.PeerPackets→Tinker.NamedValueMapTinker.WC3.Protocol.PlayerActionSetJar→Tinker.NamedValueMapTinker.WC3.Protocol.ServerPackets→Tinker.NamedValueMapTinker.WC3.Protocol.SlotJar→Tinker.NamedValueMapTinker.WC3.Protocol.W3PacketHandler→Tinker.LoggerTinker.WC3.Protocol.W3PacketHandler→Tinker.PacketHandlerLogger
- Direction
- WC3.Protocol uses Tinker, so a change to Tinker can break WC3.Protocol, while a change to WC3.Protocol can't break Tinker.
- 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.
6→5 WC3.Download uses WC3.Protocol✕
- Connections
- 8 pairs of types, where a type in WC3.Download uses a type in WC3.Protocol.
- The types involved
Tinker.WC3.Download.ContractClass→Tinker.WC3.Protocol.DefinitionTinker.WC3.Download.ContractClass→Tinker.WC3.Protocol.PacketTinker.WC3.Download.ContractClass→Tinker.WC3.Protocol.PlayerLeaveReasonTinker.WC3.Download.IPlayerDownloadAspect→Tinker.WC3.Protocol.DefinitionTinker.WC3.Download.IPlayerDownloadAspect→Tinker.WC3.Protocol.PacketTinker.WC3.Download.IPlayerDownloadAspect→Tinker.WC3.Protocol.PlayerLeaveReasonTinker.WC3.Download.Manager→Tinker.WC3.Protocol.MapTransferStateTinker.WC3.Download.TransferClient→Tinker.WC3.Protocol.MapTransferState
- Direction
- WC3.Download uses WC3.Protocol, so a change to WC3.Protocol can break WC3.Download, while a change to WC3.Download can't break WC3.Protocol.
- Position
- Below the diagonal: WC3.Download uses a module listed above it, which is the healthy direction.
6→7 WC3.Download uses WC3 part of a loop✕
- Connections
- 4 pairs of types, where a type in WC3.Download uses a type in WC3.
- The types involved
Tinker.WC3.Download.ContractClass→Tinker.WC3.PlayerIdTinker.WC3.Download.IPlayerDownloadAspect→Tinker.WC3.PlayerIdTinker.WC3.Download.Manager→Tinker.WC3.MapTinker.WC3.Download.TransferClient→Tinker.WC3.Map
- Direction
- WC3.Download uses WC3, so a change to WC3 can break WC3.Download, while a change to WC3.Download can't break WC3.
- 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.
6→11 WC3.Download uses Tinker part of a loop✕
- Connections
- 3 pairs of types, where a type in WC3.Download uses a type in Tinker.
- The types involved
Tinker.WC3.Download.Manager→Tinker.IHoldPointTinker.WC3.Download.Manager→Tinker.LoggerTinker.WC3.Download.Manager→Tinker.NamedValueMap
- Direction
- WC3.Download uses Tinker, so a change to Tinker can break WC3.Download, while a change to WC3.Download can't break Tinker.
- 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.
7→2 WC3 uses Commands✕
- Connections
- 52 pairs of types, where a type in WC3 uses a type in Commands. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tinker.WC3.CommandBoot→Tinker.Commands.CommandArgumentTinker.WC3.CommandBoot→Tinker.Commands.TemplatedCommandTinker.WC3.CommandBot→Tinker.Commands.BaseCommandTinker.WC3.CommandCPU→Tinker.Commands.CommandArgumentTinker.WC3.CommandCPU→Tinker.Commands.TemplatedCommandTinker.WC3.CommandCancel→Tinker.Commands.CommandArgumentTinker.WC3.CommandCancel→Tinker.Commands.TemplatedCommandTinker.WC3.CommandClose→Tinker.Commands.CommandArgumentTinker.WC3.CommandClose→Tinker.Commands.TemplatedCommandTinker.WC3.CommandColor→Tinker.Commands.CommandArgumentTinker.WC3.CommandColor→Tinker.Commands.TemplatedCommandTinker.WC3.CommandDisconnect→Tinker.Commands.CommandArgumentTinker.WC3.CommandDisconnect→Tinker.Commands.TemplatedCommandTinker.WC3.CommandElevate→Tinker.Commands.CommandArgumentTinker.WC3.CommandElevate→Tinker.Commands.TemplatedCommandTinker.WC3.CommandGet→Tinker.Commands.CommandArgumentTinker.WC3.CommandGet→Tinker.Commands.TemplatedCommandTinker.WC3.CommandHandicap→Tinker.Commands.CommandArgumentTinker.WC3.CommandHandicap→Tinker.Commands.TemplatedCommandTinker.WC3.CommandLock→Tinker.Commands.CommandArgumentTinker.WC3.CommandLock→Tinker.Commands.TemplatedCommandTinker.WC3.CommandOpen→Tinker.Commands.CommandArgumentTinker.WC3.CommandOpen→Tinker.Commands.TemplatedCommandTinker.WC3.CommandPing→Tinker.Commands.CommandArgumentTinker.WC3.CommandPing→Tinker.Commands.TemplatedCommand
- Direction
- WC3 uses Commands, so a change to Commands can break WC3, while a change to WC3 can't break Commands.
- Position
- Below the diagonal: WC3 uses a module listed above it, which is the healthy direction.
7→3 WC3 uses Pickling✕
- Connections
- 8 pairs of types, where a type in WC3 uses a type in Pickling.
- The types involved
Tinker.WC3.PlayerIdJar→Tinker.Pickling.BaseJarTinker.WC3.PlayerIdJar→Tinker.Pickling.IValueEditorTinker.WC3.PlayerIdJar→Tinker.Pickling.ParsedValueTinker.WC3.W3ConnectionAccepter→Tinker.Pickling.IPickleTinker.WC3.W3ConnectionAccepterBase→Tinker.Pickling.IPickleTinker.WC3.W3DummyPlayer→Tinker.Pickling.IPickleTinker.WC3.W3Peer→Tinker.Pickling.IPickleTinker.WC3.W3PeerConnectionAccepter→Tinker.Pickling.IPickle
- Direction
- WC3 uses Pickling, so a change to Pickling can break WC3, while a change to WC3 can't break Pickling.
- Position
- Below the diagonal: WC3 uses a module listed above it, which is the healthy direction.
7→4 WC3 uses Components✕
- Connections
- 3 pairs of types, where a type in WC3 uses a type in Components.
- The types involved
Tinker.WC3.GameManager→Tinker.Components.IBotComponentTinker.WC3.GameServerManager→Tinker.Components.IBotComponentTinker.WC3.W3ServerControl→Tinker.Components.TabManager
- Direction
- WC3 uses Components, so a change to Components can break WC3, while a change to WC3 can't break Components.
- Position
- Below the diagonal: WC3 uses a module listed above it, which is the healthy direction.
7→5 WC3 uses WC3.Protocol✕
- Connections
- 45 pairs of types, where a type in WC3 uses a type in WC3.Protocol. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tinker.WC3.ConnectionEventHandler→Tinker.WC3.Protocol.KnockDataTinker.WC3.Game→Tinker.WC3.Protocol.ChatGroupTinker.WC3.Game→Tinker.WC3.Protocol.ChatTypeTinker.WC3.Game→Tinker.WC3.Protocol.ComputerLevelTinker.WC3.Game→Tinker.WC3.Protocol.KnockDataTinker.WC3.Game→Tinker.WC3.Protocol.PlayerColorTinker.WC3.Game→Tinker.WC3.Protocol.PlayerLeaveReasonTinker.WC3.Game→Tinker.WC3.Protocol.RacesTinker.WC3.GameDescription→Tinker.WC3.Protocol.GameTypesTinker.WC3.GameLobby→Tinker.WC3.Protocol.ComputerLevelTinker.WC3.GameLobby→Tinker.WC3.Protocol.KnockDataTinker.WC3.GameLobby→Tinker.WC3.Protocol.PacketTinker.WC3.GameLobby→Tinker.WC3.Protocol.PlayerColorTinker.WC3.GameLobby→Tinker.WC3.Protocol.RacesTinker.WC3.GameMotor→Tinker.WC3.Protocol.PacketTinker.WC3.GameMotor→Tinker.WC3.Protocol.SpecificPlayerActionSetTinker.WC3.GameServer→Tinker.WC3.Protocol.KnockDataTinker.WC3.GameSet→Tinker.WC3.Protocol.KnockDataTinker.WC3.LocalGameDescription→Tinker.WC3.Protocol.GameTypesTinker.WC3.Map→Tinker.WC3.Protocol.GameTypesTinker.WC3.Map→Tinker.WC3.Protocol.LobbyLayoutStyleTinker.WC3.Player→Tinker.WC3.Protocol.DefinitionTinker.WC3.Player→Tinker.WC3.Protocol.KnockDataTinker.WC3.Player→Tinker.WC3.Protocol.PacketTinker.WC3.Player→Tinker.WC3.Protocol.PacketId
- Direction
- WC3 uses WC3.Protocol, so a change to WC3.Protocol can break WC3, while a change to WC3 can't break WC3.Protocol.
- Position
- Below the diagonal: WC3 uses a module listed above it, which is the healthy direction.
7→6 WC3 uses WC3.Download✕
- Connections
- 5 pairs of types, where a type in WC3 uses a type in WC3.Download.
- The types involved
Tinker.WC3.Game→Tinker.WC3.Download.IPlayerDownloadAspectTinker.WC3.GameLobby→Tinker.WC3.Download.IPlayerDownloadAspectTinker.WC3.GameLobby→Tinker.WC3.Download.ManagerTinker.WC3.Player→Tinker.WC3.Download.IPlayerDownloadAspectTinker.WC3.Player→Tinker.WC3.Download.Manager
- Direction
- WC3 uses WC3.Download, so a change to WC3.Download can break WC3, while a change to WC3 can't break WC3.Download.
- Position
- Below the diagonal: WC3 uses a module listed above it, which is the healthy direction.
7→8 WC3 uses Bot part of a loop✕
- Connections
- 2 pairs of types, where a type in WC3 uses a type in Bot.
- The types involved
Tinker.WC3.GameManager→Tinker.Bot.MainBotTinker.WC3.GameServerManager→Tinker.Bot.MainBot
- Direction
- WC3 uses Bot, so a change to Bot can break WC3, while a change to WC3 can't break Bot.
- 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.
7→10 WC3 uses Bnet.Protocol part of a loop✕
- Connections
- 3 pairs of types, where a type in WC3 uses a type in Bnet.Protocol.
- The types involved
Tinker.WC3.GameDescription→Tinker.Bnet.Protocol.GameStatesTinker.WC3.LocalGameDescription→Tinker.Bnet.Protocol.GameStatesTinker.WC3.RemoteGameDescription→Tinker.Bnet.Protocol.GameStates
- Direction
- WC3 uses Bnet.Protocol, so a change to Bnet.Protocol can break WC3, while a change to WC3 can't break Bnet.Protocol.
- 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.
7→11 WC3 uses Tinker part of a loop✕
- Connections
- 61 pairs of types, where a type in WC3 uses a type in Tinker. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tinker.WC3.CommandBoot→Tinker.BotUserTinker.WC3.CommandBot→Tinker.BotUserTinker.WC3.CommandCPU→Tinker.BotUserTinker.WC3.CommandCancel→Tinker.BotUserTinker.WC3.CommandClose→Tinker.BotUserTinker.WC3.CommandColor→Tinker.BotUserTinker.WC3.CommandDisconnect→Tinker.BotUserTinker.WC3.CommandElevate→Tinker.BotUserTinker.WC3.CommandGet→Tinker.BotUserTinker.WC3.CommandHandicap→Tinker.BotUserTinker.WC3.CommandLock→Tinker.BotUserTinker.WC3.CommandOpen→Tinker.BotUserTinker.WC3.CommandPing→Tinker.BotUserTinker.WC3.CommandRace→Tinker.BotUserTinker.WC3.CommandReserve→Tinker.BotUserTinker.WC3.CommandSet→Tinker.BotUserTinker.WC3.CommandSetTeam→Tinker.BotUserTinker.WC3.CommandSetupTeams→Tinker.BotUserTinker.WC3.CommandStart→Tinker.BotUserTinker.WC3.CommandSwap→Tinker.BotUserTinker.WC3.CommandUnlock→Tinker.BotUserTinker.WC3.CommandVoteStart→Tinker.BotUserTinker.WC3.Game→Tinker.IHoldPointTinker.WC3.Game→Tinker.LoggerTinker.WC3.Game→Tinker.NamedValueMap
- Direction
- WC3 uses Tinker, so a change to Tinker can break WC3, while a change to WC3 can't break Tinker.
- 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.
8→2 Bot uses Commands✕
- Connections
- 8 pairs of types, where a type in Bot uses a type in Commands.
- The types involved
Tinker.Bot.BotExtensions→Tinker.Commands.ICommandTinker.Bot.CommandDownloadMap→Tinker.Commands.CommandArgumentTinker.Bot.CommandDownloadMap→Tinker.Commands.TemplatedCommandTinker.Bot.CommandFindMaps→Tinker.Commands.BaseCommandTinker.Bot.CommandRecacheIP→Tinker.Commands.CommandArgumentTinker.Bot.CommandRecacheIP→Tinker.Commands.TemplatedCommandTinker.Bot.MainBotManager→Tinker.Commands.CommandSetTinker.Bot.MainBotManager→Tinker.Commands.ICommand
- Direction
- Bot uses Commands, so a change to Commands can break Bot, while a change to Bot can't break Commands.
- Position
- Below the diagonal: Bot uses a module listed above it, which is the healthy direction.
8→4 Bot uses Components✕
- Connections
- 2 pairs of types, where a type in Bot uses a type in Components.
- The types involved
Tinker.Bot.MainBot→Tinker.Components.ComponentSetTinker.Bot.MainBotManager→Tinker.Components.IBotComponent
- Direction
- Bot uses Components, so a change to Components can break Bot, while a change to Bot can't break Components.
- Position
- Below the diagonal: Bot uses a module listed above it, which is the healthy direction.
8→7 Bot uses WC3✕
- Connections
- 3 pairs of types, where a type in Bot uses a type in WC3.
- The types involved
Tinker.Bot.BotExtensions→Tinker.WC3.GameServerTinker.Bot.BotExtensions→Tinker.WC3.GameServerManagerTinker.Bot.BotExtensions→Tinker.WC3.GameSet
- Direction
- Bot uses WC3, so a change to WC3 can break Bot, while a change to Bot can't break WC3.
- Position
- Below the diagonal: Bot uses a module listed above it, which is the healthy direction.
8→11 Bot uses Tinker part of a loop✕
- Connections
- 9 pairs of types, where a type in Bot uses a type in Tinker.
- The types involved
Tinker.Bot.BotExtensions→Tinker.BotUserTinker.Bot.ClientProfile→Tinker.BotUserSetTinker.Bot.CommandDownloadMap→Tinker.BotUserTinker.Bot.CommandFindMaps→Tinker.BotUserTinker.Bot.CommandRecacheIP→Tinker.BotUserTinker.Bot.MainBot→Tinker.LoggerTinker.Bot.MainBot→Tinker.PortPoolTinker.Bot.MainBotManager→Tinker.BotUserTinker.Bot.MainBotManager→Tinker.Logger
- Direction
- Bot uses Tinker, so a change to Tinker can break Bot, while a change to Bot can't break Tinker.
- 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.
9→2 Bnet uses Commands✕
- Connections
- 2 pairs of types, where a type in Bnet uses a type in Commands.
- The types involved
Tinker.Bnet.ClientComponent→Tinker.Commands.CommandSetTinker.Bnet.ClientComponent→Tinker.Commands.ICommand
- Direction
- Bnet uses Commands, so a change to Commands can break Bnet, while a change to Bnet can't break Commands.
- Position
- Below the diagonal: Bnet uses a module listed above it, which is the healthy direction.
9→3 Bnet uses Pickling✕
- Connections
- 1 pair of types, where a type in Bnet uses a type in Pickling.
- The types involved
Tinker.Bnet.Client→Tinker.Pickling.IPickle
- Direction
- Bnet uses Pickling, so a change to Pickling can break Bnet, while a change to Bnet can't break Pickling.
- Position
- Below the diagonal: Bnet uses a module listed above it, which is the healthy direction.
9→4 Bnet uses Components✕
- Connections
- 1 pair of types, where a type in Bnet uses a type in Components.
- The types involved
Tinker.Bnet.ClientComponent→Tinker.Components.IBotComponent
- Direction
- Bnet uses Components, so a change to Components can break Bnet, while a change to Bnet can't break Components.
- Position
- Below the diagonal: Bnet uses a module listed above it, which is the healthy direction.
9→7 Bnet uses WC3✕
- Connections
- 5 pairs of types, where a type in Bnet uses a type in WC3.
- The types involved
Tinker.Bnet.AdvertisedGameEventHandler→Tinker.WC3.LocalGameDescriptionTinker.Bnet.AdvertisementEntry→Tinker.WC3.LocalGameDescriptionTinker.Bnet.BnetClientControl→Tinker.WC3.LocalGameDescriptionTinker.Bnet.Client→Tinker.WC3.LocalGameDescriptionTinker.Bnet.ClientComponent→Tinker.WC3.GameSet
- Direction
- Bnet uses WC3, so a change to WC3 can break Bnet, while a change to Bnet can't break WC3.
- Position
- Below the diagonal: Bnet uses a module listed above it, which is the healthy direction.
9→8 Bnet uses Bot✕
- Connections
- 3 pairs of types, where a type in Bnet uses a type in Bot.
- The types involved
Tinker.Bnet.Client→Tinker.Bot.ClientProfileTinker.Bnet.ClientComponent→Tinker.Bot.ClientProfileTinker.Bnet.ClientComponent→Tinker.Bot.MainBot
- Direction
- Bnet uses Bot, so a change to Bot can break Bnet, while a change to Bnet can't break Bot.
- Position
- Below the diagonal: Bnet uses a module listed above it, which is the healthy direction.
9→10 Bnet uses Bnet.Protocol part of a loop✕
- Connections
- 4 pairs of types, where a type in Bnet uses a type in Bnet.Protocol.
- The types involved
Tinker.Bnet.BnetClientControl→Tinker.Bnet.Protocol.QueryGamesListResponseTinker.Bnet.Client→Tinker.Bnet.Protocol.DefinitionTinker.Bnet.Client→Tinker.Bnet.Protocol.PacketTinker.Bnet.Client→Tinker.Bnet.Protocol.PacketId
- Direction
- Bnet uses Bnet.Protocol, so a change to Bnet.Protocol can break Bnet, while a change to Bnet can't break Bnet.Protocol.
- 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.
9→11 Bnet uses Tinker part of a loop✕
- Connections
- 12 pairs of types, where a type in Bnet uses a type in Tinker.
- The types involved
Tinker.Bnet.BnetClientControl→Tinker.CommandControlTinker.Bnet.BnetClientControl→Tinker.LoggerControlTinker.Bnet.BnetClientControl→Tinker.NamedValueMapTinker.Bnet.Client→Tinker.IConnecterTinker.Bnet.Client→Tinker.IProductInfoProviderTinker.Bnet.Client→Tinker.LoggerTinker.Bnet.Client→Tinker.PacketPusherTinker.Bnet.Client→Tinker.PacketSocketTinker.Bnet.Client→Tinker.PacketWalkerTinker.Bnet.ClientComponent→Tinker.BotUserTinker.Bnet.ClientComponent→Tinker.LoggerTinker.Bnet.ClientComponent→Tinker.NamedValueMap
- Direction
- Bnet uses Tinker, so a change to Tinker can break Bnet, while a change to Bnet can't break Tinker.
- 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.
10→3 Bnet.Protocol uses Pickling✕
- Connections
- 17 pairs of types, where a type in Bnet.Protocol uses a type in Pickling.
- The types involved
Tinker.Bnet.Protocol.Definition→Tinker.Pickling.IJarTinker.Bnet.Protocol.FileTimeJar→Tinker.Pickling.BaseFixedSizeJarTinker.Bnet.Protocol.IPAddressJar→Tinker.Pickling.BaseFixedSizeJarTinker.Bnet.Protocol.IPEndPointJar→Tinker.Pickling.BaseJarTinker.Bnet.Protocol.IPEndPointJar→Tinker.Pickling.IValueEditorTinker.Bnet.Protocol.IPEndPointJar→Tinker.Pickling.ParsedValueTinker.Bnet.Protocol.IPEndPointJar→Tinker.Pickling.TupleJarTinker.Bnet.Protocol.Packet→Tinker.Pickling.IPickleTinker.Bnet.Protocol.Packets→Tinker.Pickling.IJarTinker.Bnet.Protocol.ProductCredentialsJar→Tinker.Pickling.BaseConversionJarTinker.Bnet.Protocol.ProductCredentialsJar→Tinker.Pickling.IJarTinker.Bnet.Protocol.ProductCredentialsJar→Tinker.Pickling.TupleJarTinker.Bnet.Protocol.QueryGamesListResponseJar→Tinker.Pickling.BaseJarTinker.Bnet.Protocol.QueryGamesListResponseJar→Tinker.Pickling.INamedJarTinker.Bnet.Protocol.QueryGamesListResponseJar→Tinker.Pickling.IValueEditorTinker.Bnet.Protocol.QueryGamesListResponseJar→Tinker.Pickling.ParsedValueTinker.Bnet.Protocol.TextHexUInt32Jar→Tinker.Pickling.BaseFixedSizeJar
- Direction
- Bnet.Protocol uses Pickling, so a change to Pickling can break Bnet.Protocol, while a change to Bnet.Protocol can't break Pickling.
- Position
- Below the diagonal: Bnet.Protocol uses a module listed above it, which is the healthy direction.
10→7 Bnet.Protocol uses WC3✕
- Connections
- 2 pairs of types, where a type in Bnet.Protocol uses a type in WC3.
- The types involved
Tinker.Bnet.Protocol.Packers→Tinker.WC3.GameDescriptionTinker.Bnet.Protocol.QueryGamesListResponseJar→Tinker.WC3.RemoteGameDescription
- Direction
- Bnet.Protocol uses WC3, so a change to WC3 can break Bnet.Protocol, while a change to Bnet.Protocol can't break WC3.
- Position
- Below the diagonal: Bnet.Protocol uses a module listed above it, which is the healthy direction.
10→9 Bnet.Protocol uses Bnet✕
- Connections
- 3 pairs of types, where a type in Bnet.Protocol uses a type in Bnet.
- The types involved
Tinker.Bnet.Protocol.Packers→Tinker.Bnet.ClientCredentialsTinker.Bnet.Protocol.Packers→Tinker.Bnet.ProductCredentialPairTinker.Bnet.Protocol.ProductCredentialsJar→Tinker.Bnet.ProductCredentials
- Direction
- Bnet.Protocol uses Bnet, so a change to Bnet can break Bnet.Protocol, while a change to Bnet.Protocol can't break Bnet.
- Position
- Below the diagonal: Bnet.Protocol uses a module listed above it, which is the healthy direction.
10→11 Bnet.Protocol uses Tinker part of a loop✕
- Connections
- 6 pairs of types, where a type in Bnet.Protocol uses a type in Tinker.
- The types involved
Tinker.Bnet.Protocol.BnetPacketHandler→Tinker.LoggerTinker.Bnet.Protocol.BnetPacketHandler→Tinker.PacketHandlerLoggerTinker.Bnet.Protocol.ClientToServer→Tinker.NamedValueMapTinker.Bnet.Protocol.ProductCredentialsJar→Tinker.NamedValueMapTinker.Bnet.Protocol.QueryGamesListResponseJar→Tinker.NamedValueMapTinker.Bnet.Protocol.ServerToClient→Tinker.NamedValueMap
- Direction
- Bnet.Protocol uses Tinker, so a change to Tinker can break Bnet.Protocol, while a change to Bnet.Protocol can't break Tinker.
- 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→3 Tinker uses Pickling✕
- Connections
- 7 pairs of types, where a type in Tinker uses a type in Pickling.
- The types involved
Tinker.PacketHandlerLogger→Tinker.Pickling.IJarTinker.PacketHandlerLogger→Tinker.Pickling.IPickleTinker.PacketPusher→Tinker.Pickling.IPickleTinker.PacketWalker→Tinker.Pickling.IJarTinker.PacketWalker→Tinker.Pickling.IPickleTinker.StreamExtensions→Tinker.Pickling.IJarTinker.StreamExtensions→Tinker.Pickling.IPickle
- Direction
- Tinker uses Pickling, so a change to Pickling can break Tinker, while a change to Tinker can't break Pickling.
- Position
- Below the diagonal: Tinker uses a module listed above it, which is the healthy direction.
11→8 Tinker uses Bot✕
- Connections
- 4 pairs of types, where a type in Tinker uses a type in Bot.
- The types involved
Tinker.ClientForm→Tinker.Bot.MainBotTinker.ProfileSettingsControl→Tinker.Bot.ClientProfileTinker.SettingsForm→Tinker.Bot.ClientProfileTinker.SettingsForm→Tinker.Bot.PluginProfile
- Direction
- Tinker uses Bot, so a change to Bot can break Tinker, while a change to Tinker can't break Bot.
- Position
- Below the diagonal: Tinker uses a module listed above it, which is the healthy direction.
11→10 Tinker uses Bnet.Protocol✕
- Connections
- 2 pairs of types, where a type in Tinker uses a type in Bnet.Protocol.
- The types involved
Tinker.WalkerEx→Tinker.Bnet.Protocol.DefinitionTinker.WalkerEx→Tinker.Bnet.Protocol.PacketId
- Direction
- Tinker uses Bnet.Protocol, so a change to Bnet.Protocol can break Tinker, while a change to Tinker can't break Bnet.Protocol.
- Position
- Below the diagonal: Tinker uses a module listed above it, which is the healthy direction.
12→2 Bnet.Commands uses Commands✕
- Connections
- 34 pairs of types, where a type in Bnet.Commands uses a type in Commands. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Tinker.Bnet.Commands.CommandAddUser→Tinker.Commands.CommandArgumentTinker.Bnet.Commands.CommandAddUser→Tinker.Commands.TemplatedCommandTinker.Bnet.Commands.CommandAdminCode→Tinker.Commands.CommandArgumentTinker.Bnet.Commands.CommandAdminCode→Tinker.Commands.TemplatedCommandTinker.Bnet.Commands.CommandAuto→Tinker.Commands.CommandArgumentTinker.Bnet.Commands.CommandAuto→Tinker.Commands.TemplatedCommandTinker.Bnet.Commands.CommandBot→Tinker.Commands.BaseCommandTinker.Bnet.Commands.CommandCancelAllHost→Tinker.Commands.CommandArgumentTinker.Bnet.Commands.CommandCancelAllHost→Tinker.Commands.TemplatedCommandTinker.Bnet.Commands.CommandCancelHost→Tinker.Commands.CommandArgumentTinker.Bnet.Commands.CommandCancelHost→Tinker.Commands.TemplatedCommandTinker.Bnet.Commands.CommandConnect→Tinker.Commands.CommandArgumentTinker.Bnet.Commands.CommandConnect→Tinker.Commands.TemplatedCommandTinker.Bnet.Commands.CommandDemote→Tinker.Commands.CommandArgumentTinker.Bnet.Commands.CommandDemote→Tinker.Commands.TemplatedCommandTinker.Bnet.Commands.CommandDisconnect→Tinker.Commands.CommandArgumentTinker.Bnet.Commands.CommandDisconnect→Tinker.Commands.TemplatedCommandTinker.Bnet.Commands.CommandElevate→Tinker.Commands.CommandArgumentTinker.Bnet.Commands.CommandElevate→Tinker.Commands.TemplatedCommandTinker.Bnet.Commands.CommandGame→Tinker.Commands.PartialCommandTinker.Bnet.Commands.CommandHost→Tinker.Commands.CommandArgumentTinker.Bnet.Commands.CommandHost→Tinker.Commands.TemplatedCommandTinker.Bnet.Commands.CommandLogOn→Tinker.Commands.CommandArgumentTinker.Bnet.Commands.CommandLogOn→Tinker.Commands.TemplatedCommandTinker.Bnet.Commands.CommandPromote→Tinker.Commands.CommandArgument
- Direction
- Bnet.Commands uses Commands, so a change to Commands can break Bnet.Commands, while a change to Bnet.Commands can't break Commands.
- Position
- Below the diagonal: Bnet.Commands uses a module listed above it, which is the healthy direction.
12→9 Bnet.Commands uses Bnet✕
- Connections
- 18 pairs of types, where a type in Bnet.Commands uses a type in Bnet.
- The types involved
Tinker.Bnet.Commands.CommandAddUser→Tinker.Bnet.ClientTinker.Bnet.Commands.CommandAdminCode→Tinker.Bnet.ClientComponentTinker.Bnet.Commands.CommandAuto→Tinker.Bnet.ClientComponentTinker.Bnet.Commands.CommandBot→Tinker.Bnet.ClientComponentTinker.Bnet.Commands.CommandCancelAllHost→Tinker.Bnet.ClientTinker.Bnet.Commands.CommandCancelHost→Tinker.Bnet.ClientComponentTinker.Bnet.Commands.CommandConnect→Tinker.Bnet.ClientTinker.Bnet.Commands.CommandDemote→Tinker.Bnet.ClientTinker.Bnet.Commands.CommandDisconnect→Tinker.Bnet.ClientTinker.Bnet.Commands.CommandElevate→Tinker.Bnet.ClientComponentTinker.Bnet.Commands.CommandGame→Tinker.Bnet.ClientComponentTinker.Bnet.Commands.CommandHost→Tinker.Bnet.ClientComponentTinker.Bnet.Commands.CommandLogOn→Tinker.Bnet.ClientTinker.Bnet.Commands.CommandPromote→Tinker.Bnet.ClientTinker.Bnet.Commands.CommandRefreshGamesList→Tinker.Bnet.ClientTinker.Bnet.Commands.CommandRemoveUser→Tinker.Bnet.ClientTinker.Bnet.Commands.CommandSay→Tinker.Bnet.ClientTinker.Bnet.Commands.CommandUser→Tinker.Bnet.Client
- Direction
- Bnet.Commands uses Bnet, so a change to Bnet can break Bnet.Commands, while a change to Bnet.Commands can't break Bnet.
- Position
- Below the diagonal: Bnet.Commands uses a module listed above it, which is the healthy direction.
12→11 Bnet.Commands uses Tinker✕
- Connections
- 18 pairs of types, where a type in Bnet.Commands uses a type in Tinker.
- The types involved
Tinker.Bnet.Commands.CommandAddUser→Tinker.BotUserTinker.Bnet.Commands.CommandAdminCode→Tinker.BotUserTinker.Bnet.Commands.CommandAuto→Tinker.BotUserTinker.Bnet.Commands.CommandBot→Tinker.BotUserTinker.Bnet.Commands.CommandCancelAllHost→Tinker.BotUserTinker.Bnet.Commands.CommandCancelHost→Tinker.BotUserTinker.Bnet.Commands.CommandConnect→Tinker.BotUserTinker.Bnet.Commands.CommandDemote→Tinker.BotUserTinker.Bnet.Commands.CommandDisconnect→Tinker.BotUserTinker.Bnet.Commands.CommandElevate→Tinker.BotUserTinker.Bnet.Commands.CommandGame→Tinker.BotUserTinker.Bnet.Commands.CommandHost→Tinker.BotUserTinker.Bnet.Commands.CommandLogOn→Tinker.BotUserTinker.Bnet.Commands.CommandPromote→Tinker.BotUserTinker.Bnet.Commands.CommandRefreshGamesList→Tinker.BotUserTinker.Bnet.Commands.CommandRemoveUser→Tinker.BotUserTinker.Bnet.Commands.CommandSay→Tinker.BotUserTinker.Bnet.Commands.CommandUser→Tinker.BotUser
- Direction
- Bnet.Commands uses Tinker, so a change to Tinker can break Bnet.Commands, while a change to Bnet.Commands can't break Tinker.
- Position
- Below the diagonal: Bnet.Commands uses a module listed above it, which is the healthy direction.
13→2 Bot.Commands uses Commands✕
- Connections
- 22 pairs of types, where a type in Bot.Commands uses a type in Commands.
- The types involved
Tinker.Bot.Commands.CommandConnect→Tinker.Commands.BaseCommandTinker.Bot.Commands.CommandCreateAdminGame→Tinker.Commands.CommandArgumentTinker.Bot.Commands.CommandCreateAdminGame→Tinker.Commands.TemplatedCommandTinker.Bot.Commands.CommandCreateCKL→Tinker.Commands.CommandArgumentTinker.Bot.Commands.CommandCreateCKL→Tinker.Commands.TemplatedCommandTinker.Bot.Commands.CommandCreateClient→Tinker.Commands.CommandArgumentTinker.Bot.Commands.CommandCreateClient→Tinker.Commands.TemplatedCommandTinker.Bot.Commands.CommandCreateLan→Tinker.Commands.CommandArgumentTinker.Bot.Commands.CommandCreateLan→Tinker.Commands.TemplatedCommandTinker.Bot.Commands.CommandDispose→Tinker.Commands.CommandArgumentTinker.Bot.Commands.CommandDispose→Tinker.Commands.TemplatedCommandTinker.Bot.Commands.CommandGet→Tinker.Commands.CommandArgumentTinker.Bot.Commands.CommandGet→Tinker.Commands.TemplatedCommandTinker.Bot.Commands.CommandHost→Tinker.Commands.CommandArgumentTinker.Bot.Commands.CommandHost→Tinker.Commands.TemplatedCommandTinker.Bot.Commands.CommandListComponents→Tinker.Commands.CommandArgumentTinker.Bot.Commands.CommandListComponents→Tinker.Commands.TemplatedCommandTinker.Bot.Commands.CommandLoadPlugin→Tinker.Commands.CommandArgumentTinker.Bot.Commands.CommandLoadPlugin→Tinker.Commands.TemplatedCommandTinker.Bot.Commands.CommandSet→Tinker.Commands.CommandArgumentTinker.Bot.Commands.CommandSet→Tinker.Commands.TemplatedCommandTinker.Bot.Commands.CommandTo→Tinker.Commands.PartialCommand
- Direction
- Bot.Commands uses Commands, so a change to Commands can break Bot.Commands, while a change to Bot.Commands can't break Commands.
- Position
- Below the diagonal: Bot.Commands uses a module listed above it, which is the healthy direction.
13→8 Bot.Commands uses Bot✕
- Connections
- 12 pairs of types, where a type in Bot.Commands uses a type in Bot.
- The types involved
Tinker.Bot.Commands.CommandConnect→Tinker.Bot.MainBotTinker.Bot.Commands.CommandCreateAdminGame→Tinker.Bot.MainBotTinker.Bot.Commands.CommandCreateCKL→Tinker.Bot.MainBotTinker.Bot.Commands.CommandCreateClient→Tinker.Bot.MainBotTinker.Bot.Commands.CommandCreateLan→Tinker.Bot.MainBotTinker.Bot.Commands.CommandDispose→Tinker.Bot.MainBotTinker.Bot.Commands.CommandGet→Tinker.Bot.MainBotTinker.Bot.Commands.CommandHost→Tinker.Bot.MainBotTinker.Bot.Commands.CommandListComponents→Tinker.Bot.MainBotTinker.Bot.Commands.CommandLoadPlugin→Tinker.Bot.MainBotTinker.Bot.Commands.CommandSet→Tinker.Bot.MainBotTinker.Bot.Commands.CommandTo→Tinker.Bot.MainBot
- Direction
- Bot.Commands uses Bot, so a change to Bot can break Bot.Commands, while a change to Bot.Commands can't break Bot.
- Position
- Below the diagonal: Bot.Commands uses a module listed above it, which is the healthy direction.
13→9 Bot.Commands uses Bnet✕
- Connections
- 1 pair of types, where a type in Bot.Commands uses a type in Bnet.
- The types involved
Tinker.Bot.Commands.CommandConnect→Tinker.Bnet.ClientComponent
- Direction
- Bot.Commands uses Bnet, so a change to Bnet can break Bot.Commands, while a change to Bot.Commands can't break Bnet.
- Position
- Below the diagonal: Bot.Commands uses a module listed above it, which is the healthy direction.
13→11 Bot.Commands uses Tinker✕
- Connections
- 12 pairs of types, where a type in Bot.Commands uses a type in Tinker.
- The types involved
Tinker.Bot.Commands.CommandConnect→Tinker.BotUserTinker.Bot.Commands.CommandCreateAdminGame→Tinker.BotUserTinker.Bot.Commands.CommandCreateCKL→Tinker.BotUserTinker.Bot.Commands.CommandCreateClient→Tinker.BotUserTinker.Bot.Commands.CommandCreateLan→Tinker.BotUserTinker.Bot.Commands.CommandDispose→Tinker.BotUserTinker.Bot.Commands.CommandGet→Tinker.BotUserTinker.Bot.Commands.CommandHost→Tinker.BotUserTinker.Bot.Commands.CommandListComponents→Tinker.BotUserTinker.Bot.Commands.CommandLoadPlugin→Tinker.BotUserTinker.Bot.Commands.CommandSet→Tinker.BotUserTinker.Bot.Commands.CommandTo→Tinker.BotUser
- Direction
- Bot.Commands uses Tinker, so a change to Tinker can break Bot.Commands, while a change to Bot.Commands can't break Tinker.
- Position
- Below the diagonal: Bot.Commands uses a module listed above it, which is the healthy direction.
14→2 CKL uses Commands✕
- Connections
- 2 pairs of types, where a type in CKL uses a type in Commands.
- The types involved
Tinker.CKL.ServerManager→Tinker.Commands.CommandSetTinker.CKL.ServerManager→Tinker.Commands.ICommand
- Direction
- CKL uses Commands, so a change to Commands can break CKL, while a change to CKL can't break Commands.
- Position
- Below the diagonal: CKL uses a module listed above it, which is the healthy direction.
14→4 CKL uses Components✕
- Connections
- 2 pairs of types, where a type in CKL uses a type in Components.
- The types involved
Tinker.CKL.ServerManager→Tinker.Components.GenericBotComponentControlTinker.CKL.ServerManager→Tinker.Components.IBotComponent
- Direction
- CKL uses Components, so a change to Components can break CKL, while a change to CKL can't break Components.
- Position
- Below the diagonal: CKL uses a module listed above it, which is the healthy direction.
14→9 CKL uses Bnet✕
- Connections
- 3 pairs of types, where a type in CKL uses a type in Bnet.
- The types involved
Tinker.CKL.Client→Tinker.Bnet.IProductAuthenticatorTinker.CKL.Client→Tinker.Bnet.ProductCredentialPairTinker.CKL.KeyEntry→Tinker.Bnet.ProductCredentialPair
- Direction
- CKL uses Bnet, so a change to Bnet can break CKL, while a change to CKL can't break Bnet.
- Position
- Below the diagonal: CKL uses a module listed above it, which is the healthy direction.
14→10 CKL uses Bnet.Protocol✕
- Connections
- 2 pairs of types, where a type in CKL uses a type in Bnet.Protocol.
- The types involved
Tinker.CKL.Client→Tinker.Bnet.Protocol.ProductCredentialsJarTinker.CKL.Server→Tinker.Bnet.Protocol.ProductCredentialsJar
- Direction
- CKL uses Bnet.Protocol, so a change to Bnet.Protocol can break CKL, while a change to CKL can't break Bnet.Protocol.
- Position
- Below the diagonal: CKL uses a module listed above it, which is the healthy direction.
14→11 CKL uses Tinker✕
- Connections
- 8 pairs of types, where a type in CKL uses a type in Tinker.
- The types involved
Tinker.CKL.Client→Tinker.LoggerTinker.CKL.Server→Tinker.ConnectionAccepterTinker.CKL.Server→Tinker.LoggerTinker.CKL.Server→Tinker.ObservableCollectionTinker.CKL.Server→Tinker.PacketSocketTinker.CKL.Server→Tinker.PortHandleTinker.CKL.ServerManager→Tinker.BotUserTinker.CKL.ServerManager→Tinker.Logger
- Direction
- CKL uses Tinker, so a change to Tinker can break CKL, while a change to CKL can't break Tinker.
- Position
- Below the diagonal: CKL uses a module listed above it, which is the healthy direction.
15→2 Lan uses Commands✕
- Connections
- 2 pairs of types, where a type in Lan uses a type in Commands.
- The types involved
Tinker.Lan.UDPAdvertiserComponent→Tinker.Commands.CommandSetTinker.Lan.UDPAdvertiserComponent→Tinker.Commands.ICommand
- Direction
- Lan uses Commands, so a change to Commands can break Lan, while a change to Lan can't break Commands.
- Position
- Below the diagonal: Lan uses a module listed above it, which is the healthy direction.
15→4 Lan uses Components✕
- Connections
- 1 pair of types, where a type in Lan uses a type in Components.
- The types involved
Tinker.Lan.UDPAdvertiserComponent→Tinker.Components.IBotComponent
- Direction
- Lan uses Components, so a change to Components can break Lan, while a change to Lan can't break Components.
- Position
- Below the diagonal: Lan uses a module listed above it, which is the healthy direction.
15→5 Lan uses WC3.Protocol✕
- Connections
- 1 pair of types, where a type in Lan uses a type in WC3.Protocol.
- The types involved
Tinker.Lan.UDPAdvertiser→Tinker.WC3.Protocol.Packet
- Direction
- Lan uses WC3.Protocol, so a change to WC3.Protocol can break Lan, while a change to Lan can't break WC3.Protocol.
- Position
- Below the diagonal: Lan uses a module listed above it, which is the healthy direction.
15→7 Lan uses WC3✕
- Connections
- 2 pairs of types, where a type in Lan uses a type in WC3.
- The types involved
Tinker.Lan.LanGame→Tinker.WC3.LocalGameDescriptionTinker.Lan.UDPAdvertiser→Tinker.WC3.LocalGameDescription
- Direction
- Lan uses WC3, so a change to WC3 can break Lan, while a change to Lan can't break WC3.
- Position
- Below the diagonal: Lan uses a module listed above it, which is the healthy direction.
15→8 Lan uses Bot✕
- Connections
- 1 pair of types, where a type in Lan uses a type in Bot.
- The types involved
Tinker.Lan.UDPAdvertiserComponent→Tinker.Bot.MainBot
- Direction
- Lan uses Bot, so a change to Bot can break Lan, while a change to Lan can't break Bot.
- Position
- Below the diagonal: Lan uses a module listed above it, which is the healthy direction.
15→11 Lan uses Tinker✕
- Connections
- 7 pairs of types, where a type in Lan uses a type in Tinker.
- The types involved
Tinker.Lan.UDPAdvertiser→Tinker.IProductInfoProviderTinker.Lan.UDPAdvertiser→Tinker.LoggerTinker.Lan.UDPAdvertiser→Tinker.ObservableCollectionTinker.Lan.UDPAdvertiserComponent→Tinker.BotUserTinker.Lan.UDPAdvertiserComponent→Tinker.LoggerTinker.Lan.UDPAdvertiserControl→Tinker.CommandControlTinker.Lan.UDPAdvertiserControl→Tinker.LoggerControl
- Direction
- Lan uses Tinker, so a change to Tinker can break Lan, while a change to Lan can't break Tinker.
- Position
- Below the diagonal: Lan uses a module listed above it, which is the healthy direction.
16→2 Plugins uses Commands✕
- Connections
- 3 pairs of types, where a type in Plugins uses a type in Commands.
- The types involved
Tinker.Plugins.ContractClass→Tinker.Commands.ICommandTinker.Plugins.IPlugin→Tinker.Commands.ICommandTinker.Plugins.PluginManager→Tinker.Commands.ICommand
- Direction
- Plugins uses Commands, so a change to Commands can break Plugins, while a change to Plugins can't break Commands.
- Position
- Below the diagonal: Plugins uses a module listed above it, which is the healthy direction.
16→4 Plugins uses Components✕
- Connections
- 1 pair of types, where a type in Plugins uses a type in Components.
- The types involved
Tinker.Plugins.PluginManager→Tinker.Components.IBotComponent
- Direction
- Plugins uses Components, so a change to Components can break Plugins, while a change to Plugins can't break Components.
- Position
- Below the diagonal: Plugins uses a module listed above it, which is the healthy direction.
16→8 Plugins uses Bot✕
- Connections
- 2 pairs of types, where a type in Plugins uses a type in Bot.
- The types involved
Tinker.Plugins.IPluginFactory→Tinker.Bot.MainBotTinker.Plugins.Socket→Tinker.Bot.MainBot
- Direction
- Plugins uses Bot, so a change to Bot can break Plugins, while a change to Plugins can't break Bot.
- Position
- Below the diagonal: Plugins uses a module listed above it, which is the healthy direction.
16→11 Plugins uses Tinker✕
- Connections
- 6 pairs of types, where a type in Plugins uses a type in Tinker.
- The types involved
Tinker.Plugins.ContractClass→Tinker.BotUserTinker.Plugins.ContractClass→Tinker.LoggerTinker.Plugins.IPlugin→Tinker.BotUserTinker.Plugins.IPlugin→Tinker.LoggerTinker.Plugins.PluginManager→Tinker.BotUserTinker.Plugins.PluginManager→Tinker.Logger
- Direction
- Plugins uses Tinker, so a change to Tinker can break Plugins, while a change to Plugins can't break Tinker.
- Position
- Below the diagonal: Plugins uses a module listed above it, which is the healthy direction.
17→3 WC3.Replay uses Pickling✕
- Connections
- 5 pairs of types, where a type in WC3.Replay uses a type in Pickling.
- The types involved
Tinker.WC3.Replay.Definition→Tinker.Pickling.IJarTinker.WC3.Replay.Format→Tinker.Pickling.IJarTinker.WC3.Replay.ReplayEntryJar→Tinker.Pickling.BaseConversionJarTinker.WC3.Replay.ReplayEntryJar→Tinker.Pickling.IJarTinker.WC3.Replay.ReplayEntryJar→Tinker.Pickling.KeyPrefixedJar
- Direction
- WC3.Replay uses Pickling, so a change to Pickling can break WC3.Replay, while a change to WC3.Replay can't break Pickling.
- Position
- Below the diagonal: WC3.Replay uses a module listed above it, which is the healthy direction.
17→5 WC3.Replay uses WC3.Protocol✕
- Connections
- 6 pairs of types, where a type in WC3.Replay uses a type in WC3.Protocol.
- The types involved
Tinker.WC3.Replay.Packers→Tinker.WC3.Protocol.ChatGroupTinker.WC3.Replay.Packers→Tinker.WC3.Protocol.GameTypesTinker.WC3.Replay.Packers→Tinker.WC3.Protocol.LobbyLayoutStyleTinker.WC3.Replay.Packers→Tinker.WC3.Protocol.PlayerLeaveReasonTinker.WC3.Replay.ReplayManager→Tinker.WC3.Protocol.ChatGroupTinker.WC3.Replay.ReplayManager→Tinker.WC3.Protocol.PlayerLeaveReason
- Direction
- WC3.Replay uses WC3.Protocol, so a change to WC3.Protocol can break WC3.Replay, while a change to WC3.Replay can't break WC3.Protocol.
- Position
- Below the diagonal: WC3.Replay uses a module listed above it, which is the healthy direction.
17→7 WC3.Replay uses WC3✕
- Connections
- 6 pairs of types, where a type in WC3.Replay uses a type in WC3.
- The types involved
Tinker.WC3.Replay.Packers→Tinker.WC3.GameStatsTinker.WC3.Replay.Packers→Tinker.WC3.PlayerIdTinker.WC3.Replay.Packers→Tinker.WC3.SlotTinker.WC3.Replay.ReplayManager→Tinker.WC3.GameTinker.WC3.Replay.ReplayManager→Tinker.WC3.PlayerTinker.WC3.Replay.ReplayManager→Tinker.WC3.Slot
- Direction
- WC3.Replay uses WC3, so a change to WC3 can break WC3.Replay, while a change to WC3.Replay can't break WC3.
- Position
- Below the diagonal: WC3.Replay uses a module listed above it, which is the healthy direction.
17→11 WC3.Replay uses Tinker✕
- Connections
- 2 pairs of types, where a type in WC3.Replay uses a type in Tinker.
- The types involved
Tinker.WC3.Replay.Format→Tinker.NamedValueMapTinker.WC3.Replay.ReplayManager→Tinker.IProductInfoProvider
- Direction
- WC3.Replay uses Tinker, so a change to Tinker can break WC3.Replay, while a change to WC3.Replay can't break Tinker.
- Position
- Below the diagonal: WC3.Replay uses a module listed above it, which is the healthy direction.
18→2 WC3.ServerCommands uses Commands✕
- Connections
- 2 pairs of types, where a type in WC3.ServerCommands uses a type in Commands.
- The types involved
Tinker.WC3.ServerCommands.CommandAddGame→Tinker.Commands.CommandArgumentTinker.WC3.ServerCommands.CommandAddGame→Tinker.Commands.TemplatedCommand
- Direction
- WC3.ServerCommands uses Commands, so a change to Commands can break WC3.ServerCommands, while a change to WC3.ServerCommands can't break Commands.
- Position
- Below the diagonal: WC3.ServerCommands uses a module listed above it, which is the healthy direction.
18→7 WC3.ServerCommands uses WC3✕
- Connections
- 1 pair of types, where a type in WC3.ServerCommands uses a type in WC3.
- The types involved
Tinker.WC3.ServerCommands.CommandAddGame→Tinker.WC3.GameServerManager
- Direction
- WC3.ServerCommands uses WC3, so a change to WC3 can break WC3.ServerCommands, while a change to WC3.ServerCommands can't break WC3.
- Position
- Below the diagonal: WC3.ServerCommands uses a module listed above it, which is the healthy direction.
18→11 WC3.ServerCommands uses Tinker✕
- Connections
- 1 pair of types, where a type in WC3.ServerCommands uses a type in Tinker.
- The types involved
Tinker.WC3.ServerCommands.CommandAddGame→Tinker.BotUser
- Direction
- WC3.ServerCommands uses Tinker, so a change to Tinker can break WC3.ServerCommands, while a change to WC3.ServerCommands can't break Tinker.
- Position
- Below the diagonal: WC3.ServerCommands uses a module listed above it, which is the healthy direction.
19→3 Warden uses Pickling✕
- Connections
- 3 pairs of types, where a type in Warden uses a type in Pickling.
- The types involved
Tinker.Warden.ClientPacket→Tinker.Pickling.IPickleTinker.Warden.ClientPackets→Tinker.Pickling.TupleJarTinker.Warden.ServerPacket→Tinker.Pickling.TupleJar
- Direction
- Warden uses Pickling, so a change to Pickling can break Warden, while a change to Warden can't break Pickling.
- Position
- Below the diagonal: Warden uses a module listed above it, which is the healthy direction.
19→11 Warden uses Tinker✕
- Connections
- 2 pairs of types, where a type in Warden uses a type in Tinker.
- The types involved
Tinker.Warden.Socket→Tinker.LoggerTinker.Warden.Socket→Tinker.PacketSocket
- Direction
- Warden uses Tinker, so a change to Tinker can break Warden, while a change to Warden can't break Tinker.
- Position
- Below the diagonal: Warden uses a module listed above it, which is the healthy direction.
20→2 CKL.ServerCommands uses Commands✕
- Connections
- 4 pairs of types, where a type in CKL.ServerCommands uses a type in Commands.
- The types involved
Tinker.CKL.ServerCommands.CommandAddKey→Tinker.Commands.CommandArgumentTinker.CKL.ServerCommands.CommandAddKey→Tinker.Commands.TemplatedCommandTinker.CKL.ServerCommands.CommandRemoveKey→Tinker.Commands.CommandArgumentTinker.CKL.ServerCommands.CommandRemoveKey→Tinker.Commands.TemplatedCommand
- Direction
- CKL.ServerCommands uses Commands, so a change to Commands can break CKL.ServerCommands, while a change to CKL.ServerCommands can't break Commands.
- Position
- Below the diagonal: CKL.ServerCommands uses a module listed above it, which is the healthy direction.
20→11 CKL.ServerCommands uses Tinker✕
- Connections
- 2 pairs of types, where a type in CKL.ServerCommands uses a type in Tinker.
- The types involved
Tinker.CKL.ServerCommands.CommandAddKey→Tinker.BotUserTinker.CKL.ServerCommands.CommandRemoveKey→Tinker.BotUser
- Direction
- CKL.ServerCommands uses Tinker, so a change to Tinker can break CKL.ServerCommands, while a change to CKL.ServerCommands can't break Tinker.
- Position
- Below the diagonal: CKL.ServerCommands uses a module listed above it, which is the healthy direction.
20→14 CKL.ServerCommands uses CKL✕
- Connections
- 2 pairs of types, where a type in CKL.ServerCommands uses a type in CKL.
- The types involved
Tinker.CKL.ServerCommands.CommandAddKey→Tinker.CKL.ServerTinker.CKL.ServerCommands.CommandRemoveKey→Tinker.CKL.Server
- Direction
- CKL.ServerCommands uses CKL, so a change to CKL can break CKL.ServerCommands, while a change to CKL.ServerCommands can't break CKL.
- Position
- Below the diagonal: CKL.ServerCommands uses a module listed above it, which is the healthy direction.
21→2 Lan.Commands uses Commands✕
- Connections
- 8 pairs of types, where a type in Lan.Commands uses a type in Commands.
- The types involved
Tinker.Lan.Commands.CommandAdd→Tinker.Commands.CommandArgumentTinker.Lan.Commands.CommandAdd→Tinker.Commands.TemplatedCommandTinker.Lan.Commands.CommandAuto→Tinker.Commands.CommandArgumentTinker.Lan.Commands.CommandAuto→Tinker.Commands.TemplatedCommandTinker.Lan.Commands.CommandHost→Tinker.Commands.CommandArgumentTinker.Lan.Commands.CommandHost→Tinker.Commands.TemplatedCommandTinker.Lan.Commands.CommandRemove→Tinker.Commands.CommandArgumentTinker.Lan.Commands.CommandRemove→Tinker.Commands.TemplatedCommand
- Direction
- Lan.Commands uses Commands, so a change to Commands can break Lan.Commands, while a change to Lan.Commands can't break Commands.
- Position
- Below the diagonal: Lan.Commands uses a module listed above it, which is the healthy direction.
21→11 Lan.Commands uses Tinker✕
- Connections
- 4 pairs of types, where a type in Lan.Commands uses a type in Tinker.
- The types involved
Tinker.Lan.Commands.CommandAdd→Tinker.BotUserTinker.Lan.Commands.CommandAuto→Tinker.BotUserTinker.Lan.Commands.CommandHost→Tinker.BotUserTinker.Lan.Commands.CommandRemove→Tinker.BotUser
- Direction
- Lan.Commands uses Tinker, so a change to Tinker can break Lan.Commands, while a change to Lan.Commands can't break Tinker.
- Position
- Below the diagonal: Lan.Commands uses a module listed above it, which is the healthy direction.
21→15 Lan.Commands uses Lan✕
- Connections
- 4 pairs of types, where a type in Lan.Commands uses a type in Lan.
- The types involved
Tinker.Lan.Commands.CommandAdd→Tinker.Lan.UDPAdvertiserTinker.Lan.Commands.CommandAuto→Tinker.Lan.UDPAdvertiserComponentTinker.Lan.Commands.CommandHost→Tinker.Lan.UDPAdvertiserComponentTinker.Lan.Commands.CommandRemove→Tinker.Lan.UDPAdvertiser
- Direction
- Lan.Commands uses Lan, so a change to Lan can break Lan.Commands, while a change to Lan.Commands can't break Lan.
- Position
- Below the diagonal: Lan.Commands uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 123 Orphaned file finding(s) in Knowledge Freshness — start with Common.vb (2), Bnet Client.vb, Game Action Protocol.vb; Add a CI workflow that builds and runs the test suite on every push/PR.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +10.1 pts | Low | ADR Quality |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +8.1 pts | Medium | CI/CD gates |
| 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. | +7.3 pts | Medium | Architecture documentation |
| Resolve the 11 redundant comment finding(s) in Comment Value — start with AssemblyInfo.vb (8), Download Manager.vb, ReplayReader.vb. | +6.9 pts | Medium | Comment Value |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Tinker.vbproj. | +3.1 pts | Low | Project Cohesion |
| Resolve the 123 Orphaned file finding(s) in Knowledge Freshness — start with Common.vb (2), Bnet Client.vb, Game Action Protocol.vb. | +10.0 pts | High | Knowledge Freshness |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.7 pts | Medium | Release Hygiene |
| 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. | +2.9 pts | Medium | Architecture & structure |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| HostBotTests/Utilities/Common.vb | 5.4 | Mixed | Explicit Debt: EmptyCatchBlock |
| Warcraft3/W3Map.vb | 6.0 | Mixed | Explicit Debt: TodoComment |
| Warcraft3/Player/W3Player.vb | 6.1 | Mixed | Explicit Debt: EmptyCatchBlock |
| Bot/MainBot.vb | 6.1 | Mixed | Explicit Debt: EmptyCatchBlock |
| Warcraft3/Game/Game Lobby.vb | 7.1 | Mixed | Cyclomatic Complexity: GameLobby.OnPlayerSetTeam (cyclomatic 17) |
| Library/Common.vb | 7.2 | Mixed | Cognitive Complexity: PoorlyCategorizedFunctions.LayoutPanel (cognitive 22) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| Library/Common Async.vb | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Warcraft3/W3DummyPlayer.vb | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Warcraft3/W3Relay.vb | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Warcraft3/W3RemotePlayer.vb | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Warcraft3/W3GameStats.vb | 7.8 | Mixed | Cyclomatic Complexity: GameStats.Equals (cyclomatic 18) |
| Commands/CommandArgument.vb | 7.8 | Mixed | Cognitive Complexity: CommandArgument.New.ctor (cognitive 26) |
| HostBotTests/GameActionProtocolTest.vb | 7.8 | Mixed | God Classes: TooManyMethods: GameActionProtocolTest |
| Warcraft3/Game/W3Game.vb | 7.8 | Mixed | God Classes: TooManyMethods: Game |
| Bnet/Bnet Client.vb | 7.8 | Mixed | God Classes: ClassTooLong: Client |
| Warcraft3/Game/Game Commands.vb | 7.8 | Mixed | God Classes: ClassTooLong: GameCommands |
| Warcraft3/W3GameDescription.vb | 7.8 | Mixed | Code Duplication: Duplicated block (7 lines × 2) |
| Warcraft3/Download/Download Manager.vb | 8.0 | Near-clean | Cognitive Complexity: Manager.ClientLatencyDescription.Get (cognitive 17) |
| Tinker.vbproj | 8.0 | Near-clean | Coupling: Off the main sequence: Tinker |
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 31 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 31 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, 196 of 206 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
- D8 Code Coverage — 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. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D11 Test Reliability — 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. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No dependency manifest this pass reads for hygiene (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
- D14 License Compliance — 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. License scan produced no result — the tool ran but wrote no JSON report (no package reference resolved); the offline NuGet fallback resolved nothing.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 622 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 1 hold 3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'Tinker.vbproj' with message: Unable to find code signing certificate in the current user’s Windows certificate store. To correct this, either disable signing of the ClickOnce manifest or install the certificate into the certificate store.
- D18 Solution Shape — evaluation did not complete — Dimension evaluation failed — excluded from the score.
- 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (24,123 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
- 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.
- PF3 Async & latency hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No function of a language this check models was read, so there was no async code to examine. That is a limit of the analyzer on this repository, not a finding about it.
- S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X10 Duplicated predicate — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X20 Mistyped argument guard — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — 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 check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — 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 check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — 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 check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 REDACTED Scanning: REDACTED 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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.
- 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
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was GameStatsJar.PackDataValue at 18. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being BnetClientControl.OnClientReceivedChatEventAsync at 21 — 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: Bnet/BnetClientControl.vb (BnetClientControl.OnClientReceivedChatEventAsync at 21). 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 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with GameStatsJar.PackDataValue (cyclomatic 18), GameStats.Equals (cyclomatic 18), TestingCommon.ObjectEqual (cyclomatic 18). — 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 4 together lifts Cyclomatic Complexity from 9.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
14 method(s) exceeded the cognitive complexity threshold of 15; the worst was TestingCommon.ObjectEqual at 30.
What to do
- Bring the 14 bodies over 15 down to 15 or less in Cognitive Complexity — start with TestingCommon.ObjectEqual (cognitive 30), GameLobby.OnPlayerSetTeam (cognitive 26), CommandArgument.New.ctor (cognitive 26). — 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 14 together lifts Cognitive Complexity from 8.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
18 god class(es) detected.
What to do
- Resolve the 9 TooManyMethods finding(s) in God Classes — start with GameActionProtocolTest.vb, W3Game.vb, Common.vb. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 5 FileTooLong finding(s) in God Classes — start with GameActionProtocolTest.vb, Game Lobby.vb, W3Game.vb. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 ClassTooLong finding(s) in God Classes — start with Bnet Client.vb, Game Commands.vb, PicklingTest.vb. — One of this dimension's main actionable groups (4 warning-level).
- Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
9 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with W3Map.vb, W3GameDescription.vb. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Pickling Base.vb, GameServer.vb. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (22 lines × 2) finding(s) in Code Duplication — start with MainBot.vb. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
2 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling — start with Tinker.vbproj. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 133 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with IPlayerDownloadAspect.vb. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
9 deducted debt markers + unmeasured dead symbols across 24123 LoC in the .NET projects (0.3/KLoC) → score 9.4. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 7 EmptyCatchBlock finding(s) in Explicit Debt — start with MainBot.vb, Common.vb, Common Async.vb. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with W3Map.vb (2). — One of this dimension's main actionable groups (2 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
11 of 191 judged comments only repeat the code they sit on (5.8 %). 40 comment(s) in another language or script were not judged.
What to do
- Resolve the 11 redundant comment finding(s) in Comment Value — start with AssemblyInfo.vb (8), Download Manager.vb, ReplayReader.vb. — One of this dimension's main actionable groups (11 recommendation-level).
D26 · Project Cohesion
1 of 2 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Tinker.vbproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
88 % of calls cross a namespace and 3 % go through an interface, but 80 % of collaborators are co-located — so following a call takes several hops. Baseline: medium — clean/modular boundaries expected.
What to do
- Improve Navigability — currently 7.9/10. — 88 % of calls cross a namespace and 3 % go through an interface, but 80 % of collaborators are co-located — so following a call takes several hops. Baseline: medium — clean/modular boundaries expected.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
semgrep found no security issues.
D34 · Knowledge Freshness
126 of 126 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Warcraft3/Game/Game Lobby.vb. Counted over 126 of the 152 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 123 Orphaned file finding(s) in Knowledge Freshness — start with Common.vb (2), Bnet Client.vb, Game Action Protocol.vb. — One of this dimension's main actionable groups (123 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Game Lobby.vb, W3Game.vb, W3Map.vb. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
- ~24.1k production LoC (488 types) across 2 project(s) / 24 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
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- 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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
What to do
- For more than a log file, an `ActivitySource`/`EventSource` the user can switch on gives you a structured trace to attach to a bug report. A health-check endpoint does not apply here: nothing orchestrates or load-balances a binary the user launches.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
What to do
- Run what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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.
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.
X28 · Index access outside its own emptiness guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 90% | Checked 5 of 13 | Solid. |
| Architecture | 69% | Adequate — gated by D26, AX5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 43% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 29% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 95% | Checked 2 of 9 | Strongest area. |
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 81 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.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations 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 — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~4455 lines of test source are present (.vb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D12 Dependency Hygiene — Dependency hygiene not measured — no supported dependency manifest was read
- D14 License Compliance — Licence collector did not produce a result
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — Dimension evaluation failed
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Visual Basic not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- D9 Test Distribution — Test source is present (.vb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- 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
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
Appendix A — Findings (grouped)
Critical — 8 finding(s)
- EmptyCatchBlock Bot/MainBot.vb:121
- EmptyCatchBlock HostBotTests/Utilities/Common.vb:56
- EmptyCatchBlock Library/Common Async.vb:102
- EmptyCatchBlock Warcraft3/Player/W3Player.vb:155
- EmptyCatchBlock Warcraft3/W3DummyPlayer.vb:116
- EmptyCatchBlock Warcraft3/W3Relay.vb:185
- EmptyCatchBlock Warcraft3/W3RemotePlayer.vb:68
- REDACTED
Serious — 51 finding(s)
- TooManyMethods: GameActionProtocolTest HostBotTests/GameActionProtocolTest.vb
- TooManyMethods: Game Warcraft3/Game/W3Game.vb
- TooManyMethods: PoorlyCategorizedFunctions Library/Common.vb
- TooManyMethods: GameLobby Warcraft3/Game/Game Lobby.vb
- TooManyMethods: WC3ProtocolTest HostBotTests/WC3ProtocolTest.vb
- TooManyMethods: BnetProtocolTest HostBotTests/BnetProtocolTest.vb
- TooManyMethods: Packers Warcraft3/Protocol/WC3 Protocol Packers.vb
- TooManyMethods: Player Warcraft3/Player/W3Player.vb
- TooManyMethods: WC3ProtocolPackersTest HostBotTests/WC3ProtocolPackersTest.vb
- FileTooLong: HostBotTests/GameActionProtocolTest.vb HostBotTests/GameActionProtocolTest.vb
- FileTooLong: Game/Game Lobby.vb Warcraft3/Game/Game Lobby.vb
- FileTooLong: Game/W3Game.vb Warcraft3/Game/W3Game.vb
- FileTooLong: Bnet/Bnet Client.vb Bnet/Bnet Client.vb
- FileTooLong: Library/Common.vb Library/Common.vb
- ClassTooLong: Client Bnet/Bnet Client.vb
- ClassTooLong: GameCommands Warcraft3/Game/Game Commands.vb
- ClassTooLong: PicklingTest HostBotTests/PicklingTest.vb
- ClassTooLong: GameSettings Warcraft3/Server/GameSettings.vb
- TodoComment Warcraft3/W3Map.vb:285
- TodoComment Warcraft3/W3Map.vb:309
- Duplicated block (7 lines × 2) Warcraft3/W3Map.vb:576
- Duplicated block (7 lines × 2) Warcraft3/W3GameDescription.vb:224
- Duplicated block (5 lines × 2) Pickling/Pickling Base.vb:123
- Duplicated block (5 lines × 2) Warcraft3/Server/GameServer.vb:241
- Appears unstructured (no recognised architecture)
- GameStatsJar.PackDataValue (cyclomatic 18) Warcraft3/Protocol/GameStatsJar.vb:59
- GameStats.Equals (cyclomatic 18) Warcraft3/W3GameStats.vb:264
- TestingCommon.ObjectEqual (cyclomatic 18) HostBotTests/Utilities/Common.vb:155
- GameLobby.OnPlayerSetTeam (cyclomatic 17) Warcraft3/Game/Game Lobby.vb:438
- TestingCommon.ObjectEqual (cognitive 30) HostBotTests/Utilities/Common.vb:155
- GameLobby.OnPlayerSetTeam (cognitive 26) Warcraft3/Game/Game Lobby.vb:438
- CommandArgument.New.ctor (cognitive 26) Commands/CommandArgument.vb:30
- CommandArgument.Tokenize (cognitive 26) Commands/CommandArgument.vb:73
- GameLobby.New.ctor (cognitive 23) Warcraft3/Game/Game Lobby.vb:27
- GameLoadScreen.OnReceiveReady (cognitive 23) Warcraft3/Game/Game Load Screen.vb:118
- CommandTemplate.TryFindMismatch (cognitive 22) Commands/CommandTemplate.vb:48
- PoorlyCategorizedFunctions.LayoutPanel (cognitive 22) Library/Common.vb:511
- PoorlyCategorizedFunctions.SplitText (cognitive 20) Library/Common.vb:46
- SettingsForm.btnSave_Click (cognitive 20) Interface/SettingsForm.vb:148
- GameMotor.UpdateLagScreen (cognitive 19) Warcraft3/Game/Game Motor.vb:156
- GameStats.Equals (cognitive 18) Warcraft3/W3GameStats.vb:264
- Manager.ClientLatencyDescription.Get (cognitive 17) Warcraft3/Download/Download Manager.vb:98
- LoggerControl.EmptyQueue (cognitive 17) Interface/LoggerControl.vb:209
- Duplicated block (22 lines × 2) Bot/MainBot.vb:147
- Duplicated block (11 lines × 3) Warcraft3/Game/Game Commands.vb:27
- Duplicated block (10 lines × 2) Library/Stream Extensions.vb:103
- Duplicated block (5 lines × 3) Warcraft3/W3GameDescription.vb:63
- Duplicated block (6 lines × 2) Bnet/ClientCredentials.vb:167
- Off the main sequence: Tinker Tinker.vbproj:1
- Low cohesion: ContractClass (LCOM4 4) Warcraft3/Download/IPlayerDownloadAspect.vb:13
- No CI pipeline
Minor — 146 finding(s)
- Orphaned file Bnet/Bnet Client.vb:1
- Orphaned file Warcraft3/Protocol/Game Action Protocol.vb:1
- Orphaned file Warcraft3/Protocol/WC3 Protocol.vb:1
- Orphaned file Library/Common.vb:1
- Orphaned file Warcraft3/Game/Game Commands.vb:1
- Orphaned file Warcraft3/Player/W3Player.vb:1
- Orphaned file Warcraft3/Server/GameSettings.vb:1
- Orphaned file Bnet/Bnet Client Commands.vb:1
- Orphaned file Bnet/Protocol/Bnet Protocol.vb:1
- Orphaned file Warcraft3/Download/Download Manager.vb:1
- Orphaned file Warcraft3/Protocol/WC3 Protocol Packers.vb:1
- Orphaned file Bot/Bot Commands.vb:1
- Orphaned file Warcraft3/W3GameDescription.vb:1
- Orphaned file Interface/LoggerControl.vb:1
- Orphaned file REDACTED:1
- Orphaned file Interface/SettingsForm.vb:1
- Orphaned file Warcraft3/W3DummyPlayer.vb:1
- Orphaned file Warcraft3/Server/WC3GameServerManager.vb:1
- Orphaned file Pickling/List Framing Jars.vb:1
- Orphaned file Bot/MainBot.vb:1
- Orphaned file Warcraft3/Replay/ReplayDataReader.vb:1
- Orphaned file Warcraft3/Game/Game Motor.vb:1
- Orphaned file Pickling/Framing Jars.vb:1
- Orphaned file Bnet/Revision Check.vb:1
- Orphaned file Warcraft3/W3GameStats.vb:1
- redundant comment HostBotTests/My Project/AssemblyInfo.vb:5
- redundant comment HostBotTests/My Project/AssemblyInfo.vb:9
- redundant comment HostBotTests/My Project/AssemblyInfo.vb:22
- redundant comment HostBotTests/My Project/AssemblyInfo.vb:25
- redundant comment My Project/AssemblyInfo.vb:5
- redundant comment My Project/AssemblyInfo.vb:9
- redundant comment My Project/AssemblyInfo.vb:20
- redundant comment My Project/AssemblyInfo.vb:23
- redundant comment Warcraft3/Download/Download Manager.vb:361
- redundant comment Warcraft3/Replay/ReplayReader.vb:62
- redundant comment Warcraft3/W3Map.vb:126
- Most significant orphaned file Warcraft3/Game/Game Lobby.vb:1
- Most significant orphaned file Warcraft3/Game/W3Game.vb:1
- Most significant orphaned file Warcraft3/W3Map.vb:1
- No ADRs found
- Projects may be oversized for their cohesion Tinker.vbproj:1
- REDACTED
- Dormant codebase
- No ADRs
- No architecture diagram/doc
- No src/ separation
- No SAST
- No changelog
Minor — 1 finding(s)
- doc comments repeat the names Library/ConnectionAccepter.vb:83
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 --report-format json --report-path /tmp/watchdog-gitleaks-c648d249cd5e4c428d4dfb6a55dc0c57/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.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-c648d249cd5e4c428d4dfb6a55dc0c57/tree.json --exit-code 0 --source . | 1 | 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 --exclude HostBotTests/obj Bnet Bot CKL "Code Analysis Rules.ruleset" Commands Components CustomDictionary.xml Docs.txt GlobalSuppressions.vb HostBotTests Interface LICENSE Lan Library "My Project" Pickling Plugins README.md Resources Tinker.vbproj Tinker.vbproj.user Warcraft3 Warden app.config | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |