Executive summary
not-fl3/macroquad falls short of our standard for a preview release, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 64 out of 100 and is rated Adequate, and all six of its critical findings are security problems in the build pipeline.
Production Readiness, at 50, is the weakest lens and counts most in the score. The best first step is adding tests for untested code, worth about 12 points. Recording design decisions comes next, worth about 8 points. Raising Production Readiness to 62 would lift the score to about 68.
Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 16,290 lines, about €22,000 to rebuild.
If Production Readiness rose from 50 to 62, the lowest score rated Strong, the score would rise from 64 to about 68.
New since the last survey: 74 findings
- Code Duplication · Edited copy of a member (31 corresponding lines) src/texture.rs
- Code Duplication · Edited copy of a member (25 corresponding lines) src/shapes.rs
- Code Duplication · Edited copy of a member (32 corresponding lines) physics-platformer/src/lib.rs
- Code Duplication · Edited copy of a member (21 corresponding lines) src/ui/style.rs
- Code Duplication · Edited copy of a member (24 corresponding lines) src/camera.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) src/models.rs
- Code Duplication · Edited copy of a member (18 corresponding lines) src/lib.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/experimental/collections/storage.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/texture.rs
- Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) src/ui/render/painter.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/lib.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/shapes.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/texture.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/lib.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/ui/widgets/editbox/text_editor.rs
- Code Duplication · Duplicated block (10–11 lines × 2) src/ui/widgets/checkbox.rs
- Code Duplication · Duplicated block (10 lines × 2) src/quad_gl.rs
- Code Duplication · Duplicated block (5 lines × 2) macroquad_macro/src/lib.rs
- Code Duplication · Duplicated block (5 lines × 2) src/shapes.rs
- Code Duplication · Duplicated block (5 lines × 2) src/ui/render/mesh_rasterizer.rs
- Code Duplication · Duplicated block (5 lines × 2) src/ui/widgets/progress_bar.rs
- Code Coverage · Low coverage: src/audio.rs src/audio.rs
- Code Coverage · Low coverage: src/camera.rs src/camera.rs
- Code Coverage · Low coverage: src/color.rs src/color.rs
- Code Coverage · Low coverage: src/error.rs src/error.rs
- Code Coverage · Low coverage: src/exec.rs src/exec.rs
- Code Coverage · Low coverage: src/experimental/animation.rs src/experimental/animation.rs
- Code Coverage · Low coverage: src/experimental/camera/mouse.rs src/experimental/camera/mouse.rs
- Code Coverage · Low coverage: src/experimental/coroutines.rs src/experimental/coroutines.rs
- Code Coverage · Low coverage: src/experimental/coroutines/generational_storage.rs src/experimental/coroutines/generational_storage.rs
- Code Coverage · Low coverage: src/experimental/scene.rs src/experimental/scene.rs
- Code Coverage · Low coverage: src/experimental/scene/arena.rs src/experimental/scene/arena.rs
- Code Coverage · Low coverage: src/experimental/state_machine.rs src/experimental/state_machine.rs
- Code Coverage · Low coverage: src/file.rs src/file.rs
- Code Coverage · Low coverage: src/input.rs src/input.rs
- Code Coverage · Low coverage: src/lib.rs src/lib.rs
- Code Coverage · Low coverage: src/math.rs src/math.rs
- Code Coverage · Low coverage: src/math/circle.rs src/math/circle.rs
- Code Coverage · Low coverage: src/math/rect.rs src/math/rect.rs
- Code Coverage · Low coverage: src/models.rs src/models.rs
- Code Coverage · Low coverage: src/quad_gl.rs src/quad_gl.rs
- Code Coverage · Low coverage: src/shapes.rs src/shapes.rs
- Code Coverage · Low coverage: src/telemetry.rs src/telemetry.rs
- Code Coverage · Low coverage: src/text.rs src/text.rs
- Code Coverage · Low coverage: src/texture.rs src/texture.rs
- Code Coverage · Low coverage: src/texture/slotmap.rs src/texture/slotmap.rs
- Code Coverage · Low coverage: src/time.rs src/time.rs
- Code Coverage · Low coverage: src/tobytes.rs src/tobytes.rs
- Code Coverage · Low coverage: src/ui.rs src/ui.rs
- Code Coverage · Low coverage: src/ui/canvas.rs src/ui/canvas.rs
- Code Coverage · Low coverage: src/ui/cursor.rs src/ui/cursor.rs
- Code Coverage · Low coverage: src/ui/input.rs src/ui/input.rs
- Code Coverage · Low coverage: src/ui/key_repeat.rs src/ui/key_repeat.rs
- Code Coverage · Low coverage: src/ui/render/mesh_rasterizer.rs src/ui/render/mesh_rasterizer.rs
- Code Coverage · Low coverage: src/ui/render/painter.rs src/ui/render/painter.rs
- Code Coverage · Low coverage: src/ui/style.rs src/ui/style.rs
- Code Coverage · Low coverage: src/ui/widgets/button.rs src/ui/widgets/button.rs
- Code Coverage · Low coverage: src/ui/widgets/checkbox.rs src/ui/widgets/checkbox.rs
- Code Coverage · Low coverage: src/ui/widgets/combobox.rs src/ui/widgets/combobox.rs
- Code Coverage · Low coverage: src/ui/widgets/drag.rs src/ui/widgets/drag.rs
- Code Coverage · Low coverage: src/ui/widgets/editbox.rs src/ui/widgets/editbox.rs
- Code Coverage · Low coverage: src/ui/widgets/editbox/text_editor.rs src/ui/widgets/editbox/text_editor.rs
- Code Coverage · Low coverage: src/ui/widgets/group.rs src/ui/widgets/group.rs
- Code Coverage · Low coverage: src/ui/widgets/input.rs src/ui/widgets/input.rs
- Code Coverage · Low coverage: src/ui/widgets/label.rs src/ui/widgets/label.rs
- Code Coverage · Low coverage: src/ui/widgets/popup.rs src/ui/widgets/popup.rs
- Code Coverage · Low coverage: src/ui/widgets/progress_bar.rs src/ui/widgets/progress_bar.rs
- Code Coverage · Low coverage: src/ui/widgets/separator.rs src/ui/widgets/separator.rs
- Code Coverage · Low coverage: src/ui/widgets/slider.rs src/ui/widgets/slider.rs
- Code Coverage · Low coverage: src/ui/widgets/tabbar.rs src/ui/widgets/tabbar.rs
- Code Coverage · Low coverage: src/ui/widgets/texture.rs src/ui/widgets/texture.rs
- Code Coverage · Low coverage: src/ui/widgets/tree_node.rs src/ui/widgets/tree_node.rs
- Code Coverage · Low coverage: src/ui/widgets/window.rs src/ui/widgets/window.rs
- Code Coverage · Low coverage: src/window.rs src/window.rs
Fixed since the last survey: 5 findings
- Code Duplication · Duplicated block (7 lines × 2) src/ui/widgets/checkbox.rs
- Code Duplication · Duplicated block (5 lines × 2) src/shapes.rs
- Code Duplication · Duplicated block (5 lines × 2) src/ui/render/mesh_rasterizer.rs
- Code Duplication · Duplicated block (6 lines × 2) macroquad_macro/src/lib.rs
- Code Duplication · Duplicated block (5 lines × 3) src/ui/style.rs
Rebuild cost: about €22,000 · Estimate
| Cost to rebuild | €7,400 to €37,000, for 123 to 390 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 64. 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: 16,290 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 macroquad.color | 2 macroquad.math.rect | 3 macroquad.ui.input | 4 macroquad.ui.input_handler | 5 macroquad.audio | 6 macroquad.conf | 7 macroquad.experimental.coroutines | 8 macroquad.experimental.scene.arena | 9 macroquad.input | 10 macroquad.text.atlas | 11 macroquad.ui.cursor | 12 macroquad.ui.key_repeat | 13 macroquad.audio.dummy_audio | 14 macroquad.text | 15 macroquad.texture | 16 macroquad.camera | 17 macroquad.models | 18 macroquad.ui.canvas | 19 macroquad.ui.style | 20 macroquad_tiled | 21 macroquad.experimental.scene | 22 macroquad.quad_gl | 23 macroquad.ui.render.painter | 24 macroquad.experimental.state_machine | 25 macroquad.material | 26 macroquad.ui.render.mesh_rasterizer | 27 macroquad.ui.widgets.drag | 28 macroquad_particles | 29 macroquad.ui | 30 macroquad.ui.ui_context | 31 macroquad.ui.widgets.checkbox | 32 macroquad.ui.widgets.combobox | 33 macroquad.ui.widgets.editbox | 34 macroquad.ui.widgets.group | 35 macroquad.ui.widgets.input | 36 macroquad | 37 macroquad.exec | 38 macroquad.experimental.coroutines.tweens | 39 macroquad.ui.widgets.window | 40 macroquad.window |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 macroquad.color | ||||||||||||||||||||||||||||||||||||||||
| 2 macroquad.math.rect | ||||||||||||||||||||||||||||||||||||||||
| 3 macroquad.ui.input | ||||||||||||||||||||||||||||||||||||||||
| 4 macroquad.ui.input_handler | ||||||||||||||||||||||||||||||||||||||||
| 5 macroquad.audio | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 macroquad.conf | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 macroquad.experimental.coroutines | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 macroquad.experimental.scene.arena | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 macroquad.input | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 macroquad.text.atlas | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 macroquad.ui.cursor | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 macroquad.ui.key_repeat | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 macroquad.audio.dummy_audio | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 macroquad.text | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 macroquad.texture | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 macroquad.camera | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 17 macroquad.models | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 macroquad.ui.canvas | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 macroquad.ui.style | 2 | 2 | 3 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 20 macroquad_tiled | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 macroquad.experimental.scene | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 macroquad.quad_gl | 1 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 macroquad.ui.render.painter | 2 | 2 | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 24 macroquad.experimental.state_machine | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 macroquad.material | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 macroquad.ui.render.mesh_rasterizer | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 27 macroquad.ui.widgets.drag | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 macroquad_particles | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 macroquad.ui | 3 | 3 | 2 | 3 | 1 | 1 | 2 | 2 | 1 | 4 | 4 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||
| 30 macroquad.ui.ui_context | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 macroquad.ui.widgets.checkbox | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 macroquad.ui.widgets.combobox | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 macroquad.ui.widgets.editbox | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 macroquad.ui.widgets.group | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 35 macroquad.ui.widgets.input | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 macroquad | 1 | 1 | 1 | 1 | 1 | 1 | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 37 macroquad.exec | 2 | |||||||||||||||||||||||||||||||||||||||
| 38 macroquad.experimental.coroutines.tweens | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 macroquad.ui.widgets.window | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 macroquad.window | 1 | 1 | 1 |
5→13 macroquad.audio uses macroquad.audio.dummy_audio part of a loop✕
- Connections
- 2 pairs of types, where a type in macroquad.audio uses a type in macroquad.audio.dummy_audio.
- The types involved
macroquad.audio.AudioContext→macroquad.audio.dummy_audio.AudioContextmacroquad.audio.audio$module→macroquad.audio.dummy_audio.Sound
- Direction
- macroquad.audio uses macroquad.audio.dummy_audio, so a change to macroquad.audio.dummy_audio can break macroquad.audio, while a change to macroquad.audio can't break macroquad.audio.dummy_audio.
- 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.
6→4 macroquad.conf uses macroquad.ui.input_handler✕
- Connections
- 1 pair of types, where a type in macroquad.conf uses a type in macroquad.ui.input_handler.
- The types involved
macroquad.conf.UpdateTrigger→macroquad.ui.input_handler.KeyCode
- Direction
- macroquad.conf uses macroquad.ui.input_handler, so a change to macroquad.ui.input_handler can break macroquad.conf, while a change to macroquad.conf can't break macroquad.ui.input_handler.
- Position
- Below the diagonal: macroquad.conf uses a module listed above it, which is the healthy direction.
7→36 macroquad.experimental.coroutines uses macroquad part of a loop✕
- Connections
- 1 pair of types, where a type in macroquad.experimental.coroutines uses a type in macroquad.
- The types involved
macroquad.experimental.coroutines.TimerDelayFuture→macroquad.Context
- Direction
- macroquad.experimental.coroutines uses macroquad, so a change to macroquad can break macroquad.experimental.coroutines, while a change to macroquad.experimental.coroutines can't break macroquad.
- 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.
8→21 macroquad.experimental.scene.arena uses macroquad.experimental.scene part of a loop✕
- Connections
- 1 pair of types, where a type in macroquad.experimental.scene.arena uses a type in macroquad.experimental.scene.
- The types involved
macroquad.experimental.scene.arena.Arena→macroquad.experimental.scene.Cell
- Direction
- macroquad.experimental.scene.arena uses macroquad.experimental.scene, so a change to macroquad.experimental.scene can break macroquad.experimental.scene.arena, while a change to macroquad.experimental.scene.arena can't break macroquad.experimental.scene.
- 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.
9→4 macroquad.input uses macroquad.ui.input_handler✕
- Connections
- 1 pair of types, where a type in macroquad.input uses a type in macroquad.ui.input_handler.
- The types involved
macroquad.input.input$module→macroquad.ui.input_handler.KeyCode
- Direction
- macroquad.input uses macroquad.ui.input_handler, so a change to macroquad.ui.input_handler can break macroquad.input, while a change to macroquad.input can't break macroquad.ui.input_handler.
- Position
- Below the diagonal: macroquad.input uses a module listed above it, which is the healthy direction.
9→36 macroquad.input uses macroquad part of a loop✕
- Connections
- 1 pair of types, where a type in macroquad.input uses a type in macroquad.
- The types involved
macroquad.input.input$module→macroquad.DroppedFile
- Direction
- macroquad.input uses macroquad, so a change to macroquad can break macroquad.input, while a change to macroquad.input can't break macroquad.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 macroquad.text.atlas uses macroquad.math.rect✕
- Connections
- 2 pairs of types, where a type in macroquad.text.atlas uses a type in macroquad.math.rect.
- The types involved
macroquad.text.atlas.Atlas→macroquad.math.rect.Rectmacroquad.text.atlas.Sprite→macroquad.math.rect.Rect
- Direction
- macroquad.text.atlas uses macroquad.math.rect, so a change to macroquad.math.rect can break macroquad.text.atlas, while a change to macroquad.text.atlas can't break macroquad.math.rect.
- Position
- Below the diagonal: macroquad.text.atlas uses a module listed above it, which is the healthy direction.
10→15 macroquad.text.atlas uses macroquad.texture part of a loop✕
- Connections
- 1 pair of types, where a type in macroquad.text.atlas uses a type in macroquad.texture.
- The types involved
macroquad.text.atlas.Atlas→macroquad.texture.Image
- Direction
- macroquad.text.atlas uses macroquad.texture, so a change to macroquad.texture can break macroquad.text.atlas, while a change to macroquad.text.atlas can't break macroquad.texture.
- 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.
11→2 macroquad.ui.cursor uses macroquad.math.rect✕
- Connections
- 2 pairs of types, where a type in macroquad.ui.cursor uses a type in macroquad.math.rect.
- The types involved
macroquad.ui.cursor.Cursor→macroquad.math.rect.Rectmacroquad.ui.cursor.Scroll→macroquad.math.rect.Rect
- Direction
- macroquad.ui.cursor uses macroquad.math.rect, so a change to macroquad.math.rect can break macroquad.ui.cursor, while a change to macroquad.ui.cursor can't break macroquad.math.rect.
- Position
- Below the diagonal: macroquad.ui.cursor uses a module listed above it, which is the healthy direction.
12→4 macroquad.ui.key_repeat uses macroquad.ui.input_handler✕
- Connections
- 1 pair of types, where a type in macroquad.ui.key_repeat uses a type in macroquad.ui.input_handler.
- The types involved
macroquad.ui.key_repeat.KeyRepeat→macroquad.ui.input_handler.KeyCode
- Direction
- macroquad.ui.key_repeat uses macroquad.ui.input_handler, so a change to macroquad.ui.input_handler can break macroquad.ui.key_repeat, while a change to macroquad.ui.key_repeat can't break macroquad.ui.input_handler.
- Position
- Below the diagonal: macroquad.ui.key_repeat uses a module listed above it, which is the healthy direction.
13→5 macroquad.audio.dummy_audio uses macroquad.audio✕
- Connections
- 1 pair of types, where a type in macroquad.audio.dummy_audio uses a type in macroquad.audio.
- The types involved
macroquad.audio.dummy_audio.Sound→macroquad.audio.PlaySoundParams
- Direction
- macroquad.audio.dummy_audio uses macroquad.audio, so a change to macroquad.audio can break macroquad.audio.dummy_audio, while a change to macroquad.audio.dummy_audio can't break macroquad.audio.
- Position
- Below the diagonal: macroquad.audio.dummy_audio uses a module listed above it, which is the healthy direction.
14→1 macroquad.text uses macroquad.color✕
- Connections
- 2 pairs of types, where a type in macroquad.text uses a type in macroquad.color.
- The types involved
macroquad.text.TextParams→macroquad.color.Colormacroquad.text.text$module→macroquad.color.Color
- Direction
- macroquad.text uses macroquad.color, so a change to macroquad.color can break macroquad.text, while a change to macroquad.text can't break macroquad.color.
- Position
- Below the diagonal: macroquad.text uses a module listed above it, which is the healthy direction.
14→10 macroquad.text uses macroquad.text.atlas✕
- Connections
- 2 pairs of types, where a type in macroquad.text uses a type in macroquad.text.atlas.
- The types involved
macroquad.text.CharacterInfo→macroquad.text.atlas.SpriteKeymacroquad.text.Font→macroquad.text.atlas.Atlas
- Direction
- macroquad.text uses macroquad.text.atlas, so a change to macroquad.text.atlas can break macroquad.text, while a change to macroquad.text can't break macroquad.text.atlas.
- Position
- Below the diagonal: macroquad.text uses a module listed above it, which is the healthy direction.
15→1 macroquad.texture uses macroquad.color✕
- Connections
- 2 pairs of types, where a type in macroquad.texture uses a type in macroquad.color.
- The types involved
macroquad.texture.Image→macroquad.color.Colormacroquad.texture.texture$module→macroquad.color.Color
- Direction
- macroquad.texture uses macroquad.color, so a change to macroquad.color can break macroquad.texture, while a change to macroquad.texture can't break macroquad.color.
- Position
- Below the diagonal: macroquad.texture uses a module listed above it, which is the healthy direction.
15→2 macroquad.texture uses macroquad.math.rect✕
- Connections
- 2 pairs of types, where a type in macroquad.texture uses a type in macroquad.math.rect.
- The types involved
macroquad.texture.DrawTextureParams→macroquad.math.rect.Rectmacroquad.texture.Image→macroquad.math.rect.Rect
- Direction
- macroquad.texture uses macroquad.math.rect, so a change to macroquad.math.rect can break macroquad.texture, while a change to macroquad.texture can't break macroquad.math.rect.
- Position
- Below the diagonal: macroquad.texture uses a module listed above it, which is the healthy direction.
15→10 macroquad.texture uses macroquad.text.atlas✕
- Connections
- 1 pair of types, where a type in macroquad.texture uses a type in macroquad.text.atlas.
- The types involved
macroquad.texture.Batcher→macroquad.text.atlas.Atlas
- Direction
- macroquad.texture uses macroquad.text.atlas, so a change to macroquad.text.atlas can break macroquad.texture, while a change to macroquad.texture can't break macroquad.text.atlas.
- Position
- Below the diagonal: macroquad.texture uses a module listed above it, which is the healthy direction.
15→36 macroquad.texture uses macroquad part of a loop✕
- Connections
- 1 pair of types, where a type in macroquad.texture uses a type in macroquad.
- The types involved
macroquad.texture.TexturesContext→macroquad.Context
- Direction
- macroquad.texture uses macroquad, so a change to macroquad can break macroquad.texture, while a change to macroquad.texture can't break macroquad.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→2 macroquad.camera uses macroquad.math.rect✕
- Connections
- 1 pair of types, where a type in macroquad.camera uses a type in macroquad.math.rect.
- The types involved
macroquad.camera.Camera2D→macroquad.math.rect.Rect
- Direction
- macroquad.camera uses macroquad.math.rect, so a change to macroquad.math.rect can break macroquad.camera, while a change to macroquad.camera can't break macroquad.math.rect.
- Position
- Below the diagonal: macroquad.camera uses a module listed above it, which is the healthy direction.
16→15 macroquad.camera uses macroquad.texture✕
- Connections
- 6 pairs of types, where a type in macroquad.camera uses a type in macroquad.texture.
- The types involved
macroquad.camera.Camera→macroquad.texture.RenderPassmacroquad.camera.Camera2D→macroquad.texture.RenderPassmacroquad.camera.Camera2D→macroquad.texture.RenderTargetmacroquad.camera.Camera3D→macroquad.texture.RenderPassmacroquad.camera.Camera3D→macroquad.texture.RenderTargetmacroquad.camera.CameraState→macroquad.texture.RenderPass
- Direction
- macroquad.camera uses macroquad.texture, so a change to macroquad.texture can break macroquad.camera, while a change to macroquad.camera can't break macroquad.texture.
- Position
- Below the diagonal: macroquad.camera uses a module listed above it, which is the healthy direction.
17→1 macroquad.models uses macroquad.color✕
- Connections
- 2 pairs of types, where a type in macroquad.models uses a type in macroquad.color.
- The types involved
macroquad.models.Vertex→macroquad.color.Colormacroquad.models.models$module→macroquad.color.Color
- Direction
- macroquad.models uses macroquad.color, so a change to macroquad.color can break macroquad.models, while a change to macroquad.models can't break macroquad.color.
- Position
- Below the diagonal: macroquad.models uses a module listed above it, which is the healthy direction.
17→15 macroquad.models uses macroquad.texture✕
- Connections
- 2 pairs of types, where a type in macroquad.models uses a type in macroquad.texture.
- The types involved
macroquad.models.Mesh→macroquad.texture.Texture2Dmacroquad.models.models$module→macroquad.texture.Texture2D
- Direction
- macroquad.models uses macroquad.texture, so a change to macroquad.texture can break macroquad.models, while a change to macroquad.models can't break macroquad.texture.
- Position
- Below the diagonal: macroquad.models uses a module listed above it, which is the healthy direction.
17→22 macroquad.models uses macroquad.quad_gl part of a loop✕
- Connections
- 2 pairs of types, where a type in macroquad.models uses a type in macroquad.quad_gl.
- The types involved
macroquad.models.DrawCylinderParams→macroquad.quad_gl.DrawModemacroquad.models.DrawSphereParams→macroquad.quad_gl.DrawMode
- Direction
- macroquad.models uses macroquad.quad_gl, so a change to macroquad.quad_gl can break macroquad.models, while a change to macroquad.models can't break macroquad.quad_gl.
- 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.
18→1 macroquad.ui.canvas uses macroquad.color✕
- Connections
- 1 pair of types, where a type in macroquad.ui.canvas uses a type in macroquad.color.
- The types involved
macroquad.ui.canvas.DrawCanvas→macroquad.color.Color
- Direction
- macroquad.ui.canvas uses macroquad.color, so a change to macroquad.color can break macroquad.ui.canvas, while a change to macroquad.ui.canvas can't break macroquad.color.
- Position
- Below the diagonal: macroquad.ui.canvas uses a module listed above it, which is the healthy direction.
18→2 macroquad.ui.canvas uses macroquad.math.rect✕
- Connections
- 1 pair of types, where a type in macroquad.ui.canvas uses a type in macroquad.math.rect.
- The types involved
macroquad.ui.canvas.DrawCanvas→macroquad.math.rect.Rect
- Direction
- macroquad.ui.canvas uses macroquad.math.rect, so a change to macroquad.math.rect can break macroquad.ui.canvas, while a change to macroquad.ui.canvas can't break macroquad.math.rect.
- Position
- Below the diagonal: macroquad.ui.canvas uses a module listed above it, which is the healthy direction.
18→15 macroquad.ui.canvas uses macroquad.texture✕
- Connections
- 1 pair of types, where a type in macroquad.ui.canvas uses a type in macroquad.texture.
- The types involved
macroquad.ui.canvas.DrawCanvas→macroquad.texture.Texture2D
- Direction
- macroquad.ui.canvas uses macroquad.texture, so a change to macroquad.texture can break macroquad.ui.canvas, while a change to macroquad.ui.canvas can't break macroquad.texture.
- Position
- Below the diagonal: macroquad.ui.canvas uses a module listed above it, which is the healthy direction.
18→29 macroquad.ui.canvas uses macroquad.ui part of a loop✕
- Connections
- 1 pair of types, where a type in macroquad.ui.canvas uses a type in macroquad.ui.
- The types involved
macroquad.ui.canvas.DrawCanvas→macroquad.ui.WindowContext
- Direction
- macroquad.ui.canvas uses macroquad.ui, so a change to macroquad.ui can break macroquad.ui.canvas, while a change to macroquad.ui.canvas can't break macroquad.ui.
- 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.
19→1 macroquad.ui.style uses macroquad.color✕
- Connections
- 2 pairs of types, where a type in macroquad.ui.style uses a type in macroquad.color.
- The types involved
macroquad.ui.style.Style→macroquad.color.Colormacroquad.ui.style.StyleBuilder→macroquad.color.Color
- Direction
- macroquad.ui.style uses macroquad.color, so a change to macroquad.color can break macroquad.ui.style, while a change to macroquad.ui.style can't break macroquad.color.
- Position
- Below the diagonal: macroquad.ui.style uses a module listed above it, which is the healthy direction.
19→2 macroquad.ui.style uses macroquad.math.rect✕
- Connections
- 2 pairs of types, where a type in macroquad.ui.style uses a type in macroquad.math.rect.
- The types involved
macroquad.ui.style.Style→macroquad.math.rect.RectOffsetmacroquad.ui.style.StyleBuilder→macroquad.math.rect.RectOffset
- Direction
- macroquad.ui.style uses macroquad.math.rect, so a change to macroquad.math.rect can break macroquad.ui.style, while a change to macroquad.ui.style can't break macroquad.math.rect.
- Position
- Below the diagonal: macroquad.ui.style uses a module listed above it, which is the healthy direction.
19→10 macroquad.ui.style uses macroquad.text.atlas✕
- Connections
- 3 pairs of types, where a type in macroquad.ui.style uses a type in macroquad.text.atlas.
- The types involved
macroquad.ui.style.Skin→macroquad.text.atlas.Atlasmacroquad.ui.style.Style→macroquad.text.atlas.SpriteKeymacroquad.ui.style.StyleBuilder→macroquad.text.atlas.Atlas
- Direction
- macroquad.ui.style uses macroquad.text.atlas, so a change to macroquad.text.atlas can break macroquad.ui.style, while a change to macroquad.ui.style can't break macroquad.text.atlas.
- Position
- Below the diagonal: macroquad.ui.style uses a module listed above it, which is the healthy direction.
19→14 macroquad.ui.style uses macroquad.text✕
- Connections
- 3 pairs of types, where a type in macroquad.ui.style uses a type in macroquad.text.
- The types involved
macroquad.ui.style.Skin→macroquad.text.Fontmacroquad.ui.style.Style→macroquad.text.Fontmacroquad.ui.style.StyleBuilder→macroquad.text.Font
- Direction
- macroquad.ui.style uses macroquad.text, so a change to macroquad.text can break macroquad.ui.style, while a change to macroquad.ui.style can't break macroquad.text.
- Position
- Below the diagonal: macroquad.ui.style uses a module listed above it, which is the healthy direction.
19→15 macroquad.ui.style uses macroquad.texture✕
- Connections
- 1 pair of types, where a type in macroquad.ui.style uses a type in macroquad.texture.
- The types involved
macroquad.ui.style.StyleBuilder→macroquad.texture.Image
- Direction
- macroquad.ui.style uses macroquad.texture, so a change to macroquad.texture can break macroquad.ui.style, while a change to macroquad.ui.style can't break macroquad.texture.
- Position
- Below the diagonal: macroquad.ui.style uses a module listed above it, which is the healthy direction.
19→23 macroquad.ui.style uses macroquad.ui.render.painter part of a loop✕
- Connections
- 1 pair of types, where a type in macroquad.ui.style uses a type in macroquad.ui.render.painter.
- The types involved
macroquad.ui.style.Style→macroquad.ui.render.painter.ElementState
- Direction
- macroquad.ui.style uses macroquad.ui.render.painter, so a change to macroquad.ui.render.painter can break macroquad.ui.style, while a change to macroquad.ui.style can't break macroquad.ui.render.painter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→2 macroquad_tiled uses macroquad.math.rect✕
- Connections
- 3 pairs of types, where a type in macroquad_tiled uses a type in macroquad.math.rect.
- The types involved
macroquad_tiled.Map→macroquad.math.rect.Rectmacroquad_tiled.TileSet→macroquad.math.rect.Rectmacroquad_tiled.TilesIterator→macroquad.math.rect.Rect
- Direction
- macroquad_tiled uses macroquad.math.rect, so a change to macroquad.math.rect can break macroquad_tiled, while a change to macroquad_tiled can't break macroquad.math.rect.
- Position
- Below the diagonal: macroquad_tiled uses a module listed above it, which is the healthy direction.
20→15 macroquad_tiled uses macroquad.texture✕
- Connections
- 2 pairs of types, where a type in macroquad_tiled uses a type in macroquad.texture.
- The types involved
macroquad_tiled.Layer→macroquad.texture.Texture2Dmacroquad_tiled.TileSet→macroquad.texture.Texture2D
- Direction
- macroquad_tiled uses macroquad.texture, so a change to macroquad.texture can break macroquad_tiled, while a change to macroquad_tiled can't break macroquad.texture.
- Position
- Below the diagonal: macroquad_tiled uses a module listed above it, which is the healthy direction.
21→8 macroquad.experimental.scene uses macroquad.experimental.scene.arena✕
- Connections
- 1 pair of types, where a type in macroquad.experimental.scene uses a type in macroquad.experimental.scene.arena.
- The types involved
macroquad.experimental.scene.Scene→macroquad.experimental.scene.arena.Arena
- Direction
- macroquad.experimental.scene uses macroquad.experimental.scene.arena, so a change to macroquad.experimental.scene.arena can break macroquad.experimental.scene, while a change to macroquad.experimental.scene can't break macroquad.experimental.scene.arena.
- Position
- Below the diagonal: macroquad.experimental.scene uses a module listed above it, which is the healthy direction.
21→16 macroquad.experimental.scene uses macroquad.camera✕
- Connections
- 1 pair of types, where a type in macroquad.experimental.scene uses a type in macroquad.camera.
- The types involved
macroquad.experimental.scene.scene$module→macroquad.camera.Camera2D
- Direction
- macroquad.experimental.scene uses macroquad.camera, so a change to macroquad.camera can break macroquad.experimental.scene, while a change to macroquad.experimental.scene can't break macroquad.camera.
- Position
- Below the diagonal: macroquad.experimental.scene uses a module listed above it, which is the healthy direction.
22→1 macroquad.quad_gl uses macroquad.color✕
- Connections
- 1 pair of types, where a type in macroquad.quad_gl uses a type in macroquad.color.
- The types involved
macroquad.quad_gl.QuadGl→macroquad.color.Color
- Direction
- macroquad.quad_gl uses macroquad.color, so a change to macroquad.color can break macroquad.quad_gl, while a change to macroquad.quad_gl can't break macroquad.color.
- Position
- Below the diagonal: macroquad.quad_gl uses a module listed above it, which is the healthy direction.
22→15 macroquad.quad_gl uses macroquad.texture✕
- Connections
- 5 pairs of types, where a type in macroquad.quad_gl uses a type in macroquad.texture.
- The types involved
macroquad.quad_gl.DrawCall→macroquad.texture.RenderPassmacroquad.quad_gl.GlState→macroquad.texture.RenderPassmacroquad.quad_gl.MagicSnapshotter→macroquad.texture.RenderPassmacroquad.quad_gl.QuadGl→macroquad.texture.RenderPassmacroquad.quad_gl.QuadGl→macroquad.texture.Texture2D
- Direction
- macroquad.quad_gl uses macroquad.texture, so a change to macroquad.texture can break macroquad.quad_gl, while a change to macroquad.quad_gl can't break macroquad.texture.
- Position
- Below the diagonal: macroquad.quad_gl uses a module listed above it, which is the healthy direction.
22→17 macroquad.quad_gl uses macroquad.models✕
- Connections
- 1 pair of types, where a type in macroquad.quad_gl uses a type in macroquad.models.
- The types involved
macroquad.quad_gl.QuadGl→macroquad.models.Vertex
- Direction
- macroquad.quad_gl uses macroquad.models, so a change to macroquad.models can break macroquad.quad_gl, while a change to macroquad.quad_gl can't break macroquad.models.
- Position
- Below the diagonal: macroquad.quad_gl uses a module listed above it, which is the healthy direction.
23→1 macroquad.ui.render.painter uses macroquad.color✕
- Connections
- 2 pairs of types, where a type in macroquad.ui.render.painter uses a type in macroquad.color.
- The types involved
macroquad.ui.render.painter.LabelParams→macroquad.color.Colormacroquad.ui.render.painter.Painter→macroquad.color.Color
- Direction
- macroquad.ui.render.painter uses macroquad.color, so a change to macroquad.color can break macroquad.ui.render.painter, while a change to macroquad.ui.render.painter can't break macroquad.color.
- Position
- Below the diagonal: macroquad.ui.render.painter uses a module listed above it, which is the healthy direction.
23→2 macroquad.ui.render.painter uses macroquad.math.rect✕
- Connections
- 2 pairs of types, where a type in macroquad.ui.render.painter uses a type in macroquad.math.rect.
- The types involved
macroquad.ui.render.painter.Painter→macroquad.math.rect.Rectmacroquad.ui.render.painter.Painter→macroquad.math.rect.RectOffset
- Direction
- macroquad.ui.render.painter uses macroquad.math.rect, so a change to macroquad.math.rect can break macroquad.ui.render.painter, while a change to macroquad.ui.render.painter can't break macroquad.math.rect.
- Position
- Below the diagonal: macroquad.ui.render.painter uses a module listed above it, which is the healthy direction.
23→10 macroquad.ui.render.painter uses macroquad.text.atlas✕
- Connections
- 2 pairs of types, where a type in macroquad.ui.render.painter uses a type in macroquad.text.atlas.
- The types involved
macroquad.ui.render.painter.Painter→macroquad.text.atlas.Atlasmacroquad.ui.render.painter.Painter→macroquad.text.atlas.SpriteKey
- Direction
- macroquad.ui.render.painter uses macroquad.text.atlas, so a change to macroquad.text.atlas can break macroquad.ui.render.painter, while a change to macroquad.ui.render.painter can't break macroquad.text.atlas.
- Position
- Below the diagonal: macroquad.ui.render.painter uses a module listed above it, which is the healthy direction.
23→14 macroquad.ui.render.painter uses macroquad.text✕
- Connections
- 2 pairs of types, where a type in macroquad.ui.render.painter uses a type in macroquad.text.
- The types involved
macroquad.ui.render.painter.Painter→macroquad.text.Fontmacroquad.ui.render.painter.Painter→macroquad.text.TextDimensions
- Direction
- macroquad.ui.render.painter uses macroquad.text, so a change to macroquad.text can break macroquad.ui.render.painter, while a change to macroquad.ui.render.painter can't break macroquad.text.
- Position
- Below the diagonal: macroquad.ui.render.painter uses a module listed above it, which is the healthy direction.
23→15 macroquad.ui.render.painter uses macroquad.texture✕
- Connections
- 1 pair of types, where a type in macroquad.ui.render.painter uses a type in macroquad.texture.
- The types involved
macroquad.ui.render.painter.Painter→macroquad.texture.Texture2D
- Direction
- macroquad.ui.render.painter uses macroquad.texture, so a change to macroquad.texture can break macroquad.ui.render.painter, while a change to macroquad.ui.render.painter can't break macroquad.texture.
- Position
- Below the diagonal: macroquad.ui.render.painter uses a module listed above it, which is the healthy direction.
23→19 macroquad.ui.render.painter uses macroquad.ui.style✕
- Connections
- 1 pair of types, where a type in macroquad.ui.render.painter uses a type in macroquad.ui.style.
- The types involved
macroquad.ui.render.painter.Painter→macroquad.ui.style.Style
- Direction
- macroquad.ui.render.painter uses macroquad.ui.style, so a change to macroquad.ui.style can break macroquad.ui.render.painter, while a change to macroquad.ui.render.painter can't break macroquad.ui.style.
- Position
- Below the diagonal: macroquad.ui.render.painter uses a module listed above it, which is the healthy direction.
23→29 macroquad.ui.render.painter uses macroquad.ui part of a loop✕
- Connections
- 1 pair of types, where a type in macroquad.ui.render.painter uses a type in macroquad.ui.
- The types involved
macroquad.ui.render.painter.Painter→macroquad.ui.UiContent
- Direction
- macroquad.ui.render.painter uses macroquad.ui, so a change to macroquad.ui can break macroquad.ui.render.painter, while a change to macroquad.ui.render.painter can't break macroquad.ui.
- 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.
24→7 macroquad.experimental.state_machine uses macroquad.experimental.coroutines✕
- Connections
- 1 pair of types, where a type in macroquad.experimental.state_machine uses a type in macroquad.experimental.coroutines.
- The types involved
macroquad.experimental.state_machine.StateMachineOwned→macroquad.experimental.coroutines.Coroutine
- Direction
- macroquad.experimental.state_machine uses macroquad.experimental.coroutines, so a change to macroquad.experimental.coroutines can break macroquad.experimental.state_machine, while a change to macroquad.experimental.state_machine can't break macroquad.experimental.coroutines.
- Position
- Below the diagonal: macroquad.experimental.state_machine uses a module listed above it, which is the healthy direction.
24→21 macroquad.experimental.state_machine uses macroquad.experimental.scene✕
- Connections
- 2 pairs of types, where a type in macroquad.experimental.state_machine uses a type in macroquad.experimental.scene.
- The types involved
macroquad.experimental.state_machine.StateMachine→macroquad.experimental.scene.RefMutmacroquad.experimental.state_machine.StateMachineOwned→macroquad.experimental.scene.RefMut
- Direction
- macroquad.experimental.state_machine uses macroquad.experimental.scene, so a change to macroquad.experimental.scene can break macroquad.experimental.state_machine, while a change to macroquad.experimental.state_machine can't break macroquad.experimental.scene.
- Position
- Below the diagonal: macroquad.experimental.state_machine uses a module listed above it, which is the healthy direction.
25→15 macroquad.material uses macroquad.texture✕
- Connections
- 1 pair of types, where a type in macroquad.material uses a type in macroquad.texture.
- The types involved
macroquad.material.Material→macroquad.texture.Texture2D
- Direction
- macroquad.material uses macroquad.texture, so a change to macroquad.texture can break macroquad.material, while a change to macroquad.material can't break macroquad.texture.
- Position
- Below the diagonal: macroquad.material uses a module listed above it, which is the healthy direction.
25→22 macroquad.material uses macroquad.quad_gl✕
- Connections
- 1 pair of types, where a type in macroquad.material uses a type in macroquad.quad_gl.
- The types involved
macroquad.material.GlPipelineGuarded→macroquad.quad_gl.GlPipeline
- Direction
- macroquad.material uses macroquad.quad_gl, so a change to macroquad.quad_gl can break macroquad.material, while a change to macroquad.material can't break macroquad.quad_gl.
- Position
- Below the diagonal: macroquad.material uses a module listed above it, which is the healthy direction.
26→1 macroquad.ui.render.mesh_rasterizer uses macroquad.color✕
- Connections
- 1 pair of types, where a type in macroquad.ui.render.mesh_rasterizer uses a type in macroquad.color.
- The types involved
macroquad.ui.render.mesh_rasterizer.DrawList→macroquad.color.Color
- Direction
- macroquad.ui.render.mesh_rasterizer uses macroquad.color, so a change to macroquad.color can break macroquad.ui.render.mesh_rasterizer, while a change to macroquad.ui.render.mesh_rasterizer can't break macroquad.color.
- Position
- Below the diagonal: macroquad.ui.render.mesh_rasterizer uses a module listed above it, which is the healthy direction.
26→2 macroquad.ui.render.mesh_rasterizer uses macroquad.math.rect✕
- Connections
- 2 pairs of types, where a type in macroquad.ui.render.mesh_rasterizer uses a type in macroquad.math.rect.
- The types involved
macroquad.ui.render.mesh_rasterizer.DrawList→macroquad.math.rect.Rectmacroquad.ui.render.mesh_rasterizer.DrawList→macroquad.math.rect.RectOffset
- Direction
- macroquad.ui.render.mesh_rasterizer uses macroquad.math.rect, so a change to macroquad.math.rect can break macroquad.ui.render.mesh_rasterizer, while a change to macroquad.ui.render.mesh_rasterizer can't break macroquad.math.rect.
- Position
- Below the diagonal: macroquad.ui.render.mesh_rasterizer uses a module listed above it, which is the healthy direction.
26→15 macroquad.ui.render.mesh_rasterizer uses macroquad.texture✕
- Connections
- 1 pair of types, where a type in macroquad.ui.render.mesh_rasterizer uses a type in macroquad.texture.
- The types involved
macroquad.ui.render.mesh_rasterizer.DrawList→macroquad.texture.Texture2D
- Direction
- macroquad.ui.render.mesh_rasterizer uses macroquad.texture, so a change to macroquad.texture can break macroquad.ui.render.mesh_rasterizer, while a change to macroquad.ui.render.mesh_rasterizer can't break macroquad.texture.
- Position
- Below the diagonal: macroquad.ui.render.mesh_rasterizer uses a module listed above it, which is the healthy direction.
26→17 macroquad.ui.render.mesh_rasterizer uses macroquad.models✕
- Connections
- 1 pair of types, where a type in macroquad.ui.render.mesh_rasterizer uses a type in macroquad.models.
- The types involved
macroquad.ui.render.mesh_rasterizer.DrawList→macroquad.models.Vertex
- Direction
- macroquad.ui.render.mesh_rasterizer uses macroquad.models, so a change to macroquad.models can break macroquad.ui.render.mesh_rasterizer, while a change to macroquad.ui.render.mesh_rasterizer can't break macroquad.models.
- Position
- Below the diagonal: macroquad.ui.render.mesh_rasterizer uses a module listed above it, which is the healthy direction.
26→23 macroquad.ui.render.mesh_rasterizer uses macroquad.ui.render.painter✕
- Connections
- 1 pair of types, where a type in macroquad.ui.render.mesh_rasterizer uses a type in macroquad.ui.render.painter.
- The types involved
macroquad.ui.render.mesh_rasterizer.mesh_rasterizer$module→macroquad.ui.render.painter.DrawCommand
- Direction
- macroquad.ui.render.mesh_rasterizer uses macroquad.ui.render.painter, so a change to macroquad.ui.render.painter can break macroquad.ui.render.mesh_rasterizer, while a change to macroquad.ui.render.mesh_rasterizer can't break macroquad.ui.render.painter.
- Position
- Below the diagonal: macroquad.ui.render.mesh_rasterizer uses a module listed above it, which is the healthy direction.
27→21 macroquad.ui.widgets.drag uses macroquad.experimental.scene✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.drag uses a type in macroquad.experimental.scene.
- The types involved
macroquad.ui.widgets.drag.Drag→macroquad.experimental.scene.Id
- Direction
- macroquad.ui.widgets.drag uses macroquad.experimental.scene, so a change to macroquad.experimental.scene can break macroquad.ui.widgets.drag, while a change to macroquad.ui.widgets.drag can't break macroquad.experimental.scene.
- Position
- Below the diagonal: macroquad.ui.widgets.drag uses a module listed above it, which is the healthy direction.
27→29 macroquad.ui.widgets.drag uses macroquad.ui part of a loop✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.drag uses a type in macroquad.ui.
- The types involved
macroquad.ui.widgets.drag.Drag→macroquad.ui.Ui
- Direction
- macroquad.ui.widgets.drag uses macroquad.ui, so a change to macroquad.ui can break macroquad.ui.widgets.drag, while a change to macroquad.ui.widgets.drag can't break macroquad.ui.
- 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.
28→1 macroquad_particles uses macroquad.color✕
- Connections
- 2 pairs of types, where a type in macroquad_particles uses a type in macroquad.color.
- The types involved
macroquad_particles.ColorCurve→macroquad.color.Colormacroquad_particles.ColorSerializable→macroquad.color.Color
- Direction
- macroquad_particles uses macroquad.color, so a change to macroquad.color can break macroquad_particles, while a change to macroquad_particles can't break macroquad.color.
- Position
- Below the diagonal: macroquad_particles uses a module listed above it, which is the healthy direction.
28→15 macroquad_particles uses macroquad.texture✕
- Connections
- 3 pairs of types, where a type in macroquad_particles uses a type in macroquad.texture.
- The types involved
macroquad_particles.Emitter→macroquad.texture.RenderPassmacroquad_particles.EmitterConfig→macroquad.texture.Texture2Dmacroquad_particles.ParticleShape→macroquad.texture.Texture2D
- Direction
- macroquad_particles uses macroquad.texture, so a change to macroquad.texture can break macroquad_particles, while a change to macroquad_particles can't break macroquad.texture.
- Position
- Below the diagonal: macroquad_particles uses a module listed above it, which is the healthy direction.
28→22 macroquad_particles uses macroquad.quad_gl✕
- Connections
- 1 pair of types, where a type in macroquad_particles uses a type in macroquad.quad_gl.
- The types involved
macroquad_particles.Emitter→macroquad.quad_gl.QuadGl
- Direction
- macroquad_particles uses macroquad.quad_gl, so a change to macroquad.quad_gl can break macroquad_particles, while a change to macroquad_particles can't break macroquad.quad_gl.
- Position
- Below the diagonal: macroquad_particles uses a module listed above it, which is the healthy direction.
29→2 macroquad.ui uses macroquad.math.rect✕
- Connections
- 3 pairs of types, where a type in macroquad.ui uses a type in macroquad.math.rect.
- The types involved
macroquad.ui.Window→macroquad.math.rect.Rectmacroquad.ui.Window→macroquad.math.rect.RectOffsetmacroquad.ui.WindowContext→macroquad.math.rect.Rect
- Direction
- macroquad.ui uses macroquad.math.rect, so a change to macroquad.math.rect can break macroquad.ui, while a change to macroquad.ui can't break macroquad.math.rect.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→3 macroquad.ui uses macroquad.ui.input✕
- Connections
- 3 pairs of types, where a type in macroquad.ui uses a type in macroquad.ui.input.
- The types involved
macroquad.ui.TabSelector→macroquad.ui.input.Inputmacroquad.ui.Ui→macroquad.ui.input.Inputmacroquad.ui.WindowContext→macroquad.ui.input.Input
- Direction
- macroquad.ui uses macroquad.ui.input, so a change to macroquad.ui.input can break macroquad.ui, while a change to macroquad.ui can't break macroquad.ui.input.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→4 macroquad.ui uses macroquad.ui.input_handler✕
- Connections
- 2 pairs of types, where a type in macroquad.ui uses a type in macroquad.ui.input_handler.
- The types involved
macroquad.ui.Ui→macroquad.ui.input_handler.InputHandlermacroquad.ui.Ui→macroquad.ui.input_handler.KeyCode
- Direction
- macroquad.ui uses macroquad.ui.input_handler, so a change to macroquad.ui.input_handler can break macroquad.ui, while a change to macroquad.ui can't break macroquad.ui.input_handler.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→10 macroquad.ui uses macroquad.text.atlas✕
- Connections
- 3 pairs of types, where a type in macroquad.ui uses a type in macroquad.text.atlas.
- The types involved
macroquad.ui.StyleStack→macroquad.text.atlas.Atlasmacroquad.ui.Ui→macroquad.text.atlas.Atlasmacroquad.ui.Window→macroquad.text.atlas.Atlas
- Direction
- macroquad.ui uses macroquad.text.atlas, so a change to macroquad.text.atlas can break macroquad.ui, while a change to macroquad.ui can't break macroquad.text.atlas.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→11 macroquad.ui uses macroquad.ui.cursor✕
- Connections
- 1 pair of types, where a type in macroquad.ui uses a type in macroquad.ui.cursor.
- The types involved
macroquad.ui.Window→macroquad.ui.cursor.Cursor
- Direction
- macroquad.ui uses macroquad.ui.cursor, so a change to macroquad.ui.cursor can break macroquad.ui, while a change to macroquad.ui can't break macroquad.ui.cursor.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→12 macroquad.ui uses macroquad.ui.key_repeat✕
- Connections
- 1 pair of types, where a type in macroquad.ui uses a type in macroquad.ui.key_repeat.
- The types involved
macroquad.ui.Ui→macroquad.ui.key_repeat.KeyRepeat
- Direction
- macroquad.ui uses macroquad.ui.key_repeat, so a change to macroquad.ui.key_repeat can break macroquad.ui, while a change to macroquad.ui can't break macroquad.ui.key_repeat.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→14 macroquad.ui uses macroquad.text✕
- Connections
- 2 pairs of types, where a type in macroquad.ui uses a type in macroquad.text.
- The types involved
macroquad.ui.StyleStack→macroquad.text.Fontmacroquad.ui.Ui→macroquad.text.Font
- Direction
- macroquad.ui uses macroquad.text, so a change to macroquad.text can break macroquad.ui, while a change to macroquad.ui can't break macroquad.text.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→15 macroquad.ui uses macroquad.texture✕
- Connections
- 2 pairs of types, where a type in macroquad.ui uses a type in macroquad.texture.
- The types involved
macroquad.ui.Ui→macroquad.texture.Texture2Dmacroquad.ui.UiContent→macroquad.texture.Texture2D
- Direction
- macroquad.ui uses macroquad.texture, so a change to macroquad.texture can break macroquad.ui, while a change to macroquad.ui can't break macroquad.texture.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→18 macroquad.ui uses macroquad.ui.canvas✕
- Connections
- 1 pair of types, where a type in macroquad.ui uses a type in macroquad.ui.canvas.
- The types involved
macroquad.ui.Ui→macroquad.ui.canvas.DrawCanvas
- Direction
- macroquad.ui uses macroquad.ui.canvas, so a change to macroquad.ui.canvas can break macroquad.ui, while a change to macroquad.ui can't break macroquad.ui.canvas.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→19 macroquad.ui uses macroquad.ui.style✕
- Connections
- 4 pairs of types, where a type in macroquad.ui uses a type in macroquad.ui.style.
- The types involved
macroquad.ui.StyleStack→macroquad.ui.style.Skinmacroquad.ui.Ui→macroquad.ui.style.Skinmacroquad.ui.Ui→macroquad.ui.style.StyleBuildermacroquad.ui.WindowContext→macroquad.ui.style.Skin
- Direction
- macroquad.ui uses macroquad.ui.style, so a change to macroquad.ui.style can break macroquad.ui, while a change to macroquad.ui can't break macroquad.ui.style.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→21 macroquad.ui uses macroquad.experimental.scene✕
- Connections
- 4 pairs of types, where a type in macroquad.ui uses a type in macroquad.experimental.scene.
- The types involved
macroquad.ui.AnyStorage→macroquad.experimental.scene.Idmacroquad.ui.Ui→macroquad.experimental.scene.Idmacroquad.ui.Window→macroquad.experimental.scene.Idmacroquad.ui.WindowContext→macroquad.experimental.scene.Id
- Direction
- macroquad.ui uses macroquad.experimental.scene, so a change to macroquad.experimental.scene can break macroquad.ui, while a change to macroquad.ui can't break macroquad.experimental.scene.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→23 macroquad.ui uses macroquad.ui.render.painter✕
- Connections
- 1 pair of types, where a type in macroquad.ui uses a type in macroquad.ui.render.painter.
- The types involved
macroquad.ui.Window→macroquad.ui.render.painter.Painter
- Direction
- macroquad.ui uses macroquad.ui.render.painter, so a change to macroquad.ui.render.painter can break macroquad.ui, while a change to macroquad.ui can't break macroquad.ui.render.painter.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→26 macroquad.ui uses macroquad.ui.render.mesh_rasterizer✕
- Connections
- 1 pair of types, where a type in macroquad.ui uses a type in macroquad.ui.render.mesh_rasterizer.
- The types involved
macroquad.ui.Ui→macroquad.ui.render.mesh_rasterizer.DrawList
- Direction
- macroquad.ui uses macroquad.ui.render.mesh_rasterizer, so a change to macroquad.ui.render.mesh_rasterizer can break macroquad.ui, while a change to macroquad.ui can't break macroquad.ui.render.mesh_rasterizer.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→27 macroquad.ui uses macroquad.ui.widgets.drag✕
- Connections
- 1 pair of types, where a type in macroquad.ui uses a type in macroquad.ui.widgets.drag.
- The types involved
macroquad.ui.Ui→macroquad.ui.widgets.drag.Drag
- Direction
- macroquad.ui uses macroquad.ui.widgets.drag, so a change to macroquad.ui.widgets.drag can break macroquad.ui, while a change to macroquad.ui can't break macroquad.ui.widgets.drag.
- Position
- Below the diagonal: macroquad.ui uses a module listed above it, which is the healthy direction.
29→36 macroquad.ui uses macroquad part of a loop✕
- Connections
- 3 pairs of types, where a type in macroquad.ui uses a type in macroquad.
- The types involved
macroquad.ui.Ui→macroquad.Windowmacroquad.ui.Window→macroquad.Windowmacroquad.ui.WindowContext→macroquad.Window
- Direction
- macroquad.ui uses macroquad, so a change to macroquad can break macroquad.ui, while a change to macroquad.ui can't break macroquad.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→22 macroquad.ui.ui_context uses macroquad.quad_gl✕
- Connections
- 1 pair of types, where a type in macroquad.ui.ui_context uses a type in macroquad.quad_gl.
- The types involved
macroquad.ui.ui_context.UiContext→macroquad.quad_gl.QuadGl
- Direction
- macroquad.ui.ui_context uses macroquad.quad_gl, so a change to macroquad.quad_gl can break macroquad.ui.ui_context, while a change to macroquad.ui.ui_context can't break macroquad.quad_gl.
- Position
- Below the diagonal: macroquad.ui.ui_context uses a module listed above it, which is the healthy direction.
30→25 macroquad.ui.ui_context uses macroquad.material✕
- Connections
- 1 pair of types, where a type in macroquad.ui.ui_context uses a type in macroquad.material.
- The types involved
macroquad.ui.ui_context.UiContext→macroquad.material.Material
- Direction
- macroquad.ui.ui_context uses macroquad.material, so a change to macroquad.material can break macroquad.ui.ui_context, while a change to macroquad.ui.ui_context can't break macroquad.material.
- Position
- Below the diagonal: macroquad.ui.ui_context uses a module listed above it, which is the healthy direction.
30→26 macroquad.ui.ui_context uses macroquad.ui.render.mesh_rasterizer✕
- Connections
- 1 pair of types, where a type in macroquad.ui.ui_context uses a type in macroquad.ui.render.mesh_rasterizer.
- The types involved
macroquad.ui.ui_context.UiContext→macroquad.ui.render.mesh_rasterizer.DrawList
- Direction
- macroquad.ui.ui_context uses macroquad.ui.render.mesh_rasterizer, so a change to macroquad.ui.render.mesh_rasterizer can break macroquad.ui.ui_context, while a change to macroquad.ui.ui_context can't break macroquad.ui.render.mesh_rasterizer.
- Position
- Below the diagonal: macroquad.ui.ui_context uses a module listed above it, which is the healthy direction.
30→29 macroquad.ui.ui_context uses macroquad.ui✕
- Connections
- 1 pair of types, where a type in macroquad.ui.ui_context uses a type in macroquad.ui.
- The types involved
macroquad.ui.ui_context.UiContext→macroquad.ui.Ui
- Direction
- macroquad.ui.ui_context uses macroquad.ui, so a change to macroquad.ui can break macroquad.ui.ui_context, while a change to macroquad.ui.ui_context can't break macroquad.ui.
- Position
- Below the diagonal: macroquad.ui.ui_context uses a module listed above it, which is the healthy direction.
31→21 macroquad.ui.widgets.checkbox uses macroquad.experimental.scene✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.checkbox uses a type in macroquad.experimental.scene.
- The types involved
macroquad.ui.widgets.checkbox.Checkbox→macroquad.experimental.scene.Id
- Direction
- macroquad.ui.widgets.checkbox uses macroquad.experimental.scene, so a change to macroquad.experimental.scene can break macroquad.ui.widgets.checkbox, while a change to macroquad.ui.widgets.checkbox can't break macroquad.experimental.scene.
- Position
- Below the diagonal: macroquad.ui.widgets.checkbox uses a module listed above it, which is the healthy direction.
31→29 macroquad.ui.widgets.checkbox uses macroquad.ui✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.checkbox uses a type in macroquad.ui.
- The types involved
macroquad.ui.widgets.checkbox.Checkbox→macroquad.ui.Ui
- Direction
- macroquad.ui.widgets.checkbox uses macroquad.ui, so a change to macroquad.ui can break macroquad.ui.widgets.checkbox, while a change to macroquad.ui.widgets.checkbox can't break macroquad.ui.
- Position
- Below the diagonal: macroquad.ui.widgets.checkbox uses a module listed above it, which is the healthy direction.
32→21 macroquad.ui.widgets.combobox uses macroquad.experimental.scene✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.combobox uses a type in macroquad.experimental.scene.
- The types involved
macroquad.ui.widgets.combobox.ComboBox→macroquad.experimental.scene.Id
- Direction
- macroquad.ui.widgets.combobox uses macroquad.experimental.scene, so a change to macroquad.experimental.scene can break macroquad.ui.widgets.combobox, while a change to macroquad.ui.widgets.combobox can't break macroquad.experimental.scene.
- Position
- Below the diagonal: macroquad.ui.widgets.combobox uses a module listed above it, which is the healthy direction.
32→29 macroquad.ui.widgets.combobox uses macroquad.ui✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.combobox uses a type in macroquad.ui.
- The types involved
macroquad.ui.widgets.combobox.ComboBox→macroquad.ui.Ui
- Direction
- macroquad.ui.widgets.combobox uses macroquad.ui, so a change to macroquad.ui can break macroquad.ui.widgets.combobox, while a change to macroquad.ui.widgets.combobox can't break macroquad.ui.
- Position
- Below the diagonal: macroquad.ui.widgets.combobox uses a module listed above it, which is the healthy direction.
33→3 macroquad.ui.widgets.editbox uses macroquad.ui.input✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.editbox uses a type in macroquad.ui.input.
- The types involved
macroquad.ui.widgets.editbox.Editbox→macroquad.ui.input.InputCharacter
- Direction
- macroquad.ui.widgets.editbox uses macroquad.ui.input, so a change to macroquad.ui.input can break macroquad.ui.widgets.editbox, while a change to macroquad.ui.widgets.editbox can't break macroquad.ui.input.
- Position
- Below the diagonal: macroquad.ui.widgets.editbox uses a module listed above it, which is the healthy direction.
33→21 macroquad.ui.widgets.editbox uses macroquad.experimental.scene✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.editbox uses a type in macroquad.experimental.scene.
- The types involved
macroquad.ui.widgets.editbox.Editbox→macroquad.experimental.scene.Id
- Direction
- macroquad.ui.widgets.editbox uses macroquad.experimental.scene, so a change to macroquad.experimental.scene can break macroquad.ui.widgets.editbox, while a change to macroquad.ui.widgets.editbox can't break macroquad.experimental.scene.
- Position
- Below the diagonal: macroquad.ui.widgets.editbox uses a module listed above it, which is the healthy direction.
33→29 macroquad.ui.widgets.editbox uses macroquad.ui✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.editbox uses a type in macroquad.ui.
- The types involved
macroquad.ui.widgets.editbox.Editbox→macroquad.ui.Ui
- Direction
- macroquad.ui.widgets.editbox uses macroquad.ui, so a change to macroquad.ui can break macroquad.ui.widgets.editbox, while a change to macroquad.ui.widgets.editbox can't break macroquad.ui.
- Position
- Below the diagonal: macroquad.ui.widgets.editbox uses a module listed above it, which is the healthy direction.
34→11 macroquad.ui.widgets.group uses macroquad.ui.cursor✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.group uses a type in macroquad.ui.cursor.
- The types involved
macroquad.ui.widgets.group.Group→macroquad.ui.cursor.Layout
- Direction
- macroquad.ui.widgets.group uses macroquad.ui.cursor, so a change to macroquad.ui.cursor can break macroquad.ui.widgets.group, while a change to macroquad.ui.widgets.group can't break macroquad.ui.cursor.
- Position
- Below the diagonal: macroquad.ui.widgets.group uses a module listed above it, which is the healthy direction.
34→21 macroquad.ui.widgets.group uses macroquad.experimental.scene✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.group uses a type in macroquad.experimental.scene.
- The types involved
macroquad.ui.widgets.group.Group→macroquad.experimental.scene.Id
- Direction
- macroquad.ui.widgets.group uses macroquad.experimental.scene, so a change to macroquad.experimental.scene can break macroquad.ui.widgets.group, while a change to macroquad.ui.widgets.group can't break macroquad.experimental.scene.
- Position
- Below the diagonal: macroquad.ui.widgets.group uses a module listed above it, which is the healthy direction.
34→27 macroquad.ui.widgets.group uses macroquad.ui.widgets.drag✕
- Connections
- 2 pairs of types, where a type in macroquad.ui.widgets.group uses a type in macroquad.ui.widgets.drag.
- The types involved
macroquad.ui.widgets.group.Group→macroquad.ui.widgets.drag.Dragmacroquad.ui.widgets.group.GroupToken→macroquad.ui.widgets.drag.Drag
- Direction
- macroquad.ui.widgets.group uses macroquad.ui.widgets.drag, so a change to macroquad.ui.widgets.drag can break macroquad.ui.widgets.group, while a change to macroquad.ui.widgets.group can't break macroquad.ui.widgets.drag.
- Position
- Below the diagonal: macroquad.ui.widgets.group uses a module listed above it, which is the healthy direction.
34→29 macroquad.ui.widgets.group uses macroquad.ui✕
- Connections
- 2 pairs of types, where a type in macroquad.ui.widgets.group uses a type in macroquad.ui.
- The types involved
macroquad.ui.widgets.group.Group→macroquad.ui.Uimacroquad.ui.widgets.group.GroupToken→macroquad.ui.Ui
- Direction
- macroquad.ui.widgets.group uses macroquad.ui, so a change to macroquad.ui can break macroquad.ui.widgets.group, while a change to macroquad.ui.widgets.group can't break macroquad.ui.
- Position
- Below the diagonal: macroquad.ui.widgets.group uses a module listed above it, which is the healthy direction.
35→21 macroquad.ui.widgets.input uses macroquad.experimental.scene✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.input uses a type in macroquad.experimental.scene.
- The types involved
macroquad.ui.widgets.input.InputText→macroquad.experimental.scene.Id
- Direction
- macroquad.ui.widgets.input uses macroquad.experimental.scene, so a change to macroquad.experimental.scene can break macroquad.ui.widgets.input, while a change to macroquad.ui.widgets.input can't break macroquad.experimental.scene.
- Position
- Below the diagonal: macroquad.ui.widgets.input uses a module listed above it, which is the healthy direction.
35→29 macroquad.ui.widgets.input uses macroquad.ui✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.input uses a type in macroquad.ui.
- The types involved
macroquad.ui.widgets.input.InputText→macroquad.ui.Ui
- Direction
- macroquad.ui.widgets.input uses macroquad.ui, so a change to macroquad.ui can break macroquad.ui.widgets.input, while a change to macroquad.ui.widgets.input can't break macroquad.ui.
- Position
- Below the diagonal: macroquad.ui.widgets.input uses a module listed above it, which is the healthy direction.
36→4 macroquad uses macroquad.ui.input_handler✕
- Connections
- 1 pair of types, where a type in macroquad uses a type in macroquad.ui.input_handler.
- The types involved
macroquad.Stage→macroquad.ui.input_handler.KeyCode
- Direction
- macroquad uses macroquad.ui.input_handler, so a change to macroquad.ui.input_handler can break macroquad, while a change to macroquad can't break macroquad.ui.input_handler.
- Position
- Below the diagonal: macroquad uses a module listed above it, which is the healthy direction.
36→6 macroquad uses macroquad.conf✕
- Connections
- 1 pair of types, where a type in macroquad uses a type in macroquad.conf.
- The types involved
macroquad.Context→macroquad.conf.UpdateTrigger
- Direction
- macroquad uses macroquad.conf, so a change to macroquad.conf can break macroquad, while a change to macroquad can't break macroquad.conf.
- Position
- Below the diagonal: macroquad uses a module listed above it, which is the healthy direction.
36→7 macroquad uses macroquad.experimental.coroutines✕
- Connections
- 1 pair of types, where a type in macroquad uses a type in macroquad.experimental.coroutines.
- The types involved
macroquad.Context→macroquad.experimental.coroutines.CoroutinesContext
- Direction
- macroquad uses macroquad.experimental.coroutines, so a change to macroquad.experimental.coroutines can break macroquad, while a change to macroquad can't break macroquad.experimental.coroutines.
- Position
- Below the diagonal: macroquad uses a module listed above it, which is the healthy direction.
36→9 macroquad uses macroquad.input✕
- Connections
- 1 pair of types, where a type in macroquad uses a type in macroquad.input.
- The types involved
macroquad.Stage→macroquad.input.TouchPhase
- Direction
- macroquad uses macroquad.input, so a change to macroquad.input can break macroquad, while a change to macroquad can't break macroquad.input.
- Position
- Below the diagonal: macroquad uses a module listed above it, which is the healthy direction.
36→13 macroquad uses macroquad.audio.dummy_audio✕
- Connections
- 1 pair of types, where a type in macroquad uses a type in macroquad.audio.dummy_audio.
- The types involved
macroquad.Context→macroquad.audio.dummy_audio.AudioContext
- Direction
- macroquad uses macroquad.audio.dummy_audio, so a change to macroquad.audio.dummy_audio can break macroquad, while a change to macroquad can't break macroquad.audio.dummy_audio.
- Position
- Below the diagonal: macroquad uses a module listed above it, which is the healthy direction.
36→14 macroquad uses macroquad.text✕
- Connections
- 1 pair of types, where a type in macroquad uses a type in macroquad.text.
- The types involved
macroquad.Context→macroquad.text.FontsStorage
- Direction
- macroquad uses macroquad.text, so a change to macroquad.text can break macroquad, while a change to macroquad can't break macroquad.text.
- Position
- Below the diagonal: macroquad uses a module listed above it, which is the healthy direction.
36→15 macroquad uses macroquad.texture✕
- Connections
- 3 pairs of types, where a type in macroquad uses a type in macroquad.texture.
- The types involved
macroquad.Context→macroquad.texture.Batchermacroquad.Context→macroquad.texture.TextureHandlemacroquad.Context→macroquad.texture.TexturesContext
- Direction
- macroquad uses macroquad.texture, so a change to macroquad.texture can break macroquad, while a change to macroquad can't break macroquad.texture.
- Position
- Below the diagonal: macroquad uses a module listed above it, which is the healthy direction.
36→16 macroquad uses macroquad.camera✕
- Connections
- 1 pair of types, where a type in macroquad uses a type in macroquad.camera.
- The types involved
macroquad.Context→macroquad.camera.CameraState
- Direction
- macroquad uses macroquad.camera, so a change to macroquad.camera can break macroquad, while a change to macroquad can't break macroquad.camera.
- Position
- Below the diagonal: macroquad uses a module listed above it, which is the healthy direction.
36→22 macroquad uses macroquad.quad_gl✕
- Connections
- 1 pair of types, where a type in macroquad uses a type in macroquad.quad_gl.
- The types involved
macroquad.Context→macroquad.quad_gl.QuadGl
- Direction
- macroquad uses macroquad.quad_gl, so a change to macroquad.quad_gl can break macroquad, while a change to macroquad can't break macroquad.quad_gl.
- Position
- Below the diagonal: macroquad uses a module listed above it, which is the healthy direction.
36→30 macroquad uses macroquad.ui.ui_context✕
- Connections
- 1 pair of types, where a type in macroquad uses a type in macroquad.ui.ui_context.
- The types involved
macroquad.Context→macroquad.ui.ui_context.UiContext
- Direction
- macroquad uses macroquad.ui.ui_context, so a change to macroquad.ui.ui_context can break macroquad, while a change to macroquad can't break macroquad.ui.ui_context.
- Position
- Below the diagonal: macroquad uses a module listed above it, which is the healthy direction.
37→36 macroquad.exec uses macroquad✕
- Connections
- 2 pairs of types, where a type in macroquad.exec uses a type in macroquad.
- The types involved
macroquad.exec.FileLoadingFuture→macroquad.Contextmacroquad.exec.FrameFuture→macroquad.Context
- Direction
- macroquad.exec uses macroquad, so a change to macroquad can break macroquad.exec, while a change to macroquad.exec can't break macroquad.
- Position
- Below the diagonal: macroquad.exec uses a module listed above it, which is the healthy direction.
38→21 macroquad.experimental.coroutines.tweens uses macroquad.experimental.scene✕
- Connections
- 2 pairs of types, where a type in macroquad.experimental.coroutines.tweens uses a type in macroquad.experimental.scene.
- The types involved
macroquad.experimental.coroutines.tweens.LinearTweenFuture→macroquad.experimental.scene.Lensmacroquad.experimental.coroutines.tweens.tweens$module→macroquad.experimental.scene.Handle
- Direction
- macroquad.experimental.coroutines.tweens uses macroquad.experimental.scene, so a change to macroquad.experimental.scene can break macroquad.experimental.coroutines.tweens, while a change to macroquad.experimental.coroutines.tweens can't break macroquad.experimental.scene.
- Position
- Below the diagonal: macroquad.experimental.coroutines.tweens uses a module listed above it, which is the healthy direction.
38→36 macroquad.experimental.coroutines.tweens uses macroquad✕
- Connections
- 1 pair of types, where a type in macroquad.experimental.coroutines.tweens uses a type in macroquad.
- The types involved
macroquad.experimental.coroutines.tweens.LinearTweenFuture→macroquad.Context
- Direction
- macroquad.experimental.coroutines.tweens uses macroquad, so a change to macroquad can break macroquad.experimental.coroutines.tweens, while a change to macroquad.experimental.coroutines.tweens can't break macroquad.
- Position
- Below the diagonal: macroquad.experimental.coroutines.tweens uses a module listed above it, which is the healthy direction.
39→21 macroquad.ui.widgets.window uses macroquad.experimental.scene✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.window uses a type in macroquad.experimental.scene.
- The types involved
macroquad.ui.widgets.window.Window→macroquad.experimental.scene.Id
- Direction
- macroquad.ui.widgets.window uses macroquad.experimental.scene, so a change to macroquad.experimental.scene can break macroquad.ui.widgets.window, while a change to macroquad.ui.widgets.window can't break macroquad.experimental.scene.
- Position
- Below the diagonal: macroquad.ui.widgets.window uses a module listed above it, which is the healthy direction.
39→29 macroquad.ui.widgets.window uses macroquad.ui✕
- Connections
- 3 pairs of types, where a type in macroquad.ui.widgets.window uses a type in macroquad.ui.
- The types involved
macroquad.ui.widgets.window.Window→macroquad.ui.Uimacroquad.ui.widgets.window.Window→macroquad.ui.WindowContextmacroquad.ui.widgets.window.WindowToken→macroquad.ui.Ui
- Direction
- macroquad.ui.widgets.window uses macroquad.ui, so a change to macroquad.ui can break macroquad.ui.widgets.window, while a change to macroquad.ui.widgets.window can't break macroquad.ui.
- Position
- Below the diagonal: macroquad.ui.widgets.window uses a module listed above it, which is the healthy direction.
39→36 macroquad.ui.widgets.window uses macroquad✕
- Connections
- 1 pair of types, where a type in macroquad.ui.widgets.window uses a type in macroquad.
- The types involved
macroquad.ui.widgets.window.Window→macroquad.Window
- Direction
- macroquad.ui.widgets.window uses macroquad, so a change to macroquad can break macroquad.ui.widgets.window, while a change to macroquad.ui.widgets.window can't break macroquad.
- Position
- Below the diagonal: macroquad.ui.widgets.window uses a module listed above it, which is the healthy direction.
40→1 macroquad.window uses macroquad.color✕
- Connections
- 1 pair of types, where a type in macroquad.window uses a type in macroquad.color.
- The types involved
macroquad.window.window$module→macroquad.color.Color
- Direction
- macroquad.window uses macroquad.color, so a change to macroquad.color can break macroquad.window, while a change to macroquad.window can't break macroquad.color.
- Position
- Below the diagonal: macroquad.window uses a module listed above it, which is the healthy direction.
40→22 macroquad.window uses macroquad.quad_gl✕
- Connections
- 1 pair of types, where a type in macroquad.window uses a type in macroquad.quad_gl.
- The types involved
macroquad.window.InternalGlContext→macroquad.quad_gl.QuadGl
- Direction
- macroquad.window uses macroquad.quad_gl, so a change to macroquad.quad_gl can break macroquad.window, while a change to macroquad.window can't break macroquad.quad_gl.
- Position
- Below the diagonal: macroquad.window uses a module listed above it, which is the healthy direction.
40→37 macroquad.window uses macroquad.exec✕
- Connections
- 1 pair of types, where a type in macroquad.window uses a type in macroquad.exec.
- The types involved
macroquad.window.window$module→macroquad.exec.FrameFuture
- Direction
- macroquad.window uses macroquad.exec, so a change to macroquad.exec can break macroquad.window, while a change to macroquad.window can't break macroquad.exec.
- Position
- Below the diagonal: macroquad.window uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 11 | High / Critical |
Roadmap
Top priorities: Resolve the 53 Low coverage finding(s) in Code Coverage — start with input.rs (3), texture.rs (2), window.rs (2); 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 SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 53 Low coverage finding(s) in Code Coverage — start with input.rs (3), texture.rs (2), window.rs (2). | +11.5 pts | Medium | Code Coverage |
| 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. | +8.4 pts | Medium | Architecture documentation |
| Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +6.4 pts | Medium | Security & performance tooling |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.9 pts | Medium | Release Hygiene |
| 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. | +1.7 pts | Medium | Documentation (README) |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with slotmap.rs, progress_bar.rs, mouse.rs. | +0.4 pts | Low | Knowledge Freshness |
| Run the test suite in CI via an explicit runner step (`cargo test` for the toolchain this pipeline already uses) and gate merges on it. | +0.6 pts | Medium | CI/CD gates |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.4 | Slop | Static Analysis (SAST): High: REDACTED |
| src/ui/style.rs | 5.5 | Mixed | Code Duplication: Edited copy of a member (21 corresponding lines) |
| src/ui/widgets/editbox.rs | 5.6 | Mixed | Cyclomatic Complexity: Editbox::apply_keyboard_input (cyclomatic 37) |
| src/texture.rs | 5.6 | Mixed | God Classes: FileTooLong: src/texture.rs |
| src/quad_gl.rs | 5.6 | Mixed | Cognitive Complexity: QuadGl::draw (cognitive 28) |
| src/models.rs | 5.6 | Mixed | Code Duplication: Edited copy of a member (12 corresponding lines) |
| src/ui.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| particles/src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| tiled/src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/ui/widgets/slider.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/shapes.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/ui/widgets/window.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/ui/widgets/drag.rs | 6.3 | Mixed | Cyclomatic Complexity: Drag::ui (cyclomatic 22) |
| src/ui/widgets/combobox.rs | 6.3 | Mixed | Cognitive Complexity: ComboBox::ui (cognitive 17) |
| src/camera.rs | 6.3 | Mixed | Code Duplication: Edited copy of a member (24 corresponding lines) |
| src/ui/widgets/checkbox.rs | 6.3 | Mixed | Code Duplication: Duplicated block (10–11 lines × 2) |
| src/input.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/ui/widgets/separator.rs | 6.7 | Mixed | Explicit Debt: HackComment |
| src/experimental/scene.rs | 7.0 | Near-clean | Cognitive Complexity: Scene::update (cognitive 19) |
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 36 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 — 36 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, 162 of 169 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
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- 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.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded, and the 1 JavaScript/TypeScript file(s) found looked minified or bundled, which this check does not read, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- 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.
- 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.
- 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
7 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was UiContext::process_input at 43.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with UiContext::process_input (cyclomatic 43), Editbox::apply_keyboard_input (cyclomatic 37), Editbox::ui (cyclomatic 35). — 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 7 together lifts Cyclomatic Complexity from 8.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
18 function(s) exceeded the cognitive complexity threshold of 15; the worst was Editbox::apply_keyboard_input at 68.
What to do
- Bring the 5 bodies over 30 down to 30 or less in Cognitive Complexity — start with Editbox::apply_keyboard_input (cognitive 68), Drag::ui (cognitive 53), Editbox::ui (cognitive 47). — 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 5 together lifts Cognitive Complexity from 7.0 to about 7.8/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
12 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 5 FileTooLong finding(s) in God Classes — start with lib.rs (2), ui.rs, quad_gl.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with editbox.rs (2), lib.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with ui.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
25 duplicated block group(s) detected. 5.5 % of the production lines (889 of 16,290) are in a reported copy. A further 15 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 (5 lines × 2) finding(s) in Code Duplication — start with lib.rs, shapes.rs, mesh_rasterizer.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Edited copy of a member (16 corresponding lines) finding(s) in Code Duplication — start with texture.rs, lib.rs, shapes.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (10–11 lines × 2) finding(s) in Code Duplication — start with lib.rs, models.rs, checkbox.rs. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
6 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 5 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
2 of 57 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with lib.rs, style.rs. — One of this dimension's main actionable groups (2 warning-level).
D8 · Code Coverage
Line coverage 3.5% — 53 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 57 production file(s), 5 test binaries and 14 doc-test binaries).
What to do
- Resolve the 53 Low coverage finding(s) in Code Coverage — start with input.rs (3), texture.rs (2), window.rs (2). — One of this dimension's main actionable groups (53 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 11 test files): measured (0 flaky).
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 82 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/file.rs. Counted over 48 of the 74 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
12 deducted task-comment markers across 16290 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 11 TodoComment finding(s) in Explicit Debt — start with lib.rs (4), ui.rs (2), window.rs (2). — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with separator.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 6 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 6 high, 5 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
3 of 48 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/texture/slotmap.rs. Counted over 48 of the 74 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
ES2 · Immutable events
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
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`cargo test` for the toolchain this pipeline already uses) and gate merges on it.
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) as a CI step. What was searched, so you can tell an absence from a miss: the 1 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. — REDACTED:1
What to do
- Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — 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.
PF3 · Async & latency hygiene
X1 · Async correctness
X21 · Side-effecting pattern guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 90% | Exemplary | Solid. |
| Architecture | 97% | Exemplary | Solid. |
| Maturity | 56% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 50% | Adequate — gated by D8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 89% | Exemplary | Solid. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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 — 77 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: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; 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 — ~3124 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (3038 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- 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.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- 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 — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 13 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
- 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 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 4 current-state document(s) make no claim of a kind M4 checks. 2 claim(s) of kinds M4 does not check were not checked (path 2); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, 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 data present for 57 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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.
- S1 Web-Security Posture — No web surface: 74 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. 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.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 6 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 150 finding(s)
- Low coverage: src/audio.rs src/audio.rs:1
- Low coverage: src/camera.rs src/camera.rs:1
- Low coverage: src/color.rs src/color.rs:1
- Low coverage: src/error.rs src/error.rs:1
- Low coverage: src/exec.rs src/exec.rs:1
- Low coverage: src/experimental/animation.rs src/experimental/animation.rs:1
- Low coverage: src/experimental/camera/mouse.rs src/experimental/camera/mouse.rs:1
- Low coverage: src/experimental/coroutines.rs src/experimental/coroutines.rs:1
- Low coverage: src/experimental/coroutines/generational_storage.rs src/experimental/coroutines/generational_storage.rs:1
- Low coverage: src/experimental/scene.rs src/experimental/scene.rs:1
- Low coverage: src/experimental/scene/arena.rs src/experimental/scene/arena.rs:1
- Low coverage: src/experimental/state_machine.rs src/experimental/state_machine.rs:1
- Low coverage: src/file.rs src/file.rs:1
- Low coverage: src/input.rs src/input.rs:1
- Low coverage: src/lib.rs src/lib.rs:1
- Low coverage: src/math.rs src/math.rs:1
- Low coverage: src/math/circle.rs src/math/circle.rs:1
- Low coverage: src/math/rect.rs src/math/rect.rs:1
- Low coverage: src/models.rs src/models.rs:1
- Low coverage: src/quad_gl.rs src/quad_gl.rs:1
- Low coverage: src/shapes.rs src/shapes.rs:1
- Low coverage: src/telemetry.rs src/telemetry.rs:1
- Low coverage: src/text.rs src/text.rs:1
- Low coverage: src/texture.rs src/texture.rs:1
- Low coverage: src/texture/slotmap.rs src/texture/slotmap.rs:1
- TodoComment tiled/src/lib.rs:86
- TodoComment src/input.rs:158
- TodoComment src/lib.rs:743
- TodoComment src/shapes.rs:107
- TodoComment src/ui.rs:345
- TodoComment src/ui.rs:1288
- TodoComment src/ui/widgets/slider.rs:131
- TodoComment src/ui/widgets/window.rs:77
- TodoComment src/ui/widgets/window.rs:141
- TodoComment particles/src/lib.rs:830
- TodoComment particles/src/lib.rs:936
- FileTooLong: src/ui.rs src/ui.rs
- FileTooLong: src/quad_gl.rs src/quad_gl.rs
- FileTooLong: src/lib.rs particles/src/lib.rs
- FileTooLong: src/lib.rs src/lib.rs
- FileTooLong: src/texture.rs src/texture.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) macroquad_macro/src/lib.rs:94
- Duplicated block (5 lines × 2) src/shapes.rs:105
- Duplicated block (5 lines × 2) src/ui/render/mesh_rasterizer.rs:150
- Duplicated block (5 lines × 2) src/ui/widgets/progress_bar.rs:33
- World::collide_tag (cognitive 24) physics-platformer/src/lib.rs:381
- World::move_v (cognitive 18) physics-platformer/src/lib.rs:177
- World::solid_move (cognitive 16) physics-platformer/src/lib.rs:259
- MethodTooLong: Editbox.apply_keyboard_input src/ui/widgets/editbox.rs:81
- MethodTooLong: Editbox.ui src/ui/widgets/editbox.rs:283
- MethodTooLong: Emitter.new particles/src/lib.rs:538
- Edited copy of a member (16 corresponding lines) src/texture.rs:124
- Edited copy of a member (16 corresponding lines) src/lib.rs:545
- Edited copy of a member (16 corresponding lines) src/shapes.rs:34
- Duplicated block (10–11 lines × 2) particles/src/lib.rs:656
- Duplicated block (10–11 lines × 2) src/models.rs:625
- Duplicated block (10–11 lines × 2) src/ui/widgets/checkbox.rs:59
- Duplicated block (10 lines × 2) src/quad_gl.rs:298
- Duplicated block (10 lines × 2) src/quad_gl.rs:683
- Duplicated block (10 lines × 2) src/ui/widgets/combobox.rs:99
- Editbox::apply_keyboard_input (cyclomatic 37) src/ui/widgets/editbox.rs:81
- Editbox::ui (cyclomatic 35) src/ui/widgets/editbox.rs:283
- macroquad_profiler::profiler_window (cyclomatic 21) profiler/src/lib.rs:30
- macroquad_profiler::profiler (cyclomatic 17) profiler/src/lib.rs:161
- Editbox::apply_keyboard_input (cognitive 68) src/ui/widgets/editbox.rs:81
- Editbox::ui (cognitive 47) src/ui/widgets/editbox.rs:283
- macroquad_profiler::profiler_window (cognitive 30) profiler/src/lib.rs:30
- macroquad_profiler::profiler (cognitive 26) profiler/src/lib.rs:161
- Duplicated block (9 lines × 2) src/ui/widgets/checkbox.rs:139
- Duplicated block (9 lines × 2) src/shapes.rs:90
- Low cohesion: Stage (LCOM4 15) src/lib.rs:513
- Low cohesion: Style (LCOM4 4) src/ui/style.rs:232
- UiContext::process_input (cyclomatic 43) src/ui.rs:1222
- Drag::ui (cyclomatic 22) src/ui/widgets/drag.rs:80
- Emitter::update (cyclomatic 18) particles/src/lib.rs:786
- HackComment src/ui/widgets/separator.rs:10
- Drag::ui (cognitive 53) src/ui/widgets/drag.rs:80
- UiContext::process_input (cognitive 43) src/ui.rs:1222
- Emitter::update (cognitive 34) particles/src/lib.rs:786
- QuadGl::draw (cognitive 28) src/quad_gl.rs:679
- macroquad_macro::main (cognitive 24) macroquad_macro/src/lib.rs:35
- macroquad_tiled::load_map (cognitive 21) tiled/src/lib.rs:341
- Scene::update (cognitive 19) src/experimental/scene.rs:480
- Group::begin (cognitive 19) src/ui/widgets/group.rs:59
- PipelineExt::set_uniform (cognitive 18) src/quad_gl.rs:297
- Slider::ui (cognitive 18) src/ui/widgets/slider.rs:36
- ComboBox::ui (cognitive 17) src/ui/widgets/combobox.rs:35
- REDACTED
- TooManyMethods: Ui src/ui.rs:335
- TooManyFields: Context src/lib.rs:177
- FunctionTooLong: macroquad_tiled::load_map tiled/src/lib.rs:341
- ClassTooLong: Ui src/ui.rs:335
- REDACTED
- Edited copy of a member (31 corresponding lines) src/texture.rs:247
- Edited copy of a member (25 corresponding lines) src/shapes.rs:211
- Edited copy of a member (32 corresponding lines) physics-platformer/src/lib.rs:177
- Edited copy of a member (21 corresponding lines) src/ui/style.rs:40
- Edited copy of a member (24 corresponding lines) src/camera.rs:125
- Edited copy of a member (12 corresponding lines) src/models.rs:119
- Edited copy of a member (18 corresponding lines) src/lib.rs:578
- Edited copy of a member (13 corresponding lines) src/experimental/collections/storage.rs:51
- Edited copies of one member (3 members, 21+ corresponding lines) src/ui/render/painter.rs:422
- Edited copy of a member (11 corresponding lines) src/texture.rs:180
- Edited copy of a member (14 corresponding lines) src/lib.rs:562
- Edited copy of a member (9 corresponding lines) src/ui/widgets/editbox/text_editor.rs:273
- Duplicated block (19 lines × 2) src/texture.rs:248
- Duplicated block (17 lines × 2) particles/src/lib.rs:307
- Duplicated block (16 lines × 3) src/ui.rs:810
- Duplicated block (14 lines × 2) src/camera.rs:126
- Duplicated block (11–14 lines × 2) src/shapes.rs:344
- Duplicated block (12 lines × 3) src/models.rs:230
- Duplicated block (11 lines × 4) src/models.rs:640
- Duplicated block (11 lines × 2) src/shapes.rs:225
- Duplicated block (8 lines × 2) src/experimental/collections/storage.rs:52
- Duplicated block (4–6 lines × 3) src/shapes.rs:284
- Duplicated block (5 lines × 3) macroquad_macro/src/lib.rs:94
- Duplicated block (7 lines × 2) src/models.rs:486
- Duplicated block (6 lines × 2) src/texture.rs:272
Minor — 13 finding(s)
- Orphaned file src/texture/slotmap.rs:1
- Orphaned file src/ui/widgets/progress_bar.rs:1
- Orphaned file src/experimental/camera/mouse.rs:1
- Duplicated predicate src/ui/widgets/tabbar.rs:54
- Duplicated predicate src/ui/widgets/drag.rs:177
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:1
- No changelog
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-afc807bd29904be4a90e5cb2f4f65c71/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-afc807bd29904be4a90e5cb2f4f65c71/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 . | 11 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| 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 | — |
| 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |