Executive summary
abiosoft/colima meets our standard for a preview release, though we found no recorded design decisions and no architecture document or diagram. It scores 67 out of 100 and is rated Strong, and all six of its critical findings are security problems in the build pipeline and in its automatic dependency updates.
Maturity, at 57, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 10 points. Raising Maturity to 62 would lift the score to about 69.
Five pipeline steps run downloads nobody checks. One automatic update takes new releases before a bad one can be spotted. Checking each download against a checksum and setting a waiting period for automatic updates would close both risks.
The product code is 11,281 lines, about €16,000 to rebuild.
If Maturity rose from 57 to 62, the lowest score rated Strong, the score would rise from 67 to about 69.
New since the last survey: 9 findings
- Code Duplication · Edited copy of a member (24 corresponding lines) util/downloader/http.go
- Code Duplication · Edited copy of a member (21 corresponding lines) environment/container/kubernetes/kubernetes.go
- Code Duplication · Edited copies of one member (4 members, 21+ corresponding lines) environment/host/host.go
- Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) model/docker.go
- Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) environment/vm/lima/limautil/disk.go
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) cmd/delete.go
- Code Duplication · Edited copy of a member (12 corresponding lines) environment/vm/lima/shell.go
- Code Duplication · Edited copy of a member (8 corresponding lines) environment/vm/lima/network.go
- Code Duplication · Edited copy of a member (10 corresponding lines) cmd/ssh.go
Rebuild cost: about €16,000 · Estimate
| Cost to rebuild | €5,200 to €26,000, for 86 to 272 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 67. 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: 11,281 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/abiosoft/colima/cli | 2 com/abiosoft/colima/cmd/colima | 3 com/abiosoft/colima/config | 4 com/abiosoft/colima/embedded | 5 com/abiosoft/colima/environment/guest/systemctl | 6 com/abiosoft/colima/store | 7 com/abiosoft/colima/util | 8 com/abiosoft/colima/util/fsutil | 9 com/abiosoft/colima/util/osutil | 10 com/abiosoft/colima/util/shautil | 11 com/abiosoft/colima/util/terminal | 12 com/abiosoft/colima/cmd/root | 13 com/abiosoft/colima/config/configmanager | 14 com/abiosoft/colima/environment | 15 com/abiosoft/colima/util/yamlutil | 16 com/abiosoft/colima/app | 17 com/abiosoft/colima/core | 18 com/abiosoft/colima/daemon/process | 19 com/abiosoft/colima/environment/container/containerd | 20 com/abiosoft/colima/environment/container/docker | 21 com/abiosoft/colima/environment/container/incus | 22 com/abiosoft/colima/environment/container/kubernetes | 23 com/abiosoft/colima/environment/host | 24 com/abiosoft/colima/environment/vm/lima/limaconfig | 25 com/abiosoft/colima/util/debutil | 26 com/abiosoft/colima/util/downloader | 27 com/abiosoft/colima/cmd/daemon | 28 com/abiosoft/colima/daemon | 29 com/abiosoft/colima/daemon/process/inotify | 30 com/abiosoft/colima/daemon/process/vmnet | 31 com/abiosoft/colima/environment/vm/lima/limautil | 32 com/abiosoft/colima/model | 33 com/abiosoft/colima/cmd | 34 com/abiosoft/colima/environment/vm/lima |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com/abiosoft/colima/cli | ||||||||||||||||||||||||||||||||||
| 2 com/abiosoft/colima/cmd/colima | ||||||||||||||||||||||||||||||||||
| 3 com/abiosoft/colima/config | ||||||||||||||||||||||||||||||||||
| 4 com/abiosoft/colima/embedded | ||||||||||||||||||||||||||||||||||
| 5 com/abiosoft/colima/environment/guest/systemctl | ||||||||||||||||||||||||||||||||||
| 6 com/abiosoft/colima/store | ||||||||||||||||||||||||||||||||||
| 7 com/abiosoft/colima/util | ||||||||||||||||||||||||||||||||||
| 8 com/abiosoft/colima/util/fsutil | ||||||||||||||||||||||||||||||||||
| 9 com/abiosoft/colima/util/osutil | ||||||||||||||||||||||||||||||||||
| 10 com/abiosoft/colima/util/shautil | ||||||||||||||||||||||||||||||||||
| 11 com/abiosoft/colima/util/terminal | ||||||||||||||||||||||||||||||||||
| 12 com/abiosoft/colima/cmd/root | 1 | |||||||||||||||||||||||||||||||||
| 13 com/abiosoft/colima/config/configmanager | 2 | |||||||||||||||||||||||||||||||||
| 14 com/abiosoft/colima/environment | 1 | 1 | ||||||||||||||||||||||||||||||||
| 15 com/abiosoft/colima/util/yamlutil | 1 | |||||||||||||||||||||||||||||||||
| 16 com/abiosoft/colima/app | 3 | 3 | ||||||||||||||||||||||||||||||||
| 17 com/abiosoft/colima/core | 3 | |||||||||||||||||||||||||||||||||
| 18 com/abiosoft/colima/daemon/process | 2 | |||||||||||||||||||||||||||||||||
| 19 com/abiosoft/colima/environment/container/containerd | 1 | 1 | 8 | |||||||||||||||||||||||||||||||
| 20 com/abiosoft/colima/environment/container/docker | 1 | 1 | 8 | |||||||||||||||||||||||||||||||
| 21 com/abiosoft/colima/environment/container/incus | 1 | 1 | 7 | |||||||||||||||||||||||||||||||
| 22 com/abiosoft/colima/environment/container/kubernetes | 3 | 1 | 1 | 6 | ||||||||||||||||||||||||||||||
| 23 com/abiosoft/colima/environment/host | 1 | 1 | 6 | |||||||||||||||||||||||||||||||
| 24 com/abiosoft/colima/environment/vm/lima/limaconfig | 3 | |||||||||||||||||||||||||||||||||
| 25 com/abiosoft/colima/util/debutil | 1 | 1 | ||||||||||||||||||||||||||||||||
| 26 com/abiosoft/colima/util/downloader | 3 | |||||||||||||||||||||||||||||||||
| 27 com/abiosoft/colima/cmd/daemon | 1 | |||||||||||||||||||||||||||||||||
| 28 com/abiosoft/colima/daemon | 3 | 2 | 3 | |||||||||||||||||||||||||||||||
| 29 com/abiosoft/colima/daemon/process/inotify | 1 | 1 | 4 | 3 | ||||||||||||||||||||||||||||||
| 30 com/abiosoft/colima/daemon/process/vmnet | 2 | 3 | 6 | |||||||||||||||||||||||||||||||
| 31 com/abiosoft/colima/environment/vm/lima/limautil | 2 | 3 | 1 | |||||||||||||||||||||||||||||||
| 32 com/abiosoft/colima/model | 1 | 4 | ||||||||||||||||||||||||||||||||
| 33 com/abiosoft/colima/cmd | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 34 com/abiosoft/colima/environment/vm/lima | 2 | 3 | 1 | 1 | 10 | 2 | 1 | 1 |
12→3 com/abiosoft/colima/cmd/root uses com/abiosoft/colima/config✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/cmd/root uses a type in com/abiosoft/colima/config.
- The types involved
github.com/abiosoft/colima/cmd/root.root→github.com/abiosoft/colima/config.VersionInfo
- Direction
- com/abiosoft/colima/cmd/root uses com/abiosoft/colima/config, so a change to com/abiosoft/colima/config can break com/abiosoft/colima/cmd/root, while a change to com/abiosoft/colima/cmd/root can't break com/abiosoft/colima/config.
- Position
- Below the diagonal: com/abiosoft/colima/cmd/root uses a module listed above it, which is the healthy direction.
13→3 com/abiosoft/colima/config/configmanager uses com/abiosoft/colima/config✕
- Connections
- 2 pairs of types, where a type in com/abiosoft/colima/config/configmanager uses a type in com/abiosoft/colima/config.
- The types involved
github.com/abiosoft/colima/config/configmanager.configmanager→github.com/abiosoft/colima/config.Configgithub.com/abiosoft/colima/config/configmanager.configmanager→github.com/abiosoft/colima/config.Mount
- Direction
- com/abiosoft/colima/config/configmanager uses com/abiosoft/colima/config, so a change to com/abiosoft/colima/config can break com/abiosoft/colima/config/configmanager, while a change to com/abiosoft/colima/config/configmanager can't break com/abiosoft/colima/config.
- Position
- Below the diagonal: com/abiosoft/colima/config/configmanager uses a module listed above it, which is the healthy direction.
14→3 com/abiosoft/colima/environment uses com/abiosoft/colima/config✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment uses a type in com/abiosoft/colima/config.
- The types involved
github.com/abiosoft/colima/environment.GuestActions→github.com/abiosoft/colima/config.Config
- Direction
- com/abiosoft/colima/environment uses com/abiosoft/colima/config, so a change to com/abiosoft/colima/config can break com/abiosoft/colima/environment, while a change to com/abiosoft/colima/environment can't break com/abiosoft/colima/config.
- Position
- Below the diagonal: com/abiosoft/colima/environment uses a module listed above it, which is the healthy direction.
14→5 com/abiosoft/colima/environment uses com/abiosoft/colima/environment/guest/systemctl✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment uses a type in com/abiosoft/colima/environment/guest/systemctl.
- The types involved
github.com/abiosoft/colima/environment.GuestActions→github.com/abiosoft/colima/environment/guest/systemctl.Runner
- Direction
- com/abiosoft/colima/environment uses com/abiosoft/colima/environment/guest/systemctl, so a change to com/abiosoft/colima/environment/guest/systemctl can break com/abiosoft/colima/environment, while a change to com/abiosoft/colima/environment can't break com/abiosoft/colima/environment/guest/systemctl.
- Position
- Below the diagonal: com/abiosoft/colima/environment uses a module listed above it, which is the healthy direction.
15→3 com/abiosoft/colima/util/yamlutil uses com/abiosoft/colima/config✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/util/yamlutil uses a type in com/abiosoft/colima/config.
- The types involved
github.com/abiosoft/colima/util/yamlutil.yamlutil→github.com/abiosoft/colima/config.Config
- Direction
- com/abiosoft/colima/util/yamlutil uses com/abiosoft/colima/config, so a change to com/abiosoft/colima/config can break com/abiosoft/colima/util/yamlutil, while a change to com/abiosoft/colima/util/yamlutil can't break com/abiosoft/colima/config.
- Position
- Below the diagonal: com/abiosoft/colima/util/yamlutil uses a module listed above it, which is the healthy direction.
16→3 com/abiosoft/colima/app uses com/abiosoft/colima/config✕
- Connections
- 3 pairs of types, where a type in com/abiosoft/colima/app uses a type in com/abiosoft/colima/config.
- The types involved
github.com/abiosoft/colima/app.App→github.com/abiosoft/colima/config.Configgithub.com/abiosoft/colima/app.colimaApp→github.com/abiosoft/colima/config.Configgithub.com/abiosoft/colima/app.colimaApp→github.com/abiosoft/colima/config.Kubernetes
- Direction
- com/abiosoft/colima/app uses com/abiosoft/colima/config, so a change to com/abiosoft/colima/config can break com/abiosoft/colima/app, while a change to com/abiosoft/colima/app can't break com/abiosoft/colima/config.
- Position
- Below the diagonal: com/abiosoft/colima/app uses a module listed above it, which is the healthy direction.
16→14 com/abiosoft/colima/app uses com/abiosoft/colima/environment✕
- Connections
- 3 pairs of types, where a type in com/abiosoft/colima/app uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/app.App→github.com/abiosoft/colima/environment.Containergithub.com/abiosoft/colima/app.colimaApp→github.com/abiosoft/colima/environment.Containergithub.com/abiosoft/colima/app.colimaApp→github.com/abiosoft/colima/environment.VM
- Direction
- com/abiosoft/colima/app uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/app, while a change to com/abiosoft/colima/app can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/app uses a module listed above it, which is the healthy direction.
17→14 com/abiosoft/colima/core uses com/abiosoft/colima/environment✕
- Connections
- 3 pairs of types, where a type in com/abiosoft/colima/core uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/core.core→github.com/abiosoft/colima/environment.Archgithub.com/abiosoft/colima/core.core→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/core.core→github.com/abiosoft/colima/environment.HostActions
- Direction
- com/abiosoft/colima/core uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/core, while a change to com/abiosoft/colima/core can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/core uses a module listed above it, which is the healthy direction.
18→14 com/abiosoft/colima/daemon/process uses com/abiosoft/colima/environment✕
- Connections
- 2 pairs of types, where a type in com/abiosoft/colima/daemon/process uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/daemon/process.Dependency→github.com/abiosoft/colima/environment.HostActionsgithub.com/abiosoft/colima/daemon/process.processDeps→github.com/abiosoft/colima/environment.HostActions
- Direction
- com/abiosoft/colima/daemon/process uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/daemon/process, while a change to com/abiosoft/colima/daemon/process can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/daemon/process uses a module listed above it, which is the healthy direction.
19→1 com/abiosoft/colima/environment/container/containerd uses com/abiosoft/colima/cli✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/container/containerd uses a type in com/abiosoft/colima/cli.
- The types involved
github.com/abiosoft/colima/environment/container/containerd.containerdRuntime→github.com/abiosoft/colima/cli.CommandChain
- Direction
- com/abiosoft/colima/environment/container/containerd uses com/abiosoft/colima/cli, so a change to com/abiosoft/colima/cli can break com/abiosoft/colima/environment/container/containerd, while a change to com/abiosoft/colima/environment/container/containerd can't break com/abiosoft/colima/cli.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/containerd uses a module listed above it, which is the healthy direction.
19→5 com/abiosoft/colima/environment/container/containerd uses com/abiosoft/colima/environment/guest/systemctl✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/container/containerd uses a type in com/abiosoft/colima/environment/guest/systemctl.
- The types involved
github.com/abiosoft/colima/environment/container/containerd.containerdRuntime→github.com/abiosoft/colima/environment/guest/systemctl.Systemctl
- Direction
- com/abiosoft/colima/environment/container/containerd uses com/abiosoft/colima/environment/guest/systemctl, so a change to com/abiosoft/colima/environment/guest/systemctl can break com/abiosoft/colima/environment/container/containerd, while a change to com/abiosoft/colima/environment/container/containerd can't break com/abiosoft/colima/environment/guest/systemctl.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/containerd uses a module listed above it, which is the healthy direction.
19→14 com/abiosoft/colima/environment/container/containerd uses com/abiosoft/colima/environment✕
- Connections
- 8 pairs of types, where a type in com/abiosoft/colima/environment/container/containerd uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/environment/container/containerd.containerd→github.com/abiosoft/colima/environment.Containergithub.com/abiosoft/colima/environment/container/containerd.containerd→github.com/abiosoft/colima/environment.DataDiskgithub.com/abiosoft/colima/environment/container/containerd.containerd→github.com/abiosoft/colima/environment.DiskDirgithub.com/abiosoft/colima/environment/container/containerd.containerd→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/environment/container/containerd.containerd→github.com/abiosoft/colima/environment.HostActionsgithub.com/abiosoft/colima/environment/container/containerd.containerdRuntime→github.com/abiosoft/colima/environment.Containergithub.com/abiosoft/colima/environment/container/containerd.containerdRuntime→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/environment/container/containerd.containerdRuntime→github.com/abiosoft/colima/environment.HostActions
- Direction
- com/abiosoft/colima/environment/container/containerd uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/environment/container/containerd, while a change to com/abiosoft/colima/environment/container/containerd can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/containerd uses a module listed above it, which is the healthy direction.
20→1 com/abiosoft/colima/environment/container/docker uses com/abiosoft/colima/cli✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/container/docker uses a type in com/abiosoft/colima/cli.
- The types involved
github.com/abiosoft/colima/environment/container/docker.dockerRuntime→github.com/abiosoft/colima/cli.CommandChain
- Direction
- com/abiosoft/colima/environment/container/docker uses com/abiosoft/colima/cli, so a change to com/abiosoft/colima/cli can break com/abiosoft/colima/environment/container/docker, while a change to com/abiosoft/colima/environment/container/docker can't break com/abiosoft/colima/cli.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/docker uses a module listed above it, which is the healthy direction.
20→5 com/abiosoft/colima/environment/container/docker uses com/abiosoft/colima/environment/guest/systemctl✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/container/docker uses a type in com/abiosoft/colima/environment/guest/systemctl.
- The types involved
github.com/abiosoft/colima/environment/container/docker.dockerRuntime→github.com/abiosoft/colima/environment/guest/systemctl.Systemctl
- Direction
- com/abiosoft/colima/environment/container/docker uses com/abiosoft/colima/environment/guest/systemctl, so a change to com/abiosoft/colima/environment/guest/systemctl can break com/abiosoft/colima/environment/container/docker, while a change to com/abiosoft/colima/environment/container/docker can't break com/abiosoft/colima/environment/guest/systemctl.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/docker uses a module listed above it, which is the healthy direction.
20→14 com/abiosoft/colima/environment/container/docker uses com/abiosoft/colima/environment✕
- Connections
- 8 pairs of types, where a type in com/abiosoft/colima/environment/container/docker uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/environment/container/docker.docker→github.com/abiosoft/colima/environment.Containergithub.com/abiosoft/colima/environment/container/docker.docker→github.com/abiosoft/colima/environment.DataDiskgithub.com/abiosoft/colima/environment/container/docker.docker→github.com/abiosoft/colima/environment.DiskDirgithub.com/abiosoft/colima/environment/container/docker.docker→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/environment/container/docker.docker→github.com/abiosoft/colima/environment.HostActionsgithub.com/abiosoft/colima/environment/container/docker.dockerRuntime→github.com/abiosoft/colima/environment.Containergithub.com/abiosoft/colima/environment/container/docker.dockerRuntime→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/environment/container/docker.dockerRuntime→github.com/abiosoft/colima/environment.HostActions
- Direction
- com/abiosoft/colima/environment/container/docker uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/environment/container/docker, while a change to com/abiosoft/colima/environment/container/docker can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/docker uses a module listed above it, which is the healthy direction.
21→1 com/abiosoft/colima/environment/container/incus uses com/abiosoft/colima/cli✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/container/incus uses a type in com/abiosoft/colima/cli.
- The types involved
github.com/abiosoft/colima/environment/container/incus.incusRuntime→github.com/abiosoft/colima/cli.CommandChain
- Direction
- com/abiosoft/colima/environment/container/incus uses com/abiosoft/colima/cli, so a change to com/abiosoft/colima/cli can break com/abiosoft/colima/environment/container/incus, while a change to com/abiosoft/colima/environment/container/incus can't break com/abiosoft/colima/cli.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/incus uses a module listed above it, which is the healthy direction.
21→5 com/abiosoft/colima/environment/container/incus uses com/abiosoft/colima/environment/guest/systemctl✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/container/incus uses a type in com/abiosoft/colima/environment/guest/systemctl.
- The types involved
github.com/abiosoft/colima/environment/container/incus.incusRuntime→github.com/abiosoft/colima/environment/guest/systemctl.Systemctl
- Direction
- com/abiosoft/colima/environment/container/incus uses com/abiosoft/colima/environment/guest/systemctl, so a change to com/abiosoft/colima/environment/guest/systemctl can break com/abiosoft/colima/environment/container/incus, while a change to com/abiosoft/colima/environment/container/incus can't break com/abiosoft/colima/environment/guest/systemctl.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/incus uses a module listed above it, which is the healthy direction.
21→14 com/abiosoft/colima/environment/container/incus uses com/abiosoft/colima/environment✕
- Connections
- 7 pairs of types, where a type in com/abiosoft/colima/environment/container/incus uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/environment/container/incus.incus→github.com/abiosoft/colima/environment.Containergithub.com/abiosoft/colima/environment/container/incus.incus→github.com/abiosoft/colima/environment.DataDiskgithub.com/abiosoft/colima/environment/container/incus.incus→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/environment/container/incus.incus→github.com/abiosoft/colima/environment.HostActionsgithub.com/abiosoft/colima/environment/container/incus.incusRuntime→github.com/abiosoft/colima/environment.Containergithub.com/abiosoft/colima/environment/container/incus.incusRuntime→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/environment/container/incus.incusRuntime→github.com/abiosoft/colima/environment.HostActions
- Direction
- com/abiosoft/colima/environment/container/incus uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/environment/container/incus, while a change to com/abiosoft/colima/environment/container/incus can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/incus uses a module listed above it, which is the healthy direction.
22→1 com/abiosoft/colima/environment/container/kubernetes uses com/abiosoft/colima/cli✕
- Connections
- 3 pairs of types, where a type in com/abiosoft/colima/environment/container/kubernetes uses a type in com/abiosoft/colima/cli.
- The types involved
github.com/abiosoft/colima/environment/container/kubernetes.kubernetes→github.com/abiosoft/colima/cli.ActiveCommandChaingithub.com/abiosoft/colima/environment/container/kubernetes.kubernetesRuntime→github.com/abiosoft/colima/cli.ActiveCommandChaingithub.com/abiosoft/colima/environment/container/kubernetes.kubernetesRuntime→github.com/abiosoft/colima/cli.CommandChain
- Direction
- com/abiosoft/colima/environment/container/kubernetes uses com/abiosoft/colima/cli, so a change to com/abiosoft/colima/cli can break com/abiosoft/colima/environment/container/kubernetes, while a change to com/abiosoft/colima/environment/container/kubernetes can't break com/abiosoft/colima/cli.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/kubernetes uses a module listed above it, which is the healthy direction.
22→3 com/abiosoft/colima/environment/container/kubernetes uses com/abiosoft/colima/config✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/container/kubernetes uses a type in com/abiosoft/colima/config.
- The types involved
github.com/abiosoft/colima/environment/container/kubernetes.kubernetesRuntime→github.com/abiosoft/colima/config.Kubernetes
- Direction
- com/abiosoft/colima/environment/container/kubernetes uses com/abiosoft/colima/config, so a change to com/abiosoft/colima/config can break com/abiosoft/colima/environment/container/kubernetes, while a change to com/abiosoft/colima/environment/container/kubernetes can't break com/abiosoft/colima/config.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/kubernetes uses a module listed above it, which is the healthy direction.
22→5 com/abiosoft/colima/environment/container/kubernetes uses com/abiosoft/colima/environment/guest/systemctl✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/container/kubernetes uses a type in com/abiosoft/colima/environment/guest/systemctl.
- The types involved
github.com/abiosoft/colima/environment/container/kubernetes.kubernetesRuntime→github.com/abiosoft/colima/environment/guest/systemctl.Systemctl
- Direction
- com/abiosoft/colima/environment/container/kubernetes uses com/abiosoft/colima/environment/guest/systemctl, so a change to com/abiosoft/colima/environment/guest/systemctl can break com/abiosoft/colima/environment/container/kubernetes, while a change to com/abiosoft/colima/environment/container/kubernetes can't break com/abiosoft/colima/environment/guest/systemctl.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/kubernetes uses a module listed above it, which is the healthy direction.
22→14 com/abiosoft/colima/environment/container/kubernetes uses com/abiosoft/colima/environment✕
- Connections
- 6 pairs of types, where a type in com/abiosoft/colima/environment/container/kubernetes uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/environment/container/kubernetes.kubernetes→github.com/abiosoft/colima/environment.Containergithub.com/abiosoft/colima/environment/container/kubernetes.kubernetes→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/environment/container/kubernetes.kubernetes→github.com/abiosoft/colima/environment.HostActionsgithub.com/abiosoft/colima/environment/container/kubernetes.kubernetesRuntime→github.com/abiosoft/colima/environment.Containergithub.com/abiosoft/colima/environment/container/kubernetes.kubernetesRuntime→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/environment/container/kubernetes.kubernetesRuntime→github.com/abiosoft/colima/environment.HostActions
- Direction
- com/abiosoft/colima/environment/container/kubernetes uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/environment/container/kubernetes, while a change to com/abiosoft/colima/environment/container/kubernetes can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/environment/container/kubernetes uses a module listed above it, which is the healthy direction.
23→4 com/abiosoft/colima/environment/host uses com/abiosoft/colima/embedded✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/host uses a type in com/abiosoft/colima/embedded.
- The types involved
github.com/abiosoft/colima/environment/host.hostEnv→github.com/abiosoft/colima/embedded.SudoersInstaller
- Direction
- com/abiosoft/colima/environment/host uses com/abiosoft/colima/embedded, so a change to com/abiosoft/colima/embedded can break com/abiosoft/colima/environment/host, while a change to com/abiosoft/colima/environment/host can't break com/abiosoft/colima/embedded.
- Position
- Below the diagonal: com/abiosoft/colima/environment/host uses a module listed above it, which is the healthy direction.
23→5 com/abiosoft/colima/environment/host uses com/abiosoft/colima/environment/guest/systemctl✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/host uses a type in com/abiosoft/colima/environment/guest/systemctl.
- The types involved
github.com/abiosoft/colima/environment/host.hostEnv→github.com/abiosoft/colima/environment/guest/systemctl.Runner
- Direction
- com/abiosoft/colima/environment/host uses com/abiosoft/colima/environment/guest/systemctl, so a change to com/abiosoft/colima/environment/guest/systemctl can break com/abiosoft/colima/environment/host, while a change to com/abiosoft/colima/environment/host can't break com/abiosoft/colima/environment/guest/systemctl.
- Position
- Below the diagonal: com/abiosoft/colima/environment/host uses a module listed above it, which is the healthy direction.
23→14 com/abiosoft/colima/environment/host uses com/abiosoft/colima/environment✕
- Connections
- 6 pairs of types, where a type in com/abiosoft/colima/environment/host uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/environment/host.host→github.com/abiosoft/colima/environment.Dependenciesgithub.com/abiosoft/colima/environment/host.host→github.com/abiosoft/colima/environment.Hostgithub.com/abiosoft/colima/environment/host.hostEnv→github.com/abiosoft/colima/environment.Hostgithub.com/abiosoft/colima/environment/host.hostEnv→github.com/abiosoft/colima/environment.HostActionsgithub.com/abiosoft/colima/environment/host.hostEnv→github.com/abiosoft/colima/environment.fileActionsgithub.com/abiosoft/colima/environment/host.hostEnv→github.com/abiosoft/colima/environment.runActions
- Direction
- com/abiosoft/colima/environment/host uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/environment/host, while a change to com/abiosoft/colima/environment/host can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/environment/host uses a module listed above it, which is the healthy direction.
24→14 com/abiosoft/colima/environment/vm/lima/limaconfig uses com/abiosoft/colima/environment✕
- Connections
- 3 pairs of types, where a type in com/abiosoft/colima/environment/vm/lima/limaconfig uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/environment/vm/lima/limaconfig.Config→github.com/abiosoft/colima/environment.Archgithub.com/abiosoft/colima/environment/vm/lima/limaconfig.File→github.com/abiosoft/colima/environment.Archgithub.com/abiosoft/colima/environment/vm/lima/limaconfig.QEMUOpts→github.com/abiosoft/colima/environment.Arch
- Direction
- com/abiosoft/colima/environment/vm/lima/limaconfig uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/environment/vm/lima/limaconfig, while a change to com/abiosoft/colima/environment/vm/lima/limaconfig can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/environment/vm/lima/limaconfig uses a module listed above it, which is the healthy direction.
25→1 com/abiosoft/colima/util/debutil uses com/abiosoft/colima/cli✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/util/debutil uses a type in com/abiosoft/colima/cli.
- The types involved
github.com/abiosoft/colima/util/debutil.debutil→github.com/abiosoft/colima/cli.CommandChain
- Direction
- com/abiosoft/colima/util/debutil uses com/abiosoft/colima/cli, so a change to com/abiosoft/colima/cli can break com/abiosoft/colima/util/debutil, while a change to com/abiosoft/colima/util/debutil can't break com/abiosoft/colima/cli.
- Position
- Below the diagonal: com/abiosoft/colima/util/debutil uses a module listed above it, which is the healthy direction.
25→14 com/abiosoft/colima/util/debutil uses com/abiosoft/colima/environment✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/util/debutil uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/util/debutil.debutil→github.com/abiosoft/colima/environment.GuestActions
- Direction
- com/abiosoft/colima/util/debutil uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/util/debutil, while a change to com/abiosoft/colima/util/debutil can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/util/debutil uses a module listed above it, which is the healthy direction.
26→14 com/abiosoft/colima/util/downloader uses com/abiosoft/colima/environment✕
- Connections
- 3 pairs of types, where a type in com/abiosoft/colima/util/downloader uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/util/downloader.SHA→github.com/abiosoft/colima/environment.HostActionsgithub.com/abiosoft/colima/util/downloader.downloader→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/util/downloader.downloader→github.com/abiosoft/colima/environment.HostActions
- Direction
- com/abiosoft/colima/util/downloader uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/util/downloader, while a change to com/abiosoft/colima/util/downloader can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/util/downloader uses a module listed above it, which is the healthy direction.
27→18 com/abiosoft/colima/cmd/daemon uses com/abiosoft/colima/daemon/process✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/cmd/daemon uses a type in com/abiosoft/colima/daemon/process.
- The types involved
github.com/abiosoft/colima/cmd/daemon.daemon→github.com/abiosoft/colima/daemon/process.Process
- Direction
- com/abiosoft/colima/cmd/daemon uses com/abiosoft/colima/daemon/process, so a change to com/abiosoft/colima/daemon/process can break com/abiosoft/colima/cmd/daemon, while a change to com/abiosoft/colima/cmd/daemon can't break com/abiosoft/colima/daemon/process.
- Position
- Below the diagonal: com/abiosoft/colima/cmd/daemon uses a module listed above it, which is the healthy direction.
28→3 com/abiosoft/colima/daemon uses com/abiosoft/colima/config✕
- Connections
- 3 pairs of types, where a type in com/abiosoft/colima/daemon uses a type in com/abiosoft/colima/config.
- The types involved
github.com/abiosoft/colima/daemon.Manager→github.com/abiosoft/colima/config.Configgithub.com/abiosoft/colima/daemon.daemon→github.com/abiosoft/colima/config.Configgithub.com/abiosoft/colima/daemon.processManager→github.com/abiosoft/colima/config.Config
- Direction
- com/abiosoft/colima/daemon uses com/abiosoft/colima/config, so a change to com/abiosoft/colima/config can break com/abiosoft/colima/daemon, while a change to com/abiosoft/colima/daemon can't break com/abiosoft/colima/config.
- Position
- Below the diagonal: com/abiosoft/colima/daemon uses a module listed above it, which is the healthy direction.
28→14 com/abiosoft/colima/daemon uses com/abiosoft/colima/environment✕
- Connections
- 2 pairs of types, where a type in com/abiosoft/colima/daemon uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/daemon.daemon→github.com/abiosoft/colima/environment.HostActionsgithub.com/abiosoft/colima/daemon.processManager→github.com/abiosoft/colima/environment.HostActions
- Direction
- com/abiosoft/colima/daemon uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/daemon, while a change to com/abiosoft/colima/daemon can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/daemon uses a module listed above it, which is the healthy direction.
28→18 com/abiosoft/colima/daemon uses com/abiosoft/colima/daemon/process✕
- Connections
- 3 pairs of types, where a type in com/abiosoft/colima/daemon uses a type in com/abiosoft/colima/daemon/process.
- The types involved
github.com/abiosoft/colima/daemon.Manager→github.com/abiosoft/colima/daemon/process.Dependencygithub.com/abiosoft/colima/daemon.daemon→github.com/abiosoft/colima/daemon/process.Processgithub.com/abiosoft/colima/daemon.processManager→github.com/abiosoft/colima/daemon/process.Dependency
- Direction
- com/abiosoft/colima/daemon uses com/abiosoft/colima/daemon/process, so a change to com/abiosoft/colima/daemon/process can break com/abiosoft/colima/daemon, while a change to com/abiosoft/colima/daemon can't break com/abiosoft/colima/daemon/process.
- Position
- Below the diagonal: com/abiosoft/colima/daemon uses a module listed above it, which is the healthy direction.
29→4 com/abiosoft/colima/daemon/process/inotify uses com/abiosoft/colima/embedded✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/daemon/process/inotify uses a type in com/abiosoft/colima/embedded.
- The types involved
github.com/abiosoft/colima/daemon/process/inotify.Args→github.com/abiosoft/colima/embedded.SudoersInstaller
- Direction
- com/abiosoft/colima/daemon/process/inotify uses com/abiosoft/colima/embedded, so a change to com/abiosoft/colima/embedded can break com/abiosoft/colima/daemon/process/inotify, while a change to com/abiosoft/colima/daemon/process/inotify can't break com/abiosoft/colima/embedded.
- Position
- Below the diagonal: com/abiosoft/colima/daemon/process/inotify uses a module listed above it, which is the healthy direction.
29→5 com/abiosoft/colima/daemon/process/inotify uses com/abiosoft/colima/environment/guest/systemctl✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/daemon/process/inotify uses a type in com/abiosoft/colima/environment/guest/systemctl.
- The types involved
github.com/abiosoft/colima/daemon/process/inotify.Args→github.com/abiosoft/colima/environment/guest/systemctl.Runner
- Direction
- com/abiosoft/colima/daemon/process/inotify uses com/abiosoft/colima/environment/guest/systemctl, so a change to com/abiosoft/colima/environment/guest/systemctl can break com/abiosoft/colima/daemon/process/inotify, while a change to com/abiosoft/colima/daemon/process/inotify can't break com/abiosoft/colima/environment/guest/systemctl.
- Position
- Below the diagonal: com/abiosoft/colima/daemon/process/inotify uses a module listed above it, which is the healthy direction.
29→14 com/abiosoft/colima/daemon/process/inotify uses com/abiosoft/colima/environment✕
- Connections
- 4 pairs of types, where a type in com/abiosoft/colima/daemon/process/inotify uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/daemon/process/inotify.Args→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/daemon/process/inotify.Args→github.com/abiosoft/colima/environment.fileActionsgithub.com/abiosoft/colima/daemon/process/inotify.Args→github.com/abiosoft/colima/environment.runActionsgithub.com/abiosoft/colima/daemon/process/inotify.inotifyProcess→github.com/abiosoft/colima/environment.GuestActions
- Direction
- com/abiosoft/colima/daemon/process/inotify uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/daemon/process/inotify, while a change to com/abiosoft/colima/daemon/process/inotify can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/daemon/process/inotify uses a module listed above it, which is the healthy direction.
29→18 com/abiosoft/colima/daemon/process/inotify uses com/abiosoft/colima/daemon/process✕
- Connections
- 3 pairs of types, where a type in com/abiosoft/colima/daemon/process/inotify uses a type in com/abiosoft/colima/daemon/process.
- The types involved
github.com/abiosoft/colima/daemon/process/inotify.inotify→github.com/abiosoft/colima/daemon/process.Processgithub.com/abiosoft/colima/daemon/process/inotify.inotifyProcess→github.com/abiosoft/colima/daemon/process.Dependencygithub.com/abiosoft/colima/daemon/process/inotify.inotifyProcess→github.com/abiosoft/colima/daemon/process.Process
- Direction
- com/abiosoft/colima/daemon/process/inotify uses com/abiosoft/colima/daemon/process, so a change to com/abiosoft/colima/daemon/process can break com/abiosoft/colima/daemon/process/inotify, while a change to com/abiosoft/colima/daemon/process/inotify can't break com/abiosoft/colima/daemon/process.
- Position
- Below the diagonal: com/abiosoft/colima/daemon/process/inotify uses a module listed above it, which is the healthy direction.
30→3 com/abiosoft/colima/daemon/process/vmnet uses com/abiosoft/colima/config✕
- Connections
- 2 pairs of types, where a type in com/abiosoft/colima/daemon/process/vmnet uses a type in com/abiosoft/colima/config.
- The types involved
github.com/abiosoft/colima/daemon/process/vmnet.vmnet→github.com/abiosoft/colima/config.Subnetgithub.com/abiosoft/colima/daemon/process/vmnet.vmnetProcess→github.com/abiosoft/colima/config.Subnet
- Direction
- com/abiosoft/colima/daemon/process/vmnet uses com/abiosoft/colima/config, so a change to com/abiosoft/colima/config can break com/abiosoft/colima/daemon/process/vmnet, while a change to com/abiosoft/colima/daemon/process/vmnet can't break com/abiosoft/colima/config.
- Position
- Below the diagonal: com/abiosoft/colima/daemon/process/vmnet uses a module listed above it, which is the healthy direction.
30→14 com/abiosoft/colima/daemon/process/vmnet uses com/abiosoft/colima/environment✕
- Connections
- 3 pairs of types, where a type in com/abiosoft/colima/daemon/process/vmnet uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/daemon/process/vmnet.sudoerFile→github.com/abiosoft/colima/environment.HostActionsgithub.com/abiosoft/colima/daemon/process/vmnet.vmnetFile→github.com/abiosoft/colima/environment.HostActionsgithub.com/abiosoft/colima/daemon/process/vmnet.vmnetRunDir→github.com/abiosoft/colima/environment.HostActions
- Direction
- com/abiosoft/colima/daemon/process/vmnet uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/daemon/process/vmnet, while a change to com/abiosoft/colima/daemon/process/vmnet can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/daemon/process/vmnet uses a module listed above it, which is the healthy direction.
30→18 com/abiosoft/colima/daemon/process/vmnet uses com/abiosoft/colima/daemon/process✕
- Connections
- 6 pairs of types, where a type in com/abiosoft/colima/daemon/process/vmnet uses a type in com/abiosoft/colima/daemon/process.
- The types involved
github.com/abiosoft/colima/daemon/process/vmnet.sudoerFile→github.com/abiosoft/colima/daemon/process.Dependencygithub.com/abiosoft/colima/daemon/process/vmnet.vmnet→github.com/abiosoft/colima/daemon/process.Processgithub.com/abiosoft/colima/daemon/process/vmnet.vmnetFile→github.com/abiosoft/colima/daemon/process.Dependencygithub.com/abiosoft/colima/daemon/process/vmnet.vmnetProcess→github.com/abiosoft/colima/daemon/process.Dependencygithub.com/abiosoft/colima/daemon/process/vmnet.vmnetProcess→github.com/abiosoft/colima/daemon/process.Processgithub.com/abiosoft/colima/daemon/process/vmnet.vmnetRunDir→github.com/abiosoft/colima/daemon/process.Dependency
- Direction
- com/abiosoft/colima/daemon/process/vmnet uses com/abiosoft/colima/daemon/process, so a change to com/abiosoft/colima/daemon/process can break com/abiosoft/colima/daemon/process/vmnet, while a change to com/abiosoft/colima/daemon/process/vmnet can't break com/abiosoft/colima/daemon/process.
- Position
- Below the diagonal: com/abiosoft/colima/daemon/process/vmnet uses a module listed above it, which is the healthy direction.
31→3 com/abiosoft/colima/environment/vm/lima/limautil uses com/abiosoft/colima/config✕
- Connections
- 2 pairs of types, where a type in com/abiosoft/colima/environment/vm/lima/limautil uses a type in com/abiosoft/colima/config.
- The types involved
github.com/abiosoft/colima/environment/vm/lima/limautil.InstanceInfo→github.com/abiosoft/colima/config.Configgithub.com/abiosoft/colima/environment/vm/lima/limautil.limautil→github.com/abiosoft/colima/config.Config
- Direction
- com/abiosoft/colima/environment/vm/lima/limautil uses com/abiosoft/colima/config, so a change to com/abiosoft/colima/config can break com/abiosoft/colima/environment/vm/lima/limautil, while a change to com/abiosoft/colima/environment/vm/lima/limautil can't break com/abiosoft/colima/config.
- Position
- Below the diagonal: com/abiosoft/colima/environment/vm/lima/limautil uses a module listed above it, which is the healthy direction.
31→14 com/abiosoft/colima/environment/vm/lima/limautil uses com/abiosoft/colima/environment✕
- Connections
- 3 pairs of types, where a type in com/abiosoft/colima/environment/vm/lima/limautil uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/environment/vm/lima/limautil.limautil→github.com/abiosoft/colima/environment.Archgithub.com/abiosoft/colima/environment/vm/lima/limautil.limautil→github.com/abiosoft/colima/environment.Hostgithub.com/abiosoft/colima/environment/vm/lima/limautil.limautil→github.com/abiosoft/colima/environment.HostActions
- Direction
- com/abiosoft/colima/environment/vm/lima/limautil uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/environment/vm/lima/limautil, while a change to com/abiosoft/colima/environment/vm/lima/limautil can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/environment/vm/lima/limautil uses a module listed above it, which is the healthy direction.
31→24 com/abiosoft/colima/environment/vm/lima/limautil uses com/abiosoft/colima/environment/vm/lima/limaconfig✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/vm/lima/limautil uses a type in com/abiosoft/colima/environment/vm/lima/limaconfig.
- The types involved
github.com/abiosoft/colima/environment/vm/lima/limautil.limautil→github.com/abiosoft/colima/environment/vm/lima/limaconfig.File
- Direction
- com/abiosoft/colima/environment/vm/lima/limautil uses com/abiosoft/colima/environment/vm/lima/limaconfig, so a change to com/abiosoft/colima/environment/vm/lima/limaconfig can break com/abiosoft/colima/environment/vm/lima/limautil, while a change to com/abiosoft/colima/environment/vm/lima/limautil can't break com/abiosoft/colima/environment/vm/lima/limaconfig.
- Position
- Below the diagonal: com/abiosoft/colima/environment/vm/lima/limautil uses a module listed above it, which is the healthy direction.
32→14 com/abiosoft/colima/model uses com/abiosoft/colima/environment✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/model uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/model.model→github.com/abiosoft/colima/environment.VM
- Direction
- com/abiosoft/colima/model uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/model, while a change to com/abiosoft/colima/model can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/model uses a module listed above it, which is the healthy direction.
32→16 com/abiosoft/colima/model uses com/abiosoft/colima/app✕
- Connections
- 4 pairs of types, where a type in com/abiosoft/colima/model uses a type in com/abiosoft/colima/app.
- The types involved
github.com/abiosoft/colima/model.Runner→github.com/abiosoft/colima/app.Appgithub.com/abiosoft/colima/model.dockerRunner→github.com/abiosoft/colima/app.Appgithub.com/abiosoft/colima/model.model→github.com/abiosoft/colima/app.Appgithub.com/abiosoft/colima/model.ramalamaRunner→github.com/abiosoft/colima/app.App
- Direction
- com/abiosoft/colima/model uses com/abiosoft/colima/app, so a change to com/abiosoft/colima/app can break com/abiosoft/colima/model, while a change to com/abiosoft/colima/model can't break com/abiosoft/colima/app.
- Position
- Below the diagonal: com/abiosoft/colima/model uses a module listed above it, which is the healthy direction.
33→3 com/abiosoft/colima/cmd uses com/abiosoft/colima/config✕
- Connections
- 2 pairs of types, where a type in com/abiosoft/colima/cmd uses a type in com/abiosoft/colima/config.
- The types involved
github.com/abiosoft/colima/cmd.cmd→github.com/abiosoft/colima/config.Configgithub.com/abiosoft/colima/cmd.cmd→github.com/abiosoft/colima/config.Mount
- Direction
- com/abiosoft/colima/cmd uses com/abiosoft/colima/config, so a change to com/abiosoft/colima/config can break com/abiosoft/colima/cmd, while a change to com/abiosoft/colima/cmd can't break com/abiosoft/colima/config.
- Position
- Below the diagonal: com/abiosoft/colima/cmd uses a module listed above it, which is the healthy direction.
33→9 com/abiosoft/colima/cmd uses com/abiosoft/colima/util/osutil✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/cmd uses a type in com/abiosoft/colima/util/osutil.
- The types involved
github.com/abiosoft/colima/cmd.cmd→github.com/abiosoft/colima/util/osutil.EnvVar
- Direction
- com/abiosoft/colima/cmd uses com/abiosoft/colima/util/osutil, so a change to com/abiosoft/colima/util/osutil can break com/abiosoft/colima/cmd, while a change to com/abiosoft/colima/cmd can't break com/abiosoft/colima/util/osutil.
- Position
- Below the diagonal: com/abiosoft/colima/cmd uses a module listed above it, which is the healthy direction.
33→16 com/abiosoft/colima/cmd uses com/abiosoft/colima/app✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/cmd uses a type in com/abiosoft/colima/app.
- The types involved
github.com/abiosoft/colima/cmd.cmd→github.com/abiosoft/colima/app.App
- Direction
- com/abiosoft/colima/cmd uses com/abiosoft/colima/app, so a change to com/abiosoft/colima/app can break com/abiosoft/colima/cmd, while a change to com/abiosoft/colima/cmd can't break com/abiosoft/colima/app.
- Position
- Below the diagonal: com/abiosoft/colima/cmd uses a module listed above it, which is the healthy direction.
33→32 com/abiosoft/colima/cmd uses com/abiosoft/colima/model✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/cmd uses a type in com/abiosoft/colima/model.
- The types involved
github.com/abiosoft/colima/cmd.cmd→github.com/abiosoft/colima/model.Runner
- Direction
- com/abiosoft/colima/cmd uses com/abiosoft/colima/model, so a change to com/abiosoft/colima/model can break com/abiosoft/colima/cmd, while a change to com/abiosoft/colima/cmd can't break com/abiosoft/colima/model.
- Position
- Below the diagonal: com/abiosoft/colima/cmd uses a module listed above it, which is the healthy direction.
34→1 com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/cli✕
- Connections
- 2 pairs of types, where a type in com/abiosoft/colima/environment/vm/lima uses a type in com/abiosoft/colima/cli.
- The types involved
github.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/cli.ActiveCommandChaingithub.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/cli.CommandChain
- Direction
- com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/cli, so a change to com/abiosoft/colima/cli can break com/abiosoft/colima/environment/vm/lima, while a change to com/abiosoft/colima/environment/vm/lima can't break com/abiosoft/colima/cli.
- Position
- Below the diagonal: com/abiosoft/colima/environment/vm/lima uses a module listed above it, which is the healthy direction.
34→3 com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/config✕
- Connections
- 3 pairs of types, where a type in com/abiosoft/colima/environment/vm/lima uses a type in com/abiosoft/colima/config.
- The types involved
github.com/abiosoft/colima/environment/vm/lima.lima→github.com/abiosoft/colima/config.Configgithub.com/abiosoft/colima/environment/vm/lima.lima→github.com/abiosoft/colima/config.Mountgithub.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/config.Config
- Direction
- com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/config, so a change to com/abiosoft/colima/config can break com/abiosoft/colima/environment/vm/lima, while a change to com/abiosoft/colima/environment/vm/lima can't break com/abiosoft/colima/config.
- Position
- Below the diagonal: com/abiosoft/colima/environment/vm/lima uses a module listed above it, which is the healthy direction.
34→4 com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/embedded✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/vm/lima uses a type in com/abiosoft/colima/embedded.
- The types involved
github.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/embedded.SudoersInstaller
- Direction
- com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/embedded, so a change to com/abiosoft/colima/embedded can break com/abiosoft/colima/environment/vm/lima, while a change to com/abiosoft/colima/environment/vm/lima can't break com/abiosoft/colima/embedded.
- Position
- Below the diagonal: com/abiosoft/colima/environment/vm/lima uses a module listed above it, which is the healthy direction.
34→5 com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/environment/guest/systemctl✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/vm/lima uses a type in com/abiosoft/colima/environment/guest/systemctl.
- The types involved
github.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/environment/guest/systemctl.Runner
- Direction
- com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/environment/guest/systemctl, so a change to com/abiosoft/colima/environment/guest/systemctl can break com/abiosoft/colima/environment/vm/lima, while a change to com/abiosoft/colima/environment/vm/lima can't break com/abiosoft/colima/environment/guest/systemctl.
- Position
- Below the diagonal: com/abiosoft/colima/environment/vm/lima uses a module listed above it, which is the healthy direction.
34→14 com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/environment✕
- Connections
- 10 pairs of types, where a type in com/abiosoft/colima/environment/vm/lima uses a type in com/abiosoft/colima/environment.
- The types involved
github.com/abiosoft/colima/environment/vm/lima.lima→github.com/abiosoft/colima/environment.DataDiskgithub.com/abiosoft/colima/environment/vm/lima.lima→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/environment/vm/lima.lima→github.com/abiosoft/colima/environment.HostActionsgithub.com/abiosoft/colima/environment/vm/lima.lima→github.com/abiosoft/colima/environment.VMgithub.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/environment.Archgithub.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/environment.GuestActionsgithub.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/environment.HostActionsgithub.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/environment.VMgithub.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/environment.fileActionsgithub.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/environment.runActions
- Direction
- com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/environment, so a change to com/abiosoft/colima/environment can break com/abiosoft/colima/environment/vm/lima, while a change to com/abiosoft/colima/environment/vm/lima can't break com/abiosoft/colima/environment.
- Position
- Below the diagonal: com/abiosoft/colima/environment/vm/lima uses a module listed above it, which is the healthy direction.
34→24 com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/environment/vm/lima/limaconfig✕
- Connections
- 2 pairs of types, where a type in com/abiosoft/colima/environment/vm/lima uses a type in com/abiosoft/colima/environment/vm/lima/limaconfig.
- The types involved
github.com/abiosoft/colima/environment/vm/lima.lima→github.com/abiosoft/colima/environment/vm/lima/limaconfig.Configgithub.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/environment/vm/lima/limaconfig.Config
- Direction
- com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/environment/vm/lima/limaconfig, so a change to com/abiosoft/colima/environment/vm/lima/limaconfig can break com/abiosoft/colima/environment/vm/lima, while a change to com/abiosoft/colima/environment/vm/lima can't break com/abiosoft/colima/environment/vm/lima/limaconfig.
- Position
- Below the diagonal: com/abiosoft/colima/environment/vm/lima uses a module listed above it, which is the healthy direction.
34→28 com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/daemon✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/vm/lima uses a type in com/abiosoft/colima/daemon.
- The types involved
github.com/abiosoft/colima/environment/vm/lima.limaVM→github.com/abiosoft/colima/daemon.Manager
- Direction
- com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/daemon, so a change to com/abiosoft/colima/daemon can break com/abiosoft/colima/environment/vm/lima, while a change to com/abiosoft/colima/environment/vm/lima can't break com/abiosoft/colima/daemon.
- Position
- Below the diagonal: com/abiosoft/colima/environment/vm/lima uses a module listed above it, which is the healthy direction.
34→31 com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/environment/vm/lima/limautil✕
- Connections
- 1 pair of types, where a type in com/abiosoft/colima/environment/vm/lima uses a type in com/abiosoft/colima/environment/vm/lima/limautil.
- The types involved
github.com/abiosoft/colima/environment/vm/lima.lima→github.com/abiosoft/colima/environment/vm/lima/limautil.LimaNetwork
- Direction
- com/abiosoft/colima/environment/vm/lima uses com/abiosoft/colima/environment/vm/lima/limautil, so a change to com/abiosoft/colima/environment/vm/lima/limautil can break com/abiosoft/colima/environment/vm/lima, while a change to com/abiosoft/colima/environment/vm/lima can't break com/abiosoft/colima/environment/vm/lima/limautil.
- Position
- Below the diagonal: com/abiosoft/colima/environment/vm/lima 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 | 11 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.go; 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; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.go. | +9.6 pts | Low | ADR Quality |
| 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. | +8.8 pts | Medium | Architecture documentation |
| Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with start.go, configmanager.go. | +2.1 pts | Medium | Churn × Complexity Hotspots |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +3.5 pts | Medium | Documentation (README) |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +1.4 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.4 pts | Low | Bus Factor |
| Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. | +0.9 pts | Low | Dependency Hygiene |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.8 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| environment/vm/lima/daemon.go | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| cmd/start.go | 7.1 | Near-clean | Cyclomatic Complexity: cmd.prepareConfig (cyclomatic 62) |
| app/app.go | 7.1 | Near-clean | Cyclomatic Complexity: app.generateSSHConfig (cyclomatic 18) |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| environment/vm/lima/limautil/network.go | 7.3 | Near-clean | Explicit Debt: TodoComment |
| environment/vm/lima/yaml.go | 7.4 | Near-clean | Cyclomatic Complexity: lima.newConf (cyclomatic 51) |
| util/downloader/http.go | 7.4 | Near-clean | Cyclomatic Complexity: HTTPClient.Download (cyclomatic 23) |
| environment/host/host.go | 7.4 | Near-clean | Code Duplication: Edited copies of one member (4 members, 21+ corresponding lines) |
| config/configmanager/configmanager.go | 7.8 | Near-clean | Cyclomatic Complexity: configmanager.ValidateConfig (cyclomatic 21) |
| daemon/process/inotify/events.go | 7.8 | Near-clean | Cyclomatic Complexity: inotifyProcess.handleEvents (cyclomatic 17) |
| util/yamlutil/yaml.go | 7.8 | Near-clean | Cognitive Complexity: yamlutil.traverseNode (cognitive 31) |
| environment/vm/lima/lima.go | 7.8 | Near-clean | Cognitive Complexity: limaVM.addPostStartActions (cognitive 20) |
| environment/vm/lima/limautil/disk.go | 7.8 | Near-clean | Code Duplication: Edited copies of one member (3 members, 14+ 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 42 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 — 42 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, 106 of 119 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)` (11281 LoC, 106 module-visible types across 34 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.
- 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 REDACTED (REDACTED). docker run failed (exit 125) — docker: Error response from daemon: no command specified. See 'docker run --help'.; runtime evidence skipped.
- 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.
- 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.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — 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.
- 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
10 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was cmd.prepareConfig at 62.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with cmd.prepareConfig (cyclomatic 62), lima.newConf (cyclomatic 51). — 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 2 together lifts Cyclomatic Complexity from 7.7 to about 8.5/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
18 function(s) exceeded the cognitive complexity threshold of 15; the worst was cmd.prepareConfig at 85.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with cmd.prepareConfig (cognitive 85), lima.newConf (cognitive 83). — 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 2 together lifts Cognitive Complexity from 6.1 to about 6.6/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with yaml.go, start.go. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with lima.go. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
9 duplicated block group(s) detected. A further 9 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 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with host.go (2), disk.go (2), k3s.go. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Edited copies of one member (3 members, 14+ corresponding lines) finding(s) in Code Duplication — start with docker.go, disk.go. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with kubernetes.go, model.go. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 18 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Go (github.com/abiosoft/colima): measured (0 flaky).
D12 · Dependency Hygiene
3 outdated, 0 author-deprecated direct Go module(s), 1 pinning or checksum defect(s). 11 of 11 direct requirement(s) were graded against proxy.golang.org (0 not served there, 1 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 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 19 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.
D15 · Churn × Complexity Hotspots
Top hotspots: cmd/start.go (5×62=310); config/configmanager/configmanager.go (2×21=42)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with start.go, configmanager.go. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
9 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is model/runner.go. Counted over 52 of the 98 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
5 deducted task-comment markers across 11281 LoC (0.0/KLoC) → score 9.9. 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 5 TodoComment finding(s) in Explicit Debt — start with network.go (2), environment.go, daemon.go. — One of this dimension's main actionable groups (5 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 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
73 % of calls cross a namespace and 26 % go through an interface, but 36 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 6 high, 5 medium, 0 low. semgrep hit a parse error in 2 file(s) — `environment/container/incus/config.yaml`, `environment/vm/lima/disk.sh` (lines 10–39) — 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 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 52 of the 98 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
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
AX4 · Dependency direction
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
What to do
- Add a health-check endpoint (a /healthz handler) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X14 · Bypassable address classification
X2 · Cancellation propagation
X26 · Unsynchronised callback handoff
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. (×23) — util/macos.go:126, REDACTED:42, REDACTED:68, …
- `if err := listener.Close(); 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. — REDACTED:45
- `if err := cmd.Run(); 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. — environment/vm/lima/limautil/disk.go:25
- `if err := json.NewDecoder(&buf).Decode(&resp); 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. — environment/vm/lima/limautil/disk.go:29
- `if _, err := os.Stat(bin); 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. — daemon/process/vmnet/deps.go:36
- `if _, err := os.Stat(f); 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. — config/configmanager/configmanager.go:154
- `if err := fsutil.MkdirAll(" ", 0755); 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. — REDACTED:130
- `if err := c.guest.Run(" ", " ", s.Script); 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. — app/app.go:170
What to do
- Swallowed exception (caught, then discarded)
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81% | Strong | Solid. |
| Architecture | 92% | Exemplary | Strongest area. |
| Maturity | 57% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 71% | Strong | Solid. |
| Security | 75% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 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 — 69 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 — docker run failed (exit 125) — docker: Error response from daemon: no command specified. See 'docker run --help'.; runtime evidence skipped 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 — ~1484 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) — 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.
- 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 — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 2 value object(s)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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
- 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
- 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.
- 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 — 6 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 97 finding(s)
- Swallowed exception (caught, then discarded) util/macos.go:126
- Swallowed exception (caught, then discarded) REDACTED:42
- Swallowed exception (caught, then discarded) REDACTED:45
- Swallowed exception (caught, then discarded) REDACTED:68
- Swallowed exception (caught, then discarded) REDACTED:87
- Swallowed exception (caught, then discarded) REDACTED:92
- Swallowed exception (caught, then discarded) REDACTED:98
- Swallowed exception (caught, then discarded) REDACTED:119
- Swallowed exception (caught, then discarded) REDACTED:124
- Swallowed exception (caught, then discarded) util/terminal/terminal.go:93
- Swallowed exception (caught, then discarded) util/downloader/http.go:297
- Swallowed exception (caught, then discarded) model/docker.go:140
- Swallowed exception (caught, then discarded) model/ramalama.go:29
- Swallowed exception (caught, then discarded) model/ramalama.go:96
- Swallowed exception (caught, then discarded) environment/vm/lima/limautil/disk.go:25
- Swallowed exception (caught, then discarded) environment/vm/lima/limautil/disk.go:29
- Swallowed exception (caught, then discarded) environment/vm/lima/limautil/image.go:43
- Swallowed exception (caught, then discarded) environment/vm/lima/limautil/network.go:24
- Swallowed exception (caught, then discarded) environment/container/kubernetes/kubernetes.go:61
- Swallowed exception (caught, then discarded) environment/container/incus/incus.go:352
- Swallowed exception (caught, then discarded) environment/container/docker/daemon.go:34
- Swallowed exception (caught, then discarded) environment/container/docker/daemon.go:38
- Swallowed exception (caught, then discarded) environment/container/containerd/containerd.go:100
- Swallowed exception (caught, then discarded) embedded/sudoers.go:27
- Swallowed exception (caught, then discarded) embedded/sudoers.go:31
- TodoComment environment/environment.go:76
- TodoComment environment/vm/lima/daemon.go:132
- TodoComment environment/vm/lima/limautil/network.go:20
- TodoComment environment/vm/lima/limautil/network.go:46
- TodoComment REDACTED:94
- Duplicated block (8 lines × 2) environment/container/kubernetes/k3s.go:67
- Duplicated block (8 lines × 2) environment/host/host.go:52
- Duplicated block (8 lines × 2) environment/host/host.go:133
- Duplicated block (8 lines × 2) environment/vm/lima/disk.go:50
- Duplicated block (8 lines × 2) environment/vm/lima/limautil/disk.go:38
- Hotspot: cmd/start.go cmd/start.go:468
- Hotspot: config/configmanager/configmanager.go config/configmanager/configmanager.go:51
- FunctionTooLong: lima.newConf environment/vm/lima/yaml.go:43
- FunctionTooLong: cmd.prepareConfig cmd/start.go:468
- Edited copies of one member (3 members, 14+ corresponding lines) model/docker.go:98
- Edited copies of one member (3 members, 14+ corresponding lines) environment/vm/lima/limautil/disk.go:37
- Duplicated block (11 lines × 2) cmd/kubernetes.go:59
- Duplicated block (11 lines × 2) cmd/model.go:81
- cmd.prepareConfig (cyclomatic 62) cmd/start.go:468
- lima.newConf (cyclomatic 51) environment/vm/lima/yaml.go:43
- limaVM.startDaemon (cyclomatic 29) environment/vm/lima/daemon.go:24
- cmd.setFlagDefaults (cyclomatic 25) cmd/start.go:345
- HTTPClient.Download (cyclomatic 23) util/downloader/http.go:100
- cmd.nerdctlLinkFunc (cyclomatic 21) REDACTED:71
- configmanager.ValidateConfig (cyclomatic 21) config/configmanager/configmanager.go:51
- app.generateSSHConfig (cyclomatic 18) app/app.go:649
- colimaApp.Delete (cyclomatic 17) app/app.go:225
- inotifyProcess.handleEvents (cyclomatic 17) daemon/process/inotify/events.go:23
- Dependency pinned to a stale untagged commit: github.com/google/shlex
- cmd.prepareConfig (cognitive 85) cmd/start.go:468
- lima.newConf (cognitive 83) environment/vm/lima/yaml.go:43
- limaVM.startDaemon (cognitive 54) environment/vm/lima/daemon.go:24
- inotifyProcess.handleEvents (cognitive 35) daemon/process/inotify/events.go:23
- HTTPClient.Download (cognitive 33) util/downloader/http.go:100
- cmd.setFlagDefaults (cognitive 32) cmd/start.go:345
- yamlutil.traverseNode (cognitive 31) util/yamlutil/yaml.go:140
- colimaApp.Status (cognitive 30) app/app.go:415
- app.generateSSHConfig (cognitive 27) app/app.go:649
- colimaApp.Delete (cognitive 26) app/app.go:225
- inotifyProcess.monitorContainerVolumes (cognitive 26) daemon/process/inotify/volumes.go:16
- cmd.nerdctlLinkFunc (cognitive 25) REDACTED:71
- configmanager.ValidateConfig (cognitive 24) config/configmanager/configmanager.go:51
- limaVM.addPostStartActions (cognitive 20) environment/vm/lima/lima.go:298
- yamlutil.encodeYAML (cognitive 20) util/yamlutil/yaml.go:39
- limautil.Instances (cognitive 18) environment/vm/lima/limautil/instance.go:77
- defaultWatcher.Watch (cognitive 17) daemon/process/inotify/watch.go:29
- ActiveCommandChain.Exec (cognitive 16) cli/chain.go:110
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: limaVM environment/vm/lima/lima.go:55
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (24 corresponding lines) util/downloader/http.go:73
- Edited copy of a member (21 corresponding lines) environment/container/kubernetes/kubernetes.go:186
- Edited copies of one member (4 members, 21+ corresponding lines) environment/host/host.go:51
- Edited copies of one member (3 members, 15+ corresponding lines) cmd/delete.go:8
- Edited copy of a member (12 corresponding lines) environment/vm/lima/shell.go:62
- Edited copy of a member (8 corresponding lines) environment/vm/lima/network.go:61
- Edited copy of a member (10 corresponding lines) cmd/ssh.go:9
- Duplicated block (8 lines × 3) cmd/model.go:43
- Duplicated block (8 lines × 4) environment/container/containerd/containerd.go:46
Minor — 13 finding(s)
- Silent fallback default on error environment/container/containerd/containerd.go:100
- Silent fallback default on error util/downloader/http.go:297
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found cmd/colima/main.go:1
- Scattered collaborators
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No changelog
- Duplicated predicate environment/vm/lima/network.go:62
Minor — 3 finding(s)
- Outdated: github.com/sevlyar/go-daemon
- Outdated: github.com/sirupsen/logrus
- Outdated: golang.org/x/term
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-11a20d8df08647cb976131dde3257940/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-11a20d8df08647cb976131dde3257940/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 . | 11 | 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-d36b17bf5c554e8e85239abeaed2ffe5 | 1 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | 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. | 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-d36b17bf5c554e8e85239abeaed2ffe5 | 0 | artifacts/raw/osv-scanner.json |