Executive summary
jesseduffield/lazydocker is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because 40 files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 60 out of 100, which the At risk rating leaves unchanged.
Maturity, at 53, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points. Having someone learn and document the 40 files no active contributor knows comes next, worth about 7 points. Raising Maturity to 70 would lift the score to about 65.
Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four known security holes in the packages the code depends on can be used by attackers, and two secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. The two unsafe settings in infrastructure or container files need changing to safe values. The password or key in the code's history needs replacing, with the old one switched off.
The product code is 9,680 lines, about €14,000 to rebuild.
If Maturity rose from 53 to 70, the lowest score rated Strong, the score would rise from 60 to about 65.
New since the last survey: 16 findings
- Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (25 corresponding lines) pkg/gui/view_helpers.go
- Code Duplication · Edited copy of a member (26 corresponding lines) pkg/gui/tasks_adapter.go
- Code Duplication · Edited copy of a member (16 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (16 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (21 corresponding lines) pkg/commands/network.go
- Code Duplication · Edited copy of a member (13 corresponding lines) REDACTED
- Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (14 corresponding lines) pkg/gui/gocui.go
- Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (14 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (11 corresponding lines) pkg/gui/view_helpers.go
- Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (13 corresponding lines) REDACTED
- Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (8 corresponding lines) pkg/gui/gui.go
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,600 to €23,000, for 77 to 245 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 60. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 9,680 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 com/jesseduffield/lazydocker | 2 com/jesseduffield/lazydocker/pkg/commands/ssh | 3 com/jesseduffield/lazydocker/pkg/config | 4 com/jesseduffield/lazydocker/pkg/gui/types | 5 com/jesseduffield/lazydocker/pkg/i18n | 6 com/jesseduffield/lazydocker/pkg/utils | 7 com/jesseduffield/lazydocker/scripts/cheatsheet | 8 com/jesseduffield/lazydocker/scripts/translations | 9 com/jesseduffield/lazydocker/pkg/commands | 10 com/jesseduffield/lazydocker/pkg/log | 11 com/jesseduffield/lazydocker/pkg/tasks | 12 com/jesseduffield/lazydocker/pkg/gui/panels | 13 com/jesseduffield/lazydocker/pkg/gui/presentation | 14 com/jesseduffield/lazydocker/pkg/gui | 15 com/jesseduffield/lazydocker/pkg/app | 16 com/jesseduffield/lazydocker/pkg/cheatsheet |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com/jesseduffield/lazydocker | ||||||||||||||||
| 2 com/jesseduffield/lazydocker/pkg/commands/ssh | ||||||||||||||||
| 3 com/jesseduffield/lazydocker/pkg/config | ||||||||||||||||
| 4 com/jesseduffield/lazydocker/pkg/gui/types | ||||||||||||||||
| 5 com/jesseduffield/lazydocker/pkg/i18n | ||||||||||||||||
| 6 com/jesseduffield/lazydocker/pkg/utils | ||||||||||||||||
| 7 com/jesseduffield/lazydocker/scripts/cheatsheet | ||||||||||||||||
| 8 com/jesseduffield/lazydocker/scripts/translations | ||||||||||||||||
| 9 com/jesseduffield/lazydocker/pkg/commands | 1 | 3 | 3 | |||||||||||||
| 10 com/jesseduffield/lazydocker/pkg/log | 1 | |||||||||||||||
| 11 com/jesseduffield/lazydocker/pkg/tasks | 2 | |||||||||||||||
| 12 com/jesseduffield/lazydocker/pkg/gui/panels | 1 | |||||||||||||||
| 13 com/jesseduffield/lazydocker/pkg/gui/presentation | 3 | 1 | 6 | |||||||||||||
| 14 com/jesseduffield/lazydocker/pkg/gui | 3 | 3 | 2 | 20 | 2 | 5 | ||||||||||
| 15 com/jesseduffield/lazydocker/pkg/app | 2 | 1 | 2 | 1 | ||||||||||||
| 16 com/jesseduffield/lazydocker/pkg/cheatsheet | 2 | 1 |
9→2 com/jesseduffield/lazydocker/pkg/commands uses com/jesseduffield/lazydocker/pkg/commands/ssh✕
- Connections
- 1 pair of types, where a type in com/jesseduffield/lazydocker/pkg/commands uses a type in com/jesseduffield/lazydocker/pkg/commands/ssh.
- The types involved
github.com/jesseduffield/lazydocker/pkg/commands.OSCommand→github.com/jesseduffield/lazydocker/pkg/commands/ssh.CmdKiller
- Direction
- com/jesseduffield/lazydocker/pkg/commands uses com/jesseduffield/lazydocker/pkg/commands/ssh, so a change to com/jesseduffield/lazydocker/pkg/commands/ssh can break com/jesseduffield/lazydocker/pkg/commands, while a change to com/jesseduffield/lazydocker/pkg/commands can't break com/jesseduffield/lazydocker/pkg/commands/ssh.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/commands uses a module listed above it, which is the healthy direction.
9→3 com/jesseduffield/lazydocker/pkg/commands uses com/jesseduffield/lazydocker/pkg/config✕
- Connections
- 3 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/commands uses a type in com/jesseduffield/lazydocker/pkg/config.
- The types involved
github.com/jesseduffield/lazydocker/pkg/commands.DockerCommand→github.com/jesseduffield/lazydocker/pkg/config.AppConfiggithub.com/jesseduffield/lazydocker/pkg/commands.OSCommand→github.com/jesseduffield/lazydocker/pkg/config.AppConfiggithub.com/jesseduffield/lazydocker/pkg/commands.commands→github.com/jesseduffield/lazydocker/pkg/config.AppConfig
- Direction
- com/jesseduffield/lazydocker/pkg/commands uses com/jesseduffield/lazydocker/pkg/config, so a change to com/jesseduffield/lazydocker/pkg/config can break com/jesseduffield/lazydocker/pkg/commands, while a change to com/jesseduffield/lazydocker/pkg/commands can't break com/jesseduffield/lazydocker/pkg/config.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/commands uses a module listed above it, which is the healthy direction.
9→5 com/jesseduffield/lazydocker/pkg/commands uses com/jesseduffield/lazydocker/pkg/i18n✕
- Connections
- 3 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/commands uses a type in com/jesseduffield/lazydocker/pkg/i18n.
- The types involved
github.com/jesseduffield/lazydocker/pkg/commands.Container→github.com/jesseduffield/lazydocker/pkg/i18n.TranslationSetgithub.com/jesseduffield/lazydocker/pkg/commands.DockerCommand→github.com/jesseduffield/lazydocker/pkg/i18n.TranslationSetgithub.com/jesseduffield/lazydocker/pkg/commands.commands→github.com/jesseduffield/lazydocker/pkg/i18n.TranslationSet
- Direction
- com/jesseduffield/lazydocker/pkg/commands uses com/jesseduffield/lazydocker/pkg/i18n, so a change to com/jesseduffield/lazydocker/pkg/i18n can break com/jesseduffield/lazydocker/pkg/commands, while a change to com/jesseduffield/lazydocker/pkg/commands can't break com/jesseduffield/lazydocker/pkg/i18n.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/commands uses a module listed above it, which is the healthy direction.
10→3 com/jesseduffield/lazydocker/pkg/log uses com/jesseduffield/lazydocker/pkg/config✕
- Connections
- 1 pair of types, where a type in com/jesseduffield/lazydocker/pkg/log uses a type in com/jesseduffield/lazydocker/pkg/config.
- The types involved
github.com/jesseduffield/lazydocker/pkg/log.log→github.com/jesseduffield/lazydocker/pkg/config.AppConfig
- Direction
- com/jesseduffield/lazydocker/pkg/log uses com/jesseduffield/lazydocker/pkg/config, so a change to com/jesseduffield/lazydocker/pkg/config can break com/jesseduffield/lazydocker/pkg/log, while a change to com/jesseduffield/lazydocker/pkg/log can't break com/jesseduffield/lazydocker/pkg/config.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/log uses a module listed above it, which is the healthy direction.
11→5 com/jesseduffield/lazydocker/pkg/tasks uses com/jesseduffield/lazydocker/pkg/i18n✕
- Connections
- 2 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/tasks uses a type in com/jesseduffield/lazydocker/pkg/i18n.
- The types involved
github.com/jesseduffield/lazydocker/pkg/tasks.TaskManager→github.com/jesseduffield/lazydocker/pkg/i18n.TranslationSetgithub.com/jesseduffield/lazydocker/pkg/tasks.tasks→github.com/jesseduffield/lazydocker/pkg/i18n.TranslationSet
- Direction
- com/jesseduffield/lazydocker/pkg/tasks uses com/jesseduffield/lazydocker/pkg/i18n, so a change to com/jesseduffield/lazydocker/pkg/i18n can break com/jesseduffield/lazydocker/pkg/tasks, while a change to com/jesseduffield/lazydocker/pkg/tasks can't break com/jesseduffield/lazydocker/pkg/i18n.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/tasks uses a module listed above it, which is the healthy direction.
12→11 com/jesseduffield/lazydocker/pkg/gui/panels uses com/jesseduffield/lazydocker/pkg/tasks✕
- Connections
- 1 pair of types, where a type in com/jesseduffield/lazydocker/pkg/gui/panels uses a type in com/jesseduffield/lazydocker/pkg/tasks.
- The types involved
github.com/jesseduffield/lazydocker/pkg/gui/panels.IGui→github.com/jesseduffield/lazydocker/pkg/tasks.TaskFunc
- Direction
- com/jesseduffield/lazydocker/pkg/gui/panels uses com/jesseduffield/lazydocker/pkg/tasks, so a change to com/jesseduffield/lazydocker/pkg/tasks can break com/jesseduffield/lazydocker/pkg/gui/panels, while a change to com/jesseduffield/lazydocker/pkg/gui/panels can't break com/jesseduffield/lazydocker/pkg/tasks.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/gui/panels uses a module listed above it, which is the healthy direction.
13→3 com/jesseduffield/lazydocker/pkg/gui/presentation uses com/jesseduffield/lazydocker/pkg/config✕
- Connections
- 3 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/gui/presentation uses a type in com/jesseduffield/lazydocker/pkg/config.
- The types involved
github.com/jesseduffield/lazydocker/pkg/gui/presentation.presentation→github.com/jesseduffield/lazydocker/pkg/config.GraphConfiggithub.com/jesseduffield/lazydocker/pkg/gui/presentation.presentation→github.com/jesseduffield/lazydocker/pkg/config.GuiConfiggithub.com/jesseduffield/lazydocker/pkg/gui/presentation.presentation→github.com/jesseduffield/lazydocker/pkg/config.UserConfig
- Direction
- com/jesseduffield/lazydocker/pkg/gui/presentation uses com/jesseduffield/lazydocker/pkg/config, so a change to com/jesseduffield/lazydocker/pkg/config can break com/jesseduffield/lazydocker/pkg/gui/presentation, while a change to com/jesseduffield/lazydocker/pkg/gui/presentation can't break com/jesseduffield/lazydocker/pkg/config.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/gui/presentation uses a module listed above it, which is the healthy direction.
13→4 com/jesseduffield/lazydocker/pkg/gui/presentation uses com/jesseduffield/lazydocker/pkg/gui/types✕
- Connections
- 1 pair of types, where a type in com/jesseduffield/lazydocker/pkg/gui/presentation uses a type in com/jesseduffield/lazydocker/pkg/gui/types.
- The types involved
github.com/jesseduffield/lazydocker/pkg/gui/presentation.presentation→github.com/jesseduffield/lazydocker/pkg/gui/types.MenuItem
- Direction
- com/jesseduffield/lazydocker/pkg/gui/presentation uses com/jesseduffield/lazydocker/pkg/gui/types, so a change to com/jesseduffield/lazydocker/pkg/gui/types can break com/jesseduffield/lazydocker/pkg/gui/presentation, while a change to com/jesseduffield/lazydocker/pkg/gui/presentation can't break com/jesseduffield/lazydocker/pkg/gui/types.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/gui/presentation uses a module listed above it, which is the healthy direction.
13→9 com/jesseduffield/lazydocker/pkg/gui/presentation uses com/jesseduffield/lazydocker/pkg/commands✕
- Connections
- 6 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/gui/presentation uses a type in com/jesseduffield/lazydocker/pkg/commands.
- The types involved
github.com/jesseduffield/lazydocker/pkg/gui/presentation.presentation→github.com/jesseduffield/lazydocker/pkg/commands.Containergithub.com/jesseduffield/lazydocker/pkg/gui/presentation.presentation→github.com/jesseduffield/lazydocker/pkg/commands.Imagegithub.com/jesseduffield/lazydocker/pkg/gui/presentation.presentation→github.com/jesseduffield/lazydocker/pkg/commands.Networkgithub.com/jesseduffield/lazydocker/pkg/gui/presentation.presentation→github.com/jesseduffield/lazydocker/pkg/commands.Projectgithub.com/jesseduffield/lazydocker/pkg/gui/presentation.presentation→github.com/jesseduffield/lazydocker/pkg/commands.Servicegithub.com/jesseduffield/lazydocker/pkg/gui/presentation.presentation→github.com/jesseduffield/lazydocker/pkg/commands.Volume
- Direction
- com/jesseduffield/lazydocker/pkg/gui/presentation uses com/jesseduffield/lazydocker/pkg/commands, so a change to com/jesseduffield/lazydocker/pkg/commands can break com/jesseduffield/lazydocker/pkg/gui/presentation, while a change to com/jesseduffield/lazydocker/pkg/gui/presentation can't break com/jesseduffield/lazydocker/pkg/commands.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/gui/presentation uses a module listed above it, which is the healthy direction.
14→3 com/jesseduffield/lazydocker/pkg/gui uses com/jesseduffield/lazydocker/pkg/config✕
- Connections
- 3 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/gui uses a type in com/jesseduffield/lazydocker/pkg/config.
- The types involved
github.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/config.AppConfiggithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/config.CustomCommandgithub.com/jesseduffield/lazydocker/pkg/gui.gui→github.com/jesseduffield/lazydocker/pkg/config.AppConfig
- Direction
- com/jesseduffield/lazydocker/pkg/gui uses com/jesseduffield/lazydocker/pkg/config, so a change to com/jesseduffield/lazydocker/pkg/config can break com/jesseduffield/lazydocker/pkg/gui, while a change to com/jesseduffield/lazydocker/pkg/gui can't break com/jesseduffield/lazydocker/pkg/config.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/gui uses a module listed above it, which is the healthy direction.
14→4 com/jesseduffield/lazydocker/pkg/gui uses com/jesseduffield/lazydocker/pkg/gui/types✕
- Connections
- 3 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/gui uses a type in com/jesseduffield/lazydocker/pkg/gui/types.
- The types involved
github.com/jesseduffield/lazydocker/pkg/gui.CreateMenuOptions→github.com/jesseduffield/lazydocker/pkg/gui/types.MenuItemgithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/gui/types.MenuItemgithub.com/jesseduffield/lazydocker/pkg/gui.Panels→github.com/jesseduffield/lazydocker/pkg/gui/types.MenuItem
- Direction
- com/jesseduffield/lazydocker/pkg/gui uses com/jesseduffield/lazydocker/pkg/gui/types, so a change to com/jesseduffield/lazydocker/pkg/gui/types can break com/jesseduffield/lazydocker/pkg/gui, while a change to com/jesseduffield/lazydocker/pkg/gui can't break com/jesseduffield/lazydocker/pkg/gui/types.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/gui uses a module listed above it, which is the healthy direction.
14→5 com/jesseduffield/lazydocker/pkg/gui uses com/jesseduffield/lazydocker/pkg/i18n✕
- Connections
- 2 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/gui uses a type in com/jesseduffield/lazydocker/pkg/i18n.
- The types involved
github.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/i18n.TranslationSetgithub.com/jesseduffield/lazydocker/pkg/gui.gui→github.com/jesseduffield/lazydocker/pkg/i18n.TranslationSet
- Direction
- com/jesseduffield/lazydocker/pkg/gui uses com/jesseduffield/lazydocker/pkg/i18n, so a change to com/jesseduffield/lazydocker/pkg/i18n can break com/jesseduffield/lazydocker/pkg/gui, while a change to com/jesseduffield/lazydocker/pkg/gui can't break com/jesseduffield/lazydocker/pkg/i18n.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/gui uses a module listed above it, which is the healthy direction.
14→9 com/jesseduffield/lazydocker/pkg/gui uses com/jesseduffield/lazydocker/pkg/commands✕
- Connections
- 20 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/gui uses a type in com/jesseduffield/lazydocker/pkg/commands.
- The types involved
github.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/commands.CommandObjectgithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/commands.Containergithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/commands.DockerCommandgithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/commands.Imagegithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/commands.Networkgithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/commands.OSCommandgithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/commands.Projectgithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/commands.Servicegithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/commands.Volumegithub.com/jesseduffield/lazydocker/pkg/gui.Panels→github.com/jesseduffield/lazydocker/pkg/commands.Containergithub.com/jesseduffield/lazydocker/pkg/gui.Panels→github.com/jesseduffield/lazydocker/pkg/commands.Imagegithub.com/jesseduffield/lazydocker/pkg/gui.Panels→github.com/jesseduffield/lazydocker/pkg/commands.Networkgithub.com/jesseduffield/lazydocker/pkg/gui.Panels→github.com/jesseduffield/lazydocker/pkg/commands.Projectgithub.com/jesseduffield/lazydocker/pkg/gui.Panels→github.com/jesseduffield/lazydocker/pkg/commands.Servicegithub.com/jesseduffield/lazydocker/pkg/gui.Panels→github.com/jesseduffield/lazydocker/pkg/commands.Volumegithub.com/jesseduffield/lazydocker/pkg/gui.gui→github.com/jesseduffield/lazydocker/pkg/commands.Containergithub.com/jesseduffield/lazydocker/pkg/gui.gui→github.com/jesseduffield/lazydocker/pkg/commands.DockerCommandgithub.com/jesseduffield/lazydocker/pkg/gui.gui→github.com/jesseduffield/lazydocker/pkg/commands.OSCommandgithub.com/jesseduffield/lazydocker/pkg/gui.guiState→github.com/jesseduffield/lazydocker/pkg/commands.ContainerStatsgithub.com/jesseduffield/lazydocker/pkg/gui.guiState→github.com/jesseduffield/lazydocker/pkg/commands.Platform
- Direction
- com/jesseduffield/lazydocker/pkg/gui uses com/jesseduffield/lazydocker/pkg/commands, so a change to com/jesseduffield/lazydocker/pkg/commands can break com/jesseduffield/lazydocker/pkg/gui, while a change to com/jesseduffield/lazydocker/pkg/gui can't break com/jesseduffield/lazydocker/pkg/commands.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/gui uses a module listed above it, which is the healthy direction.
14→11 com/jesseduffield/lazydocker/pkg/gui uses com/jesseduffield/lazydocker/pkg/tasks✕
- Connections
- 2 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/gui uses a type in com/jesseduffield/lazydocker/pkg/tasks.
- The types involved
github.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/tasks.TaskFuncgithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/tasks.TaskManager
- Direction
- com/jesseduffield/lazydocker/pkg/gui uses com/jesseduffield/lazydocker/pkg/tasks, so a change to com/jesseduffield/lazydocker/pkg/tasks can break com/jesseduffield/lazydocker/pkg/gui, while a change to com/jesseduffield/lazydocker/pkg/gui can't break com/jesseduffield/lazydocker/pkg/tasks.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/gui uses a module listed above it, which is the healthy direction.
14→12 com/jesseduffield/lazydocker/pkg/gui uses com/jesseduffield/lazydocker/pkg/gui/panels✕
- Connections
- 5 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/gui uses a type in com/jesseduffield/lazydocker/pkg/gui/panels.
- The types involved
github.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/gui/panels.IGuigithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/gui/panels.ISideListPanelgithub.com/jesseduffield/lazydocker/pkg/gui.Gui→github.com/jesseduffield/lazydocker/pkg/gui/panels.SideListPanelgithub.com/jesseduffield/lazydocker/pkg/gui.Panels→github.com/jesseduffield/lazydocker/pkg/gui/panels.SideListPanelgithub.com/jesseduffield/lazydocker/pkg/gui.filterState→github.com/jesseduffield/lazydocker/pkg/gui/panels.ISideListPanel
- Direction
- com/jesseduffield/lazydocker/pkg/gui uses com/jesseduffield/lazydocker/pkg/gui/panels, so a change to com/jesseduffield/lazydocker/pkg/gui/panels can break com/jesseduffield/lazydocker/pkg/gui, while a change to com/jesseduffield/lazydocker/pkg/gui can't break com/jesseduffield/lazydocker/pkg/gui/panels.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/gui uses a module listed above it, which is the healthy direction.
15→3 com/jesseduffield/lazydocker/pkg/app uses com/jesseduffield/lazydocker/pkg/config✕
- Connections
- 2 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/app uses a type in com/jesseduffield/lazydocker/pkg/config.
- The types involved
github.com/jesseduffield/lazydocker/pkg/app.App→github.com/jesseduffield/lazydocker/pkg/config.AppConfiggithub.com/jesseduffield/lazydocker/pkg/app.app→github.com/jesseduffield/lazydocker/pkg/config.AppConfig
- Direction
- com/jesseduffield/lazydocker/pkg/app uses com/jesseduffield/lazydocker/pkg/config, so a change to com/jesseduffield/lazydocker/pkg/config can break com/jesseduffield/lazydocker/pkg/app, while a change to com/jesseduffield/lazydocker/pkg/app can't break com/jesseduffield/lazydocker/pkg/config.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/app uses a module listed above it, which is the healthy direction.
15→5 com/jesseduffield/lazydocker/pkg/app uses com/jesseduffield/lazydocker/pkg/i18n✕
- Connections
- 1 pair of types, where a type in com/jesseduffield/lazydocker/pkg/app uses a type in com/jesseduffield/lazydocker/pkg/i18n.
- The types involved
github.com/jesseduffield/lazydocker/pkg/app.App→github.com/jesseduffield/lazydocker/pkg/i18n.TranslationSet
- Direction
- com/jesseduffield/lazydocker/pkg/app uses com/jesseduffield/lazydocker/pkg/i18n, so a change to com/jesseduffield/lazydocker/pkg/i18n can break com/jesseduffield/lazydocker/pkg/app, while a change to com/jesseduffield/lazydocker/pkg/app can't break com/jesseduffield/lazydocker/pkg/i18n.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/app uses a module listed above it, which is the healthy direction.
15→9 com/jesseduffield/lazydocker/pkg/app uses com/jesseduffield/lazydocker/pkg/commands✕
- Connections
- 2 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/app uses a type in com/jesseduffield/lazydocker/pkg/commands.
- The types involved
github.com/jesseduffield/lazydocker/pkg/app.App→github.com/jesseduffield/lazydocker/pkg/commands.DockerCommandgithub.com/jesseduffield/lazydocker/pkg/app.App→github.com/jesseduffield/lazydocker/pkg/commands.OSCommand
- Direction
- com/jesseduffield/lazydocker/pkg/app uses com/jesseduffield/lazydocker/pkg/commands, so a change to com/jesseduffield/lazydocker/pkg/commands can break com/jesseduffield/lazydocker/pkg/app, while a change to com/jesseduffield/lazydocker/pkg/app can't break com/jesseduffield/lazydocker/pkg/commands.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/app uses a module listed above it, which is the healthy direction.
15→14 com/jesseduffield/lazydocker/pkg/app uses com/jesseduffield/lazydocker/pkg/gui✕
- Connections
- 1 pair of types, where a type in com/jesseduffield/lazydocker/pkg/app uses a type in com/jesseduffield/lazydocker/pkg/gui.
- The types involved
github.com/jesseduffield/lazydocker/pkg/app.App→github.com/jesseduffield/lazydocker/pkg/gui.Gui
- Direction
- com/jesseduffield/lazydocker/pkg/app uses com/jesseduffield/lazydocker/pkg/gui, so a change to com/jesseduffield/lazydocker/pkg/gui can break com/jesseduffield/lazydocker/pkg/app, while a change to com/jesseduffield/lazydocker/pkg/app can't break com/jesseduffield/lazydocker/pkg/gui.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/app uses a module listed above it, which is the healthy direction.
16→14 com/jesseduffield/lazydocker/pkg/cheatsheet uses com/jesseduffield/lazydocker/pkg/gui✕
- Connections
- 2 pairs of types, where a type in com/jesseduffield/lazydocker/pkg/cheatsheet uses a type in com/jesseduffield/lazydocker/pkg/gui.
- The types involved
github.com/jesseduffield/lazydocker/pkg/cheatsheet.bindingSection→github.com/jesseduffield/lazydocker/pkg/gui.Bindinggithub.com/jesseduffield/lazydocker/pkg/cheatsheet.cheatsheet→github.com/jesseduffield/lazydocker/pkg/gui.Binding
- Direction
- com/jesseduffield/lazydocker/pkg/cheatsheet uses com/jesseduffield/lazydocker/pkg/gui, so a change to com/jesseduffield/lazydocker/pkg/gui can break com/jesseduffield/lazydocker/pkg/cheatsheet, while a change to com/jesseduffield/lazydocker/pkg/cheatsheet can't break com/jesseduffield/lazydocker/pkg/gui.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/cheatsheet uses a module listed above it, which is the healthy direction.
16→15 com/jesseduffield/lazydocker/pkg/cheatsheet uses com/jesseduffield/lazydocker/pkg/app✕
- Connections
- 1 pair of types, where a type in com/jesseduffield/lazydocker/pkg/cheatsheet uses a type in com/jesseduffield/lazydocker/pkg/app.
- The types involved
github.com/jesseduffield/lazydocker/pkg/cheatsheet.cheatsheet→github.com/jesseduffield/lazydocker/pkg/app.App
- Direction
- com/jesseduffield/lazydocker/pkg/cheatsheet uses com/jesseduffield/lazydocker/pkg/app, so a change to com/jesseduffield/lazydocker/pkg/app can break com/jesseduffield/lazydocker/pkg/cheatsheet, while a change to com/jesseduffield/lazydocker/pkg/cheatsheet can't break com/jesseduffield/lazydocker/pkg/app.
- Position
- Below the diagonal: com/jesseduffield/lazydocker/pkg/cheatsheet uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 62 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 16 | High / Critical |
| A02:2025 — Security Misconfiguration | 10 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.go; Resolve the 40 Orphaned file finding(s) in Knowledge Freshness — start with container_stats.go (2), docker.go, REDACTED; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.go. | +8.1 pts | Low | ADR Quality |
| Resolve the 40 Orphaned file finding(s) in Knowledge Freshness — start with container_stats.go (2), docker.go, REDACTED. | +7.1 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.7 pts | Medium | Architecture documentation |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| 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.5 pts | Medium | Documentation (README) |
| Resolve the 10 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. | +1.9 pts | Medium | Dependency Hygiene |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.8 pts | Low | Bus Factor |
| Swallowed exception (caught, then discarded) | +1.5 pts | Medium | Exception handling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.8 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.1 | Slop | Secrets (history): High secret: REDACTED |
| REDACTED | 3.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| pkg/gui/gui.go | 6.0 | Mixed | Explicit Debt: TodoComment |
| pkg/gui/container_logs.go | 6.7 | Mixed | Explicit Debt: TodoComment |
| pkg/gui/keybindings.go | 6.7 | Mixed | Explicit Debt: FixmeComment |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | IaC & Container Security: High IaC: REDACTED |
| pkg/gui/focus.go | 7.3 | Mixed | Explicit Debt: TodoComment |
| pkg/commands/docker.go | 7.4 | Mixed | Cyclomatic Complexity: DockerCommand.RefreshContainersAndServices (cyclomatic 16) |
| pkg/gui/view_helpers.go | 7.4 | Mixed | Code Duplication: Edited copy of a member (25 corresponding lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 39 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 39 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, 209 of 244 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.go) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (9680 LoC, 68 module-visible types across 16 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `pkg/gui/panels/side_list_panel.go` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). the app booted but exposed no published HTTP port — nothing to crawl (publish the web service's port to unlock runtime evidence).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was DockerCommand.RefreshContainersAndServices at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with DockerCommand.RefreshContainersAndServices (cyclomatic 16). — Refactoring it lifts Cyclomatic Complexity from 9.9 to about 10.0/10.
D2 · Cognitive Complexity
8 function(s) exceeded the cognitive complexity threshold of 15; the worst was Gui.getBindings at 30.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cognitive Complexity — start with Gui.getBindings (cognitive 30), DockerCommand.RefreshContainersAndServices (cognitive 26), Gui.sidePanelChildren (cognitive 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
4 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with gui.go. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyFields finding(s) in God Classes — start with english.go. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with keybindings.go. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
6 duplicated block group(s) detected. A further 16 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 2 Edited copy of a member (16 corresponding lines) finding(s) in Code Duplication — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with gocui.go, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
1 of 17 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Go (github.com/jesseduffield/lazydocker): measured (0 flaky).
D12 · Dependency Hygiene
14 outdated, 0 author-deprecated direct Go module(s), 10 pinning or checksum defect(s). 26 of 26 direct requirement(s) were graded against proxy.golang.org (0 not served there, 7 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
What to do
- Resolve the 10 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (10 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 71 required Go module(s) use a banned license. Licences were read per module version from the licence files pkg.go.dev detects (via api.deps.dev), over every module this repository's REDACTED requires, direct and indirect, at the version the build uses. Go records no test-only scope at module level, so modules only this repository's own tests import are included. 1 of them carry no licence file that matches a known SPDX licence; that is missing data, not a violation, and none of them is charged.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is pkg/gui/gui.go. Counted over 41 of the 79 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
10 deducted task-comment markers across 9680 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 9 TodoComment finding(s) in Explicit Debt — start with gui.go (3), focus.go (2), container_logs.go. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with keybindings.go. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.go. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
36 % of calls cross a namespace and 4 % go through an interface, but 43 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
62 finding(s): 0 critical, 26 high, 36 medium, 0 low. 19 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `README.md`, `pkg/gui/panels/side_list_panel.go` (line 38) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 19 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (19 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
8 finding(s): 1 critical, 3 high, 4 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D31 · IaC & Container Security
10 finding(s): 0 critical, 2 high, 3 medium, 5 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 5 Low IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
41 of 41 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is pkg/config/app_config.go. Counted over 41 of the 79 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 40 Orphaned file finding(s) in Knowledge Freshness — start with container_stats.go (2), docker.go, REDACTED. — One of this dimension's main actionable groups (40 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with app_config.go. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX5 · Architecture & structure
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- 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
P2 · Observability
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
X26 · Unsynchronised callback handoff
- `PipeCommands` starts a goroutine on every pass of a loop, and each one writes `finalErrors`, a slice declared before the loop — `finalErrors = append(finalErrors, …)` on line 347. The loop never waits on `wg` before its next pass, so the goroutines of successive passes run at the same time and each one's write races the next one's; waiting on `wg` after the loop orders only what follows the wait. `finalErrors = append(finalErrors, …)` rewrites the slice variable itself — its pointer, length and capacity — so the other side reads or rewrites a variable mid-update: an append is lost, or a read sees a length its backing array does not have. `wg` is a `sync.WaitGroup`, which orders the handoff's signal and takes no exclusion over the slice's own state. Guard every write to `finalErrors` with one `sync.Mutex`, or have each goroutine send its result on a channel that this body alone receives from and writes into `finalErrors`. — REDACTED:347
What to do
- In Go, hand values from a goroutine to the body waiting on it over a channel the body receives from, rather than through a map or slice beside a `sync.WaitGroup` or a signal channel — or hold one `sync.Mutex` over every access to the shared map or slice on both sides. The wait orders the signal; it takes no exclusion over the map's or slice's own state.
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×34) — pkg/log/log.go:37, REDACTED:324, REDACTED:380, …
What to do
- Swallowed exception (caught, then discarded)
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 77% | Strong | Solid. |
| Architecture | 96% | Exemplary | Strongest area. |
| Maturity | 53% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 71% | Strong | Solid. |
| Security | 57% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 73 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the app booted but exposed no published HTTP port — nothing to crawl (publish the web service's port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~1149 lines of test source are present (.go) 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.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Go not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .go, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- D5 Coupling — Not applicable — this Go build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows none of the 2 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 CQRS handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 2 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Go source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a `func BenchmarkXxx(b *testing.B)` in any `_test.go` file, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. Go's `++`, `--` and assignments are STATEMENTS, not expressions, so none of them can appear in a `case` expression or anywhere else in a condition, and a type switch's cases are types. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Go's type system has no nullable and non-nullable types — every pointer, map, slice and interface is nil-able at every position, there is no switch that turns null checking on, and the compiler produces no nullability warning for an operator to silence. Not a gap in the analyzer and not a finding about your code.
- 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 — 33 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 138 finding(s)
- Swallowed exception (caught, then discarded) pkg/log/log.go:37
- Swallowed exception (caught, then discarded) REDACTED:324
- Swallowed exception (caught, then discarded) REDACTED:380
- Swallowed exception (caught, then discarded) REDACTED:389
- Swallowed exception (caught, then discarded) REDACTED:406
- Swallowed exception (caught, then discarded) REDACTED:421
- Swallowed exception (caught, then discarded) REDACTED:447
- Swallowed exception (caught, then discarded) REDACTED:458
- Swallowed exception (caught, then discarded) REDACTED:479
- Swallowed exception (caught, then discarded) REDACTED:545
- Swallowed exception (caught, then discarded) REDACTED:130
- Swallowed exception (caught, then discarded) REDACTED:196
- Swallowed exception (caught, then discarded) REDACTED:52
- Swallowed exception (caught, then discarded) REDACTED:104
- Swallowed exception (caught, then discarded) REDACTED:154
- Swallowed exception (caught, then discarded) pkg/gui/project_panel.go:134
- Swallowed exception (caught, then discarded) REDACTED:166
- Swallowed exception (caught, then discarded) REDACTED:210
- Swallowed exception (caught, then discarded) REDACTED:222
- Swallowed exception (caught, then discarded) REDACTED:244
- Swallowed exception (caught, then discarded) REDACTED:263
- Swallowed exception (caught, then discarded) REDACTED:283
- Swallowed exception (caught, then discarded) REDACTED:306
- Swallowed exception (caught, then discarded) REDACTED:324
- Swallowed exception (caught, then discarded) REDACTED:413
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dependency pinned to a stale untagged commit: github.com/OpenPeeDeeP/xdg
- Dependency pinned to a stale untagged commit: github.com/boz/go-throttle
- Dependency pinned to a stale untagged commit: github.com/cloudfoundry/jibber_jabber
- Dependency pinned to a stale untagged commit: github.com/jesseduffield/asciigraph
- Dependency pinned to a stale untagged commit: github.com/jesseduffield/kill
- Dependency pinned to a stale untagged commit: github.com/jesseduffield/lazycore
- Dependency pinned to a stale untagged commit: github.com/jesseduffield/yaml
- Dependency pinned to a stale untagged commit: github.com/mcuadros/go-lookup
- Dependency pinned to a stale untagged commit: github.com/spkg/bom
- Dependency pinned to a stale untagged commit: golang.org/x/xerrors
- TodoComment pkg/gui/container_logs.go:25
- TodoComment REDACTED:470
- TodoComment pkg/commands/container.go:106
- TodoComment pkg/gui/focus.go:31
- TodoComment pkg/gui/focus.go:61
- TodoComment pkg/gui/gui.go:171
- TodoComment pkg/gui/gui.go:202
- TodoComment pkg/gui/gui.go:240
- TodoComment REDACTED:136
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (16 corresponding lines) REDACTED:387
- Edited copy of a member (16 corresponding lines) REDACTED:356
- Edited copy of a member (13 corresponding lines) REDACTED:492
- Edited copy of a member (13 corresponding lines) REDACTED:419
- Edited copy of a member (14 corresponding lines) pkg/gui/gocui.go:9
- Edited copy of a member (14 corresponding lines) REDACTED:396
- Duplicated block (15 lines × 2) REDACTED:252
- Duplicated block (15 lines × 2) pkg/gui/view_helpers.go:32
- Duplicated block (13 lines × 2) pkg/gui/gocui.go:10
- Duplicated block (13 lines × 2) pkg/utils/utils.go:209
- DockerCommand.RefreshContainersAndServices (cyclomatic 16) pkg/commands/docker.go:226
- FixmeComment pkg/gui/keybindings.go:15
- Gui.getBindings (cognitive 30) pkg/gui/options_menu_panel.go:10
- DockerCommand.RefreshContainersAndServices (cognitive 26) pkg/commands/docker.go:226
- Gui.sidePanelChildren (cognitive 21) pkg/gui/arrangement.go:142
- Gui.writeContainerLogs (cognitive 18) pkg/gui/container_logs.go:107
- OSCommand.PipeCommands (cognitive 17) REDACTED:309
- Gui.containerConfigStr (cognitive 17) REDACTED:184
- Gui.Run (cognitive 17) pkg/gui/gui.go:184
- DockerCommand.GetContainers (cognitive 16) pkg/commands/docker.go:374
- REDACTED
- TooManyMethods: Gui pkg/gui/gui.go:27
- TooManyFields: TranslationSet pkg/i18n/english.go:4
- MethodTooLong: Gui.GetInitialKeybindings pkg/gui/keybindings.go:57
- FunctionTooLong: i18n.englishSet pkg/i18n/english.go:141
- REDACTED
- Edited copies of one member (3 members, 37+ corresponding lines) REDACTED:122
- Edited copy of a member (25 corresponding lines) pkg/gui/view_helpers.go:22
- Edited copy of a member (26 corresponding lines) pkg/gui/tasks_adapter.go:68
- Edited copy of a member (21 corresponding lines) pkg/commands/network.go:23
- Edited copies of one member (4 members, 11+ corresponding lines) REDACTED:433
- Edited copies of one member (3 members, 18+ corresponding lines) REDACTED:242
- Edited copy of a member (11 corresponding lines) pkg/gui/view_helpers.go:288
- Edited copies of one member (4 members, 14+ corresponding lines) REDACTED:477
- Edited copies of one member (4 members, 13+ corresponding lines) REDACTED:520
- Edited copy of a member (8 corresponding lines) pkg/gui/gui.go:429
- Duplicated block (12 lines × 2) REDACTED:398
- Duplicated block (10 lines × 3) REDACTED:103
- Low cohesion: OSCommand (LCOM4 6) REDACTED:33
- Collection crosses a callback boundary unsynchronised REDACTED:347
Minor — 59 finding(s)
- Orphaned file pkg/commands/docker.go:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file pkg/gui/keybindings.go:1
- Orphaned file pkg/gui/gui.go:1
- Orphaned file pkg/i18n/english.go:1
- Orphaned file pkg/utils/utils.go:1
- Orphaned file REDACTED:1
- Orphaned file pkg/gui/view_helpers.go:1
- Orphaned file pkg/i18n/portuguese.go:1
- Orphaned file pkg/gui/project_panel.go:1
- Orphaned file pkg/i18n/french.go:1
- Orphaned file pkg/commands/container_stats.go:1
- Orphaned file pkg/i18n/spanish.go:1
- Orphaned file pkg/gui/views.go:1
- Orphaned file pkg/i18n/chinese.go:1
- Orphaned file pkg/gui/panels/side_list_panel.go:1
- Orphaned file REDACTED:1
- Orphaned file pkg/gui/arrangement.go:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file pkg/i18n/german.go:1
- Orphaned file pkg/i18n/turkish.go:1
- Orphaned file pkg/gui/presentation/containers.go:1
- Orphaned file pkg/i18n/dutch.go:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate pkg/gui/layout.go:106
- Duplicated predicate pkg/gui/project_panel.go:199
- Off-boarding risk: anonymized user #1
- No ADRs found main.go:1
- REDACTED
- Dormant codebase
- Most significant orphaned file pkg/config/app_config.go:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No release approval gate
Minor — 14 finding(s)
- Outdated: github.com/OpenPeeDeeP/xdg
- Outdated: github.com/docker/cli
- Outdated: github.com/fatih/color
- Outdated: github.com/goccy/go-yaml
- Outdated: github.com/gookit/color
- Outdated: github.com/imdario/mergo
- Outdated: github.com/integrii/flaggy
- Outdated: github.com/jesseduffield/asciigraph
- Outdated: github.com/mattn/go-runewidth
- Outdated: github.com/samber/lo
- Outdated: github.com/sasha-s/go-deadlock
- Outdated: github.com/sirupsen/logrus
- Outdated: github.com/spkg/bom
- Outdated: github.com/stretchr/testify
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1ebe8a6a6a7947b9b61d59f960471d99/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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1ebe8a6a6a7947b9b61d59f960471d99/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 62 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-418c476e76454a7291f5b0d9ead12d70 | 8 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 10 | artifacts/raw/trivy-config.json |
| 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. semgrep could not parse 1 file(s) — `pkg/gui/panels/side_list_panel.go` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-418c476e76454a7291f5b0d9ead12d70 | 0 | artifacts/raw/osv-scanner.json |