Executive summary
simplerr/rust-renderer falls short of our standard for a preview release because its Testing dimensions are rated Critical, and the project has no automated tests. It scores 49.1 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 26.9, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 8.0 points. Adding automated tests would lift Production Readiness itself, worth about 21.3 points. Raising Production Readiness to 62 would lift the score to about 64.2.
The project has no automated tests, so a change can break it without warning. Adding automated tests would close this risk.
The product code is 7,896 lines, about €7,300 to rebuild.
If Production Readiness rose from 26.9 to 62, the lowest score rated Strong, the score would rise from 49.1 to about 64.2.
Rebuild cost: about €7,300 · Estimate
| Cost to rebuild | €2,400 to €12,000, for 40 to 128 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 49. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 7,896 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 utopian.device | 2 utopian.directory_watcher | 3 utopian.fps_timer | 4 utopian.input | 5 utopian.render_utils | 6 prototype.ui | 7 utopian.camera | 8 utopian.image | 9 utopian.shader | 10 utopian.buffer | 11 utopian.synch | 12 utopian.texture | 13 utopian.vulkan_base | 14 utopian.descriptor_set | 15 utopian.pipeline | 16 utopian.primitive | 17 utopian.profiler_backend | 18 utopian.bindless | 19 utopian.gltf_loader | 20 utopian.pass | 21 utopian.raytracing | 22 utopian.model_loader | 23 utopian.renderer | 24 prototype.scenes | 25 utopian.graph | 26 prototype.main | 27 utopian.renderers | 28 utopian.renderers.atmosphere | 29 utopian.renderers.deferred | 30 utopian.renderers.forward | 31 utopian.renderers.gbuffer | 32 utopian.renderers.ibl | 33 utopian.renderers.marching_cubes | 34 utopian.renderers.present | 35 utopian.renderers.rt_reflections | 36 utopian.renderers.rt_shadows | 37 utopian.renderers.shadertoy | 38 utopian.renderers.shadow | 39 utopian.renderers.ssao |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 utopian.device | |||||||||||||||||||||||||||||||||||||||
| 2 utopian.directory_watcher | |||||||||||||||||||||||||||||||||||||||
| 3 utopian.fps_timer | |||||||||||||||||||||||||||||||||||||||
| 4 utopian.input | |||||||||||||||||||||||||||||||||||||||
| 5 utopian.render_utils | |||||||||||||||||||||||||||||||||||||||
| 6 prototype.ui | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 utopian.camera | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 utopian.image | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 utopian.shader | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 utopian.buffer | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 11 utopian.synch | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 utopian.texture | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 13 utopian.vulkan_base | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 14 utopian.descriptor_set | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 15 utopian.pipeline | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 utopian.primitive | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 utopian.profiler_backend | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 utopian.bindless | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 utopian.gltf_loader | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 utopian.pass | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 21 utopian.raytracing | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 22 utopian.model_loader | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 utopian.renderer | 1 | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 24 prototype.scenes | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 utopian.graph | 2 | 2 | 2 | 1 | 1 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||
| 26 prototype.main | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||
| 27 utopian.renderers | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 28 utopian.renderers.atmosphere | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 utopian.renderers.deferred | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 utopian.renderers.forward | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 utopian.renderers.gbuffer | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 utopian.renderers.ibl | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 utopian.renderers.marching_cubes | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 utopian.renderers.present | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 utopian.renderers.rt_reflections | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 utopian.renderers.rt_shadows | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 utopian.renderers.shadertoy | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 utopian.renderers.shadow | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 utopian.renderers.ssao | 1 | 1 |
6→1 prototype.ui uses utopian.device✕
- Connections
- 1 pair of types, where a type in prototype.ui uses a type in utopian.device.
- The types involved
prototype.ui.Ui→utopian.device.Device
- Direction
- prototype.ui uses utopian.device, so a change to utopian.device can break prototype.ui, while a change to prototype.ui can't break utopian.device.
- Position
- Below the diagonal: prototype.ui uses a module listed above it, which is the healthy direction.
7→4 utopian.camera uses utopian.input✕
- Connections
- 1 pair of types, where a type in utopian.camera uses a type in utopian.input.
- The types involved
utopian.camera.Camera→utopian.input.Input
- Direction
- utopian.camera uses utopian.input, so a change to utopian.input can break utopian.camera, while a change to utopian.camera can't break utopian.input.
- Position
- Below the diagonal: utopian.camera uses a module listed above it, which is the healthy direction.
8→1 utopian.image uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.image uses a type in utopian.device.
- The types involved
utopian.image.Image→utopian.device.Device
- Direction
- utopian.image uses utopian.device, so a change to utopian.device can break utopian.image, while a change to utopian.image can't break utopian.device.
- Position
- Below the diagonal: utopian.image uses a module listed above it, which is the healthy direction.
9→1 utopian.shader uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.shader uses a type in utopian.device.
- The types involved
utopian.shader.shader$module→utopian.device.Device
- Direction
- utopian.shader uses utopian.device, so a change to utopian.device can break utopian.shader, while a change to utopian.shader can't break utopian.device.
- Position
- Below the diagonal: utopian.shader uses a module listed above it, which is the healthy direction.
10→1 utopian.buffer uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.buffer uses a type in utopian.device.
- The types involved
utopian.buffer.Buffer→utopian.device.Device
- Direction
- utopian.buffer uses utopian.device, so a change to utopian.device can break utopian.buffer, while a change to utopian.buffer can't break utopian.device.
- Position
- Below the diagonal: utopian.buffer uses a module listed above it, which is the healthy direction.
10→8 utopian.buffer uses utopian.image✕
- Connections
- 1 pair of types, where a type in utopian.buffer uses a type in utopian.image.
- The types involved
utopian.buffer.Buffer→utopian.image.Image
- Direction
- utopian.buffer uses utopian.image, so a change to utopian.image can break utopian.buffer, while a change to utopian.buffer can't break utopian.image.
- Position
- Below the diagonal: utopian.buffer uses a module listed above it, which is the healthy direction.
11→1 utopian.synch uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.synch uses a type in utopian.device.
- The types involved
utopian.synch.synch$module→utopian.device.Device
- Direction
- utopian.synch uses utopian.device, so a change to utopian.device can break utopian.synch, while a change to utopian.synch can't break utopian.device.
- Position
- Below the diagonal: utopian.synch uses a module listed above it, which is the healthy direction.
11→8 utopian.synch uses utopian.image✕
- Connections
- 1 pair of types, where a type in utopian.synch uses a type in utopian.image.
- The types involved
utopian.synch.synch$module→utopian.image.Image
- Direction
- utopian.synch uses utopian.image, so a change to utopian.image can break utopian.synch, while a change to utopian.synch can't break utopian.image.
- Position
- Below the diagonal: utopian.synch uses a module listed above it, which is the healthy direction.
12→1 utopian.texture uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.texture uses a type in utopian.device.
- The types involved
utopian.texture.Texture→utopian.device.Device
- Direction
- utopian.texture uses utopian.device, so a change to utopian.device can break utopian.texture, while a change to utopian.texture can't break utopian.device.
- Position
- Below the diagonal: utopian.texture uses a module listed above it, which is the healthy direction.
12→8 utopian.texture uses utopian.image✕
- Connections
- 2 pairs of types, where a type in utopian.texture uses a type in utopian.image.
- The types involved
utopian.texture.Texture→utopian.image.Imageutopian.texture.Texture→utopian.image.ImageDesc
- Direction
- utopian.texture uses utopian.image, so a change to utopian.image can break utopian.texture, while a change to utopian.texture can't break utopian.image.
- Position
- Below the diagonal: utopian.texture uses a module listed above it, which is the healthy direction.
13→1 utopian.vulkan_base uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.vulkan_base uses a type in utopian.device.
- The types involved
utopian.vulkan_base.VulkanBase→utopian.device.Device
- Direction
- utopian.vulkan_base uses utopian.device, so a change to utopian.device can break utopian.vulkan_base, while a change to utopian.vulkan_base can't break utopian.device.
- Position
- Below the diagonal: utopian.vulkan_base uses a module listed above it, which is the healthy direction.
13→8 utopian.vulkan_base uses utopian.image✕
- Connections
- 1 pair of types, where a type in utopian.vulkan_base uses a type in utopian.image.
- The types involved
utopian.vulkan_base.VulkanBase→utopian.image.Image
- Direction
- utopian.vulkan_base uses utopian.image, so a change to utopian.image can break utopian.vulkan_base, while a change to utopian.vulkan_base can't break utopian.image.
- Position
- Below the diagonal: utopian.vulkan_base uses a module listed above it, which is the healthy direction.
14→1 utopian.descriptor_set uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.descriptor_set uses a type in utopian.device.
- The types involved
utopian.descriptor_set.DescriptorSet→utopian.device.Device
- Direction
- utopian.descriptor_set uses utopian.device, so a change to utopian.device can break utopian.descriptor_set, while a change to utopian.descriptor_set can't break utopian.device.
- Position
- Below the diagonal: utopian.descriptor_set uses a module listed above it, which is the healthy direction.
14→8 utopian.descriptor_set uses utopian.image✕
- Connections
- 1 pair of types, where a type in utopian.descriptor_set uses a type in utopian.image.
- The types involved
utopian.descriptor_set.DescriptorSet→utopian.image.Image
- Direction
- utopian.descriptor_set uses utopian.image, so a change to utopian.image can break utopian.descriptor_set, while a change to utopian.descriptor_set can't break utopian.image.
- Position
- Below the diagonal: utopian.descriptor_set uses a module listed above it, which is the healthy direction.
14→10 utopian.descriptor_set uses utopian.buffer✕
- Connections
- 1 pair of types, where a type in utopian.descriptor_set uses a type in utopian.buffer.
- The types involved
utopian.descriptor_set.DescriptorSet→utopian.buffer.Buffer
- Direction
- utopian.descriptor_set uses utopian.buffer, so a change to utopian.buffer can break utopian.descriptor_set, while a change to utopian.descriptor_set can't break utopian.buffer.
- Position
- Below the diagonal: utopian.descriptor_set uses a module listed above it, which is the healthy direction.
14→12 utopian.descriptor_set uses utopian.texture✕
- Connections
- 1 pair of types, where a type in utopian.descriptor_set uses a type in utopian.texture.
- The types involved
utopian.descriptor_set.DescriptorSet→utopian.texture.Texture
- Direction
- utopian.descriptor_set uses utopian.texture, so a change to utopian.texture can break utopian.descriptor_set, while a change to utopian.descriptor_set can't break utopian.texture.
- Position
- Below the diagonal: utopian.descriptor_set uses a module listed above it, which is the healthy direction.
15→1 utopian.pipeline uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.pipeline uses a type in utopian.device.
- The types involved
utopian.pipeline.Pipeline→utopian.device.Device
- Direction
- utopian.pipeline uses utopian.device, so a change to utopian.device can break utopian.pipeline, while a change to utopian.pipeline can't break utopian.device.
- Position
- Below the diagonal: utopian.pipeline uses a module listed above it, which is the healthy direction.
15→9 utopian.pipeline uses utopian.shader✕
- Connections
- 1 pair of types, where a type in utopian.pipeline uses a type in utopian.shader.
- The types involved
utopian.pipeline.Pipeline→utopian.shader.Reflection
- Direction
- utopian.pipeline uses utopian.shader, so a change to utopian.shader can break utopian.pipeline, while a change to utopian.pipeline can't break utopian.shader.
- Position
- Below the diagonal: utopian.pipeline uses a module listed above it, which is the healthy direction.
15→10 utopian.pipeline uses utopian.buffer✕
- Connections
- 1 pair of types, where a type in utopian.pipeline uses a type in utopian.buffer.
- The types involved
utopian.pipeline.RayTracingSbt→utopian.buffer.Buffer
- Direction
- utopian.pipeline uses utopian.buffer, so a change to utopian.buffer can break utopian.pipeline, while a change to utopian.pipeline can't break utopian.buffer.
- Position
- Below the diagonal: utopian.pipeline uses a module listed above it, which is the healthy direction.
16→1 utopian.primitive uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.primitive uses a type in utopian.device.
- The types involved
utopian.primitive.Primitive→utopian.device.Device
- Direction
- utopian.primitive uses utopian.device, so a change to utopian.device can break utopian.primitive, while a change to utopian.primitive can't break utopian.device.
- Position
- Below the diagonal: utopian.primitive uses a module listed above it, which is the healthy direction.
16→10 utopian.primitive uses utopian.buffer✕
- Connections
- 1 pair of types, where a type in utopian.primitive uses a type in utopian.buffer.
- The types involved
utopian.primitive.Primitive→utopian.buffer.Buffer
- Direction
- utopian.primitive uses utopian.buffer, so a change to utopian.buffer can break utopian.primitive, while a change to utopian.primitive can't break utopian.buffer.
- Position
- Below the diagonal: utopian.primitive uses a module listed above it, which is the healthy direction.
17→1 utopian.profiler_backend uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.profiler_backend uses a type in utopian.device.
- The types involved
utopian.profiler_backend.ProfilerBackend→utopian.device.Device
- Direction
- utopian.profiler_backend uses utopian.device, so a change to utopian.device can break utopian.profiler_backend, while a change to utopian.profiler_backend can't break utopian.device.
- Position
- Below the diagonal: utopian.profiler_backend uses a module listed above it, which is the healthy direction.
17→10 utopian.profiler_backend uses utopian.buffer✕
- Connections
- 2 pairs of types, where a type in utopian.profiler_backend uses a type in utopian.buffer.
- The types involved
utopian.profiler_backend.ProfilerBackend→utopian.buffer.Bufferutopian.profiler_backend.ProfilerBuffer→utopian.buffer.Buffer
- Direction
- utopian.profiler_backend uses utopian.buffer, so a change to utopian.buffer can break utopian.profiler_backend, while a change to utopian.profiler_backend can't break utopian.buffer.
- Position
- Below the diagonal: utopian.profiler_backend uses a module listed above it, which is the healthy direction.
18→1 utopian.bindless uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.bindless uses a type in utopian.device.
- The types involved
utopian.bindless.bindless$module→utopian.device.Device
- Direction
- utopian.bindless uses utopian.device, so a change to utopian.device can break utopian.bindless, while a change to utopian.bindless can't break utopian.device.
- Position
- Below the diagonal: utopian.bindless uses a module listed above it, which is the healthy direction.
18→14 utopian.bindless uses utopian.descriptor_set✕
- Connections
- 1 pair of types, where a type in utopian.bindless uses a type in utopian.descriptor_set.
- The types involved
utopian.bindless.bindless$module→utopian.descriptor_set.DescriptorSet
- Direction
- utopian.bindless uses utopian.descriptor_set, so a change to utopian.descriptor_set can break utopian.bindless, while a change to utopian.bindless can't break utopian.descriptor_set.
- Position
- Below the diagonal: utopian.bindless uses a module listed above it, which is the healthy direction.
19→1 utopian.gltf_loader uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.gltf_loader uses a type in utopian.device.
- The types involved
utopian.gltf_loader.gltf_loader$module→utopian.device.Device
- Direction
- utopian.gltf_loader uses utopian.device, so a change to utopian.device can break utopian.gltf_loader, while a change to utopian.gltf_loader can't break utopian.device.
- Position
- Below the diagonal: utopian.gltf_loader uses a module listed above it, which is the healthy direction.
19→12 utopian.gltf_loader uses utopian.texture✕
- Connections
- 1 pair of types, where a type in utopian.gltf_loader uses a type in utopian.texture.
- The types involved
utopian.gltf_loader.Model→utopian.texture.Texture
- Direction
- utopian.gltf_loader uses utopian.texture, so a change to utopian.texture can break utopian.gltf_loader, while a change to utopian.gltf_loader can't break utopian.texture.
- Position
- Below the diagonal: utopian.gltf_loader uses a module listed above it, which is the healthy direction.
19→16 utopian.gltf_loader uses utopian.primitive✕
- Connections
- 1 pair of types, where a type in utopian.gltf_loader uses a type in utopian.primitive.
- The types involved
utopian.gltf_loader.Mesh→utopian.primitive.Primitive
- Direction
- utopian.gltf_loader uses utopian.primitive, so a change to utopian.primitive can break utopian.gltf_loader, while a change to utopian.gltf_loader can't break utopian.primitive.
- Position
- Below the diagonal: utopian.gltf_loader uses a module listed above it, which is the healthy direction.
20→1 utopian.pass uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.pass uses a type in utopian.device.
- The types involved
utopian.pass.RenderPass→utopian.device.Device
- Direction
- utopian.pass uses utopian.device, so a change to utopian.device can break utopian.pass, while a change to utopian.pass can't break utopian.device.
- Position
- Below the diagonal: utopian.pass uses a module listed above it, which is the healthy direction.
20→14 utopian.pass uses utopian.descriptor_set✕
- Connections
- 1 pair of types, where a type in utopian.pass uses a type in utopian.descriptor_set.
- The types involved
utopian.pass.RenderPass→utopian.descriptor_set.DescriptorSet
- Direction
- utopian.pass uses utopian.descriptor_set, so a change to utopian.descriptor_set can break utopian.pass, while a change to utopian.pass can't break utopian.descriptor_set.
- Position
- Below the diagonal: utopian.pass uses a module listed above it, which is the healthy direction.
20→25 utopian.pass uses utopian.graph part of a loop✕
- Connections
- 4 pairs of types, where a type in utopian.pass uses a type in utopian.graph.
- The types involved
utopian.pass.RenderPass→utopian.graph.Attachmentutopian.pass.RenderPass→utopian.graph.DepthAttachmentutopian.pass.RenderPass→utopian.graph.Resourceutopian.pass.RenderPass→utopian.graph.TextureCopy
- Direction
- utopian.pass uses utopian.graph, so a change to utopian.graph can break utopian.pass, while a change to utopian.pass can't break utopian.graph.
- 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→1 utopian.raytracing uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.raytracing uses a type in utopian.device.
- The types involved
utopian.raytracing.Raytracing→utopian.device.Device
- Direction
- utopian.raytracing uses utopian.device, so a change to utopian.device can break utopian.raytracing, while a change to utopian.raytracing can't break utopian.device.
- Position
- Below the diagonal: utopian.raytracing uses a module listed above it, which is the healthy direction.
21→8 utopian.raytracing uses utopian.image✕
- Connections
- 1 pair of types, where a type in utopian.raytracing uses a type in utopian.image.
- The types involved
utopian.raytracing.Raytracing→utopian.image.Image
- Direction
- utopian.raytracing uses utopian.image, so a change to utopian.image can break utopian.raytracing, while a change to utopian.raytracing can't break utopian.image.
- Position
- Below the diagonal: utopian.raytracing uses a module listed above it, which is the healthy direction.
21→10 utopian.raytracing uses utopian.buffer✕
- Connections
- 1 pair of types, where a type in utopian.raytracing uses a type in utopian.buffer.
- The types involved
utopian.raytracing.Tlas→utopian.buffer.Buffer
- Direction
- utopian.raytracing uses utopian.buffer, so a change to utopian.buffer can break utopian.raytracing, while a change to utopian.raytracing can't break utopian.buffer.
- Position
- Below the diagonal: utopian.raytracing uses a module listed above it, which is the healthy direction.
21→14 utopian.raytracing uses utopian.descriptor_set✕
- Connections
- 1 pair of types, where a type in utopian.raytracing uses a type in utopian.descriptor_set.
- The types involved
utopian.raytracing.Raytracing→utopian.descriptor_set.DescriptorSet
- Direction
- utopian.raytracing uses utopian.descriptor_set, so a change to utopian.descriptor_set can break utopian.raytracing, while a change to utopian.raytracing can't break utopian.descriptor_set.
- Position
- Below the diagonal: utopian.raytracing uses a module listed above it, which is the healthy direction.
21→15 utopian.raytracing uses utopian.pipeline✕
- Connections
- 1 pair of types, where a type in utopian.raytracing uses a type in utopian.pipeline.
- The types involved
utopian.raytracing.Raytracing→utopian.pipeline.Pipeline
- Direction
- utopian.raytracing uses utopian.pipeline, so a change to utopian.pipeline can break utopian.raytracing, while a change to utopian.raytracing can't break utopian.pipeline.
- Position
- Below the diagonal: utopian.raytracing uses a module listed above it, which is the healthy direction.
21→16 utopian.raytracing uses utopian.primitive✕
- Connections
- 1 pair of types, where a type in utopian.raytracing uses a type in utopian.primitive.
- The types involved
utopian.raytracing.Raytracing→utopian.primitive.Primitive
- Direction
- utopian.raytracing uses utopian.primitive, so a change to utopian.primitive can break utopian.raytracing, while a change to utopian.raytracing can't break utopian.primitive.
- Position
- Below the diagonal: utopian.raytracing uses a module listed above it, which is the healthy direction.
22→1 utopian.model_loader uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.model_loader uses a type in utopian.device.
- The types involved
utopian.model_loader.ModelLoader→utopian.device.Device
- Direction
- utopian.model_loader uses utopian.device, so a change to utopian.device can break utopian.model_loader, while a change to utopian.model_loader can't break utopian.device.
- Position
- Below the diagonal: utopian.model_loader uses a module listed above it, which is the healthy direction.
22→16 utopian.model_loader uses utopian.primitive✕
- Connections
- 1 pair of types, where a type in utopian.model_loader uses a type in utopian.primitive.
- The types involved
utopian.model_loader.model_loader$module→utopian.primitive.Vertex
- Direction
- utopian.model_loader uses utopian.primitive, so a change to utopian.primitive can break utopian.model_loader, while a change to utopian.model_loader can't break utopian.primitive.
- Position
- Below the diagonal: utopian.model_loader uses a module listed above it, which is the healthy direction.
22→19 utopian.model_loader uses utopian.gltf_loader✕
- Connections
- 1 pair of types, where a type in utopian.model_loader uses a type in utopian.gltf_loader.
- The types involved
utopian.model_loader.ModelLoader→utopian.gltf_loader.Model
- Direction
- utopian.model_loader uses utopian.gltf_loader, so a change to utopian.gltf_loader can break utopian.model_loader, while a change to utopian.model_loader can't break utopian.gltf_loader.
- Position
- Below the diagonal: utopian.model_loader uses a module listed above it, which is the healthy direction.
23→1 utopian.renderer uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderer uses a type in utopian.device.
- The types involved
utopian.renderer.Renderer→utopian.device.Device
- Direction
- utopian.renderer uses utopian.device, so a change to utopian.device can break utopian.renderer, while a change to utopian.renderer can't break utopian.device.
- Position
- Below the diagonal: utopian.renderer uses a module listed above it, which is the healthy direction.
23→10 utopian.renderer uses utopian.buffer✕
- Connections
- 1 pair of types, where a type in utopian.renderer uses a type in utopian.buffer.
- The types involved
utopian.renderer.Renderer→utopian.buffer.Buffer
- Direction
- utopian.renderer uses utopian.buffer, so a change to utopian.buffer can break utopian.renderer, while a change to utopian.renderer can't break utopian.buffer.
- Position
- Below the diagonal: utopian.renderer uses a module listed above it, which is the healthy direction.
23→12 utopian.renderer uses utopian.texture✕
- Connections
- 1 pair of types, where a type in utopian.renderer uses a type in utopian.texture.
- The types involved
utopian.renderer.Renderer→utopian.texture.Texture
- Direction
- utopian.renderer uses utopian.texture, so a change to utopian.texture can break utopian.renderer, while a change to utopian.renderer can't break utopian.texture.
- Position
- Below the diagonal: utopian.renderer uses a module listed above it, which is the healthy direction.
23→14 utopian.renderer uses utopian.descriptor_set✕
- Connections
- 1 pair of types, where a type in utopian.renderer uses a type in utopian.descriptor_set.
- The types involved
utopian.renderer.Renderer→utopian.descriptor_set.DescriptorSet
- Direction
- utopian.renderer uses utopian.descriptor_set, so a change to utopian.descriptor_set can break utopian.renderer, while a change to utopian.renderer can't break utopian.descriptor_set.
- Position
- Below the diagonal: utopian.renderer uses a module listed above it, which is the healthy direction.
23→19 utopian.renderer uses utopian.gltf_loader✕
- Connections
- 2 pairs of types, where a type in utopian.renderer uses a type in utopian.gltf_loader.
- The types involved
utopian.renderer.ModelInstance→utopian.gltf_loader.Modelutopian.renderer.Renderer→utopian.gltf_loader.Model
- Direction
- utopian.renderer uses utopian.gltf_loader, so a change to utopian.gltf_loader can break utopian.renderer, while a change to utopian.renderer can't break utopian.gltf_loader.
- Position
- Below the diagonal: utopian.renderer uses a module listed above it, which is the healthy direction.
23→21 utopian.renderer uses utopian.raytracing✕
- Connections
- 1 pair of types, where a type in utopian.renderer uses a type in utopian.raytracing.
- The types involved
utopian.renderer.Renderer→utopian.raytracing.Raytracing
- Direction
- utopian.renderer uses utopian.raytracing, so a change to utopian.raytracing can break utopian.renderer, while a change to utopian.renderer can't break utopian.raytracing.
- Position
- Below the diagonal: utopian.renderer uses a module listed above it, which is the healthy direction.
24→1 prototype.scenes uses utopian.device✕
- Connections
- 1 pair of types, where a type in prototype.scenes uses a type in utopian.device.
- The types involved
prototype.scenes.scenes$module→utopian.device.Device
- Direction
- prototype.scenes uses utopian.device, so a change to utopian.device can break prototype.scenes, while a change to prototype.scenes can't break utopian.device.
- Position
- Below the diagonal: prototype.scenes uses a module listed above it, which is the healthy direction.
24→7 prototype.scenes uses utopian.camera✕
- Connections
- 1 pair of types, where a type in prototype.scenes uses a type in utopian.camera.
- The types involved
prototype.scenes.scenes$module→utopian.camera.Camera
- Direction
- prototype.scenes uses utopian.camera, so a change to utopian.camera can break prototype.scenes, while a change to prototype.scenes can't break utopian.camera.
- Position
- Below the diagonal: prototype.scenes uses a module listed above it, which is the healthy direction.
24→23 prototype.scenes uses utopian.renderer✕
- Connections
- 1 pair of types, where a type in prototype.scenes uses a type in utopian.renderer.
- The types involved
prototype.scenes.scenes$module→utopian.renderer.Renderer
- Direction
- prototype.scenes uses utopian.renderer, so a change to utopian.renderer can break prototype.scenes, while a change to prototype.scenes can't break utopian.renderer.
- Position
- Below the diagonal: prototype.scenes uses a module listed above it, which is the healthy direction.
25→1 utopian.graph uses utopian.device✕
- Connections
- 2 pairs of types, where a type in utopian.graph uses a type in utopian.device.
- The types involved
utopian.graph.Graph→utopian.device.Deviceutopian.graph.PassBuilder→utopian.device.Device
- Direction
- utopian.graph uses utopian.device, so a change to utopian.device can break utopian.graph, while a change to utopian.graph can't break utopian.device.
- Position
- Below the diagonal: utopian.graph uses a module listed above it, which is the healthy direction.
25→8 utopian.graph uses utopian.image✕
- Connections
- 2 pairs of types, where a type in utopian.graph uses a type in utopian.image.
- The types involved
utopian.graph.Graph→utopian.image.ImageDescutopian.graph.PassBuilder→utopian.image.Image
- Direction
- utopian.graph uses utopian.image, so a change to utopian.image can break utopian.graph, while a change to utopian.graph can't break utopian.image.
- Position
- Below the diagonal: utopian.graph uses a module listed above it, which is the healthy direction.
25→10 utopian.graph uses utopian.buffer✕
- Connections
- 2 pairs of types, where a type in utopian.graph uses a type in utopian.buffer.
- The types involved
utopian.graph.Graph→utopian.buffer.Bufferutopian.graph.GraphBuffer→utopian.buffer.Buffer
- Direction
- utopian.graph uses utopian.buffer, so a change to utopian.buffer can break utopian.graph, while a change to utopian.graph can't break utopian.buffer.
- Position
- Below the diagonal: utopian.graph uses a module listed above it, which is the healthy direction.
25→12 utopian.graph uses utopian.texture✕
- Connections
- 1 pair of types, where a type in utopian.graph uses a type in utopian.texture.
- The types involved
utopian.graph.GraphTexture→utopian.texture.Texture
- Direction
- utopian.graph uses utopian.texture, so a change to utopian.texture can break utopian.graph, while a change to utopian.graph can't break utopian.texture.
- Position
- Below the diagonal: utopian.graph uses a module listed above it, which is the healthy direction.
25→14 utopian.graph uses utopian.descriptor_set✕
- Connections
- 1 pair of types, where a type in utopian.graph uses a type in utopian.descriptor_set.
- The types involved
utopian.graph.Graph→utopian.descriptor_set.DescriptorSet
- Direction
- utopian.graph uses utopian.descriptor_set, so a change to utopian.descriptor_set can break utopian.graph, while a change to utopian.graph can't break utopian.descriptor_set.
- Position
- Below the diagonal: utopian.graph uses a module listed above it, which is the healthy direction.
25→15 utopian.graph uses utopian.pipeline✕
- Connections
- 3 pairs of types, where a type in utopian.graph uses a type in utopian.pipeline.
- The types involved
utopian.graph.Graph→utopian.pipeline.PipelineDescutopian.graph.Graph→utopian.pipeline.PipelineDescBuilderutopian.graph.GraphResources→utopian.pipeline.Pipeline
- Direction
- utopian.graph uses utopian.pipeline, so a change to utopian.pipeline can break utopian.graph, while a change to utopian.graph can't break utopian.pipeline.
- Position
- Below the diagonal: utopian.graph uses a module listed above it, which is the healthy direction.
25→20 utopian.graph uses utopian.pass✕
- Connections
- 1 pair of types, where a type in utopian.graph uses a type in utopian.pass.
- The types involved
utopian.graph.Graph→utopian.pass.RenderPass
- Direction
- utopian.graph uses utopian.pass, so a change to utopian.pass can break utopian.graph, while a change to utopian.graph can't break utopian.pass.
- Position
- Below the diagonal: utopian.graph uses a module listed above it, which is the healthy direction.
25→23 utopian.graph uses utopian.renderer✕
- Connections
- 1 pair of types, where a type in utopian.graph uses a type in utopian.renderer.
- The types involved
utopian.graph.Graph→utopian.renderer.Renderer
- Direction
- utopian.graph uses utopian.renderer, so a change to utopian.renderer can break utopian.graph, while a change to utopian.graph can't break utopian.renderer.
- Position
- Below the diagonal: utopian.graph uses a module listed above it, which is the healthy direction.
26→1 prototype.main uses utopian.device✕
- Connections
- 1 pair of types, where a type in prototype.main uses a type in utopian.device.
- The types involved
prototype.main.Application→utopian.device.Device
- Direction
- prototype.main uses utopian.device, so a change to utopian.device can break prototype.main, while a change to prototype.main can't break utopian.device.
- Position
- Below the diagonal: prototype.main uses a module listed above it, which is the healthy direction.
26→2 prototype.main uses utopian.directory_watcher✕
- Connections
- 1 pair of types, where a type in prototype.main uses a type in utopian.directory_watcher.
- The types involved
prototype.main.Application→utopian.directory_watcher.DirectoryWatcher
- Direction
- prototype.main uses utopian.directory_watcher, so a change to utopian.directory_watcher can break prototype.main, while a change to prototype.main can't break utopian.directory_watcher.
- Position
- Below the diagonal: prototype.main uses a module listed above it, which is the healthy direction.
26→3 prototype.main uses utopian.fps_timer✕
- Connections
- 1 pair of types, where a type in prototype.main uses a type in utopian.fps_timer.
- The types involved
prototype.main.Application→utopian.fps_timer.FpsTimer
- Direction
- prototype.main uses utopian.fps_timer, so a change to utopian.fps_timer can break prototype.main, while a change to prototype.main can't break utopian.fps_timer.
- Position
- Below the diagonal: prototype.main uses a module listed above it, which is the healthy direction.
26→6 prototype.main uses prototype.ui✕
- Connections
- 1 pair of types, where a type in prototype.main uses a type in prototype.ui.
- The types involved
prototype.main.Application→prototype.ui.Ui
- Direction
- prototype.main uses prototype.ui, so a change to prototype.ui can break prototype.main, while a change to prototype.main can't break prototype.ui.
- Position
- Below the diagonal: prototype.main uses a module listed above it, which is the healthy direction.
26→7 prototype.main uses utopian.camera✕
- Connections
- 1 pair of types, where a type in prototype.main uses a type in utopian.camera.
- The types involved
prototype.main.Application→utopian.camera.Camera
- Direction
- prototype.main uses utopian.camera, so a change to utopian.camera can break prototype.main, while a change to prototype.main can't break utopian.camera.
- Position
- Below the diagonal: prototype.main uses a module listed above it, which is the healthy direction.
26→10 prototype.main uses utopian.buffer✕
- Connections
- 1 pair of types, where a type in prototype.main uses a type in utopian.buffer.
- The types involved
prototype.main.Application→utopian.buffer.Buffer
- Direction
- prototype.main uses utopian.buffer, so a change to utopian.buffer can break prototype.main, while a change to prototype.main can't break utopian.buffer.
- Position
- Below the diagonal: prototype.main uses a module listed above it, which is the healthy direction.
26→13 prototype.main uses utopian.vulkan_base✕
- Connections
- 1 pair of types, where a type in prototype.main uses a type in utopian.vulkan_base.
- The types involved
prototype.main.Application→utopian.vulkan_base.VulkanBase
- Direction
- prototype.main uses utopian.vulkan_base, so a change to utopian.vulkan_base can break prototype.main, while a change to prototype.main can't break utopian.vulkan_base.
- Position
- Below the diagonal: prototype.main uses a module listed above it, which is the healthy direction.
26→23 prototype.main uses utopian.renderer✕
- Connections
- 2 pairs of types, where a type in prototype.main uses a type in utopian.renderer.
- The types involved
prototype.main.Application→utopian.renderer.Rendererprototype.main.Application→utopian.renderer.ViewUniformData
- Direction
- prototype.main uses utopian.renderer, so a change to utopian.renderer can break prototype.main, while a change to prototype.main can't break utopian.renderer.
- Position
- Below the diagonal: prototype.main uses a module listed above it, which is the healthy direction.
26→25 prototype.main uses utopian.graph✕
- Connections
- 1 pair of types, where a type in prototype.main uses a type in utopian.graph.
- The types involved
prototype.main.Application→utopian.graph.Graph
- Direction
- prototype.main uses utopian.graph, so a change to utopian.graph can break prototype.main, while a change to prototype.main can't break utopian.graph.
- Position
- Below the diagonal: prototype.main uses a module listed above it, which is the healthy direction.
27→1 utopian.renderers uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers uses a type in utopian.device.
- The types involved
utopian.renderers.renderers$module→utopian.device.Device
- Direction
- utopian.renderers uses utopian.device, so a change to utopian.device can break utopian.renderers, while a change to utopian.renderers can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers uses a module listed above it, which is the healthy direction.
27→7 utopian.renderers uses utopian.camera✕
- Connections
- 1 pair of types, where a type in utopian.renderers uses a type in utopian.camera.
- The types involved
utopian.renderers.renderers$module→utopian.camera.Camera
- Direction
- utopian.renderers uses utopian.camera, so a change to utopian.camera can break utopian.renderers, while a change to utopian.renderers can't break utopian.camera.
- Position
- Below the diagonal: utopian.renderers uses a module listed above it, which is the healthy direction.
27→13 utopian.renderers uses utopian.vulkan_base✕
- Connections
- 1 pair of types, where a type in utopian.renderers uses a type in utopian.vulkan_base.
- The types involved
utopian.renderers.renderers$module→utopian.vulkan_base.VulkanBase
- Direction
- utopian.renderers uses utopian.vulkan_base, so a change to utopian.vulkan_base can break utopian.renderers, while a change to utopian.renderers can't break utopian.vulkan_base.
- Position
- Below the diagonal: utopian.renderers uses a module listed above it, which is the healthy direction.
27→23 utopian.renderers uses utopian.renderer✕
- Connections
- 2 pairs of types, where a type in utopian.renderers uses a type in utopian.renderer.
- The types involved
utopian.renderers.renderers$module→utopian.renderer.Rendererutopian.renderers.renderers$module→utopian.renderer.ViewUniformData
- Direction
- utopian.renderers uses utopian.renderer, so a change to utopian.renderer can break utopian.renderers, while a change to utopian.renderers can't break utopian.renderer.
- Position
- Below the diagonal: utopian.renderers uses a module listed above it, which is the healthy direction.
27→25 utopian.renderers uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers uses a type in utopian.graph.
- The types involved
utopian.renderers.renderers$module→utopian.graph.Graph
- Direction
- utopian.renderers uses utopian.graph, so a change to utopian.graph can break utopian.renderers, while a change to utopian.renderers can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers uses a module listed above it, which is the healthy direction.
28→1 utopian.renderers.atmosphere uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers.atmosphere uses a type in utopian.device.
- The types involved
utopian.renderers.atmosphere.atmosphere$module→utopian.device.Device
- Direction
- utopian.renderers.atmosphere uses utopian.device, so a change to utopian.device can break utopian.renderers.atmosphere, while a change to utopian.renderers.atmosphere can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers.atmosphere uses a module listed above it, which is the healthy direction.
28→7 utopian.renderers.atmosphere uses utopian.camera✕
- Connections
- 1 pair of types, where a type in utopian.renderers.atmosphere uses a type in utopian.camera.
- The types involved
utopian.renderers.atmosphere.atmosphere$module→utopian.camera.Camera
- Direction
- utopian.renderers.atmosphere uses utopian.camera, so a change to utopian.camera can break utopian.renderers.atmosphere, while a change to utopian.renderers.atmosphere can't break utopian.camera.
- Position
- Below the diagonal: utopian.renderers.atmosphere uses a module listed above it, which is the healthy direction.
28→13 utopian.renderers.atmosphere uses utopian.vulkan_base✕
- Connections
- 1 pair of types, where a type in utopian.renderers.atmosphere uses a type in utopian.vulkan_base.
- The types involved
utopian.renderers.atmosphere.atmosphere$module→utopian.vulkan_base.VulkanBase
- Direction
- utopian.renderers.atmosphere uses utopian.vulkan_base, so a change to utopian.vulkan_base can break utopian.renderers.atmosphere, while a change to utopian.renderers.atmosphere can't break utopian.vulkan_base.
- Position
- Below the diagonal: utopian.renderers.atmosphere uses a module listed above it, which is the healthy direction.
28→25 utopian.renderers.atmosphere uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers.atmosphere uses a type in utopian.graph.
- The types involved
utopian.renderers.atmosphere.atmosphere$module→utopian.graph.Graph
- Direction
- utopian.renderers.atmosphere uses utopian.graph, so a change to utopian.graph can break utopian.renderers.atmosphere, while a change to utopian.renderers.atmosphere can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers.atmosphere uses a module listed above it, which is the healthy direction.
29→1 utopian.renderers.deferred uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers.deferred uses a type in utopian.device.
- The types involved
utopian.renderers.deferred.deferred$module→utopian.device.Device
- Direction
- utopian.renderers.deferred uses utopian.device, so a change to utopian.device can break utopian.renderers.deferred, while a change to utopian.renderers.deferred can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers.deferred uses a module listed above it, which is the healthy direction.
29→25 utopian.renderers.deferred uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers.deferred uses a type in utopian.graph.
- The types involved
utopian.renderers.deferred.deferred$module→utopian.graph.Graph
- Direction
- utopian.renderers.deferred uses utopian.graph, so a change to utopian.graph can break utopian.renderers.deferred, while a change to utopian.renderers.deferred can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers.deferred uses a module listed above it, which is the healthy direction.
30→1 utopian.renderers.forward uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers.forward uses a type in utopian.device.
- The types involved
utopian.renderers.forward.forward$module→utopian.device.Device
- Direction
- utopian.renderers.forward uses utopian.device, so a change to utopian.device can break utopian.renderers.forward, while a change to utopian.renderers.forward can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers.forward uses a module listed above it, which is the healthy direction.
30→13 utopian.renderers.forward uses utopian.vulkan_base✕
- Connections
- 1 pair of types, where a type in utopian.renderers.forward uses a type in utopian.vulkan_base.
- The types involved
utopian.renderers.forward.forward$module→utopian.vulkan_base.VulkanBase
- Direction
- utopian.renderers.forward uses utopian.vulkan_base, so a change to utopian.vulkan_base can break utopian.renderers.forward, while a change to utopian.renderers.forward can't break utopian.vulkan_base.
- Position
- Below the diagonal: utopian.renderers.forward uses a module listed above it, which is the healthy direction.
30→25 utopian.renderers.forward uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers.forward uses a type in utopian.graph.
- The types involved
utopian.renderers.forward.forward$module→utopian.graph.Graph
- Direction
- utopian.renderers.forward uses utopian.graph, so a change to utopian.graph can break utopian.renderers.forward, while a change to utopian.renderers.forward can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers.forward uses a module listed above it, which is the healthy direction.
31→1 utopian.renderers.gbuffer uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers.gbuffer uses a type in utopian.device.
- The types involved
utopian.renderers.gbuffer.gbuffer$module→utopian.device.Device
- Direction
- utopian.renderers.gbuffer uses utopian.device, so a change to utopian.device can break utopian.renderers.gbuffer, while a change to utopian.renderers.gbuffer can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers.gbuffer uses a module listed above it, which is the healthy direction.
31→13 utopian.renderers.gbuffer uses utopian.vulkan_base✕
- Connections
- 1 pair of types, where a type in utopian.renderers.gbuffer uses a type in utopian.vulkan_base.
- The types involved
utopian.renderers.gbuffer.gbuffer$module→utopian.vulkan_base.VulkanBase
- Direction
- utopian.renderers.gbuffer uses utopian.vulkan_base, so a change to utopian.vulkan_base can break utopian.renderers.gbuffer, while a change to utopian.renderers.gbuffer can't break utopian.vulkan_base.
- Position
- Below the diagonal: utopian.renderers.gbuffer uses a module listed above it, which is the healthy direction.
31→25 utopian.renderers.gbuffer uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers.gbuffer uses a type in utopian.graph.
- The types involved
utopian.renderers.gbuffer.gbuffer$module→utopian.graph.Graph
- Direction
- utopian.renderers.gbuffer uses utopian.graph, so a change to utopian.graph can break utopian.renderers.gbuffer, while a change to utopian.renderers.gbuffer can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers.gbuffer uses a module listed above it, which is the healthy direction.
32→1 utopian.renderers.ibl uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers.ibl uses a type in utopian.device.
- The types involved
utopian.renderers.ibl.ibl$module→utopian.device.Device
- Direction
- utopian.renderers.ibl uses utopian.device, so a change to utopian.device can break utopian.renderers.ibl, while a change to utopian.renderers.ibl can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers.ibl uses a module listed above it, which is the healthy direction.
32→23 utopian.renderers.ibl uses utopian.renderer✕
- Connections
- 1 pair of types, where a type in utopian.renderers.ibl uses a type in utopian.renderer.
- The types involved
utopian.renderers.ibl.ibl$module→utopian.renderer.Renderer
- Direction
- utopian.renderers.ibl uses utopian.renderer, so a change to utopian.renderer can break utopian.renderers.ibl, while a change to utopian.renderers.ibl can't break utopian.renderer.
- Position
- Below the diagonal: utopian.renderers.ibl uses a module listed above it, which is the healthy direction.
32→25 utopian.renderers.ibl uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers.ibl uses a type in utopian.graph.
- The types involved
utopian.renderers.ibl.ibl$module→utopian.graph.Graph
- Direction
- utopian.renderers.ibl uses utopian.graph, so a change to utopian.graph can break utopian.renderers.ibl, while a change to utopian.renderers.ibl can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers.ibl uses a module listed above it, which is the healthy direction.
33→1 utopian.renderers.marching_cubes uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers.marching_cubes uses a type in utopian.device.
- The types involved
utopian.renderers.marching_cubes.marching_cubes$module→utopian.device.Device
- Direction
- utopian.renderers.marching_cubes uses utopian.device, so a change to utopian.device can break utopian.renderers.marching_cubes, while a change to utopian.renderers.marching_cubes can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers.marching_cubes uses a module listed above it, which is the healthy direction.
33→13 utopian.renderers.marching_cubes uses utopian.vulkan_base✕
- Connections
- 1 pair of types, where a type in utopian.renderers.marching_cubes uses a type in utopian.vulkan_base.
- The types involved
utopian.renderers.marching_cubes.marching_cubes$module→utopian.vulkan_base.VulkanBase
- Direction
- utopian.renderers.marching_cubes uses utopian.vulkan_base, so a change to utopian.vulkan_base can break utopian.renderers.marching_cubes, while a change to utopian.renderers.marching_cubes can't break utopian.vulkan_base.
- Position
- Below the diagonal: utopian.renderers.marching_cubes uses a module listed above it, which is the healthy direction.
33→25 utopian.renderers.marching_cubes uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers.marching_cubes uses a type in utopian.graph.
- The types involved
utopian.renderers.marching_cubes.marching_cubes$module→utopian.graph.Graph
- Direction
- utopian.renderers.marching_cubes uses utopian.graph, so a change to utopian.graph can break utopian.renderers.marching_cubes, while a change to utopian.renderers.marching_cubes can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers.marching_cubes uses a module listed above it, which is the healthy direction.
34→1 utopian.renderers.present uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers.present uses a type in utopian.device.
- The types involved
utopian.renderers.present.present$module→utopian.device.Device
- Direction
- utopian.renderers.present uses utopian.device, so a change to utopian.device can break utopian.renderers.present, while a change to utopian.renderers.present can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers.present uses a module listed above it, which is the healthy direction.
34→13 utopian.renderers.present uses utopian.vulkan_base✕
- Connections
- 1 pair of types, where a type in utopian.renderers.present uses a type in utopian.vulkan_base.
- The types involved
utopian.renderers.present.present$module→utopian.vulkan_base.VulkanBase
- Direction
- utopian.renderers.present uses utopian.vulkan_base, so a change to utopian.vulkan_base can break utopian.renderers.present, while a change to utopian.renderers.present can't break utopian.vulkan_base.
- Position
- Below the diagonal: utopian.renderers.present uses a module listed above it, which is the healthy direction.
34→25 utopian.renderers.present uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers.present uses a type in utopian.graph.
- The types involved
utopian.renderers.present.present$module→utopian.graph.Graph
- Direction
- utopian.renderers.present uses utopian.graph, so a change to utopian.graph can break utopian.renderers.present, while a change to utopian.renderers.present can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers.present uses a module listed above it, which is the healthy direction.
35→1 utopian.renderers.rt_reflections uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers.rt_reflections uses a type in utopian.device.
- The types involved
utopian.renderers.rt_reflections.rt_reflections$module→utopian.device.Device
- Direction
- utopian.renderers.rt_reflections uses utopian.device, so a change to utopian.device can break utopian.renderers.rt_reflections, while a change to utopian.renderers.rt_reflections can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers.rt_reflections uses a module listed above it, which is the healthy direction.
35→25 utopian.renderers.rt_reflections uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers.rt_reflections uses a type in utopian.graph.
- The types involved
utopian.renderers.rt_reflections.rt_reflections$module→utopian.graph.Graph
- Direction
- utopian.renderers.rt_reflections uses utopian.graph, so a change to utopian.graph can break utopian.renderers.rt_reflections, while a change to utopian.renderers.rt_reflections can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers.rt_reflections uses a module listed above it, which is the healthy direction.
36→1 utopian.renderers.rt_shadows uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers.rt_shadows uses a type in utopian.device.
- The types involved
utopian.renderers.rt_shadows.rt_shadows$module→utopian.device.Device
- Direction
- utopian.renderers.rt_shadows uses utopian.device, so a change to utopian.device can break utopian.renderers.rt_shadows, while a change to utopian.renderers.rt_shadows can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers.rt_shadows uses a module listed above it, which is the healthy direction.
36→25 utopian.renderers.rt_shadows uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers.rt_shadows uses a type in utopian.graph.
- The types involved
utopian.renderers.rt_shadows.rt_shadows$module→utopian.graph.Graph
- Direction
- utopian.renderers.rt_shadows uses utopian.graph, so a change to utopian.graph can break utopian.renderers.rt_shadows, while a change to utopian.renderers.rt_shadows can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers.rt_shadows uses a module listed above it, which is the healthy direction.
37→1 utopian.renderers.shadertoy uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers.shadertoy uses a type in utopian.device.
- The types involved
utopian.renderers.shadertoy.shadertoy$module→utopian.device.Device
- Direction
- utopian.renderers.shadertoy uses utopian.device, so a change to utopian.device can break utopian.renderers.shadertoy, while a change to utopian.renderers.shadertoy can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers.shadertoy uses a module listed above it, which is the healthy direction.
37→13 utopian.renderers.shadertoy uses utopian.vulkan_base✕
- Connections
- 1 pair of types, where a type in utopian.renderers.shadertoy uses a type in utopian.vulkan_base.
- The types involved
utopian.renderers.shadertoy.shadertoy$module→utopian.vulkan_base.VulkanBase
- Direction
- utopian.renderers.shadertoy uses utopian.vulkan_base, so a change to utopian.vulkan_base can break utopian.renderers.shadertoy, while a change to utopian.renderers.shadertoy can't break utopian.vulkan_base.
- Position
- Below the diagonal: utopian.renderers.shadertoy uses a module listed above it, which is the healthy direction.
37→25 utopian.renderers.shadertoy uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers.shadertoy uses a type in utopian.graph.
- The types involved
utopian.renderers.shadertoy.shadertoy$module→utopian.graph.Graph
- Direction
- utopian.renderers.shadertoy uses utopian.graph, so a change to utopian.graph can break utopian.renderers.shadertoy, while a change to utopian.renderers.shadertoy can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers.shadertoy uses a module listed above it, which is the healthy direction.
38→1 utopian.renderers.shadow uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers.shadow uses a type in utopian.device.
- The types involved
utopian.renderers.shadow.shadow$module→utopian.device.Device
- Direction
- utopian.renderers.shadow uses utopian.device, so a change to utopian.device can break utopian.renderers.shadow, while a change to utopian.renderers.shadow can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers.shadow uses a module listed above it, which is the healthy direction.
38→7 utopian.renderers.shadow uses utopian.camera✕
- Connections
- 1 pair of types, where a type in utopian.renderers.shadow uses a type in utopian.camera.
- The types involved
utopian.renderers.shadow.shadow$module→utopian.camera.Camera
- Direction
- utopian.renderers.shadow uses utopian.camera, so a change to utopian.camera can break utopian.renderers.shadow, while a change to utopian.renderers.shadow can't break utopian.camera.
- Position
- Below the diagonal: utopian.renderers.shadow uses a module listed above it, which is the healthy direction.
38→25 utopian.renderers.shadow uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers.shadow uses a type in utopian.graph.
- The types involved
utopian.renderers.shadow.shadow$module→utopian.graph.Graph
- Direction
- utopian.renderers.shadow uses utopian.graph, so a change to utopian.graph can break utopian.renderers.shadow, while a change to utopian.renderers.shadow can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers.shadow uses a module listed above it, which is the healthy direction.
39→1 utopian.renderers.ssao uses utopian.device✕
- Connections
- 1 pair of types, where a type in utopian.renderers.ssao uses a type in utopian.device.
- The types involved
utopian.renderers.ssao.ssao$module→utopian.device.Device
- Direction
- utopian.renderers.ssao uses utopian.device, so a change to utopian.device can break utopian.renderers.ssao, while a change to utopian.renderers.ssao can't break utopian.device.
- Position
- Below the diagonal: utopian.renderers.ssao uses a module listed above it, which is the healthy direction.
39→25 utopian.renderers.ssao uses utopian.graph✕
- Connections
- 1 pair of types, where a type in utopian.renderers.ssao uses a type in utopian.graph.
- The types involved
utopian.renderers.ssao.ssao$module→utopian.graph.Graph
- Direction
- utopian.renderers.ssao uses utopian.graph, so a change to utopian.graph can break utopian.renderers.ssao, while a change to utopian.renderers.ssao can't break utopian.graph.
- Position
- Below the diagonal: utopian.renderers.ssao uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 25 | Medium |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs; Add a CI workflow that builds and runs the test suite on every push/PR.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. | +8.0 pts | Low | ADR Quality |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +21.3 pts | High | Code Coverage |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +6.0 pts | Medium | CI/CD gates |
| 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. | +5.9 pts | Medium | Architecture documentation |
| Resolve the 1 Yanked release finding(s) in Dependency Hygiene. | +2.6 pts | Low | Dependency Hygiene |
| Resolve the 46 TodoComment finding(s) in Explicit Debt — start with graph.rs (13), descriptor_set.rs (4), image.rs (4). | +1.3 pts | Medium | Explicit Debt |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.3 pts | Medium | Release Hygiene |
| Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.rs. | +0.9 pts | Medium | Churn × Complexity Hotspots |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| utopian/src/graph.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| prototype/src/main.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| utopian/src/image.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| utopian/src/renderers/mod.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| utopian/src/renderers/ibl.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| utopian/src/pipeline.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| utopian/src/raytracing.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| utopian/src/descriptor_set.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| utopian/src/renderers/forward.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| utopian/src/bindless.rs | 6.9 | Mixed | Explicit Debt: HackComment |
| utopian/src/buffer.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| utopian/src/pass.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| utopian/src/renderers/atmosphere.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| utopian/src/camera.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| utopian/src/primitive.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| utopian/src/synch.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| utopian/src/renderers/shadow.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| utopian/src/renderers/ssao.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| utopian/src/renderers/gbuffer.rs | 8.2 | Near-clean | 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
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 43 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 43 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, 164 of 173 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 238 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 1 hold 2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# or Visual Basic was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 72 further occurrence(s) are not listed individually; the score already reflects all 112.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
2 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was Graph::render at 29.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Graph::render (cyclomatic 29), Application::run (cyclomatic 28). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
6 function(s) exceeded the cognitive complexity threshold of 15; the worst was Graph::render at 62.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with Graph::render (cognitive 62), Application::run (cognitive 33). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 8.0 to about 8.8/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
11 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 4 MethodTooLong finding(s) in God Classes — start with main.rs (2), graph.rs, device.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with graph.rs, main.rs, pipeline.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with graph.rs, pipeline.rs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
14 duplicated block group(s) detected. 7.7 % of the production lines (607 of 7,896) are in a reported copy. A further 7 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with forward.rs, main.rs, mod.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with descriptor_set.rs, renderer.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with raytracing.rs (2). — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
2 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 22 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
1 outdated, 1 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.
What to do
- Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 338 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 7 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.
D15 · Churn × Complexity Hotspots
Top hotspots: prototype/src/main.rs (3×28=84)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.rs. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
49 deducted task-comment markers across 7896 LoC (0.5/KLoC) → score 9.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 46 TodoComment finding(s) in Explicit Debt — start with graph.rs (13), descriptor_set.rs (4), image.rs (4). — One of this dimension's main actionable groups (46 warning-level).
- Resolve the 3 HackComment finding(s) in Explicit Debt — start with bindless.rs (3). — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 3 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 2 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
25 finding(s): 0 critical, 0 high, 25 medium, 0 low.
What to do
- Resolve the 11 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 6 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 6 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 27 of the 41 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `new` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — utopian/src/descriptor_set.rs:48
- `new_from_desc` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — utopian/src/image.rs:175
- `new_from_handle` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — utopian/src/image.rs:233
- `create_image_view` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — utopian/src/image.rs:278
- `transition_layout` does real work, but one of its branches is `unimplemented!` — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. (×2) — utopian/src/image.rs:376, utopian/src/image.rs:408
What to do
- Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `prototype/Cargo.toml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — prototype/Cargo.toml:8
What to do
- Run what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X25 · Inert configuration knob
- `ImageDesc.usage` is offered as a builder setter option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — utopian/src/image.rs:26
What to do
- Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
X5 · Nullable reference types
- `device.handle.create_descriptor_set_layout(&descriptor_sets_layout_info,None)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `create_bindless_descriptor_set_layout` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/bindless.rs:77
- `device.handle.create_descriptor_pool(&descriptor_pool_info,None)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `create_bindless_descriptor_set` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/bindless.rs:109
- `device.handle.allocate_descriptor_sets(&vk::DescriptorSetAllocateInfo::builder().descriptor_pool(descriptor_pool).set_layouts(std::slice::from_ref(&layout)).push_next(&mut variable_descriptor_count_allocate_info).build(),)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `create_bindless_descriptor_set` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/bindless.rs:128
- `device.handle.create_buffer(&buffer_info,None)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `create_buffer` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/buffer.rs:34
- `device.gpu_allocator.lock().unwrap().allocate(&AllocationCreateDesc{name:"Example allocation",requirements:buffer_memory_req,location:memory_location,linear:true,})` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `create_buffer` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/buffer.rs:48
- `device.handle.bind_buffer_memory(buffer,allocation.memory(),allocation.offset())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `create_buffer` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/buffer.rs:53
- `self.allocation.mapped_ptr()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `update_memory` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/buffer.rs:95
- `staging_buffer.allocation.mapped_ptr()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `update_memory` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/buffer.rs:107
- `device.gpu_allocator.lock().unwrap().free(staging_buffer.allocation)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `update_memory` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/buffer.rs:131
- `device.handle.create_descriptor_pool(&descriptor_pool_info,None)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/descriptor_set.rs:73
- `device.handle.allocate_descriptor_sets(&descriptor_alloc_info)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/descriptor_set.rs:88
- `self.binding_map.iter().next()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `get_set_index` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/descriptor_set.rs:283
- `self.handle.device_wait_idle()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `drop` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:28
- `instance.enumerate_physical_devices()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:42
- `queue_family_properties.iter().position(|info|info.queue_flags.contains(vk::QueueFlags::GRAPHICS))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:52
- `surface_loader.get_physical_device_surface_support(physical_device,queue_family_index,surface)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:56
- `instance.enumerate_device_extension_properties(physical_device)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:61
- `instance.create_device(physical_device,&device_create_info,None)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:164
- `Allocator::new(&AllocatorCreateDesc{instance:instance.clone(),device:device.clone(),physical_device,debug_settings:AllocatorDebugSettings{log_leaks_on_shutdown:false,log_memory_information:true,log_allocations:true,log_stack_traces:true,..Default::default()},buffer_device_address:true,})` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:196
- `device.create_command_pool(&pool_create_info,None)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `create_setup_command_buffer` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:270
- `device.allocate_command_buffers(&command_buffer_allocate_info)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `create_setup_command_buffer` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:281
- `self.handle.begin_command_buffer(self.setup_cmd_buf,&command_buffer_begin_info)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `execute_and_submit` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:293
- `self.handle.end_command_buffer(self.setup_cmd_buf)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `execute_and_submit` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:301
- `self.handle.queue_submit(self.queue,&[submit_info.build()],vk::Fence::null())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `execute_and_submit` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:310
- `self.handle.device_wait_idle()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `execute_and_submit` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:314
- `std::mem::size_of_val(&data).try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `cmd_push_constants` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:346
- `std::ffi::CString::new(name)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `set_debug_name` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:353
- `self.debug_utils.set_debug_utils_object_name(self.handle.handle(),&name_info)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `set_debug_name` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/device.rs:362
- `Watcher::new(watcher_tx,Duration::from_millis(100))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/directory_watcher.rs:15
- `directory_watcher.watch(path,RecursiveMode::Recursive)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/directory_watcher.rs:18
- `reader.read_indices()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `load_node` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/gltf_loader.rs:68
- `reader.read_positions()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `load_node` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/gltf_loader.rs:69
- `reader.read_normals()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `load_node` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/gltf_loader.rs:70
- `model.meshes.last_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `load_node` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×2) — utopian/src/gltf_loader.rs:151, utopian/src/gltf_loader.rs:158
- `image::RgbImage::from_raw(image.width,image.height,std::mem::take(&mut image.pixels),)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `load_gltf` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/gltf_loader.rs:189
- `self.uniforms.keys().next()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/graph.rs:406
- `self.uniforms.values().next()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `build` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/graph.rs:411
- `device.handle.create_descriptor_set_layout(&descriptor_sets_layout_info,None)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `create_camera_descriptor_set` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/graph.rs:509
- `raytracing.top_level_acceleration.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `prepare` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — utopian/src/graph.rs:662
What to do
- Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70.4 | Strong | Solid. |
| Architecture | 96.3 | Exemplary | Solid. |
| Maturity | 54.9 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 26.9 | Weak — gated by D8, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100.0 | Exemplary | Strongest area. |
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- 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 — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1162 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- 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.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (4 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
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 41 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.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not 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.
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 1 finding(s)
- No automated tests
Serious — 165 finding(s)
- TodoComment utopian/src/buffer.rs:19
- TodoComment utopian/src/buffer.rs:69
- TodoComment utopian/src/camera.rs:84
- TodoComment utopian/src/descriptor_set.rs:53
- TodoComment utopian/src/descriptor_set.rs:58
- TodoComment utopian/src/descriptor_set.rs:114
- TodoComment utopian/src/descriptor_set.rs:148
- TodoComment utopian/src/graph.rs:281
- TodoComment utopian/src/graph.rs:291
- TodoComment utopian/src/graph.rs:947
- TodoComment utopian/src/graph.rs:948
- TodoComment utopian/src/renderers/mod.rs:392
- TodoComment utopian/src/graph.rs:403
- TodoComment utopian/src/graph.rs:575
- TodoComment utopian/src/graph.rs:576
- TodoComment utopian/src/graph.rs:644
- TodoComment utopian/src/graph.rs:712
- TodoComment utopian/src/graph.rs:753
- TodoComment utopian/src/graph.rs:755
- TodoComment utopian/src/graph.rs:874
- TodoComment utopian/src/graph.rs:925
- TodoComment utopian/src/image.rs:40
- TodoComment utopian/src/image.rs:59
- TodoComment utopian/src/image.rs:76
- TodoComment utopian/src/image.rs:100
- Symbol treated as nullable, then dereferenced unguarded utopian/src/bindless.rs:77
- Symbol treated as nullable, then dereferenced unguarded utopian/src/bindless.rs:109
- Symbol treated as nullable, then dereferenced unguarded utopian/src/bindless.rs:128
- Symbol treated as nullable, then dereferenced unguarded utopian/src/buffer.rs:34
- Symbol treated as nullable, then dereferenced unguarded utopian/src/buffer.rs:48
- Symbol treated as nullable, then dereferenced unguarded utopian/src/buffer.rs:53
- Symbol treated as nullable, then dereferenced unguarded utopian/src/buffer.rs:95
- Symbol treated as nullable, then dereferenced unguarded utopian/src/buffer.rs:107
- Symbol treated as nullable, then dereferenced unguarded utopian/src/buffer.rs:131
- Symbol treated as nullable, then dereferenced unguarded utopian/src/descriptor_set.rs:73
- Symbol treated as nullable, then dereferenced unguarded utopian/src/descriptor_set.rs:88
- Symbol treated as nullable, then dereferenced unguarded utopian/src/descriptor_set.rs:283
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:28
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:42
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:52
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:56
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:61
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:164
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:196
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:270
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:281
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:293
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:301
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:310
- Symbol treated as nullable, then dereferenced unguarded utopian/src/device.rs:314
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unfinished branch — a todo!() / unimplemented!() arm in a real function utopian/src/descriptor_set.rs:48
- Unfinished branch — a todo!() / unimplemented!() arm in a real function utopian/src/image.rs:175
- Unfinished branch — a todo!() / unimplemented!() arm in a real function utopian/src/image.rs:233
- Unfinished branch — a todo!() / unimplemented!() arm in a real function utopian/src/image.rs:278
- Unfinished branch — a todo!() / unimplemented!() arm in a real function utopian/src/image.rs:376
- Unfinished branch — a todo!() / unimplemented!() arm in a real function utopian/src/image.rs:408
- MethodTooLong: Graph.render utopian/src/graph.rs:707
- MethodTooLong: Application.run prototype/src/main.rs:374
- MethodTooLong: Device.new utopian/src/device.rs:33
- MethodTooLong: Application.update_ui prototype/src/main.rs:186
- Duplicated block (8 lines × 2) utopian/src/renderers/forward.rs:33
- Duplicated block (8 lines × 2) prototype/src/main.rs:207
- Duplicated block (8 lines × 2) utopian/src/renderers/mod.rs:227
- Duplicated block (8 lines × 2) utopian/src/renderers/ibl.rs:68
- HackComment utopian/src/bindless.rs:35
- HackComment utopian/src/bindless.rs:42
- HackComment utopian/src/bindless.rs:49
- ClassTooLong: Graph utopian/src/graph.rs:99
- ClassTooLong: Application prototype/src/main.rs:14
- ClassTooLong: Pipeline utopian/src/pipeline.rs:25
- FileTooLong: src/graph.rs utopian/src/graph.rs
- FileTooLong: src/pipeline.rs utopian/src/pipeline.rs
- FunctionTooLong: utopian::renderers::build_path_tracing_render_graph utopian/src/renderers/mod.rs:190
- FunctionTooLong: utopian::renderers::ibl::setup_cubemap_pass utopian/src/renderers/ibl.rs:6
- REDACTED
- REDACTED
- Duplicated block (18 lines × 2) utopian/src/descriptor_set.rs:30
- Duplicated block (18 lines × 2) utopian/src/renderer.rs:326
- Duplicated block (9 lines × 2) utopian/src/raytracing.rs:300
- Duplicated block (9 lines × 2) utopian/src/raytracing.rs:310
- Graph::render (cyclomatic 29) utopian/src/graph.rs:707
- Application::run (cyclomatic 28) prototype/src/main.rs:374
- Yanked release: log
- Hotspot: prototype/src/main.rs prototype/src/main.rs:374
- Graph::render (cognitive 62) utopian/src/graph.rs:707
- Application::run (cognitive 33) prototype/src/main.rs:374
- Input::update (cognitive 25) utopian/src/input.rs:28
- Reflection::new (cognitive 19) utopian/src/shader.rs:30
- utopian::gltf_loader::load_node (cognitive 19) utopian/src/gltf_loader.rs:47
- Image::new_from_desc (cognitive 16) utopian/src/image.rs:113
- Near-duplicate member pair (64 shared lines) utopian/src/raytracing.rs:116
- Edited copy of a member (44 corresponding lines) utopian/src/pipeline.rs:201
- Edited copies of one member (4 members, 22+ corresponding lines) utopian/src/descriptor_set.rs:130
- Edited copy of a member (23 corresponding lines) utopian/src/renderers/forward.rs:18
- Edited copy of a member (28 corresponding lines) utopian/src/renderers/rt_reflections.rs:17
- Edited copies of one member (3 members, 19+ corresponding lines) utopian/src/descriptor_set.rs:259
- Edited copy of a member (9 corresponding lines) utopian/src/model_loader.rs:27
- Duplicated block (23 lines × 2) utopian/src/raytracing.rs:192
- Duplicated block (21 lines × 2) utopian/src/raytracing.rs:148
- Duplicated block (20 lines × 2) utopian/src/raytracing.rs:170
- Duplicated block (17 lines × 2) utopian/src/image.rs:168
- Duplicated block (13–15 lines × 2) utopian/src/renderers/ibl.rs:84
- Duplicated block (7 lines × 3) utopian/src/descriptor_set.rs:131
- Off the main sequence: utopian
- No CI pipeline
- Configuration option is read nowhere utopian/src/image.rs:26
Minor — 6 finding(s)
- No ADRs found prototype/src/main.rs:1
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation prototype/Cargo.toml:8
- No changelog
Minor — 1 finding(s)
- Outdated: simple_logger
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-0c70b6ce3d3c48e89f81c93beafadd38/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=38" --report-format json --report-path /tmp/watchdog-gitleaks-0c70b6ce3d3c48e89f81c93beafadd38/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-0c70b6ce3d3c48e89f81c93beafadd38/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | 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 . | 25 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| 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 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |