Executive summary
youki-dev/youki meets our standard for a preview release, though it has pipeline tools referenced by a changeable name. It scores 67 out of 100 and is rated Strong, and 117 of its 123 critical findings are security problems.
Security and Compliance, at 57, is the weakest lens and counts most in the score. The best first steps are fixing the password or key in the code and fixing the product with no limit on what it can connect to, each worth about 2 points. Raising Security and Compliance to 68 would lift the score to about 72.
Ninety-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Ten settings leave the servers or containers unsafe, and five secrets can leak from the build pipeline. Pinning each tool to an exact version, correcting the unsafe settings and limiting each secret to its own step would close these risks. Passing outside input through environment variables would fix the three pipeline steps that put outside input straight into a shell command, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The six parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 41,060 lines, about €72,000 to rebuild.
If Security and Compliance rose from 57 to 68, the lowest score rated Strong, the score would rise from 67 to about 72.
New since the last survey: 34 findings
- Cyclomatic Complexity · Memory::apply (cyclomatic 16) crates/libcgroups/src/v2/memory.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Knowledge Freshness · Orphaned knowledge experiment/seccomp/src/seccomp.rs
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 7 findings
- Churn × Complexity Hotspots · Hotspot: crates/libcontainer/src/container/container_checkpoint.rs crates/libcontainer/src/container/container_checkpoint.rs
- Explicit Debt · TodoComment crates/libcontainer/src/process/init/process.rs
- Dependency Vulnerabilities · Medium advisory (unsound): REDACTED REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0316 REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €72,000 · Estimate
| Cost to rebuild | €24,000 to €120,000, for 400 to 1,268 hours of work, about 0.5 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 67. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 41,060 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 libcgroups.common | 2 libcgroups.stats | 3 libcgroups.systemd.dbus_native.message | 4 libcontainer.container.state | 5 libcontainer.namespaces | 6 libcontainer.network.traits | 7 liboci_cli.spec | 8 libcgroups.systemd.controller | 9 libcgroups.systemd.dbus_native.proxy | 10 libcontainer.config | 11 libcontainer.container.container | 12 libcontainer.container.init_builder | 13 libcontainer.network.wrapper | 14 libcontainer.process.channel | 15 libcontainer.user_ns | 16 libcontainer.workload | 17 libcgroups.systemd.dbus_native.dbus | 18 libcgroups.v1.blkio | 19 libcgroups.v1.cpu | 20 libcgroups.v1.cpuacct | 21 libcgroups.v1.hugetlb | 22 libcgroups.v1.memory | 23 libcgroups.v1.pids | 24 libcgroups.v2.cpu | 25 libcgroups.v2.hugetlb | 26 libcgroups.v2.io | 27 libcgroups.v2.memory | 28 libcgroups.v2.pids | 29 libcontainer.container.tenant_builder | 30 libcontainer.network.address | 31 libcontainer.syscall.linux | 32 libcontainer.rootfs.mount | 33 libcontainer.syscall.syscall | 34 libcontainer.container.builder | 35 libcontainer.process.args | 36 libcontainer.container.builder_impl | 37 libcontainer.process.container_intermediate_process | 38 libcontainer.process.container_main_process | 39 libcontainer.process.init.context | 40 libcontainer.process.init.process |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 libcgroups.common | ||||||||||||||||||||||||||||||||||||||||
| 2 libcgroups.stats | ||||||||||||||||||||||||||||||||||||||||
| 3 libcgroups.systemd.dbus_native.message | ||||||||||||||||||||||||||||||||||||||||
| 4 libcontainer.container.state | ||||||||||||||||||||||||||||||||||||||||
| 5 libcontainer.namespaces | ||||||||||||||||||||||||||||||||||||||||
| 6 libcontainer.network.traits | ||||||||||||||||||||||||||||||||||||||||
| 7 liboci_cli.spec | ||||||||||||||||||||||||||||||||||||||||
| 8 libcgroups.systemd.controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 libcgroups.systemd.dbus_native.proxy | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 libcontainer.config | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 libcontainer.container.container | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 libcontainer.container.init_builder | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 libcontainer.network.wrapper | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 libcontainer.process.channel | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 libcontainer.user_ns | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 libcontainer.workload | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 libcgroups.systemd.dbus_native.dbus | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 libcgroups.v1.blkio | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 libcgroups.v1.cpu | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 libcgroups.v1.cpuacct | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 libcgroups.v1.hugetlb | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 libcgroups.v1.memory | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 libcgroups.v1.pids | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 libcgroups.v2.cpu | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 libcgroups.v2.hugetlb | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 libcgroups.v2.io | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 libcgroups.v2.memory | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 libcgroups.v2.pids | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 libcontainer.container.tenant_builder | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 libcontainer.network.address | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 libcontainer.syscall.linux | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 libcontainer.rootfs.mount | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 libcontainer.syscall.syscall | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 libcontainer.container.builder | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 libcontainer.process.args | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 libcontainer.container.builder_impl | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 libcontainer.process.container_intermediate_process | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 libcontainer.process.container_main_process | 3 | 1 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 39 libcontainer.process.init.context | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 libcontainer.process.init.process | 1 | 1 | 2 | 1 | 1 |
8→1 libcgroups.systemd.controller uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcgroups.systemd.controller uses a type in libcgroups.common.
- The types involved
libcgroups.systemd.controller.Controller→libcgroups.common.ControllerOpt
- Direction
- libcgroups.systemd.controller uses libcgroups.common, so a change to libcgroups.common can break libcgroups.systemd.controller, while a change to libcgroups.systemd.controller can't break libcgroups.common.
- Position
- Below the diagonal: libcgroups.systemd.controller uses a module listed above it, which is the healthy direction.
9→17 libcgroups.systemd.dbus_native.proxy uses libcgroups.systemd.dbus_native.dbus part of a loop✕
- Connections
- 1 pair of types, where a type in libcgroups.systemd.dbus_native.proxy uses a type in libcgroups.systemd.dbus_native.dbus.
- The types involved
libcgroups.systemd.dbus_native.proxy.Proxy→libcgroups.systemd.dbus_native.dbus.DbusConnection
- Direction
- libcgroups.systemd.dbus_native.proxy uses libcgroups.systemd.dbus_native.dbus, so a change to libcgroups.systemd.dbus_native.dbus can break libcgroups.systemd.dbus_native.proxy, while a change to libcgroups.systemd.dbus_native.proxy can't break libcgroups.systemd.dbus_native.dbus.
- 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.
10→7 libcontainer.config uses liboci_cli.spec✕
- Connections
- 1 pair of types, where a type in libcontainer.config uses a type in liboci_cli.spec.
- The types involved
libcontainer.config.YoukiConfig→liboci_cli.spec.Spec
- Direction
- libcontainer.config uses liboci_cli.spec, so a change to liboci_cli.spec can break libcontainer.config, while a change to libcontainer.config can't break liboci_cli.spec.
- Position
- Below the diagonal: libcontainer.config uses a module listed above it, which is the healthy direction.
11→4 libcontainer.container.container uses libcontainer.container.state✕
- Connections
- 2 pairs of types, where a type in libcontainer.container.container uses a type in libcontainer.container.state.
- The types involved
libcontainer.container.container.Container→libcontainer.container.state.ContainerStatuslibcontainer.container.container.Container→libcontainer.container.state.State
- Direction
- libcontainer.container.container uses libcontainer.container.state, so a change to libcontainer.container.state can break libcontainer.container.container, while a change to libcontainer.container.container can't break libcontainer.container.state.
- Position
- Below the diagonal: libcontainer.container.container uses a module listed above it, which is the healthy direction.
12→7 libcontainer.container.init_builder uses liboci_cli.spec✕
- Connections
- 1 pair of types, where a type in libcontainer.container.init_builder uses a type in liboci_cli.spec.
- The types involved
libcontainer.container.init_builder.InitContainerBuilder→liboci_cli.spec.Spec
- Direction
- libcontainer.container.init_builder uses liboci_cli.spec, so a change to liboci_cli.spec can break libcontainer.container.init_builder, while a change to libcontainer.container.init_builder can't break liboci_cli.spec.
- Position
- Below the diagonal: libcontainer.container.init_builder uses a module listed above it, which is the healthy direction.
12→34 libcontainer.container.init_builder uses libcontainer.container.builder part of a loop✕
- Connections
- 1 pair of types, where a type in libcontainer.container.init_builder uses a type in libcontainer.container.builder.
- The types involved
libcontainer.container.init_builder.InitContainerBuilder→libcontainer.container.builder.ContainerBuilder
- Direction
- libcontainer.container.init_builder uses libcontainer.container.builder, so a change to libcontainer.container.builder can break libcontainer.container.init_builder, while a change to libcontainer.container.init_builder can't break libcontainer.container.builder.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→6 libcontainer.network.wrapper uses libcontainer.network.traits✕
- Connections
- 1 pair of types, where a type in libcontainer.network.wrapper uses a type in libcontainer.network.traits.
- The types involved
libcontainer.network.wrapper.ClientWrapper→libcontainer.network.traits.Client
- Direction
- libcontainer.network.wrapper uses libcontainer.network.traits, so a change to libcontainer.network.traits can break libcontainer.network.wrapper, while a change to libcontainer.network.wrapper can't break libcontainer.network.traits.
- Position
- Below the diagonal: libcontainer.network.wrapper uses a module listed above it, which is the healthy direction.
14→3 libcontainer.process.channel uses libcgroups.systemd.dbus_native.message✕
- Connections
- 1 pair of types, where a type in libcontainer.process.channel uses a type in libcgroups.systemd.dbus_native.message.
- The types involved
libcontainer.process.channel.ChannelError→libcgroups.systemd.dbus_native.message.Message
- Direction
- libcontainer.process.channel uses libcgroups.systemd.dbus_native.message, so a change to libcgroups.systemd.dbus_native.message can break libcontainer.process.channel, while a change to libcontainer.process.channel can't break libcgroups.systemd.dbus_native.message.
- Position
- Below the diagonal: libcontainer.process.channel uses a module listed above it, which is the healthy direction.
15→7 libcontainer.user_ns uses liboci_cli.spec✕
- Connections
- 2 pairs of types, where a type in libcontainer.user_ns uses a type in liboci_cli.spec.
- The types involved
libcontainer.user_ns.UserNamespaceConfig→liboci_cli.spec.Speclibcontainer.user_ns.user_ns$module→liboci_cli.spec.Spec
- Direction
- libcontainer.user_ns uses liboci_cli.spec, so a change to liboci_cli.spec can break libcontainer.user_ns, while a change to libcontainer.user_ns can't break liboci_cli.spec.
- Position
- Below the diagonal: libcontainer.user_ns uses a module listed above it, which is the healthy direction.
16→7 libcontainer.workload uses liboci_cli.spec✕
- Connections
- 1 pair of types, where a type in libcontainer.workload uses a type in liboci_cli.spec.
- The types involved
libcontainer.workload.Executor→liboci_cli.spec.Spec
- Direction
- libcontainer.workload uses liboci_cli.spec, so a change to liboci_cli.spec can break libcontainer.workload, while a change to libcontainer.workload can't break liboci_cli.spec.
- Position
- Below the diagonal: libcontainer.workload uses a module listed above it, which is the healthy direction.
17→3 libcgroups.systemd.dbus_native.dbus uses libcgroups.systemd.dbus_native.message✕
- Connections
- 2 pairs of types, where a type in libcgroups.systemd.dbus_native.dbus uses a type in libcgroups.systemd.dbus_native.message.
- The types involved
libcgroups.systemd.dbus_native.dbus.DbusConnection→libcgroups.systemd.dbus_native.message.Headerlibcgroups.systemd.dbus_native.dbus.DbusConnection→libcgroups.systemd.dbus_native.message.MessageType
- Direction
- libcgroups.systemd.dbus_native.dbus uses libcgroups.systemd.dbus_native.message, so a change to libcgroups.systemd.dbus_native.message can break libcgroups.systemd.dbus_native.dbus, while a change to libcgroups.systemd.dbus_native.dbus can't break libcgroups.systemd.dbus_native.message.
- Position
- Below the diagonal: libcgroups.systemd.dbus_native.dbus uses a module listed above it, which is the healthy direction.
17→9 libcgroups.systemd.dbus_native.dbus uses libcgroups.systemd.dbus_native.proxy✕
- Connections
- 1 pair of types, where a type in libcgroups.systemd.dbus_native.dbus uses a type in libcgroups.systemd.dbus_native.proxy.
- The types involved
libcgroups.systemd.dbus_native.dbus.DbusConnection→libcgroups.systemd.dbus_native.proxy.Proxy
- Direction
- libcgroups.systemd.dbus_native.dbus uses libcgroups.systemd.dbus_native.proxy, so a change to libcgroups.systemd.dbus_native.proxy can break libcgroups.systemd.dbus_native.dbus, while a change to libcgroups.systemd.dbus_native.dbus can't break libcgroups.systemd.dbus_native.proxy.
- Position
- Below the diagonal: libcgroups.systemd.dbus_native.dbus uses a module listed above it, which is the healthy direction.
18→1 libcgroups.v1.blkio uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.blkio uses a type in libcgroups.common.
- The types involved
libcgroups.v1.blkio.Blkio→libcgroups.common.ControllerOpt
- Direction
- libcgroups.v1.blkio uses libcgroups.common, so a change to libcgroups.common can break libcgroups.v1.blkio, while a change to libcgroups.v1.blkio can't break libcgroups.common.
- Position
- Below the diagonal: libcgroups.v1.blkio uses a module listed above it, which is the healthy direction.
18→2 libcgroups.v1.blkio uses libcgroups.stats✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.blkio uses a type in libcgroups.stats.
- The types involved
libcgroups.v1.blkio.Blkio→libcgroups.stats.StatsProvider
- Direction
- libcgroups.v1.blkio uses libcgroups.stats, so a change to libcgroups.stats can break libcgroups.v1.blkio, while a change to libcgroups.v1.blkio can't break libcgroups.stats.
- Position
- Below the diagonal: libcgroups.v1.blkio uses a module listed above it, which is the healthy direction.
18→8 libcgroups.v1.blkio uses libcgroups.systemd.controller✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.blkio uses a type in libcgroups.systemd.controller.
- The types involved
libcgroups.v1.blkio.Blkio→libcgroups.systemd.controller.Controller
- Direction
- libcgroups.v1.blkio uses libcgroups.systemd.controller, so a change to libcgroups.systemd.controller can break libcgroups.v1.blkio, while a change to libcgroups.v1.blkio can't break libcgroups.systemd.controller.
- Position
- Below the diagonal: libcgroups.v1.blkio uses a module listed above it, which is the healthy direction.
19→1 libcgroups.v1.cpu uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.cpu uses a type in libcgroups.common.
- The types involved
libcgroups.v1.cpu.Cpu→libcgroups.common.ControllerOpt
- Direction
- libcgroups.v1.cpu uses libcgroups.common, so a change to libcgroups.common can break libcgroups.v1.cpu, while a change to libcgroups.v1.cpu can't break libcgroups.common.
- Position
- Below the diagonal: libcgroups.v1.cpu uses a module listed above it, which is the healthy direction.
19→2 libcgroups.v1.cpu uses libcgroups.stats✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.cpu uses a type in libcgroups.stats.
- The types involved
libcgroups.v1.cpu.Cpu→libcgroups.stats.StatsProvider
- Direction
- libcgroups.v1.cpu uses libcgroups.stats, so a change to libcgroups.stats can break libcgroups.v1.cpu, while a change to libcgroups.v1.cpu can't break libcgroups.stats.
- Position
- Below the diagonal: libcgroups.v1.cpu uses a module listed above it, which is the healthy direction.
19→8 libcgroups.v1.cpu uses libcgroups.systemd.controller✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.cpu uses a type in libcgroups.systemd.controller.
- The types involved
libcgroups.v1.cpu.Cpu→libcgroups.systemd.controller.Controller
- Direction
- libcgroups.v1.cpu uses libcgroups.systemd.controller, so a change to libcgroups.systemd.controller can break libcgroups.v1.cpu, while a change to libcgroups.v1.cpu can't break libcgroups.systemd.controller.
- Position
- Below the diagonal: libcgroups.v1.cpu uses a module listed above it, which is the healthy direction.
20→1 libcgroups.v1.cpuacct uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.cpuacct uses a type in libcgroups.common.
- The types involved
libcgroups.v1.cpuacct.CpuAcct→libcgroups.common.ControllerOpt
- Direction
- libcgroups.v1.cpuacct uses libcgroups.common, so a change to libcgroups.common can break libcgroups.v1.cpuacct, while a change to libcgroups.v1.cpuacct can't break libcgroups.common.
- Position
- Below the diagonal: libcgroups.v1.cpuacct uses a module listed above it, which is the healthy direction.
20→2 libcgroups.v1.cpuacct uses libcgroups.stats✕
- Connections
- 2 pairs of types, where a type in libcgroups.v1.cpuacct uses a type in libcgroups.stats.
- The types involved
libcgroups.v1.cpuacct.CpuAcct→libcgroups.stats.CpuUsagelibcgroups.v1.cpuacct.CpuAcct→libcgroups.stats.StatsProvider
- Direction
- libcgroups.v1.cpuacct uses libcgroups.stats, so a change to libcgroups.stats can break libcgroups.v1.cpuacct, while a change to libcgroups.v1.cpuacct can't break libcgroups.stats.
- Position
- Below the diagonal: libcgroups.v1.cpuacct uses a module listed above it, which is the healthy direction.
20→8 libcgroups.v1.cpuacct uses libcgroups.systemd.controller✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.cpuacct uses a type in libcgroups.systemd.controller.
- The types involved
libcgroups.v1.cpuacct.CpuAcct→libcgroups.systemd.controller.Controller
- Direction
- libcgroups.v1.cpuacct uses libcgroups.systemd.controller, so a change to libcgroups.systemd.controller can break libcgroups.v1.cpuacct, while a change to libcgroups.v1.cpuacct can't break libcgroups.systemd.controller.
- Position
- Below the diagonal: libcgroups.v1.cpuacct uses a module listed above it, which is the healthy direction.
21→1 libcgroups.v1.hugetlb uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.hugetlb uses a type in libcgroups.common.
- The types involved
libcgroups.v1.hugetlb.HugeTlb→libcgroups.common.ControllerOpt
- Direction
- libcgroups.v1.hugetlb uses libcgroups.common, so a change to libcgroups.common can break libcgroups.v1.hugetlb, while a change to libcgroups.v1.hugetlb can't break libcgroups.common.
- Position
- Below the diagonal: libcgroups.v1.hugetlb uses a module listed above it, which is the healthy direction.
21→2 libcgroups.v1.hugetlb uses libcgroups.stats✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.hugetlb uses a type in libcgroups.stats.
- The types involved
libcgroups.v1.hugetlb.HugeTlb→libcgroups.stats.StatsProvider
- Direction
- libcgroups.v1.hugetlb uses libcgroups.stats, so a change to libcgroups.stats can break libcgroups.v1.hugetlb, while a change to libcgroups.v1.hugetlb can't break libcgroups.stats.
- Position
- Below the diagonal: libcgroups.v1.hugetlb uses a module listed above it, which is the healthy direction.
21→8 libcgroups.v1.hugetlb uses libcgroups.systemd.controller✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.hugetlb uses a type in libcgroups.systemd.controller.
- The types involved
libcgroups.v1.hugetlb.HugeTlb→libcgroups.systemd.controller.Controller
- Direction
- libcgroups.v1.hugetlb uses libcgroups.systemd.controller, so a change to libcgroups.systemd.controller can break libcgroups.v1.hugetlb, while a change to libcgroups.v1.hugetlb can't break libcgroups.systemd.controller.
- Position
- Below the diagonal: libcgroups.v1.hugetlb uses a module listed above it, which is the healthy direction.
22→1 libcgroups.v1.memory uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.memory uses a type in libcgroups.common.
- The types involved
libcgroups.v1.memory.Memory→libcgroups.common.ControllerOpt
- Direction
- libcgroups.v1.memory uses libcgroups.common, so a change to libcgroups.common can break libcgroups.v1.memory, while a change to libcgroups.v1.memory can't break libcgroups.common.
- Position
- Below the diagonal: libcgroups.v1.memory uses a module listed above it, which is the healthy direction.
22→2 libcgroups.v1.memory uses libcgroups.stats✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.memory uses a type in libcgroups.stats.
- The types involved
libcgroups.v1.memory.Memory→libcgroups.stats.StatsProvider
- Direction
- libcgroups.v1.memory uses libcgroups.stats, so a change to libcgroups.stats can break libcgroups.v1.memory, while a change to libcgroups.v1.memory can't break libcgroups.stats.
- Position
- Below the diagonal: libcgroups.v1.memory uses a module listed above it, which is the healthy direction.
22→8 libcgroups.v1.memory uses libcgroups.systemd.controller✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.memory uses a type in libcgroups.systemd.controller.
- The types involved
libcgroups.v1.memory.Memory→libcgroups.systemd.controller.Controller
- Direction
- libcgroups.v1.memory uses libcgroups.systemd.controller, so a change to libcgroups.systemd.controller can break libcgroups.v1.memory, while a change to libcgroups.v1.memory can't break libcgroups.systemd.controller.
- Position
- Below the diagonal: libcgroups.v1.memory uses a module listed above it, which is the healthy direction.
23→1 libcgroups.v1.pids uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.pids uses a type in libcgroups.common.
- The types involved
libcgroups.v1.pids.Pids→libcgroups.common.ControllerOpt
- Direction
- libcgroups.v1.pids uses libcgroups.common, so a change to libcgroups.common can break libcgroups.v1.pids, while a change to libcgroups.v1.pids can't break libcgroups.common.
- Position
- Below the diagonal: libcgroups.v1.pids uses a module listed above it, which is the healthy direction.
23→2 libcgroups.v1.pids uses libcgroups.stats✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.pids uses a type in libcgroups.stats.
- The types involved
libcgroups.v1.pids.Pids→libcgroups.stats.StatsProvider
- Direction
- libcgroups.v1.pids uses libcgroups.stats, so a change to libcgroups.stats can break libcgroups.v1.pids, while a change to libcgroups.v1.pids can't break libcgroups.stats.
- Position
- Below the diagonal: libcgroups.v1.pids uses a module listed above it, which is the healthy direction.
23→8 libcgroups.v1.pids uses libcgroups.systemd.controller✕
- Connections
- 1 pair of types, where a type in libcgroups.v1.pids uses a type in libcgroups.systemd.controller.
- The types involved
libcgroups.v1.pids.Pids→libcgroups.systemd.controller.Controller
- Direction
- libcgroups.v1.pids uses libcgroups.systemd.controller, so a change to libcgroups.systemd.controller can break libcgroups.v1.pids, while a change to libcgroups.v1.pids can't break libcgroups.systemd.controller.
- Position
- Below the diagonal: libcgroups.v1.pids uses a module listed above it, which is the healthy direction.
24→1 libcgroups.v2.cpu uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.cpu uses a type in libcgroups.common.
- The types involved
libcgroups.v2.cpu.Cpu→libcgroups.common.ControllerOpt
- Direction
- libcgroups.v2.cpu uses libcgroups.common, so a change to libcgroups.common can break libcgroups.v2.cpu, while a change to libcgroups.v2.cpu can't break libcgroups.common.
- Position
- Below the diagonal: libcgroups.v2.cpu uses a module listed above it, which is the healthy direction.
24→2 libcgroups.v2.cpu uses libcgroups.stats✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.cpu uses a type in libcgroups.stats.
- The types involved
libcgroups.v2.cpu.Cpu→libcgroups.stats.StatsProvider
- Direction
- libcgroups.v2.cpu uses libcgroups.stats, so a change to libcgroups.stats can break libcgroups.v2.cpu, while a change to libcgroups.v2.cpu can't break libcgroups.stats.
- Position
- Below the diagonal: libcgroups.v2.cpu uses a module listed above it, which is the healthy direction.
24→8 libcgroups.v2.cpu uses libcgroups.systemd.controller✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.cpu uses a type in libcgroups.systemd.controller.
- The types involved
libcgroups.v2.cpu.Cpu→libcgroups.systemd.controller.Controller
- Direction
- libcgroups.v2.cpu uses libcgroups.systemd.controller, so a change to libcgroups.systemd.controller can break libcgroups.v2.cpu, while a change to libcgroups.v2.cpu can't break libcgroups.systemd.controller.
- Position
- Below the diagonal: libcgroups.v2.cpu uses a module listed above it, which is the healthy direction.
25→1 libcgroups.v2.hugetlb uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.hugetlb uses a type in libcgroups.common.
- The types involved
libcgroups.v2.hugetlb.HugeTlb→libcgroups.common.ControllerOpt
- Direction
- libcgroups.v2.hugetlb uses libcgroups.common, so a change to libcgroups.common can break libcgroups.v2.hugetlb, while a change to libcgroups.v2.hugetlb can't break libcgroups.common.
- Position
- Below the diagonal: libcgroups.v2.hugetlb uses a module listed above it, which is the healthy direction.
25→2 libcgroups.v2.hugetlb uses libcgroups.stats✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.hugetlb uses a type in libcgroups.stats.
- The types involved
libcgroups.v2.hugetlb.HugeTlb→libcgroups.stats.StatsProvider
- Direction
- libcgroups.v2.hugetlb uses libcgroups.stats, so a change to libcgroups.stats can break libcgroups.v2.hugetlb, while a change to libcgroups.v2.hugetlb can't break libcgroups.stats.
- Position
- Below the diagonal: libcgroups.v2.hugetlb uses a module listed above it, which is the healthy direction.
25→8 libcgroups.v2.hugetlb uses libcgroups.systemd.controller✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.hugetlb uses a type in libcgroups.systemd.controller.
- The types involved
libcgroups.v2.hugetlb.HugeTlb→libcgroups.systemd.controller.Controller
- Direction
- libcgroups.v2.hugetlb uses libcgroups.systemd.controller, so a change to libcgroups.systemd.controller can break libcgroups.v2.hugetlb, while a change to libcgroups.v2.hugetlb can't break libcgroups.systemd.controller.
- Position
- Below the diagonal: libcgroups.v2.hugetlb uses a module listed above it, which is the healthy direction.
26→1 libcgroups.v2.io uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.io uses a type in libcgroups.common.
- The types involved
libcgroups.v2.io.Io→libcgroups.common.ControllerOpt
- Direction
- libcgroups.v2.io uses libcgroups.common, so a change to libcgroups.common can break libcgroups.v2.io, while a change to libcgroups.v2.io can't break libcgroups.common.
- Position
- Below the diagonal: libcgroups.v2.io uses a module listed above it, which is the healthy direction.
26→2 libcgroups.v2.io uses libcgroups.stats✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.io uses a type in libcgroups.stats.
- The types involved
libcgroups.v2.io.Io→libcgroups.stats.StatsProvider
- Direction
- libcgroups.v2.io uses libcgroups.stats, so a change to libcgroups.stats can break libcgroups.v2.io, while a change to libcgroups.v2.io can't break libcgroups.stats.
- Position
- Below the diagonal: libcgroups.v2.io uses a module listed above it, which is the healthy direction.
26→8 libcgroups.v2.io uses libcgroups.systemd.controller✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.io uses a type in libcgroups.systemd.controller.
- The types involved
libcgroups.v2.io.Io→libcgroups.systemd.controller.Controller
- Direction
- libcgroups.v2.io uses libcgroups.systemd.controller, so a change to libcgroups.systemd.controller can break libcgroups.v2.io, while a change to libcgroups.v2.io can't break libcgroups.systemd.controller.
- Position
- Below the diagonal: libcgroups.v2.io uses a module listed above it, which is the healthy direction.
27→1 libcgroups.v2.memory uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.memory uses a type in libcgroups.common.
- The types involved
libcgroups.v2.memory.Memory→libcgroups.common.ControllerOpt
- Direction
- libcgroups.v2.memory uses libcgroups.common, so a change to libcgroups.common can break libcgroups.v2.memory, while a change to libcgroups.v2.memory can't break libcgroups.common.
- Position
- Below the diagonal: libcgroups.v2.memory uses a module listed above it, which is the healthy direction.
27→2 libcgroups.v2.memory uses libcgroups.stats✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.memory uses a type in libcgroups.stats.
- The types involved
libcgroups.v2.memory.Memory→libcgroups.stats.StatsProvider
- Direction
- libcgroups.v2.memory uses libcgroups.stats, so a change to libcgroups.stats can break libcgroups.v2.memory, while a change to libcgroups.v2.memory can't break libcgroups.stats.
- Position
- Below the diagonal: libcgroups.v2.memory uses a module listed above it, which is the healthy direction.
27→8 libcgroups.v2.memory uses libcgroups.systemd.controller✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.memory uses a type in libcgroups.systemd.controller.
- The types involved
libcgroups.v2.memory.Memory→libcgroups.systemd.controller.Controller
- Direction
- libcgroups.v2.memory uses libcgroups.systemd.controller, so a change to libcgroups.systemd.controller can break libcgroups.v2.memory, while a change to libcgroups.v2.memory can't break libcgroups.systemd.controller.
- Position
- Below the diagonal: libcgroups.v2.memory uses a module listed above it, which is the healthy direction.
28→1 libcgroups.v2.pids uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.pids uses a type in libcgroups.common.
- The types involved
libcgroups.v2.pids.Pids→libcgroups.common.ControllerOpt
- Direction
- libcgroups.v2.pids uses libcgroups.common, so a change to libcgroups.common can break libcgroups.v2.pids, while a change to libcgroups.v2.pids can't break libcgroups.common.
- Position
- Below the diagonal: libcgroups.v2.pids uses a module listed above it, which is the healthy direction.
28→2 libcgroups.v2.pids uses libcgroups.stats✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.pids uses a type in libcgroups.stats.
- The types involved
libcgroups.v2.pids.Pids→libcgroups.stats.StatsProvider
- Direction
- libcgroups.v2.pids uses libcgroups.stats, so a change to libcgroups.stats can break libcgroups.v2.pids, while a change to libcgroups.v2.pids can't break libcgroups.stats.
- Position
- Below the diagonal: libcgroups.v2.pids uses a module listed above it, which is the healthy direction.
28→8 libcgroups.v2.pids uses libcgroups.systemd.controller✕
- Connections
- 1 pair of types, where a type in libcgroups.v2.pids uses a type in libcgroups.systemd.controller.
- The types involved
libcgroups.v2.pids.Pids→libcgroups.systemd.controller.Controller
- Direction
- libcgroups.v2.pids uses libcgroups.systemd.controller, so a change to libcgroups.systemd.controller can break libcgroups.v2.pids, while a change to libcgroups.v2.pids can't break libcgroups.systemd.controller.
- Position
- Below the diagonal: libcgroups.v2.pids uses a module listed above it, which is the healthy direction.
29→7 libcontainer.container.tenant_builder uses liboci_cli.spec✕
- Connections
- 2 pairs of types, where a type in libcontainer.container.tenant_builder uses a type in liboci_cli.spec.
- The types involved
libcontainer.container.tenant_builder.TenantContainerBuilder→liboci_cli.spec.Speclibcontainer.container.tenant_builder.tenant_builder$module→liboci_cli.spec.Spec
- Direction
- libcontainer.container.tenant_builder uses liboci_cli.spec, so a change to liboci_cli.spec can break libcontainer.container.tenant_builder, while a change to libcontainer.container.tenant_builder can't break liboci_cli.spec.
- Position
- Below the diagonal: libcontainer.container.tenant_builder uses a module listed above it, which is the healthy direction.
29→11 libcontainer.container.tenant_builder uses libcontainer.container.container✕
- Connections
- 1 pair of types, where a type in libcontainer.container.tenant_builder uses a type in libcontainer.container.container.
- The types involved
libcontainer.container.tenant_builder.TenantContainerBuilder→libcontainer.container.container.Container
- Direction
- libcontainer.container.tenant_builder uses libcontainer.container.container, so a change to libcontainer.container.container can break libcontainer.container.tenant_builder, while a change to libcontainer.container.tenant_builder can't break libcontainer.container.container.
- Position
- Below the diagonal: libcontainer.container.tenant_builder uses a module listed above it, which is the healthy direction.
29→34 libcontainer.container.tenant_builder uses libcontainer.container.builder part of a loop✕
- Connections
- 1 pair of types, where a type in libcontainer.container.tenant_builder uses a type in libcontainer.container.builder.
- The types involved
libcontainer.container.tenant_builder.TenantContainerBuilder→libcontainer.container.builder.ContainerBuilder
- Direction
- libcontainer.container.tenant_builder uses libcontainer.container.builder, so a change to libcontainer.container.builder can break libcontainer.container.tenant_builder, while a change to libcontainer.container.tenant_builder can't break libcontainer.container.builder.
- 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.
30→6 libcontainer.network.address uses libcontainer.network.traits✕
- Connections
- 1 pair of types, where a type in libcontainer.network.address uses a type in libcontainer.network.traits.
- The types involved
libcontainer.network.address.AddressMessageHandler→libcontainer.network.traits.NetlinkMessageHandler
- Direction
- libcontainer.network.address uses libcontainer.network.traits, so a change to libcontainer.network.traits can break libcontainer.network.address, while a change to libcontainer.network.address can't break libcontainer.network.traits.
- Position
- Below the diagonal: libcontainer.network.address uses a module listed above it, which is the healthy direction.
30→13 libcontainer.network.address uses libcontainer.network.wrapper✕
- Connections
- 1 pair of types, where a type in libcontainer.network.address uses a type in libcontainer.network.wrapper.
- The types involved
libcontainer.network.address.AddressClient→libcontainer.network.wrapper.ClientWrapper
- Direction
- libcontainer.network.address uses libcontainer.network.wrapper, so a change to libcontainer.network.wrapper can break libcontainer.network.address, while a change to libcontainer.network.address can't break libcontainer.network.wrapper.
- Position
- Below the diagonal: libcontainer.network.address uses a module listed above it, which is the healthy direction.
31→10 libcontainer.syscall.linux uses libcontainer.config✕
- Connections
- 1 pair of types, where a type in libcontainer.syscall.linux uses a type in libcontainer.config.
- The types involved
libcontainer.syscall.linux.LinuxSyscall→libcontainer.config.PersonalityDomain
- Direction
- libcontainer.syscall.linux uses libcontainer.config, so a change to libcontainer.config can break libcontainer.syscall.linux, while a change to libcontainer.syscall.linux can't break libcontainer.config.
- Position
- Below the diagonal: libcontainer.syscall.linux uses a module listed above it, which is the healthy direction.
31→33 libcontainer.syscall.linux uses libcontainer.syscall.syscall part of a loop✕
- Connections
- 1 pair of types, where a type in libcontainer.syscall.linux uses a type in libcontainer.syscall.syscall.
- The types involved
libcontainer.syscall.linux.LinuxSyscall→libcontainer.syscall.syscall.Syscall
- Direction
- libcontainer.syscall.linux uses libcontainer.syscall.syscall, so a change to libcontainer.syscall.syscall can break libcontainer.syscall.linux, while a change to libcontainer.syscall.linux can't break libcontainer.syscall.syscall.
- 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.
32→31 libcontainer.rootfs.mount uses libcontainer.syscall.linux✕
- Connections
- 1 pair of types, where a type in libcontainer.rootfs.mount uses a type in libcontainer.syscall.linux.
- The types involved
libcontainer.rootfs.mount.Mount→libcontainer.syscall.linux.MountAttr
- Direction
- libcontainer.rootfs.mount uses libcontainer.syscall.linux, so a change to libcontainer.syscall.linux can break libcontainer.rootfs.mount, while a change to libcontainer.rootfs.mount can't break libcontainer.syscall.linux.
- Position
- Below the diagonal: libcontainer.rootfs.mount uses a module listed above it, which is the healthy direction.
33→10 libcontainer.syscall.syscall uses libcontainer.config✕
- Connections
- 1 pair of types, where a type in libcontainer.syscall.syscall uses a type in libcontainer.config.
- The types involved
libcontainer.syscall.syscall.Syscall→libcontainer.config.PersonalityDomain
- Direction
- libcontainer.syscall.syscall uses libcontainer.config, so a change to libcontainer.config can break libcontainer.syscall.syscall, while a change to libcontainer.syscall.syscall can't break libcontainer.config.
- Position
- Below the diagonal: libcontainer.syscall.syscall uses a module listed above it, which is the healthy direction.
33→31 libcontainer.syscall.syscall uses libcontainer.syscall.linux✕
- Connections
- 1 pair of types, where a type in libcontainer.syscall.syscall uses a type in libcontainer.syscall.linux.
- The types involved
libcontainer.syscall.syscall.Syscall→libcontainer.syscall.linux.MountAttr
- Direction
- libcontainer.syscall.syscall uses libcontainer.syscall.linux, so a change to libcontainer.syscall.linux can break libcontainer.syscall.syscall, while a change to libcontainer.syscall.syscall can't break libcontainer.syscall.linux.
- Position
- Below the diagonal: libcontainer.syscall.syscall uses a module listed above it, which is the healthy direction.
34→7 libcontainer.container.builder uses liboci_cli.spec✕
- Connections
- 1 pair of types, where a type in libcontainer.container.builder uses a type in liboci_cli.spec.
- The types involved
libcontainer.container.builder.ContainerBuilder→liboci_cli.spec.Spec
- Direction
- libcontainer.container.builder uses liboci_cli.spec, so a change to liboci_cli.spec can break libcontainer.container.builder, while a change to libcontainer.container.builder can't break liboci_cli.spec.
- Position
- Below the diagonal: libcontainer.container.builder uses a module listed above it, which is the healthy direction.
34→12 libcontainer.container.builder uses libcontainer.container.init_builder✕
- Connections
- 1 pair of types, where a type in libcontainer.container.builder uses a type in libcontainer.container.init_builder.
- The types involved
libcontainer.container.builder.ContainerBuilder→libcontainer.container.init_builder.InitContainerBuilder
- Direction
- libcontainer.container.builder uses libcontainer.container.init_builder, so a change to libcontainer.container.init_builder can break libcontainer.container.builder, while a change to libcontainer.container.builder can't break libcontainer.container.init_builder.
- Position
- Below the diagonal: libcontainer.container.builder uses a module listed above it, which is the healthy direction.
34→29 libcontainer.container.builder uses libcontainer.container.tenant_builder✕
- Connections
- 1 pair of types, where a type in libcontainer.container.builder uses a type in libcontainer.container.tenant_builder.
- The types involved
libcontainer.container.builder.ContainerBuilder→libcontainer.container.tenant_builder.TenantContainerBuilder
- Direction
- libcontainer.container.builder uses libcontainer.container.tenant_builder, so a change to libcontainer.container.tenant_builder can break libcontainer.container.builder, while a change to libcontainer.container.builder can't break libcontainer.container.tenant_builder.
- Position
- Below the diagonal: libcontainer.container.builder uses a module listed above it, which is the healthy direction.
34→33 libcontainer.container.builder uses libcontainer.syscall.syscall✕
- Connections
- 1 pair of types, where a type in libcontainer.container.builder uses a type in libcontainer.syscall.syscall.
- The types involved
libcontainer.container.builder.ContainerBuilder→libcontainer.syscall.syscall.SyscallType
- Direction
- libcontainer.container.builder uses libcontainer.syscall.syscall, so a change to libcontainer.syscall.syscall can break libcontainer.container.builder, while a change to libcontainer.container.builder can't break libcontainer.syscall.syscall.
- Position
- Below the diagonal: libcontainer.container.builder uses a module listed above it, which is the healthy direction.
35→1 libcontainer.process.args uses libcgroups.common✕
- Connections
- 1 pair of types, where a type in libcontainer.process.args uses a type in libcgroups.common.
- The types involved
libcontainer.process.args.ContainerArgs→libcgroups.common.CgroupConfig
- Direction
- libcontainer.process.args uses libcgroups.common, so a change to libcgroups.common can break libcontainer.process.args, while a change to libcontainer.process.args can't break libcgroups.common.
- Position
- Below the diagonal: libcontainer.process.args uses a module listed above it, which is the healthy direction.
35→7 libcontainer.process.args uses liboci_cli.spec✕
- Connections
- 1 pair of types, where a type in libcontainer.process.args uses a type in liboci_cli.spec.
- The types involved
libcontainer.process.args.ContainerArgs→liboci_cli.spec.Spec
- Direction
- libcontainer.process.args uses liboci_cli.spec, so a change to liboci_cli.spec can break libcontainer.process.args, while a change to libcontainer.process.args can't break liboci_cli.spec.
- Position
- Below the diagonal: libcontainer.process.args uses a module listed above it, which is the healthy direction.
35→11 libcontainer.process.args uses libcontainer.container.container✕
- Connections
- 1 pair of types, where a type in libcontainer.process.args uses a type in libcontainer.container.container.
- The types involved
libcontainer.process.args.ContainerArgs→libcontainer.container.container.Container
- Direction
- libcontainer.process.args uses libcontainer.container.container, so a change to libcontainer.container.container can break libcontainer.process.args, while a change to libcontainer.process.args can't break libcontainer.container.container.
- Position
- Below the diagonal: libcontainer.process.args uses a module listed above it, which is the healthy direction.
35→15 libcontainer.process.args uses libcontainer.user_ns✕
- Connections
- 1 pair of types, where a type in libcontainer.process.args uses a type in libcontainer.user_ns.
- The types involved
libcontainer.process.args.ContainerArgs→libcontainer.user_ns.UserNamespaceConfig
- Direction
- libcontainer.process.args uses libcontainer.user_ns, so a change to libcontainer.user_ns can break libcontainer.process.args, while a change to libcontainer.process.args can't break libcontainer.user_ns.
- Position
- Below the diagonal: libcontainer.process.args uses a module listed above it, which is the healthy direction.
35→33 libcontainer.process.args uses libcontainer.syscall.syscall✕
- Connections
- 1 pair of types, where a type in libcontainer.process.args uses a type in libcontainer.syscall.syscall.
- The types involved
libcontainer.process.args.ContainerArgs→libcontainer.syscall.syscall.SyscallType
- Direction
- libcontainer.process.args uses libcontainer.syscall.syscall, so a change to libcontainer.syscall.syscall can break libcontainer.process.args, while a change to libcontainer.process.args can't break libcontainer.syscall.syscall.
- Position
- Below the diagonal: libcontainer.process.args uses a module listed above it, which is the healthy direction.
36→7 libcontainer.container.builder_impl uses liboci_cli.spec✕
- Connections
- 1 pair of types, where a type in libcontainer.container.builder_impl uses a type in liboci_cli.spec.
- The types involved
libcontainer.container.builder_impl.ContainerBuilderImpl→liboci_cli.spec.Spec
- Direction
- libcontainer.container.builder_impl uses liboci_cli.spec, so a change to liboci_cli.spec can break libcontainer.container.builder_impl, while a change to libcontainer.container.builder_impl can't break liboci_cli.spec.
- Position
- Below the diagonal: libcontainer.container.builder_impl uses a module listed above it, which is the healthy direction.
36→11 libcontainer.container.builder_impl uses libcontainer.container.container✕
- Connections
- 1 pair of types, where a type in libcontainer.container.builder_impl uses a type in libcontainer.container.container.
- The types involved
libcontainer.container.builder_impl.ContainerBuilderImpl→libcontainer.container.container.Container
- Direction
- libcontainer.container.builder_impl uses libcontainer.container.container, so a change to libcontainer.container.container can break libcontainer.container.builder_impl, while a change to libcontainer.container.builder_impl can't break libcontainer.container.container.
- Position
- Below the diagonal: libcontainer.container.builder_impl uses a module listed above it, which is the healthy direction.
36→15 libcontainer.container.builder_impl uses libcontainer.user_ns✕
- Connections
- 1 pair of types, where a type in libcontainer.container.builder_impl uses a type in libcontainer.user_ns.
- The types involved
libcontainer.container.builder_impl.ContainerBuilderImpl→libcontainer.user_ns.UserNamespaceConfig
- Direction
- libcontainer.container.builder_impl uses libcontainer.user_ns, so a change to libcontainer.user_ns can break libcontainer.container.builder_impl, while a change to libcontainer.container.builder_impl can't break libcontainer.user_ns.
- Position
- Below the diagonal: libcontainer.container.builder_impl uses a module listed above it, which is the healthy direction.
36→33 libcontainer.container.builder_impl uses libcontainer.syscall.syscall✕
- Connections
- 1 pair of types, where a type in libcontainer.container.builder_impl uses a type in libcontainer.syscall.syscall.
- The types involved
libcontainer.container.builder_impl.ContainerBuilderImpl→libcontainer.syscall.syscall.SyscallType
- Direction
- libcontainer.container.builder_impl uses libcontainer.syscall.syscall, so a change to libcontainer.syscall.syscall can break libcontainer.container.builder_impl, while a change to libcontainer.container.builder_impl can't break libcontainer.syscall.syscall.
- Position
- Below the diagonal: libcontainer.container.builder_impl uses a module listed above it, which is the healthy direction.
36→35 libcontainer.container.builder_impl uses libcontainer.process.args✕
- Connections
- 1 pair of types, where a type in libcontainer.container.builder_impl uses a type in libcontainer.process.args.
- The types involved
libcontainer.container.builder_impl.ContainerBuilderImpl→libcontainer.process.args.ContainerType
- Direction
- libcontainer.container.builder_impl uses libcontainer.process.args, so a change to libcontainer.process.args can break libcontainer.container.builder_impl, while a change to libcontainer.container.builder_impl can't break libcontainer.process.args.
- Position
- Below the diagonal: libcontainer.container.builder_impl uses a module listed above it, which is the healthy direction.
37→5 libcontainer.process.container_intermediate_process uses libcontainer.namespaces✕
- Connections
- 1 pair of types, where a type in libcontainer.process.container_intermediate_process uses a type in libcontainer.namespaces.
- The types involved
libcontainer.process.container_intermediate_process.container_intermediate_process$module→libcontainer.namespaces.Namespaces
- Direction
- libcontainer.process.container_intermediate_process uses libcontainer.namespaces, so a change to libcontainer.namespaces can break libcontainer.process.container_intermediate_process, while a change to libcontainer.process.container_intermediate_process can't break libcontainer.namespaces.
- Position
- Below the diagonal: libcontainer.process.container_intermediate_process uses a module listed above it, which is the healthy direction.
37→14 libcontainer.process.container_intermediate_process uses libcontainer.process.channel✕
- Connections
- 2 pairs of types, where a type in libcontainer.process.container_intermediate_process uses a type in libcontainer.process.channel.
- The types involved
libcontainer.process.container_intermediate_process.container_intermediate_process$module→libcontainer.process.channel.IntermediateReceiverlibcontainer.process.container_intermediate_process.container_intermediate_process$module→libcontainer.process.channel.MainSender
- Direction
- libcontainer.process.container_intermediate_process uses libcontainer.process.channel, so a change to libcontainer.process.channel can break libcontainer.process.container_intermediate_process, while a change to libcontainer.process.container_intermediate_process can't break libcontainer.process.channel.
- Position
- Below the diagonal: libcontainer.process.container_intermediate_process uses a module listed above it, which is the healthy direction.
37→35 libcontainer.process.container_intermediate_process uses libcontainer.process.args✕
- Connections
- 1 pair of types, where a type in libcontainer.process.container_intermediate_process uses a type in libcontainer.process.args.
- The types involved
libcontainer.process.container_intermediate_process.container_intermediate_process$module→libcontainer.process.args.ContainerArgs
- Direction
- libcontainer.process.container_intermediate_process uses libcontainer.process.args, so a change to libcontainer.process.args can break libcontainer.process.container_intermediate_process, while a change to libcontainer.process.container_intermediate_process can't break libcontainer.process.args.
- Position
- Below the diagonal: libcontainer.process.container_intermediate_process uses a module listed above it, which is the healthy direction.
38→3 libcontainer.process.container_main_process uses libcgroups.systemd.dbus_native.message✕
- Connections
- 3 pairs of types, where a type in libcontainer.process.container_main_process uses a type in libcgroups.systemd.dbus_native.message.
- The types involved
libcontainer.process.container_main_process.InitRequest→libcgroups.systemd.dbus_native.message.Messagelibcontainer.process.container_main_process.InitRequestSequence→libcgroups.systemd.dbus_native.message.Messagelibcontainer.process.container_main_process.container_main_process$module→libcgroups.systemd.dbus_native.message.Message
- Direction
- libcontainer.process.container_main_process uses libcgroups.systemd.dbus_native.message, so a change to libcgroups.systemd.dbus_native.message can break libcontainer.process.container_main_process, while a change to libcontainer.process.container_main_process can't break libcgroups.systemd.dbus_native.message.
- Position
- Below the diagonal: libcontainer.process.container_main_process uses a module listed above it, which is the healthy direction.
38→7 libcontainer.process.container_main_process uses liboci_cli.spec✕
- Connections
- 1 pair of types, where a type in libcontainer.process.container_main_process uses a type in liboci_cli.spec.
- The types involved
libcontainer.process.container_main_process.InitRequestSequence→liboci_cli.spec.Spec
- Direction
- libcontainer.process.container_main_process uses liboci_cli.spec, so a change to liboci_cli.spec can break libcontainer.process.container_main_process, while a change to libcontainer.process.container_main_process can't break liboci_cli.spec.
- Position
- Below the diagonal: libcontainer.process.container_main_process uses a module listed above it, which is the healthy direction.
38→11 libcontainer.process.container_main_process uses libcontainer.container.container✕
- Connections
- 1 pair of types, where a type in libcontainer.process.container_main_process uses a type in libcontainer.container.container.
- The types involved
libcontainer.process.container_main_process.container_main_process$module→libcontainer.container.container.Container
- Direction
- libcontainer.process.container_main_process uses libcontainer.container.container, so a change to libcontainer.container.container can break libcontainer.process.container_main_process, while a change to libcontainer.process.container_main_process can't break libcontainer.container.container.
- Position
- Below the diagonal: libcontainer.process.container_main_process uses a module listed above it, which is the healthy direction.
38→14 libcontainer.process.container_main_process uses libcontainer.process.channel✕
- Connections
- 1 pair of types, where a type in libcontainer.process.container_main_process uses a type in libcontainer.process.channel.
- The types involved
libcontainer.process.container_main_process.container_main_process$module→libcontainer.process.channel.InitSender
- Direction
- libcontainer.process.container_main_process uses libcontainer.process.channel, so a change to libcontainer.process.channel can break libcontainer.process.container_main_process, while a change to libcontainer.process.container_main_process can't break libcontainer.process.channel.
- Position
- Below the diagonal: libcontainer.process.container_main_process uses a module listed above it, which is the healthy direction.
38→15 libcontainer.process.container_main_process uses libcontainer.user_ns✕
- Connections
- 1 pair of types, where a type in libcontainer.process.container_main_process uses a type in libcontainer.user_ns.
- The types involved
libcontainer.process.container_main_process.container_main_process$module→libcontainer.user_ns.UserNamespaceConfig
- Direction
- libcontainer.process.container_main_process uses libcontainer.user_ns, so a change to libcontainer.user_ns can break libcontainer.process.container_main_process, while a change to libcontainer.process.container_main_process can't break libcontainer.user_ns.
- Position
- Below the diagonal: libcontainer.process.container_main_process uses a module listed above it, which is the healthy direction.
38→35 libcontainer.process.container_main_process uses libcontainer.process.args✕
- Connections
- 3 pairs of types, where a type in libcontainer.process.container_main_process uses a type in libcontainer.process.args.
- The types involved
libcontainer.process.container_main_process.InitRequestSequence→libcontainer.process.args.ContainerTypelibcontainer.process.container_main_process.container_main_process$module→libcontainer.process.args.ContainerArgslibcontainer.process.container_main_process.container_main_process$module→libcontainer.process.args.ContainerType
- Direction
- libcontainer.process.container_main_process uses libcontainer.process.args, so a change to libcontainer.process.args can break libcontainer.process.container_main_process, while a change to libcontainer.process.container_main_process can't break libcontainer.process.args.
- Position
- Below the diagonal: libcontainer.process.container_main_process uses a module listed above it, which is the healthy direction.
39→5 libcontainer.process.init.context uses libcontainer.namespaces✕
- Connections
- 1 pair of types, where a type in libcontainer.process.init.context uses a type in libcontainer.namespaces.
- The types involved
libcontainer.process.init.context.InitContext→libcontainer.namespaces.Namespaces
- Direction
- libcontainer.process.init.context uses libcontainer.namespaces, so a change to libcontainer.namespaces can break libcontainer.process.init.context, while a change to libcontainer.process.init.context can't break libcontainer.namespaces.
- Position
- Below the diagonal: libcontainer.process.init.context uses a module listed above it, which is the healthy direction.
39→7 libcontainer.process.init.context uses liboci_cli.spec✕
- Connections
- 1 pair of types, where a type in libcontainer.process.init.context uses a type in liboci_cli.spec.
- The types involved
libcontainer.process.init.context.InitContext→liboci_cli.spec.Spec
- Direction
- libcontainer.process.init.context uses liboci_cli.spec, so a change to liboci_cli.spec can break libcontainer.process.init.context, while a change to libcontainer.process.init.context can't break liboci_cli.spec.
- Position
- Below the diagonal: libcontainer.process.init.context uses a module listed above it, which is the healthy direction.
39→11 libcontainer.process.init.context uses libcontainer.container.container✕
- Connections
- 1 pair of types, where a type in libcontainer.process.init.context uses a type in libcontainer.container.container.
- The types involved
libcontainer.process.init.context.InitContext→libcontainer.container.container.Container
- Direction
- libcontainer.process.init.context uses libcontainer.container.container, so a change to libcontainer.container.container can break libcontainer.process.init.context, while a change to libcontainer.process.init.context can't break libcontainer.container.container.
- Position
- Below the diagonal: libcontainer.process.init.context uses a module listed above it, which is the healthy direction.
39→35 libcontainer.process.init.context uses libcontainer.process.args✕
- Connections
- 1 pair of types, where a type in libcontainer.process.init.context uses a type in libcontainer.process.args.
- The types involved
libcontainer.process.init.context.InitContext→libcontainer.process.args.ContainerArgs
- Direction
- libcontainer.process.init.context uses libcontainer.process.args, so a change to libcontainer.process.args can break libcontainer.process.init.context, while a change to libcontainer.process.init.context can't break libcontainer.process.args.
- Position
- Below the diagonal: libcontainer.process.init.context uses a module listed above it, which is the healthy direction.
40→5 libcontainer.process.init.process uses libcontainer.namespaces✕
- Connections
- 1 pair of types, where a type in libcontainer.process.init.process uses a type in libcontainer.namespaces.
- The types involved
libcontainer.process.init.process.process$module→libcontainer.namespaces.Namespaces
- Direction
- libcontainer.process.init.process uses libcontainer.namespaces, so a change to libcontainer.namespaces can break libcontainer.process.init.process, while a change to libcontainer.process.init.process can't break libcontainer.namespaces.
- Position
- Below the diagonal: libcontainer.process.init.process uses a module listed above it, which is the healthy direction.
40→7 libcontainer.process.init.process uses liboci_cli.spec✕
- Connections
- 1 pair of types, where a type in libcontainer.process.init.process uses a type in liboci_cli.spec.
- The types involved
libcontainer.process.init.process.process$module→liboci_cli.spec.Spec
- Direction
- libcontainer.process.init.process uses liboci_cli.spec, so a change to liboci_cli.spec can break libcontainer.process.init.process, while a change to libcontainer.process.init.process can't break liboci_cli.spec.
- Position
- Below the diagonal: libcontainer.process.init.process uses a module listed above it, which is the healthy direction.
40→14 libcontainer.process.init.process uses libcontainer.process.channel✕
- Connections
- 2 pairs of types, where a type in libcontainer.process.init.process uses a type in libcontainer.process.channel.
- The types involved
libcontainer.process.init.process.process$module→libcontainer.process.channel.InitReceiverlibcontainer.process.init.process.process$module→libcontainer.process.channel.MainSender
- Direction
- libcontainer.process.init.process uses libcontainer.process.channel, so a change to libcontainer.process.channel can break libcontainer.process.init.process, while a change to libcontainer.process.init.process can't break libcontainer.process.channel.
- Position
- Below the diagonal: libcontainer.process.init.process uses a module listed above it, which is the healthy direction.
40→15 libcontainer.process.init.process uses libcontainer.user_ns✕
- Connections
- 1 pair of types, where a type in libcontainer.process.init.process uses a type in libcontainer.user_ns.
- The types involved
libcontainer.process.init.process.process$module→libcontainer.user_ns.UserNamespaceConfig
- Direction
- libcontainer.process.init.process uses libcontainer.user_ns, so a change to libcontainer.user_ns can break libcontainer.process.init.process, while a change to libcontainer.process.init.process can't break libcontainer.user_ns.
- Position
- Below the diagonal: libcontainer.process.init.process uses a module listed above it, which is the healthy direction.
40→35 libcontainer.process.init.process uses libcontainer.process.args✕
- Connections
- 1 pair of types, where a type in libcontainer.process.init.process uses a type in libcontainer.process.args.
- The types involved
libcontainer.process.init.process.process$module→libcontainer.process.args.ContainerArgs
- Direction
- libcontainer.process.init.process uses libcontainer.process.args, so a change to libcontainer.process.args can break libcontainer.process.init.process, while a change to libcontainer.process.init.process can't break libcontainer.process.args.
- Position
- Below the diagonal: libcontainer.process.init.process uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 111 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 54 | High / Critical |
| A02:2025 — Security Misconfiguration | 53 | High / Critical |
| A07:2025 — Authentication Failures | 1 | High / Critical |
Roadmap
Begin by fixing the interpolated log messages to enable proper structured logging, and immediately address the single leaked secret in REDACTED. Next, resolve the medium-severity IaC and container security findings, prioritizing REDACTED, while also implementing the missing network egress policy. Finally, refactor the 26 most complex code bodies to reduce cognitive load and improve maintainability.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +1.9 pts | Low | Secret Scanning |
| Resolve the 1 No network policy finding(s) in Network Egress Confinement. | +1.7 pts | Low | Network Egress Confinement |
| Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED. | +1.7 pts | Low | Kernel & Syscall Confinement |
| Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. | +1.7 pts | Low | Platform End-of-Life |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.4 pts | Low | ADR Quality |
| Interpolated log message defeats structured logging | +2.6 pts | Medium | Structured logging |
| Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. | +1.1 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 0.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.1 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.7 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.0 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| crates/libcontainer/src/process/init/process.rs | 5.6 | Mixed | Cyclomatic Complexity: libcontainer::process::init::process::container_init_process (cyclomatic 45) |
| experiment/seccomp/src/seccomp.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 53 of 53 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 53 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, 438 of 458 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (.codecov.yml) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rs), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 100 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.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> # syntax=docker/dockerfile:1.4 2 | 3 | FROM rust:1-slim-bookworm AS youki-build -------------------- ERROR: failed to solve: failed to resolve source metadata for docker.io/docker/dockerfile:1.4: failed to do request: Head "https://registry-1.docker.io/v2/docker/dockerfile/manifests/1.4": Forbidden; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). 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.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 153 further occurrence(s) are not listed individually; the score already reflects all 193.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
- 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.
- 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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 libcontainer::rootfs::utils::parse_mount at 49. A further 5 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 MountOption::from_str at 34 — they are counted neither in the figure above nor in this dimension's score. 3 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: REDACTED (MountOption::from_str at 34), crates/libcontainer/src/signal.rs (Signal::try_from at 32), crates/libcontainer/src/process/message.rs (Message::fmt at 17). 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 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with libcontainer::rootfs::utils::parse_mount (cyclomatic 49), libcontainer::process::init::process::container_init_process (cyclomatic 45). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 7.3 to about 7.8/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
26 function(s) exceeded the cognitive complexity threshold of 15; the worst was libcontainer::process::init::process::container_init_process at 66.
What to do
- Bring the 26 bodies over 15 down to 15 or less in Cognitive Complexity — start with libcontainer::process::init::process::container_init_process (cognitive 66), Validator::validate_spec_for_sysctl (cognitive 63), libcontainer::rootfs::utils::parse_mount (cognitive 51). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 26 together lifts Cognitive Complexity from 6.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
16 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 4 FunctionTooLong finding(s) in God Classes — start with process.rs, container_main_process.rs, container_intermediate_process.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 FileTooLong finding(s) in God Classes — start with mount.rs, process.rs, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with mount.rs, seccomp.rs, container_checkpoint.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
37 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with seccomp.rs (2), memory.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with message.rs, container_intermediate_process.rs, process.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with common.rs, cpuset.rs, hugetlb.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
7 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 6 of the 7 (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 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
2 of 48 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with selinux.rs, builder.rs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
572 test methods: 564 unit, 8 integration, 0 BDD, 0 e2e. The Rust suite contributes 572 `#[test]` function(s) across 100 file(s) declaring at least one; its unit/integration split is Cargo's own — 5 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
3 outdated, 0 yanked direct Cargo dependencies. 47 of 49 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
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 698 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.
D15 · Churn × Complexity Hotspots
Top hotspots: crates/libcontainer/src/process/init/process.rs (3×45=135); crates/libcontainer/src/rootfs/mount.rs (5×20=100); crates/libcontainer/src/rootfs/utils.rs (2×49=98)
What to do
- Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with process.rs, mount.rs, utils.rs. — One of this dimension's main actionable groups (5 warning-level).
D16 · Bus Factor
6 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/libcgroups/src/v2/memory.rs. Counted over 113 of the 193 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
32 deducted task-comment markers across 41060 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 27 TodoComment finding(s) in Explicit Debt — start with checkpoint.rs (6), mod.rs (4), seccomp.rs (4). — One of this dimension's main actionable groups (27 warning-level).
- Resolve the 5 FixmeComment finding(s) in Explicit Debt — start with controller.rs (3), tty.rs, emulator.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 52 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. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 7 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)
111 finding(s): 0 critical, 105 high, 6 medium, 0 low. 94 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 4 file(s) — `REDACTED`, `crates/libcontainer/src/process/init/process.rs` (line 956), `scripts/build.sh` (line 66), `tools/youki-deploy/install-youki.sh` (line 38) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 5 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 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 94 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 (94 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
37 finding(s): 0 critical, 1 high, 36 medium, 0 low.
What to do
- Resolve the 15 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (15). — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 12 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (12). — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
53 finding(s): 0 critical, 10 high, 34 medium, 9 low.
What to do
- Resolve the 34 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (27), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (34 warning-level).
- Resolve the 10 High IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 9 Low IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED (4). — One of this dimension's main actionable groups (9 recommendation-level).
D34 · Knowledge Freshness
41 of 113 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is experiment/seccomp/src/seccomp.rs. Counted over 113 of the 193 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 35 Orphaned file finding(s) in Knowledge Freshness — start with freezer.rs (2), hugetlb.rs (2), cpu.rs (2). — One of this dimension's main actionable groups (35 recommendation-level).
- Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with seccomp.rs, message.rs, memory.rs. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: process.rs↔default.rs 80%; init_builder.rs↔tenant_builder.rs 59%; init_builder.rs↔run.rs 50%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with init_builder.rs (2), process.rs. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
0/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 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D40 · Network Egress Confinement
0/2 network-egress controls present (network policy, egress restriction).
What to do
- Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
D41 · Kernel & Syscall Confinement
0/1 workload(s) run every container under a seccomp profile; 0/1 declare an AppArmor/SELinux profile.
What to do
- Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D42 · Runtime Threat Enforcement
1/2 runtime-enforcement controls present (threat detection, admission control).
What to do
- Resolve the 1 No runtime threat detection finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
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
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Add a README to the 1 of 7 project(s) that lack one — worth up to 0.3 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
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: `experiment/selinux`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `github-actions`, `gitsubmodule` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug!` at line 92 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`. — crates/youki/src/main.rs:92
- `error!` at line 119 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`. — crates/youki/src/main.rs:119
- `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`. — crates/youki/src/main.rs:131
- `error!` at line 149 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`. — crates/youki/src/main.rs:149
- `error!` at line 41 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`. — crates/youki/src/workload/wasmer.rs:41
- `error!` at line 32 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`. — crates/youki/src/workload/wasmtime.rs:32
- `debug!` at line 12 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`. — crates/youki/src/commands/checkpoint.rs:12
- `debug!` at line 9 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`. — crates/youki/src/commands/delete.rs:9
- `debug!` at line 15 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`. (×2) — crates/youki/src/commands/pause.rs:15, crates/youki/src/commands/resume.rs:15
- `debug!` at line 140 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`. — crates/libcontainer/src/capabilities.rs:140
- `debug!` at line 144 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`. — crates/libcontainer/src/capabilities.rs:144
- `debug!` at line 149 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`. — crates/libcontainer/src/capabilities.rs:149
- `debug!` at line 154 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`. — crates/libcontainer/src/capabilities.rs:154
- `debug!` at line 159 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`. — crates/libcontainer/src/capabilities.rs:159
- `debug!` at line 73 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`. — crates/libcontainer/src/hooks.rs:73
- `debug!` at line 86 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`. — crates/libcontainer/src/hooks.rs:86
- `debug!` at line 108 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`. — crates/libcontainer/src/namespaces.rs:108
- `debug!` at line 87 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`. — crates/libcontainer/src/notify_socket.rs:87
- `debug!` at line 384 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`. — crates/libcontainer/src/tty.rs:384
- `error!` at line 401 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`. — crates/libcontainer/src/tty.rs:401
- `error!` at line 408 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`. — crates/libcontainer/src/tty.rs:408
- `debug!` at line 417 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`. — crates/libcontainer/src/tty.rs:417
- `error!` at line 160 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`. — crates/libcontainer/src/user_ns.rs:160
- `debug!` at line 177 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`. — crates/libcontainer/src/user_ns.rs:177
- `debug!` at line 190 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`. — crates/libcontainer/src/user_ns.rs:190
- `debug!` at line 409 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`. — crates/libcontainer/src/user_ns.rs:409
- `warn!` 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: `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`. — crates/libcontainer/src/validator.rs:120
- `error!` at line 26 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`. — crates/libcontainer/src/workload/default.rs:26
- `warn!` at line 202 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`. — crates/libcontainer/src/seccomp/mod.rs:202
- `warn!` at line 215 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`. — crates/libcontainer/src/seccomp/mod.rs:215
- `error!` at line 259 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`. — crates/libcontainer/src/seccomp/mod.rs:259
- `error!` at line 276 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`. — crates/libcontainer/src/seccomp/mod.rs:276
- `error!` at line 288 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`. — crates/libcontainer/src/seccomp/mod.rs:288
- `error!` at line 90 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`. — crates/libcontainer/src/rootfs/device.rs:90
- `debug!` at line 111 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`. — crates/libcontainer/src/rootfs/device.rs:111
- `error!` at line 122 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`. — crates/libcontainer/src/rootfs/device.rs:122
- `error!` at line 197 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`. — crates/libcontainer/src/rootfs/device.rs:197
- `error!` at line 205 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`. — crates/libcontainer/src/rootfs/device.rs:205
- `error!` at line 214 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`. — crates/libcontainer/src/rootfs/device.rs:214
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 72% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 93% | Exemplary | Strongest area. |
| Maturity | 79% | Strong | Solid. |
| Readiness | 76% | Strong | Solid. |
| Security | 57% | Adequate — gated by D29, D30, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 2 check(s) recorded observations but carry no score
- 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 — 2 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 — 64 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> # syntax=docker/dockerfile:1.4 2 | 3 | FROM rust:1-slim-bookworm AS youki-build -------------------- ERROR: failed to solve: failed to resolve source metadata for docker.io/docker/dockerfile:1.4: failed to do request: Head "https://registry-1.docker.io/v2/docker/dockerfile/manifests/1.4": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — 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 — ~18136 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
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust not measured.
- 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+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 186 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
- 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.
- 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
- 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 — 123 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge experiment/seccomp/src/seccomp.rs:1
- Orphaned knowledge crates/libcgroups/src/systemd/dbus_native/message.rs:1
- Orphaned knowledge crates/libcgroups/src/v1/memory.rs:1
- Orphaned knowledge crates/libcgroups/src/stats.rs:1
- Orphaned knowledge experiment/selinux/src/selinux.rs:1
- Orphaned knowledge crates/libcontainer/src/process/memory_policy.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 232 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment tests/contest/runtimetest/src/tests.rs:57
- TodoComment tests/contest/contest/src/tests/update/mod.rs:58
- TodoComment tests/contest/contest/src/tests/poststop_fail/mod.rs:61
- TodoComment tests/contest/contest/src/tests/personality/mod.rs:76
- TodoComment tests/contest/contest/src/tests/lifecycle/container_lifecycle.rs:223
- TodoComment tests/contest/contest/src/tests/exec/cgroup_test.rs:121
- TodoComment tests/contest/contest/src/tests/checkpoint_restore/mod.rs:31
- TodoComment experiment/selinux/src/selinux_label.rs:242
- TodoComment experiment/selinux/src/selinux_label.rs:251
- TodoComment experiment/selinux/src/selinux_label.rs:274
- TodoComment experiment/seccomp/src/seccomp.rs:67
- TodoComment experiment/seccomp/src/seccomp.rs:126
- TodoComment experiment/seccomp/src/seccomp.rs:281
- TodoComment experiment/seccomp/src/seccomp.rs:388
- TodoComment crates/youki/src/observability.rs:111
- TodoComment crates/youki/src/commands/features.rs:78
- TodoComment crates/liboci-cli/src/checkpoint.rs:16
- TodoComment crates/liboci-cli/src/checkpoint.rs:37
- TodoComment crates/liboci-cli/src/checkpoint.rs:40
- TodoComment crates/liboci-cli/src/checkpoint.rs:43
- TodoComment crates/liboci-cli/src/checkpoint.rs:49
- TodoComment crates/liboci-cli/src/checkpoint.rs:60
- TodoComment crates/libcontainer/src/hooks.rs:39
- TodoComment crates/libcontainer/src/container/builder_impl.rs:70
- TodoComment crates/libcontainer/src/container/mount_validation.rs:96
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- libcontainer::rootfs::utils::parse_mount (cyclomatic 49) crates/libcontainer/src/rootfs/utils.rs:97
- libcontainer::process::init::process::container_init_process (cyclomatic 45) crates/libcontainer/src/process/init/process.rs:42
- libcontainer::process::container_intermediate_process::container_intermediate_process (cyclomatic 23) crates/libcontainer/src/process/container_intermediate_process.rs:42
- libcontainer::process::memory_policy::validate_memory_policy (cyclomatic 21) crates/libcontainer/src/process/memory_policy.rs:94
- libcontainer::seccomp::initialize_seccomp (cyclomatic 19) crates/libcontainer/src/seccomp/mod.rs:150
- libcontainer::hooks::run_hooks (cyclomatic 17) crates/libcontainer/src/hooks.rs:36
- libcontainer::process::container_main_process::container_main_process (cyclomatic 17) crates/libcontainer/src/process/container_main_process.rs:50
- libcontainer::process::init::process::setup_scheduler (cyclomatic 17) crates/libcontainer/src/process/init/process.rs:915
- libcontainer::process::init::process::container_init_process (cognitive 66) crates/libcontainer/src/process/init/process.rs:42
- libcontainer::rootfs::utils::parse_mount (cognitive 51) crates/libcontainer/src/rootfs/utils.rs:97
- libcontainer::seccomp::initialize_seccomp (cognitive 51) crates/libcontainer/src/seccomp/mod.rs:150
- libcontainer::hooks::run_hooks (cognitive 43) crates/libcontainer/src/hooks.rs:36
- libcontainer::process::container_intermediate_process::container_intermediate_process (cognitive 34) crates/libcontainer/src/process/container_intermediate_process.rs:42
- libcontainer::process::memory_policy::validate_memory_policy (cognitive 27) crates/libcontainer/src/process/memory_policy.rs:94
- libcontainer::seccomp::check_seccomp (cognitive 16) crates/libcontainer/src/seccomp/mod.rs:119
- libcontainer::user_ns::validate_mounts_for_new_user_ns (cognitive 16) crates/libcontainer/src/user_ns.rs:319
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Hotspot: crates/libcontainer/src/process/init/process.rs crates/libcontainer/src/process/init/process.rs:42
- Hotspot: crates/libcontainer/src/rootfs/mount.rs crates/libcontainer/src/rootfs/mount.rs:579
- Hotspot: crates/libcontainer/src/rootfs/utils.rs crates/libcontainer/src/rootfs/utils.rs:97
- Hotspot: crates/libcgroups/src/v2/io.rs crates/libcgroups/src/v2/io.rs:126
- Hotspot: crates/libcontainer/src/process/container_main_process.rs crates/libcontainer/src/process/container_main_process.rs:50
- FixmeComment crates/libcontainer/src/tty.rs:438
- FixmeComment crates/libcgroups/src/v2/devices/controller.rs:54
- FixmeComment crates/libcgroups/src/v2/devices/controller.rs:57
- FixmeComment crates/libcgroups/src/v2/devices/controller.rs:82
- FixmeComment crates/libcgroups/src/v2/devices/emulator.rs:16
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: libcontainer::process::init::process::container_init_process crates/libcontainer/src/process/init/process.rs:42
- FunctionTooLong: libcontainer::process::container_main_process::container_main_process crates/libcontainer/src/process/container_main_process.rs:50
- FunctionTooLong: libcontainer::process::container_intermediate_process::container_intermediate_process crates/libcontainer/src/process/container_intermediate_process.rs:42
- FunctionTooLong: libcontainer::seccomp::initialize_seccomp crates/libcontainer/src/seccomp/mod.rs:150
- FileTooLong: rootfs/mount.rs crates/libcontainer/src/rootfs/mount.rs
- FileTooLong: init/process.rs crates/libcontainer/src/process/init/process.rs
- FileTooLong: REDACTED REDACTED
- FileTooLong: src/common.rs crates/libcgroups/src/common.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: Mount.mount_into_container crates/libcontainer/src/rootfs/mount.rs:579
- MethodTooLong: Rule.build_instruction_with_args experiment/seccomp/src/seccomp.rs:506
- MethodTooLong: Container.checkpoint crates/libcontainer/src/container/container_checkpoint.rs:29
- TooManyMethods: SELinux experiment/selinux/src/selinux.rs:96
- TooManyMethods: Container crates/libcontainer/src/container/container.rs:17
- TooManyMethods: TenantContainerBuilder crates/libcontainer/src/container/tenant_builder.rs:40
- REDACTED
- REDACTED
- REDACTED
- Change coupling: process.rs ↔ default.rs crates/libcontainer/src/process/init/process.rs:1
- Change coupling: init_builder.rs ↔ tenant_builder.rs crates/libcontainer/src/container/init_builder.rs:1
- Change coupling: init_builder.rs ↔ run.rs crates/libcontainer/src/container/init_builder.rs:1
- Duplicated block (17 lines × 2) crates/libcgroups/src/v1/memory.rs:231
- Duplicated block (17 lines × 2) experiment/seccomp/src/seccomp.rs:538
- Duplicated block (17 lines × 2) experiment/seccomp/src/seccomp.rs:618
- Duplicated block (11 lines × 2) crates/libcgroups/src/systemd/dbus_native/message.rs:205
- Duplicated block (11 lines × 2) crates/libcontainer/src/process/container_intermediate_process.rs:62
- Duplicated block (11 lines × 2) crates/libcontainer/src/process/init/process.rs:369
- Duplicated block (10 lines × 2) crates/libcgroups/src/common.rs:220
- Duplicated block (10 lines × 2) crates/libcgroups/src/v1/cpuset.rs:70
- Duplicated block (10 lines × 2) crates/libcgroups/src/v1/hugetlb.rs:111
- Duplicated block (7 lines × 2) crates/libcgroups/src/v1/manager.rs:229
- Duplicated block (7 lines × 2) crates/libcontainer/src/rootfs/mount.rs:514
- Duplicated block (7 lines × 2) crates/libcgroups/src/v2/cpu.rs:33
- Validator::validate_spec_for_sysctl (cognitive 63) crates/libcontainer/src/validator.rs:224
- Validator::validate_spec_for_scheduler (cognitive 29) crates/libcontainer/src/validator.rs:330
- Mount::mount_into_container (cognitive 39) crates/libcontainer/src/rootfs/mount.rs:579
- Mount::check_proc_mount (cognitive 20) crates/libcontainer/src/rootfs/mount.rs:1032
- ClassTooLong: Mount crates/libcontainer/src/rootfs/mount.rs:122
- ClassTooLong: LinuxSyscall REDACTED:311
- Duplicated block (12 lines × 2) crates/libcgroups/src/v1/util.rs:28
- Duplicated block (12 lines × 2) crates/youki/src/workload/wasmer.rs:35
- Duplicated block (9 lines × 2) crates/libcontainer/src/network/address.rs:60
- Duplicated block (9 lines × 2) crates/libcontainer/src/network/link.rs:96
- Duplicated block (8 lines × 2) crates/libcgroups/src/v1/hugetlb.rs:88
- Duplicated block (8 lines × 2) crates/libcgroups/src/systemd/dbus_native/message.rs:437
- Duplicated block (5 lines × 2) crates/youki/src/commands/foreground.rs:124
- Duplicated block (5 lines × 2) crates/libcgroups/src/systemd/io.rs:81
- Duplicated block (6 lines × 3) crates/libcgroups/src/systemd/dbus_native/message.rs:429
- Duplicated block (6 lines × 3) crates/libcgroups/src/systemd/dbus_native/message.rs:199
- Off the main sequence: liboci-cli
- Off the main sequence: libcgroups
- Low cohesion: SELinux (LCOM4 16) experiment/selinux/src/selinux.rs:96
- Low cohesion: ContainerBuilder (LCOM4 9) crates/libcontainer/src/container/builder.rs:13
- youki::main (cyclomatic 23) crates/youki/src/main.rs:65
- SeccompProgramPlan::try_from (cyclomatic 21) experiment/seccomp/src/seccomp.rs:355
- Unified::apply (cyclomatic 20) crates/libcgroups/src/systemd/unified.rs:59
- Mount::mount_into_container (cyclomatic 20) crates/libcontainer/src/rootfs/mount.rs:579
- Validator::validate_spec_for_sysctl (cyclomatic 19) crates/libcontainer/src/validator.rs:224
- Header::parse (cyclomatic 18) crates/libcgroups/src/systemd/dbus_native/message.rs:128
- Io::apply (cyclomatic 18) crates/libcgroups/src/v2/io.rs:126
- Devices::apply_devices_from (cyclomatic 16) crates/libcgroups/src/systemd/devices.rs:85
- Memory::apply (cyclomatic 16) crates/libcgroups/src/v2/memory.rs:127
- Container::checkpoint (cyclomatic 16) crates/libcontainer/src/container/container_checkpoint.rs:29
- SeccompProgramPlan::try_from (cognitive 50) experiment/seccomp/src/seccomp.rs:355
- Io::apply (cognitive 31) crates/libcgroups/src/v2/io.rs:126
- Memory::apply (cognitive 30) crates/libcgroups/src/v2/memory.rs:127
- Container::checkpoint (cognitive 30) crates/libcontainer/src/container/container_checkpoint.rs:29
- Unified::apply (cognitive 24) crates/libcgroups/src/systemd/unified.rs:59
- Devices::apply_devices_from (cognitive 23) crates/libcgroups/src/systemd/devices.rs:85
- libcgroups::systemd::devices::find_device_group_in (cognitive 22) crates/libcgroups/src/systemd/devices.rs:242
- TenantContainerBuilder::adapt_spec_for_tenant (cognitive 20) crates/libcontainer/src/container/tenant_builder.rs:393
- Blkio::apply (cognitive 19) crates/libcgroups/src/v1/blkio.rs:123
- youki::commands::ps::ps (cognitive 19) crates/youki/src/commands/ps.rs:10
- SELinux::get_config_key (cognitive 19) experiment/selinux/src/selinux.rs:161
- Freezer::apply (cognitive 18) crates/libcgroups/src/v1/freezer.rs:47
- Cpu::apply (cognitive 17) crates/libcgroups/src/v1/cpu.rs:90
- seccomp::seccomp::check_seccomp (cognitive 16) experiment/seccomp/src/seccomp.rs:269
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (51 lines × 2) crates/libcgroups/src/common.rs:599
- Duplicated block (42 lines × 2) crates/libcontainer/src/rootfs/mount.rs:667
- Duplicated block (21 lines × 2) experiment/seccomp/src/seccomp.rs:515
- Duplicated block (15–16 lines × 2) crates/libcgroups/src/common.rs:558
- Duplicated block (14 lines × 3) experiment/seccomp/src/seccomp.rs:551
- Duplicated block (12–14 lines × 2) crates/libcgroups/src/v1/controller_type.rs:22
- Duplicated block (14 lines × 2) crates/libcontainer/src/container/init_builder.rs:217
- Duplicated block (12 lines × 3) crates/libcgroups/src/v1/memory.rs:229
- Duplicated block (10 lines × 6) experiment/seccomp/src/seccomp.rs:520
- Duplicated block (5–8 lines × 4) crates/libcgroups/src/v1/blkio.rs:141
- Duplicated block (7 lines × 7) experiment/seccomp/src/seccomp.rs:515
- Duplicated block (4–6 lines × 4) crates/libcontainer/src/container/tenant_builder.rs:83
- Duplicated block (13 lines × 3) crates/youki/src/workload/wasmedge.rs:79
- Duplicated block (7 lines × 3) crates/libcgroups/src/systemd/dbus_native/message.rs:207
- Duplicated block (9 lines × 3) crates/libcgroups/src/v2/io.rs:163
- End-of-life runtime: Rust 1.96 rust-toolchain.toml:1
- Coverage collected but not gated
Minor — 100 finding(s)
- Interpolated log message defeats structured logging crates/youki/src/main.rs:92
- Interpolated log message defeats structured logging crates/youki/src/main.rs:119
- Interpolated log message defeats structured logging crates/youki/src/main.rs:131
- Interpolated log message defeats structured logging crates/youki/src/main.rs:149
- Interpolated log message defeats structured logging crates/youki/src/workload/wasmer.rs:41
- Interpolated log message defeats structured logging crates/youki/src/workload/wasmtime.rs:32
- Interpolated log message defeats structured logging crates/youki/src/commands/checkpoint.rs:12
- Interpolated log message defeats structured logging crates/youki/src/commands/delete.rs:9
- Interpolated log message defeats structured logging crates/youki/src/commands/pause.rs:15
- Interpolated log message defeats structured logging crates/youki/src/commands/resume.rs:15
- Interpolated log message defeats structured logging crates/libcontainer/src/capabilities.rs:140
- Interpolated log message defeats structured logging crates/libcontainer/src/capabilities.rs:144
- Interpolated log message defeats structured logging crates/libcontainer/src/capabilities.rs:149
- Interpolated log message defeats structured logging crates/libcontainer/src/capabilities.rs:154
- Interpolated log message defeats structured logging crates/libcontainer/src/capabilities.rs:159
- Interpolated log message defeats structured logging crates/libcontainer/src/hooks.rs:73
- Interpolated log message defeats structured logging crates/libcontainer/src/hooks.rs:86
- Interpolated log message defeats structured logging crates/libcontainer/src/namespaces.rs:108
- Interpolated log message defeats structured logging crates/libcontainer/src/notify_socket.rs:87
- Interpolated log message defeats structured logging crates/libcontainer/src/tty.rs:384
- Interpolated log message defeats structured logging crates/libcontainer/src/tty.rs:401
- Interpolated log message defeats structured logging crates/libcontainer/src/tty.rs:408
- Interpolated log message defeats structured logging crates/libcontainer/src/tty.rs:417
- Interpolated log message defeats structured logging crates/libcontainer/src/user_ns.rs:160
- Interpolated log message defeats structured logging crates/libcontainer/src/user_ns.rs:177
- Orphaned file crates/libcontainer/src/process/fork.rs:1
- Orphaned file experiment/selinux/src/selinux_label.rs:1
- Orphaned file crates/libcgroups/src/v1/blkio.rs:1
- Orphaned file crates/libcgroups/src/v2/devices/program.rs:1
- Orphaned file crates/libcgroups/src/v2/devices/bpf.rs:1
- Orphaned file crates/youki/src/observability.rs:1
- Orphaned file crates/libcgroups/src/v1/freezer.rs:1
- Orphaned file crates/libcgroups/src/v1/hugetlb.rs:1
- Orphaned file crates/libcgroups/src/v2/hugetlb.rs:1
- Orphaned file crates/libcgroups/src/v1/cpu.rs:1
- Orphaned file crates/libcgroups/src/systemd/dbus_native/proxy.rs:1
- Orphaned file crates/libcontainer/src/workload/default.rs:1
- Orphaned file crates/youki/src/rootpath.rs:1
- Orphaned file crates/libcgroups/src/v1/cpuacct.rs:1
- Orphaned file crates/libcgroups/src/systemd/memory.rs:1
- Orphaned file crates/libcgroups/src/systemd/io.rs:1
- Orphaned file crates/libcgroups/src/systemd/cpuset.rs:1
- Orphaned file crates/libcgroups/src/v2/freezer.rs:1
- Orphaned file crates/libcontainer/src/notify_socket.rs:1
- Orphaned file crates/libcontainer/src/channel.rs:1
- Orphaned file crates/youki/src/main.rs:1
- Orphaned file crates/libcgroups/src/v2/devices/controller.rs:1
- Orphaned file crates/libcgroups/src/systemd/cpu.rs:1
- Orphaned file experiment/selinux/src/tools/xattr.rs:1
- Orphaned file crates/libcontainer/src/container/container_kill.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate crates/youki/src/workload/wasmer.rs:40
- Duplicated predicate crates/libcgroups/src/v1/hugetlb.rs:240
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No network policy
- No seccomp profile REDACTED:51
- No runtime threat detection
- No ADRs
- Logging is not universal
Minor — 3 finding(s)
- Outdated: clap
- Outdated: clap_complete
- Outdated: wasmer
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6face48f64944d49b708ea2a3fad99ed/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6face48f64944d49b708ea2a3fad99ed/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 111 | 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 . | 37 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 53 | 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 | — |
| 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 |