Executive summary
nickkossolapov/fame-boy falls short of our standard for production, in part because we found no logging, tracing or health checks in the code. It scores 59 out of 100 and is rated Adequate, and all 15 of its critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 46, is the weakest lens and counts most in the score. The best first step is adding a diagnostic log, worth about 7 points. Updating the outdated dependencies comes next, worth about 2 points. Raising Production Readiness to 70 would lift the score to about 68.
Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks.
The product code is 3,202 lines, about €7,100 to rebuild.
If Production Readiness rose from 46 to 70, the lowest score rated Strong, the score would rise from 59 to about 68.
New since the last survey: 3 findings
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Visual & motion safety · Animation without a prefers-reduced-motion guard src/FameBoy.Web/styles.css
Fixed since the last survey: 2 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €7,100 · Estimate
| Cost to rebuild | €2,400 to €12,000, for 39 to 125 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,202 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 — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Apu | 2 Cartridges.Mbc1Cart | 3 Cartridges.Mbc3Cart | 4 Cartridges.Mbc5Cart | 5 Cpu.Instructions.LoadTypes | 6 Interrupts | 7 IoController | 8 Joypad | 9 Apu.ApuModule | 10 Apu.NoiseChannelModule | 11 Apu.PulseChannelModule | 12 Apu.Shared | 13 Apu.SoundProcessing | 14 Apu.SweepChannelModule | 15 Apu.WaveChannelModule | 16 Benchmark.Web.Program | 17 Cartridge | 18 Memory | 19 Ppu.Lcdc | 20 Ppu.Palettes | 21 Web.Audio | 22 Cpu.State | 23 Ppu | 24 Cpu.Instructions.Operand | 25 Ppu.Scanline | 26 Ppu.ShadeModule | 27 Ppu.StatRegister | 28 Raylib.Graphics.GraphicsPipeline | 29 Startup | 30 Cpu.Instructions | 31 Cpu.Execute | 32 Cpu.Executors.Arithmetic | 33 Cpu.Executors.Bitwise | 34 Cpu.Executors.Control | 35 Cpu.Executors.Load | 36 Cpu.Executors.Logic | 37 Cpu.Instructions.LengthsAndCycles | 38 Cpu.Opcodes | 39 Cpu.Opcodes.TwoByteInstructions | 40 Cpu.Utils |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Apu | ||||||||||||||||||||||||||||||||||||||||
| 2 Cartridges.Mbc1Cart | ||||||||||||||||||||||||||||||||||||||||
| 3 Cartridges.Mbc3Cart | ||||||||||||||||||||||||||||||||||||||||
| 4 Cartridges.Mbc5Cart | ||||||||||||||||||||||||||||||||||||||||
| 5 Cpu.Instructions.LoadTypes | ||||||||||||||||||||||||||||||||||||||||
| 6 Interrupts | ||||||||||||||||||||||||||||||||||||||||
| 7 IoController | ||||||||||||||||||||||||||||||||||||||||
| 8 Joypad | ||||||||||||||||||||||||||||||||||||||||
| 9 Apu.ApuModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Apu.NoiseChannelModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Apu.PulseChannelModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Apu.Shared | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Apu.SoundProcessing | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 Apu.SweepChannelModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Apu.WaveChannelModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Benchmark.Web.Program | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Cartridge | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 Memory | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Ppu.Lcdc | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Ppu.Palettes | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 Web.Audio | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Cpu.State | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 Ppu | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 Cpu.Instructions.Operand | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 Ppu.Scanline | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 26 Ppu.ShadeModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 Ppu.StatRegister | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Raylib.Graphics.GraphicsPipeline | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 Startup | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 Cpu.Instructions | 4 | 2 | 6 | |||||||||||||||||||||||||||||||||||||
| 31 Cpu.Execute | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 Cpu.Executors.Arithmetic | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Cpu.Executors.Bitwise | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 Cpu.Executors.Control | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 Cpu.Executors.Load | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 Cpu.Executors.Logic | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 Cpu.Instructions.LengthsAndCycles | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 38 Cpu.Opcodes | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 Cpu.Opcodes.TwoByteInstructions | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 Cpu.Utils | 1 | 1 | 1 |
9→1 Apu.ApuModule uses Apu✕
- Connections
- 1 pair of types, where a type in Apu.ApuModule uses a type in Apu.
- The types involved
FameBoy.Apu.ApuModule.ApuModule→FameBoy.Apu.Apu
- Direction
- Apu.ApuModule uses Apu, so a change to Apu can break Apu.ApuModule, while a change to Apu.ApuModule can't break Apu.
- Position
- Below the diagonal: Apu.ApuModule uses a module listed above it, which is the healthy direction.
10→1 Apu.NoiseChannelModule uses Apu✕
- Connections
- 1 pair of types, where a type in Apu.NoiseChannelModule uses a type in Apu.
- The types involved
FameBoy.Apu.NoiseChannelModule.NoiseChannelModule→FameBoy.Apu.NoiseChannel
- Direction
- Apu.NoiseChannelModule uses Apu, so a change to Apu can break Apu.NoiseChannelModule, while a change to Apu.NoiseChannelModule can't break Apu.
- Position
- Below the diagonal: Apu.NoiseChannelModule uses a module listed above it, which is the healthy direction.
11→1 Apu.PulseChannelModule uses Apu✕
- Connections
- 1 pair of types, where a type in Apu.PulseChannelModule uses a type in Apu.
- The types involved
FameBoy.Apu.PulseChannelModule.PulseChannelModule→FameBoy.Apu.PulseChannel
- Direction
- Apu.PulseChannelModule uses Apu, so a change to Apu can break Apu.PulseChannelModule, while a change to Apu.PulseChannelModule can't break Apu.
- Position
- Below the diagonal: Apu.PulseChannelModule uses a module listed above it, which is the healthy direction.
12→1 Apu.Shared uses Apu✕
- Connections
- 1 pair of types, where a type in Apu.Shared uses a type in Apu.
- The types involved
FameBoy.Apu.Shared.Shared→FameBoy.Apu.Envelope
- Direction
- Apu.Shared uses Apu, so a change to Apu can break Apu.Shared, while a change to Apu.Shared can't break Apu.
- Position
- Below the diagonal: Apu.Shared uses a module listed above it, which is the healthy direction.
13→1 Apu.SoundProcessing uses Apu✕
- Connections
- 3 pairs of types, where a type in Apu.SoundProcessing uses a type in Apu.
- The types involved
FameBoy.Apu.SoundProcessing.SoundProcessing→FameBoy.Apu.ApuFameBoy.Apu.SoundProcessing.SoundProcessing→FameBoy.Apu.HighPassFilterFameBoy.Apu.SoundProcessing.SoundProcessing→FameBoy.Apu.LowPassFilter
- Direction
- Apu.SoundProcessing uses Apu, so a change to Apu can break Apu.SoundProcessing, while a change to Apu.SoundProcessing can't break Apu.
- Position
- Below the diagonal: Apu.SoundProcessing uses a module listed above it, which is the healthy direction.
14→1 Apu.SweepChannelModule uses Apu✕
- Connections
- 1 pair of types, where a type in Apu.SweepChannelModule uses a type in Apu.
- The types involved
FameBoy.Apu.SweepChannelModule.SweepChannelModule→FameBoy.Apu.SweepChannel
- Direction
- Apu.SweepChannelModule uses Apu, so a change to Apu can break Apu.SweepChannelModule, while a change to Apu.SweepChannelModule can't break Apu.
- Position
- Below the diagonal: Apu.SweepChannelModule uses a module listed above it, which is the healthy direction.
15→1 Apu.WaveChannelModule uses Apu✕
- Connections
- 1 pair of types, where a type in Apu.WaveChannelModule uses a type in Apu.
- The types involved
FameBoy.Apu.WaveChannelModule.WaveChannelModule→FameBoy.Apu.WaveChannel
- Direction
- Apu.WaveChannelModule uses Apu, so a change to Apu can break Apu.WaveChannelModule, while a change to Apu.WaveChannelModule can't break Apu.
- Position
- Below the diagonal: Apu.WaveChannelModule uses a module listed above it, which is the healthy direction.
16→8 Benchmark.Web.Program uses Joypad✕
- Connections
- 1 pair of types, where a type in Benchmark.Web.Program uses a type in Joypad.
- The types involved
FameBoy.Benchmark.Web.Program.Program→FameBoy.Joypad.JoypadState
- Direction
- Benchmark.Web.Program uses Joypad, so a change to Joypad can break Benchmark.Web.Program, while a change to Benchmark.Web.Program can't break Joypad.
- Position
- Below the diagonal: Benchmark.Web.Program uses a module listed above it, which is the healthy direction.
17→2 Cartridge uses Cartridges.Mbc1Cart✕
- Connections
- 1 pair of types, where a type in Cartridge uses a type in Cartridges.Mbc1Cart.
- The types involved
FameBoy.Cartridge.Mbc→FameBoy.Cartridges.Mbc1Cart.State
- Direction
- Cartridge uses Cartridges.Mbc1Cart, so a change to Cartridges.Mbc1Cart can break Cartridge, while a change to Cartridge can't break Cartridges.Mbc1Cart.
- Position
- Below the diagonal: Cartridge uses a module listed above it, which is the healthy direction.
17→3 Cartridge uses Cartridges.Mbc3Cart✕
- Connections
- 1 pair of types, where a type in Cartridge uses a type in Cartridges.Mbc3Cart.
- The types involved
FameBoy.Cartridge.Mbc→FameBoy.Cartridges.Mbc3Cart.State
- Direction
- Cartridge uses Cartridges.Mbc3Cart, so a change to Cartridges.Mbc3Cart can break Cartridge, while a change to Cartridge can't break Cartridges.Mbc3Cart.
- Position
- Below the diagonal: Cartridge uses a module listed above it, which is the healthy direction.
17→4 Cartridge uses Cartridges.Mbc5Cart✕
- Connections
- 1 pair of types, where a type in Cartridge uses a type in Cartridges.Mbc5Cart.
- The types involved
FameBoy.Cartridge.Mbc→FameBoy.Cartridges.Mbc5Cart.State
- Direction
- Cartridge uses Cartridges.Mbc5Cart, so a change to Cartridges.Mbc5Cart can break Cartridge, while a change to Cartridge can't break Cartridges.Mbc5Cart.
- Position
- Below the diagonal: Cartridge uses a module listed above it, which is the healthy direction.
18→7 Memory uses IoController✕
- Connections
- 1 pair of types, where a type in Memory uses a type in IoController.
- The types involved
FameBoy.Memory.Memory→FameBoy.IoController.IoController
- Direction
- Memory uses IoController, so a change to IoController can break Memory, while a change to Memory can't break IoController.
- Position
- Below the diagonal: Memory uses a module listed above it, which is the healthy direction.
19→7 Ppu.Lcdc uses IoController✕
- Connections
- 1 pair of types, where a type in Ppu.Lcdc uses a type in IoController.
- The types involved
FameBoy.Ppu.Lcdc.Lcdc→FameBoy.IoController.IoController
- Direction
- Ppu.Lcdc uses IoController, so a change to IoController can break Ppu.Lcdc, while a change to Ppu.Lcdc can't break IoController.
- Position
- Below the diagonal: Ppu.Lcdc uses a module listed above it, which is the healthy direction.
20→7 Ppu.Palettes uses IoController✕
- Connections
- 1 pair of types, where a type in Ppu.Palettes uses a type in IoController.
- The types involved
FameBoy.Ppu.Palettes.Palettes→FameBoy.IoController.IoController
- Direction
- Ppu.Palettes uses IoController, so a change to IoController can break Ppu.Palettes, while a change to Ppu.Palettes can't break IoController.
- Position
- Below the diagonal: Ppu.Palettes uses a module listed above it, which is the healthy direction.
21→1 Web.Audio uses Apu✕
- Connections
- 1 pair of types, where a type in Web.Audio uses a type in Apu.
- The types involved
FameBoy.Web.Audio.Audio→FameBoy.Apu.Apu
- Direction
- Web.Audio uses Apu, so a change to Apu can break Web.Audio, while a change to Web.Audio can't break Apu.
- Position
- Below the diagonal: Web.Audio uses a module listed above it, which is the healthy direction.
22→18 Cpu.State uses Memory✕
- Connections
- 2 pairs of types, where a type in Cpu.State uses a type in Memory.
- The types involved
FameBoy.Cpu.State.Cpu→FameBoy.Memory.MemoryFameBoy.Cpu.State.State→FameBoy.Memory.Memory
- Direction
- Cpu.State uses Memory, so a change to Memory can break Cpu.State, while a change to Cpu.State can't break Memory.
- Position
- Below the diagonal: Cpu.State uses a module listed above it, which is the healthy direction.
23→7 Ppu uses IoController✕
- Connections
- 1 pair of types, where a type in Ppu uses a type in IoController.
- The types involved
FameBoy.Ppu.Ppu→FameBoy.IoController.IoController
- Direction
- Ppu uses IoController, so a change to IoController can break Ppu, while a change to Ppu can't break IoController.
- Position
- Below the diagonal: Ppu uses a module listed above it, which is the healthy direction.
23→18 Ppu uses Memory✕
- Connections
- 1 pair of types, where a type in Ppu uses a type in Memory.
- The types involved
FameBoy.Ppu.Ppu→FameBoy.Memory.Memory
- Direction
- Ppu uses Memory, so a change to Memory can break Ppu, while a change to Ppu can't break Memory.
- Position
- Below the diagonal: Ppu uses a module listed above it, which is the healthy direction.
24→22 Cpu.Instructions.Operand uses Cpu.State✕
- Connections
- 2 pairs of types, where a type in Cpu.Instructions.Operand uses a type in Cpu.State.
- The types involved
FameBoy.Cpu.Instructions.Operand.Source→FameBoy.Cpu.State.CpuFameBoy.Cpu.Instructions.Operand.Target→FameBoy.Cpu.State.Cpu
- Direction
- Cpu.Instructions.Operand uses Cpu.State, so a change to Cpu.State can break Cpu.Instructions.Operand, while a change to Cpu.Instructions.Operand can't break Cpu.State.
- Position
- Below the diagonal: Cpu.Instructions.Operand uses a module listed above it, which is the healthy direction.
24→30 Cpu.Instructions.Operand uses Cpu.Instructions part of a loop✕
- Connections
- 2 pairs of types, where a type in Cpu.Instructions.Operand uses a type in Cpu.Instructions.
- The types involved
FameBoy.Cpu.Instructions.Operand.Source→FameBoy.Cpu.Instructions.Reg8FameBoy.Cpu.Instructions.Operand.Target→FameBoy.Cpu.Instructions.Reg8
- Direction
- Cpu.Instructions.Operand uses Cpu.Instructions, so a change to Cpu.Instructions can break Cpu.Instructions.Operand, while a change to Cpu.Instructions.Operand can't break Cpu.Instructions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→7 Ppu.Scanline uses IoController✕
- Connections
- 1 pair of types, where a type in Ppu.Scanline uses a type in IoController.
- The types involved
FameBoy.Ppu.Scanline.Scanline→FameBoy.IoController.IoController
- Direction
- Ppu.Scanline uses IoController, so a change to IoController can break Ppu.Scanline, while a change to Ppu.Scanline can't break IoController.
- Position
- Below the diagonal: Ppu.Scanline uses a module listed above it, which is the healthy direction.
25→23 Ppu.Scanline uses Ppu✕
- Connections
- 3 pairs of types, where a type in Ppu.Scanline uses a type in Ppu.
- The types involved
FameBoy.Ppu.Scanline.ObjPixel→FameBoy.Ppu.ShadeFameBoy.Ppu.Scanline.Scanline→FameBoy.Ppu.PpuFameBoy.Ppu.Scanline.Scanline→FameBoy.Ppu.Shade
- Direction
- Ppu.Scanline uses Ppu, so a change to Ppu can break Ppu.Scanline, while a change to Ppu.Scanline can't break Ppu.
- Position
- Below the diagonal: Ppu.Scanline uses a module listed above it, which is the healthy direction.
26→23 Ppu.ShadeModule uses Ppu✕
- Connections
- 1 pair of types, where a type in Ppu.ShadeModule uses a type in Ppu.
- The types involved
FameBoy.Ppu.ShadeModule.ShadeModule→FameBoy.Ppu.Shade
- Direction
- Ppu.ShadeModule uses Ppu, so a change to Ppu can break Ppu.ShadeModule, while a change to Ppu.ShadeModule can't break Ppu.
- Position
- Below the diagonal: Ppu.ShadeModule uses a module listed above it, which is the healthy direction.
27→23 Ppu.StatRegister uses Ppu✕
- Connections
- 1 pair of types, where a type in Ppu.StatRegister uses a type in Ppu.
- The types involved
FameBoy.Ppu.StatRegister.StatRegister→FameBoy.Ppu.Ppu
- Direction
- Ppu.StatRegister uses Ppu, so a change to Ppu can break Ppu.StatRegister, while a change to Ppu.StatRegister can't break Ppu.
- Position
- Below the diagonal: Ppu.StatRegister uses a module listed above it, which is the healthy direction.
28→23 Raylib.Graphics.GraphicsPipeline uses Ppu✕
- Connections
- 2 pairs of types, where a type in Raylib.Graphics.GraphicsPipeline uses a type in Ppu.
- The types involved
FameBoy.Raylib.Graphics.GraphicsPipeline.GraphicsPipeline→FameBoy.Ppu.PpuFameBoy.Raylib.Graphics.GraphicsPipeline.GraphicsPipeline→FameBoy.Ppu.Shade
- Direction
- Raylib.Graphics.GraphicsPipeline uses Ppu, so a change to Ppu can break Raylib.Graphics.GraphicsPipeline, while a change to Raylib.Graphics.GraphicsPipeline can't break Ppu.
- Position
- Below the diagonal: Raylib.Graphics.GraphicsPipeline uses a module listed above it, which is the healthy direction.
29→7 Startup uses IoController✕
- Connections
- 1 pair of types, where a type in Startup uses a type in IoController.
- The types involved
FameBoy.Startup.Startup→FameBoy.IoController.IoController
- Direction
- Startup uses IoController, so a change to IoController can break Startup, while a change to Startup can't break IoController.
- Position
- Below the diagonal: Startup uses a module listed above it, which is the healthy direction.
29→18 Startup uses Memory✕
- Connections
- 1 pair of types, where a type in Startup uses a type in Memory.
- The types involved
FameBoy.Startup.Startup→FameBoy.Memory.Memory
- Direction
- Startup uses Memory, so a change to Memory can break Startup, while a change to Startup can't break Memory.
- Position
- Below the diagonal: Startup uses a module listed above it, which is the healthy direction.
29→22 Startup uses Cpu.State✕
- Connections
- 1 pair of types, where a type in Startup uses a type in Cpu.State.
- The types involved
FameBoy.Startup.Startup→FameBoy.Cpu.State.Cpu
- Direction
- Startup uses Cpu.State, so a change to Cpu.State can break Startup, while a change to Startup can't break Cpu.State.
- Position
- Below the diagonal: Startup uses a module listed above it, which is the healthy direction.
30→5 Cpu.Instructions uses Cpu.Instructions.LoadTypes✕
- Connections
- 4 pairs of types, where a type in Cpu.Instructions uses a type in Cpu.Instructions.LoadTypes.
- The types involved
FameBoy.Cpu.Instructions.ControlInstr→FameBoy.Cpu.Instructions.LoadTypes.ConditionFameBoy.Cpu.Instructions.LoadInstr→FameBoy.Cpu.Instructions.LoadTypes.AHighSourceFameBoy.Cpu.Instructions.LoadInstr→FameBoy.Cpu.Instructions.LoadTypes.ASourceFameBoy.Cpu.Instructions.LoadInstr→FameBoy.Cpu.Instructions.LoadTypes.LoadA
- Direction
- Cpu.Instructions uses Cpu.Instructions.LoadTypes, so a change to Cpu.Instructions.LoadTypes can break Cpu.Instructions, while a change to Cpu.Instructions can't break Cpu.Instructions.LoadTypes.
- Position
- Below the diagonal: Cpu.Instructions uses a module listed above it, which is the healthy direction.
30→22 Cpu.Instructions uses Cpu.State✕
- Connections
- 2 pairs of types, where a type in Cpu.Instructions uses a type in Cpu.State.
- The types involved
FameBoy.Cpu.Instructions.Reg16→FameBoy.Cpu.State.CpuFameBoy.Cpu.Instructions.Reg8→FameBoy.Cpu.State.Cpu
- Direction
- Cpu.Instructions uses Cpu.State, so a change to Cpu.State can break Cpu.Instructions, while a change to Cpu.Instructions can't break Cpu.State.
- Position
- Below the diagonal: Cpu.Instructions uses a module listed above it, which is the healthy direction.
30→24 Cpu.Instructions uses Cpu.Instructions.Operand✕
- Connections
- 6 pairs of types, where a type in Cpu.Instructions uses a type in Cpu.Instructions.Operand.
- The types involved
FameBoy.Cpu.Instructions.ArithmeticInstr→FameBoy.Cpu.Instructions.Operand.SourceFameBoy.Cpu.Instructions.ArithmeticInstr→FameBoy.Cpu.Instructions.Operand.TargetFameBoy.Cpu.Instructions.BitwiseInstr→FameBoy.Cpu.Instructions.Operand.TargetFameBoy.Cpu.Instructions.LoadInstr→FameBoy.Cpu.Instructions.Operand.SourceFameBoy.Cpu.Instructions.LoadInstr→FameBoy.Cpu.Instructions.Operand.TargetFameBoy.Cpu.Instructions.LogicInstr→FameBoy.Cpu.Instructions.Operand.Source
- Direction
- Cpu.Instructions uses Cpu.Instructions.Operand, so a change to Cpu.Instructions.Operand can break Cpu.Instructions, while a change to Cpu.Instructions can't break Cpu.Instructions.Operand.
- Position
- Below the diagonal: Cpu.Instructions uses a module listed above it, which is the healthy direction.
31→6 Cpu.Execute uses Interrupts✕
- Connections
- 1 pair of types, where a type in Cpu.Execute uses a type in Interrupts.
- The types involved
FameBoy.Cpu.Execute.Execute→FameBoy.Interrupts.InterruptType
- Direction
- Cpu.Execute uses Interrupts, so a change to Interrupts can break Cpu.Execute, while a change to Cpu.Execute can't break Interrupts.
- Position
- Below the diagonal: Cpu.Execute uses a module listed above it, which is the healthy direction.
31→7 Cpu.Execute uses IoController✕
- Connections
- 1 pair of types, where a type in Cpu.Execute uses a type in IoController.
- The types involved
FameBoy.Cpu.Execute.Execute→FameBoy.IoController.IoController
- Direction
- Cpu.Execute uses IoController, so a change to IoController can break Cpu.Execute, while a change to Cpu.Execute can't break IoController.
- Position
- Below the diagonal: Cpu.Execute uses a module listed above it, which is the healthy direction.
31→22 Cpu.Execute uses Cpu.State✕
- Connections
- 1 pair of types, where a type in Cpu.Execute uses a type in Cpu.State.
- The types involved
FameBoy.Cpu.Execute.Execute→FameBoy.Cpu.State.Cpu
- Direction
- Cpu.Execute uses Cpu.State, so a change to Cpu.State can break Cpu.Execute, while a change to Cpu.Execute can't break Cpu.State.
- Position
- Below the diagonal: Cpu.Execute uses a module listed above it, which is the healthy direction.
31→30 Cpu.Execute uses Cpu.Instructions✕
- Connections
- 1 pair of types, where a type in Cpu.Execute uses a type in Cpu.Instructions.
- The types involved
FameBoy.Cpu.Execute.Execute→FameBoy.Cpu.Instructions.DecodedInstruction
- Direction
- Cpu.Execute uses Cpu.Instructions, so a change to Cpu.Instructions can break Cpu.Execute, while a change to Cpu.Execute can't break Cpu.Instructions.
- Position
- Below the diagonal: Cpu.Execute uses a module listed above it, which is the healthy direction.
32→22 Cpu.Executors.Arithmetic uses Cpu.State✕
- Connections
- 1 pair of types, where a type in Cpu.Executors.Arithmetic uses a type in Cpu.State.
- The types involved
FameBoy.Cpu.Executors.Arithmetic.Arithmetic→FameBoy.Cpu.State.Cpu
- Direction
- Cpu.Executors.Arithmetic uses Cpu.State, so a change to Cpu.State can break Cpu.Executors.Arithmetic, while a change to Cpu.Executors.Arithmetic can't break Cpu.State.
- Position
- Below the diagonal: Cpu.Executors.Arithmetic uses a module listed above it, which is the healthy direction.
32→30 Cpu.Executors.Arithmetic uses Cpu.Instructions✕
- Connections
- 1 pair of types, where a type in Cpu.Executors.Arithmetic uses a type in Cpu.Instructions.
- The types involved
FameBoy.Cpu.Executors.Arithmetic.Arithmetic→FameBoy.Cpu.Instructions.ArithmeticInstr
- Direction
- Cpu.Executors.Arithmetic uses Cpu.Instructions, so a change to Cpu.Instructions can break Cpu.Executors.Arithmetic, while a change to Cpu.Executors.Arithmetic can't break Cpu.Instructions.
- Position
- Below the diagonal: Cpu.Executors.Arithmetic uses a module listed above it, which is the healthy direction.
33→22 Cpu.Executors.Bitwise uses Cpu.State✕
- Connections
- 1 pair of types, where a type in Cpu.Executors.Bitwise uses a type in Cpu.State.
- The types involved
FameBoy.Cpu.Executors.Bitwise.Bitwise→FameBoy.Cpu.State.Cpu
- Direction
- Cpu.Executors.Bitwise uses Cpu.State, so a change to Cpu.State can break Cpu.Executors.Bitwise, while a change to Cpu.Executors.Bitwise can't break Cpu.State.
- Position
- Below the diagonal: Cpu.Executors.Bitwise uses a module listed above it, which is the healthy direction.
33→24 Cpu.Executors.Bitwise uses Cpu.Instructions.Operand✕
- Connections
- 1 pair of types, where a type in Cpu.Executors.Bitwise uses a type in Cpu.Instructions.Operand.
- The types involved
FameBoy.Cpu.Executors.Bitwise.Bitwise→FameBoy.Cpu.Instructions.Operand.Target
- Direction
- Cpu.Executors.Bitwise uses Cpu.Instructions.Operand, so a change to Cpu.Instructions.Operand can break Cpu.Executors.Bitwise, while a change to Cpu.Executors.Bitwise can't break Cpu.Instructions.Operand.
- Position
- Below the diagonal: Cpu.Executors.Bitwise uses a module listed above it, which is the healthy direction.
33→30 Cpu.Executors.Bitwise uses Cpu.Instructions✕
- Connections
- 1 pair of types, where a type in Cpu.Executors.Bitwise uses a type in Cpu.Instructions.
- The types involved
FameBoy.Cpu.Executors.Bitwise.Bitwise→FameBoy.Cpu.Instructions.BitwiseInstr
- Direction
- Cpu.Executors.Bitwise uses Cpu.Instructions, so a change to Cpu.Instructions can break Cpu.Executors.Bitwise, while a change to Cpu.Executors.Bitwise can't break Cpu.Instructions.
- Position
- Below the diagonal: Cpu.Executors.Bitwise uses a module listed above it, which is the healthy direction.
34→5 Cpu.Executors.Control uses Cpu.Instructions.LoadTypes✕
- Connections
- 1 pair of types, where a type in Cpu.Executors.Control uses a type in Cpu.Instructions.LoadTypes.
- The types involved
FameBoy.Cpu.Executors.Control.Control→FameBoy.Cpu.Instructions.LoadTypes.Condition
- Direction
- Cpu.Executors.Control uses Cpu.Instructions.LoadTypes, so a change to Cpu.Instructions.LoadTypes can break Cpu.Executors.Control, while a change to Cpu.Executors.Control can't break Cpu.Instructions.LoadTypes.
- Position
- Below the diagonal: Cpu.Executors.Control uses a module listed above it, which is the healthy direction.
34→22 Cpu.Executors.Control uses Cpu.State✕
- Connections
- 1 pair of types, where a type in Cpu.Executors.Control uses a type in Cpu.State.
- The types involved
FameBoy.Cpu.Executors.Control.Control→FameBoy.Cpu.State.Cpu
- Direction
- Cpu.Executors.Control uses Cpu.State, so a change to Cpu.State can break Cpu.Executors.Control, while a change to Cpu.Executors.Control can't break Cpu.State.
- Position
- Below the diagonal: Cpu.Executors.Control uses a module listed above it, which is the healthy direction.
34→30 Cpu.Executors.Control uses Cpu.Instructions✕
- Connections
- 1 pair of types, where a type in Cpu.Executors.Control uses a type in Cpu.Instructions.
- The types involved
FameBoy.Cpu.Executors.Control.Control→FameBoy.Cpu.Instructions.ControlInstr
- Direction
- Cpu.Executors.Control uses Cpu.Instructions, so a change to Cpu.Instructions can break Cpu.Executors.Control, while a change to Cpu.Executors.Control can't break Cpu.Instructions.
- Position
- Below the diagonal: Cpu.Executors.Control uses a module listed above it, which is the healthy direction.
35→22 Cpu.Executors.Load uses Cpu.State✕
- Connections
- 1 pair of types, where a type in Cpu.Executors.Load uses a type in Cpu.State.
- The types involved
FameBoy.Cpu.Executors.Load.Load→FameBoy.Cpu.State.Cpu
- Direction
- Cpu.Executors.Load uses Cpu.State, so a change to Cpu.State can break Cpu.Executors.Load, while a change to Cpu.Executors.Load can't break Cpu.State.
- Position
- Below the diagonal: Cpu.Executors.Load uses a module listed above it, which is the healthy direction.
35→30 Cpu.Executors.Load uses Cpu.Instructions✕
- Connections
- 1 pair of types, where a type in Cpu.Executors.Load uses a type in Cpu.Instructions.
- The types involved
FameBoy.Cpu.Executors.Load.Load→FameBoy.Cpu.Instructions.LoadInstr
- Direction
- Cpu.Executors.Load uses Cpu.Instructions, so a change to Cpu.Instructions can break Cpu.Executors.Load, while a change to Cpu.Executors.Load can't break Cpu.Instructions.
- Position
- Below the diagonal: Cpu.Executors.Load uses a module listed above it, which is the healthy direction.
36→22 Cpu.Executors.Logic uses Cpu.State✕
- Connections
- 1 pair of types, where a type in Cpu.Executors.Logic uses a type in Cpu.State.
- The types involved
FameBoy.Cpu.Executors.Logic.Logic→FameBoy.Cpu.State.Cpu
- Direction
- Cpu.Executors.Logic uses Cpu.State, so a change to Cpu.State can break Cpu.Executors.Logic, while a change to Cpu.Executors.Logic can't break Cpu.State.
- Position
- Below the diagonal: Cpu.Executors.Logic uses a module listed above it, which is the healthy direction.
36→30 Cpu.Executors.Logic uses Cpu.Instructions✕
- Connections
- 1 pair of types, where a type in Cpu.Executors.Logic uses a type in Cpu.Instructions.
- The types involved
FameBoy.Cpu.Executors.Logic.Logic→FameBoy.Cpu.Instructions.LogicInstr
- Direction
- Cpu.Executors.Logic uses Cpu.Instructions, so a change to Cpu.Instructions can break Cpu.Executors.Logic, while a change to Cpu.Executors.Logic can't break Cpu.Instructions.
- Position
- Below the diagonal: Cpu.Executors.Logic uses a module listed above it, which is the healthy direction.
37→24 Cpu.Instructions.LengthsAndCycles uses Cpu.Instructions.Operand✕
- Connections
- 1 pair of types, where a type in Cpu.Instructions.LengthsAndCycles uses a type in Cpu.Instructions.Operand.
- The types involved
FameBoy.Cpu.Instructions.LengthsAndCycles.LengthsAndCycles→FameBoy.Cpu.Instructions.Operand.Source
- Direction
- Cpu.Instructions.LengthsAndCycles uses Cpu.Instructions.Operand, so a change to Cpu.Instructions.Operand can break Cpu.Instructions.LengthsAndCycles, while a change to Cpu.Instructions.LengthsAndCycles can't break Cpu.Instructions.Operand.
- Position
- Below the diagonal: Cpu.Instructions.LengthsAndCycles uses a module listed above it, which is the healthy direction.
37→30 Cpu.Instructions.LengthsAndCycles uses Cpu.Instructions✕
- Connections
- 4 pairs of types, where a type in Cpu.Instructions.LengthsAndCycles uses a type in Cpu.Instructions.
- The types involved
FameBoy.Cpu.Instructions.LengthsAndCycles.LengthsAndCycles→FameBoy.Cpu.Instructions.ArithmeticInstrFameBoy.Cpu.Instructions.LengthsAndCycles.LengthsAndCycles→FameBoy.Cpu.Instructions.ControlInstrFameBoy.Cpu.Instructions.LengthsAndCycles.LengthsAndCycles→FameBoy.Cpu.Instructions.LoadInstrFameBoy.Cpu.Instructions.LengthsAndCycles.LengthsAndCycles→FameBoy.Cpu.Instructions.LogicInstr
- Direction
- Cpu.Instructions.LengthsAndCycles uses Cpu.Instructions, so a change to Cpu.Instructions can break Cpu.Instructions.LengthsAndCycles, while a change to Cpu.Instructions.LengthsAndCycles can't break Cpu.Instructions.
- Position
- Below the diagonal: Cpu.Instructions.LengthsAndCycles uses a module listed above it, which is the healthy direction.
38→18 Cpu.Opcodes uses Memory✕
- Connections
- 1 pair of types, where a type in Cpu.Opcodes uses a type in Memory.
- The types involved
FameBoy.Cpu.Opcodes.Opcodes→FameBoy.Memory.Memory
- Direction
- Cpu.Opcodes uses Memory, so a change to Memory can break Cpu.Opcodes, while a change to Cpu.Opcodes can't break Memory.
- Position
- Below the diagonal: Cpu.Opcodes uses a module listed above it, which is the healthy direction.
38→30 Cpu.Opcodes uses Cpu.Instructions✕
- Connections
- 1 pair of types, where a type in Cpu.Opcodes uses a type in Cpu.Instructions.
- The types involved
FameBoy.Cpu.Opcodes.Opcodes→FameBoy.Cpu.Instructions.DecodedInstruction
- Direction
- Cpu.Opcodes uses Cpu.Instructions, so a change to Cpu.Instructions can break Cpu.Opcodes, while a change to Cpu.Opcodes can't break Cpu.Instructions.
- Position
- Below the diagonal: Cpu.Opcodes uses a module listed above it, which is the healthy direction.
39→30 Cpu.Opcodes.TwoByteInstructions uses Cpu.Instructions✕
- Connections
- 1 pair of types, where a type in Cpu.Opcodes.TwoByteInstructions uses a type in Cpu.Instructions.
- The types involved
FameBoy.Cpu.Opcodes.TwoByteInstructions.TwoByteInstructions→FameBoy.Cpu.Instructions.Instruction
- Direction
- Cpu.Opcodes.TwoByteInstructions uses Cpu.Instructions, so a change to Cpu.Instructions can break Cpu.Opcodes.TwoByteInstructions, while a change to Cpu.Opcodes.TwoByteInstructions can't break Cpu.Instructions.
- Position
- Below the diagonal: Cpu.Opcodes.TwoByteInstructions uses a module listed above it, which is the healthy direction.
40→18 Cpu.Utils uses Memory✕
- Connections
- 1 pair of types, where a type in Cpu.Utils uses a type in Memory.
- The types involved
FameBoy.Cpu.Utils.Utils→FameBoy.Memory.Memory
- Direction
- Cpu.Utils uses Memory, so a change to Memory can break Cpu.Utils, while a change to Cpu.Utils can't break Memory.
- Position
- Below the diagonal: Cpu.Utils uses a module listed above it, which is the healthy direction.
40→22 Cpu.Utils uses Cpu.State✕
- Connections
- 1 pair of types, where a type in Cpu.Utils uses a type in Cpu.State.
- The types involved
FameBoy.Cpu.Utils.Utils→FameBoy.Cpu.State.Cpu
- Direction
- Cpu.Utils uses Cpu.State, so a change to Cpu.State can break Cpu.Utils, while a change to Cpu.Utils can't break Cpu.State.
- Position
- Below the diagonal: Cpu.Utils uses a module listed above it, which is the healthy direction.
40→30 Cpu.Utils uses Cpu.Instructions✕
- Connections
- 1 pair of types, where a type in Cpu.Utils uses a type in Cpu.Instructions.
- The types involved
FameBoy.Cpu.Utils.Utils→FameBoy.Cpu.Instructions.Reg16
- Direction
- Cpu.Utils uses Cpu.Instructions, so a change to Cpu.Instructions can break Cpu.Utils, while a change to Cpu.Utils can't break Cpu.Instructions.
- Position
- Below the diagonal: Cpu.Utils uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 11 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | High / Critical |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +7.5 pts | Medium | Observability |
| Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with FameBoy.Test.fsproj. | +1.8 pts | Low | Dependency Hygiene |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +3.1 pts | Medium | Visual & motion safety |
| Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI. | +2.7 pts | Medium | A11y enforcement |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.1 pts | Low | ADR Quality |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +2.3 pts | Medium | Page structure |
| 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. | +1.0 pts | Medium | Architecture documentation |
| Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). | +0.5 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/FameBoy/Ppu.fs | 7.4 | Mixed | Cyclomatic Complexity: Ppu.stepPpu (cyclomatic 16) |
| src/FameBoy/Apu.fs | 7.4 | Mixed | Cognitive Complexity: SoundProcessing.getMixedSample (cognitive 16) |
| src/FameBoy/Cpu/Instructions.fs | 8.5 | Near-clean | Cyclomatic Complexity: LengthsAndCycles.forLoad (cyclomatic 21) |
| src/FameBoy/Cpu/Executors/Control.fs | 8.5 | Near-clean | Cyclomatic Complexity: Control.executeControl (cyclomatic 16) |
| src/FameBoy.Web/Audio.fs | 8.5 | Near-clean | Cognitive Complexity: Audio.tryQueueAudio (cognitive 21) |
| src/FameBoy/Cartridges/Cartridge.fs | 8.5 | Near-clean | Cognitive Complexity: Cartridge.handleCartridgeWrite (cognitive 16) |
| src/FameBoy/Cpu/Executors/Arithmetic.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| src/FameBoy.Raylib/FameBoy.Raylib.fsproj | 8.5 | Near-clean | Code Coverage: No test project references FameBoy.Raylib |
| src/FameBoy.Web/FameBoy.Web.fsproj | 8.5 | Near-clean | Code Coverage: No test project references FameBoy.Web |
| src/FameBoy.Benchmark.Web/FameBoy.Benchmark.Web.fsproj | 8.5 | Near-clean | Code Coverage: No test project references FameBoy.Benchmark.Web |
| src/FameBoy.Test/FameBoy.Test.fsproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: coverlet.collector |
| src/FameBoy/Cpu/Opcodes.fs | 9.5 | Near-clean | IL Efficiency: IL efficiency: 4 authored method(s) exceed the IL budget |
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
Watchdog 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. 50 of 50 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 50 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, 38 of 54 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D12 Dependency Hygiene — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares npm dependencies as well as NuGet ones — manifests: src/FameBoy.Benchmark.Web/package.json, src/FameBoy.Web/package.json — and the counts on this row cover the NuGet side ONLY. This dimension reads dependency currency from `<PackageReference>` elements via `dotnet list package`; it does not read them, so the npm packages declared there were not checked for newer, deprecated or unmaintained releases. Their absence from the counts above is a gap in this analyzer's ecosystem coverage — not a finding that those dependencies are current.
- 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 (3 contributor(s) across 223 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 2 hold 2% 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.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog 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 — Watchdog 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — Watchdog 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- AX6 Interface segregation — not measured this run — Watchdog 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 computed over the public interfaces this run's compilations declare, and none was loaded, 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.
- AXR1 Runtime accessibility — not measured this run — Watchdog 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. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- C1 Data Protection — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- S1 Web-Security Posture — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D1 · Cyclomatic Complexity
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was LengthsAndCycles.forLoad at 21. A further 4 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 Opcodes.fetchAndDecode at 246 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/FameBoy/Cpu/Opcodes.fs (Opcodes.fetchAndDecode at 246), src/FameBoy/Cpu/Executors/Load.fs (Load.executeLoad at 24), src/FameBoy/Cpu/Execute.fs (Execute.execute at 18), src/FameBoy/Cpu/Executors/Bitwise.fs (Bitwise.executeBitwise at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with LengthsAndCycles.forLoad (cyclomatic 21), Ppu.stepPpu (cyclomatic 16), Control.executeControl (cyclomatic 16). — 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 3 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
5 method(s) exceeded the cognitive complexity threshold of 15; the worst was Ppu.stepPpu at 33.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with Ppu.stepPpu (cognitive 33), Audio.tryQueueAudio (cognitive 21), Scanline.renderScanline (cognitive 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 5 together lifts Cognitive Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
3 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Apu.fs (2), Arithmetic.fs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
6 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D8 · Code Coverage
Line coverage 89.2%.
What to do
- Resolve the 1 No test project references FameBoy.Raylib finding(s) in Code Coverage — start with FameBoy.Raylib.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references FameBoy.Web finding(s) in Code Coverage — start with FameBoy.Web.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references FameBoy.Benchmark.Web finding(s) in Code Coverage — start with FameBoy.Benchmark.Web.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 1 measured tier(s). other: measured (0 flaky).
D12 · Dependency Hygiene
8 outdated, 0 vulnerable, 0 deprecated packages. NuGet only — this repository also declares npm dependencies, which are not read for currency here.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 144 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 10 direct `PackageReference`(s), and 133 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
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).
D26 · Project Cohesion
0 of 5 build units (MSBuild, npm) flagged as possibly oversized/incoherent.
D27 · Navigability
96 % of calls cross a namespace and 1 % go through an interface, but 70 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Improve Navigability — currently 8.5/10. — 96 % of calls cross a namespace and 1 % go through an interface, but 70 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 11 high, 0 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 10 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 4 high, 0 medium, 0 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 17 of the 37 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D39 · IL Efficiency
4 of 331 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 6 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/FameBoy.Web/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.d-pad` moves (`transition: transform 0.1s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/FameBoy.Web/styles.css:390
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 1 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — src/FameBoy.Web/package.json:13
What to do
- Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Add a README to the 2 of 2 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 2675 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `src/FameBoy.Benchmark.Web/FameBoy.Benchmark.Web.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/FameBoy.Benchmark.Web/FameBoy.Benchmark.Web.fsproj:13
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
PF1 · Benchmark discipline
- A F#/VB BenchmarkDotNet suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — src/FameBoy.Benchmark/Program.fs
What to do
- Add [<MemoryDiagnoser>] to the benchmarks so allocation regressions are visible, not just time.
PF2 · Allocation hygiene
PF3 · Async & latency hygiene
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 95% | Exemplary | Strongest area. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 79% | Strong | Solid. |
| Readiness | 46% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 77% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 58% | Adequate — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 91% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 64 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads. Its F# is compiled by Fable to JavaScript, which runs on one event loop, so no two requests write a shared object at the same instant.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) 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
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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 — ~3469 lines of test source are present (.fs) 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 3 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (1 with fewer than two methods, 2 stateless), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D9 Test Distribution — Test source is present (.fs) 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 — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 24 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- 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
- 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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- 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.
- 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.
- 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
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 21 finding(s)
- Duplicated block (5 lines × 2) src/FameBoy/Apu.fs:198
- Duplicated block (5 lines × 2) src/FameBoy/Apu.fs:418
- Duplicated block (5 lines × 2) src/FameBoy/Cpu/Executors/Arithmetic.fs:75
- Page without a main landmark src/FameBoy.Web/index.html:2
- Animation without a prefers-reduced-motion guard src/FameBoy.Web/styles.css:390
- Accessibility enforcement below the top rung src/FameBoy.Web/package.json:13
- LengthsAndCycles.forLoad (cyclomatic 21) src/FameBoy/Cpu/Instructions.fs:275
- Ppu.stepPpu (cyclomatic 16) src/FameBoy/Ppu.fs:320
- Control.executeControl (cyclomatic 16) src/FameBoy/Cpu/Executors/Control.fs:24
- Ppu.stepPpu (cognitive 33) src/FameBoy/Ppu.fs:320
- Audio.tryQueueAudio (cognitive 21) src/FameBoy.Web/Audio.fs:92
- Scanline.renderScanline (cognitive 18) src/FameBoy/Ppu.fs:223
- SoundProcessing.getMixedSample (cognitive 16) src/FameBoy/Apu.fs:406
- Cartridge.handleCartridgeWrite (cognitive 16) src/FameBoy/Cartridges/Cartridge.fs:77
- REDACTED
- REDACTED
- No test project references FameBoy.Raylib src/FameBoy.Raylib/FameBoy.Raylib.fsproj
- No test project references FameBoy.Web src/FameBoy.Web/FameBoy.Web.fsproj
- No test project references FameBoy.Benchmark.Web src/FameBoy.Benchmark.Web/FameBoy.Benchmark.Web.fsproj
- No structured logging
- NuGet dependencies are not locked
Minor — 11 finding(s)
- Outdated: coverlet.collector src/FameBoy.Test/FameBoy.Test.fsproj:38
- No ADRs found
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- IL efficiency: 4 authored method(s) exceed the IL budget src/FameBoy/Cpu/Opcodes.fs:42
- No ADRs
- No SAST REDACTED:6
- No dependency-update automation src/FameBoy.Benchmark.Web/FameBoy.Benchmark.Web.fsproj:13
- Benchmarks don't track allocations src/FameBoy.Benchmark/Program.fs
Minor — 7 finding(s)
- Outdated: FSharp.Core
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: NUnit
- Outdated: NUnit.Analyzers
- Outdated: NUnit3TestAdapter
- Outdated: Raylib-cs
- Outdated: Fable.Core
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2ec8a658ecba4196ac4ad96e263aeea5/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2ec8a658ecba4196ac4ad96e263aeea5/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-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 . | 11 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list FameBoy.sln package --vulnerable --include-transitive --format json | 4 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |