Executive summary
ilya-zlobintsev/LACT falls short of our standard for a preview release, in part because it has pipeline tools referenced by a changeable name. It scores 58 out of 100 and is rated Adequate, and 27 of its 29 critical findings are security problems in its servers and containers and in the build pipeline.
Security and Compliance, at 49, is the weakest lens and counts most in the score. The best first steps are recording design decisions and fixing the runtime or framework that no longer gets security updates, each worth about 3 points. Raising Security and Compliance to 68 would lift the score to about 65.
Eleven settings leave the servers or containers unsafe. Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and three pipeline steps run downloads nobody checks. Correcting the unsafe settings, pinning each tool to an exact version and checking each download against a checksum would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and correcting the flagged pipeline settings would deal with the weakness in the build pipeline's configuration. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 30,799 lines, about €33,000 to rebuild.
If Security and Compliance rose from 49 to 68, the lowest score rated Strong, the score would rise from 58 to about 65.
New since the last survey: 18 findings
- Cognitive Complexity · PowerFrame::update_with_view (cognitive 17) lact-gui/src/app/pages/oc_page/power_frame.rs
- God Classes · MethodTooLong: ProfileSelector.update_with_view lact-gui/src/app/profiles.rs
- Code Duplication · Edited copy of a member (34 corresponding lines) lact-daemon/src/server/vulkan.rs
- Code Duplication · Edited copy of a member (42 corresponding lines) lact-daemon/src/server/gpu_controller/intel/drm/i915.rs
- Code Duplication · Edited copy of a member (22 corresponding lines) lact-gui/src/app/components/setting_row/boolean_control.rs
- Code Duplication · Edited copy of a member (24 corresponding lines) lact-daemon/src/server/handler.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) lact-gui/src/app/pages/oc_page/clocks_frame/mod.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) lact-cli/src/subcommands.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) lact-daemon/src/server/handler.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) lact-client/src/connection/unix.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) lact-client/src/connection/tcp.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) lact-gui/src/app/components/info_row.rs
- Code Duplication · Duplicated block (17 lines × 2) lact-daemon/src/server/gpu_controller/amd.rs
- Code Duplication · Duplicated block (14 lines × 2) lact-daemon/src/server/handler.rs
- Code Duplication · Duplicated block (14 lines × 2) lact-gui/src/app/components/setting_row/boolean_control.rs
- Churn × Complexity Hotspots · Hotspot: lact-daemon/src/server/gpu_controller/intel.rs lact-daemon/src/server/gpu_controller/intel.rs
- Explicit Debt · FixmeComment lact-gui/src/app.rs
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 6 findings
- Cyclomatic Complexity · PerformanceFrame::update_with_view (cyclomatic 16) lact-gui/src/app/pages/oc_page/performance_frame/mod.rs
- Cognitive Complexity · PerformanceFrame::update_with_view (cognitive 20) lact-gui/src/app/pages/oc_page/performance_frame/mod.rs
- God Classes · MethodTooLong: OcPage.update_with_view lact-gui/src/app/pages/oc_page.rs
- Code Duplication · Duplicated block (13 lines × 2) lact-gui/src/app/components/page_section.rs
- Churn × Complexity Hotspots · Hotspot: lact-daemon/src/server/gpu_controller/nvidia.rs lact-daemon/src/server/gpu_controller/nvidia.rs
- Explicit Debt · FixmeComment lact-gui/src/app/pages/oc_page/power_frame.rs
Rebuild cost: about €33,000 · Estimate
| Cost to rebuild | €11,000 to €54,000, for 181 to 573 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 | ×0.8 at a score of 58. 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 | Medium: 30,799 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 lact_client.connection | 2 lact_daemon.server.metrics.schema | 3 lact_gui.app.components.adjustment_row | 4 lact_gui.app.components.setting_row.select_control | 5 lact_gui.app.graphs_window.plot | 6 lact_schema | 7 lact_schema.args | 8 lact_schema.request | 9 lact_daemon.server.gpu_controller.amd.drm | 10 lact_daemon.server.gpu_controller.intel.drm | 11 lact_gui.app.components.setting_row | 12 lact_gui.app.graphs_window.stat | 13 lact_gui.app.pages.oc_page.clocks_frame | 14 lact_schema.config | 15 lact_client | 16 lact_daemon.config | 17 lact_daemon.server.gpu_controller.intel.drm.i915 | 18 lact_daemon.server.gpu_controller.intel.drm.xe | 19 lact_gui.app.graphs_window.plot.render_thread | 20 lact_gui.app.pages.oc_page | 21 lact_gui.app.pages.thermals_page | 22 lact_gui.config | 23 lact_cli | 24 lact_daemon.server.handler | 25 lact_gui.app | 26 lact_cli.subcommands | 27 lact_daemon.server | 28 lact_daemon.server.gpu_controller | 29 lact_daemon.server.gpu_controller.amd.drm.mock | 30 lact_daemon.server.gpu_controller.intel.drm.mock | 31 lact_daemon.server.metrics | 32 lact_daemon.server.profiles | 33 lact_daemon.server.gpu_controller.amd.drm.amdgpu | 34 lact_daemon.server.gpu_controller.common.fdinfo | 35 lact_daemon.server.gpu_controller.nvidia.driver | 36 lact_daemon.server.opencl | 37 lact_daemon.server.vulkan | 38 lact_daemon.server.gpu_controller.amd | 39 lact_daemon.server.gpu_controller.intel | 40 lact_daemon.server.gpu_controller.nvidia |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 lact_client.connection | ||||||||||||||||||||||||||||||||||||||||
| 2 lact_daemon.server.metrics.schema | ||||||||||||||||||||||||||||||||||||||||
| 3 lact_gui.app.components.adjustment_row | ||||||||||||||||||||||||||||||||||||||||
| 4 lact_gui.app.components.setting_row.select_control | ||||||||||||||||||||||||||||||||||||||||
| 5 lact_gui.app.graphs_window.plot | ||||||||||||||||||||||||||||||||||||||||
| 6 lact_schema | ||||||||||||||||||||||||||||||||||||||||
| 7 lact_schema.args | ||||||||||||||||||||||||||||||||||||||||
| 8 lact_schema.request | ||||||||||||||||||||||||||||||||||||||||
| 9 lact_daemon.server.gpu_controller.amd.drm | 4 | |||||||||||||||||||||||||||||||||||||||
| 10 lact_daemon.server.gpu_controller.intel.drm | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 lact_gui.app.components.setting_row | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 lact_gui.app.graphs_window.stat | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 lact_gui.app.pages.oc_page.clocks_frame | 3 | 4 | ||||||||||||||||||||||||||||||||||||||
| 14 lact_schema.config | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 lact_client | 1 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 16 lact_daemon.config | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 lact_daemon.server.gpu_controller.intel.drm.i915 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 lact_daemon.server.gpu_controller.intel.drm.xe | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 lact_gui.app.graphs_window.plot.render_thread | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 lact_gui.app.pages.oc_page | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 21 lact_gui.app.pages.thermals_page | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 lact_gui.config | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 lact_cli | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 lact_daemon.server.handler | 10 | 3 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 25 lact_gui.app | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 lact_cli.subcommands | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 lact_daemon.server | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 28 lact_daemon.server.gpu_controller | 6 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 lact_daemon.server.gpu_controller.amd.drm.mock | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 lact_daemon.server.gpu_controller.intel.drm.mock | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 lact_daemon.server.metrics | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 lact_daemon.server.profiles | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 lact_daemon.server.gpu_controller.amd.drm.amdgpu | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 lact_daemon.server.gpu_controller.common.fdinfo | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 lact_daemon.server.gpu_controller.nvidia.driver | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 lact_daemon.server.opencl | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 lact_daemon.server.vulkan | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 38 lact_daemon.server.gpu_controller.amd | 8 | 4 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 lact_daemon.server.gpu_controller.intel | 4 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 lact_daemon.server.gpu_controller.nvidia | 6 | 3 | 2 | 1 |
9→6 lact_daemon.server.gpu_controller.amd.drm uses lact_schema✕
- Connections
- 4 pairs of types, where a type in lact_daemon.server.gpu_controller.amd.drm uses a type in lact_schema.
- The types involved
lact_daemon.server.gpu_controller.amd.drm.DrmProvider→lact_schema.AmdUmaCarveoutlact_daemon.server.gpu_controller.amd.drm.DrmProvider→lact_schema.CacheInfolact_daemon.server.gpu_controller.amd.drm.DrmProvider→lact_schema.DeviceTypelact_daemon.server.gpu_controller.amd.drm.DrmProvider→lact_schema.DrmInfo
- Direction
- lact_daemon.server.gpu_controller.amd.drm uses lact_schema, so a change to lact_schema can break lact_daemon.server.gpu_controller.amd.drm, while a change to lact_daemon.server.gpu_controller.amd.drm can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.amd.drm uses a module listed above it, which is the healthy direction.
10→6 lact_daemon.server.gpu_controller.intel.drm uses lact_schema✕
- Connections
- 2 pairs of types, where a type in lact_daemon.server.gpu_controller.intel.drm uses a type in lact_schema.
- The types involved
lact_daemon.server.gpu_controller.intel.drm.DrmProvider→lact_schema.IntelDrmInfolact_daemon.server.gpu_controller.intel.drm.VramInfo→lact_schema.DrmMemoryInfo
- Direction
- lact_daemon.server.gpu_controller.intel.drm uses lact_schema, so a change to lact_schema can break lact_daemon.server.gpu_controller.intel.drm, while a change to lact_daemon.server.gpu_controller.intel.drm can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel.drm uses a module listed above it, which is the healthy direction.
11→4 lact_gui.app.components.setting_row uses lact_gui.app.components.setting_row.select_control✕
- Connections
- 1 pair of types, where a type in lact_gui.app.components.setting_row uses a type in lact_gui.app.components.setting_row.select_control.
- The types involved
lact_gui.app.components.setting_row.SettingControlInit→lact_gui.app.components.setting_row.select_control.SelectInit
- Direction
- lact_gui.app.components.setting_row uses lact_gui.app.components.setting_row.select_control, so a change to lact_gui.app.components.setting_row.select_control can break lact_gui.app.components.setting_row, while a change to lact_gui.app.components.setting_row can't break lact_gui.app.components.setting_row.select_control.
- Position
- Below the diagonal: lact_gui.app.components.setting_row uses a module listed above it, which is the healthy direction.
12→6 lact_gui.app.graphs_window.stat uses lact_schema✕
- Connections
- 1 pair of types, where a type in lact_gui.app.graphs_window.stat uses a type in lact_schema.
- The types involved
lact_gui.app.graphs_window.stat.StatsData→lact_schema.DeviceStats
- Direction
- lact_gui.app.graphs_window.stat uses lact_schema, so a change to lact_schema can break lact_gui.app.graphs_window.stat, while a change to lact_gui.app.graphs_window.stat can't break lact_schema.
- Position
- Below the diagonal: lact_gui.app.graphs_window.stat uses a module listed above it, which is the healthy direction.
13→6 lact_gui.app.pages.oc_page.clocks_frame uses lact_schema✕
- Connections
- 3 pairs of types, where a type in lact_gui.app.pages.oc_page.clocks_frame uses a type in lact_schema.
- The types involved
lact_gui.app.pages.oc_page.clocks_frame.ClocksFrame→lact_schema.IntelClocksTablelact_gui.app.pages.oc_page.clocks_frame.ClocksFrame→lact_schema.NvidiaClocksTablelact_gui.app.pages.oc_page.clocks_frame.clocks_frame$module→lact_schema.NvidiaClockOffset
- Direction
- lact_gui.app.pages.oc_page.clocks_frame uses lact_schema, so a change to lact_schema can break lact_gui.app.pages.oc_page.clocks_frame, while a change to lact_gui.app.pages.oc_page.clocks_frame can't break lact_schema.
- Position
- Below the diagonal: lact_gui.app.pages.oc_page.clocks_frame uses a module listed above it, which is the healthy direction.
13→8 lact_gui.app.pages.oc_page.clocks_frame uses lact_schema.request✕
- Connections
- 4 pairs of types, where a type in lact_gui.app.pages.oc_page.clocks_frame uses a type in lact_schema.request.
- The types involved
lact_gui.app.pages.oc_page.clocks_frame.ClockDomain→lact_schema.request.ClockspeedTypelact_gui.app.pages.oc_page.clocks_frame.ClocksFrame→lact_schema.request.ClockspeedTypelact_gui.app.pages.oc_page.clocks_frame.ClocksFrame→lact_schema.request.SetClocksCommandlact_gui.app.pages.oc_page.clocks_frame.clocks_frame$module→lact_schema.request.ClockspeedType
- Direction
- lact_gui.app.pages.oc_page.clocks_frame uses lact_schema.request, so a change to lact_schema.request can break lact_gui.app.pages.oc_page.clocks_frame, while a change to lact_gui.app.pages.oc_page.clocks_frame can't break lact_schema.request.
- Position
- Below the diagonal: lact_gui.app.pages.oc_page.clocks_frame uses a module listed above it, which is the healthy direction.
14→6 lact_schema.config uses lact_schema✕
- Connections
- 4 pairs of types, where a type in lact_schema.config uses a type in lact_schema.
- The types involved
lact_schema.config.FanControlSettings→lact_schema.FanControlModelact_schema.config.GpuConfig→lact_schema.NvidiaThermalOptionslact_schema.config.GpuConfig→lact_schema.PmfwOptionslact_schema.config.Profile→lact_schema.ProfileRule
- Direction
- lact_schema.config uses lact_schema, so a change to lact_schema can break lact_schema.config, while a change to lact_schema.config can't break lact_schema.
- Position
- Below the diagonal: lact_schema.config uses a module listed above it, which is the healthy direction.
14→8 lact_schema.config uses lact_schema.request✕
- Connections
- 1 pair of types, where a type in lact_schema.config uses a type in lact_schema.request.
- The types involved
lact_schema.config.ClocksConfiguration→lact_schema.request.SetClocksCommand
- Direction
- lact_schema.config uses lact_schema.request, so a change to lact_schema.request can break lact_schema.config, while a change to lact_schema.config can't break lact_schema.request.
- Position
- Below the diagonal: lact_schema.config uses a module listed above it, which is the healthy direction.
15→6 lact_client uses lact_schema✕
- Connections
- 1 pair of types, where a type in lact_client uses a type in lact_schema.
- The types involved
lact_client.DaemonClient→lact_schema.ProfileRule
- Direction
- lact_client uses lact_schema, so a change to lact_schema can break lact_client, while a change to lact_client can't break lact_schema.
- Position
- Below the diagonal: lact_client uses a module listed above it, which is the healthy direction.
15→8 lact_client uses lact_schema.request✕
- Connections
- 4 pairs of types, where a type in lact_client uses a type in lact_schema.request.
- The types involved
lact_client.DaemonClient→lact_schema.request.ConfirmCommandlact_client.DaemonClient→lact_schema.request.ProfileBaselact_client.DaemonClient→lact_schema.request.Requestlact_client.DaemonClient→lact_schema.request.SetClocksCommand
- Direction
- lact_client uses lact_schema.request, so a change to lact_schema.request can break lact_client, while a change to lact_client can't break lact_schema.request.
- Position
- Below the diagonal: lact_client uses a module listed above it, which is the healthy direction.
15→14 lact_client uses lact_schema.config✕
- Connections
- 2 pairs of types, where a type in lact_client uses a type in lact_schema.config.
- The types involved
lact_client.DaemonClient→lact_schema.config.GpuConfiglact_client.DaemonClient→lact_schema.config.ProfileHooks
- Direction
- lact_client uses lact_schema.config, so a change to lact_schema.config can break lact_client, while a change to lact_client can't break lact_schema.config.
- Position
- Below the diagonal: lact_client uses a module listed above it, which is the healthy direction.
16→14 lact_daemon.config uses lact_schema.config✕
- Connections
- 1 pair of types, where a type in lact_daemon.config uses a type in lact_schema.config.
- The types involved
lact_daemon.config.Config→lact_schema.config.Profile
- Direction
- lact_daemon.config uses lact_schema.config, so a change to lact_schema.config can break lact_daemon.config, while a change to lact_daemon.config can't break lact_schema.config.
- Position
- Below the diagonal: lact_daemon.config uses a module listed above it, which is the healthy direction.
17→6 lact_daemon.server.gpu_controller.intel.drm.i915 uses lact_schema✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.intel.drm.i915 uses a type in lact_schema.
- The types involved
lact_daemon.server.gpu_controller.intel.drm.i915.I915DrmProvider→lact_schema.IntelDrmInfo
- Direction
- lact_daemon.server.gpu_controller.intel.drm.i915 uses lact_schema, so a change to lact_schema can break lact_daemon.server.gpu_controller.intel.drm.i915, while a change to lact_daemon.server.gpu_controller.intel.drm.i915 can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel.drm.i915 uses a module listed above it, which is the healthy direction.
17→9 lact_daemon.server.gpu_controller.intel.drm.i915 uses lact_daemon.server.gpu_controller.amd.drm✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.intel.drm.i915 uses a type in lact_daemon.server.gpu_controller.amd.drm.
- The types involved
lact_daemon.server.gpu_controller.intel.drm.i915.I915DrmProvider→lact_daemon.server.gpu_controller.amd.drm.DrmProvider
- Direction
- lact_daemon.server.gpu_controller.intel.drm.i915 uses lact_daemon.server.gpu_controller.amd.drm, so a change to lact_daemon.server.gpu_controller.amd.drm can break lact_daemon.server.gpu_controller.intel.drm.i915, while a change to lact_daemon.server.gpu_controller.intel.drm.i915 can't break lact_daemon.server.gpu_controller.amd.drm.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel.drm.i915 uses a module listed above it, which is the healthy direction.
17→10 lact_daemon.server.gpu_controller.intel.drm.i915 uses lact_daemon.server.gpu_controller.intel.drm✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.intel.drm.i915 uses a type in lact_daemon.server.gpu_controller.intel.drm.
- The types involved
lact_daemon.server.gpu_controller.intel.drm.i915.I915DrmProvider→lact_daemon.server.gpu_controller.intel.drm.VramInfo
- Direction
- lact_daemon.server.gpu_controller.intel.drm.i915 uses lact_daemon.server.gpu_controller.intel.drm, so a change to lact_daemon.server.gpu_controller.intel.drm can break lact_daemon.server.gpu_controller.intel.drm.i915, while a change to lact_daemon.server.gpu_controller.intel.drm.i915 can't break lact_daemon.server.gpu_controller.intel.drm.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel.drm.i915 uses a module listed above it, which is the healthy direction.
18→6 lact_daemon.server.gpu_controller.intel.drm.xe uses lact_schema✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.intel.drm.xe uses a type in lact_schema.
- The types involved
lact_daemon.server.gpu_controller.intel.drm.xe.XeDrmProvider→lact_schema.IntelDrmInfo
- Direction
- lact_daemon.server.gpu_controller.intel.drm.xe uses lact_schema, so a change to lact_schema can break lact_daemon.server.gpu_controller.intel.drm.xe, while a change to lact_daemon.server.gpu_controller.intel.drm.xe can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel.drm.xe uses a module listed above it, which is the healthy direction.
18→9 lact_daemon.server.gpu_controller.intel.drm.xe uses lact_daemon.server.gpu_controller.amd.drm✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.intel.drm.xe uses a type in lact_daemon.server.gpu_controller.amd.drm.
- The types involved
lact_daemon.server.gpu_controller.intel.drm.xe.XeDrmProvider→lact_daemon.server.gpu_controller.amd.drm.DrmProvider
- Direction
- lact_daemon.server.gpu_controller.intel.drm.xe uses lact_daemon.server.gpu_controller.amd.drm, so a change to lact_daemon.server.gpu_controller.amd.drm can break lact_daemon.server.gpu_controller.intel.drm.xe, while a change to lact_daemon.server.gpu_controller.intel.drm.xe can't break lact_daemon.server.gpu_controller.amd.drm.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel.drm.xe uses a module listed above it, which is the healthy direction.
18→10 lact_daemon.server.gpu_controller.intel.drm.xe uses lact_daemon.server.gpu_controller.intel.drm✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.intel.drm.xe uses a type in lact_daemon.server.gpu_controller.intel.drm.
- The types involved
lact_daemon.server.gpu_controller.intel.drm.xe.XeDrmProvider→lact_daemon.server.gpu_controller.intel.drm.VramInfo
- Direction
- lact_daemon.server.gpu_controller.intel.drm.xe uses lact_daemon.server.gpu_controller.intel.drm, so a change to lact_daemon.server.gpu_controller.intel.drm can break lact_daemon.server.gpu_controller.intel.drm.xe, while a change to lact_daemon.server.gpu_controller.intel.drm.xe can't break lact_daemon.server.gpu_controller.intel.drm.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel.drm.xe uses a module listed above it, which is the healthy direction.
19→5 lact_gui.app.graphs_window.plot.render_thread uses lact_gui.app.graphs_window.plot✕
- Connections
- 1 pair of types, where a type in lact_gui.app.graphs_window.plot.render_thread uses a type in lact_gui.app.graphs_window.plot.
- The types involved
lact_gui.app.graphs_window.plot.render_thread.RenderRequest→lact_gui.app.graphs_window.plot.PlotColorScheme
- Direction
- lact_gui.app.graphs_window.plot.render_thread uses lact_gui.app.graphs_window.plot, so a change to lact_gui.app.graphs_window.plot can break lact_gui.app.graphs_window.plot.render_thread, while a change to lact_gui.app.graphs_window.plot.render_thread can't break lact_gui.app.graphs_window.plot.
- Position
- Below the diagonal: lact_gui.app.graphs_window.plot.render_thread uses a module listed above it, which is the healthy direction.
19→12 lact_gui.app.graphs_window.plot.render_thread uses lact_gui.app.graphs_window.stat✕
- Connections
- 2 pairs of types, where a type in lact_gui.app.graphs_window.plot.render_thread uses a type in lact_gui.app.graphs_window.stat.
- The types involved
lact_gui.app.graphs_window.plot.render_thread.RenderRequest→lact_gui.app.graphs_window.stat.StatTypelact_gui.app.graphs_window.plot.render_thread.RenderRequest→lact_gui.app.graphs_window.stat.StatsData
- Direction
- lact_gui.app.graphs_window.plot.render_thread uses lact_gui.app.graphs_window.stat, so a change to lact_gui.app.graphs_window.stat can break lact_gui.app.graphs_window.plot.render_thread, while a change to lact_gui.app.graphs_window.plot.render_thread can't break lact_gui.app.graphs_window.stat.
- Position
- Below the diagonal: lact_gui.app.graphs_window.plot.render_thread uses a module listed above it, which is the healthy direction.
20→6 lact_gui.app.pages.oc_page uses lact_schema✕
- Connections
- 1 pair of types, where a type in lact_gui.app.pages.oc_page uses a type in lact_schema.
- The types involved
lact_gui.app.pages.oc_page.OcPage→lact_schema.DeviceInfo
- Direction
- lact_gui.app.pages.oc_page uses lact_schema, so a change to lact_schema can break lact_gui.app.pages.oc_page, while a change to lact_gui.app.pages.oc_page can't break lact_schema.
- Position
- Below the diagonal: lact_gui.app.pages.oc_page uses a module listed above it, which is the healthy direction.
20→14 lact_gui.app.pages.oc_page uses lact_schema.config✕
- Connections
- 3 pairs of types, where a type in lact_gui.app.pages.oc_page uses a type in lact_schema.config.
- The types involved
lact_gui.app.pages.oc_page.OcPage→lact_schema.config.ClocksConfigurationlact_gui.app.pages.oc_page.OcPage→lact_schema.config.GpuConfiglact_gui.app.pages.oc_page.OcPageSerialized→lact_schema.config.ClocksConfiguration
- Direction
- lact_gui.app.pages.oc_page uses lact_schema.config, so a change to lact_schema.config can break lact_gui.app.pages.oc_page, while a change to lact_gui.app.pages.oc_page can't break lact_schema.config.
- Position
- Below the diagonal: lact_gui.app.pages.oc_page uses a module listed above it, which is the healthy direction.
21→3 lact_gui.app.pages.thermals_page uses lact_gui.app.components.adjustment_row✕
- Connections
- 1 pair of types, where a type in lact_gui.app.pages.thermals_page uses a type in lact_gui.app.components.adjustment_row.
- The types involved
lact_gui.app.pages.thermals_page.thermals_page$module→lact_gui.app.components.adjustment_row.AdjustmentRowInit
- Direction
- lact_gui.app.pages.thermals_page uses lact_gui.app.components.adjustment_row, so a change to lact_gui.app.components.adjustment_row can break lact_gui.app.pages.thermals_page, while a change to lact_gui.app.pages.thermals_page can't break lact_gui.app.components.adjustment_row.
- Position
- Below the diagonal: lact_gui.app.pages.thermals_page uses a module listed above it, which is the healthy direction.
21→6 lact_gui.app.pages.thermals_page uses lact_schema✕
- Connections
- 1 pair of types, where a type in lact_gui.app.pages.thermals_page uses a type in lact_schema.
- The types involved
lact_gui.app.pages.thermals_page.ThermalsPage→lact_schema.FanControlMode
- Direction
- lact_gui.app.pages.thermals_page uses lact_schema, so a change to lact_schema can break lact_gui.app.pages.thermals_page, while a change to lact_gui.app.pages.thermals_page can't break lact_schema.
- Position
- Below the diagonal: lact_gui.app.pages.thermals_page uses a module listed above it, which is the healthy direction.
21→14 lact_gui.app.pages.thermals_page uses lact_schema.config✕
- Connections
- 1 pair of types, where a type in lact_gui.app.pages.thermals_page uses a type in lact_schema.config.
- The types involved
lact_gui.app.pages.thermals_page.ThermalsPage→lact_schema.config.GpuConfig
- Direction
- lact_gui.app.pages.thermals_page uses lact_schema.config, so a change to lact_schema.config can break lact_gui.app.pages.thermals_page, while a change to lact_gui.app.pages.thermals_page can't break lact_schema.config.
- Position
- Below the diagonal: lact_gui.app.pages.thermals_page uses a module listed above it, which is the healthy direction.
22→12 lact_gui.config uses lact_gui.app.graphs_window.stat✕
- Connections
- 1 pair of types, where a type in lact_gui.config uses a type in lact_gui.app.graphs_window.stat.
- The types involved
lact_gui.config.UiGpuConfig→lact_gui.app.graphs_window.stat.StatType
- Direction
- lact_gui.config uses lact_gui.app.graphs_window.stat, so a change to lact_gui.app.graphs_window.stat can break lact_gui.config, while a change to lact_gui.config can't break lact_gui.app.graphs_window.stat.
- Position
- Below the diagonal: lact_gui.config uses a module listed above it, which is the healthy direction.
23→15 lact_cli uses lact_client✕
- Connections
- 1 pair of types, where a type in lact_cli uses a type in lact_client.
- The types involved
lact_cli.CliContext→lact_client.DaemonClient
- Direction
- lact_cli uses lact_client, so a change to lact_client can break lact_cli, while a change to lact_cli can't break lact_client.
- Position
- Below the diagonal: lact_cli uses a module listed above it, which is the healthy direction.
24→6 lact_daemon.server.handler uses lact_schema✕
- Connections
- 10 pairs of types, where a type in lact_daemon.server.handler uses a type in lact_schema.
- The types involved
lact_daemon.server.handler.Handler→lact_schema.DeviceListEntrylact_daemon.server.handler.Handler→lact_schema.FanOptionslact_daemon.server.handler.Handler→lact_schema.ProfileRulelact_daemon.server.handler.Handler→lact_schema.ProfileWatcherStatelact_daemon.server.handler.Handler→lact_schema.ProfilesInfolact_daemon.server.handler.SnapshotDeviceInfo→lact_schema.ClocksInfolact_daemon.server.handler.SnapshotDeviceInfo→lact_schema.DeviceInfolact_daemon.server.handler.SnapshotDeviceInfo→lact_schema.DeviceStatslact_daemon.server.handler.SnapshotDeviceInfo→lact_schema.GpuPciInfolact_daemon.server.handler.SnapshotDeviceInfo→lact_schema.PowerStates
- Direction
- lact_daemon.server.handler uses lact_schema, so a change to lact_schema can break lact_daemon.server.handler, while a change to lact_daemon.server.handler can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.handler uses a module listed above it, which is the healthy direction.
24→8 lact_daemon.server.handler uses lact_schema.request✕
- Connections
- 3 pairs of types, where a type in lact_daemon.server.handler uses a type in lact_schema.request.
- The types involved
lact_daemon.server.handler.Handler→lact_schema.request.ConfirmCommandlact_daemon.server.handler.Handler→lact_schema.request.ProfileBaselact_daemon.server.handler.Handler→lact_schema.request.SetClocksCommand
- Direction
- lact_daemon.server.handler uses lact_schema.request, so a change to lact_schema.request can break lact_daemon.server.handler, while a change to lact_daemon.server.handler can't break lact_schema.request.
- Position
- Below the diagonal: lact_daemon.server.handler uses a module listed above it, which is the healthy direction.
24→14 lact_daemon.server.handler uses lact_schema.config✕
- Connections
- 2 pairs of types, where a type in lact_daemon.server.handler uses a type in lact_schema.config.
- The types involved
lact_daemon.server.handler.Handler→lact_schema.config.GpuConfiglact_daemon.server.handler.Handler→lact_schema.config.ProfileHooks
- Direction
- lact_daemon.server.handler uses lact_schema.config, so a change to lact_schema.config can break lact_daemon.server.handler, while a change to lact_daemon.server.handler can't break lact_schema.config.
- Position
- Below the diagonal: lact_daemon.server.handler uses a module listed above it, which is the healthy direction.
24→16 lact_daemon.server.handler uses lact_daemon.config✕
- Connections
- 2 pairs of types, where a type in lact_daemon.server.handler uses a type in lact_daemon.config.
- The types involved
lact_daemon.server.handler.Handler→lact_daemon.config.Configlact_daemon.server.handler.handler$module→lact_daemon.config.Config
- Direction
- lact_daemon.server.handler uses lact_daemon.config, so a change to lact_daemon.config can break lact_daemon.server.handler, while a change to lact_daemon.server.handler can't break lact_daemon.config.
- Position
- Below the diagonal: lact_daemon.server.handler uses a module listed above it, which is the healthy direction.
24→27 lact_daemon.server.handler uses lact_daemon.server part of a loop✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.handler uses a type in lact_daemon.server.
- The types involved
lact_daemon.server.handler.Handler→lact_daemon.server.ClientContext
- Direction
- lact_daemon.server.handler uses lact_daemon.server, so a change to lact_daemon.server can break lact_daemon.server.handler, while a change to lact_daemon.server.handler can't break lact_daemon.server.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→6 lact_gui.app uses lact_schema✕
- Connections
- 2 pairs of types, where a type in lact_gui.app uses a type in lact_schema.
- The types involved
lact_gui.app.AppModel→lact_schema.DeviceFlaglact_gui.app.AppModel→lact_schema.SystemInfo
- Direction
- lact_gui.app uses lact_schema, so a change to lact_schema can break lact_gui.app, while a change to lact_gui.app can't break lact_schema.
- Position
- Below the diagonal: lact_gui.app uses a module listed above it, which is the healthy direction.
25→15 lact_gui.app uses lact_client✕
- Connections
- 2 pairs of types, where a type in lact_gui.app uses a type in lact_client.
- The types involved
lact_gui.app.AppModel→lact_client.DaemonClientlact_gui.app.app$module→lact_client.DaemonClient
- Direction
- lact_gui.app uses lact_client, so a change to lact_client can break lact_gui.app, while a change to lact_gui.app can't break lact_client.
- Position
- Below the diagonal: lact_gui.app uses a module listed above it, which is the healthy direction.
26→23 lact_cli.subcommands uses lact_cli✕
- Connections
- 1 pair of types, where a type in lact_cli.subcommands uses a type in lact_cli.
- The types involved
lact_cli.subcommands.subcommands$module→lact_cli.CliContext
- Direction
- lact_cli.subcommands uses lact_cli, so a change to lact_cli can break lact_cli.subcommands, while a change to lact_cli.subcommands can't break lact_cli.
- Position
- Below the diagonal: lact_cli.subcommands uses a module listed above it, which is the healthy direction.
27→6 lact_daemon.server uses lact_schema✕
- Connections
- 1 pair of types, where a type in lact_daemon.server uses a type in lact_schema.
- The types involved
lact_daemon.server.server$module→lact_schema.Pong
- Direction
- lact_daemon.server uses lact_schema, so a change to lact_schema can break lact_daemon.server, while a change to lact_daemon.server can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server uses a module listed above it, which is the healthy direction.
27→8 lact_daemon.server uses lact_schema.request✕
- Connections
- 1 pair of types, where a type in lact_daemon.server uses a type in lact_schema.request.
- The types involved
lact_daemon.server.server$module→lact_schema.request.Request
- Direction
- lact_daemon.server uses lact_schema.request, so a change to lact_schema.request can break lact_daemon.server, while a change to lact_daemon.server can't break lact_schema.request.
- Position
- Below the diagonal: lact_daemon.server uses a module listed above it, which is the healthy direction.
27→16 lact_daemon.server uses lact_daemon.config✕
- Connections
- 1 pair of types, where a type in lact_daemon.server uses a type in lact_daemon.config.
- The types involved
lact_daemon.server.Server→lact_daemon.config.Config
- Direction
- lact_daemon.server uses lact_daemon.config, so a change to lact_daemon.config can break lact_daemon.server, while a change to lact_daemon.server can't break lact_daemon.config.
- Position
- Below the diagonal: lact_daemon.server uses a module listed above it, which is the healthy direction.
27→24 lact_daemon.server uses lact_daemon.server.handler✕
- Connections
- 2 pairs of types, where a type in lact_daemon.server uses a type in lact_daemon.server.handler.
- The types involved
lact_daemon.server.Server→lact_daemon.server.handler.Handlerlact_daemon.server.server$module→lact_daemon.server.handler.Handler
- Direction
- lact_daemon.server uses lact_daemon.server.handler, so a change to lact_daemon.server.handler can break lact_daemon.server, while a change to lact_daemon.server can't break lact_daemon.server.handler.
- Position
- Below the diagonal: lact_daemon.server uses a module listed above it, which is the healthy direction.
28→6 lact_daemon.server.gpu_controller uses lact_schema✕
- Connections
- 6 pairs of types, where a type in lact_daemon.server.gpu_controller uses a type in lact_schema.
- The types involved
lact_daemon.server.gpu_controller.CommonControllerInfo→lact_schema.GpuPciInfolact_daemon.server.gpu_controller.GpuController→lact_schema.DeviceStatslact_daemon.server.gpu_controller.GpuController→lact_schema.DeviceTypelact_daemon.server.gpu_controller.GpuController→lact_schema.DisplaysInfolact_daemon.server.gpu_controller.GpuController→lact_schema.PowerStateslact_daemon.server.gpu_controller.gpu_controller$module→lact_schema.GpuPciInfo
- Direction
- lact_daemon.server.gpu_controller uses lact_schema, so a change to lact_schema can break lact_daemon.server.gpu_controller, while a change to lact_daemon.server.gpu_controller can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller uses a module listed above it, which is the healthy direction.
28→14 lact_daemon.server.gpu_controller uses lact_schema.config✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller uses a type in lact_schema.config.
- The types involved
lact_daemon.server.gpu_controller.GpuController→lact_schema.config.GpuConfig
- Direction
- lact_daemon.server.gpu_controller uses lact_schema.config, so a change to lact_schema.config can break lact_daemon.server.gpu_controller, while a change to lact_daemon.server.gpu_controller can't break lact_schema.config.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller uses a module listed above it, which is the healthy direction.
28→16 lact_daemon.server.gpu_controller uses lact_daemon.config✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller uses a type in lact_daemon.config.
- The types involved
lact_daemon.server.gpu_controller.gpu_controller$module→lact_daemon.config.Config
- Direction
- lact_daemon.server.gpu_controller uses lact_daemon.config, so a change to lact_daemon.config can break lact_daemon.server.gpu_controller, while a change to lact_daemon.server.gpu_controller can't break lact_daemon.config.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller uses a module listed above it, which is the healthy direction.
28→24 lact_daemon.server.gpu_controller uses lact_daemon.server.handler✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller uses a type in lact_daemon.server.handler.
- The types involved
lact_daemon.server.gpu_controller.gpu_controller$module→lact_daemon.server.handler.SnapshotDeviceInfo
- Direction
- lact_daemon.server.gpu_controller uses lact_daemon.server.handler, so a change to lact_daemon.server.handler can break lact_daemon.server.gpu_controller, while a change to lact_daemon.server.gpu_controller can't break lact_daemon.server.handler.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller uses a module listed above it, which is the healthy direction.
29→6 lact_daemon.server.gpu_controller.amd.drm.mock uses lact_schema✕
- Connections
- 4 pairs of types, where a type in lact_daemon.server.gpu_controller.amd.drm.mock uses a type in lact_schema.
- The types involved
lact_daemon.server.gpu_controller.amd.drm.mock.MockDrmProvider→lact_schema.AmdUmaCarveoutlact_daemon.server.gpu_controller.amd.drm.mock.MockDrmProvider→lact_schema.CacheInfolact_daemon.server.gpu_controller.amd.drm.mock.MockDrmProvider→lact_schema.DeviceTypelact_daemon.server.gpu_controller.amd.drm.mock.MockDrmProvider→lact_schema.DrmInfo
- Direction
- lact_daemon.server.gpu_controller.amd.drm.mock uses lact_schema, so a change to lact_schema can break lact_daemon.server.gpu_controller.amd.drm.mock, while a change to lact_daemon.server.gpu_controller.amd.drm.mock can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.amd.drm.mock uses a module listed above it, which is the healthy direction.
29→9 lact_daemon.server.gpu_controller.amd.drm.mock uses lact_daemon.server.gpu_controller.amd.drm✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.amd.drm.mock uses a type in lact_daemon.server.gpu_controller.amd.drm.
- The types involved
lact_daemon.server.gpu_controller.amd.drm.mock.MockDrmProvider→lact_daemon.server.gpu_controller.amd.drm.DrmProvider
- Direction
- lact_daemon.server.gpu_controller.amd.drm.mock uses lact_daemon.server.gpu_controller.amd.drm, so a change to lact_daemon.server.gpu_controller.amd.drm can break lact_daemon.server.gpu_controller.amd.drm.mock, while a change to lact_daemon.server.gpu_controller.amd.drm.mock can't break lact_daemon.server.gpu_controller.amd.drm.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.amd.drm.mock uses a module listed above it, which is the healthy direction.
29→24 lact_daemon.server.gpu_controller.amd.drm.mock uses lact_daemon.server.handler✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.amd.drm.mock uses a type in lact_daemon.server.handler.
- The types involved
lact_daemon.server.gpu_controller.amd.drm.mock.MockDrmProvider→lact_daemon.server.handler.SnapshotDeviceInfo
- Direction
- lact_daemon.server.gpu_controller.amd.drm.mock uses lact_daemon.server.handler, so a change to lact_daemon.server.handler can break lact_daemon.server.gpu_controller.amd.drm.mock, while a change to lact_daemon.server.gpu_controller.amd.drm.mock can't break lact_daemon.server.handler.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.amd.drm.mock uses a module listed above it, which is the healthy direction.
30→6 lact_daemon.server.gpu_controller.intel.drm.mock uses lact_schema✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.intel.drm.mock uses a type in lact_schema.
- The types involved
lact_daemon.server.gpu_controller.intel.drm.mock.MockDrmProvider→lact_schema.IntelDrmInfo
- Direction
- lact_daemon.server.gpu_controller.intel.drm.mock uses lact_schema, so a change to lact_schema can break lact_daemon.server.gpu_controller.intel.drm.mock, while a change to lact_daemon.server.gpu_controller.intel.drm.mock can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel.drm.mock uses a module listed above it, which is the healthy direction.
30→9 lact_daemon.server.gpu_controller.intel.drm.mock uses lact_daemon.server.gpu_controller.amd.drm✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.intel.drm.mock uses a type in lact_daemon.server.gpu_controller.amd.drm.
- The types involved
lact_daemon.server.gpu_controller.intel.drm.mock.MockDrmProvider→lact_daemon.server.gpu_controller.amd.drm.DrmProvider
- Direction
- lact_daemon.server.gpu_controller.intel.drm.mock uses lact_daemon.server.gpu_controller.amd.drm, so a change to lact_daemon.server.gpu_controller.amd.drm can break lact_daemon.server.gpu_controller.intel.drm.mock, while a change to lact_daemon.server.gpu_controller.intel.drm.mock can't break lact_daemon.server.gpu_controller.amd.drm.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel.drm.mock uses a module listed above it, which is the healthy direction.
30→10 lact_daemon.server.gpu_controller.intel.drm.mock uses lact_daemon.server.gpu_controller.intel.drm✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.intel.drm.mock uses a type in lact_daemon.server.gpu_controller.intel.drm.
- The types involved
lact_daemon.server.gpu_controller.intel.drm.mock.MockDrmProvider→lact_daemon.server.gpu_controller.intel.drm.VramInfo
- Direction
- lact_daemon.server.gpu_controller.intel.drm.mock uses lact_daemon.server.gpu_controller.intel.drm, so a change to lact_daemon.server.gpu_controller.intel.drm can break lact_daemon.server.gpu_controller.intel.drm.mock, while a change to lact_daemon.server.gpu_controller.intel.drm.mock can't break lact_daemon.server.gpu_controller.intel.drm.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel.drm.mock uses a module listed above it, which is the healthy direction.
30→24 lact_daemon.server.gpu_controller.intel.drm.mock uses lact_daemon.server.handler✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.intel.drm.mock uses a type in lact_daemon.server.handler.
- The types involved
lact_daemon.server.gpu_controller.intel.drm.mock.MockDrmProvider→lact_daemon.server.handler.SnapshotDeviceInfo
- Direction
- lact_daemon.server.gpu_controller.intel.drm.mock uses lact_daemon.server.handler, so a change to lact_daemon.server.handler can break lact_daemon.server.gpu_controller.intel.drm.mock, while a change to lact_daemon.server.gpu_controller.intel.drm.mock can't break lact_daemon.server.handler.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel.drm.mock uses a module listed above it, which is the healthy direction.
31→2 lact_daemon.server.metrics uses lact_daemon.server.metrics.schema✕
- Connections
- 3 pairs of types, where a type in lact_daemon.server.metrics uses a type in lact_daemon.server.metrics.schema.
- The types involved
lact_daemon.server.metrics.metrics$module→lact_daemon.server.metrics.schema.Attributelact_daemon.server.metrics.metrics$module→lact_daemon.server.metrics.schema.Metriclact_daemon.server.metrics.metrics$module→lact_daemon.server.metrics.schema.NumberValue
- Direction
- lact_daemon.server.metrics uses lact_daemon.server.metrics.schema, so a change to lact_daemon.server.metrics.schema can break lact_daemon.server.metrics, while a change to lact_daemon.server.metrics can't break lact_daemon.server.metrics.schema.
- Position
- Below the diagonal: lact_daemon.server.metrics uses a module listed above it, which is the healthy direction.
31→6 lact_daemon.server.metrics uses lact_schema✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.metrics uses a type in lact_schema.
- The types involved
lact_daemon.server.metrics.metrics$module→lact_schema.DeviceStats
- Direction
- lact_daemon.server.metrics uses lact_schema, so a change to lact_schema can break lact_daemon.server.metrics, while a change to lact_daemon.server.metrics can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.metrics uses a module listed above it, which is the healthy direction.
31→16 lact_daemon.server.metrics uses lact_daemon.config✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.metrics uses a type in lact_daemon.config.
- The types involved
lact_daemon.server.metrics.metrics$module→lact_daemon.config.Metrics
- Direction
- lact_daemon.server.metrics uses lact_daemon.config, so a change to lact_daemon.config can break lact_daemon.server.metrics, while a change to lact_daemon.server.metrics can't break lact_daemon.config.
- Position
- Below the diagonal: lact_daemon.server.metrics uses a module listed above it, which is the healthy direction.
31→24 lact_daemon.server.metrics uses lact_daemon.server.handler✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.metrics uses a type in lact_daemon.server.handler.
- The types involved
lact_daemon.server.metrics.metrics$module→lact_daemon.server.handler.Handler
- Direction
- lact_daemon.server.metrics uses lact_daemon.server.handler, so a change to lact_daemon.server.handler can break lact_daemon.server.metrics, while a change to lact_daemon.server.metrics can't break lact_daemon.server.handler.
- Position
- Below the diagonal: lact_daemon.server.metrics uses a module listed above it, which is the healthy direction.
32→6 lact_daemon.server.profiles uses lact_schema✕
- Connections
- 2 pairs of types, where a type in lact_daemon.server.profiles uses a type in lact_schema.
- The types involved
lact_daemon.server.profiles.profiles$module→lact_schema.ProfileRulelact_daemon.server.profiles.profiles$module→lact_schema.ProfileWatcherState
- Direction
- lact_daemon.server.profiles uses lact_schema, so a change to lact_schema can break lact_daemon.server.profiles, while a change to lact_daemon.server.profiles can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.profiles uses a module listed above it, which is the healthy direction.
32→24 lact_daemon.server.profiles uses lact_daemon.server.handler✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.profiles uses a type in lact_daemon.server.handler.
- The types involved
lact_daemon.server.profiles.profiles$module→lact_daemon.server.handler.Handler
- Direction
- lact_daemon.server.profiles uses lact_daemon.server.handler, so a change to lact_daemon.server.handler can break lact_daemon.server.profiles, while a change to lact_daemon.server.profiles can't break lact_daemon.server.handler.
- Position
- Below the diagonal: lact_daemon.server.profiles uses a module listed above it, which is the healthy direction.
33→6 lact_daemon.server.gpu_controller.amd.drm.amdgpu uses lact_schema✕
- Connections
- 4 pairs of types, where a type in lact_daemon.server.gpu_controller.amd.drm.amdgpu uses a type in lact_schema.
- The types involved
lact_daemon.server.gpu_controller.amd.drm.amdgpu.AmdGpuDrmProvider→lact_schema.AmdUmaCarveoutlact_daemon.server.gpu_controller.amd.drm.amdgpu.AmdGpuDrmProvider→lact_schema.CacheInfolact_daemon.server.gpu_controller.amd.drm.amdgpu.AmdGpuDrmProvider→lact_schema.DeviceTypelact_daemon.server.gpu_controller.amd.drm.amdgpu.AmdGpuDrmProvider→lact_schema.DrmInfo
- Direction
- lact_daemon.server.gpu_controller.amd.drm.amdgpu uses lact_schema, so a change to lact_schema can break lact_daemon.server.gpu_controller.amd.drm.amdgpu, while a change to lact_daemon.server.gpu_controller.amd.drm.amdgpu can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.amd.drm.amdgpu uses a module listed above it, which is the healthy direction.
33→9 lact_daemon.server.gpu_controller.amd.drm.amdgpu uses lact_daemon.server.gpu_controller.amd.drm✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.amd.drm.amdgpu uses a type in lact_daemon.server.gpu_controller.amd.drm.
- The types involved
lact_daemon.server.gpu_controller.amd.drm.amdgpu.AmdGpuDrmProvider→lact_daemon.server.gpu_controller.amd.drm.DrmProvider
- Direction
- lact_daemon.server.gpu_controller.amd.drm.amdgpu uses lact_daemon.server.gpu_controller.amd.drm, so a change to lact_daemon.server.gpu_controller.amd.drm can break lact_daemon.server.gpu_controller.amd.drm.amdgpu, while a change to lact_daemon.server.gpu_controller.amd.drm.amdgpu can't break lact_daemon.server.gpu_controller.amd.drm.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.amd.drm.amdgpu uses a module listed above it, which is the healthy direction.
33→28 lact_daemon.server.gpu_controller.amd.drm.amdgpu uses lact_daemon.server.gpu_controller✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.amd.drm.amdgpu uses a type in lact_daemon.server.gpu_controller.
- The types involved
lact_daemon.server.gpu_controller.amd.drm.amdgpu.AmdGpuDrmProvider→lact_daemon.server.gpu_controller.CommonControllerInfo
- Direction
- lact_daemon.server.gpu_controller.amd.drm.amdgpu uses lact_daemon.server.gpu_controller, so a change to lact_daemon.server.gpu_controller can break lact_daemon.server.gpu_controller.amd.drm.amdgpu, while a change to lact_daemon.server.gpu_controller.amd.drm.amdgpu can't break lact_daemon.server.gpu_controller.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.amd.drm.amdgpu uses a module listed above it, which is the healthy direction.
34→28 lact_daemon.server.gpu_controller.common.fdinfo uses lact_daemon.server.gpu_controller✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.common.fdinfo uses a type in lact_daemon.server.gpu_controller.
- The types involved
lact_daemon.server.gpu_controller.common.fdinfo.fdinfo$module→lact_daemon.server.gpu_controller.CommonControllerInfo
- Direction
- lact_daemon.server.gpu_controller.common.fdinfo uses lact_daemon.server.gpu_controller, so a change to lact_daemon.server.gpu_controller can break lact_daemon.server.gpu_controller.common.fdinfo, while a change to lact_daemon.server.gpu_controller.common.fdinfo can't break lact_daemon.server.gpu_controller.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.common.fdinfo uses a module listed above it, which is the healthy direction.
35→28 lact_daemon.server.gpu_controller.nvidia.driver uses lact_daemon.server.gpu_controller✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.nvidia.driver uses a type in lact_daemon.server.gpu_controller.
- The types involved
lact_daemon.server.gpu_controller.nvidia.driver.DriverHandle→lact_daemon.server.gpu_controller.PciSlotInfo
- Direction
- lact_daemon.server.gpu_controller.nvidia.driver uses lact_daemon.server.gpu_controller, so a change to lact_daemon.server.gpu_controller can break lact_daemon.server.gpu_controller.nvidia.driver, while a change to lact_daemon.server.gpu_controller.nvidia.driver can't break lact_daemon.server.gpu_controller.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.nvidia.driver uses a module listed above it, which is the healthy direction.
36→6 lact_daemon.server.opencl uses lact_schema✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.opencl uses a type in lact_schema.
- The types involved
lact_daemon.server.opencl.opencl$module→lact_schema.OpenCLInfo
- Direction
- lact_daemon.server.opencl uses lact_schema, so a change to lact_schema can break lact_daemon.server.opencl, while a change to lact_daemon.server.opencl can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.opencl uses a module listed above it, which is the healthy direction.
36→28 lact_daemon.server.opencl uses lact_daemon.server.gpu_controller✕
- Connections
- 2 pairs of types, where a type in lact_daemon.server.opencl uses a type in lact_daemon.server.gpu_controller.
- The types involved
lact_daemon.server.opencl.opencl$module→lact_daemon.server.gpu_controller.CommonControllerInfolact_daemon.server.opencl.opencl$module→lact_daemon.server.gpu_controller.PciSlotInfo
- Direction
- lact_daemon.server.opencl uses lact_daemon.server.gpu_controller, so a change to lact_daemon.server.gpu_controller can break lact_daemon.server.opencl, while a change to lact_daemon.server.opencl can't break lact_daemon.server.gpu_controller.
- Position
- Below the diagonal: lact_daemon.server.opencl uses a module listed above it, which is the healthy direction.
37→6 lact_daemon.server.vulkan uses lact_schema✕
- Connections
- 2 pairs of types, where a type in lact_daemon.server.vulkan uses a type in lact_schema.
- The types involved
lact_daemon.server.vulkan.SummaryDeviceEntry→lact_schema.VulkanDriverInfolact_daemon.server.vulkan.vulkan$module→lact_schema.VulkanInfo
- Direction
- lact_daemon.server.vulkan uses lact_schema, so a change to lact_schema can break lact_daemon.server.vulkan, while a change to lact_daemon.server.vulkan can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.vulkan uses a module listed above it, which is the healthy direction.
37→7 lact_daemon.server.vulkan uses lact_schema.args✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.vulkan uses a type in lact_schema.args.
- The types involved
lact_daemon.server.vulkan.vulkan$module→lact_schema.args.Command
- Direction
- lact_daemon.server.vulkan uses lact_schema.args, so a change to lact_schema.args can break lact_daemon.server.vulkan, while a change to lact_daemon.server.vulkan can't break lact_schema.args.
- Position
- Below the diagonal: lact_daemon.server.vulkan uses a module listed above it, which is the healthy direction.
37→28 lact_daemon.server.vulkan uses lact_daemon.server.gpu_controller✕
- Connections
- 2 pairs of types, where a type in lact_daemon.server.vulkan uses a type in lact_daemon.server.gpu_controller.
- The types involved
lact_daemon.server.vulkan.vulkan$module→lact_daemon.server.gpu_controller.CommonControllerInfolact_daemon.server.vulkan.vulkan$module→lact_daemon.server.gpu_controller.PciSlotInfo
- Direction
- lact_daemon.server.vulkan uses lact_daemon.server.gpu_controller, so a change to lact_daemon.server.gpu_controller can break lact_daemon.server.vulkan, while a change to lact_daemon.server.vulkan can't break lact_daemon.server.gpu_controller.
- Position
- Below the diagonal: lact_daemon.server.vulkan uses a module listed above it, which is the healthy direction.
38→6 lact_daemon.server.gpu_controller.amd uses lact_schema✕
- Connections
- 8 pairs of types, where a type in lact_daemon.server.gpu_controller.amd uses a type in lact_schema.
- The types involved
lact_daemon.server.gpu_controller.amd.AmdGpuController→lact_schema.ClockspeedStatslact_daemon.server.gpu_controller.amd.AmdGpuController→lact_schema.DeviceStatslact_daemon.server.gpu_controller.amd.AmdGpuController→lact_schema.DeviceTypelact_daemon.server.gpu_controller.amd.AmdGpuController→lact_schema.DisplaysInfolact_daemon.server.gpu_controller.amd.AmdGpuController→lact_schema.DrmInfolact_daemon.server.gpu_controller.amd.AmdGpuController→lact_schema.LinkInfolact_daemon.server.gpu_controller.amd.AmdGpuController→lact_schema.PowerStatelact_daemon.server.gpu_controller.amd.AmdGpuController→lact_schema.PowerStates
- Direction
- lact_daemon.server.gpu_controller.amd uses lact_schema, so a change to lact_schema can break lact_daemon.server.gpu_controller.amd, while a change to lact_daemon.server.gpu_controller.amd can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.amd uses a module listed above it, which is the healthy direction.
38→14 lact_daemon.server.gpu_controller.amd uses lact_schema.config✕
- Connections
- 4 pairs of types, where a type in lact_daemon.server.gpu_controller.amd uses a type in lact_schema.config.
- The types involved
lact_daemon.server.gpu_controller.amd.AmdGpuController→lact_schema.config.FanControlSettingslact_daemon.server.gpu_controller.amd.AmdGpuController→lact_schema.config.FanCurvelact_daemon.server.gpu_controller.amd.AmdGpuController→lact_schema.config.GpuConfiglact_daemon.server.gpu_controller.amd.amd$module→lact_schema.config.ClocksConfiguration
- Direction
- lact_daemon.server.gpu_controller.amd uses lact_schema.config, so a change to lact_schema.config can break lact_daemon.server.gpu_controller.amd, while a change to lact_daemon.server.gpu_controller.amd can't break lact_schema.config.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.amd uses a module listed above it, which is the healthy direction.
38→28 lact_daemon.server.gpu_controller.amd uses lact_daemon.server.gpu_controller✕
- Connections
- 2 pairs of types, where a type in lact_daemon.server.gpu_controller.amd uses a type in lact_daemon.server.gpu_controller.
- The types involved
lact_daemon.server.gpu_controller.amd.AmdGpuController→lact_daemon.server.gpu_controller.CommonControllerInfolact_daemon.server.gpu_controller.amd.AmdGpuController→lact_daemon.server.gpu_controller.GpuController
- Direction
- lact_daemon.server.gpu_controller.amd uses lact_daemon.server.gpu_controller, so a change to lact_daemon.server.gpu_controller can break lact_daemon.server.gpu_controller.amd, while a change to lact_daemon.server.gpu_controller.amd can't break lact_daemon.server.gpu_controller.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.amd uses a module listed above it, which is the healthy direction.
38→34 lact_daemon.server.gpu_controller.amd uses lact_daemon.server.gpu_controller.common.fdinfo✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.amd uses a type in lact_daemon.server.gpu_controller.common.fdinfo.
- The types involved
lact_daemon.server.gpu_controller.amd.AmdGpuController→lact_daemon.server.gpu_controller.common.fdinfo.DrmUtilMap
- Direction
- lact_daemon.server.gpu_controller.amd uses lact_daemon.server.gpu_controller.common.fdinfo, so a change to lact_daemon.server.gpu_controller.common.fdinfo can break lact_daemon.server.gpu_controller.amd, while a change to lact_daemon.server.gpu_controller.amd can't break lact_daemon.server.gpu_controller.common.fdinfo.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.amd uses a module listed above it, which is the healthy direction.
39→6 lact_daemon.server.gpu_controller.intel uses lact_schema✕
- Connections
- 4 pairs of types, where a type in lact_daemon.server.gpu_controller.intel uses a type in lact_schema.
- The types involved
lact_daemon.server.gpu_controller.intel.IntelGpuController→lact_schema.DeviceStatslact_daemon.server.gpu_controller.intel.IntelGpuController→lact_schema.DeviceTypelact_daemon.server.gpu_controller.intel.IntelGpuController→lact_schema.FanControlModelact_daemon.server.gpu_controller.intel.IntelGpuController→lact_schema.PowerStates
- Direction
- lact_daemon.server.gpu_controller.intel uses lact_schema, so a change to lact_schema can break lact_daemon.server.gpu_controller.intel, while a change to lact_daemon.server.gpu_controller.intel can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel uses a module listed above it, which is the healthy direction.
39→14 lact_daemon.server.gpu_controller.intel uses lact_schema.config✕
- Connections
- 3 pairs of types, where a type in lact_daemon.server.gpu_controller.intel uses a type in lact_schema.config.
- The types involved
lact_daemon.server.gpu_controller.intel.IntelGpuController→lact_schema.config.FanCurvelact_daemon.server.gpu_controller.intel.IntelGpuController→lact_schema.config.GpuConfiglact_daemon.server.gpu_controller.intel.intel$module→lact_schema.config.GpuConfig
- Direction
- lact_daemon.server.gpu_controller.intel uses lact_schema.config, so a change to lact_schema.config can break lact_daemon.server.gpu_controller.intel, while a change to lact_daemon.server.gpu_controller.intel can't break lact_schema.config.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel uses a module listed above it, which is the healthy direction.
39→28 lact_daemon.server.gpu_controller.intel uses lact_daemon.server.gpu_controller✕
- Connections
- 2 pairs of types, where a type in lact_daemon.server.gpu_controller.intel uses a type in lact_daemon.server.gpu_controller.
- The types involved
lact_daemon.server.gpu_controller.intel.IntelGpuController→lact_daemon.server.gpu_controller.CommonControllerInfolact_daemon.server.gpu_controller.intel.IntelGpuController→lact_daemon.server.gpu_controller.GpuController
- Direction
- lact_daemon.server.gpu_controller.intel uses lact_daemon.server.gpu_controller, so a change to lact_daemon.server.gpu_controller can break lact_daemon.server.gpu_controller.intel, while a change to lact_daemon.server.gpu_controller.intel can't break lact_daemon.server.gpu_controller.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel uses a module listed above it, which is the healthy direction.
39→34 lact_daemon.server.gpu_controller.intel uses lact_daemon.server.gpu_controller.common.fdinfo✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.intel uses a type in lact_daemon.server.gpu_controller.common.fdinfo.
- The types involved
lact_daemon.server.gpu_controller.intel.IntelGpuController→lact_daemon.server.gpu_controller.common.fdinfo.DrmUtilMap
- Direction
- lact_daemon.server.gpu_controller.intel uses lact_daemon.server.gpu_controller.common.fdinfo, so a change to lact_daemon.server.gpu_controller.common.fdinfo can break lact_daemon.server.gpu_controller.intel, while a change to lact_daemon.server.gpu_controller.intel can't break lact_daemon.server.gpu_controller.common.fdinfo.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.intel uses a module listed above it, which is the healthy direction.
40→6 lact_daemon.server.gpu_controller.nvidia uses lact_schema✕
- Connections
- 6 pairs of types, where a type in lact_daemon.server.gpu_controller.nvidia uses a type in lact_schema.
- The types involved
lact_daemon.server.gpu_controller.nvidia.NvidiaGpuController→lact_schema.DeviceStatslact_daemon.server.gpu_controller.nvidia.NvidiaGpuController→lact_schema.DeviceTypelact_daemon.server.gpu_controller.nvidia.NvidiaGpuController→lact_schema.DisplaysInfolact_daemon.server.gpu_controller.nvidia.NvidiaGpuController→lact_schema.NvidiaThermalInfolact_daemon.server.gpu_controller.nvidia.NvidiaGpuController→lact_schema.PowerStateslact_daemon.server.gpu_controller.nvidia.nvidia$module→lact_schema.NvidiaVfPoint
- Direction
- lact_daemon.server.gpu_controller.nvidia uses lact_schema, so a change to lact_schema can break lact_daemon.server.gpu_controller.nvidia, while a change to lact_daemon.server.gpu_controller.nvidia can't break lact_schema.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.nvidia uses a module listed above it, which is the healthy direction.
40→14 lact_daemon.server.gpu_controller.nvidia uses lact_schema.config✕
- Connections
- 3 pairs of types, where a type in lact_daemon.server.gpu_controller.nvidia uses a type in lact_schema.config.
- The types involved
lact_daemon.server.gpu_controller.nvidia.NvidiaGpuController→lact_schema.config.FanControlSettingslact_daemon.server.gpu_controller.nvidia.NvidiaGpuController→lact_schema.config.FanCurvelact_daemon.server.gpu_controller.nvidia.NvidiaGpuController→lact_schema.config.GpuConfig
- Direction
- lact_daemon.server.gpu_controller.nvidia uses lact_schema.config, so a change to lact_schema.config can break lact_daemon.server.gpu_controller.nvidia, while a change to lact_daemon.server.gpu_controller.nvidia can't break lact_schema.config.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.nvidia uses a module listed above it, which is the healthy direction.
40→28 lact_daemon.server.gpu_controller.nvidia uses lact_daemon.server.gpu_controller✕
- Connections
- 2 pairs of types, where a type in lact_daemon.server.gpu_controller.nvidia uses a type in lact_daemon.server.gpu_controller.
- The types involved
lact_daemon.server.gpu_controller.nvidia.NvidiaGpuController→lact_daemon.server.gpu_controller.CommonControllerInfolact_daemon.server.gpu_controller.nvidia.NvidiaGpuController→lact_daemon.server.gpu_controller.GpuController
- Direction
- lact_daemon.server.gpu_controller.nvidia uses lact_daemon.server.gpu_controller, so a change to lact_daemon.server.gpu_controller can break lact_daemon.server.gpu_controller.nvidia, while a change to lact_daemon.server.gpu_controller.nvidia can't break lact_daemon.server.gpu_controller.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.nvidia uses a module listed above it, which is the healthy direction.
40→35 lact_daemon.server.gpu_controller.nvidia uses lact_daemon.server.gpu_controller.nvidia.driver✕
- Connections
- 1 pair of types, where a type in lact_daemon.server.gpu_controller.nvidia uses a type in lact_daemon.server.gpu_controller.nvidia.driver.
- The types involved
lact_daemon.server.gpu_controller.nvidia.NvidiaGpuController→lact_daemon.server.gpu_controller.nvidia.driver.DriverHandle
- Direction
- lact_daemon.server.gpu_controller.nvidia uses lact_daemon.server.gpu_controller.nvidia.driver, so a change to lact_daemon.server.gpu_controller.nvidia.driver can break lact_daemon.server.gpu_controller.nvidia, while a change to lact_daemon.server.gpu_controller.nvidia can't break lact_daemon.server.gpu_controller.nvidia.driver.
- Position
- Below the diagonal: lact_daemon.server.gpu_controller.nvidia uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 23 | High / Critical |
| A05:2025 — Injection | 18 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 14 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs; 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; Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. | +3.4 pts | Low | ADR Quality |
| Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. | +2.6 pts | Low | Platform End-of-Life |
| Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +2.0 pts | Low | Supply-chain Provenance & Signing |
| 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. | +3.2 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| Interpolated log message defeats structured logging | +2.4 pts | Medium | Structured logging |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.8 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.5 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| lact-daemon/src/server/gpu_controller/amd.rs | 5.5 | Mixed | Cyclomatic Complexity: AmdGpuController::apply_config (cyclomatic 42) |
| lact-gui/src/app.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| lact-daemon/src/server/gpu_controller/intel.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| lact-daemon/src/server/gpu_controller/nvidia.rs | 7.0 | Near-clean | Cyclomatic Complexity: NvidiaGpuController::apply_config (cyclomatic 23) |
| lact-daemon/src/server/handler.rs | 7.0 | Near-clean | Cognitive Complexity: Handler::set_fan_control (cognitive 31) |
| lact-gui/src/app/pages/oc_page/vf_curve.rs | 7.0 | Near-clean | Cyclomatic Complexity: VfCurveEditor::draw_chart (cyclomatic 37) |
| lact-gui/src/app/pages/oc_page/clocks_frame/mod.rs | 7.0 | Near-clean | Cyclomatic Complexity: ClocksFrame::update_with_view (cyclomatic 21) |
| lact-daemon/src/server/profiles.rs | 7.2 | Near-clean | Cyclomatic Complexity: lact_daemon::server::profiles::run_watcher (cyclomatic 18) |
| lact-daemon/src/server/metrics.rs | 7.2 | Near-clean | Cyclomatic Complexity: lact_daemon::server::metrics::collect_metrics (cyclomatic 16) |
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 45 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 45 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, 227 of 246 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`cargo llvm-cov`) shows coverage is measured in your own CI.
- D11 Test Reliability — 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. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 18 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (57 contributor(s) across 1291 commit(s) sampled, automation and bot accounts excluded). One of them holds 80% of the history; the other 56 hold 0.4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — 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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D31 IaC & Container Security — 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. Pkg/images/arch/Dockerfile, REDACTED, REDACTED, REDACTED carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 6 of 10 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- PF1 Benchmark discipline — 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — 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 PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — 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. 223 further occurrence(s) are not listed individually; the score already reflects all 263.
- X5 Nullable reference types — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust 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.
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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
18 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was AppModel::handle_msg at 55. A further 7 function(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 lact_daemon::server::handle_request at 40 — they are counted neither in the figure above nor in this dimension's score. 6 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: lact-daemon/src/server.rs (lact_daemon::server::handle_request at 40), lact-gui/src/app/preferences_dialog.rs (lact_gui::app::preferences_dialog::language_name at 27), lact-daemon/src/server/gpu_controller/nvidia/driver.rs (DriverHandle::get_ram_type at 22), lact-daemon/src/server/gpu_controller/nvidia/nvapi.rs (NvGpuClockDomainId::into_str at 18), lact-gui/src/app/graphs_window/stat.rs (StatType::display at 18), and 1 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 18 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with AppModel::handle_msg (cyclomatic 55), AmdGpuController::apply_config (cyclomatic 42), VfCurveEditor::draw_chart (cyclomatic 37). — 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 18 together lifts Cyclomatic Complexity from 7.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
48 function(s) exceeded the cognitive complexity threshold of 15; the worst was Config::migrate_versions at 86.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with Config::migrate_versions (cognitive 86), lact_daemon::server::gpu_controller::amd::apply_clocks_config_to_table (cognitive 85), AmdGpuController::apply_config (cognitive 80). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 3.7 to about 4.6/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
32 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 13 MethodTooLong finding(s) in God Classes — start with amd.rs (3), app.rs (2), nvidia.rs (2). — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 9 FileTooLong finding(s) in God Classes — start with amd.rs, handler.rs, nvidia.rs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 7 ClassTooLong finding(s) in God Classes — start with amd.rs, app.rs, nvidia.rs. — One of this dimension's main actionable groups (7 warning-level).
D4 · Code Duplication
14 duplicated block group(s) detected. 2.0 % of the production lines (603 of 30,799) are in a reported copy. A further 10 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with tcp.rs, info_row.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with amd.rs, vulkan.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with handler.rs, boolean_control.rs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
6 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 5 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 76 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with imp.rs. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
6 outdated, 0 yanked direct Cargo dependencies. 40 of 42 direct crates were graded against crates.io (0 not published there, 2 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 377 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 2 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: lact-gui/src/app.rs (12×55=660); lact-daemon/src/server/gpu_controller/amd.rs (11×42=462); lact-gui/src/app/pages/oc_page/vf_curve.rs (6×37=222)
What to do
- Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with app.rs, amd.rs, vf_curve.rs. — One of this dimension's main actionable groups (6 warning-level).
D17 · Explicit Debt
2 deducted task-comment markers across 30799 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.
What to do
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with app.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with intel.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 13 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 6 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
18 finding(s): 0 critical, 16 high, 2 medium, 0 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 3 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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).
- No action in Static Analysis (SAST) — all 9 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (9 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
23 finding(s): 0 critical, 11 high, 12 medium, 0 low.
What to do
- Resolve the 11 High IaC finding(s) in IaC & Container Security — start with REDACTED (11). — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 12 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (12). — One of this dimension's main actionable groups (12 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 89 of the 122 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: intel.rs↔nvidia.rs 61%; amd.rs↔intel.rs 57%; lib.rs↔server.rs 56%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with lib.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with intel.rs, amd.rs. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 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.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC6 · Visual & motion safety
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 3/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `lact`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X21 · Side-effecting pattern guard
X29 · Per-element action decided by a fixed element
X4 · Structured logging
- `error!` at line 355 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:355
- `info!` at line 361 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:361
- `error!` at line 666 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:666
- `warn!` at line 906 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:906
- `warn!` at line 927 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:927
- `debug!` at line 1008 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:1008
- `warn!` at line 1111 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:1111
- `debug!` at line 1137 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:1137
- `debug!` at line 1179 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:1179
- `debug!` at line 1197 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:1197
- `debug!` at line 1206 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:1206
- `warn!` at line 1212 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:1212
- `debug!` at line 1230 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:1230
- `error!` at line 1448 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:1448
- `error!` at line 1457 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:1457
- `error!` at line 1517 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app.rs:1517
- `debug!` at line 77 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/config.rs:77
- `error!` at line 82 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/config.rs:82
- `error!` at line 88 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/config.rs:88
- `error!` at line 99 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/config.rs:99
- `error!` at line 104 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/config.rs:104
- `warn!` at line 102 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/lib.rs:102
- `warn!` at line 189 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app/info_dialog.rs:189
- `debug!` at line 355 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app/profiles.rs:355
- `debug!` at line 347 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app/pages/oc_page.rs:347
- `error!` at line 168 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app/graphs_window/plot/render_thread.rs:168
- `debug!` at line 56 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-gui/src/app/components/adjustment_value/mod.rs:56
- `debug!` at line 126 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/config.rs:126
- `info!` at line 207 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/config.rs:207
- `info!` at line 266 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/config.rs:266
- `warn!` at line 269 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/config.rs:269
- `info!` at line 277 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/config.rs:277
- `debug!` at line 394 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/config.rs:394
- `error!` at line 430 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/config.rs:430
- `error!` at line 440 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/config.rs:440
- `error!` at line 445 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/config.rs:445
- `debug!` at line 449 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/config.rs:449
- `error!` at line 120 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/lib.rs:120
- `error!` at line 131 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/lib.rs:131
- `info!` at line 42 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — lact-daemon/src/server.rs:42
What to do
- Interpolated log message defeats structured logging
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 63% | Adequate — gated by D2, X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 91% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 60% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 70% | Strong | Solid. |
| Security | 49% | Adequate — gated by D29, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 100% | Exemplary | Strongest area. |
| Performance | 89% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · 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.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 69 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC3 Page structure — No structural check found in the parsed markup — AC3 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~363 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D16 Bus Factor — single-maintainer 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 (3207 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. 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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Rust suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (7 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- 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.
- S1 Web-Security Posture — No web surface: 121 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- 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.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — 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.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 29 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: amdgpu-sysfs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: lib.rs ↔ server.rs lact-client/src/lib.rs:1
Serious — 161 finding(s)
- MethodTooLong: AppModel.handle_msg lact-gui/src/app.rs:615
- MethodTooLong: VfCurveEditor.draw_chart lact-gui/src/app/pages/oc_page/vf_curve.rs:462
- MethodTooLong: AmdGpuController.apply_config lact-daemon/src/server/gpu_controller/amd.rs:1129
- MethodTooLong: AmdGpuController.get_stats lact-daemon/src/server/gpu_controller/amd.rs:820
- MethodTooLong: NvidiaGpuController.get_stats lact-daemon/src/server/gpu_controller/nvidia.rs:879
- MethodTooLong: AppModel.init lact-gui/src/app.rs:335
- MethodTooLong: RenderRequest.draw lact-gui/src/app/graphs_window/plot/render_thread.rs:200
- MethodTooLong: ThermalsPage.update_with_view lact-gui/src/app/pages/thermals_page.rs:278
- MethodTooLong: FanCurveFrame.update_with_view lact-gui/src/app/pages/thermals_page/fan_curve_frame.rs:256
- MethodTooLong: AmdGpuController.start_curve_fan_control_task lact-daemon/src/server/gpu_controller/amd.rs:215
- MethodTooLong: NvidiaGpuController.apply_config lact-daemon/src/server/gpu_controller/nvidia.rs:1222
- MethodTooLong: DeviceInfo.info_elements lact-schema/src/lib.rs:213
- MethodTooLong: ProfileSelector.update_with_view lact-gui/src/app/profiles.rs:185
- lact_daemon::server::gpu_controller::amd::apply_clocks_config_to_table (cognitive 85) lact-daemon/src/server/gpu_controller/amd.rs:1528
- lact_daemon::server::gpu_controller::common::fdinfo::read_process_list (cognitive 54) lact-daemon/src/server/gpu_controller/common/fdinfo.rs:19
- lact_daemon::server::profiles::profile_rule_matches (cognitive 52) lact-daemon/src/server/profiles.rs:270
- lact_daemon::server::profiles::run_watcher (cognitive 44) lact-daemon/src/server/profiles.rs:36
- lact_daemon::config::start_watcher (cognitive 36) lact-daemon/src/config.rs:376
- lact_daemon::server::opencl::extract_device_info (cognitive 33) lact-daemon/src/server/opencl.rs:60
- lact_daemon::server::vulkan::get_vulkan_info (cognitive 24) lact-daemon/src/server/vulkan.rs:17
- lact_daemon::server::gpu_controller::common::fdinfo::parse_fdinfo (cognitive 22) lact-daemon/src/server/gpu_controller/common/fdinfo.rs:208
- lact_daemon::system::power_profiles_daemon::disable_conflicting_actions (cognitive 22) lact-daemon/src/system/power_profiles_daemon.rs:38
- lact_daemon::server::handler::add_path_recursively (cognitive 20) lact-daemon/src/server/handler.rs:1518
- lact_daemon::server::gpu_controller::init_controller (cognitive 17) lact-daemon/src/server/gpu_controller.rs:249
- lact_daemon::server::metrics::collect_metrics (cognitive 17) lact-daemon/src/server/metrics.rs:107
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: gpu_controller/amd.rs lact-daemon/src/server/gpu_controller/amd.rs
- FileTooLong: server/handler.rs lact-daemon/src/server/handler.rs
- FileTooLong: gpu_controller/nvidia.rs lact-daemon/src/server/gpu_controller/nvidia.rs
- FileTooLong: src/app.rs lact-gui/src/app.rs
- FileTooLong: src/lib.rs lact-schema/src/lib.rs
- FileTooLong: gpu_controller/intel.rs lact-daemon/src/server/gpu_controller/intel.rs
- FileTooLong: nvidia/nvapi.rs lact-daemon/src/server/gpu_controller/nvidia/nvapi.rs
- FileTooLong: oc_page/vf_curve.rs lact-gui/src/app/pages/oc_page/vf_curve.rs
- FileTooLong: clocks_frame/mod.rs lact-gui/src/app/pages/oc_page/clocks_frame/mod.rs
- ClassTooLong: AmdGpuController lact-daemon/src/server/gpu_controller/amd.rs:67
- ClassTooLong: AppModel lact-gui/src/app.rs:104
- ClassTooLong: NvidiaGpuController lact-daemon/src/server/gpu_controller/nvidia.rs:61
- ClassTooLong: Handler lact-daemon/src/server/handler.rs:100
- ClassTooLong: IntelGpuController lact-daemon/src/server/gpu_controller/intel.rs:60
- ClassTooLong: VfCurveEditor lact-gui/src/app/pages/oc_page/vf_curve.rs:37
- ClassTooLong: ClocksFrame lact-gui/src/app/pages/oc_page/clocks_frame/mod.rs:29
- Hotspot: lact-gui/src/app.rs lact-gui/src/app.rs:615
- Hotspot: lact-daemon/src/server/gpu_controller/amd.rs lact-daemon/src/server/gpu_controller/amd.rs:1129
- Hotspot: lact-gui/src/app/pages/oc_page/vf_curve.rs lact-gui/src/app/pages/oc_page/vf_curve.rs:462
- Hotspot: lact-gui/src/app/pages/oc_page/clocks_frame/mod.rs lact-gui/src/app/pages/oc_page/clocks_frame/mod.rs:331
- Hotspot: lact-gui/src/app/pages/oc_page/power_states/power_states_dialog.rs lact-gui/src/app/pages/oc_page/power_states/power_states_dialog.rs:188
- Hotspot: lact-daemon/src/server/gpu_controller/intel.rs lact-daemon/src/server/gpu_controller/intel.rs:775
- NvidiaGpuController::apply_config (cognitive 36) lact-daemon/src/server/gpu_controller/nvidia.rs:1222
- NvidiaGpuController::start_curve_fan_control_task (cognitive 32) lact-daemon/src/server/gpu_controller/nvidia.rs:193
- NvidiaGpuController::get_stats (cognitive 31) lact-daemon/src/server/gpu_controller/nvidia.rs:879
- NvidiaGpuController::reset_clocks (cognitive 25) lact-daemon/src/server/gpu_controller/nvidia.rs:1384
- NvidiaGpuController::populate_displays_info (cognitive 22) lact-daemon/src/server/gpu_controller/nvidia.rs:1529
- NvidiaGpuController::get_clocks_info (cognitive 18) lact-daemon/src/server/gpu_controller/nvidia.rs:1125
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- lact_daemon::server::gpu_controller::amd::apply_clocks_config_to_table (cyclomatic 35) lact-daemon/src/server/gpu_controller/amd.rs:1528
- lact_daemon::server::profiles::run_watcher (cyclomatic 18) lact-daemon/src/server/profiles.rs:36
- lact_daemon::server::profiles::profile_rule_matches (cyclomatic 18) lact-daemon/src/server/profiles.rs:270
- lact_daemon::server::metrics::collect_metrics (cyclomatic 16) lact-daemon/src/server/metrics.rs:107
- AmdGpuController::apply_config (cognitive 80) lact-daemon/src/server/gpu_controller/amd.rs:1129
- AmdGpuController::start_curve_fan_control_task (cognitive 41) lact-daemon/src/server/gpu_controller/amd.rs:215
- AmdGpuController::get_stats (cognitive 21) lact-daemon/src/server/gpu_controller/amd.rs:820
- Handler::set_fan_control (cognitive 31) lact-daemon/src/server/handler.rs:514
- Handler::with_base_path (cognitive 19) lact-daemon/src/server/handler.rs:127
- Handler::generate_snapshot (cognitive 16) lact-daemon/src/server/handler.rs:715
- IntelGpuController::apply_config (cognitive 30) lact-daemon/src/server/gpu_controller/intel.rs:775
- IntelGpuController::get_throttle_info (cognitive 26) lact-daemon/src/server/gpu_controller/intel.rs:421
- IntelGpuController::new (cognitive 16) lact-daemon/src/server/gpu_controller/intel.rs:74
- AmdGpuController::apply_config (cyclomatic 42) lact-daemon/src/server/gpu_controller/amd.rs:1129
- AmdGpuController::start_curve_fan_control_task (cyclomatic 19) lact-daemon/src/server/gpu_controller/amd.rs:215
- VfCurveEditor::draw_chart (cyclomatic 37) lact-gui/src/app/pages/oc_page/vf_curve.rs:462
- VfCurveEditor::update_with_view (cyclomatic 26) lact-gui/src/app/pages/oc_page/vf_curve.rs:330
- ClocksFrame::update_with_view (cyclomatic 21) lact-gui/src/app/pages/oc_page/clocks_frame/mod.rs:331
- ClocksFrame::set_amd_table (cyclomatic 16) lact-gui/src/app/pages/oc_page/clocks_frame/mod.rs:520
- VfCurveEditor::draw_chart (cognitive 58) lact-gui/src/app/pages/oc_page/vf_curve.rs:462
- VfCurveEditor::update_with_view (cognitive 37) lact-gui/src/app/pages/oc_page/vf_curve.rs:330
- ClocksFrame::set_amd_table (cognitive 35) lact-gui/src/app/pages/oc_page/clocks_frame/mod.rs:520
- ClocksFrame::update_with_view (cognitive 26) lact-gui/src/app/pages/oc_page/clocks_frame/mod.rs:331
- ThermalsPage::update_with_view (cognitive 31) lact-gui/src/app/pages/thermals_page.rs:278
- ThermalsPage::apply_config (cognitive 16) lact-gui/src/app/pages/thermals_page.rs:453
- REDACTED
- REDACTED
- FunctionTooLong: lact_daemon::server::metrics::collect_metrics lact-daemon/src/server/metrics.rs:107
- FunctionTooLong: lact_daemon::server::gpu_controller::amd::apply_clocks_config_to_table lact-daemon/src/server/gpu_controller/amd.rs:1528
- Change coupling: intel.rs ↔ nvidia.rs lact-daemon/src/server/gpu_controller/intel.rs:1
- Change coupling: amd.rs ↔ intel.rs lact-daemon/src/server/gpu_controller/amd.rs:1
- REDACTED
- REDACTED
- Edited copy of a member (7 corresponding lines) lact-client/src/connection/tcp.rs:15
- Edited copy of a member (7 corresponding lines) lact-gui/src/app/components/info_row.rs:19
- Duplicated block (17 lines × 2) lact-daemon/src/server/gpu_controller/amd.rs:318
- Duplicated block (17 lines × 2) lact-daemon/src/server/vulkan.rs:154
- Duplicated block (14 lines × 2) lact-daemon/src/server/handler.rs:380
- Duplicated block (14 lines × 2) lact-gui/src/app/components/setting_row/boolean_control.rs:60
- Duplicated block (13 lines × 2) lact-daemon/src/server.rs:102
- Duplicated block (13 lines × 2) lact-daemon/src/server/gpu_controller/intel.rs:610
- Duplicated block (6 lines × 2) lact-gui/src/app/gpu_selector.rs:91
- Duplicated block (6 lines × 2) lact-daemon/src/server/handler.rs:769
- Duplicated block (9 lines × 2) lact-daemon/src/server/gpu_controller/amd.rs:1450
- Duplicated block (9 lines × 2) lact-daemon/src/server/gpu_controller/nvidia.rs:405
- AppModel::handle_msg (cyclomatic 55) lact-gui/src/app.rs:615
- Config::migrate_versions (cyclomatic 32) lact-daemon/src/config.rs:150
- NvidiaGpuController::apply_config (cyclomatic 23) lact-daemon/src/server/gpu_controller/nvidia.rs:1222
- IntelGpuController::apply_config (cyclomatic 18) lact-daemon/src/server/gpu_controller/intel.rs:775
- FanCurveFrame::update_with_view (cyclomatic 18) lact-gui/src/app/pages/thermals_page/fan_curve_frame.rs:256
- ProfileSelector::update_with_view (cyclomatic 18) lact-gui/src/app/profiles.rs:185
- GraphsWindow::update_with_view (cyclomatic 16) lact-gui/src/app/graphs_window/mod.rs:190
- PowerStatesDialog::update_with_view (cyclomatic 16) lact-gui/src/app/pages/oc_page/power_states/power_states_dialog.rs:188
- FixmeComment lact-gui/src/app.rs:1251
- TodoComment lact-daemon/src/server/gpu_controller/intel.rs:899
- Config::migrate_versions (cognitive 86) lact-daemon/src/config.rs:150
- GameModeConnector::receieve_events (cognitive 55) lact-daemon/src/server/profiles/gamemode.rs:137
- NvApi::read_vram_temps (cognitive 49) lact-daemon/src/server/gpu_controller/nvidia/nvapi.rs:265
- InformationPage::update_items (cognitive 35) lact-gui/src/app/pages/info_page.rs:128
- AppModel::handle_msg (cognitive 34) lact-gui/src/app.rs:615
- DeviceInfo::info_elements (cognitive 25) lact-schema/src/lib.rs:213
- FanCurveFrame::update_with_view (cognitive 24) lact-gui/src/app/pages/thermals_page/fan_curve_frame.rs:256
- lact_cli::subcommands::stats (cognitive 21) lact-cli/src/subcommands.rs:43
- lact_gui::app::profiles::profile_rule_window::profile_rule_row::format_rule (cognitive 21) lact-gui/src/app/profiles/profile_rule_window/profile_rule_row.rs:397
- ProcessMonitorWindow::update (cognitive 20) lact-gui/src/app/process_monitor.rs:121
- ProfileSelector::update_with_view (cognitive 20) lact-gui/src/app/profiles.rs:185
- StatsData::update_with_timestamp (cognitive 17) lact-gui/src/app/graphs_window/stat.rs:17
- PowerFrame::update_with_view (cognitive 17) lact-gui/src/app/pages/oc_page/power_frame.rs:124
- Server::run (cognitive 16) lact-daemon/src/server.rs:80
- AdjustmentRow::update_with_view (cognitive 16) lact-gui/src/app/components/adjustment_row.rs:215
- TooManyMethods: Handler lact-daemon/src/server/handler.rs:100
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (34 corresponding lines) lact-daemon/src/server/vulkan.rs:129
- Edited copy of a member (42 corresponding lines) lact-daemon/src/server/gpu_controller/intel/drm/i915.rs:48
- Edited copy of a member (22 corresponding lines) lact-gui/src/app/components/setting_row/boolean_control.rs:56
- Edited copy of a member (24 corresponding lines) lact-daemon/src/server/handler.rs:1013
- Edited copy of a member (19 corresponding lines) lact-gui/src/app/pages/oc_page/clocks_frame/mod.rs:850
- Edited copy of a member (17 corresponding lines) lact-cli/src/subcommands.rs:234
- Edited copy of a member (10 corresponding lines) lact-daemon/src/server/handler.rs:460
- Edited copy of a member (11 corresponding lines) lact-client/src/connection/unix.rs:44
- Duplicated block (10 lines × 2) lact-daemon/src/server/handler.rs:974
- Duplicated block (11 lines × 2) lact-daemon/src/server/gpu_controller/amd.rs:1438
- Duplicated block (14 lines × 3) lact-daemon/src/server/metrics.rs:190
- Duplicated block (8 lines × 2) lact-gui/src/app/profiles/profile_rule_window/profile_rule_row.rs:421
- End-of-life runtime: Rust 1.97 rust-toolchain.toml:1
- Off the main sequence: lact-schema
- Low cohesion: AdjustmentValue (LCOM4 4) lact-gui/src/app/components/adjustment_value/imp.rs:7
- Coverage collected but not gated
Minor — 50 finding(s)
- Interpolated log message defeats structured logging lact-gui/src/app.rs:355
- Interpolated log message defeats structured logging lact-gui/src/app.rs:361
- Interpolated log message defeats structured logging lact-gui/src/app.rs:666
- Interpolated log message defeats structured logging lact-gui/src/app.rs:906
- Interpolated log message defeats structured logging lact-gui/src/app.rs:927
- Interpolated log message defeats structured logging lact-gui/src/app.rs:1008
- Interpolated log message defeats structured logging lact-gui/src/app.rs:1111
- Interpolated log message defeats structured logging lact-gui/src/app.rs:1137
- Interpolated log message defeats structured logging lact-gui/src/app.rs:1179
- Interpolated log message defeats structured logging lact-gui/src/app.rs:1197
- Interpolated log message defeats structured logging lact-gui/src/app.rs:1206
- Interpolated log message defeats structured logging lact-gui/src/app.rs:1212
- Interpolated log message defeats structured logging lact-gui/src/app.rs:1230
- Interpolated log message defeats structured logging lact-gui/src/app.rs:1448
- Interpolated log message defeats structured logging lact-gui/src/app.rs:1457
- Interpolated log message defeats structured logging lact-gui/src/app.rs:1517
- Interpolated log message defeats structured logging lact-gui/src/config.rs:77
- Interpolated log message defeats structured logging lact-gui/src/config.rs:82
- Interpolated log message defeats structured logging lact-gui/src/config.rs:88
- Interpolated log message defeats structured logging lact-gui/src/config.rs:99
- Interpolated log message defeats structured logging lact-gui/src/config.rs:104
- Interpolated log message defeats structured logging lact-gui/src/lib.rs:102
- Interpolated log message defeats structured logging lact-gui/src/app/info_dialog.rs:189
- Interpolated log message defeats structured logging lact-gui/src/app/profiles.rs:355
- Interpolated log message defeats structured logging lact-gui/src/app/pages/oc_page.rs:347
- No ADRs found lact/src/main.rs:1
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No changelog
- Duplicated predicate lact-daemon/src/server/gpu_controller/amd.rs:322
Minor — 6 finding(s)
- Outdated: cairo-rs
- Outdated: jiff
- Outdated: notify
- Outdated: rust-embed
- Outdated: ureq
- Outdated: zbus
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-ac6642ef539a4b7f9e7eef199b612792/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-ac6642ef539a4b7f9e7eef199b612792/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 --exclude lact-daemon/include . | 18 | 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 . | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 23 | 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 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |