Executive summary
mattstermiller/koffee falls short of our standard for a preview release because we found no working pipeline that builds or tests changes to the code and no logging, tracing or health checks in the code. It scores 55 out of 100 and is rated Adequate, and its one critical finding is a security problem in the packages it uses.
Production Readiness, at 29, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 9 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 8 points. Raising Production Readiness to 62 would lift the score to about 69.
One known security hole in a package the code depends on can be used by attackers. Updating the vulnerable packages would close this risk.
The product code is 6,873 lines, about €15,000 to rebuild.
If Production Readiness rose from 29 to 62, the lowest score rated Strong, the score would rise from 55 to about 69.
Fixed since the last survey: 1 finding
- Code Coverage · Coverage not measured — no coverage collector is wired up
Rebuild cost: about €15,000 · Estimate
| Cost to rebuild | €5,100 to €26,000, for 85 to 269 hours of work, about 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 55. 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: 6,873 lines of product code |
| Comment lines | The estimate prices 6,863 lines. Comment lines count towards the size of 6,873 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Build | 2 Koffee.DataFormats | 3 Koffee.FSharpJsonConverters | 4 Koffee.Key | 5 Koffee.KeyChordModule | 6 Koffee.KeyComboModule | 7 Koffee.KeyPatterns | 8 Koffee.LinkFile | 9 Koffee.OsInterop | 10 Koffee.TextEdit | 11 Utility | 12 Koffee.MainStatus | 13 UIHelpers | 14 Utility.Rect | 15 Koffee | 16 Koffee.CommandUtil | 17 Koffee.CursorCommands | 18 Koffee.DragDropEffects | 19 Koffee.ItemActionCommands | 20 Koffee.ItemActionCommands.Attributes | 21 Koffee.ItemActionCommands.Create | 22 Koffee.ItemActionCommands.Delete | 23 Koffee.ItemActionCommands.Put | 24 Koffee.ItemActionCommands.Put.MoveUtil | 25 Koffee.ItemActionCommands.Rename | 26 Koffee.ItemActionCommands.Tools | 27 Koffee.ItemActionCommands.Undo | 28 Koffee.KeyBinder | 29 Koffee.KeyBinding | 30 Koffee.MainBindings | 31 Koffee.MainView | 32 Koffee.NavigationCommands | 33 Koffee.OsUtility | 34 Koffee.ProgramOptions | 35 Koffee.SortFieldModule | 36 Koffee.ToolEdit | 37 Koffee.WindowCommands | 38 Koffee.KeyBinder.KeyBinderBinding | 39 Koffee.MainController | 40 Koffee.Settings |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Build | ||||||||||||||||||||||||||||||||||||||||
| 2 Koffee.DataFormats | ||||||||||||||||||||||||||||||||||||||||
| 3 Koffee.FSharpJsonConverters | ||||||||||||||||||||||||||||||||||||||||
| 4 Koffee.Key | ||||||||||||||||||||||||||||||||||||||||
| 5 Koffee.KeyChordModule | ||||||||||||||||||||||||||||||||||||||||
| 6 Koffee.KeyComboModule | ||||||||||||||||||||||||||||||||||||||||
| 7 Koffee.KeyPatterns | ||||||||||||||||||||||||||||||||||||||||
| 8 Koffee.LinkFile | ||||||||||||||||||||||||||||||||||||||||
| 9 Koffee.OsInterop | ||||||||||||||||||||||||||||||||||||||||
| 10 Koffee.TextEdit | ||||||||||||||||||||||||||||||||||||||||
| 11 Utility | ||||||||||||||||||||||||||||||||||||||||
| 12 Koffee.MainStatus | 20 | |||||||||||||||||||||||||||||||||||||||
| 13 UIHelpers | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 Utility.Rect | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Koffee | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 Koffee.CommandUtil | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 17 Koffee.CursorCommands | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 18 Koffee.DragDropEffects | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Koffee.ItemActionCommands | 1 | 10 | ||||||||||||||||||||||||||||||||||||||
| 20 Koffee.ItemActionCommands.Attributes | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 21 Koffee.ItemActionCommands.Create | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 22 Koffee.ItemActionCommands.Delete | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 23 Koffee.ItemActionCommands.Put | 1 | 15 | ||||||||||||||||||||||||||||||||||||||
| 24 Koffee.ItemActionCommands.Put.MoveUtil | 4 | |||||||||||||||||||||||||||||||||||||||
| 25 Koffee.ItemActionCommands.Rename | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 26 Koffee.ItemActionCommands.Tools | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 27 Koffee.ItemActionCommands.Undo | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 28 Koffee.KeyBinder | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 29 Koffee.KeyBinding | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 Koffee.MainBindings | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 Koffee.MainView | 6 | |||||||||||||||||||||||||||||||||||||||
| 32 Koffee.NavigationCommands | 2 | 2 | 23 | |||||||||||||||||||||||||||||||||||||
| 33 Koffee.OsUtility | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 Koffee.ProgramOptions | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 Koffee.SortFieldModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 Koffee.ToolEdit | 3 | |||||||||||||||||||||||||||||||||||||||
| 37 Koffee.WindowCommands | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 38 Koffee.KeyBinder.KeyBinderBinding | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 Koffee.MainController | 1 | 10 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 Koffee.Settings | 1 | 1 | 11 | 3 | 1 |
12→15 Koffee.MainStatus uses Koffee part of a loop✕
- Connections
- 20 pairs of types, where a type in Koffee.MainStatus uses a type in Koffee.
- The types involved
Koffee.MainStatus.Busy→Koffee.ItemKoffee.MainStatus.Busy→Koffee.ItemRefKoffee.MainStatus.Busy→Koffee.PathFormatKoffee.MainStatus.Busy→Koffee.PutIntentKoffee.MainStatus.Busy→Koffee.PutTypeKoffee.MainStatus.Error→Koffee.ItemKoffee.MainStatus.Error→Koffee.ItemActionKoffee.MainStatus.Error→Koffee.ItemTypeKoffee.MainStatus.Error→Koffee.PathKoffee.MainStatus.Error→Koffee.PathFormatKoffee.MainStatus.Error→Koffee.PutTypeKoffee.MainStatus.Error→Koffee.ToolVariableKoffee.MainStatus.MainStatus→Koffee.ItemActionKoffee.MainStatus.MainStatus→Koffee.PathFormatKoffee.MainStatus.Message→Koffee.ConfirmTypeKoffee.MainStatus.Message→Koffee.ItemActionKoffee.MainStatus.Message→Koffee.PathKoffee.MainStatus.Message→Koffee.PathFormatKoffee.MainStatus.Message→Koffee.PutTypeKoffee.MainStatus.Message→Koffee.Search
- Direction
- Koffee.MainStatus uses Koffee, so a change to Koffee can break Koffee.MainStatus, while a change to Koffee.MainStatus can't break Koffee.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→11 UIHelpers uses Utility✕
- Connections
- 2 pairs of types, where a type in UIHelpers uses a type in Utility.
- The types involved
UIHelpers.UIHelpers→Utility.KeyPressHandlerUIHelpers.UIHelpers→Utility.Rectangle
- Direction
- UIHelpers uses Utility, so a change to Utility can break UIHelpers, while a change to UIHelpers can't break Utility.
- Position
- Below the diagonal: UIHelpers uses a module listed above it, which is the healthy direction.
14→11 Utility.Rect uses Utility✕
- Connections
- 1 pair of types, where a type in Utility.Rect uses a type in Utility.
- The types involved
Utility.Rect.Rect→Utility.Rectangle
- Direction
- Utility.Rect uses Utility, so a change to Utility can break Utility.Rect, while a change to Utility.Rect can't break Utility.
- Position
- Below the diagonal: Utility.Rect uses a module listed above it, which is the healthy direction.
15→11 Koffee uses Utility✕
- Connections
- 3 pairs of types, where a type in Koffee uses a type in Utility.
- The types involved
Koffee.InputEvent→Utility.KeyPressHandlerKoffee.MainEvent→Utility.KeyPressHandlerKoffee.MainModel→Utility.SetValue`1
- Direction
- Koffee uses Utility, so a change to Utility can break Koffee, while a change to Koffee can't break Utility.
- Position
- Below the diagonal: Koffee uses a module listed above it, which is the healthy direction.
15→12 Koffee uses Koffee.MainStatus✕
- Connections
- 2 pairs of types, where a type in Koffee uses a type in Koffee.MainStatus.
- The types involved
Koffee.MainModel→Koffee.MainStatus.ErrorKoffee.MainModel→Koffee.MainStatus.StatusType
- Direction
- Koffee uses Koffee.MainStatus, so a change to Koffee.MainStatus can break Koffee, while a change to Koffee can't break Koffee.MainStatus.
- Position
- Below the diagonal: Koffee uses a module listed above it, which is the healthy direction.
16→11 Koffee.CommandUtil uses Utility✕
- Connections
- 1 pair of types, where a type in Koffee.CommandUtil uses a type in Utility.
- The types involved
Koffee.CommandUtil.CommandUtil→Utility.KeyPressHandler
- Direction
- Koffee.CommandUtil uses Utility, so a change to Utility can break Koffee.CommandUtil, while a change to Koffee.CommandUtil can't break Utility.
- Position
- Below the diagonal: Koffee.CommandUtil uses a module listed above it, which is the healthy direction.
16→12 Koffee.CommandUtil uses Koffee.MainStatus✕
- Connections
- 1 pair of types, where a type in Koffee.CommandUtil uses a type in Koffee.MainStatus.
- The types involved
Koffee.CommandUtil.CommandUtil→Koffee.MainStatus.Error
- Direction
- Koffee.CommandUtil uses Koffee.MainStatus, so a change to Koffee.MainStatus can break Koffee.CommandUtil, while a change to Koffee.CommandUtil can't break Koffee.MainStatus.
- Position
- Below the diagonal: Koffee.CommandUtil uses a module listed above it, which is the healthy direction.
16→15 Koffee.CommandUtil uses Koffee✕
- Connections
- 4 pairs of types, where a type in Koffee.CommandUtil uses a type in Koffee.
- The types involved
Koffee.CommandUtil.CommandUtil→Koffee.IFileSystemReaderKoffee.CommandUtil.CommandUtil→Koffee.ItemActionKoffee.CommandUtil.CommandUtil→Koffee.MainModelKoffee.CommandUtil.CommandUtil→Koffee.Path
- Direction
- Koffee.CommandUtil uses Koffee, so a change to Koffee can break Koffee.CommandUtil, while a change to Koffee.CommandUtil can't break Koffee.
- Position
- Below the diagonal: Koffee.CommandUtil uses a module listed above it, which is the healthy direction.
17→13 Koffee.CursorCommands uses UIHelpers✕
- Connections
- 2 pairs of types, where a type in Koffee.CursorCommands uses a type in UIHelpers.
- The types involved
Koffee.CursorCommands.CursorCommands→UIHelpers.DataGridScrollerKoffee.CursorCommands.Handler→UIHelpers.DataGridScroller
- Direction
- Koffee.CursorCommands uses UIHelpers, so a change to UIHelpers can break Koffee.CursorCommands, while a change to Koffee.CursorCommands can't break UIHelpers.
- Position
- Below the diagonal: Koffee.CursorCommands uses a module listed above it, which is the healthy direction.
17→15 Koffee.CursorCommands uses Koffee✕
- Connections
- 4 pairs of types, where a type in Koffee.CursorCommands uses a type in Koffee.
- The types involved
Koffee.CursorCommands.CursorCommands→Koffee.MainModelKoffee.CursorCommands.CursorCommands→Koffee.ScrollTypeKoffee.CursorCommands.Handler→Koffee.CursorCommandKoffee.CursorCommands.Handler→Koffee.MainModel
- Direction
- Koffee.CursorCommands uses Koffee, so a change to Koffee can break Koffee.CursorCommands, while a change to Koffee.CursorCommands can't break Koffee.
- Position
- Below the diagonal: Koffee.CursorCommands uses a module listed above it, which is the healthy direction.
18→15 Koffee.DragDropEffects uses Koffee✕
- Connections
- 1 pair of types, where a type in Koffee.DragDropEffects uses a type in Koffee.
- The types involved
Koffee.DragDropEffects.DragDropEffects→Koffee.PutType
- Direction
- Koffee.DragDropEffects uses Koffee, so a change to Koffee can break Koffee.DragDropEffects, while a change to Koffee.DragDropEffects can't break Koffee.
- Position
- Below the diagonal: Koffee.DragDropEffects uses a module listed above it, which is the healthy direction.
19→12 Koffee.ItemActionCommands uses Koffee.MainStatus✕
- Connections
- 1 pair of types, where a type in Koffee.ItemActionCommands uses a type in Koffee.MainStatus.
- The types involved
Koffee.ItemActionCommands.Handler→Koffee.MainStatus.Error
- Direction
- Koffee.ItemActionCommands uses Koffee.MainStatus, so a change to Koffee.MainStatus can break Koffee.ItemActionCommands, while a change to Koffee.ItemActionCommands can't break Koffee.MainStatus.
- Position
- Below the diagonal: Koffee.ItemActionCommands uses a module listed above it, which is the healthy direction.
19→15 Koffee.ItemActionCommands uses Koffee✕
- Connections
- 10 pairs of types, where a type in Koffee.ItemActionCommands uses a type in Koffee.
- The types involved
Koffee.ItemActionCommands.Handler→Koffee.DragInEventKoffee.ItemActionCommands.Handler→Koffee.DragOutEventKoffee.ItemActionCommands.Handler→Koffee.IFileSystemKoffee.ItemActionCommands.Handler→Koffee.IOperatingSystemKoffee.ItemActionCommands.Handler→Koffee.InputEventKoffee.ItemActionCommands.Handler→Koffee.ItemKoffee.ItemActionCommands.Handler→Koffee.ItemActionCommandKoffee.ItemActionCommands.Handler→Koffee.MainModelKoffee.ItemActionCommands.Handler→Koffee.PathKoffee.ItemActionCommands.Handler→Koffee.Progress
- Direction
- Koffee.ItemActionCommands uses Koffee, so a change to Koffee can break Koffee.ItemActionCommands, while a change to Koffee.ItemActionCommands can't break Koffee.
- Position
- Below the diagonal: Koffee.ItemActionCommands uses a module listed above it, which is the healthy direction.
20→12 Koffee.ItemActionCommands.Attributes uses Koffee.MainStatus✕
- Connections
- 1 pair of types, where a type in Koffee.ItemActionCommands.Attributes uses a type in Koffee.MainStatus.
- The types involved
Koffee.ItemActionCommands.Attributes.Attributes→Koffee.MainStatus.Error
- Direction
- Koffee.ItemActionCommands.Attributes uses Koffee.MainStatus, so a change to Koffee.MainStatus can break Koffee.ItemActionCommands.Attributes, while a change to Koffee.ItemActionCommands.Attributes can't break Koffee.MainStatus.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Attributes uses a module listed above it, which is the healthy direction.
20→15 Koffee.ItemActionCommands.Attributes uses Koffee✕
- Connections
- 5 pairs of types, where a type in Koffee.ItemActionCommands.Attributes uses a type in Koffee.
- The types involved
Koffee.ItemActionCommands.Attributes.Attributes→Koffee.CancelTokenKoffee.ItemActionCommands.Attributes.Attributes→Koffee.IFileSystemKoffee.ItemActionCommands.Attributes.Attributes→Koffee.ItemKoffee.ItemActionCommands.Attributes.Attributes→Koffee.MainModelKoffee.ItemActionCommands.Attributes.Attributes→Koffee.Progress
- Direction
- Koffee.ItemActionCommands.Attributes uses Koffee, so a change to Koffee can break Koffee.ItemActionCommands.Attributes, while a change to Koffee.ItemActionCommands.Attributes can't break Koffee.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Attributes uses a module listed above it, which is the healthy direction.
21→12 Koffee.ItemActionCommands.Create uses Koffee.MainStatus✕
- Connections
- 1 pair of types, where a type in Koffee.ItemActionCommands.Create uses a type in Koffee.MainStatus.
- The types involved
Koffee.ItemActionCommands.Create.Create→Koffee.MainStatus.Error
- Direction
- Koffee.ItemActionCommands.Create uses Koffee.MainStatus, so a change to Koffee.MainStatus can break Koffee.ItemActionCommands.Create, while a change to Koffee.ItemActionCommands.Create can't break Koffee.MainStatus.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Create uses a module listed above it, which is the healthy direction.
21→15 Koffee.ItemActionCommands.Create uses Koffee✕
- Connections
- 6 pairs of types, where a type in Koffee.ItemActionCommands.Create uses a type in Koffee.
- The types involved
Koffee.ItemActionCommands.Create.Create→Koffee.IFileSystemKoffee.ItemActionCommands.Create.Create→Koffee.IFileSystemReaderKoffee.ItemActionCommands.Create.Create→Koffee.InputTypeKoffee.ItemActionCommands.Create.Create→Koffee.ItemKoffee.ItemActionCommands.Create.Create→Koffee.ItemTypeKoffee.ItemActionCommands.Create.Create→Koffee.MainModel
- Direction
- Koffee.ItemActionCommands.Create uses Koffee, so a change to Koffee can break Koffee.ItemActionCommands.Create, while a change to Koffee.ItemActionCommands.Create can't break Koffee.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Create uses a module listed above it, which is the healthy direction.
22→12 Koffee.ItemActionCommands.Delete uses Koffee.MainStatus✕
- Connections
- 1 pair of types, where a type in Koffee.ItemActionCommands.Delete uses a type in Koffee.MainStatus.
- The types involved
Koffee.ItemActionCommands.Delete.Delete→Koffee.MainStatus.Error
- Direction
- Koffee.ItemActionCommands.Delete uses Koffee.MainStatus, so a change to Koffee.MainStatus can break Koffee.ItemActionCommands.Delete, while a change to Koffee.ItemActionCommands.Delete can't break Koffee.MainStatus.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Delete uses a module listed above it, which is the healthy direction.
22→15 Koffee.ItemActionCommands.Delete uses Koffee✕
- Connections
- 6 pairs of types, where a type in Koffee.ItemActionCommands.Delete uses a type in Koffee.
- The types involved
Koffee.ItemActionCommands.Delete.Delete→Koffee.CancelTokenKoffee.ItemActionCommands.Delete.Delete→Koffee.IFileSystemKoffee.ItemActionCommands.Delete.Delete→Koffee.IFileSystemReaderKoffee.ItemActionCommands.Delete.Delete→Koffee.ItemKoffee.ItemActionCommands.Delete.Delete→Koffee.MainModelKoffee.ItemActionCommands.Delete.Delete→Koffee.Progress
- Direction
- Koffee.ItemActionCommands.Delete uses Koffee, so a change to Koffee can break Koffee.ItemActionCommands.Delete, while a change to Koffee.ItemActionCommands.Delete can't break Koffee.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Delete uses a module listed above it, which is the healthy direction.
23→12 Koffee.ItemActionCommands.Put uses Koffee.MainStatus✕
- Connections
- 1 pair of types, where a type in Koffee.ItemActionCommands.Put uses a type in Koffee.MainStatus.
- The types involved
Koffee.ItemActionCommands.Put.Put→Koffee.MainStatus.Error
- Direction
- Koffee.ItemActionCommands.Put uses Koffee.MainStatus, so a change to Koffee.MainStatus can break Koffee.ItemActionCommands.Put, while a change to Koffee.ItemActionCommands.Put can't break Koffee.MainStatus.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Put uses a module listed above it, which is the healthy direction.
23→15 Koffee.ItemActionCommands.Put uses Koffee✕
- Connections
- 15 pairs of types, where a type in Koffee.ItemActionCommands.Put uses a type in Koffee.
- The types involved
Koffee.ItemActionCommands.Put.Put→Koffee.CancelTokenKoffee.ItemActionCommands.Put.Put→Koffee.DragInEventKoffee.ItemActionCommands.Put.Put→Koffee.DragOutEventKoffee.ItemActionCommands.Put.Put→Koffee.IFileSystemKoffee.ItemActionCommands.Put.Put→Koffee.IFileSystemReaderKoffee.ItemActionCommands.Put.Put→Koffee.IOperatingSystemKoffee.ItemActionCommands.Put.Put→Koffee.ItemActionKoffee.ItemActionCommands.Put.Put→Koffee.ItemRefKoffee.ItemActionCommands.Put.Put→Koffee.ItemTypeKoffee.ItemActionCommands.Put.Put→Koffee.MainModelKoffee.ItemActionCommands.Put.Put→Koffee.PathKoffee.ItemActionCommands.Put.Put→Koffee.ProgressKoffee.ItemActionCommands.Put.Put→Koffee.PutIntentKoffee.ItemActionCommands.Put.Put→Koffee.PutItemKoffee.ItemActionCommands.Put.Put→Koffee.PutType
- Direction
- Koffee.ItemActionCommands.Put uses Koffee, so a change to Koffee can break Koffee.ItemActionCommands.Put, while a change to Koffee.ItemActionCommands.Put can't break Koffee.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Put uses a module listed above it, which is the healthy direction.
24→15 Koffee.ItemActionCommands.Put.MoveUtil uses Koffee✕
- Connections
- 4 pairs of types, where a type in Koffee.ItemActionCommands.Put.MoveUtil uses a type in Koffee.
- The types involved
Koffee.ItemActionCommands.Put.MoveUtil.MoveUtil→Koffee.IFileSystemKoffee.ItemActionCommands.Put.MoveUtil.MoveUtil→Koffee.PathKoffee.ItemActionCommands.Put.MoveUtil.MoveUtil→Koffee.PutIntentKoffee.ItemActionCommands.Put.MoveUtil.MoveUtil→Koffee.PutItem
- Direction
- Koffee.ItemActionCommands.Put.MoveUtil uses Koffee, so a change to Koffee can break Koffee.ItemActionCommands.Put.MoveUtil, while a change to Koffee.ItemActionCommands.Put.MoveUtil can't break Koffee.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Put.MoveUtil uses a module listed above it, which is the healthy direction.
25→12 Koffee.ItemActionCommands.Rename uses Koffee.MainStatus✕
- Connections
- 1 pair of types, where a type in Koffee.ItemActionCommands.Rename uses a type in Koffee.MainStatus.
- The types involved
Koffee.ItemActionCommands.Rename.Rename→Koffee.MainStatus.Error
- Direction
- Koffee.ItemActionCommands.Rename uses Koffee.MainStatus, so a change to Koffee.MainStatus can break Koffee.ItemActionCommands.Rename, while a change to Koffee.ItemActionCommands.Rename can't break Koffee.MainStatus.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Rename uses a module listed above it, which is the healthy direction.
25→15 Koffee.ItemActionCommands.Rename uses Koffee✕
- Connections
- 5 pairs of types, where a type in Koffee.ItemActionCommands.Rename uses a type in Koffee.
- The types involved
Koffee.ItemActionCommands.Rename.Rename→Koffee.IFileSystemKoffee.ItemActionCommands.Rename.Rename→Koffee.ItemKoffee.ItemActionCommands.Rename.Rename→Koffee.ItemTypeKoffee.ItemActionCommands.Rename.Rename→Koffee.MainModelKoffee.ItemActionCommands.Rename.Rename→Koffee.RenamePart
- Direction
- Koffee.ItemActionCommands.Rename uses Koffee, so a change to Koffee can break Koffee.ItemActionCommands.Rename, while a change to Koffee.ItemActionCommands.Rename can't break Koffee.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Rename uses a module listed above it, which is the healthy direction.
26→12 Koffee.ItemActionCommands.Tools uses Koffee.MainStatus✕
- Connections
- 1 pair of types, where a type in Koffee.ItemActionCommands.Tools uses a type in Koffee.MainStatus.
- The types involved
Koffee.ItemActionCommands.Tools.Tools→Koffee.MainStatus.Error
- Direction
- Koffee.ItemActionCommands.Tools uses Koffee.MainStatus, so a change to Koffee.MainStatus can break Koffee.ItemActionCommands.Tools, while a change to Koffee.ItemActionCommands.Tools can't break Koffee.MainStatus.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Tools uses a module listed above it, which is the healthy direction.
26→15 Koffee.ItemActionCommands.Tools uses Koffee✕
- Connections
- 6 pairs of types, where a type in Koffee.ItemActionCommands.Tools uses a type in Koffee.
- The types involved
Koffee.ItemActionCommands.Tools.Tools→Koffee.IFileSystemReaderKoffee.ItemActionCommands.Tools.Tools→Koffee.IOperatingSystemKoffee.ItemActionCommands.Tools.Tools→Koffee.MainModelKoffee.ItemActionCommands.Tools.Tools→Koffee.PathKoffee.ItemActionCommands.Tools.VariableApplication→Koffee.PathKoffee.ItemActionCommands.Tools.VariableMatch→Koffee.ToolVariable
- Direction
- Koffee.ItemActionCommands.Tools uses Koffee, so a change to Koffee can break Koffee.ItemActionCommands.Tools, while a change to Koffee.ItemActionCommands.Tools can't break Koffee.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Tools uses a module listed above it, which is the healthy direction.
27→12 Koffee.ItemActionCommands.Undo uses Koffee.MainStatus✕
- Connections
- 1 pair of types, where a type in Koffee.ItemActionCommands.Undo uses a type in Koffee.MainStatus.
- The types involved
Koffee.ItemActionCommands.Undo.Undo→Koffee.MainStatus.Error
- Direction
- Koffee.ItemActionCommands.Undo uses Koffee.MainStatus, so a change to Koffee.MainStatus can break Koffee.ItemActionCommands.Undo, while a change to Koffee.ItemActionCommands.Undo can't break Koffee.MainStatus.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Undo uses a module listed above it, which is the healthy direction.
27→15 Koffee.ItemActionCommands.Undo uses Koffee✕
- Connections
- 3 pairs of types, where a type in Koffee.ItemActionCommands.Undo uses a type in Koffee.
- The types involved
Koffee.ItemActionCommands.Undo.Undo→Koffee.IFileSystemKoffee.ItemActionCommands.Undo.Undo→Koffee.MainModelKoffee.ItemActionCommands.Undo.Undo→Koffee.Progress
- Direction
- Koffee.ItemActionCommands.Undo uses Koffee, so a change to Koffee can break Koffee.ItemActionCommands.Undo, while a change to Koffee.ItemActionCommands.Undo can't break Koffee.
- Position
- Below the diagonal: Koffee.ItemActionCommands.Undo uses a module listed above it, which is the healthy direction.
28→11 Koffee.KeyBinder uses Utility✕
- Connections
- 1 pair of types, where a type in Koffee.KeyBinder uses a type in Utility.
- The types involved
Koffee.KeyBinder.Events→Utility.KeyPressHandler
- Direction
- Koffee.KeyBinder uses Utility, so a change to Utility can break Koffee.KeyBinder, while a change to Koffee.KeyBinder can't break Utility.
- Position
- Below the diagonal: Koffee.KeyBinder uses a module listed above it, which is the healthy direction.
28→15 Koffee.KeyBinder uses Koffee✕
- Connections
- 5 pairs of types, where a type in Koffee.KeyBinder uses a type in Koffee.
- The types involved
Koffee.KeyBinder.Command→Koffee.MainCommandKoffee.KeyBinder.CommandBinding→Koffee.KeyBinding`1Koffee.KeyBinder.CommandBinding→Koffee.MainCommandKoffee.KeyBinder.Model→Koffee.KeyBinding`1Koffee.KeyBinder.Model→Koffee.MainCommand
- Direction
- Koffee.KeyBinder uses Koffee, so a change to Koffee can break Koffee.KeyBinder, while a change to Koffee.KeyBinder can't break Koffee.
- Position
- Below the diagonal: Koffee.KeyBinder uses a module listed above it, which is the healthy direction.
29→15 Koffee.KeyBinding uses Koffee✕
- Connections
- 2 pairs of types, where a type in Koffee.KeyBinding uses a type in Koffee.
- The types involved
Koffee.KeyBinding.KeyBinding→Koffee.KeyBindMatch`1Koffee.KeyBinding.KeyBinding→Koffee.KeyBinding`1
- Direction
- Koffee.KeyBinding uses Koffee, so a change to Koffee can break Koffee.KeyBinding, while a change to Koffee.KeyBinding can't break Koffee.
- Position
- Below the diagonal: Koffee.KeyBinding uses a module listed above it, which is the healthy direction.
30→15 Koffee.MainBindings uses Koffee✕
- Connections
- 2 pairs of types, where a type in Koffee.MainBindings uses a type in Koffee.
- The types involved
Koffee.MainBindings.MainBindings→Koffee.KeyBinding`1Koffee.MainBindings.MainBindings→Koffee.MainCommand
- Direction
- Koffee.MainBindings uses Koffee, so a change to Koffee can break Koffee.MainBindings, while a change to Koffee.MainBindings can't break Koffee.
- Position
- Below the diagonal: Koffee.MainBindings uses a module listed above it, which is the healthy direction.
31→15 Koffee.MainView uses Koffee✕
- Connections
- 6 pairs of types, where a type in Koffee.MainView uses a type in Koffee.
- The types involved
Koffee.MainView.MainView→Koffee.ConfigFileKoffee.MainView.MainView→Koffee.HistoryFileKoffee.MainView.MainView→Koffee.ItemKoffee.MainView.MainView→Koffee.MainEventKoffee.MainView.MainView→Koffee.MainModelKoffee.MainView.MainView→Koffee.Path
- Direction
- Koffee.MainView uses Koffee, so a change to Koffee can break Koffee.MainView, while a change to Koffee.MainView can't break Koffee.
- Position
- Below the diagonal: Koffee.MainView uses a module listed above it, which is the healthy direction.
32→11 Koffee.NavigationCommands uses Utility✕
- Connections
- 2 pairs of types, where a type in Koffee.NavigationCommands uses a type in Utility.
- The types involved
Koffee.NavigationCommands.Handler→Utility.KeyPressHandlerKoffee.NavigationCommands.NavigationCommands→Utility.KeyPressHandler
- Direction
- Koffee.NavigationCommands uses Utility, so a change to Utility can break Koffee.NavigationCommands, while a change to Koffee.NavigationCommands can't break Utility.
- Position
- Below the diagonal: Koffee.NavigationCommands uses a module listed above it, which is the healthy direction.
32→12 Koffee.NavigationCommands uses Koffee.MainStatus✕
- Connections
- 2 pairs of types, where a type in Koffee.NavigationCommands uses a type in Koffee.MainStatus.
- The types involved
Koffee.NavigationCommands.Handler→Koffee.MainStatus.ErrorKoffee.NavigationCommands.NavigationCommands→Koffee.MainStatus.Error
- Direction
- Koffee.NavigationCommands uses Koffee.MainStatus, so a change to Koffee.MainStatus can break Koffee.NavigationCommands, while a change to Koffee.NavigationCommands can't break Koffee.MainStatus.
- Position
- Below the diagonal: Koffee.NavigationCommands uses a module listed above it, which is the healthy direction.
32→15 Koffee.NavigationCommands uses Koffee✕
- Connections
- 23 pairs of types, where a type in Koffee.NavigationCommands uses a type in Koffee.
- The types involved
Koffee.NavigationCommands.Handler→Koffee.HistoryPathKoffee.NavigationCommands.Handler→Koffee.IFileSystemReaderKoffee.NavigationCommands.Handler→Koffee.IOperatingSystemKoffee.NavigationCommands.Handler→Koffee.InputEventKoffee.NavigationCommands.Handler→Koffee.ItemKoffee.NavigationCommands.Handler→Koffee.MainModelKoffee.NavigationCommands.Handler→Koffee.MarkCommandKoffee.NavigationCommands.Handler→Koffee.NavigationCommandKoffee.NavigationCommands.Handler→Koffee.ProgressKoffee.NavigationCommands.NavigationCommands→Koffee.CursorMoveTypeKoffee.NavigationCommands.NavigationCommands→Koffee.HistoryPathKoffee.NavigationCommands.NavigationCommands→Koffee.IFileSystemReaderKoffee.NavigationCommands.NavigationCommands→Koffee.IOperatingSystemKoffee.NavigationCommands.NavigationCommands→Koffee.InputErrorKoffee.NavigationCommands.NavigationCommands→Koffee.ItemKoffee.NavigationCommands.NavigationCommands→Koffee.MainModelKoffee.NavigationCommands.NavigationCommands→Koffee.MarkCommandKoffee.NavigationCommands.NavigationCommands→Koffee.MarkTypeKoffee.NavigationCommands.NavigationCommands→Koffee.PathKoffee.NavigationCommands.NavigationCommands→Koffee.PathFormatKoffee.NavigationCommands.NavigationCommands→Koffee.ProgressKoffee.NavigationCommands.NavigationCommands→Koffee.SearchKoffee.NavigationCommands.NavigationCommands→Koffee.SortField
- Direction
- Koffee.NavigationCommands uses Koffee, so a change to Koffee can break Koffee.NavigationCommands, while a change to Koffee.NavigationCommands can't break Koffee.
- Position
- Below the diagonal: Koffee.NavigationCommands uses a module listed above it, which is the healthy direction.
33→15 Koffee.OsUtility uses Koffee✕
- Connections
- 1 pair of types, where a type in Koffee.OsUtility uses a type in Koffee.
- The types involved
Koffee.OsUtility.OsUtility→Koffee.IOperatingSystem
- Direction
- Koffee.OsUtility uses Koffee, so a change to Koffee can break Koffee.OsUtility, while a change to Koffee.OsUtility can't break Koffee.
- Position
- Below the diagonal: Koffee.OsUtility uses a module listed above it, which is the healthy direction.
34→15 Koffee.ProgramOptions uses Koffee✕
- Connections
- 1 pair of types, where a type in Koffee.ProgramOptions uses a type in Koffee.
- The types involved
Koffee.ProgramOptions.ProgramOptions→Koffee.StartOptions
- Direction
- Koffee.ProgramOptions uses Koffee, so a change to Koffee can break Koffee.ProgramOptions, while a change to Koffee.ProgramOptions can't break Koffee.
- Position
- Below the diagonal: Koffee.ProgramOptions uses a module listed above it, which is the healthy direction.
35→15 Koffee.SortFieldModule uses Koffee✕
- Connections
- 2 pairs of types, where a type in Koffee.SortFieldModule uses a type in Koffee.
- The types involved
Koffee.SortFieldModule.SortFieldModule→Koffee.ItemKoffee.SortFieldModule.SortFieldModule→Koffee.SortField
- Direction
- Koffee.SortFieldModule uses Koffee, so a change to Koffee can break Koffee.SortFieldModule, while a change to Koffee.SortFieldModule can't break Koffee.
- Position
- Below the diagonal: Koffee.SortFieldModule uses a module listed above it, which is the healthy direction.
36→15 Koffee.ToolEdit uses Koffee✕
- Connections
- 3 pairs of types, where a type in Koffee.ToolEdit uses a type in Koffee.
- The types involved
Koffee.ToolEdit.Dialog→Koffee.ToolKoffee.ToolEdit.Model→Koffee.ToolKoffee.ToolEdit.ToolEdit→Koffee.Tool
- Direction
- Koffee.ToolEdit uses Koffee, so a change to Koffee can break Koffee.ToolEdit, while a change to Koffee.ToolEdit can't break Koffee.
- Position
- Below the diagonal: Koffee.ToolEdit uses a module listed above it, which is the healthy direction.
37→12 Koffee.WindowCommands uses Koffee.MainStatus✕
- Connections
- 1 pair of types, where a type in Koffee.WindowCommands uses a type in Koffee.MainStatus.
- The types involved
Koffee.WindowCommands.WindowCommands→Koffee.MainStatus.Error
- Direction
- Koffee.WindowCommands uses Koffee.MainStatus, so a change to Koffee.MainStatus can break Koffee.WindowCommands, while a change to Koffee.WindowCommands can't break Koffee.MainStatus.
- Position
- Below the diagonal: Koffee.WindowCommands uses a module listed above it, which is the healthy direction.
37→15 Koffee.WindowCommands uses Koffee✕
- Connections
- 7 pairs of types, where a type in Koffee.WindowCommands uses a type in Koffee.
- The types involved
Koffee.WindowCommands.Handler→Koffee.IFileSystemReaderKoffee.WindowCommands.Handler→Koffee.IOperatingSystemKoffee.WindowCommands.Handler→Koffee.MainModelKoffee.WindowCommands.Handler→Koffee.WindowCommandKoffee.WindowCommands.WindowCommands→Koffee.IFileSystemReaderKoffee.WindowCommands.WindowCommands→Koffee.IOperatingSystemKoffee.WindowCommands.WindowCommands→Koffee.MainModel
- Direction
- Koffee.WindowCommands uses Koffee, so a change to Koffee can break Koffee.WindowCommands, while a change to Koffee.WindowCommands can't break Koffee.
- Position
- Below the diagonal: Koffee.WindowCommands uses a module listed above it, which is the healthy direction.
38→15 Koffee.KeyBinder.KeyBinderBinding uses Koffee✕
- Connections
- 1 pair of types, where a type in Koffee.KeyBinder.KeyBinderBinding uses a type in Koffee.
- The types involved
Koffee.KeyBinder.KeyBinderBinding.KeyBinderBinding→Koffee.KeyBinding`1
- Direction
- Koffee.KeyBinder.KeyBinderBinding uses Koffee, so a change to Koffee can break Koffee.KeyBinder.KeyBinderBinding, while a change to Koffee.KeyBinder.KeyBinderBinding can't break Koffee.
- Position
- Below the diagonal: Koffee.KeyBinder.KeyBinderBinding uses a module listed above it, which is the healthy direction.
38→28 Koffee.KeyBinder.KeyBinderBinding uses Koffee.KeyBinder✕
- Connections
- 2 pairs of types, where a type in Koffee.KeyBinder.KeyBinderBinding uses a type in Koffee.KeyBinder.
- The types involved
Koffee.KeyBinder.KeyBinderBinding.KeyBinderBinding→Koffee.KeyBinder.CommandKoffee.KeyBinder.KeyBinderBinding.KeyBinderBinding→Koffee.KeyBinder.CommandBinding
- Direction
- Koffee.KeyBinder.KeyBinderBinding uses Koffee.KeyBinder, so a change to Koffee.KeyBinder can break Koffee.KeyBinder.KeyBinderBinding, while a change to Koffee.KeyBinder.KeyBinderBinding can't break Koffee.KeyBinder.
- Position
- Below the diagonal: Koffee.KeyBinder.KeyBinderBinding uses a module listed above it, which is the healthy direction.
39→11 Koffee.MainController uses Utility✕
- Connections
- 1 pair of types, where a type in Koffee.MainController uses a type in Utility.
- The types involved
Koffee.MainController.MainController→Utility.Rectangle
- Direction
- Koffee.MainController uses Utility, so a change to Utility can break Koffee.MainController, while a change to Koffee.MainController can't break Utility.
- Position
- Below the diagonal: Koffee.MainController uses a module listed above it, which is the healthy direction.
39→15 Koffee.MainController uses Koffee✕
- Connections
- 10 pairs of types, where a type in Koffee.MainController uses a type in Koffee.
- The types involved
Koffee.MainController.Controller→Koffee.ConfigFileKoffee.MainController.Controller→Koffee.HistoryFileKoffee.MainController.Controller→Koffee.IFileSystemKoffee.MainController.Controller→Koffee.ItemKoffee.MainController.Controller→Koffee.MainModelKoffee.MainController.Controller→Koffee.ProgressKoffee.MainController.Controller→Koffee.StartOptionsKoffee.MainController.MainController→Koffee.IFileSystemReaderKoffee.MainController.MainController→Koffee.MainModelKoffee.MainController.MainController→Koffee.StartOptions
- Direction
- Koffee.MainController uses Koffee, so a change to Koffee can break Koffee.MainController, while a change to Koffee.MainController can't break Koffee.
- Position
- Below the diagonal: Koffee.MainController uses a module listed above it, which is the healthy direction.
39→17 Koffee.MainController uses Koffee.CursorCommands✕
- Connections
- 1 pair of types, where a type in Koffee.MainController uses a type in Koffee.CursorCommands.
- The types involved
Koffee.MainController.Controller→Koffee.CursorCommands.Handler
- Direction
- Koffee.MainController uses Koffee.CursorCommands, so a change to Koffee.CursorCommands can break Koffee.MainController, while a change to Koffee.MainController can't break Koffee.CursorCommands.
- Position
- Below the diagonal: Koffee.MainController uses a module listed above it, which is the healthy direction.
39→19 Koffee.MainController uses Koffee.ItemActionCommands✕
- Connections
- 1 pair of types, where a type in Koffee.MainController uses a type in Koffee.ItemActionCommands.
- The types involved
Koffee.MainController.Controller→Koffee.ItemActionCommands.Handler
- Direction
- Koffee.MainController uses Koffee.ItemActionCommands, so a change to Koffee.ItemActionCommands can break Koffee.MainController, while a change to Koffee.MainController can't break Koffee.ItemActionCommands.
- Position
- Below the diagonal: Koffee.MainController uses a module listed above it, which is the healthy direction.
39→32 Koffee.MainController uses Koffee.NavigationCommands✕
- Connections
- 1 pair of types, where a type in Koffee.MainController uses a type in Koffee.NavigationCommands.
- The types involved
Koffee.MainController.Controller→Koffee.NavigationCommands.Handler
- Direction
- Koffee.MainController uses Koffee.NavigationCommands, so a change to Koffee.NavigationCommands can break Koffee.MainController, while a change to Koffee.MainController can't break Koffee.NavigationCommands.
- Position
- Below the diagonal: Koffee.MainController uses a module listed above it, which is the healthy direction.
39→37 Koffee.MainController uses Koffee.WindowCommands✕
- Connections
- 1 pair of types, where a type in Koffee.MainController uses a type in Koffee.WindowCommands.
- The types involved
Koffee.MainController.Controller→Koffee.WindowCommands.Handler
- Direction
- Koffee.MainController uses Koffee.WindowCommands, so a change to Koffee.WindowCommands can break Koffee.MainController, while a change to Koffee.MainController can't break Koffee.WindowCommands.
- Position
- Below the diagonal: Koffee.MainController uses a module listed above it, which is the healthy direction.
40→10 Koffee.Settings uses Koffee.TextEdit✕
- Connections
- 1 pair of types, where a type in Koffee.Settings uses a type in Koffee.TextEdit.
- The types involved
Koffee.Settings.Settings→Koffee.TextEdit.Dialog
- Direction
- Koffee.Settings uses Koffee.TextEdit, so a change to Koffee.TextEdit can break Koffee.Settings, while a change to Koffee.Settings can't break Koffee.TextEdit.
- Position
- Below the diagonal: Koffee.Settings uses a module listed above it, which is the healthy direction.
40→11 Koffee.Settings uses Utility✕
- Connections
- 1 pair of types, where a type in Koffee.Settings uses a type in Utility.
- The types involved
Koffee.Settings.Events→Utility.KeyPressHandler
- Direction
- Koffee.Settings uses Utility, so a change to Utility can break Koffee.Settings, while a change to Koffee.Settings can't break Utility.
- Position
- Below the diagonal: Koffee.Settings uses a module listed above it, which is the healthy direction.
40→15 Koffee.Settings uses Koffee✕
- Connections
- 11 pairs of types, where a type in Koffee.Settings uses a type in Koffee.
- The types involved
Koffee.Settings.Events→Koffee.PathFormatKoffee.Settings.Events→Koffee.StartPathKoffee.Settings.Model→Koffee.ConfigKoffee.Settings.Model→Koffee.KeyBinding`1Koffee.Settings.Model→Koffee.MainCommandKoffee.Settings.Model→Koffee.PathKoffee.Settings.Model→Koffee.ToolKoffee.Settings.Settings→Koffee.ConfigKoffee.Settings.Settings→Koffee.KeyBinding`1Koffee.Settings.Settings→Koffee.MainCommandKoffee.Settings.Settings→Koffee.Tool
- Direction
- Koffee.Settings uses Koffee, so a change to Koffee can break Koffee.Settings, while a change to Koffee.Settings can't break Koffee.
- Position
- Below the diagonal: Koffee.Settings uses a module listed above it, which is the healthy direction.
40→28 Koffee.Settings uses Koffee.KeyBinder✕
- Connections
- 3 pairs of types, where a type in Koffee.Settings uses a type in Koffee.KeyBinder.
- The types involved
Koffee.Settings.Model→Koffee.KeyBinder.CommandBindingKoffee.Settings.Settings→Koffee.KeyBinder.CommandBindingKoffee.Settings.Settings→Koffee.KeyBinder.Dialog
- Direction
- Koffee.Settings uses Koffee.KeyBinder, so a change to Koffee.KeyBinder can break Koffee.Settings, while a change to Koffee.Settings can't break Koffee.KeyBinder.
- Position
- Below the diagonal: Koffee.Settings uses a module listed above it, which is the healthy direction.
40→36 Koffee.Settings uses Koffee.ToolEdit✕
- Connections
- 1 pair of types, where a type in Koffee.Settings uses a type in Koffee.ToolEdit.
- The types involved
Koffee.Settings.Settings→Koffee.ToolEdit.Dialog
- Direction
- Koffee.Settings uses Koffee.ToolEdit, so a change to Koffee.ToolEdit can break Koffee.Settings, while a change to Koffee.Settings can't break Koffee.ToolEdit.
- Position
- Below the diagonal: Koffee.Settings uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Add a CI workflow that builds and runs the test suite on every push/PR; Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +9.5 pts | Low | ADR Quality |
| Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with Koffee.fsproj, Koffee.Tests.fsproj. | +4.2 pts | Low | Dependency Hygiene |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +7.7 pts | Medium | CI/CD gates |
| Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run. | +7.7 pts | Medium | Observability |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.6 pts | Medium | Architecture documentation |
| Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with MainView.fs. | +1.7 pts | Medium | Churn × Complexity Hotspots |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.0 pts | Medium | Documentation (README) |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +0.8 pts | Low | Project Cohesion |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/Koffee/MainModel.fs | 7.0 | Near-clean | Cyclomatic Complexity: Error.Message (cyclomatic 43) |
| src/Koffee/ItemPutCommands.fs | 7.1 | Near-clean | Cyclomatic Complexity: Put.performPut (cyclomatic 22) |
| REDACTED | 7.2 | Near-clean | Dependency Vulnerabilities: High CVE: REDACTED |
| src/Koffee/MainView.fs | 7.4 | Near-clean | Cyclomatic Complexity: MainView.binder (cyclomatic 78) |
| src/Koffee/ItemActionCommands.fs | 7.4 | Near-clean | Cyclomatic Complexity: Attributes.setHidden (cyclomatic 17) |
| src/Koffee/FileSystem.fs | 7.8 | Near-clean | Cognitive Complexity: FileSystem.GetItem (cognitive 21) |
| src/Koffee/KeyBinding.fs | 8.5 | Near-clean | Cyclomatic Complexity: KeyChordModule.displayString (cyclomatic 44) |
| src/Koffee/MainController.fs | 8.5 | Near-clean | Cognitive Complexity: MainController.escape (cognitive 21) |
| src/Koffee/Path.fs | 8.5 | Near-clean | Cognitive Complexity: Path.Format (cognitive 16) |
| src/Koffee/NavigationCommands.fs | 8.5 | Near-clean | God Classes: FileTooLong: Koffee/NavigationCommands.fs |
| src/Koffee/Koffee.fsproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: System.Reactive |
| src/Koffee.Tests/Koffee.Tests.fsproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: FsUnit |
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. 61 of 61 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 — 61 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, 35 of 60 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
- D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D11 Test Reliability — not measured this run — 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. Test reliability not scored — the test tier(s) ran but surfaced none of this repository's 546 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
- D15 Churn × Complexity Hotspots — 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. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/Koffee/MainView.fs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- 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 (5 contributor(s) across 887 commit(s) sampled, automation and bot accounts excluded). One of them holds 89% of the history; the other 4 hold 2.8% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/Koffee/Koffee.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — 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. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (6,560 lines, 98% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — 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 — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: a native UI project (src/KoffeeUI/AppStyles.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- ED5 Idempotency — 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 classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
- 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.
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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: 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.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
10 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MainView.binder at 78. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Handler.Handle at 23 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Koffee/NavigationCommands.fs (Handler.Handle at 23). 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 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with MainView.binder (cyclomatic 78). — Refactoring it lifts Cyclomatic Complexity from 7.5 to about 7.7/10.
- Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
14 method(s) exceeded the cognitive complexity threshold of 15; the worst was MainView.binder at 86.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with MainView.binder (cognitive 86). — Refactoring it lifts Cognitive Complexity from 6.9 to about 7.3/10.
- Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with MainModel.fs, NavigationCommands.fs. — One of this dimension's main actionable groups (2 warning-level).
- Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
0 duplicated block group(s) detected.
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 3 classes have LCOM4 above 3.
D12 · Dependency Hygiene
18 outdated, 0 vulnerable, 0 deprecated packages.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 170 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 20 direct `PackageReference`(s), and 150 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
Top hotspots: src/Koffee/MainView.fs (2×78=156)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with MainView.fs. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
0 deducted debt markers + unmeasured dead symbols across 135 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (98% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 2 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
1 of 1 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
89 % of calls cross a namespace and 0 % go through an interface, but 45 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 22 of the 38 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.
D39 · IL Efficiency
0 of 60 first-party methods have an oversized IL body.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — src/KoffeeUI/BoolToIntParamConverter.cs:30, src/KoffeeUI/IsCustomRowSelectionConverter.cs:22, src/KoffeeUI/UnwrappedTextBlockWidthConverter.cs:30
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 1 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
- No logging call was found in the 29 F# production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (F#: Microsoft.Extensions.Logging (ILogger), Serilog, NLog, log4net, Logary) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run.
- Consider OpenTelemetry tracing/metrics (OpenTelemetry.Extensions.Hosting with the ASP.NET Core instrumentation) and a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) for operability.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `src/Koffee.Tests/Koffee.Tests.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/Koffee.Tests/Koffee.Tests.fsproj:46
What to do
- Run 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) — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 96% | Exemplary | Solid. |
| Architecture | 92% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 58% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 29% | Weak — gated by P1, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 98% | Exemplary | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 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.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 55 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~7866 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.
- D11 Test Reliability — Test runner surfaced no tests
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (6,873 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only; comments in this repository's .fs source were not judged.
- 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.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- D9 Test Distribution — Test source is present (.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): 26 value object(s); 6 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 only 1 of the 3 signals this lens looks for (1 event handler(s))
- ED5 Idempotency — not scored — 2 of 2 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X2 Cancellation propagation — no async method does work a token could cancel
- X5 Nullable reference types — no NRT-eligible projects
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 1 finding(s)
- REDACTED
Serious — 33 finding(s)
- Unfinished stub — throws NotImplementedException src/KoffeeUI/BoolToIntParamConverter.cs:30
- Unfinished stub — throws NotImplementedException src/KoffeeUI/IsCustomRowSelectionConverter.cs:22
- Unfinished stub — throws NotImplementedException src/KoffeeUI/UnwrappedTextBlockWidthConverter.cs:30
- FileTooLong: Koffee/MainModel.fs src/Koffee/MainModel.fs
- FileTooLong: Koffee/NavigationCommands.fs src/Koffee/NavigationCommands.fs
- MainView.binder (cyclomatic 78) src/Koffee/MainView.fs:59
- KeyChordModule.displayString (cyclomatic 44) src/Koffee/KeyBinding.fs:33
- Error.Message (cyclomatic 43) src/Koffee/MainModel.fs:854
- Message.Message (cyclomatic 42) src/Koffee/MainModel.fs:689
- Put.performPut (cyclomatic 22) src/Koffee/ItemPutCommands.fs:178
- InputMode.GetPrompt (cyclomatic 20) src/Koffee/MainModel.fs:397
- Attributes.setHidden (cyclomatic 17) src/Koffee/ItemActionCommands.fs:25
- Put.enumeratePutItems (cyclomatic 17) src/Koffee/ItemPutCommands.fs:41
- Busy.Message (cyclomatic 17) src/Koffee/MainModel.fs:780
- MainView.events (cyclomatic 16) src/Koffee/MainView.fs:460
- Hotspot: src/Koffee/MainView.fs src/Koffee/MainView.fs:59
- MainView.binder (cognitive 86) src/Koffee/MainView.fs:59
- InputMode.GetPrompt (cognitive 38) src/Koffee/MainModel.fs:397
- Put.performPut (cognitive 36) src/Koffee/ItemPutCommands.fs:178
- Message.Message (cognitive 35) src/Koffee/MainModel.fs:689
- Put.enumeratePutItems (cognitive 30) src/Koffee/ItemPutCommands.fs:41
- Attributes.setHidden (cognitive 28) src/Koffee/ItemActionCommands.fs:25
- Put.putToDestination (cognitive 28) src/Koffee/ItemPutCommands.fs:290
- Busy.Message (cognitive 24) src/Koffee/MainModel.fs:780
- MainController.escape (cognitive 21) src/Koffee/MainController.fs:60
- FileSystem.GetItem (cognitive 21) src/Koffee/FileSystem.fs:128
- Error.Message (cognitive 20) src/Koffee/MainModel.fs:854
- Undo.redoIter (cognitive 19) src/Koffee/ItemActionCommands.fs:141
- FileSystem.GetItems (cognitive 19) src/Koffee/FileSystem.fs:147
- Path.Format (cognitive 16) src/Koffee/Path.fs:93
- No CI pipeline
- No structured logging
- NuGet dependencies are not locked
Minor — 10 finding(s)
- Outdated: System.Reactive src/Koffee/Koffee.fsproj:51
- Outdated: FsUnit src/Koffee.Tests/Koffee.Tests.fsproj:46
- No ADRs found
- Projects may be oversized for their cohesion
- Scattered collaborators
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation src/Koffee.Tests/Koffee.Tests.fsproj:46
- Duplicated predicate src/Koffee/ItemActionCommands.fs:36
Minor — 16 finding(s)
- Outdated: FSharp.Core
- Outdated: Newtonsoft.Json
- Outdated: System.Management
- Outdated: CompareNETObjects
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: NUnit3TestAdapter
- Outdated: PixiEditor.ColorPicker
- Outdated: Fake.API.GitHub
- Outdated: Fake.Core.ReleaseNotes
- Outdated: Fake.Core.Target
- Outdated: Fake.DotNet.AssemblyInfoFile
- Outdated: Fake.DotNet.Cli
- Outdated: Fake.IO.FileSystem
- Outdated: Fake.IO.Zip
- Outdated: MSBuild.StructuredLogger
- Outdated: NuGet.Protocol
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-bc27bad7057b4ae0a5724211b72ae567/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-bc27bad7057b4ae0a5724211b72ae567/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Koffee.sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |