Executive summary
moezdil/siltide meets our standard for a preview release. It scores 68.0 out of 100 and is rated Strong, and all 12 of its critical findings are security problems.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step for the work it takes is recording design decisions, worth about 2.9 points. Planning backups and recovery comes next, worth about 3.7 points.
Nine settings leave the servers or containers unsafe. One automatic update takes new releases before a bad one can be spotted, and one pipeline step installs packages that can change without warning. Correcting the unsafe settings, setting a waiting period for automatic updates and pinning what the pipeline installs would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed.
The product code is 15,831 lines, about €26,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Rebuild cost: about €26,000 · Estimate
| Cost to rebuild | €8,600 to €43,000, for 143 to 453 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.0 at a score of 68. 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: 15,831 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 github.com/moezdil/siltide/internal/config | 2 github.com/moezdil/siltide/internal/device | 3 github.com/moezdil/siltide/internal/host | 4 github.com/moezdil/siltide/internal/kube | 5 github.com/moezdil/siltide/internal/procinfo | 6 github.com/moezdil/siltide/internal/provider | 7 github.com/moezdil/siltide/internal/slurm | 8 github.com/moezdil/siltide/internal/update | 9 github.com/moezdil/siltide/scripts/gif | 10 github.com/moezdil/siltide/scripts/schema | 11 site | 12 github.com/moezdil/siltide/internal/cost | 13 github.com/moezdil/siltide/internal/events | 14 github.com/moezdil/siltide/internal/health | 15 github.com/moezdil/siltide/internal/history | 16 github.com/moezdil/siltide/internal/provider/apple | 17 github.com/moezdil/siltide/internal/provider/dcgm | 18 github.com/moezdil/siltide/internal/provider/nvidia | 19 github.com/moezdil/siltide/internal/provider/remote | 20 github.com/moezdil/siltide/internal/provider/replay | 21 github.com/moezdil/siltide/internal/provider/sim | 22 github.com/moezdil/siltide/internal/provider/smi | 23 github.com/moezdil/siltide/internal/provider/sshp | 24 github.com/moezdil/siltide/internal/derive | 25 github.com/moezdil/siltide/internal/notify | 26 github.com/moezdil/siltide/internal/query | 27 github.com/moezdil/siltide/internal/collect | 28 github.com/moezdil/siltide | 29 github.com/moezdil/siltide/internal/mcp | 30 github.com/moezdil/siltide/internal/server | 31 github.com/moezdil/siltide/internal/tui | 32 github.com/moezdil/siltide/scripts/shots |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 github.com/moezdil/siltide/internal/config | ||||||||||||||||||||||||||||||||
| 2 github.com/moezdil/siltide/internal/device | ||||||||||||||||||||||||||||||||
| 3 github.com/moezdil/siltide/internal/host | ||||||||||||||||||||||||||||||||
| 4 github.com/moezdil/siltide/internal/kube | ||||||||||||||||||||||||||||||||
| 5 github.com/moezdil/siltide/internal/procinfo | ||||||||||||||||||||||||||||||||
| 6 github.com/moezdil/siltide/internal/provider | ||||||||||||||||||||||||||||||||
| 7 github.com/moezdil/siltide/internal/slurm | ||||||||||||||||||||||||||||||||
| 8 github.com/moezdil/siltide/internal/update | ||||||||||||||||||||||||||||||||
| 9 github.com/moezdil/siltide/scripts/gif | ||||||||||||||||||||||||||||||||
| 10 github.com/moezdil/siltide/scripts/schema | ||||||||||||||||||||||||||||||||
| 11 site | ||||||||||||||||||||||||||||||||
| 12 github.com/moezdil/siltide/internal/cost | 1 | |||||||||||||||||||||||||||||||
| 13 github.com/moezdil/siltide/internal/events | 3 | |||||||||||||||||||||||||||||||
| 14 github.com/moezdil/siltide/internal/health | 1 | |||||||||||||||||||||||||||||||
| 15 github.com/moezdil/siltide/internal/history | 4 | |||||||||||||||||||||||||||||||
| 16 github.com/moezdil/siltide/internal/provider/apple | 2 | 1 | ||||||||||||||||||||||||||||||
| 17 github.com/moezdil/siltide/internal/provider/dcgm | 1 | 1 | ||||||||||||||||||||||||||||||
| 18 github.com/moezdil/siltide/internal/provider/nvidia | 4 | 1 | ||||||||||||||||||||||||||||||
| 19 github.com/moezdil/siltide/internal/provider/remote | 1 | |||||||||||||||||||||||||||||||
| 20 github.com/moezdil/siltide/internal/provider/replay | 1 | 1 | ||||||||||||||||||||||||||||||
| 21 github.com/moezdil/siltide/internal/provider/sim | 3 | 1 | ||||||||||||||||||||||||||||||
| 22 github.com/moezdil/siltide/internal/provider/smi | 8 | 2 | ||||||||||||||||||||||||||||||
| 23 github.com/moezdil/siltide/internal/provider/sshp | 1 | |||||||||||||||||||||||||||||||
| 24 github.com/moezdil/siltide/internal/derive | 3 | 2 | ||||||||||||||||||||||||||||||
| 25 github.com/moezdil/siltide/internal/notify | 2 | |||||||||||||||||||||||||||||||
| 26 github.com/moezdil/siltide/internal/query | 4 | 1 | ||||||||||||||||||||||||||||||
| 27 github.com/moezdil/siltide/internal/collect | 2 | 3 | 3 | 3 | 1 | 3 | 1 | 2 | 4 | 2 | 4 | 1 | ||||||||||||||||||||
| 28 github.com/moezdil/siltide | 1 | 1 | 2 | |||||||||||||||||||||||||||||
| 29 github.com/moezdil/siltide/internal/mcp | 4 | 2 | 4 | |||||||||||||||||||||||||||||
| 30 github.com/moezdil/siltide/internal/server | 2 | |||||||||||||||||||||||||||||||
| 31 github.com/moezdil/siltide/internal/tui | 12 | 1 | 3 | 3 | 1 | 2 | 4 | |||||||||||||||||||||||||
| 32 github.com/moezdil/siltide/scripts/shots | 1 | 2 |
12→2 github.com/moezdil/siltide/internal/cost uses github.com/moezdil/siltide/internal/device✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/cost uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/cost.Table→github.com/moezdil/siltide/internal/device.Device
- Direction
- github.com/moezdil/siltide/internal/cost uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/cost, while a change to github.com/moezdil/siltide/internal/cost can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/cost uses a module listed above it, which is the healthy direction.
13→2 github.com/moezdil/siltide/internal/events uses github.com/moezdil/siltide/internal/device✕
- Connections
- 3 pairs of types, where a type in github.com/moezdil/siltide/internal/events uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/events.Detector→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/events.Rule→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/events.events→github.com/moezdil/siltide/internal/device.Process
- Direction
- github.com/moezdil/siltide/internal/events uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/events, while a change to github.com/moezdil/siltide/internal/events can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/events uses a module listed above it, which is the healthy direction.
14→2 github.com/moezdil/siltide/internal/health uses github.com/moezdil/siltide/internal/device✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/health uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/health.health→github.com/moezdil/siltide/internal/device.Device
- Direction
- github.com/moezdil/siltide/internal/health uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/health, while a change to github.com/moezdil/siltide/internal/health can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/health uses a module listed above it, which is the healthy direction.
15→2 github.com/moezdil/siltide/internal/history uses github.com/moezdil/siltide/internal/device✕
- Connections
- 4 pairs of types, where a type in github.com/moezdil/siltide/internal/history uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/history.Point→github.com/moezdil/siltide/internal/device.Metricgithub.com/moezdil/siltide/internal/history.Store→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/history.Store→github.com/moezdil/siltide/internal/device.Metricgithub.com/moezdil/siltide/internal/history.history→github.com/moezdil/siltide/internal/device.Metric
- Direction
- github.com/moezdil/siltide/internal/history uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/history, while a change to github.com/moezdil/siltide/internal/history can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/history uses a module listed above it, which is the healthy direction.
16→2 github.com/moezdil/siltide/internal/provider/apple uses github.com/moezdil/siltide/internal/device✕
- Connections
- 2 pairs of types, where a type in github.com/moezdil/siltide/internal/provider/apple uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/provider/apple.apple→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/provider/apple.state→github.com/moezdil/siltide/internal/device.Process
- Direction
- github.com/moezdil/siltide/internal/provider/apple uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/provider/apple, while a change to github.com/moezdil/siltide/internal/provider/apple can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/apple uses a module listed above it, which is the healthy direction.
16→6 github.com/moezdil/siltide/internal/provider/apple uses github.com/moezdil/siltide/internal/provider✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/provider/apple uses a type in github.com/moezdil/siltide/internal/provider.
- The types involved
github.com/moezdil/siltide/internal/provider/apple.apple→github.com/moezdil/siltide/internal/provider.Provider
- Direction
- github.com/moezdil/siltide/internal/provider/apple uses github.com/moezdil/siltide/internal/provider, so a change to github.com/moezdil/siltide/internal/provider can break github.com/moezdil/siltide/internal/provider/apple, while a change to github.com/moezdil/siltide/internal/provider/apple can't break github.com/moezdil/siltide/internal/provider.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/apple uses a module listed above it, which is the healthy direction.
17→2 github.com/moezdil/siltide/internal/provider/dcgm uses github.com/moezdil/siltide/internal/device✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/provider/dcgm uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/provider/dcgm.dcgm→github.com/moezdil/siltide/internal/device.Metrics
- Direction
- github.com/moezdil/siltide/internal/provider/dcgm uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/provider/dcgm, while a change to github.com/moezdil/siltide/internal/provider/dcgm can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/dcgm uses a module listed above it, which is the healthy direction.
17→6 github.com/moezdil/siltide/internal/provider/dcgm uses github.com/moezdil/siltide/internal/provider✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/provider/dcgm uses a type in github.com/moezdil/siltide/internal/provider.
- The types involved
github.com/moezdil/siltide/internal/provider/dcgm.dcgm→github.com/moezdil/siltide/internal/provider.Provider
- Direction
- github.com/moezdil/siltide/internal/provider/dcgm uses github.com/moezdil/siltide/internal/provider, so a change to github.com/moezdil/siltide/internal/provider can break github.com/moezdil/siltide/internal/provider/dcgm, while a change to github.com/moezdil/siltide/internal/provider/dcgm can't break github.com/moezdil/siltide/internal/provider.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/dcgm uses a module listed above it, which is the healthy direction.
18→2 github.com/moezdil/siltide/internal/provider/nvidia uses github.com/moezdil/siltide/internal/device✕
- Connections
- 4 pairs of types, where a type in github.com/moezdil/siltide/internal/provider/nvidia uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/provider/nvidia.nvidia→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/provider/nvidia.nvidia→github.com/moezdil/siltide/internal/device.Linkgithub.com/moezdil/siltide/internal/provider/nvidia.nvidia→github.com/moezdil/siltide/internal/device.Metricsgithub.com/moezdil/siltide/internal/provider/nvidia.nvidia→github.com/moezdil/siltide/internal/device.Process
- Direction
- github.com/moezdil/siltide/internal/provider/nvidia uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/provider/nvidia, while a change to github.com/moezdil/siltide/internal/provider/nvidia can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/nvidia uses a module listed above it, which is the healthy direction.
18→6 github.com/moezdil/siltide/internal/provider/nvidia uses github.com/moezdil/siltide/internal/provider✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/provider/nvidia uses a type in github.com/moezdil/siltide/internal/provider.
- The types involved
github.com/moezdil/siltide/internal/provider/nvidia.nvidia→github.com/moezdil/siltide/internal/provider.Provider
- Direction
- github.com/moezdil/siltide/internal/provider/nvidia uses github.com/moezdil/siltide/internal/provider, so a change to github.com/moezdil/siltide/internal/provider can break github.com/moezdil/siltide/internal/provider/nvidia, while a change to github.com/moezdil/siltide/internal/provider/nvidia can't break github.com/moezdil/siltide/internal/provider.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/nvidia uses a module listed above it, which is the healthy direction.
19→6 github.com/moezdil/siltide/internal/provider/remote uses github.com/moezdil/siltide/internal/provider✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/provider/remote uses a type in github.com/moezdil/siltide/internal/provider.
- The types involved
github.com/moezdil/siltide/internal/provider/remote.remote→github.com/moezdil/siltide/internal/provider.Provider
- Direction
- github.com/moezdil/siltide/internal/provider/remote uses github.com/moezdil/siltide/internal/provider, so a change to github.com/moezdil/siltide/internal/provider can break github.com/moezdil/siltide/internal/provider/remote, while a change to github.com/moezdil/siltide/internal/provider/remote can't break github.com/moezdil/siltide/internal/provider.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/remote uses a module listed above it, which is the healthy direction.
20→2 github.com/moezdil/siltide/internal/provider/replay uses github.com/moezdil/siltide/internal/device✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/provider/replay uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/provider/replay.frame→github.com/moezdil/siltide/internal/device.Device
- Direction
- github.com/moezdil/siltide/internal/provider/replay uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/provider/replay, while a change to github.com/moezdil/siltide/internal/provider/replay can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/replay uses a module listed above it, which is the healthy direction.
20→6 github.com/moezdil/siltide/internal/provider/replay uses github.com/moezdil/siltide/internal/provider✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/provider/replay uses a type in github.com/moezdil/siltide/internal/provider.
- The types involved
github.com/moezdil/siltide/internal/provider/replay.replay→github.com/moezdil/siltide/internal/provider.Provider
- Direction
- github.com/moezdil/siltide/internal/provider/replay uses github.com/moezdil/siltide/internal/provider, so a change to github.com/moezdil/siltide/internal/provider can break github.com/moezdil/siltide/internal/provider/replay, while a change to github.com/moezdil/siltide/internal/provider/replay can't break github.com/moezdil/siltide/internal/provider.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/replay uses a module listed above it, which is the healthy direction.
21→2 github.com/moezdil/siltide/internal/provider/sim uses github.com/moezdil/siltide/internal/device✕
- Connections
- 3 pairs of types, where a type in github.com/moezdil/siltide/internal/provider/sim uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/provider/sim.model→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/provider/sim.model→github.com/moezdil/siltide/internal/device.Vendorgithub.com/moezdil/siltide/internal/provider/sim.sim→github.com/moezdil/siltide/internal/device.Process
- Direction
- github.com/moezdil/siltide/internal/provider/sim uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/provider/sim, while a change to github.com/moezdil/siltide/internal/provider/sim can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/sim uses a module listed above it, which is the healthy direction.
21→6 github.com/moezdil/siltide/internal/provider/sim uses github.com/moezdil/siltide/internal/provider✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/provider/sim uses a type in github.com/moezdil/siltide/internal/provider.
- The types involved
github.com/moezdil/siltide/internal/provider/sim.sim→github.com/moezdil/siltide/internal/provider.Provider
- Direction
- github.com/moezdil/siltide/internal/provider/sim uses github.com/moezdil/siltide/internal/provider, so a change to github.com/moezdil/siltide/internal/provider can break github.com/moezdil/siltide/internal/provider/sim, while a change to github.com/moezdil/siltide/internal/provider/sim can't break github.com/moezdil/siltide/internal/provider.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/sim uses a module listed above it, which is the healthy direction.
22→2 github.com/moezdil/siltide/internal/provider/smi uses github.com/moezdil/siltide/internal/device✕
- Connections
- 8 pairs of types, where a type in github.com/moezdil/siltide/internal/provider/smi uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/provider/smi.Spec→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/provider/smi.Spec→github.com/moezdil/siltide/internal/device.Vendorgithub.com/moezdil/siltide/internal/provider/smi.neuron→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/provider/smi.smi→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/provider/smi.smi→github.com/moezdil/siltide/internal/device.Metricgithub.com/moezdil/siltide/internal/provider/smi.smi→github.com/moezdil/siltide/internal/device.Metricsgithub.com/moezdil/siltide/internal/provider/smi.smi→github.com/moezdil/siltide/internal/device.Processgithub.com/moezdil/siltide/internal/provider/smi.smi→github.com/moezdil/siltide/internal/device.Vendor
- Direction
- github.com/moezdil/siltide/internal/provider/smi uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/provider/smi, while a change to github.com/moezdil/siltide/internal/provider/smi can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/smi uses a module listed above it, which is the healthy direction.
22→6 github.com/moezdil/siltide/internal/provider/smi uses github.com/moezdil/siltide/internal/provider✕
- Connections
- 2 pairs of types, where a type in github.com/moezdil/siltide/internal/provider/smi uses a type in github.com/moezdil/siltide/internal/provider.
- The types involved
github.com/moezdil/siltide/internal/provider/smi.Spec→github.com/moezdil/siltide/internal/provider.Providergithub.com/moezdil/siltide/internal/provider/smi.smi→github.com/moezdil/siltide/internal/provider.Provider
- Direction
- github.com/moezdil/siltide/internal/provider/smi uses github.com/moezdil/siltide/internal/provider, so a change to github.com/moezdil/siltide/internal/provider can break github.com/moezdil/siltide/internal/provider/smi, while a change to github.com/moezdil/siltide/internal/provider/smi can't break github.com/moezdil/siltide/internal/provider.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/smi uses a module listed above it, which is the healthy direction.
23→6 github.com/moezdil/siltide/internal/provider/sshp uses github.com/moezdil/siltide/internal/provider✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/provider/sshp uses a type in github.com/moezdil/siltide/internal/provider.
- The types involved
github.com/moezdil/siltide/internal/provider/sshp.sshp→github.com/moezdil/siltide/internal/provider.Provider
- Direction
- github.com/moezdil/siltide/internal/provider/sshp uses github.com/moezdil/siltide/internal/provider, so a change to github.com/moezdil/siltide/internal/provider can break github.com/moezdil/siltide/internal/provider/sshp, while a change to github.com/moezdil/siltide/internal/provider/sshp can't break github.com/moezdil/siltide/internal/provider.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/provider/sshp uses a module listed above it, which is the healthy direction.
24→2 github.com/moezdil/siltide/internal/derive uses github.com/moezdil/siltide/internal/device✕
- Connections
- 3 pairs of types, where a type in github.com/moezdil/siltide/internal/derive uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/derive.Tracker→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/derive.derive→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/derive.derive→github.com/moezdil/siltide/internal/device.Metric
- Direction
- github.com/moezdil/siltide/internal/derive uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/derive, while a change to github.com/moezdil/siltide/internal/derive can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/derive uses a module listed above it, which is the healthy direction.
24→15 github.com/moezdil/siltide/internal/derive uses github.com/moezdil/siltide/internal/history✕
- Connections
- 2 pairs of types, where a type in github.com/moezdil/siltide/internal/derive uses a type in github.com/moezdil/siltide/internal/history.
- The types involved
github.com/moezdil/siltide/internal/derive.derive→github.com/moezdil/siltide/internal/history.Pointgithub.com/moezdil/siltide/internal/derive.derive→github.com/moezdil/siltide/internal/history.Store
- Direction
- github.com/moezdil/siltide/internal/derive uses github.com/moezdil/siltide/internal/history, so a change to github.com/moezdil/siltide/internal/history can break github.com/moezdil/siltide/internal/derive, while a change to github.com/moezdil/siltide/internal/derive can't break github.com/moezdil/siltide/internal/history.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/derive uses a module listed above it, which is the healthy direction.
25→13 github.com/moezdil/siltide/internal/notify uses github.com/moezdil/siltide/internal/events✕
- Connections
- 2 pairs of types, where a type in github.com/moezdil/siltide/internal/notify uses a type in github.com/moezdil/siltide/internal/events.
- The types involved
github.com/moezdil/siltide/internal/notify.Notifier→github.com/moezdil/siltide/internal/events.Eventgithub.com/moezdil/siltide/internal/notify.notify→github.com/moezdil/siltide/internal/events.Severity
- Direction
- github.com/moezdil/siltide/internal/notify uses github.com/moezdil/siltide/internal/events, so a change to github.com/moezdil/siltide/internal/events can break github.com/moezdil/siltide/internal/notify, while a change to github.com/moezdil/siltide/internal/notify can't break github.com/moezdil/siltide/internal/events.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/notify uses a module listed above it, which is the healthy direction.
26→2 github.com/moezdil/siltide/internal/query uses github.com/moezdil/siltide/internal/device✕
- Connections
- 4 pairs of types, where a type in github.com/moezdil/siltide/internal/query uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/query.Filter→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/query.Filter→github.com/moezdil/siltide/internal/device.Processgithub.com/moezdil/siltide/internal/query.query→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/query.query→github.com/moezdil/siltide/internal/device.Process
- Direction
- github.com/moezdil/siltide/internal/query uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/query, while a change to github.com/moezdil/siltide/internal/query can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/query uses a module listed above it, which is the healthy direction.
26→13 github.com/moezdil/siltide/internal/query uses github.com/moezdil/siltide/internal/events✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/query uses a type in github.com/moezdil/siltide/internal/events.
- The types involved
github.com/moezdil/siltide/internal/query.Filter→github.com/moezdil/siltide/internal/events.Event
- Direction
- github.com/moezdil/siltide/internal/query uses github.com/moezdil/siltide/internal/events, so a change to github.com/moezdil/siltide/internal/events can break github.com/moezdil/siltide/internal/query, while a change to github.com/moezdil/siltide/internal/query can't break github.com/moezdil/siltide/internal/events.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/query uses a module listed above it, which is the healthy direction.
27→1 github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/config✕
- Connections
- 2 pairs of types, where a type in github.com/moezdil/siltide/internal/collect uses a type in github.com/moezdil/siltide/internal/config.
- The types involved
github.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/config.Configgithub.com/moezdil/siltide/internal/collect.collect→github.com/moezdil/siltide/internal/config.Config
- Direction
- github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/config, so a change to github.com/moezdil/siltide/internal/config can break github.com/moezdil/siltide/internal/collect, while a change to github.com/moezdil/siltide/internal/collect can't break github.com/moezdil/siltide/internal/config.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/collect uses a module listed above it, which is the healthy direction.
27→2 github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/device✕
- Connections
- 3 pairs of types, where a type in github.com/moezdil/siltide/internal/collect uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/device.Metricgithub.com/moezdil/siltide/internal/collect.Snapshot→github.com/moezdil/siltide/internal/device.Device
- Direction
- github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/collect, while a change to github.com/moezdil/siltide/internal/collect can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/collect uses a module listed above it, which is the healthy direction.
27→3 github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/host✕
- Connections
- 3 pairs of types, where a type in github.com/moezdil/siltide/internal/collect uses a type in github.com/moezdil/siltide/internal/host.
- The types involved
github.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/host.Samplergithub.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/host.Statsgithub.com/moezdil/siltide/internal/collect.Snapshot→github.com/moezdil/siltide/internal/host.Stats
- Direction
- github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/host, so a change to github.com/moezdil/siltide/internal/host can break github.com/moezdil/siltide/internal/collect, while a change to github.com/moezdil/siltide/internal/collect can't break github.com/moezdil/siltide/internal/host.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/collect uses a module listed above it, which is the healthy direction.
27→4 github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/kube✕
- Connections
- 3 pairs of types, where a type in github.com/moezdil/siltide/internal/collect uses a type in github.com/moezdil/siltide/internal/kube.
- The types involved
github.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/kube.PodResourcesgithub.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/kube.Resolvergithub.com/moezdil/siltide/internal/collect.Snapshot→github.com/moezdil/siltide/internal/kube.NodeInfo
- Direction
- github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/kube, so a change to github.com/moezdil/siltide/internal/kube can break github.com/moezdil/siltide/internal/collect, while a change to github.com/moezdil/siltide/internal/collect can't break github.com/moezdil/siltide/internal/kube.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/collect uses a module listed above it, which is the healthy direction.
27→5 github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/procinfo✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/collect uses a type in github.com/moezdil/siltide/internal/procinfo.
- The types involved
github.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/procinfo.Cache
- Direction
- github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/procinfo, so a change to github.com/moezdil/siltide/internal/procinfo can break github.com/moezdil/siltide/internal/collect, while a change to github.com/moezdil/siltide/internal/collect can't break github.com/moezdil/siltide/internal/procinfo.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/collect uses a module listed above it, which is the healthy direction.
27→6 github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/provider✕
- Connections
- 3 pairs of types, where a type in github.com/moezdil/siltide/internal/collect uses a type in github.com/moezdil/siltide/internal/provider.
- The types involved
github.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/provider.Eventgithub.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/provider.Providergithub.com/moezdil/siltide/internal/collect.collect→github.com/moezdil/siltide/internal/provider.Provider
- Direction
- github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/provider, so a change to github.com/moezdil/siltide/internal/provider can break github.com/moezdil/siltide/internal/collect, while a change to github.com/moezdil/siltide/internal/collect can't break github.com/moezdil/siltide/internal/provider.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/collect uses a module listed above it, which is the healthy direction.
27→7 github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/slurm✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/collect uses a type in github.com/moezdil/siltide/internal/slurm.
- The types involved
github.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/slurm.Resolver
- Direction
- github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/slurm, so a change to github.com/moezdil/siltide/internal/slurm can break github.com/moezdil/siltide/internal/collect, while a change to github.com/moezdil/siltide/internal/collect can't break github.com/moezdil/siltide/internal/slurm.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/collect uses a module listed above it, which is the healthy direction.
27→12 github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/cost✕
- Connections
- 2 pairs of types, where a type in github.com/moezdil/siltide/internal/collect uses a type in github.com/moezdil/siltide/internal/cost.
- The types involved
github.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/cost.Tablegithub.com/moezdil/siltide/internal/collect.Snapshot→github.com/moezdil/siltide/internal/cost.Summary
- Direction
- github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/cost, so a change to github.com/moezdil/siltide/internal/cost can break github.com/moezdil/siltide/internal/collect, while a change to github.com/moezdil/siltide/internal/collect can't break github.com/moezdil/siltide/internal/cost.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/collect uses a module listed above it, which is the healthy direction.
27→13 github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/events✕
- Connections
- 4 pairs of types, where a type in github.com/moezdil/siltide/internal/collect uses a type in github.com/moezdil/siltide/internal/events.
- The types involved
github.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/events.Detectorgithub.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/events.Eventgithub.com/moezdil/siltide/internal/collect.Snapshot→github.com/moezdil/siltide/internal/events.Eventgithub.com/moezdil/siltide/internal/collect.collect→github.com/moezdil/siltide/internal/events.Rule
- Direction
- github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/events, so a change to github.com/moezdil/siltide/internal/events can break github.com/moezdil/siltide/internal/collect, while a change to github.com/moezdil/siltide/internal/collect can't break github.com/moezdil/siltide/internal/events.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/collect uses a module listed above it, which is the healthy direction.
27→15 github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/history✕
- Connections
- 2 pairs of types, where a type in github.com/moezdil/siltide/internal/collect uses a type in github.com/moezdil/siltide/internal/history.
- The types involved
github.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/history.Storegithub.com/moezdil/siltide/internal/collect.collect→github.com/moezdil/siltide/internal/history.Store
- Direction
- github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/history, so a change to github.com/moezdil/siltide/internal/history can break github.com/moezdil/siltide/internal/collect, while a change to github.com/moezdil/siltide/internal/collect can't break github.com/moezdil/siltide/internal/history.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/collect uses a module listed above it, which is the healthy direction.
27→24 github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/derive✕
- Connections
- 4 pairs of types, where a type in github.com/moezdil/siltide/internal/collect uses a type in github.com/moezdil/siltide/internal/derive.
- The types involved
github.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/derive.Anomalygithub.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/derive.Trackergithub.com/moezdil/siltide/internal/collect.Snapshot→github.com/moezdil/siltide/internal/derive.Anomalygithub.com/moezdil/siltide/internal/collect.Snapshot→github.com/moezdil/siltide/internal/derive.Fleet
- Direction
- github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/derive, so a change to github.com/moezdil/siltide/internal/derive can break github.com/moezdil/siltide/internal/collect, while a change to github.com/moezdil/siltide/internal/collect can't break github.com/moezdil/siltide/internal/derive.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/collect uses a module listed above it, which is the healthy direction.
27→25 github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/notify✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/collect uses a type in github.com/moezdil/siltide/internal/notify.
- The types involved
github.com/moezdil/siltide/internal/collect.Engine→github.com/moezdil/siltide/internal/notify.Notifier
- Direction
- github.com/moezdil/siltide/internal/collect uses github.com/moezdil/siltide/internal/notify, so a change to github.com/moezdil/siltide/internal/notify can break github.com/moezdil/siltide/internal/collect, while a change to github.com/moezdil/siltide/internal/collect can't break github.com/moezdil/siltide/internal/notify.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/collect uses a module listed above it, which is the healthy direction.
28→1 github.com/moezdil/siltide uses github.com/moezdil/siltide/internal/config✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide uses a type in github.com/moezdil/siltide/internal/config.
- The types involved
github.com/moezdil/siltide.main→github.com/moezdil/siltide/internal/config.Config
- Direction
- github.com/moezdil/siltide uses github.com/moezdil/siltide/internal/config, so a change to github.com/moezdil/siltide/internal/config can break github.com/moezdil/siltide, while a change to github.com/moezdil/siltide can't break github.com/moezdil/siltide/internal/config.
- Position
- Below the diagonal: github.com/moezdil/siltide uses a module listed above it, which is the healthy direction.
28→6 github.com/moezdil/siltide uses github.com/moezdil/siltide/internal/provider✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide uses a type in github.com/moezdil/siltide/internal/provider.
- The types involved
github.com/moezdil/siltide.main→github.com/moezdil/siltide/internal/provider.Provider
- Direction
- github.com/moezdil/siltide uses github.com/moezdil/siltide/internal/provider, so a change to github.com/moezdil/siltide/internal/provider can break github.com/moezdil/siltide, while a change to github.com/moezdil/siltide can't break github.com/moezdil/siltide/internal/provider.
- Position
- Below the diagonal: github.com/moezdil/siltide uses a module listed above it, which is the healthy direction.
28→27 github.com/moezdil/siltide uses github.com/moezdil/siltide/internal/collect✕
- Connections
- 2 pairs of types, where a type in github.com/moezdil/siltide uses a type in github.com/moezdil/siltide/internal/collect.
- The types involved
github.com/moezdil/siltide.main→github.com/moezdil/siltide/internal/collect.Enginegithub.com/moezdil/siltide.main→github.com/moezdil/siltide/internal/collect.Snapshot
- Direction
- github.com/moezdil/siltide uses github.com/moezdil/siltide/internal/collect, so a change to github.com/moezdil/siltide/internal/collect can break github.com/moezdil/siltide, while a change to github.com/moezdil/siltide can't break github.com/moezdil/siltide/internal/collect.
- Position
- Below the diagonal: github.com/moezdil/siltide uses a module listed above it, which is the healthy direction.
29→2 github.com/moezdil/siltide/internal/mcp uses github.com/moezdil/siltide/internal/device✕
- Connections
- 4 pairs of types, where a type in github.com/moezdil/siltide/internal/mcp uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/mcp.mcp→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/mcp.mcp→github.com/moezdil/siltide/internal/device.Metricgithub.com/moezdil/siltide/internal/mcp.mcp→github.com/moezdil/siltide/internal/device.Metricsgithub.com/moezdil/siltide/internal/mcp.mcp→github.com/moezdil/siltide/internal/device.Process
- Direction
- github.com/moezdil/siltide/internal/mcp uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/mcp, while a change to github.com/moezdil/siltide/internal/mcp can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/mcp uses a module listed above it, which is the healthy direction.
29→13 github.com/moezdil/siltide/internal/mcp uses github.com/moezdil/siltide/internal/events✕
- Connections
- 2 pairs of types, where a type in github.com/moezdil/siltide/internal/mcp uses a type in github.com/moezdil/siltide/internal/events.
- The types involved
github.com/moezdil/siltide/internal/mcp.mcp→github.com/moezdil/siltide/internal/events.Eventgithub.com/moezdil/siltide/internal/mcp.mcp→github.com/moezdil/siltide/internal/events.Severity
- Direction
- github.com/moezdil/siltide/internal/mcp uses github.com/moezdil/siltide/internal/events, so a change to github.com/moezdil/siltide/internal/events can break github.com/moezdil/siltide/internal/mcp, while a change to github.com/moezdil/siltide/internal/mcp can't break github.com/moezdil/siltide/internal/events.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/mcp uses a module listed above it, which is the healthy direction.
29→27 github.com/moezdil/siltide/internal/mcp uses github.com/moezdil/siltide/internal/collect✕
- Connections
- 4 pairs of types, where a type in github.com/moezdil/siltide/internal/mcp uses a type in github.com/moezdil/siltide/internal/collect.
- The types involved
github.com/moezdil/siltide/internal/mcp.Server→github.com/moezdil/siltide/internal/collect.Enginegithub.com/moezdil/siltide/internal/mcp.Server→github.com/moezdil/siltide/internal/collect.Snapshotgithub.com/moezdil/siltide/internal/mcp.mcp→github.com/moezdil/siltide/internal/collect.Enginegithub.com/moezdil/siltide/internal/mcp.mcp→github.com/moezdil/siltide/internal/collect.Snapshot
- Direction
- github.com/moezdil/siltide/internal/mcp uses github.com/moezdil/siltide/internal/collect, so a change to github.com/moezdil/siltide/internal/collect can break github.com/moezdil/siltide/internal/mcp, while a change to github.com/moezdil/siltide/internal/mcp can't break github.com/moezdil/siltide/internal/collect.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/mcp uses a module listed above it, which is the healthy direction.
30→27 github.com/moezdil/siltide/internal/server uses github.com/moezdil/siltide/internal/collect✕
- Connections
- 2 pairs of types, where a type in github.com/moezdil/siltide/internal/server uses a type in github.com/moezdil/siltide/internal/collect.
- The types involved
github.com/moezdil/siltide/internal/server.server→github.com/moezdil/siltide/internal/collect.Enginegithub.com/moezdil/siltide/internal/server.server→github.com/moezdil/siltide/internal/collect.Snapshot
- Direction
- github.com/moezdil/siltide/internal/server uses github.com/moezdil/siltide/internal/collect, so a change to github.com/moezdil/siltide/internal/collect can break github.com/moezdil/siltide/internal/server, while a change to github.com/moezdil/siltide/internal/server can't break github.com/moezdil/siltide/internal/collect.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/server uses a module listed above it, which is the healthy direction.
31→2 github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/device✕
- Connections
- 12 pairs of types, where a type in github.com/moezdil/siltide/internal/tui uses a type in github.com/moezdil/siltide/internal/device.
- The types involved
github.com/moezdil/siltide/internal/tui.Model→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/tui.Model→github.com/moezdil/siltide/internal/device.Metricgithub.com/moezdil/siltide/internal/tui.Model→github.com/moezdil/siltide/internal/device.Processgithub.com/moezdil/siltide/internal/tui.Theme→github.com/moezdil/siltide/internal/device.Metricgithub.com/moezdil/siltide/internal/tui.Theme→github.com/moezdil/siltide/internal/device.Metricsgithub.com/moezdil/siltide/internal/tui.nodeRow→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/tui.procRow→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/tui.procRow→github.com/moezdil/siltide/internal/device.Processgithub.com/moezdil/siltide/internal/tui.tui→github.com/moezdil/siltide/internal/device.Devicegithub.com/moezdil/siltide/internal/tui.tui→github.com/moezdil/siltide/internal/device.Metricgithub.com/moezdil/siltide/internal/tui.tui→github.com/moezdil/siltide/internal/device.Metricsgithub.com/moezdil/siltide/internal/tui.tui→github.com/moezdil/siltide/internal/device.Process
- Direction
- github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/device, so a change to github.com/moezdil/siltide/internal/device can break github.com/moezdil/siltide/internal/tui, while a change to github.com/moezdil/siltide/internal/tui can't break github.com/moezdil/siltide/internal/device.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/tui uses a module listed above it, which is the healthy direction.
31→3 github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/host✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/tui uses a type in github.com/moezdil/siltide/internal/host.
- The types involved
github.com/moezdil/siltide/internal/tui.Model→github.com/moezdil/siltide/internal/host.Stats
- Direction
- github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/host, so a change to github.com/moezdil/siltide/internal/host can break github.com/moezdil/siltide/internal/tui, while a change to github.com/moezdil/siltide/internal/tui can't break github.com/moezdil/siltide/internal/host.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/tui uses a module listed above it, which is the healthy direction.
31→4 github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/kube✕
- Connections
- 3 pairs of types, where a type in github.com/moezdil/siltide/internal/tui uses a type in github.com/moezdil/siltide/internal/kube.
- The types involved
github.com/moezdil/siltide/internal/tui.Model→github.com/moezdil/siltide/internal/kube.Attemptgithub.com/moezdil/siltide/internal/tui.Model→github.com/moezdil/siltide/internal/kube.NodeResourcegithub.com/moezdil/siltide/internal/tui.tui→github.com/moezdil/siltide/internal/kube.NodeResource
- Direction
- github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/kube, so a change to github.com/moezdil/siltide/internal/kube can break github.com/moezdil/siltide/internal/tui, while a change to github.com/moezdil/siltide/internal/tui can't break github.com/moezdil/siltide/internal/kube.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/tui uses a module listed above it, which is the healthy direction.
31→13 github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/events✕
- Connections
- 3 pairs of types, where a type in github.com/moezdil/siltide/internal/tui uses a type in github.com/moezdil/siltide/internal/events.
- The types involved
github.com/moezdil/siltide/internal/tui.Model→github.com/moezdil/siltide/internal/events.Eventgithub.com/moezdil/siltide/internal/tui.tui→github.com/moezdil/siltide/internal/events.Eventgithub.com/moezdil/siltide/internal/tui.tui→github.com/moezdil/siltide/internal/events.Severity
- Direction
- github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/events, so a change to github.com/moezdil/siltide/internal/events can break github.com/moezdil/siltide/internal/tui, while a change to github.com/moezdil/siltide/internal/tui can't break github.com/moezdil/siltide/internal/events.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/tui uses a module listed above it, which is the healthy direction.
31→15 github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/history✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/internal/tui uses a type in github.com/moezdil/siltide/internal/history.
- The types involved
github.com/moezdil/siltide/internal/tui.tui→github.com/moezdil/siltide/internal/history.Store
- Direction
- github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/history, so a change to github.com/moezdil/siltide/internal/history can break github.com/moezdil/siltide/internal/tui, while a change to github.com/moezdil/siltide/internal/tui can't break github.com/moezdil/siltide/internal/history.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/tui uses a module listed above it, which is the healthy direction.
31→26 github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/query✕
- Connections
- 2 pairs of types, where a type in github.com/moezdil/siltide/internal/tui uses a type in github.com/moezdil/siltide/internal/query.
- The types involved
github.com/moezdil/siltide/internal/tui.Model→github.com/moezdil/siltide/internal/query.Filtergithub.com/moezdil/siltide/internal/tui.tui→github.com/moezdil/siltide/internal/query.Filter
- Direction
- github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/query, so a change to github.com/moezdil/siltide/internal/query can break github.com/moezdil/siltide/internal/tui, while a change to github.com/moezdil/siltide/internal/tui can't break github.com/moezdil/siltide/internal/query.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/tui uses a module listed above it, which is the healthy direction.
31→27 github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/collect✕
- Connections
- 4 pairs of types, where a type in github.com/moezdil/siltide/internal/tui uses a type in github.com/moezdil/siltide/internal/collect.
- The types involved
github.com/moezdil/siltide/internal/tui.Model→github.com/moezdil/siltide/internal/collect.Enginegithub.com/moezdil/siltide/internal/tui.Model→github.com/moezdil/siltide/internal/collect.Snapshotgithub.com/moezdil/siltide/internal/tui.tui→github.com/moezdil/siltide/internal/collect.Enginegithub.com/moezdil/siltide/internal/tui.tui→github.com/moezdil/siltide/internal/collect.Snapshot
- Direction
- github.com/moezdil/siltide/internal/tui uses github.com/moezdil/siltide/internal/collect, so a change to github.com/moezdil/siltide/internal/collect can break github.com/moezdil/siltide/internal/tui, while a change to github.com/moezdil/siltide/internal/tui can't break github.com/moezdil/siltide/internal/collect.
- Position
- Below the diagonal: github.com/moezdil/siltide/internal/tui uses a module listed above it, which is the healthy direction.
32→27 github.com/moezdil/siltide/scripts/shots uses github.com/moezdil/siltide/internal/collect✕
- Connections
- 1 pair of types, where a type in github.com/moezdil/siltide/scripts/shots uses a type in github.com/moezdil/siltide/internal/collect.
- The types involved
github.com/moezdil/siltide/scripts/shots.main→github.com/moezdil/siltide/internal/collect.Engine
- Direction
- github.com/moezdil/siltide/scripts/shots uses github.com/moezdil/siltide/internal/collect, so a change to github.com/moezdil/siltide/internal/collect can break github.com/moezdil/siltide/scripts/shots, while a change to github.com/moezdil/siltide/scripts/shots can't break github.com/moezdil/siltide/internal/collect.
- Position
- Below the diagonal: github.com/moezdil/siltide/scripts/shots uses a module listed above it, which is the healthy direction.
32→31 github.com/moezdil/siltide/scripts/shots uses github.com/moezdil/siltide/internal/tui✕
- Connections
- 2 pairs of types, where a type in github.com/moezdil/siltide/scripts/shots uses a type in github.com/moezdil/siltide/internal/tui.
- The types involved
github.com/moezdil/siltide/scripts/shots.main→github.com/moezdil/siltide/internal/tui.Modelgithub.com/moezdil/siltide/scripts/shots.main→github.com/moezdil/siltide/internal/tui.Theme
- Direction
- github.com/moezdil/siltide/scripts/shots uses github.com/moezdil/siltide/internal/tui, so a change to github.com/moezdil/siltide/internal/tui can break github.com/moezdil/siltide/scripts/shots, while a change to github.com/moezdil/siltide/scripts/shots can't break github.com/moezdil/siltide/internal/tui.
- Position
- Below the diagonal: github.com/moezdil/siltide/scripts/shots uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 35 | High / Critical |
| A05:2025 — Injection | 10 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | Medium |
Roadmap
Top priorities: Resolve the 1 finding(s) in DR & Backup; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with cli.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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with cli.go. | +2.9 pts | Low | ADR Quality |
| Resolve the 1 finding(s) in DR & Backup. | +3.7 pts | Medium | DR & Backup |
| 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. | +2.4 pts | Medium | Architecture documentation |
| Discarded error (assigned to `_`, then its result used) | +2.1 pts | Medium | Exception handling |
| Wire the existing health endpoints into readiness/liveness probes and a rolling-update (or blue/green) strategy in the deployment manifests — or document where that wiring lives — so a bad release is caught and rolled back automatically. | +1.7 pts | Medium | Deployment & Rollback |
| Resolve the 12 Low coverage finding(s) in Code Coverage — start with main.go (3), cli.go, apple.go. | +0.8 pts | Medium | Code Coverage |
| Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with main.main (cognitive 108), nvidia.read (cognitive 89). | +0.7 pts | Medium | Cognitive Complexity |
| Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with main.main (cyclomatic 80). | +0.5 pts | Medium | Cyclomatic Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| cli.go | 5.8 | Mixed | Cyclomatic Complexity: main.diagnose (cyclomatic 20) |
| main.go | 5.9 | Mixed | Cyclomatic Complexity: main.main (cyclomatic 80) |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| internal/tui/tui.go | 7.0 | Near-clean | Cyclomatic Complexity: Model.key (cyclomatic 53) |
| internal/tui/views2.go | 7.0 | Near-clean | Cyclomatic Complexity: Model.viewCompare (cyclomatic 30) |
| internal/config/config.go | 7.0 | Near-clean | Cyclomatic Complexity: Config.Validate (cyclomatic 16) |
| internal/provider/dcgm/dcgm.go | 7.0 | Near-clean | Cognitive Complexity: dcgm.Parse (cognitive 22) |
| internal/provider/remote/remote.go | 7.0 | Near-clean | Cognitive Complexity: remote.Provider (cognitive 17) |
| internal/provider/nvidia/nvml_linux.go | 7.0 | Near-clean | Cyclomatic Complexity: nvidia.read (cyclomatic 47) |
| internal/kube/kube.go | 7.0 | Near-clean | Cyclomatic Complexity: Resolver.fromKubeconfig (cyclomatic 20) |
| internal/tui/views.go | 7.0 | Near-clean | Cyclomatic Complexity: Model.detail (cyclomatic 30) |
| internal/collect/collect.go | 7.0 | Near-clean | Cyclomatic Complexity: Engine.enrich (cyclomatic 26) |
| internal/tui/views3.go | 7.1 | Near-clean | Cyclomatic Complexity: Model.topologyMatrix (cyclomatic 23) |
| internal/events/events.go | 7.2 | Near-clean | Cyclomatic Complexity: Detector.rules (cyclomatic 28) |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
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 47 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 47 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, 233 of 255 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
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 147 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- 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.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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)` (16044 LoC, 106 module-visible types across 32 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.
- 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, Scala, Rust and Java source only, and this repository's Go is most of its product and 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, Scala and Rust source only, and this repository's Go is most of its product and 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.
- 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.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin 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.
- 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.
- X3 Exception handling — 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. 20 further occurrence(s) are not listed individually; the score already reflects all 60.
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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — 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.
- 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.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
34 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was main.main at 80. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being main.manPage at 17 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with main.main (cyclomatic 80). — Refactoring it lifts Cyclomatic Complexity from 3.7 to about 4.4/10.
D2 · Cognitive Complexity
59 method(s) exceeded the cognitive complexity threshold of 15; the worst was main.main at 108.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with main.main (cognitive 108), nvidia.read (cognitive 89). — 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 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
9 god class(es) detected.
What to do
- Resolve the 3 FileTooLong finding(s) in God Classes — start with tui.go, views.go, views2.go. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 TooManyFields finding(s) in God Classes — start with tui.go, collect.go. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with tui.go. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
3 duplicated block group(s) detected. 1.4 % of the production lines (226 of 15,831) are in a reported copy. A further 7 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 10 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with format.go, collect.go. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication — start with biren.go. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with kube.go. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 21 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with config.go. — One of this dimension's main actionable groups (1 warning-level).
D8 · Code Coverage
Line coverage 69.8% — 12 file(s) below 50%. Measured from the Go suite (github.com/moezdil/siltide: `go test -coverprofile -coverpkg=./...`, the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
What to do
- Resolve the 12 Low coverage finding(s) in Code Coverage — start with main.go (3), cli.go, apple.go. — One of this dimension's main actionable groups (12 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Go (github.com/moezdil/siltide): measured (0 flaky).
D12 · Dependency Hygiene
2 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). 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.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 21 required Go module(s) use a banned license. Licences were read per module version from the licence files pkg.go.dev detects (via api.deps.dev), over every module this repository's REDACTED requires, direct and indirect, at the version the build uses. Go records no test-only scope at module level, so modules only this repository's own tests import are included. 1 of them carry no licence file that matches a known SPDX licence; that is missing data, not a violation, and none of them is charged.
D15 · Churn × Complexity Hotspots
Top hotspots: main.go (11×80=880); internal/tui/views.go (17×30=510); internal/tui/tui.go (11×34=374)
What to do
- Resolve the 9 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.go (2), views.go, tui.go. — One of this dimension's main actionable groups (9 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 15831 LoC (0.0/KLoC) → score 10.0. 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 9 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 cli.go. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
24 % of calls cross a namespace and 0 % go through an interface, but 66 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
12 finding(s): 0 critical, 3 high, 4 medium, 5 low. semgrep hit a parse error in 2 file(s) — `scripts/shots/film.sh` (lines 7–32), `site/download.html` (lines 84–89) — 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. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- 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 issue-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
35 finding(s): 0 critical, 9 high, 24 medium, 2 low.
What to do
- Resolve the 24 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (22), REDACTED (2). — One of this dimension's main actionable groups (24 warning-level).
- Resolve the 9 High IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 57 of the 80 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
Build pipeline generates provenance, signs artifacts and produces an SBOM.
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. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D40 · Network Egress Confinement
0/2 network-egress controls present (network policy, egress restriction).
What to do
- Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
D41 · Kernel & Syscall Confinement
0/1 workload(s) run every container under a seccomp profile; 0/1 declare an AppArmor/SELinux profile.
What to do
- Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gomod`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:12
What to do
- Dependabot is configured but does not watch `gomod` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment automation exists and the service already exposes health probe endpoints (healthz/livez/readyz or a container healthcheck), but no manifest in this repository wires them into readiness/liveness probes, a rolling-update strategy, lifecycle hooks or a migration job — a bad release is harder to detect and reverse. If that wiring lives in a separate ops/Helm repository, document the pointer here so release safety is evidenced. — REDACTED:94
What to do
- Wire the existing health endpoints into readiness/liveness probes and a rolling-update (or blue/green) strategy in the deployment manifests — or document where that wiring lives — so a bad release is caught and rolled back automatically.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
PF1 · Benchmark discipline
X2 · Cancellation propagation
- Only 3/4 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `HTTP` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — internal/update/update.go:274
What to do
- Thread a context.Context through functions that make requests, so the work stops when its caller gives up.
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
- `files` is walked by the `for … range` at line 222, and line 234 removes from (or inserts into) `files` by shifting its elements in the backing array the loop is still reading: the element after each change moves under the index the loop has already passed, so it is skipped, and the last ones are read twice. — internal/history/history.go:222
What to do
- Each finding names the two lines that cannot both stand — the `for … range` over the collection, and the change to it in the body. Confirm from those two, then pick one: build the result instead of editing the walked collection (`var kept []T` … `kept = append(kept, v)`, or `kept := s[:0]` and assign `s = kept` after the loop; `slices.DeleteFunc(s, drop)` in one call); for a worklist that must visit what it adds, loop `for len(queue) > 0` or by index (`for i := 0; i < len(s); i++`); walk a copy (`range slices.Clone(s)`, `range slices.Collect(maps.Keys(m))`) and change the original; delete only the CURRENT key (`delete(m, k)`), which the specification allows; or — where only the first match was ever meant — `break` straight after the change.
X28 · Index access outside its own emptiness guard
- This condition tests `f` for emptiness and then indexes it on a branch that test does not reach. `f[0]` is evaluated whenever the guarded half is false — which includes the case the guard exists to anticipate, `f` being empty — so an empty `f` indexes position 0 of nothing and throws. This same condition already shows the intended bracketing: `f[1]` sits INSIDE the guard. Either the guard is load-bearing, in which case this access escapes it and crashes, or `f` cannot be empty here, in which case the guard beside it is dead code — the condition is wrong under both readings. Move the parenthesis so the emptiness test brackets every access to `f`. — internal/provider/dcgm/dcgm.go:95
- `strings.Fields(string(up))[0]` takes element 0 of what `Fields` returns without checking its length, and this file tests that same result elsewhere before indexing it — the result can be nil or shorter. Here a short result panics with `index out of range`. Assign it and test `len` (or nil) first, as the other call site does. — internal/procinfo/procinfo.go:127
- `l[:strings.LastIndex(l, " ")]` uses a search that answers -1 when nothing is found directly as a bound. When the search misses, the bound is -1 and the access panics with `slice bounds out of range`. Assign the result, test it for -1, then slice (or use `strings.Cut`). — internal/history/history.go:174
What to do
- Each finding names the index access that escapes the guard and the line of the correctly bracketed access beside it. Compare the two: they differ only in where one parenthesis sits. Move it so the emptiness test brackets every access to that symbol — and if the value provably cannot be empty at this point, delete the test rather than leave a condition that guards one access and not its neighbour.
X3 · Exception handling
- `files, _ := filepath.Glob(filepath.Join(themes, "*.yaml"))` writes the call's error to `_` and then uses `files` as if the call succeeded. When `filepath.Glob` fails, `files` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `files` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — cli.go:232
- `files, _ := filepath.Glob(filepath.Join(config.ConfigDir(), "themes", "*.yaml"))` writes the call's error to `_` and then uses `files` as if the call succeeded. When `filepath.Glob` fails, `files` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `files` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — main.go:148
- `o, _ := uiOptions(cfg)` writes the call's error to `_` and then uses `o` as if the call succeeded. When `uiOptions` fails, `o` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `o` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — main.go:407
- `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. (×12) — internal/tui/bookmark.go:31, internal/tui/views2.go:835, internal/slurm/slurm.go:98, …
- `if err := yaml.Unmarshal(b, &out); 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. — internal/tui/bookmark.go:35
- `colors, _ = resolve("default", dir, 0)` writes the call's error to `_` and then uses `colors` as if the call succeeded. When `resolve` fails, `colors` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `colors` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/tui/theme.go:148
- `t, _ := LoadTheme(name, "", overrides, false)` writes the call's error to `_` and then uses `t` as if the call succeeded. When `LoadTheme` fails, `t` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `t` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/tui/theme.go:199
- `home, _ := userHome()` writes the call's error to `_` and then uses `home` as if the call succeeded. When `userHome` fails, `home` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `home` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/tui/tui.go:1199
- `b, _ = strconv.Atoi(hi)` writes the call's error to `_` and then uses `b` as if the call succeeded. When `strconv.Atoi` fails, `b` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `b` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/slurm/slurm.go:142
- `n, _ := strconv.Atoi(r.URL.Query().Get("n"))` writes the call's error to `_` and then uses `n` as if the call succeeded. When `strconv.Atoi` fails, `n` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `n` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/server/server.go:104
- `if _, err := strconv.Atoi(f0[0]); 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. — internal/provider/smi/ascend.go:57
- `card, _ := strconv.Atoi(m[1])` writes the call's error to `_` and then uses `card` as if the call succeeded. When `strconv.Atoi` fails, `card` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `card` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/provider/smi/cambricon.go:70
- `pid, _ := strconv.Atoi(m[3])` writes the call's error to `_` and then uses `pid` as if the call succeeded. When `strconv.Atoi` fails, `pid` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `pid` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/provider/smi/cambricon.go:71
- `idx, _ := strconv.Atoi(b["#"])` writes the call's error to `_` and then uses `idx` as if the call succeeded. When `strconv.Atoi` fails, `idx` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `idx` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/provider/smi/enflame.go:27
- `idx, _ := strconv.Atoi(m[1])` writes the call's error to `_` and then uses `idx` as if the call succeeded. When `strconv.Atoi` fails, `idx` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `idx` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. (×2) — internal/provider/smi/hygon.go:63, internal/provider/smi/mthreads.go:40
- `if _, err := exec.LookPath(path); 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. — internal/provider/smi/neuron.go:117
- `cands, _ = filepath.Glob(t)` writes the call's error to `_` and then uses `cands` as if the call succeeded. When `filepath.Glob` fails, `cands` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `cands` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/provider/smi/provider.go:168
- `entries, _ := os.ReadDir(root)` writes the call's error to `_` and then uses `entries` as if the call succeeded. When `os.ReadDir` fails, `entries` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `entries` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. (×2) — internal/provider/smi/sysfs.go:54, internal/provider/smi/sysfs.go:239
- `idx, _ := strconv.Atoi(strings.TrimPrefix(card, "card"))` writes the call's error to `_` and then uses `idx` as if the call succeeded. When `strconv.Atoi` fails, `idx` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `idx` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/provider/smi/sysfs.go:70
- `hw, _ := filepath.Glob(filepath.Join(dev, "hwmon", "hwmon*"))` writes the call's error to `_` and then uses `hw` as if the call succeeded. When `filepath.Glob` fails, `hw` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `hw` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/provider/smi/sysfs.go:77
- `pids, _ := os.ReadDir(proc)` writes the call's error to `_` and then uses `pids` as if the call succeeded. When `os.ReadDir` fails, `pids` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `pids` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/provider/smi/sysfs.go:140
- `if _, err := os.Stat(pciRoot); 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. — internal/provider/smi/sysfs.go:257
- `b, _ := os.ReadFile(path)` writes the call's error to `_` and then uses `b` as if the call succeeded. When `os.ReadFile` fails, `b` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `b` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/provider/smi/sysfs.go:271
- `memTotal, _ = strconv.ParseFloat(strings.TrimSpace(string(b)), 64)` writes the call's error to `_` and then uses `memTotal` as if the call succeeded. When `strconv.ParseFloat` fails, `memTotal` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `memTotal` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/provider/apple/apple.go:53
- `pid, _ := strconv.Atoi(c[1])` writes the call's error to `_` and then uses `pid` as if the call succeeded. When `strconv.Atoi` fails, `pid` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `pid` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — REDACTED:290
- `ns, _ := strconv.ParseFloat(g[1], 64)` writes the call's error to `_` and then uses `ns` as if the call succeeded. When `strconv.ParseFloat` fails, `ns` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `ns` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — REDACTED:294
- `uptime, _ := strconv.ParseFloat(strings.Fields(string(up))[0], 64)` writes the call's error to `_` and then uses `uptime` as if the call succeeded. When `strconv.ParseFloat` fails, `uptime` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `uptime` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — internal/procinfo/procinfo.go:127
What to do
- Discarded error (assigned to `_`, then its result used)
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65.9 | Adequate — gated by D1, D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 98.1 | Exemplary | Solid. |
| Maturity | 68.4 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 63.3 | Adequate — gated by P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 76.3 | Strong | Solid. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 4 check(s) recorded observations but carry no score
- AXH1 Runtime security headers — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXI1 Runtime container hardening — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility (rendered) — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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.
Not included — 68 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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 — no interface, protocol or abstract type declares an operation an implementer must write
- 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
- AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXP1 Runtime third-party data flows — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — ~4790 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.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- 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 — N/A — too few peers to establish a naming convention (2457 declarations, no unit with a dominant convention).
- 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. Aggregate roots were found in only one source directory (events), which is a layered codebase, not two contexts. 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; comments in this repository's .go source were not judged.
- 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.
- D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
- 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
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 1 value object(s)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 event-sourced shape(s) (event folds / event-recording aggregates))
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 Go aggregate(s) recording domain events (own events-slice append / raise-record))
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, 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 — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- 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 data present for 72 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 1% of this repository's production lines — go (15,831 lines), c (93 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 1% of this repository's production lines — go (15,831 lines), c (93 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Go was read, and it logs through none: the standard library's `log` takes one finished line, or it makes no log call outside its tests at all, so an assembled message there loses nothing the API could have kept (as with log4net in C#). Calls through log/slog, zap, logrus, zerolog, hclog, go-kit's log or logr would be judged.
- 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. Plain JavaScript carries no type annotations and commits no tsconfig, so it states no null-typed discipline for this check to grade: there is nothing here that switches null checking on or off, and TypeScript (or `// @ts-check`) is how a repository acquires one — advice, not a defect this card measures. 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 — 12 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 225 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Discarded error (assigned to `_`, then its result used) cli.go:232
- Discarded error (assigned to `_`, then its result used) main.go:148
- Discarded error (assigned to `_`, then its result used) main.go:407
- Discarded error (assigned to `_`, then its result used) internal/tui/theme.go:148
- Discarded error (assigned to `_`, then its result used) internal/tui/theme.go:199
- Discarded error (assigned to `_`, then its result used) internal/tui/tui.go:1199
- Discarded error (assigned to `_`, then its result used) internal/slurm/slurm.go:142
- Discarded error (assigned to `_`, then its result used) internal/server/server.go:104
- Discarded error (assigned to `_`, then its result used) internal/provider/smi/cambricon.go:70
- Discarded error (assigned to `_`, then its result used) internal/provider/smi/cambricon.go:71
- Discarded error (assigned to `_`, then its result used) internal/provider/smi/enflame.go:27
- Discarded error (assigned to `_`, then its result used) internal/provider/smi/hygon.go:63
- Discarded error (assigned to `_`, then its result used) internal/provider/smi/mthreads.go:40
- Discarded error (assigned to `_`, then its result used) internal/provider/smi/provider.go:168
- Discarded error (assigned to `_`, then its result used) internal/provider/smi/sysfs.go:54
- Discarded error (assigned to `_`, then its result used) internal/provider/smi/sysfs.go:70
- Discarded error (assigned to `_`, then its result used) internal/provider/smi/sysfs.go:77
- Discarded error (assigned to `_`, then its result used) internal/provider/smi/sysfs.go:140
- Discarded error (assigned to `_`, then its result used) internal/provider/smi/sysfs.go:239
- Discarded error (assigned to `_`, then its result used) internal/provider/smi/sysfs.go:271
- Discarded error (assigned to `_`, then its result used) internal/provider/apple/apple.go:53
- Discarded error (assigned to `_`, then its result used) REDACTED:290
- Discarded error (assigned to `_`, then its result used) REDACTED:294
- Discarded error (assigned to `_`, then its result used) internal/procinfo/procinfo.go:127
- Swallowed exception (caught, then discarded) internal/tui/bookmark.go:31
- Swallowed exception (caught, then discarded) internal/tui/bookmark.go:35
- Swallowed exception (caught, then discarded) internal/tui/views2.go:835
- Swallowed exception (caught, then discarded) internal/slurm/slurm.go:98
- Swallowed exception (caught, then discarded) internal/slurm/slurm.go:137
- Swallowed exception (caught, then discarded) internal/provider/provider.go:47
- Swallowed exception (caught, then discarded) internal/provider/smi/ascend.go:57
- Swallowed exception (caught, then discarded) internal/provider/smi/iluvatar.go:61
- Swallowed exception (caught, then discarded) internal/provider/smi/neuron.go:117
- Swallowed exception (caught, then discarded) internal/provider/smi/sysfs.go:143
- Swallowed exception (caught, then discarded) internal/provider/smi/sysfs.go:147
- Swallowed exception (caught, then discarded) internal/provider/smi/sysfs.go:257
- Swallowed exception (caught, then discarded) internal/provider/smi/sysfs.go:298
- Swallowed exception (caught, then discarded) internal/provider/nvidia/nvml_linux.go:390
- Swallowed exception (caught, then discarded) REDACTED:281
- Swallowed exception (caught, then discarded) internal/procinfo/procinfo.go:139
- Low coverage: cli.go cli.go:1
- Low coverage: internal/provider/apple/apple.go internal/provider/apple/apple.go:1
- Low coverage: internal/provider/apple/deep_other.go internal/provider/apple/deep_other.go:1
- Low coverage: internal/provider/dcgm/dcgm.go internal/provider/dcgm/dcgm.go:1
- Low coverage: internal/provider/remote/remote.go internal/provider/remote/remote.go:1
- Low coverage: internal/provider/smi/proc_linux.go internal/provider/smi/proc_linux.go:1
- Low coverage: internal/provider/sshp/sshp.go internal/provider/sshp/sshp.go:1
- Low coverage: main.go main.go:1
- Low coverage: scripts/schema/main.go scripts/schema/main.go:1
- Low coverage: scripts/shots/film.go scripts/shots/film.go:1
- Low coverage: scripts/shots/main.go scripts/shots/main.go:1
- Low coverage: scripts/shots/svg.go scripts/shots/svg.go:1
- Runtime security header not set: content-security-policy
- Runtime security header not set: cross-origin-embedder-policy
- Runtime security header not set: cross-origin-opener-policy
- Runtime security header not set: cross-origin-resource-policy
- Runtime security header not set: permissions-policy
- Runtime security header not set: referrer-policy
- Runtime security header not set: strict-transport-security
- Runtime security header not set: x-dns-prefetch-control
- Runtime security header not set: x-permitted-cross-domain-policies
- Hotspot: main.go main.go:50
- Hotspot: internal/tui/views.go internal/tui/views.go:367
- Hotspot: internal/tui/tui.go internal/tui/tui.go:616
- Hotspot: cli.go cli.go:208
- Hotspot: scripts/shots/main.go scripts/shots/main.go:60
- Hotspot: internal/tui/format.go internal/tui/format.go:259
- Hotspot: internal/collect/collect.go internal/collect/collect.go:249
- Hotspot: internal/provider/sim/sim.go internal/provider/sim/sim.go:104
- Hotspot: internal/server/server.go internal/server/server.go:212
- FileTooLong: tui/tui.go internal/tui/tui.go
- FileTooLong: tui/views.go internal/tui/views.go
- FileTooLong: tui/views2.go internal/tui/views2.go
- Index access outside its own emptiness guard internal/provider/dcgm/dcgm.go:95
- Index access outside its own emptiness guard internal/procinfo/procinfo.go:127
- Index access outside its own emptiness guard internal/history/history.go:174
- REDACTED
- REDACTED
- TooManyFields: Model internal/tui/tui.go:78
- TooManyFields: Engine internal/collect/collect.go:93
- Edited copy of a member (12 corresponding lines) internal/mcp/format.go:147
- Edited copy of a member (12 corresponding lines) internal/collect/collect.go:233
- Container process runs as root: compose-siltide-1
- WCAG 1.1.1 reproducibly failed in a rendered surface
- WCAG 1.4.3 reproducibly failed in a rendered surface
- WCAG 2.4.2 reproducibly failed in a rendered surface
- WCAG 3.1.1 reproducibly failed in a rendered surface
- WCAG 4.1.2 reproducibly failed in a rendered surface
- main.main (cyclomatic 80) main.go:50
- Model.key (cyclomatic 53) internal/tui/tui.go:339
- nvidia.read (cyclomatic 47) internal/provider/nvidia/nvml_linux.go:232
- Model.command (cyclomatic 34) internal/tui/tui.go:616
- health.Score (cyclomatic 30) internal/health/health.go:34
- Model.detail (cyclomatic 30) internal/tui/views.go:367
- Model.viewCompare (cyclomatic 30) internal/tui/views2.go:806
- Model.mouse (cyclomatic 29) internal/tui/tui.go:221
- Detector.rules (cyclomatic 28) internal/events/events.go:226
- Engine.enrich (cyclomatic 26) internal/collect/collect.go:488
- nvidia.depth (cyclomatic 25) internal/provider/nvidia/nvml_linux.go:411
- Model.viewHistory (cyclomatic 24) internal/tui/views.go:826
- smi.drmProcs (cyclomatic 23) internal/provider/smi/sysfs.go:132
- server.Prometheus (cyclomatic 23) internal/server/server.go:212
- Model.argSuggestions (cyclomatic 23) internal/tui/commands.go:64
- Model.hostDetail (cyclomatic 23) internal/tui/views2.go:189
- Model.topologyMatrix (cyclomatic 23) internal/tui/views3.go:19
- main.diagnose (cyclomatic 20) cli.go:208
- derive.Anomalies (cyclomatic 20) internal/derive/anomaly.go:30
- Resolver.fromKubeconfig (cyclomatic 20) internal/kube/kube.go:195
- Resolver.Describe (cyclomatic 19) internal/kube/kube.go:511
- Resolver.Nodes (cyclomatic 19) internal/kube/nodes.go:101
- Engine.Collect (cyclomatic 18) internal/collect/collect.go:249
- nvidia.links (cyclomatic 18) internal/provider/nvidia/nvml_linux.go:468
- nvidia.events (cyclomatic 18) internal/provider/nvidia/nvml_linux.go:547
- Filter.Device (cyclomatic 18) internal/query/filter.go:226
- Model.overlayKey (cyclomatic 18) internal/tui/tui.go:527
- smi.parseNpuSmi (cyclomatic 17) internal/provider/smi/ascend.go:30
- Model.pods (cyclomatic 17) internal/tui/views2.go:332
- Config.Validate (cyclomatic 16) internal/config/config.go:241
- derive.Summarize (cyclomatic 16) internal/derive/derive.go:113
- model.device (cyclomatic 16) internal/provider/sim/sim.go:104
- Theme.tableMarks (cyclomatic 16) internal/tui/format.go:259
- Model.reliabilityTable (cyclomatic 16) internal/tui/views3.go:91
- main.main (cognitive 108) main.go:50
- nvidia.read (cognitive 89) internal/provider/nvidia/nvml_linux.go:232
- Model.detail (cognitive 54) internal/tui/views.go:367
- Engine.enrich (cognitive 52) internal/collect/collect.go:488
- Model.mouse (cognitive 51) internal/tui/tui.go:221
- Model.viewCompare (cognitive 46) internal/tui/views2.go:806
- smi.drmProcs (cognitive 43) internal/provider/smi/sysfs.go:132
- Model.topologyMatrix (cognitive 42) internal/tui/views3.go:19
- Model.viewHistory (cognitive 38) internal/tui/views.go:826
- nvidia.links (cognitive 37) internal/provider/nvidia/nvml_linux.go:468
- Model.hostDetail (cognitive 37) internal/tui/views2.go:189
- server.Prometheus (cognitive 35) internal/server/server.go:212
- Detector.rules (cognitive 34) internal/events/events.go:226
- Model.pods (cognitive 34) internal/tui/views2.go:332
- nvidia.depth (cognitive 33) internal/provider/nvidia/nvml_linux.go:411
- main.diagnose (cognitive 32) cli.go:208
- Resolver.Nodes (cognitive 32) internal/kube/nodes.go:101
- Resolver.Describe (cognitive 31) internal/kube/kube.go:511
- Model.command (cognitive 31) internal/tui/tui.go:616
- Model.workloads (cognitive 31) internal/tui/views2.go:555
- smi.parseNpuSmi (cognitive 30) internal/provider/smi/ascend.go:30
- derive.Anomalies (cognitive 29) internal/derive/anomaly.go:30
- Resolver.fromKubeconfig (cognitive 29) internal/kube/kube.go:195
- Filter.Device (cognitive 28) internal/query/filter.go:226
- Model.argSuggestions (cognitive 28) internal/tui/commands.go:64
- Model.reliabilityTable (cognitive 27) internal/tui/views3.go:91
- smi.parseMxSmi (cognitive 26) internal/provider/smi/metax.go:32
- Engine.Collect (cognitive 24) internal/collect/collect.go:249
- health.Score (cognitive 24) internal/health/health.go:34
- Theme.tableMarks (cognitive 24) internal/tui/format.go:259
- Model.viewNodes (cognitive 23) internal/tui/views2.go:64
- Store.Record (cognitive 22) internal/history/history.go:104
- dcgm.Parse (cognitive 22) internal/provider/dcgm/dcgm.go:87
- smi.parseCnmon (cognitive 22) internal/provider/smi/cambricon.go:32
- Model.key (cognitive 22) internal/tui/tui.go:339
- Engine.trackEnergy (cognitive 21) internal/collect/collect.go:411
- Detector.Observe (cognitive 21) internal/events/events.go:185
- kube.walk (cognitive 21) internal/kube/podresources.go:182
- model.device (cognitive 21) internal/provider/sim/sim.go:104
- sim.Provider (cognitive 21) internal/provider/sim/sim.go:40
- derive.Summarize (cognitive 20) internal/derive/derive.go:113
- Resolver.Logs (cognitive 20) internal/kube/kube.go:578
- Model.viewWorkloads (cognitive 20) internal/tui/views2.go:617
- Model.viewDashboard (cognitive 20) internal/tui/views2.go:674
- kube.ParseListResponse (cognitive 19) internal/kube/podresources.go:121
- procinfo.read (cognitive 19) internal/procinfo/procinfo.go:72
- Server.ServeStdio (cognitive 18) internal/mcp/transport.go:27
- remote.Provider (cognitive 17) internal/provider/remote/remote.go:31
- smi.loadPCINames (cognitive 17) internal/provider/smi/sysfs.go:293
- Model.viewHealth (cognitive 17) internal/tui/views2.go:742
- host.rates (cognitive 16) internal/host/host.go:193
- kube.convert (cognitive 16) internal/kube/kube.go:452
- nvidia.events (cognitive 16) internal/provider/nvidia/nvml_linux.go:547
- neuron.read (cognitive 16) internal/provider/smi/neuron.go:73
- neuron.apply (cognitive 16) internal/provider/smi/neuron.go:145
- tui.NewKeymap (cognitive 16) internal/tui/keys.go:76
- tui.ExportCSV (cognitive 16) internal/tui/views3.go:147
- Model.typing (cognitive 16) internal/tui/tui.go:569
- Model.viewOverview (cognitive 16) internal/tui/views.go:93
- REDACTED
- REDACTED
- TooManyMethods: Model internal/tui/tui.go:78
- FunctionTooLong: main.main main.go:50
- ClassTooLong: Model internal/tui/tui.go:78
- MethodTooLong: Model.key internal/tui/tui.go:339
- REDACTED
- REDACTED
- Edited copy of a member (21 corresponding lines) internal/provider/smi/biren.go:25
- Edited copy of a member (11 corresponding lines) internal/kube/kube.go:657
- Edited copy of a member (13 corresponding lines) internal/history/history.go:290
- Edited copy of a member (10 corresponding lines) internal/kube/kube.go:275
- Edited copy of a member (5 corresponding lines) internal/events/events.go:395
- Duplicated block (5 lines × 2) internal/mcp/transport.go:96
- Duplicated block (8 lines × 2) internal/tui/views.go:495
- Duplicated block (16–17 lines × 2) REDACTED:19
- Low cohesion: Config (LCOM4 4) internal/config/config.go:18
- No DR/backup evidence
- Function without context.Context: HTTP internal/update/update.go:274
- Collection is structurally changed while it is being enumerated internal/history/history.go:222
Minor — 16 finding(s)
- REDACTED
- REDACTED
- REDACTED
- Silent fallback default on error internal/procinfo/procinfo.go:120
- Silent fallback default on error internal/provider/provider.go:47
- Silent fallback default on error REDACTED:108
- REDACTED
- REDACTED
- No ADRs found cli.go:1
- REDACTED
- No network policy
- No seccomp profile REDACTED:37
- No ADRs
- Dependabot does not watch gomod REDACTED:12
- No rollback/health safety REDACTED:94
- Not all functions that make a request accept a context.Context
Minor — 2 finding(s)
- Outdated: github.com/ebitengine/purego
- Outdated: go.yaml.in/yaml/v3
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-689ac6986e8e4b0aa0aa2c850be81099/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-689ac6986e8e4b0aa0aa2c850be81099/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 . | 12 | 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-5ed6394a377e4392af6b5bc622007dd8 | 1 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 35 | 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 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess. | 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-5ed6394a377e4392af6b5bc622007dd8 | 0 | artifacts/raw/osv-scanner.json |