Executive summary
hyperlight-dev/hyperlight meets our standard for a preview release. It scores 71 out of 100 and is rated Strong, and 52 of its 53 critical findings are security problems in the build pipeline.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step for the work it takes is recording design decisions, worth about 2 points. Planning backups and recovery comes next, worth about 3 points.
Thirty-one secrets can leak from the build pipeline. Twenty pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Limiting each secret to its own step and passing outside input through environment variables would close both risks. The pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The part of the code nobody has worked on for a long time needs someone to learn and document it before anyone changes it.
The product code is 76,767 lines, about €120,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
New since the last survey: 7 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Knowledge Freshness · Orphaned knowledge src/hyperlight_common/src/flatbuffer_wrappers/guest_trace_data.rs
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Supply-chain Provenance & Signing REDACTED
- Platform End-of-Life · End-of-life runtime: Rust 1.94
Rebuild cost: about €120,000 · Estimate
| Cost to rebuild | €40,000 to €200,000, for 674 to 2,140 hours of work, about 0.8 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.0 at a score of 71. 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: 76,767 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 hyperlight_common.flatbuffer_wrappers.guest_error | 2 hyperlight_common.func.error | 3 hyperlight_common.virtq.pool.slot | 4 hyperlight_common.vmem | 5 hyperlight_component_util.etypes | 6 hyperlight_host.hypervisor.regs.aarch64 | 7 hyperlight_host.hypervisor.regs.aarch64.common_fpu | 8 hyperlight_host.hypervisor.regs.aarch64.common_regs | 9 hyperlight_host.hypervisor.regs.aarch64.special_regs | 10 hyperlight_host.mem.memory_region | 11 hyperlight_common.flatbuffers.hyperlight.generated.guest_event_envelope_type_generated | 12 hyperlight_common.flatbuffers.hyperlight.generated.guest_event_generated | 13 hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated | 14 hyperlight_common.virtq.buffer | 15 hyperlight_common.virtq.ring | 16 hyperlight_component_util.emit | 17 hyperlight_host.hypervisor.virtual_machine | 18 hyperlight_host.mem.layout | 19 hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated | 20 hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated | 21 hyperlight_common.transport | 22 hyperlight_common.virtq | 23 hyperlight_host.hypervisor.hyperlight_vm.test_support | 24 hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 | 25 hyperlight_host.hypervisor.virtual_machine.whp.aarch64 | 26 hyperlight_host.mem.shared_mem | 27 hyperlight_common.flatbuffer_wrappers.function_types | 28 hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated | 29 hyperlight_common.virtq.consumer | 30 hyperlight_common.virtq.producer | 31 hyperlight_host.hypervisor.virtual_machine.hvf | 32 hyperlight_common.flatbuffer_wrappers.function_call | 33 hyperlight_common.flatbuffer_wrappers.host_function_definition | 34 hyperlight_guest.transport.context | 35 hyperlight_host.mem.mgr | 36 hyperlight_host.hypervisor.gdb | 37 hyperlight_host.hypervisor.hyperlight_vm | 38 hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 | 39 hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 | 40 hyperlight_host.hypervisor.virtual_machine.whp.x86_64 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 hyperlight_common.flatbuffer_wrappers.guest_error | ||||||||||||||||||||||||||||||||||||||||
| 2 hyperlight_common.func.error | ||||||||||||||||||||||||||||||||||||||||
| 3 hyperlight_common.virtq.pool.slot | ||||||||||||||||||||||||||||||||||||||||
| 4 hyperlight_common.vmem | ||||||||||||||||||||||||||||||||||||||||
| 5 hyperlight_component_util.etypes | ||||||||||||||||||||||||||||||||||||||||
| 6 hyperlight_host.hypervisor.regs.aarch64 | ||||||||||||||||||||||||||||||||||||||||
| 7 hyperlight_host.hypervisor.regs.aarch64.common_fpu | ||||||||||||||||||||||||||||||||||||||||
| 8 hyperlight_host.hypervisor.regs.aarch64.common_regs | ||||||||||||||||||||||||||||||||||||||||
| 9 hyperlight_host.hypervisor.regs.aarch64.special_regs | ||||||||||||||||||||||||||||||||||||||||
| 10 hyperlight_host.mem.memory_region | ||||||||||||||||||||||||||||||||||||||||
| 11 hyperlight_common.flatbuffers.hyperlight.generated.guest_event_envelope_type_generated | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 hyperlight_common.flatbuffers.hyperlight.generated.guest_event_generated | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 hyperlight_common.virtq.buffer | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 hyperlight_common.virtq.ring | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 hyperlight_component_util.emit | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 hyperlight_host.hypervisor.virtual_machine | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 hyperlight_host.mem.layout | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 20 hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 21 hyperlight_common.transport | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 hyperlight_common.virtq | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 hyperlight_host.hypervisor.hyperlight_vm.test_support | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 24 hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 25 hyperlight_host.hypervisor.virtual_machine.whp.aarch64 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 26 hyperlight_host.mem.shared_mem | 2 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 hyperlight_common.flatbuffer_wrappers.function_types | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 28 hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 hyperlight_common.virtq.consumer | 4 | 8 | ||||||||||||||||||||||||||||||||||||||
| 30 hyperlight_common.virtq.producer | 3 | 1 | 3 | 4 | ||||||||||||||||||||||||||||||||||||
| 31 hyperlight_host.hypervisor.virtual_machine.hvf | 1 | 2 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 32 hyperlight_common.flatbuffer_wrappers.function_call | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 hyperlight_common.flatbuffer_wrappers.host_function_definition | 2 | |||||||||||||||||||||||||||||||||||||||
| 34 hyperlight_guest.transport.context | 1 | 2 | 5 | 4 | ||||||||||||||||||||||||||||||||||||
| 35 hyperlight_host.mem.mgr | 4 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 36 hyperlight_host.hypervisor.gdb | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 hyperlight_host.hypervisor.hyperlight_vm | 1 | 1 | 1 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 38 hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 39 hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 hyperlight_host.hypervisor.virtual_machine.whp.x86_64 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
11→3 hyperlight_common.flatbuffers.hyperlight.generated.guest_event_envelope_type_generated uses hyperlight_common.virtq.pool.slot✕
- Connections
- 1 pair of types, where a type in hyperlight_common.flatbuffers.hyperlight.generated.guest_event_envelope_type_generated uses a type in hyperlight_common.virtq.pool.slot.
- The types involved
hyperlight_common.flatbuffers.hyperlight.generated.guest_event_envelope_type_generated.GuestEventEnvelopeType→hyperlight_common.virtq.pool.slot.Inner
- Direction
- hyperlight_common.flatbuffers.hyperlight.generated.guest_event_envelope_type_generated uses hyperlight_common.virtq.pool.slot, so a change to hyperlight_common.virtq.pool.slot can break hyperlight_common.flatbuffers.hyperlight.generated.guest_event_envelope_type_generated, while a change to hyperlight_common.flatbuffers.hyperlight.generated.guest_event_envelope_type_generated can't break hyperlight_common.virtq.pool.slot.
- Position
- Below the diagonal: hyperlight_common.flatbuffers.hyperlight.generated.guest_event_envelope_type_generated uses a module listed above it, which is the healthy direction.
12→3 hyperlight_common.flatbuffers.hyperlight.generated.guest_event_generated uses hyperlight_common.virtq.pool.slot✕
- Connections
- 1 pair of types, where a type in hyperlight_common.flatbuffers.hyperlight.generated.guest_event_generated uses a type in hyperlight_common.virtq.pool.slot.
- The types involved
hyperlight_common.flatbuffers.hyperlight.generated.guest_event_generated.GuestEvent→hyperlight_common.virtq.pool.slot.Inner
- Direction
- hyperlight_common.flatbuffers.hyperlight.generated.guest_event_generated uses hyperlight_common.virtq.pool.slot, so a change to hyperlight_common.virtq.pool.slot can break hyperlight_common.flatbuffers.hyperlight.generated.guest_event_generated, while a change to hyperlight_common.flatbuffers.hyperlight.generated.guest_event_generated can't break hyperlight_common.virtq.pool.slot.
- Position
- Below the diagonal: hyperlight_common.flatbuffers.hyperlight.generated.guest_event_generated uses a module listed above it, which is the healthy direction.
13→3 hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated uses hyperlight_common.virtq.pool.slot✕
- Connections
- 1 pair of types, where a type in hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated uses a type in hyperlight_common.virtq.pool.slot.
- The types involved
hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated.hlexternalbytes→hyperlight_common.virtq.pool.slot.Inner
- Direction
- hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated uses hyperlight_common.virtq.pool.slot, so a change to hyperlight_common.virtq.pool.slot can break hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated, while a change to hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated can't break hyperlight_common.virtq.pool.slot.
- Position
- Below the diagonal: hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated uses a module listed above it, which is the healthy direction.
14→3 hyperlight_common.virtq.buffer uses hyperlight_common.virtq.pool.slot✕
- Connections
- 1 pair of types, where a type in hyperlight_common.virtq.buffer uses a type in hyperlight_common.virtq.pool.slot.
- The types involved
hyperlight_common.virtq.buffer.BufferLease→hyperlight_common.virtq.pool.slot.SlotPool
- Direction
- hyperlight_common.virtq.buffer uses hyperlight_common.virtq.pool.slot, so a change to hyperlight_common.virtq.pool.slot can break hyperlight_common.virtq.buffer, while a change to hyperlight_common.virtq.buffer can't break hyperlight_common.virtq.pool.slot.
- Position
- Below the diagonal: hyperlight_common.virtq.buffer uses a module listed above it, which is the healthy direction.
15→22 hyperlight_common.virtq.ring uses hyperlight_common.virtq part of a loop✕
- Connections
- 2 pairs of types, where a type in hyperlight_common.virtq.ring uses a type in hyperlight_common.virtq.
- The types involved
hyperlight_common.virtq.ring.RingConsumer→hyperlight_common.virtq.Layouthyperlight_common.virtq.ring.RingProducer→hyperlight_common.virtq.Layout
- Direction
- hyperlight_common.virtq.ring uses hyperlight_common.virtq, so a change to hyperlight_common.virtq can break hyperlight_common.virtq.ring, while a change to hyperlight_common.virtq.ring can't break hyperlight_common.virtq.
- 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.
16→5 hyperlight_component_util.emit uses hyperlight_component_util.etypes✕
- Connections
- 2 pairs of types, where a type in hyperlight_component_util.emit uses a type in hyperlight_component_util.etypes.
- The types involved
hyperlight_component_util.emit.State→hyperlight_component_util.etypes.Definedhyperlight_component_util.emit.State→hyperlight_component_util.etypes.ImportExport
- Direction
- hyperlight_component_util.emit uses hyperlight_component_util.etypes, so a change to hyperlight_component_util.etypes can break hyperlight_component_util.emit, while a change to hyperlight_component_util.emit can't break hyperlight_component_util.etypes.
- Position
- Below the diagonal: hyperlight_component_util.emit uses a module listed above it, which is the healthy direction.
17→6 hyperlight_host.hypervisor.virtual_machine uses hyperlight_host.hypervisor.regs.aarch64✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine uses a type in hyperlight_host.hypervisor.regs.aarch64.
- The types involved
hyperlight_host.hypervisor.virtual_machine.VirtualMachine→hyperlight_host.hypervisor.regs.aarch64.CommonDebugRegs
- Direction
- hyperlight_host.hypervisor.virtual_machine uses hyperlight_host.hypervisor.regs.aarch64, so a change to hyperlight_host.hypervisor.regs.aarch64 can break hyperlight_host.hypervisor.virtual_machine, while a change to hyperlight_host.hypervisor.virtual_machine can't break hyperlight_host.hypervisor.regs.aarch64.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine uses a module listed above it, which is the healthy direction.
17→7 hyperlight_host.hypervisor.virtual_machine uses hyperlight_host.hypervisor.regs.aarch64.common_fpu✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine uses a type in hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- The types involved
hyperlight_host.hypervisor.virtual_machine.VirtualMachine→hyperlight_host.hypervisor.regs.aarch64.common_fpu.CommonFpu
- Direction
- hyperlight_host.hypervisor.virtual_machine uses hyperlight_host.hypervisor.regs.aarch64.common_fpu, so a change to hyperlight_host.hypervisor.regs.aarch64.common_fpu can break hyperlight_host.hypervisor.virtual_machine, while a change to hyperlight_host.hypervisor.virtual_machine can't break hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine uses a module listed above it, which is the healthy direction.
17→8 hyperlight_host.hypervisor.virtual_machine uses hyperlight_host.hypervisor.regs.aarch64.common_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine uses a type in hyperlight_host.hypervisor.regs.aarch64.common_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.VirtualMachine→hyperlight_host.hypervisor.regs.aarch64.common_regs.CommonRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine uses hyperlight_host.hypervisor.regs.aarch64.common_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.common_regs can break hyperlight_host.hypervisor.virtual_machine, while a change to hyperlight_host.hypervisor.virtual_machine can't break hyperlight_host.hypervisor.regs.aarch64.common_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine uses a module listed above it, which is the healthy direction.
17→9 hyperlight_host.hypervisor.virtual_machine uses hyperlight_host.hypervisor.regs.aarch64.special_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine uses a type in hyperlight_host.hypervisor.regs.aarch64.special_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.VirtualMachine→hyperlight_host.hypervisor.regs.aarch64.special_regs.CommonSpecialRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine uses hyperlight_host.hypervisor.regs.aarch64.special_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.special_regs can break hyperlight_host.hypervisor.virtual_machine, while a change to hyperlight_host.hypervisor.virtual_machine can't break hyperlight_host.hypervisor.regs.aarch64.special_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine uses a module listed above it, which is the healthy direction.
18→10 hyperlight_host.mem.layout uses hyperlight_host.mem.memory_region✕
- Connections
- 1 pair of types, where a type in hyperlight_host.mem.layout uses a type in hyperlight_host.mem.memory_region.
- The types involved
hyperlight_host.mem.layout.SandboxMemoryLayout→hyperlight_host.mem.memory_region.MemoryRegionFlags
- Direction
- hyperlight_host.mem.layout uses hyperlight_host.mem.memory_region, so a change to hyperlight_host.mem.memory_region can break hyperlight_host.mem.layout, while a change to hyperlight_host.mem.layout can't break hyperlight_host.mem.memory_region.
- Position
- Below the diagonal: hyperlight_host.mem.layout uses a module listed above it, which is the healthy direction.
19→3 hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated uses hyperlight_common.virtq.pool.slot✕
- Connections
- 1 pair of types, where a type in hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated uses a type in hyperlight_common.virtq.pool.slot.
- The types involved
hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated.Parameter→hyperlight_common.virtq.pool.slot.Inner
- Direction
- hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated uses hyperlight_common.virtq.pool.slot, so a change to hyperlight_common.virtq.pool.slot can break hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated, while a change to hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated can't break hyperlight_common.virtq.pool.slot.
- Position
- Below the diagonal: hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated uses a module listed above it, which is the healthy direction.
19→13 hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated uses hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated✕
- Connections
- 1 pair of types, where a type in hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated uses a type in hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated.
- The types involved
hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated.Parameter→hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated.hlexternalbytes
- Direction
- hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated uses hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated, so a change to hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated can break hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated, while a change to hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated can't break hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated.
- Position
- Below the diagonal: hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated uses a module listed above it, which is the healthy direction.
19→27 hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated uses hyperlight_common.flatbuffer_wrappers.function_types part of a loop✕
- Connections
- 3 pairs of types, where a type in hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated uses a type in hyperlight_common.flatbuffer_wrappers.function_types.
- The types involved
hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated.Parameter→hyperlight_common.flatbuffer_wrappers.function_types.ParameterValuehyperlight_common.flatbuffers.hyperlight.generated.parameter_generated.ParameterArgs→hyperlight_common.flatbuffer_wrappers.function_types.ParameterValuehyperlight_common.flatbuffers.hyperlight.generated.parameter_generated.ParameterBuilder→hyperlight_common.flatbuffer_wrappers.function_types.ParameterValue
- Direction
- hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated uses hyperlight_common.flatbuffer_wrappers.function_types, so a change to hyperlight_common.flatbuffer_wrappers.function_types can break hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated, while a change to hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated can't break hyperlight_common.flatbuffer_wrappers.function_types.
- 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.
20→3 hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated uses hyperlight_common.virtq.pool.slot✕
- Connections
- 1 pair of types, where a type in hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated uses a type in hyperlight_common.virtq.pool.slot.
- The types involved
hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated.ReturnValueBox→hyperlight_common.virtq.pool.slot.Inner
- Direction
- hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated uses hyperlight_common.virtq.pool.slot, so a change to hyperlight_common.virtq.pool.slot can break hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated, while a change to hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated can't break hyperlight_common.virtq.pool.slot.
- Position
- Below the diagonal: hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated uses a module listed above it, which is the healthy direction.
20→13 hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated uses hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated✕
- Connections
- 1 pair of types, where a type in hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated uses a type in hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated.
- The types involved
hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated.ReturnValueBox→hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated.hlexternalbytes
- Direction
- hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated uses hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated, so a change to hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated can break hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated, while a change to hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated can't break hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated.
- Position
- Below the diagonal: hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated uses a module listed above it, which is the healthy direction.
20→27 hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated uses hyperlight_common.flatbuffer_wrappers.function_types part of a loop✕
- Connections
- 3 pairs of types, where a type in hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated uses a type in hyperlight_common.flatbuffer_wrappers.function_types.
- The types involved
hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated.ReturnValueBox→hyperlight_common.flatbuffer_wrappers.function_types.ReturnValuehyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated.ReturnValueBoxArgs→hyperlight_common.flatbuffer_wrappers.function_types.ReturnValuehyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated.ReturnValueBoxBuilder→hyperlight_common.flatbuffer_wrappers.function_types.ReturnValue
- Direction
- hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated uses hyperlight_common.flatbuffer_wrappers.function_types, so a change to hyperlight_common.flatbuffer_wrappers.function_types can break hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated, while a change to hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated can't break hyperlight_common.flatbuffer_wrappers.function_types.
- 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.
21→14 hyperlight_common.transport uses hyperlight_common.virtq.buffer✕
- Connections
- 1 pair of types, where a type in hyperlight_common.transport uses a type in hyperlight_common.virtq.buffer.
- The types involved
hyperlight_common.transport.transport$module→hyperlight_common.virtq.buffer.Segments
- Direction
- hyperlight_common.transport uses hyperlight_common.virtq.buffer, so a change to hyperlight_common.virtq.buffer can break hyperlight_common.transport, while a change to hyperlight_common.transport can't break hyperlight_common.virtq.buffer.
- Position
- Below the diagonal: hyperlight_common.transport uses a module listed above it, which is the healthy direction.
22→15 hyperlight_common.virtq uses hyperlight_common.virtq.ring✕
- Connections
- 1 pair of types, where a type in hyperlight_common.virtq uses a type in hyperlight_common.virtq.ring.
- The types involved
hyperlight_common.virtq.VirtqError→hyperlight_common.virtq.ring.RingError
- Direction
- hyperlight_common.virtq uses hyperlight_common.virtq.ring, so a change to hyperlight_common.virtq.ring can break hyperlight_common.virtq, while a change to hyperlight_common.virtq can't break hyperlight_common.virtq.ring.
- Position
- Below the diagonal: hyperlight_common.virtq uses a module listed above it, which is the healthy direction.
23→6 hyperlight_host.hypervisor.hyperlight_vm.test_support uses hyperlight_host.hypervisor.regs.aarch64✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.hyperlight_vm.test_support uses a type in hyperlight_host.hypervisor.regs.aarch64.
- The types involved
hyperlight_host.hypervisor.hyperlight_vm.test_support.FaultInjectingVirtualMachine→hyperlight_host.hypervisor.regs.aarch64.CommonDebugRegs
- Direction
- hyperlight_host.hypervisor.hyperlight_vm.test_support uses hyperlight_host.hypervisor.regs.aarch64, so a change to hyperlight_host.hypervisor.regs.aarch64 can break hyperlight_host.hypervisor.hyperlight_vm.test_support, while a change to hyperlight_host.hypervisor.hyperlight_vm.test_support can't break hyperlight_host.hypervisor.regs.aarch64.
- Position
- Below the diagonal: hyperlight_host.hypervisor.hyperlight_vm.test_support uses a module listed above it, which is the healthy direction.
23→7 hyperlight_host.hypervisor.hyperlight_vm.test_support uses hyperlight_host.hypervisor.regs.aarch64.common_fpu✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.hyperlight_vm.test_support uses a type in hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- The types involved
hyperlight_host.hypervisor.hyperlight_vm.test_support.FaultInjectingVirtualMachine→hyperlight_host.hypervisor.regs.aarch64.common_fpu.CommonFpu
- Direction
- hyperlight_host.hypervisor.hyperlight_vm.test_support uses hyperlight_host.hypervisor.regs.aarch64.common_fpu, so a change to hyperlight_host.hypervisor.regs.aarch64.common_fpu can break hyperlight_host.hypervisor.hyperlight_vm.test_support, while a change to hyperlight_host.hypervisor.hyperlight_vm.test_support can't break hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- Position
- Below the diagonal: hyperlight_host.hypervisor.hyperlight_vm.test_support uses a module listed above it, which is the healthy direction.
23→8 hyperlight_host.hypervisor.hyperlight_vm.test_support uses hyperlight_host.hypervisor.regs.aarch64.common_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.hyperlight_vm.test_support uses a type in hyperlight_host.hypervisor.regs.aarch64.common_regs.
- The types involved
hyperlight_host.hypervisor.hyperlight_vm.test_support.FaultInjectingVirtualMachine→hyperlight_host.hypervisor.regs.aarch64.common_regs.CommonRegisters
- Direction
- hyperlight_host.hypervisor.hyperlight_vm.test_support uses hyperlight_host.hypervisor.regs.aarch64.common_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.common_regs can break hyperlight_host.hypervisor.hyperlight_vm.test_support, while a change to hyperlight_host.hypervisor.hyperlight_vm.test_support can't break hyperlight_host.hypervisor.regs.aarch64.common_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.hyperlight_vm.test_support uses a module listed above it, which is the healthy direction.
23→9 hyperlight_host.hypervisor.hyperlight_vm.test_support uses hyperlight_host.hypervisor.regs.aarch64.special_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.hyperlight_vm.test_support uses a type in hyperlight_host.hypervisor.regs.aarch64.special_regs.
- The types involved
hyperlight_host.hypervisor.hyperlight_vm.test_support.FaultInjectingVirtualMachine→hyperlight_host.hypervisor.regs.aarch64.special_regs.CommonSpecialRegisters
- Direction
- hyperlight_host.hypervisor.hyperlight_vm.test_support uses hyperlight_host.hypervisor.regs.aarch64.special_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.special_regs can break hyperlight_host.hypervisor.hyperlight_vm.test_support, while a change to hyperlight_host.hypervisor.hyperlight_vm.test_support can't break hyperlight_host.hypervisor.regs.aarch64.special_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.hyperlight_vm.test_support uses a module listed above it, which is the healthy direction.
23→17 hyperlight_host.hypervisor.hyperlight_vm.test_support uses hyperlight_host.hypervisor.virtual_machine✕
- Connections
- 2 pairs of types, where a type in hyperlight_host.hypervisor.hyperlight_vm.test_support uses a type in hyperlight_host.hypervisor.virtual_machine.
- The types involved
hyperlight_host.hypervisor.hyperlight_vm.test_support.FaultInjectingVirtualMachine→hyperlight_host.hypervisor.virtual_machine.HypervisorErrorhyperlight_host.hypervisor.hyperlight_vm.test_support.FaultInjectingVirtualMachine→hyperlight_host.hypervisor.virtual_machine.VirtualMachine
- Direction
- hyperlight_host.hypervisor.hyperlight_vm.test_support uses hyperlight_host.hypervisor.virtual_machine, so a change to hyperlight_host.hypervisor.virtual_machine can break hyperlight_host.hypervisor.hyperlight_vm.test_support, while a change to hyperlight_host.hypervisor.hyperlight_vm.test_support can't break hyperlight_host.hypervisor.virtual_machine.
- Position
- Below the diagonal: hyperlight_host.hypervisor.hyperlight_vm.test_support uses a module listed above it, which is the healthy direction.
24→6 hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses hyperlight_host.hypervisor.regs.aarch64✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses a type in hyperlight_host.hypervisor.regs.aarch64.
- The types involved
hyperlight_host.hypervisor.virtual_machine.kvm.aarch64.KvmVm→hyperlight_host.hypervisor.regs.aarch64.CommonDebugRegs
- Direction
- hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses hyperlight_host.hypervisor.regs.aarch64, so a change to hyperlight_host.hypervisor.regs.aarch64 can break hyperlight_host.hypervisor.virtual_machine.kvm.aarch64, while a change to hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 can't break hyperlight_host.hypervisor.regs.aarch64.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses a module listed above it, which is the healthy direction.
24→7 hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses hyperlight_host.hypervisor.regs.aarch64.common_fpu✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses a type in hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- The types involved
hyperlight_host.hypervisor.virtual_machine.kvm.aarch64.KvmVm→hyperlight_host.hypervisor.regs.aarch64.common_fpu.CommonFpu
- Direction
- hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses hyperlight_host.hypervisor.regs.aarch64.common_fpu, so a change to hyperlight_host.hypervisor.regs.aarch64.common_fpu can break hyperlight_host.hypervisor.virtual_machine.kvm.aarch64, while a change to hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 can't break hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses a module listed above it, which is the healthy direction.
24→8 hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses hyperlight_host.hypervisor.regs.aarch64.common_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses a type in hyperlight_host.hypervisor.regs.aarch64.common_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.kvm.aarch64.KvmVm→hyperlight_host.hypervisor.regs.aarch64.common_regs.CommonRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses hyperlight_host.hypervisor.regs.aarch64.common_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.common_regs can break hyperlight_host.hypervisor.virtual_machine.kvm.aarch64, while a change to hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 can't break hyperlight_host.hypervisor.regs.aarch64.common_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses a module listed above it, which is the healthy direction.
24→9 hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses hyperlight_host.hypervisor.regs.aarch64.special_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses a type in hyperlight_host.hypervisor.regs.aarch64.special_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.kvm.aarch64.KvmVm→hyperlight_host.hypervisor.regs.aarch64.special_regs.CommonSpecialRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses hyperlight_host.hypervisor.regs.aarch64.special_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.special_regs can break hyperlight_host.hypervisor.virtual_machine.kvm.aarch64, while a change to hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 can't break hyperlight_host.hypervisor.regs.aarch64.special_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses a module listed above it, which is the healthy direction.
24→17 hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses hyperlight_host.hypervisor.virtual_machine✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses a type in hyperlight_host.hypervisor.virtual_machine.
- The types involved
hyperlight_host.hypervisor.virtual_machine.kvm.aarch64.KvmVm→hyperlight_host.hypervisor.virtual_machine.VirtualMachine
- Direction
- hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses hyperlight_host.hypervisor.virtual_machine, so a change to hyperlight_host.hypervisor.virtual_machine can break hyperlight_host.hypervisor.virtual_machine.kvm.aarch64, while a change to hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 can't break hyperlight_host.hypervisor.virtual_machine.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.kvm.aarch64 uses a module listed above it, which is the healthy direction.
25→6 hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses hyperlight_host.hypervisor.regs.aarch64✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses a type in hyperlight_host.hypervisor.regs.aarch64.
- The types involved
hyperlight_host.hypervisor.virtual_machine.whp.aarch64.WhpVm→hyperlight_host.hypervisor.regs.aarch64.CommonDebugRegs
- Direction
- hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses hyperlight_host.hypervisor.regs.aarch64, so a change to hyperlight_host.hypervisor.regs.aarch64 can break hyperlight_host.hypervisor.virtual_machine.whp.aarch64, while a change to hyperlight_host.hypervisor.virtual_machine.whp.aarch64 can't break hyperlight_host.hypervisor.regs.aarch64.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses a module listed above it, which is the healthy direction.
25→7 hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses hyperlight_host.hypervisor.regs.aarch64.common_fpu✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses a type in hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- The types involved
hyperlight_host.hypervisor.virtual_machine.whp.aarch64.WhpVm→hyperlight_host.hypervisor.regs.aarch64.common_fpu.CommonFpu
- Direction
- hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses hyperlight_host.hypervisor.regs.aarch64.common_fpu, so a change to hyperlight_host.hypervisor.regs.aarch64.common_fpu can break hyperlight_host.hypervisor.virtual_machine.whp.aarch64, while a change to hyperlight_host.hypervisor.virtual_machine.whp.aarch64 can't break hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses a module listed above it, which is the healthy direction.
25→8 hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses hyperlight_host.hypervisor.regs.aarch64.common_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses a type in hyperlight_host.hypervisor.regs.aarch64.common_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.whp.aarch64.WhpVm→hyperlight_host.hypervisor.regs.aarch64.common_regs.CommonRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses hyperlight_host.hypervisor.regs.aarch64.common_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.common_regs can break hyperlight_host.hypervisor.virtual_machine.whp.aarch64, while a change to hyperlight_host.hypervisor.virtual_machine.whp.aarch64 can't break hyperlight_host.hypervisor.regs.aarch64.common_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses a module listed above it, which is the healthy direction.
25→9 hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses hyperlight_host.hypervisor.regs.aarch64.special_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses a type in hyperlight_host.hypervisor.regs.aarch64.special_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.whp.aarch64.WhpVm→hyperlight_host.hypervisor.regs.aarch64.special_regs.CommonSpecialRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses hyperlight_host.hypervisor.regs.aarch64.special_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.special_regs can break hyperlight_host.hypervisor.virtual_machine.whp.aarch64, while a change to hyperlight_host.hypervisor.virtual_machine.whp.aarch64 can't break hyperlight_host.hypervisor.regs.aarch64.special_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses a module listed above it, which is the healthy direction.
25→17 hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses hyperlight_host.hypervisor.virtual_machine✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses a type in hyperlight_host.hypervisor.virtual_machine.
- The types involved
hyperlight_host.hypervisor.virtual_machine.whp.aarch64.WhpVm→hyperlight_host.hypervisor.virtual_machine.VirtualMachine
- Direction
- hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses hyperlight_host.hypervisor.virtual_machine, so a change to hyperlight_host.hypervisor.virtual_machine can break hyperlight_host.hypervisor.virtual_machine.whp.aarch64, while a change to hyperlight_host.hypervisor.virtual_machine.whp.aarch64 can't break hyperlight_host.hypervisor.virtual_machine.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.whp.aarch64 uses a module listed above it, which is the healthy direction.
26→5 hyperlight_host.mem.shared_mem uses hyperlight_component_util.etypes✕
- Connections
- 2 pairs of types, where a type in hyperlight_host.mem.shared_mem uses a type in hyperlight_component_util.etypes.
- The types involved
hyperlight_host.mem.shared_mem.AtomicAccess→hyperlight_component_util.etypes.Valuehyperlight_host.mem.shared_mem.HostSharedMemory→hyperlight_component_util.etypes.Value
- Direction
- hyperlight_host.mem.shared_mem uses hyperlight_component_util.etypes, so a change to hyperlight_component_util.etypes can break hyperlight_host.mem.shared_mem, while a change to hyperlight_host.mem.shared_mem can't break hyperlight_component_util.etypes.
- Position
- Below the diagonal: hyperlight_host.mem.shared_mem uses a module listed above it, which is the healthy direction.
26→10 hyperlight_host.mem.shared_mem uses hyperlight_host.mem.memory_region✕
- Connections
- 4 pairs of types, where a type in hyperlight_host.mem.shared_mem uses a type in hyperlight_host.mem.memory_region.
- The types involved
hyperlight_host.mem.shared_mem.GuestSharedMemory→hyperlight_host.mem.memory_region.MemoryRegionTypehyperlight_host.mem.shared_mem.ReadonlySharedMemory→hyperlight_host.mem.memory_region.MemoryRegionTypehyperlight_host.mem.shared_mem.shared_mem$module→hyperlight_host.mem.memory_region.MemoryRegionFlagshyperlight_host.mem.shared_mem.shared_mem$module→hyperlight_host.mem.memory_region.MemoryRegionType
- Direction
- hyperlight_host.mem.shared_mem uses hyperlight_host.mem.memory_region, so a change to hyperlight_host.mem.memory_region can break hyperlight_host.mem.shared_mem, while a change to hyperlight_host.mem.shared_mem can't break hyperlight_host.mem.memory_region.
- Position
- Below the diagonal: hyperlight_host.mem.shared_mem uses a module listed above it, which is the healthy direction.
26→18 hyperlight_host.mem.shared_mem uses hyperlight_host.mem.layout✕
- Connections
- 1 pair of types, where a type in hyperlight_host.mem.shared_mem uses a type in hyperlight_host.mem.layout.
- The types involved
hyperlight_host.mem.shared_mem.HostSharedMemory→hyperlight_host.mem.layout.ReadableSharedMemory
- Direction
- hyperlight_host.mem.shared_mem uses hyperlight_host.mem.layout, so a change to hyperlight_host.mem.layout can break hyperlight_host.mem.shared_mem, while a change to hyperlight_host.mem.shared_mem can't break hyperlight_host.mem.layout.
- Position
- Below the diagonal: hyperlight_host.mem.shared_mem uses a module listed above it, which is the healthy direction.
27→13 hyperlight_common.flatbuffer_wrappers.function_types uses hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated✕
- Connections
- 1 pair of types, where a type in hyperlight_common.flatbuffer_wrappers.function_types uses a type in hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated.
- The types involved
hyperlight_common.flatbuffer_wrappers.function_types.function_types$module→hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated.hlexternalbytes
- Direction
- hyperlight_common.flatbuffer_wrappers.function_types uses hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated, so a change to hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated can break hyperlight_common.flatbuffer_wrappers.function_types, while a change to hyperlight_common.flatbuffer_wrappers.function_types can't break hyperlight_common.flatbuffers.hyperlight.generated.hlexternalbytes_generated.
- Position
- Below the diagonal: hyperlight_common.flatbuffer_wrappers.function_types uses a module listed above it, which is the healthy direction.
27→19 hyperlight_common.flatbuffer_wrappers.function_types uses hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated✕
- Connections
- 2 pairs of types, where a type in hyperlight_common.flatbuffer_wrappers.function_types uses a type in hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated.
- The types involved
hyperlight_common.flatbuffer_wrappers.function_types.ParameterValue→hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated.Parameterhyperlight_common.flatbuffer_wrappers.function_types.function_types$module→hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated.Parameter
- Direction
- hyperlight_common.flatbuffer_wrappers.function_types uses hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated, so a change to hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated can break hyperlight_common.flatbuffer_wrappers.function_types, while a change to hyperlight_common.flatbuffer_wrappers.function_types can't break hyperlight_common.flatbuffers.hyperlight.generated.parameter_generated.
- Position
- Below the diagonal: hyperlight_common.flatbuffer_wrappers.function_types uses a module listed above it, which is the healthy direction.
27→20 hyperlight_common.flatbuffer_wrappers.function_types uses hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated✕
- Connections
- 2 pairs of types, where a type in hyperlight_common.flatbuffer_wrappers.function_types uses a type in hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated.
- The types involved
hyperlight_common.flatbuffer_wrappers.function_types.ReturnValue→hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated.ReturnValueBoxhyperlight_common.flatbuffer_wrappers.function_types.function_types$module→hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated.ReturnValueBox
- Direction
- hyperlight_common.flatbuffer_wrappers.function_types uses hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated, so a change to hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated can break hyperlight_common.flatbuffer_wrappers.function_types, while a change to hyperlight_common.flatbuffer_wrappers.function_types can't break hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated.
- Position
- Below the diagonal: hyperlight_common.flatbuffer_wrappers.function_types uses a module listed above it, which is the healthy direction.
28→1 hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated uses hyperlight_common.flatbuffer_wrappers.guest_error✕
- Connections
- 1 pair of types, where a type in hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated uses a type in hyperlight_common.flatbuffer_wrappers.guest_error.
- The types involved
hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated.FunctionCallResult→hyperlight_common.flatbuffer_wrappers.guest_error.GuestError
- Direction
- hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated uses hyperlight_common.flatbuffer_wrappers.guest_error, so a change to hyperlight_common.flatbuffer_wrappers.guest_error can break hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated, while a change to hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated can't break hyperlight_common.flatbuffer_wrappers.guest_error.
- Position
- Below the diagonal: hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated uses a module listed above it, which is the healthy direction.
28→3 hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated uses hyperlight_common.virtq.pool.slot✕
- Connections
- 1 pair of types, where a type in hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated uses a type in hyperlight_common.virtq.pool.slot.
- The types involved
hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated.FunctionCallResult→hyperlight_common.virtq.pool.slot.Inner
- Direction
- hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated uses hyperlight_common.virtq.pool.slot, so a change to hyperlight_common.virtq.pool.slot can break hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated, while a change to hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated can't break hyperlight_common.virtq.pool.slot.
- Position
- Below the diagonal: hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated uses a module listed above it, which is the healthy direction.
28→20 hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated uses hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated✕
- Connections
- 1 pair of types, where a type in hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated uses a type in hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated.
- The types involved
hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated.FunctionCallResult→hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated.ReturnValueBox
- Direction
- hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated uses hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated, so a change to hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated can break hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated, while a change to hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated can't break hyperlight_common.flatbuffers.hyperlight.generated.return_value_box_generated.
- Position
- Below the diagonal: hyperlight_common.flatbuffers.hyperlight.generated.function_call_result_generated uses a module listed above it, which is the healthy direction.
29→15 hyperlight_common.virtq.consumer uses hyperlight_common.virtq.ring✕
- Connections
- 4 pairs of types, where a type in hyperlight_common.virtq.consumer uses a type in hyperlight_common.virtq.ring.
- The types involved
hyperlight_common.virtq.consumer.ChainState→hyperlight_common.virtq.ring.BufferElementhyperlight_common.virtq.consumer.VirtqConsumer→hyperlight_common.virtq.ring.Checkpointhyperlight_common.virtq.consumer.VirtqConsumer→hyperlight_common.virtq.ring.RingConsumerhyperlight_common.virtq.consumer.VirtqConsumer→hyperlight_common.virtq.ring.RingCursor
- Direction
- hyperlight_common.virtq.consumer uses hyperlight_common.virtq.ring, so a change to hyperlight_common.virtq.ring can break hyperlight_common.virtq.consumer, while a change to hyperlight_common.virtq.consumer can't break hyperlight_common.virtq.ring.
- Position
- Below the diagonal: hyperlight_common.virtq.consumer uses a module listed above it, which is the healthy direction.
29→22 hyperlight_common.virtq.consumer uses hyperlight_common.virtq✕
- Connections
- 8 pairs of types, where a type in hyperlight_common.virtq.consumer uses a type in hyperlight_common.virtq.
- The types involved
hyperlight_common.virtq.consumer.AckChain→hyperlight_common.virtq.Tokenhyperlight_common.virtq.consumer.ChainState→hyperlight_common.virtq.Tokenhyperlight_common.virtq.consumer.RecvChain→hyperlight_common.virtq.Tokenhyperlight_common.virtq.consumer.ReplyChain→hyperlight_common.virtq.Tokenhyperlight_common.virtq.consumer.VirtqConsumer→hyperlight_common.virtq.Layouthyperlight_common.virtq.consumer.VirtqConsumer→hyperlight_common.virtq.SuppressionKindhyperlight_common.virtq.consumer.VirtqConsumer→hyperlight_common.virtq.VirtqErrorhyperlight_common.virtq.consumer.WritableChain→hyperlight_common.virtq.Token
- Direction
- hyperlight_common.virtq.consumer uses hyperlight_common.virtq, so a change to hyperlight_common.virtq can break hyperlight_common.virtq.consumer, while a change to hyperlight_common.virtq.consumer can't break hyperlight_common.virtq.
- Position
- Below the diagonal: hyperlight_common.virtq.consumer uses a module listed above it, which is the healthy direction.
30→3 hyperlight_common.virtq.producer uses hyperlight_common.virtq.pool.slot✕
- Connections
- 3 pairs of types, where a type in hyperlight_common.virtq.producer uses a type in hyperlight_common.virtq.pool.slot.
- The types involved
hyperlight_common.virtq.producer.ChainBuilder→hyperlight_common.virtq.pool.slot.SlotPoolhyperlight_common.virtq.producer.OwnedChain→hyperlight_common.virtq.pool.slot.SlotPoolhyperlight_common.virtq.producer.VirtqProducer→hyperlight_common.virtq.pool.slot.SlotPool
- Direction
- hyperlight_common.virtq.producer uses hyperlight_common.virtq.pool.slot, so a change to hyperlight_common.virtq.pool.slot can break hyperlight_common.virtq.producer, while a change to hyperlight_common.virtq.producer can't break hyperlight_common.virtq.pool.slot.
- Position
- Below the diagonal: hyperlight_common.virtq.producer uses a module listed above it, which is the healthy direction.
30→14 hyperlight_common.virtq.producer uses hyperlight_common.virtq.buffer✕
- Connections
- 1 pair of types, where a type in hyperlight_common.virtq.producer uses a type in hyperlight_common.virtq.buffer.
- The types involved
hyperlight_common.virtq.producer.UsedChain→hyperlight_common.virtq.buffer.Segments
- Direction
- hyperlight_common.virtq.producer uses hyperlight_common.virtq.buffer, so a change to hyperlight_common.virtq.buffer can break hyperlight_common.virtq.producer, while a change to hyperlight_common.virtq.producer can't break hyperlight_common.virtq.buffer.
- Position
- Below the diagonal: hyperlight_common.virtq.producer uses a module listed above it, which is the healthy direction.
30→15 hyperlight_common.virtq.producer uses hyperlight_common.virtq.ring✕
- Connections
- 3 pairs of types, where a type in hyperlight_common.virtq.producer uses a type in hyperlight_common.virtq.ring.
- The types involved
hyperlight_common.virtq.producer.SubmitBatch→hyperlight_common.virtq.ring.RingCursorhyperlight_common.virtq.producer.VirtqProducer→hyperlight_common.virtq.ring.RingCursorhyperlight_common.virtq.producer.VirtqProducer→hyperlight_common.virtq.ring.RingProducer
- Direction
- hyperlight_common.virtq.producer uses hyperlight_common.virtq.ring, so a change to hyperlight_common.virtq.ring can break hyperlight_common.virtq.producer, while a change to hyperlight_common.virtq.producer can't break hyperlight_common.virtq.ring.
- Position
- Below the diagonal: hyperlight_common.virtq.producer uses a module listed above it, which is the healthy direction.
30→22 hyperlight_common.virtq.producer uses hyperlight_common.virtq✕
- Connections
- 4 pairs of types, where a type in hyperlight_common.virtq.producer uses a type in hyperlight_common.virtq.
- The types involved
hyperlight_common.virtq.producer.Inflight→hyperlight_common.virtq.Tokenhyperlight_common.virtq.producer.UsedChain→hyperlight_common.virtq.Tokenhyperlight_common.virtq.producer.VirtqProducer→hyperlight_common.virtq.Layouthyperlight_common.virtq.producer.VirtqProducer→hyperlight_common.virtq.SuppressionKind
- Direction
- hyperlight_common.virtq.producer uses hyperlight_common.virtq, so a change to hyperlight_common.virtq can break hyperlight_common.virtq.producer, while a change to hyperlight_common.virtq.producer can't break hyperlight_common.virtq.
- Position
- Below the diagonal: hyperlight_common.virtq.producer uses a module listed above it, which is the healthy direction.
31→6 hyperlight_host.hypervisor.virtual_machine.hvf uses hyperlight_host.hypervisor.regs.aarch64✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.hvf uses a type in hyperlight_host.hypervisor.regs.aarch64.
- The types involved
hyperlight_host.hypervisor.virtual_machine.hvf.HvfVm→hyperlight_host.hypervisor.regs.aarch64.CommonDebugRegs
- Direction
- hyperlight_host.hypervisor.virtual_machine.hvf uses hyperlight_host.hypervisor.regs.aarch64, so a change to hyperlight_host.hypervisor.regs.aarch64 can break hyperlight_host.hypervisor.virtual_machine.hvf, while a change to hyperlight_host.hypervisor.virtual_machine.hvf can't break hyperlight_host.hypervisor.regs.aarch64.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.hvf uses a module listed above it, which is the healthy direction.
31→7 hyperlight_host.hypervisor.virtual_machine.hvf uses hyperlight_host.hypervisor.regs.aarch64.common_fpu✕
- Connections
- 2 pairs of types, where a type in hyperlight_host.hypervisor.virtual_machine.hvf uses a type in hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- The types involved
hyperlight_host.hypervisor.virtual_machine.hvf.HvfCpu→hyperlight_host.hypervisor.regs.aarch64.common_fpu.CommonFpuhyperlight_host.hypervisor.virtual_machine.hvf.HvfVm→hyperlight_host.hypervisor.regs.aarch64.common_fpu.CommonFpu
- Direction
- hyperlight_host.hypervisor.virtual_machine.hvf uses hyperlight_host.hypervisor.regs.aarch64.common_fpu, so a change to hyperlight_host.hypervisor.regs.aarch64.common_fpu can break hyperlight_host.hypervisor.virtual_machine.hvf, while a change to hyperlight_host.hypervisor.virtual_machine.hvf can't break hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.hvf uses a module listed above it, which is the healthy direction.
31→8 hyperlight_host.hypervisor.virtual_machine.hvf uses hyperlight_host.hypervisor.regs.aarch64.common_regs✕
- Connections
- 2 pairs of types, where a type in hyperlight_host.hypervisor.virtual_machine.hvf uses a type in hyperlight_host.hypervisor.regs.aarch64.common_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.hvf.HvfCpu→hyperlight_host.hypervisor.regs.aarch64.common_regs.CommonRegistershyperlight_host.hypervisor.virtual_machine.hvf.HvfVm→hyperlight_host.hypervisor.regs.aarch64.common_regs.CommonRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine.hvf uses hyperlight_host.hypervisor.regs.aarch64.common_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.common_regs can break hyperlight_host.hypervisor.virtual_machine.hvf, while a change to hyperlight_host.hypervisor.virtual_machine.hvf can't break hyperlight_host.hypervisor.regs.aarch64.common_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.hvf uses a module listed above it, which is the healthy direction.
31→9 hyperlight_host.hypervisor.virtual_machine.hvf uses hyperlight_host.hypervisor.regs.aarch64.special_regs✕
- Connections
- 2 pairs of types, where a type in hyperlight_host.hypervisor.virtual_machine.hvf uses a type in hyperlight_host.hypervisor.regs.aarch64.special_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.hvf.HvfCpu→hyperlight_host.hypervisor.regs.aarch64.special_regs.CommonSpecialRegistershyperlight_host.hypervisor.virtual_machine.hvf.HvfVm→hyperlight_host.hypervisor.regs.aarch64.special_regs.CommonSpecialRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine.hvf uses hyperlight_host.hypervisor.regs.aarch64.special_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.special_regs can break hyperlight_host.hypervisor.virtual_machine.hvf, while a change to hyperlight_host.hypervisor.virtual_machine.hvf can't break hyperlight_host.hypervisor.regs.aarch64.special_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.hvf uses a module listed above it, which is the healthy direction.
31→17 hyperlight_host.hypervisor.virtual_machine.hvf uses hyperlight_host.hypervisor.virtual_machine✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.hvf uses a type in hyperlight_host.hypervisor.virtual_machine.
- The types involved
hyperlight_host.hypervisor.virtual_machine.hvf.HvfVm→hyperlight_host.hypervisor.virtual_machine.VirtualMachine
- Direction
- hyperlight_host.hypervisor.virtual_machine.hvf uses hyperlight_host.hypervisor.virtual_machine, so a change to hyperlight_host.hypervisor.virtual_machine can break hyperlight_host.hypervisor.virtual_machine.hvf, while a change to hyperlight_host.hypervisor.virtual_machine.hvf can't break hyperlight_host.hypervisor.virtual_machine.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.hvf uses a module listed above it, which is the healthy direction.
31→26 hyperlight_host.hypervisor.virtual_machine.hvf uses hyperlight_host.mem.shared_mem✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.hvf uses a type in hyperlight_host.mem.shared_mem.
- The types involved
hyperlight_host.hypervisor.virtual_machine.hvf.TlbiRegion→hyperlight_host.mem.shared_mem.ReadonlySharedMemory
- Direction
- hyperlight_host.hypervisor.virtual_machine.hvf uses hyperlight_host.mem.shared_mem, so a change to hyperlight_host.mem.shared_mem can break hyperlight_host.hypervisor.virtual_machine.hvf, while a change to hyperlight_host.hypervisor.virtual_machine.hvf can't break hyperlight_host.mem.shared_mem.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.hvf uses a module listed above it, which is the healthy direction.
32→27 hyperlight_common.flatbuffer_wrappers.function_call uses hyperlight_common.flatbuffer_wrappers.function_types✕
- Connections
- 2 pairs of types, where a type in hyperlight_common.flatbuffer_wrappers.function_call uses a type in hyperlight_common.flatbuffer_wrappers.function_types.
- The types involved
hyperlight_common.flatbuffer_wrappers.function_call.FunctionCall→hyperlight_common.flatbuffer_wrappers.function_types.ParameterValuehyperlight_common.flatbuffer_wrappers.function_call.FunctionCall→hyperlight_common.flatbuffer_wrappers.function_types.ReturnType
- Direction
- hyperlight_common.flatbuffer_wrappers.function_call uses hyperlight_common.flatbuffer_wrappers.function_types, so a change to hyperlight_common.flatbuffer_wrappers.function_types can break hyperlight_common.flatbuffer_wrappers.function_call, while a change to hyperlight_common.flatbuffer_wrappers.function_call can't break hyperlight_common.flatbuffer_wrappers.function_types.
- Position
- Below the diagonal: hyperlight_common.flatbuffer_wrappers.function_call uses a module listed above it, which is the healthy direction.
33→27 hyperlight_common.flatbuffer_wrappers.host_function_definition uses hyperlight_common.flatbuffer_wrappers.function_types✕
- Connections
- 2 pairs of types, where a type in hyperlight_common.flatbuffer_wrappers.host_function_definition uses a type in hyperlight_common.flatbuffer_wrappers.function_types.
- The types involved
hyperlight_common.flatbuffer_wrappers.host_function_definition.HostFunctionDefinition→hyperlight_common.flatbuffer_wrappers.function_types.ParameterTypehyperlight_common.flatbuffer_wrappers.host_function_definition.HostFunctionDefinition→hyperlight_common.flatbuffer_wrappers.function_types.ReturnType
- Direction
- hyperlight_common.flatbuffer_wrappers.host_function_definition uses hyperlight_common.flatbuffer_wrappers.function_types, so a change to hyperlight_common.flatbuffer_wrappers.function_types can break hyperlight_common.flatbuffer_wrappers.host_function_definition, while a change to hyperlight_common.flatbuffer_wrappers.host_function_definition can't break hyperlight_common.flatbuffer_wrappers.function_types.
- Position
- Below the diagonal: hyperlight_common.flatbuffer_wrappers.host_function_definition uses a module listed above it, which is the healthy direction.
34→3 hyperlight_guest.transport.context uses hyperlight_common.virtq.pool.slot✕
- Connections
- 1 pair of types, where a type in hyperlight_guest.transport.context uses a type in hyperlight_common.virtq.pool.slot.
- The types involved
hyperlight_guest.transport.context.context$module→hyperlight_common.virtq.pool.slot.SlotPool
- Direction
- hyperlight_guest.transport.context uses hyperlight_common.virtq.pool.slot, so a change to hyperlight_common.virtq.pool.slot can break hyperlight_guest.transport.context, while a change to hyperlight_guest.transport.context can't break hyperlight_common.virtq.pool.slot.
- Position
- Below the diagonal: hyperlight_guest.transport.context uses a module listed above it, which is the healthy direction.
34→21 hyperlight_guest.transport.context uses hyperlight_common.transport✕
- Connections
- 2 pairs of types, where a type in hyperlight_guest.transport.context uses a type in hyperlight_common.transport.
- The types involved
hyperlight_guest.transport.context.GuestContext→hyperlight_common.transport.EncodedMessagehyperlight_guest.transport.context.context$module→hyperlight_common.transport.EncodedMessage
- Direction
- hyperlight_guest.transport.context uses hyperlight_common.transport, so a change to hyperlight_common.transport can break hyperlight_guest.transport.context, while a change to hyperlight_guest.transport.context can't break hyperlight_common.transport.
- Position
- Below the diagonal: hyperlight_guest.transport.context uses a module listed above it, which is the healthy direction.
34→22 hyperlight_guest.transport.context uses hyperlight_common.virtq✕
- Connections
- 5 pairs of types, where a type in hyperlight_guest.transport.context uses a type in hyperlight_common.virtq.
- The types involved
hyperlight_guest.transport.context.NoopNotifier→hyperlight_common.virtq.Notifierhyperlight_guest.transport.context.NoopNotifier→hyperlight_common.virtq.QueueStatshyperlight_guest.transport.context.OutbNotifier→hyperlight_common.virtq.Notifierhyperlight_guest.transport.context.OutbNotifier→hyperlight_common.virtq.QueueStatshyperlight_guest.transport.context.QueueConfig→hyperlight_common.virtq.Layout
- Direction
- hyperlight_guest.transport.context uses hyperlight_common.virtq, so a change to hyperlight_common.virtq can break hyperlight_guest.transport.context, while a change to hyperlight_guest.transport.context can't break hyperlight_common.virtq.
- Position
- Below the diagonal: hyperlight_guest.transport.context uses a module listed above it, which is the healthy direction.
34→27 hyperlight_guest.transport.context uses hyperlight_common.flatbuffer_wrappers.function_types✕
- Connections
- 4 pairs of types, where a type in hyperlight_guest.transport.context uses a type in hyperlight_common.flatbuffer_wrappers.function_types.
- The types involved
hyperlight_guest.transport.context.GuestContext→hyperlight_common.flatbuffer_wrappers.function_types.FunctionCallResulthyperlight_guest.transport.context.GuestContext→hyperlight_common.flatbuffer_wrappers.function_types.ParameterValuehyperlight_guest.transport.context.GuestContext→hyperlight_common.flatbuffer_wrappers.function_types.ReturnTypehyperlight_guest.transport.context.ReplyCapacity→hyperlight_common.flatbuffer_wrappers.function_types.ReturnType
- Direction
- hyperlight_guest.transport.context uses hyperlight_common.flatbuffer_wrappers.function_types, so a change to hyperlight_common.flatbuffer_wrappers.function_types can break hyperlight_guest.transport.context, while a change to hyperlight_guest.transport.context can't break hyperlight_common.flatbuffer_wrappers.function_types.
- Position
- Below the diagonal: hyperlight_guest.transport.context uses a module listed above it, which is the healthy direction.
35→4 hyperlight_host.mem.mgr uses hyperlight_common.vmem✕
- Connections
- 4 pairs of types, where a type in hyperlight_host.mem.mgr uses a type in hyperlight_common.vmem.
- The types involved
hyperlight_host.mem.mgr.GuestPageTableBuffer→hyperlight_common.vmem.TableOpshyperlight_host.mem.mgr.GuestPageTableBuffer→hyperlight_common.vmem.TableReadOpshyperlight_host.mem.mgr.GuestPageTableBuffer→hyperlight_common.vmem.Voidhyperlight_host.mem.mgr.mgr$module→hyperlight_common.vmem.MappingKind
- Direction
- hyperlight_host.mem.mgr uses hyperlight_common.vmem, so a change to hyperlight_common.vmem can break hyperlight_host.mem.mgr, while a change to hyperlight_host.mem.mgr can't break hyperlight_common.vmem.
- Position
- Below the diagonal: hyperlight_host.mem.mgr uses a module listed above it, which is the healthy direction.
35→9 hyperlight_host.mem.mgr uses hyperlight_host.hypervisor.regs.aarch64.special_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.mem.mgr uses a type in hyperlight_host.hypervisor.regs.aarch64.special_regs.
- The types involved
hyperlight_host.mem.mgr.SandboxMemoryManager→hyperlight_host.hypervisor.regs.aarch64.special_regs.CommonSpecialRegisters
- Direction
- hyperlight_host.mem.mgr uses hyperlight_host.hypervisor.regs.aarch64.special_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.special_regs can break hyperlight_host.mem.mgr, while a change to hyperlight_host.mem.mgr can't break hyperlight_host.hypervisor.regs.aarch64.special_regs.
- Position
- Below the diagonal: hyperlight_host.mem.mgr uses a module listed above it, which is the healthy direction.
35→10 hyperlight_host.mem.mgr uses hyperlight_host.mem.memory_region✕
- Connections
- 1 pair of types, where a type in hyperlight_host.mem.mgr uses a type in hyperlight_host.mem.memory_region.
- The types involved
hyperlight_host.mem.mgr.mgr$module→hyperlight_host.mem.memory_region.MemoryRegionFlags
- Direction
- hyperlight_host.mem.mgr uses hyperlight_host.mem.memory_region, so a change to hyperlight_host.mem.memory_region can break hyperlight_host.mem.mgr, while a change to hyperlight_host.mem.mgr can't break hyperlight_host.mem.memory_region.
- Position
- Below the diagonal: hyperlight_host.mem.mgr uses a module listed above it, which is the healthy direction.
35→18 hyperlight_host.mem.mgr uses hyperlight_host.mem.layout✕
- Connections
- 1 pair of types, where a type in hyperlight_host.mem.mgr uses a type in hyperlight_host.mem.layout.
- The types involved
hyperlight_host.mem.mgr.SandboxMemoryManager→hyperlight_host.mem.layout.SandboxMemoryLayout
- Direction
- hyperlight_host.mem.mgr uses hyperlight_host.mem.layout, so a change to hyperlight_host.mem.layout can break hyperlight_host.mem.mgr, while a change to hyperlight_host.mem.mgr can't break hyperlight_host.mem.layout.
- Position
- Below the diagonal: hyperlight_host.mem.mgr uses a module listed above it, which is the healthy direction.
35→21 hyperlight_host.mem.mgr uses hyperlight_common.transport✕
- Connections
- 1 pair of types, where a type in hyperlight_host.mem.mgr uses a type in hyperlight_common.transport.
- The types involved
hyperlight_host.mem.mgr.SandboxMemoryManager→hyperlight_common.transport.EncodedMessage
- Direction
- hyperlight_host.mem.mgr uses hyperlight_common.transport, so a change to hyperlight_common.transport can break hyperlight_host.mem.mgr, while a change to hyperlight_host.mem.mgr can't break hyperlight_common.transport.
- Position
- Below the diagonal: hyperlight_host.mem.mgr uses a module listed above it, which is the healthy direction.
35→32 hyperlight_host.mem.mgr uses hyperlight_common.flatbuffer_wrappers.function_call✕
- Connections
- 1 pair of types, where a type in hyperlight_host.mem.mgr uses a type in hyperlight_common.flatbuffer_wrappers.function_call.
- The types involved
hyperlight_host.mem.mgr.SandboxMemoryManager→hyperlight_common.flatbuffer_wrappers.function_call.FunctionCall
- Direction
- hyperlight_host.mem.mgr uses hyperlight_common.flatbuffer_wrappers.function_call, so a change to hyperlight_common.flatbuffer_wrappers.function_call can break hyperlight_host.mem.mgr, while a change to hyperlight_host.mem.mgr can't break hyperlight_common.flatbuffer_wrappers.function_call.
- Position
- Below the diagonal: hyperlight_host.mem.mgr uses a module listed above it, which is the healthy direction.
36→2 hyperlight_host.hypervisor.gdb uses hyperlight_common.func.error✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.gdb uses a type in hyperlight_common.func.error.
- The types involved
hyperlight_host.hypervisor.gdb.GdbTargetError→hyperlight_common.func.error.Error
- Direction
- hyperlight_host.hypervisor.gdb uses hyperlight_common.func.error, so a change to hyperlight_common.func.error can break hyperlight_host.hypervisor.gdb, while a change to hyperlight_host.hypervisor.gdb can't break hyperlight_common.func.error.
- Position
- Below the diagonal: hyperlight_host.hypervisor.gdb uses a module listed above it, which is the healthy direction.
36→17 hyperlight_host.hypervisor.gdb uses hyperlight_host.hypervisor.virtual_machine✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.gdb uses a type in hyperlight_host.hypervisor.virtual_machine.
- The types involved
hyperlight_host.hypervisor.gdb.DebuggableVm→hyperlight_host.hypervisor.virtual_machine.VirtualMachine
- Direction
- hyperlight_host.hypervisor.gdb uses hyperlight_host.hypervisor.virtual_machine, so a change to hyperlight_host.hypervisor.virtual_machine can break hyperlight_host.hypervisor.gdb, while a change to hyperlight_host.hypervisor.gdb can't break hyperlight_host.hypervisor.virtual_machine.
- Position
- Below the diagonal: hyperlight_host.hypervisor.gdb uses a module listed above it, which is the healthy direction.
36→35 hyperlight_host.hypervisor.gdb uses hyperlight_host.mem.mgr✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.gdb uses a type in hyperlight_host.mem.mgr.
- The types involved
hyperlight_host.hypervisor.gdb.DebugMemoryView→hyperlight_host.mem.mgr.SandboxMemoryManager
- Direction
- hyperlight_host.hypervisor.gdb uses hyperlight_host.mem.mgr, so a change to hyperlight_host.mem.mgr can break hyperlight_host.hypervisor.gdb, while a change to hyperlight_host.hypervisor.gdb can't break hyperlight_host.mem.mgr.
- Position
- Below the diagonal: hyperlight_host.hypervisor.gdb uses a module listed above it, which is the healthy direction.
37→9 hyperlight_host.hypervisor.hyperlight_vm uses hyperlight_host.hypervisor.regs.aarch64.special_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.hyperlight_vm uses a type in hyperlight_host.hypervisor.regs.aarch64.special_regs.
- The types involved
hyperlight_host.hypervisor.hyperlight_vm.HyperlightVm→hyperlight_host.hypervisor.regs.aarch64.special_regs.CommonSpecialRegisters
- Direction
- hyperlight_host.hypervisor.hyperlight_vm uses hyperlight_host.hypervisor.regs.aarch64.special_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.special_regs can break hyperlight_host.hypervisor.hyperlight_vm, while a change to hyperlight_host.hypervisor.hyperlight_vm can't break hyperlight_host.hypervisor.regs.aarch64.special_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.hyperlight_vm uses a module listed above it, which is the healthy direction.
37→10 hyperlight_host.hypervisor.hyperlight_vm uses hyperlight_host.mem.memory_region✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.hyperlight_vm uses a type in hyperlight_host.mem.memory_region.
- The types involved
hyperlight_host.hypervisor.hyperlight_vm.hyperlight_vm$module→hyperlight_host.mem.memory_region.MemoryRegionFlags
- Direction
- hyperlight_host.hypervisor.hyperlight_vm uses hyperlight_host.mem.memory_region, so a change to hyperlight_host.mem.memory_region can break hyperlight_host.hypervisor.hyperlight_vm, while a change to hyperlight_host.hypervisor.hyperlight_vm can't break hyperlight_host.mem.memory_region.
- Position
- Below the diagonal: hyperlight_host.hypervisor.hyperlight_vm uses a module listed above it, which is the healthy direction.
37→23 hyperlight_host.hypervisor.hyperlight_vm uses hyperlight_host.hypervisor.hyperlight_vm.test_support✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.hyperlight_vm uses a type in hyperlight_host.hypervisor.hyperlight_vm.test_support.
- The types involved
hyperlight_host.hypervisor.hyperlight_vm.HyperlightVm→hyperlight_host.hypervisor.hyperlight_vm.test_support.VmFaultPlan
- Direction
- hyperlight_host.hypervisor.hyperlight_vm uses hyperlight_host.hypervisor.hyperlight_vm.test_support, so a change to hyperlight_host.hypervisor.hyperlight_vm.test_support can break hyperlight_host.hypervisor.hyperlight_vm, while a change to hyperlight_host.hypervisor.hyperlight_vm can't break hyperlight_host.hypervisor.hyperlight_vm.test_support.
- Position
- Below the diagonal: hyperlight_host.hypervisor.hyperlight_vm uses a module listed above it, which is the healthy direction.
37→26 hyperlight_host.hypervisor.hyperlight_vm uses hyperlight_host.mem.shared_mem✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.hyperlight_vm uses a type in hyperlight_host.mem.shared_mem.
- The types involved
hyperlight_host.hypervisor.hyperlight_vm.HyperlightVm→hyperlight_host.mem.shared_mem.GuestSharedMemory
- Direction
- hyperlight_host.hypervisor.hyperlight_vm uses hyperlight_host.mem.shared_mem, so a change to hyperlight_host.mem.shared_mem can break hyperlight_host.hypervisor.hyperlight_vm, while a change to hyperlight_host.hypervisor.hyperlight_vm can't break hyperlight_host.mem.shared_mem.
- Position
- Below the diagonal: hyperlight_host.hypervisor.hyperlight_vm uses a module listed above it, which is the healthy direction.
37→35 hyperlight_host.hypervisor.hyperlight_vm uses hyperlight_host.mem.mgr✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.hyperlight_vm uses a type in hyperlight_host.mem.mgr.
- The types involved
hyperlight_host.hypervisor.hyperlight_vm.HyperlightVm→hyperlight_host.mem.mgr.SandboxMemoryManager
- Direction
- hyperlight_host.hypervisor.hyperlight_vm uses hyperlight_host.mem.mgr, so a change to hyperlight_host.mem.mgr can break hyperlight_host.hypervisor.hyperlight_vm, while a change to hyperlight_host.hypervisor.hyperlight_vm can't break hyperlight_host.mem.mgr.
- Position
- Below the diagonal: hyperlight_host.hypervisor.hyperlight_vm uses a module listed above it, which is the healthy direction.
37→36 hyperlight_host.hypervisor.hyperlight_vm uses hyperlight_host.hypervisor.gdb✕
- Connections
- 5 pairs of types, where a type in hyperlight_host.hypervisor.hyperlight_vm uses a type in hyperlight_host.hypervisor.gdb.
- The types involved
hyperlight_host.hypervisor.hyperlight_vm.HyperlightVm→hyperlight_host.hypervisor.gdb.DebugCommChannelhyperlight_host.hypervisor.hyperlight_vm.HyperlightVm→hyperlight_host.hypervisor.gdb.DebugMemoryViewhyperlight_host.hypervisor.hyperlight_vm.HyperlightVm→hyperlight_host.hypervisor.gdb.DebugMsghyperlight_host.hypervisor.hyperlight_vm.HyperlightVm→hyperlight_host.hypervisor.gdb.DebugResponsehyperlight_host.hypervisor.hyperlight_vm.HyperlightVm→hyperlight_host.hypervisor.gdb.VcpuStopReason
- Direction
- hyperlight_host.hypervisor.hyperlight_vm uses hyperlight_host.hypervisor.gdb, so a change to hyperlight_host.hypervisor.gdb can break hyperlight_host.hypervisor.hyperlight_vm, while a change to hyperlight_host.hypervisor.hyperlight_vm can't break hyperlight_host.hypervisor.gdb.
- Position
- Below the diagonal: hyperlight_host.hypervisor.hyperlight_vm uses a module listed above it, which is the healthy direction.
38→6 hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses hyperlight_host.hypervisor.regs.aarch64✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses a type in hyperlight_host.hypervisor.regs.aarch64.
- The types involved
hyperlight_host.hypervisor.virtual_machine.kvm.x86_64.KvmVm→hyperlight_host.hypervisor.regs.aarch64.CommonDebugRegs
- Direction
- hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses hyperlight_host.hypervisor.regs.aarch64, so a change to hyperlight_host.hypervisor.regs.aarch64 can break hyperlight_host.hypervisor.virtual_machine.kvm.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 can't break hyperlight_host.hypervisor.regs.aarch64.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses a module listed above it, which is the healthy direction.
38→7 hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.common_fpu✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses a type in hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- The types involved
hyperlight_host.hypervisor.virtual_machine.kvm.x86_64.KvmVm→hyperlight_host.hypervisor.regs.aarch64.common_fpu.CommonFpu
- Direction
- hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.common_fpu, so a change to hyperlight_host.hypervisor.regs.aarch64.common_fpu can break hyperlight_host.hypervisor.virtual_machine.kvm.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 can't break hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses a module listed above it, which is the healthy direction.
38→8 hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.common_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses a type in hyperlight_host.hypervisor.regs.aarch64.common_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.kvm.x86_64.KvmVm→hyperlight_host.hypervisor.regs.aarch64.common_regs.CommonRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.common_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.common_regs can break hyperlight_host.hypervisor.virtual_machine.kvm.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 can't break hyperlight_host.hypervisor.regs.aarch64.common_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses a module listed above it, which is the healthy direction.
38→9 hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.special_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses a type in hyperlight_host.hypervisor.regs.aarch64.special_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.kvm.x86_64.KvmVm→hyperlight_host.hypervisor.regs.aarch64.special_regs.CommonSpecialRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.special_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.special_regs can break hyperlight_host.hypervisor.virtual_machine.kvm.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 can't break hyperlight_host.hypervisor.regs.aarch64.special_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses a module listed above it, which is the healthy direction.
38→17 hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses hyperlight_host.hypervisor.virtual_machine✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses a type in hyperlight_host.hypervisor.virtual_machine.
- The types involved
hyperlight_host.hypervisor.virtual_machine.kvm.x86_64.KvmVm→hyperlight_host.hypervisor.virtual_machine.VirtualMachine
- Direction
- hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses hyperlight_host.hypervisor.virtual_machine, so a change to hyperlight_host.hypervisor.virtual_machine can break hyperlight_host.hypervisor.virtual_machine.kvm.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 can't break hyperlight_host.hypervisor.virtual_machine.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses a module listed above it, which is the healthy direction.
38→36 hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses hyperlight_host.hypervisor.gdb✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses a type in hyperlight_host.hypervisor.gdb.
- The types involved
hyperlight_host.hypervisor.virtual_machine.kvm.x86_64.KvmVm→hyperlight_host.hypervisor.gdb.DebuggableVm
- Direction
- hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses hyperlight_host.hypervisor.gdb, so a change to hyperlight_host.hypervisor.gdb can break hyperlight_host.hypervisor.virtual_machine.kvm.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 can't break hyperlight_host.hypervisor.gdb.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.kvm.x86_64 uses a module listed above it, which is the healthy direction.
39→6 hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses hyperlight_host.hypervisor.regs.aarch64✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses a type in hyperlight_host.hypervisor.regs.aarch64.
- The types involved
hyperlight_host.hypervisor.virtual_machine.mshv.x86_64.MshvVm→hyperlight_host.hypervisor.regs.aarch64.CommonDebugRegs
- Direction
- hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses hyperlight_host.hypervisor.regs.aarch64, so a change to hyperlight_host.hypervisor.regs.aarch64 can break hyperlight_host.hypervisor.virtual_machine.mshv.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 can't break hyperlight_host.hypervisor.regs.aarch64.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses a module listed above it, which is the healthy direction.
39→7 hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.common_fpu✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses a type in hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- The types involved
hyperlight_host.hypervisor.virtual_machine.mshv.x86_64.MshvVm→hyperlight_host.hypervisor.regs.aarch64.common_fpu.CommonFpu
- Direction
- hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.common_fpu, so a change to hyperlight_host.hypervisor.regs.aarch64.common_fpu can break hyperlight_host.hypervisor.virtual_machine.mshv.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 can't break hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses a module listed above it, which is the healthy direction.
39→8 hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.common_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses a type in hyperlight_host.hypervisor.regs.aarch64.common_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.mshv.x86_64.MshvVm→hyperlight_host.hypervisor.regs.aarch64.common_regs.CommonRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.common_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.common_regs can break hyperlight_host.hypervisor.virtual_machine.mshv.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 can't break hyperlight_host.hypervisor.regs.aarch64.common_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses a module listed above it, which is the healthy direction.
39→9 hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.special_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses a type in hyperlight_host.hypervisor.regs.aarch64.special_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.mshv.x86_64.MshvVm→hyperlight_host.hypervisor.regs.aarch64.special_regs.CommonSpecialRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.special_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.special_regs can break hyperlight_host.hypervisor.virtual_machine.mshv.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 can't break hyperlight_host.hypervisor.regs.aarch64.special_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses a module listed above it, which is the healthy direction.
39→17 hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses hyperlight_host.hypervisor.virtual_machine✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses a type in hyperlight_host.hypervisor.virtual_machine.
- The types involved
hyperlight_host.hypervisor.virtual_machine.mshv.x86_64.MshvVm→hyperlight_host.hypervisor.virtual_machine.VirtualMachine
- Direction
- hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses hyperlight_host.hypervisor.virtual_machine, so a change to hyperlight_host.hypervisor.virtual_machine can break hyperlight_host.hypervisor.virtual_machine.mshv.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 can't break hyperlight_host.hypervisor.virtual_machine.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses a module listed above it, which is the healthy direction.
39→36 hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses hyperlight_host.hypervisor.gdb✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses a type in hyperlight_host.hypervisor.gdb.
- The types involved
hyperlight_host.hypervisor.virtual_machine.mshv.x86_64.MshvVm→hyperlight_host.hypervisor.gdb.DebuggableVm
- Direction
- hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses hyperlight_host.hypervisor.gdb, so a change to hyperlight_host.hypervisor.gdb can break hyperlight_host.hypervisor.virtual_machine.mshv.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 can't break hyperlight_host.hypervisor.gdb.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.mshv.x86_64 uses a module listed above it, which is the healthy direction.
40→6 hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.regs.aarch64✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a type in hyperlight_host.hypervisor.regs.aarch64.
- The types involved
hyperlight_host.hypervisor.virtual_machine.whp.x86_64.WhpVm→hyperlight_host.hypervisor.regs.aarch64.CommonDebugRegs
- Direction
- hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.regs.aarch64, so a change to hyperlight_host.hypervisor.regs.aarch64 can break hyperlight_host.hypervisor.virtual_machine.whp.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.whp.x86_64 can't break hyperlight_host.hypervisor.regs.aarch64.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a module listed above it, which is the healthy direction.
40→7 hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.common_fpu✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a type in hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- The types involved
hyperlight_host.hypervisor.virtual_machine.whp.x86_64.WhpVm→hyperlight_host.hypervisor.regs.aarch64.common_fpu.CommonFpu
- Direction
- hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.common_fpu, so a change to hyperlight_host.hypervisor.regs.aarch64.common_fpu can break hyperlight_host.hypervisor.virtual_machine.whp.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.whp.x86_64 can't break hyperlight_host.hypervisor.regs.aarch64.common_fpu.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a module listed above it, which is the healthy direction.
40→8 hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.common_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a type in hyperlight_host.hypervisor.regs.aarch64.common_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.whp.x86_64.WhpVm→hyperlight_host.hypervisor.regs.aarch64.common_regs.CommonRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.common_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.common_regs can break hyperlight_host.hypervisor.virtual_machine.whp.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.whp.x86_64 can't break hyperlight_host.hypervisor.regs.aarch64.common_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a module listed above it, which is the healthy direction.
40→9 hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.special_regs✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a type in hyperlight_host.hypervisor.regs.aarch64.special_regs.
- The types involved
hyperlight_host.hypervisor.virtual_machine.whp.x86_64.WhpVm→hyperlight_host.hypervisor.regs.aarch64.special_regs.CommonSpecialRegisters
- Direction
- hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.regs.aarch64.special_regs, so a change to hyperlight_host.hypervisor.regs.aarch64.special_regs can break hyperlight_host.hypervisor.virtual_machine.whp.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.whp.x86_64 can't break hyperlight_host.hypervisor.regs.aarch64.special_regs.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a module listed above it, which is the healthy direction.
40→17 hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.virtual_machine✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a type in hyperlight_host.hypervisor.virtual_machine.
- The types involved
hyperlight_host.hypervisor.virtual_machine.whp.x86_64.WhpVm→hyperlight_host.hypervisor.virtual_machine.VirtualMachine
- Direction
- hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.virtual_machine, so a change to hyperlight_host.hypervisor.virtual_machine can break hyperlight_host.hypervisor.virtual_machine.whp.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.whp.x86_64 can't break hyperlight_host.hypervisor.virtual_machine.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a module listed above it, which is the healthy direction.
40→25 hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.virtual_machine.whp.aarch64✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a type in hyperlight_host.hypervisor.virtual_machine.whp.aarch64.
- The types involved
hyperlight_host.hypervisor.virtual_machine.whp.x86_64.WhpVm→hyperlight_host.hypervisor.virtual_machine.whp.aarch64.NoSurrogateGuard
- Direction
- hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.virtual_machine.whp.aarch64, so a change to hyperlight_host.hypervisor.virtual_machine.whp.aarch64 can break hyperlight_host.hypervisor.virtual_machine.whp.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.whp.x86_64 can't break hyperlight_host.hypervisor.virtual_machine.whp.aarch64.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a module listed above it, which is the healthy direction.
40→36 hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.gdb✕
- Connections
- 1 pair of types, where a type in hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a type in hyperlight_host.hypervisor.gdb.
- The types involved
hyperlight_host.hypervisor.virtual_machine.whp.x86_64.WhpVm→hyperlight_host.hypervisor.gdb.DebuggableVm
- Direction
- hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses hyperlight_host.hypervisor.gdb, so a change to hyperlight_host.hypervisor.gdb can break hyperlight_host.hypervisor.virtual_machine.whp.x86_64, while a change to hyperlight_host.hypervisor.virtual_machine.whp.x86_64 can't break hyperlight_host.hypervisor.gdb.
- Position
- Below the diagonal: hyperlight_host.hypervisor.virtual_machine.whp.x86_64 uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 53 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
| A02:2025 — Security Misconfiguration | 8 | Medium |
Roadmap
First, codify disaster recovery and backup strategies in infrastructure as code to ensure robust geo-redundancy and recovery capabilities. Next, implement structured logging to replace interpolated messages and establish manual approval gates for deployments to prevent bad builds from reaching users. Finally, resolve the missing architecture decision record and refactor the highest-complexity code components to improve maintainability and reduce cognitive load.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.9 pts | Low | ADR Quality |
| Codify backups + geo-recovery in IaC (snapshot/replication/geo-redundant) to back the DR plan. | +2.9 pts | Medium | DR & Backup |
| Interpolated log message defeats structured logging | +2.8 pts | Medium | Structured logging |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.4 pts | Medium | Deployment & Rollback |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with guest_trace_data.rs. | +0.7 pts | Low | Knowledge Freshness |
| Bring the 23 bodies over 15 down to 15 or less in Cognitive Complexity — start with hyperlight_component_util::component::read_component_single_exported_type (cognitive 54), MshvVm::run_vcpu (cognitive 52), HyperlightVm::run (cognitive 39). | +1.6 pts | High | Cognitive Complexity |
| 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. | +1.2 pts | Medium | Architecture documentation |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +1.0 pts | Medium | Observability |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/hyperlight_component_util/src/rtypes.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/hyperlight_component_util/src/hl.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/hyperlight_component_util/src/component.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/hyperlight_host/src/hypervisor/virtual_machine/hvf/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/hyperlight_host/src/hypervisor/hyperlight_vm/x86_64.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/hyperlight_host/src/hypervisor/virtual_machine/kvm/aarch64.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/hyperlight_common/src/flatbuffer_wrappers/guest_trace_data.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/trace_dump/main.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/hyperlight_host/src/mem/shared_mem.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, 323 of 348 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 coverage step in CI (`Coverage Report`) 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, 89 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) — 2 | RUN rustup toolchain install 1.86 && rustup default 1.86 3 | -------------------- ERROR: failed to solve: dependabot/dependabot-script: failed to resolve source metadata for docker.io/dependabot/dependabot-script:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed; 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, c 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, c 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), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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 C, 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.
- X26 Unsynchronised callback handoff — 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, Kotlin, Scala, Go, Swift, Python and Ruby source only, and no C# was loaded, no Java, Kotlin, Scala, Go, Swift, Python or Ruby was found, and this repository's C 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.
- 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. 66 further occurrence(s) are not listed individually; the score already reflects all 106.
- 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 C, 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.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
9 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was HyperlightVm::run at 26. A further 10 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 hyperlight_host::hypervisor::virtual_machine::whp::x86_64::msr_to_whv_register_name at 76 — they are counted neither in the figure above nor in this dimension's score. 7 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: src/hyperlight_common/src/outb.rs (Exception::try_from at 24), src/hyperlight_host/src/hypervisor/regs/x86_64/standard_regs.rs (CommonRegisters::try_from at 23), src/hyperlight_host/src/hypervisor/regs/x86_64/special_regs.rs (CommonSpecialRegisters::try_from at 22), src/hyperlight_component_util/src/wf.rs (Ctx::wf_value at 21), src/hyperlight_component_util/src/substitute.rs (Substitution::value at 20), and 2 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 9 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with HyperlightVm::run (cyclomatic 26), hyperlight_component_util::rtypes::emit_value (cyclomatic 25), Ctx::subtype_value (cyclomatic 24). — 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 9 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- 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
23 function(s) exceeded the cognitive complexity threshold of 15; the worst was hyperlight_component_util::component::read_component_single_exported_type at 54.
What to do
- Bring the 23 bodies over 15 down to 15 or less in Cognitive Complexity — start with hyperlight_component_util::component::read_component_single_exported_type (cognitive 54), MshvVm::run_vcpu (cognitive 52), HyperlightVm::run (cognitive 39). — 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 23 together lifts Cognitive Complexity from 6.8 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
29 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 14 FileTooLong finding(s) in God Classes — start with x86_64.rs (3), mod.rs (2), shared_mem.rs. — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 6 MethodTooLong finding(s) in God Classes — start with x86_64.rs (3), function_call.rs, guest_trace_data.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with etypes.rs, layout.rs, mod.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
68 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. 3 of the 69 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 10 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with x86_64.rs (5), memory.rs, paging.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 6 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with lib.rs, rtypes.rs, aarch64.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with x86_64_target.rs, special_regs.rs, x86_64.rs. — One of this dimension's main actionable groups (5 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
13 production modules (Cargo), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 10 of the 13 (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).
- Resolve the 1 Unstable project hyperlight-guest-bin finding(s) in Coupling. — One of this dimension's main actionable groups (1 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 129 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs, ptr_offset.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
1194 test methods: 1094 unit, 100 integration, 0 BDD, 0 e2e. The Rust suite contributes 1194 `#[test]` function(s) across 89 file(s) declaring at least one; its unit/integration split is Cargo's own — 4 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
6 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 375 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 6 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/hyperlight_host/src/sandbox/snapshot/file/config.rs (14×21=294); src/hyperlight_host/src/hypervisor/hyperlight_vm/mod.rs (7×26=182); src/hyperlight_host/src/sandbox/snapshot/file/mod.rs (9×15=135)
What to do
- Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (2), config.rs, x86_64.rs. — One of this dimension's main actionable groups (5 warning-level).
D16 · Bus Factor
17 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/hyperlight_common/src/virtq/producer.rs. Counted over 147 of the 216 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 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
72 deducted task-comment markers across 76767 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 71 TodoComment finding(s) in Explicit Debt — start with mod.rs (8), handle.rs (6), paging.rs (5). — One of this dimension's main actionable groups (71 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with rtypes.rs. — One of this dimension's main actionable groups (1 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. 28 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 13 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)
53 finding(s): 0 critical, 52 high, 1 medium, 0 low. semgrep hit a parse error in 3 file(s) — `hack/update-actions.sh` (line 55), `src/hyperlight_guest_capi/src/dispatch.rs` (line 42, line 45, line 52, …), `src/hyperlight_guest_capi/src/error.rs` (line 30, line 35) — 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 17 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 31 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9), REDACTED (5), REDACTED (4). — One of this dimension's main actionable groups (31 issue-level).
- Resolve the 20 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (20 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
8 finding(s): 0 critical, 0 high, 1 medium, 7 low.
What to do
- Resolve the 7 Low IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 recommendation-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
5 of 147 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/hyperlight_common/src/flatbuffer_wrappers/guest_trace_data.rs. Counted over 147 of the 216 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with guest_trace_data.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Orphaned file finding(s) in Knowledge Freshness — start with state.rs, log_level.rs, event_loop.rs. — One of this dimension's main actionable groups (4 recommendation-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: elf.rs↔mgr.rs 50%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with elf.rs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
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
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 11 of 14 project(s) that lack one — worth up to 1.6 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
- docs/README.md links to `./debugging-hyperlight.md`, but `docs/debugging-hyperlight.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/README.md:45
What to do
- Reconcile the README with reality: docs/README.md links to `./debugging-hyperlight.md`, but `docs/debugging-hyperlight.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 8/11 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `src/hyperlight_ci`, `src/hyperlight_guest_macro`, `src/trace_dump`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `gitsubmodule` — add that `package-ecosystem` entry to .github/dependabot.yml 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
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P5 · DR & Backup
What to do
- Codify backups + geo-recovery in IaC (snapshot/replication/geo-redundant) to back the DR plan.
- Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency 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
- `error!` at line 120 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/hyperlight_host/src/lib.rs:120
- `error!` at line 124 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`. — src/hyperlight_host/src/lib.rs:124
- `error!` at line 128 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`. — src/hyperlight_host/src/lib.rs:128
- `error!` at line 134 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`. — src/hyperlight_host/src/lib.rs:134
- `info!` at line 169 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/hyperlight_host/src/lib.rs:169
- `info!` at line 173 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/hyperlight_host/src/lib.rs:173
- `info!` at line 182 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/hyperlight_host/src/lib.rs:182
- `info!` at line 188 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/hyperlight_host/src/lib.rs:188
- `error!` at line 1030 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`. — src/hyperlight_host/src/mem/mgr.rs:1030
- `error!` at line 318 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`. — src/hyperlight_host/src/mem/shared_mem.rs:318
- `error!` at line 348 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`. — src/hyperlight_host/src/mem/shared_mem.rs:348
- `error!` at line 370 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`. — src/hyperlight_host/src/mem/shared_mem.rs:370
- `error!` at line 503 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`. — src/hyperlight_host/src/mem/shared_mem.rs:503
- `error!` at line 275 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`. — src/hyperlight_host/src/hypervisor/crashdump.rs:275
- `warn!` at line 311 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`. — src/hyperlight_host/src/hypervisor/crashdump.rs:311
- `error!` at line 361 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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`. — src/hyperlight_host/src/hypervisor/mod.rs:361
- `error!` at line 374 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`. — src/hyperlight_host/src/hypervisor/mod.rs:374
- `error!` at line 396 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`. — src/hyperlight_host/src/hypervisor/mod.rs:396
- `warn!` at line 72 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`. — src/hyperlight_host/src/hypervisor/surrogate_process.rs:72
- `error!` at line 179 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`. — src/hyperlight_host/src/hypervisor/surrogate_process.rs:179
- `error!` at line 191 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`. — src/hyperlight_host/src/hypervisor/surrogate_process.rs:191
- `error!` at line 213 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`. — src/hyperlight_host/src/hypervisor/surrogate_process.rs:213
- `error!` at line 243 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`. — src/hyperlight_host/src/hypervisor/surrogate_process.rs:243
- `error!` at line 250 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`. — src/hyperlight_host/src/hypervisor/surrogate_process.rs:250
- `warn!` at line 117 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`. — src/hyperlight_host/src/hypervisor/surrogate_process_manager.rs:117
- `warn!` 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: `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`. — src/hyperlight_host/src/hypervisor/surrogate_process_manager.rs:122
- `info!` at line 251 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/hyperlight_host/src/hypervisor/surrogate_process_manager.rs:251
- `info!` 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: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/hyperlight_host/src/hypervisor/surrogate_process_manager.rs:288
- `error!` at line 331 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`. — src/hyperlight_host/src/hypervisor/surrogate_process_manager.rs:331
- `error!` at line 343 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`. — src/hyperlight_host/src/hypervisor/surrogate_process_manager.rs:343
- `info!` at line 431 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/hyperlight_host/src/hypervisor/surrogate_process_manager.rs:431
- `info!` at line 316 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/hyperlight_host/src/hypervisor/virtual_machine/whp/aarch64.rs:316
- `error!` at line 390 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`. — src/hyperlight_host/src/hypervisor/virtual_machine/whp/aarch64.rs:390
- `error!` at line 393 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`. — src/hyperlight_host/src/hypervisor/virtual_machine/whp/aarch64.rs:393
- `error!` at line 871 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`. — src/hyperlight_host/src/hypervisor/virtual_machine/whp/aarch64.rs:871
- `error!` at line 874 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`. — src/hyperlight_host/src/hypervisor/virtual_machine/whp/aarch64.rs:874
- `error!` at line 24 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`. — src/hyperlight_host/src/hypervisor/virtual_machine/whp/mod.rs:24
- `error!` at line 27 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`. — src/hyperlight_host/src/hypervisor/virtual_machine/whp/mod.rs:27
- `error!` at line 637 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`. — src/hyperlight_host/src/hypervisor/virtual_machine/whp/x86_64.rs:637
- `error!` at line 643 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`. — src/hyperlight_host/src/hypervisor/virtual_machine/whp/x86_64.rs:643
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 74% | Strong | Solid. |
| Readiness | 67% | Adequate — gated by P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 77% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 94% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X9 Subsumed condition operand — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 65 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) — 2 | RUN rustup toolchain install 1.86 && rustup default 1.86 3 | -------------------- ERROR: failed to solve: dependabot/dependabot-script: failed to resolve source metadata for docker.io/dependabot/dependabot-script:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed; 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 — ~12986 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not 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 (58 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
- 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.
- S1 Web-Security Posture — No web surface: 202 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 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
- 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.
Appendix A — Findings (grouped)
Critical — 53 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge src/hyperlight_common/src/flatbuffer_wrappers/guest_trace_data.rs:1
Serious — 219 finding(s)
- TodoComment src/trace_dump/main.rs:82
- TodoComment src/tests/rust_guests/witguest/src/main.rs:183
- TodoComment src/tests/rust_guests/simpleguest/src/main.rs:1777
- TodoComment src/hyperlight_host/tests/integration_test.rs:744
- TodoComment src/hyperlight_host/tests/integration_test.rs:749
- TodoComment src/hyperlight_host/tests/integration_test.rs:754
- TodoComment src/hyperlight_host/tests/integration_test.rs:759
- TodoComment src/hyperlight_host/src/sandbox/config.rs:110
- TodoComment src/hyperlight_host/src/sandbox/initialized.rs:836
- TodoComment src/hyperlight_host/src/sandbox/uninitialized.rs:72
- TodoComment src/hyperlight_host/src/sandbox/uninitialized.rs:582
- TodoComment src/hyperlight_host/src/sandbox/snapshot/mod.rs:42
- TodoComment src/hyperlight_host/src/sandbox/snapshot/mod.rs:68
- TodoComment src/hyperlight_host/src/sandbox/snapshot/mod.rs:493
- TodoComment src/hyperlight_host/src/sandbox/snapshot/file/config.rs:111
- TodoComment src/hyperlight_host/src/mem/elf.rs:106
- TodoComment src/hyperlight_host/src/mem/exe.rs:105
- TodoComment src/hyperlight_host/src/mem/shared_mem.rs:1437
- TodoComment src/hyperlight_host/src/mem/shared_mem.rs:1453
- TodoComment src/hyperlight_host/src/mem/virtq/mem.rs:49
- TodoComment src/hyperlight_host/src/hypervisor/virtual_machine/mod.rs:653
- TodoComment src/hyperlight_host/src/hypervisor/virtual_machine/mshv/aarch64.rs:11
- TodoComment src/hyperlight_host/src/hypervisor/virtual_machine/kvm/aarch64.rs:4
- TodoComment src/hyperlight_host/src/hypervisor/virtual_machine/hvf/mod.rs:252
- TodoComment src/hyperlight_host/src/hypervisor/virtual_machine/hvf/mod.rs:807
- FileTooLong: whp/x86_64.rs src/hyperlight_host/src/hypervisor/virtual_machine/whp/x86_64.rs
- FileTooLong: mem/shared_mem.rs src/hyperlight_host/src/mem/shared_mem.rs
- FileTooLong: hvf/mod.rs src/hyperlight_host/src/hypervisor/virtual_machine/hvf/mod.rs
- FileTooLong: virtq/ring.rs src/hyperlight_common/src/virtq/ring.rs
- FileTooLong: trace_dump/main.rs src/trace_dump/main.rs
- FileTooLong: mem/mgr.rs src/hyperlight_host/src/mem/mgr.rs
- FileTooLong: mshv/x86_64.rs src/hyperlight_host/src/hypervisor/virtual_machine/mshv/x86_64.rs
- FileTooLong: src/rtypes.rs src/hyperlight_component_util/src/rtypes.rs
- FileTooLong: whp/aarch64.rs src/hyperlight_host/src/hypervisor/virtual_machine/whp/aarch64.rs
- FileTooLong: flatbuffer_wrappers/function_types.rs src/hyperlight_common/src/flatbuffer_wrappers/function_types.rs
- FileTooLong: virtq/producer.rs src/hyperlight_common/src/virtq/producer.rs
- FileTooLong: hyperlight_vm/x86_64.rs src/hyperlight_host/src/hypervisor/hyperlight_vm/x86_64.rs
- FileTooLong: src/emit.rs src/hyperlight_component_util/src/emit.rs
- FileTooLong: hyperlight_vm/mod.rs src/hyperlight_host/src/hypervisor/hyperlight_vm/mod.rs
- Duplicated block (7 lines × 2) src/hyperlight_guest_bin/src/memory.rs:128
- Duplicated block (7 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/whp/x86_64.rs:807
- Duplicated block (7 lines × 2) src/hyperlight_guest/src/arch/aarch64/paging.rs:22
- Duplicated block (7 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/kvm/x86_64.rs:437
- Duplicated block (7 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/kvm/x86_64.rs:453
- Duplicated block (7 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/kvm/x86_64.rs:473
- Duplicated block (7 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/kvm/x86_64.rs:492
- Duplicated block (7 lines × 2) src/hyperlight_component_util/src/rtypes.rs:364
- Duplicated block (7 lines × 2) src/hyperlight_host/src/sandbox/initialized.rs:870
- Duplicated block (7 lines × 2) src/hyperlight_host/src/sandbox/snapshot/file/transport.rs:90
- hyperlight_component_util::component::read_component_single_exported_type (cognitive 54) src/hyperlight_component_util/src/component.rs:70
- hyperlight_component_util::rtypes::emit_value (cognitive 33) src/hyperlight_component_util/src/rtypes.rs:317
- hyperlight_component_util::rtypes::try_find_local_var_id (cognitive 30) src/hyperlight_component_util/src/rtypes.rs:174
- hyperlight_component_util::hl::emit_hl_unmarshal_value (cognitive 25) src/hyperlight_component_util/src/hl.rs:189
- hyperlight_component_util::hl::emit_hl_marshal_value (cognitive 25) src/hyperlight_component_util/src/hl.rs:524
- hyperlight_component_util::rtypes::emit_value_toplevel (cognitive 24) src/hyperlight_component_util/src/rtypes.rs:407
- hyperlight_component_util::rtypes::emit_resource_ref (cognitive 21) src/hyperlight_component_util/src/rtypes.rs:78
- hyperlight_component_util::rtypes::emit_extern_decl (cognitive 18) src/hyperlight_component_util/src/rtypes.rs:679
- MethodTooLong: FunctionCall.encode src/hyperlight_common/src/flatbuffer_wrappers/function_call.rs:66
- MethodTooLong: MshvVm.run_vcpu src/hyperlight_host/src/hypervisor/virtual_machine/mshv/x86_64.rs:255
- MethodTooLong: EventsBatchEncoderGeneric.encode src/hyperlight_common/src/flatbuffer_wrappers/guest_trace_data.rs:357
- MethodTooLong: MshvVm.set_batched_registers src/hyperlight_host/src/hypervisor/virtual_machine/mshv/x86_64.rs:620
- MethodTooLong: WhpVm.run_vcpu src/hyperlight_host/src/hypervisor/virtual_machine/whp/x86_64.rs:495
- MethodTooLong: HyperlightVm.run src/hyperlight_host/src/hypervisor/hyperlight_vm/mod.rs:585
- Duplicated block (6 lines × 2) src/hyperlight_component_macro/src/lib.rs:57
- Duplicated block (6 lines × 2) src/hyperlight_component_util/src/rtypes.rs:354
- Duplicated block (6 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/kvm/aarch64.rs:112
- Duplicated block (6 lines × 2) src/hyperlight_testing/src/logger.rs:33
- Duplicated block (6 lines × 2) src/hyperlight_common/src/arch/aarch64/vmem.rs:44
- Duplicated block (6 lines × 2) src/hyperlight_host/src/sandbox/file_mapping.rs:224
- Hotspot: src/hyperlight_host/src/sandbox/snapshot/file/config.rs src/hyperlight_host/src/sandbox/snapshot/file/config.rs:412
- Hotspot: src/hyperlight_host/src/hypervisor/hyperlight_vm/mod.rs src/hyperlight_host/src/hypervisor/hyperlight_vm/mod.rs:585
- Hotspot: src/hyperlight_host/src/sandbox/snapshot/file/mod.rs src/hyperlight_host/src/sandbox/snapshot/file/mod.rs:749
- Hotspot: src/hyperlight_host/src/hypervisor/virtual_machine/whp/x86_64.rs src/hyperlight_host/src/hypervisor/virtual_machine/whp/x86_64.rs:495
- Hotspot: src/hyperlight_component_util/src/rtypes.rs src/hyperlight_component_util/src/rtypes.rs:78
- Duplicated block (16 lines × 2) src/hyperlight_host/src/hypervisor/gdb/x86_64_target.rs:175
- Duplicated block (16 lines × 2) src/hyperlight_host/src/hypervisor/regs/x86_64/special_regs.rs:392
- Duplicated block (16 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/whp/x86_64.rs:860
- Duplicated block (16 lines × 2) src/hyperlight_host/src/mem/shared_mem.rs:1284
- Duplicated block (16 lines × 2) src/hyperlight_common/src/arch/aarch64/vmem.rs:450
- Duplicated block (5 lines × 2) src/hyperlight_component_util/src/hl.rs:310
- Duplicated block (5 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/mshv/x86_64.rs:398
- Duplicated block (5 lines × 2) src/hyperlight_component_util/src/emit.rs:955
- Duplicated block (5 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/whp/aarch64.rs:886
- Duplicated block (5 lines × 2) src/hyperlight_component_util/src/hl.rs:548
- hyperlight_component_util::rtypes::emit_value (cyclomatic 25) src/hyperlight_component_util/src/rtypes.rs:317
- hyperlight_component_util::hl::emit_hl_unmarshal_value (cyclomatic 24) src/hyperlight_component_util/src/hl.rs:189
- hyperlight_component_util::hl::emit_hl_marshal_value (cyclomatic 24) src/hyperlight_component_util/src/hl.rs:524
- hyperlight_component_util::component::read_component_single_exported_type (cyclomatic 20) src/hyperlight_component_util/src/component.rs:70
- Duplicated block (13 lines × 2) src/hyperlight_component_util/src/hl.rs:642
- Duplicated block (13 lines × 2) src/hyperlight_guest_macro/src/lib.rs:81
- Duplicated block (13 lines × 2) src/hyperlight_host/src/mem/shared_mem.rs:1236
- Duplicated block (13 lines × 2) src/hyperlight_guest/src/arch/aarch64/paging.rs:108
- Duplicated block (12 lines × 2) src/hyperlight_component_util/src/hl.rs:376
- Duplicated block (12 lines × 2) src/hyperlight_host/src/func/host_functions.rs:31
- Duplicated block (12 lines × 2) src/hyperlight_host/src/hypervisor/regs/x86_64/debug_regs.rs:146
- Duplicated block (12 lines × 2) src/hyperlight_host/src/hypervisor/surrogate_process.rs:135
- Duplicated block (10 lines × 2) src/hyperlight_common/src/arch/aarch64/vmem.rs:490
- Duplicated block (10 lines × 2) src/hyperlight_common/src/virtq/ring.rs:614
- Duplicated block (10 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/kvm/aarch64.rs:122
- Duplicated block (10 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/mshv/x86_64.rs:842
- Duplicated block (9 lines × 2) src/hyperlight_ci/src/remote.rs:352
- Duplicated block (9 lines × 2) src/hyperlight_component_util/src/hl.rs:44
- Duplicated block (9 lines × 2) src/hyperlight_guest/src/transport/mem.rs:128
- Duplicated block (9 lines × 2) src/hyperlight_host/src/hypervisor/regs/x86_64/fpu.rs:260
- TooManyMethods: Ctx src/hyperlight_component_util/src/etypes.rs:430
- TooManyMethods: SandboxMemoryLayout src/hyperlight_host/src/mem/layout.rs:239
- TooManyMethods: HyperlightVm src/hyperlight_host/src/hypervisor/hyperlight_vm/mod.rs:358
- ClassTooLong: WhpVm src/hyperlight_host/src/hypervisor/virtual_machine/whp/x86_64.rs:237
- ClassTooLong: MshvVm src/hyperlight_host/src/hypervisor/virtual_machine/mshv/x86_64.rs:150
- ClassTooLong: SandboxMemoryManager src/hyperlight_host/src/mem/mgr.rs:147
- FunctionTooLong: hyperlight_component_util::hl::emit_hl_unmarshal_value src/hyperlight_component_util/src/hl.rs:189
- FunctionTooLong: hyperlight_component_util::hl::emit_hl_marshal_value src/hyperlight_component_util/src/hl.rs:524
- FunctionTooLong: hyperlight_component_util::rtypes::emit_value_toplevel src/hyperlight_component_util/src/rtypes.rs:407
- Duplicated block (8 lines × 2) src/hyperlight_common/src/virtq/ring.rs:774
- Duplicated block (8 lines × 2) src/hyperlight_component_util/src/elaborate.rs:529
- Duplicated block (8 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/whp/aarch64.rs:465
- MshvVm::run_vcpu (cognitive 52) src/hyperlight_host/src/hypervisor/virtual_machine/mshv/x86_64.rs:255
- MshvVm::handle_hw_io_out (cognitive 19) src/hyperlight_host/src/hypervisor/virtual_machine/mshv/x86_64.rs:951
- HyperlightVm::run (cognitive 39) src/hyperlight_host/src/hypervisor/hyperlight_vm/mod.rs:585
- HyperlightVm::handle_debug (cognitive 25) src/hyperlight_host/src/hypervisor/hyperlight_vm/x86_64.rs:378
- WhpVm::run_vcpu (cognitive 31) src/hyperlight_host/src/hypervisor/virtual_machine/whp/x86_64.rs:495
- WhpVm::run_vcpu (cognitive 22) src/hyperlight_host/src/hypervisor/virtual_machine/whp/aarch64.rs:566
- KvmVm::run_vcpu_hw_interrupts (cognitive 19) src/hyperlight_host/src/hypervisor/virtual_machine/kvm/x86_64.rs:245
- KvmVm::run_vcpu (cognitive 18) src/hyperlight_host/src/hypervisor/virtual_machine/kvm/aarch64.rs:133
- Duplicated block (21 lines × 2) src/hyperlight_host/src/hypervisor/regs/x86_64/special_regs.rs:106
- Duplicated block (21 lines × 2) src/hyperlight_host/src/hypervisor/regs/x86_64/standard_regs.rs:35
- Duplicated block (19 lines × 2) src/hyperlight_common/src/arch/aarch64/vmem.rs:181
- Duplicated block (19 lines × 2) src/trace_dump/main.rs:324
- Duplicated block (9 lines × 3) src/hyperlight_component_util/src/rtypes.rs:425
- Duplicated block (9 lines × 3) src/hyperlight_guest_macro/src/lib.rs:78
- Duplicated block (7–8 lines × 2) src/hyperlight_component_util/src/guest.rs:139
- Duplicated block (7–8 lines × 2) src/hyperlight_component_util/src/substitute.rs:218
- Off the main sequence: hyperlight-component-util
- Off the main sequence: hyperlight-guest-tracing
- Low cohesion: HvfVm (LCOM4 5) src/hyperlight_host/src/hypervisor/virtual_machine/hvf/mod.rs:701
- Low cohesion: Offset (LCOM4 4) src/hyperlight_host/src/mem/ptr_offset.rs:17
- HyperlightVm::run (cyclomatic 26) src/hyperlight_host/src/hypervisor/hyperlight_vm/mod.rs:585
- Ctx::subtype_value (cyclomatic 24) src/hyperlight_component_util/src/subtype.rs:50
- MshvVm::run_vcpu (cyclomatic 23) src/hyperlight_host/src/hypervisor/virtual_machine/mshv/x86_64.rs:255
- WhpVm::run_vcpu (cyclomatic 18) src/hyperlight_host/src/hypervisor/virtual_machine/whp/x86_64.rs:495
- hyperlight_common::virtq::ring::canonical::validate_canon_image (cyclomatic 16) src/hyperlight_common/src/virtq/ring/canonical.rs:163
- HackComment src/hyperlight_component_util/src/rtypes.rs:871
- hyperlight_common::virtq::ring::canonical::validate_canon_image (cognitive 30) src/hyperlight_common/src/virtq/ring/canonical.rs:163
- HvfCpu::run (cognitive 27) src/hyperlight_host/src/hypervisor/virtual_machine/hvf/mod.rs:610
- BindgenInputParams::parse (cognitive 19) src/hyperlight_component_macro/src/lib.rs:145
- EventsBatchEncoderGeneric::encode (cognitive 17) src/hyperlight_common/src/flatbuffer_wrappers/guest_trace_data.rs:357
- GuestEvent::try_from (cognitive 16) src/hyperlight_common/src/flatbuffer_wrappers/guest_trace_data.rs:174
- SurrogateProcess::map (cognitive 16) src/hyperlight_host/src/hypervisor/surrogate_process.rs:62
- trace_dump::read_file (cognitive 16) src/trace_dump/main.rs:532
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change coupling: elf.rs ↔ mgr.rs src/hyperlight_host/src/mem/elf.rs:1
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/hyperlight_host/src/hypervisor/gdb/x86_64_target.rs:337
- Duplicated block (23–24 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/mshv/x86_64.rs:854
- Duplicated block (10–23 lines × 2) src/hyperlight_component_util/src/hl.rs:317
- Duplicated block (18–21 lines × 2) src/hyperlight_guest_bin/src/arch/aarch64/exception/handle.rs:48
- Duplicated block (20–21 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/mshv/x86_64.rs:879
- Duplicated block (19–20 lines × 3) src/hyperlight_common/src/flatbuffer_wrappers/guest_trace_data.rs:382
- Duplicated block (18–19 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/whp/aarch64.rs:547
- Duplicated block (11–17 lines × 3) src/hyperlight_host/src/hypervisor/regs/x86_64/debug_regs.rs:174
- Duplicated block (16 lines × 4) src/hyperlight_host/src/hypervisor/gdb/x86_64_target.rs:342
- Duplicated block (11–12 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/kvm/aarch64.rs:250
- Duplicated block (11 lines × 2) src/hyperlight_component_util/src/guest.rs:33
- Duplicated block (10–11 lines × 2) src/hyperlight_host/src/hypervisor/virtual_machine/whp/aarch64.rs:488
- Duplicated block (8–10 lines × 3) src/hyperlight_common/src/flatbuffer_wrappers/guest_trace_data.rs:192
- Duplicated block (9–10 lines × 2) src/hyperlight_common/src/virtq/consumer.rs:81
- Duplicated block (7–10 lines × 2) src/hyperlight_host/src/hypervisor/hyperlight_vm/x86_64.rs:767
- Duplicated block (8–9 lines × 2) src/hyperlight_common/src/arch/aarch64/vmem.rs:280
- Unstable project hyperlight-guest-bin
- Coverage collected but not gated
Minor — 69 finding(s)
- Interpolated log message defeats structured logging src/hyperlight_host/src/lib.rs:120
- Interpolated log message defeats structured logging src/hyperlight_host/src/lib.rs:124
- Interpolated log message defeats structured logging src/hyperlight_host/src/lib.rs:128
- Interpolated log message defeats structured logging src/hyperlight_host/src/lib.rs:134
- Interpolated log message defeats structured logging src/hyperlight_host/src/lib.rs:169
- Interpolated log message defeats structured logging src/hyperlight_host/src/lib.rs:173
- Interpolated log message defeats structured logging src/hyperlight_host/src/lib.rs:182
- Interpolated log message defeats structured logging src/hyperlight_host/src/lib.rs:188
- Interpolated log message defeats structured logging src/hyperlight_host/src/mem/mgr.rs:1030
- Interpolated log message defeats structured logging src/hyperlight_host/src/mem/shared_mem.rs:318
- Interpolated log message defeats structured logging src/hyperlight_host/src/mem/shared_mem.rs:348
- Interpolated log message defeats structured logging src/hyperlight_host/src/mem/shared_mem.rs:370
- Interpolated log message defeats structured logging src/hyperlight_host/src/mem/shared_mem.rs:503
- Interpolated log message defeats structured logging src/hyperlight_host/src/hypervisor/crashdump.rs:275
- Interpolated log message defeats structured logging src/hyperlight_host/src/hypervisor/crashdump.rs:311
- Interpolated log message defeats structured logging src/hyperlight_host/src/hypervisor/mod.rs:361
- Interpolated log message defeats structured logging src/hyperlight_host/src/hypervisor/mod.rs:374
- Interpolated log message defeats structured logging src/hyperlight_host/src/hypervisor/mod.rs:396
- Interpolated log message defeats structured logging src/hyperlight_host/src/hypervisor/surrogate_process.rs:72
- Interpolated log message defeats structured logging src/hyperlight_host/src/hypervisor/surrogate_process.rs:179
- Interpolated log message defeats structured logging src/hyperlight_host/src/hypervisor/surrogate_process.rs:191
- Interpolated log message defeats structured logging src/hyperlight_host/src/hypervisor/surrogate_process.rs:213
- Interpolated log message defeats structured logging src/hyperlight_host/src/hypervisor/surrogate_process.rs:243
- Interpolated log message defeats structured logging src/hyperlight_host/src/hypervisor/surrogate_process.rs:250
- Interpolated log message defeats structured logging src/hyperlight_host/src/hypervisor/surrogate_process_manager.rs:117
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned file src/hyperlight_guest_tracing/src/state.rs:1
- Orphaned file src/hyperlight_common/src/log_level.rs:1
- Orphaned file src/hyperlight_host/src/hypervisor/gdb/event_loop.rs:1
- Orphaned file fuzz/fuzz_targets/guest_estimate_trace_event.rs:1
- Subsumed condition operand src/hyperlight_host/src/sandbox/snapshot/file_tests.rs:801
- Subsumed condition operand src/hyperlight_host/src/sandbox/snapshot/file_tests.rs:2273
- Subsumed condition operand src/hyperlight_host/src/sandbox/snapshot/file_tests.rs:2414
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- README/code drift docs/README.md:45
- Logging is not universal
- No release approval gate
Minor — 7 finding(s)
- Outdated: arbitrary
- Outdated: cc
- Outdated: smallvec
- Outdated: tokio
- Outdated: uuid
- Outdated: wat
- Off the main sequence: hyperlight-common
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-5fd052caf136478481363e4042c5376a/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-5fd052caf136478481363e4042c5376a/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 --exclude src/hyperlight_common/src/flatbuffers --exclude src/tests/rust_guests/callbackguest . | 53 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 8 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |