Executive summary
ArthurBrussee/brush falls short of our standard for a preview release, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 54 out of 100 and is rated Adequate, and all 41 of its critical findings are security problems.
Accessibility, at 40, is the weakest lens and counts most in the score. The best first step is adding text alternatives, worth about 10 points. Recording design decisions comes next, worth about 3 points. Raising Accessibility to 65 would lift the score to about 65.
Thirty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five known security holes in the packages the code depends on can be used by attackers, and two pipeline steps run downloads nobody checks. Pinning each tool to an exact version, updating the vulnerable packages and checking each download against a checksum would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and passing outside input through environment variables would deal with the pipeline step that puts outside input straight into a shell command.
The product code is 25,676 lines, about €29,000 to rebuild.
If Accessibility rose from 40 to 65, the lowest score rated Strong, the score would rise from 54 to about 65.
New since the last survey: 33 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 3 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €29,000 · Estimate
| Cost to rebuild | €9,800 to €49,000, for 163 to 518 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 25,676 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 brush_async.native | 2 brush_cube | 3 brush_process.message | 4 brush_process.slot | 5 brush_vfs | 6 brush_app.ui.camera_controls | 7 brush_process | 8 brush_render.kernels.types | 9 brush_render.kernels.camera_model.pinhole | 10 brush_render.kernels.camera_model | 11 brush_render.kernels.camera_model.kannala_brandt_4 | 12 brush_render.kernels.camera_model.radial_tangential_8 | 13 brush_render.kernels.camera_model.thin_prism_fisheye | 14 brush_render.camera | 15 brush_app.ui.splat_backbuffer | 16 brush_app.ui.ui_process | 17 brush_render.gaussian_splats | 18 brush_app.ui.app | 19 brush_app.ui.panels | 20 brush_render | 21 brush_render.bwd.burn_glue | 22 brush_train.splat_init | 23 brush_app.ui.stats | 24 brush_dataset.config | 25 brush_dataset.load_image | 26 brush_train.eval | 27 brush_dataset.formats.colmap | 28 brush_dataset.formats.realitycapture | 29 brush_dataset.scene | 30 brush_process.config | 31 brush_app.ui.settings_panel | 32 brush_app.ui.training_panel | 33 brush_dataset | 34 brush_js | 35 brush_rerun.visualize_tools | 36 brush_train.train | 37 brush_app.ui.datasets | 38 brush_app.ui.scene | 39 brush_dataset.formats | 40 brush_process.train_stream |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 brush_async.native | ||||||||||||||||||||||||||||||||||||||||
| 2 brush_cube | ||||||||||||||||||||||||||||||||||||||||
| 3 brush_process.message | ||||||||||||||||||||||||||||||||||||||||
| 4 brush_process.slot | ||||||||||||||||||||||||||||||||||||||||
| 5 brush_vfs | ||||||||||||||||||||||||||||||||||||||||
| 6 brush_app.ui.camera_controls | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 brush_process | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 brush_render.kernels.types | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 9 brush_render.kernels.camera_model.pinhole | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 brush_render.kernels.camera_model | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 11 brush_render.kernels.camera_model.kannala_brandt_4 | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 brush_render.kernels.camera_model.radial_tangential_8 | 5 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 13 brush_render.kernels.camera_model.thin_prism_fisheye | 5 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 14 brush_render.camera | 2 | 2 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 15 brush_app.ui.splat_backbuffer | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 brush_app.ui.ui_process | 1 | 2 | 2 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 17 brush_render.gaussian_splats | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 brush_app.ui.app | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 19 brush_app.ui.panels | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 brush_render | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 brush_render.bwd.burn_glue | 2 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 22 brush_train.splat_init | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 brush_app.ui.stats | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 brush_dataset.config | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 brush_dataset.load_image | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 brush_train.eval | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 brush_dataset.formats.colmap | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 brush_dataset.formats.realitycapture | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 brush_dataset.scene | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 brush_process.config | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 brush_app.ui.settings_panel | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 brush_app.ui.training_panel | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 33 brush_dataset | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 brush_js | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 brush_rerun.visualize_tools | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 brush_train.train | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 brush_app.ui.datasets | 1 | 1 | 3 | 1 | 1 | 6 | 2 | |||||||||||||||||||||||||||||||||
| 38 brush_app.ui.scene | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 39 brush_dataset.formats | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 brush_process.train_stream | 1 | 1 | 1 | 1 | 1 | 1 |
6→2 brush_app.ui.camera_controls uses brush_cube✕
- Connections
- 4 pairs of types, where a type in brush_app.ui.camera_controls uses a type in brush_cube.
- The types involved
brush_app.ui.camera_controls.CameraController→brush_cube.Quatbrush_app.ui.camera_controls.CameraController→brush_cube.Vec2brush_app.ui.camera_controls.camera_controls$module→brush_cube.Quatbrush_app.ui.camera_controls.camera_controls$module→brush_cube.Vec2
- Direction
- brush_app.ui.camera_controls uses brush_cube, so a change to brush_cube can break brush_app.ui.camera_controls, while a change to brush_app.ui.camera_controls can't break brush_cube.
- Position
- Below the diagonal: brush_app.ui.camera_controls uses a module listed above it, which is the healthy direction.
6→18 brush_app.ui.camera_controls uses brush_app.ui.app part of a loop✕
- Connections
- 1 pair of types, where a type in brush_app.ui.camera_controls uses a type in brush_app.ui.app.
- The types involved
brush_app.ui.camera_controls.CameraController→brush_app.ui.app.CameraSettings
- Direction
- brush_app.ui.camera_controls uses brush_app.ui.app, so a change to brush_app.ui.app can break brush_app.ui.camera_controls, while a change to brush_app.ui.camera_controls can't break brush_app.ui.app.
- 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.
7→4 brush_process uses brush_process.slot✕
- Connections
- 2 pairs of types, where a type in brush_process uses a type in brush_process.slot.
- The types involved
brush_process.RunningProcess→brush_process.slot.Slotbrush_process.brush_process$module→brush_process.slot.SlotSender
- Direction
- brush_process uses brush_process.slot, so a change to brush_process.slot can break brush_process, while a change to brush_process can't break brush_process.slot.
- Position
- Below the diagonal: brush_process uses a module listed above it, which is the healthy direction.
7→5 brush_process uses brush_vfs✕
- Connections
- 1 pair of types, where a type in brush_process uses a type in brush_vfs.
- The types involved
brush_process.ProcessStream→brush_vfs.SendNotWasm
- Direction
- brush_process uses brush_vfs, so a change to brush_vfs can break brush_process, while a change to brush_process can't break brush_vfs.
- Position
- Below the diagonal: brush_process uses a module listed above it, which is the healthy direction.
8→2 brush_render.kernels.types uses brush_cube✕
- Connections
- 2 pairs of types, where a type in brush_render.kernels.types uses a type in brush_cube.
- The types involved
brush_render.kernels.types.ProjectUniforms→brush_cube.Mat3brush_render.kernels.types.ProjectUniforms→brush_cube.Vec3A
- Direction
- brush_render.kernels.types uses brush_cube, so a change to brush_cube can break brush_render.kernels.types, while a change to brush_render.kernels.types can't break brush_cube.
- Position
- Below the diagonal: brush_render.kernels.types uses a module listed above it, which is the healthy direction.
8→9 brush_render.kernels.types uses brush_render.kernels.camera_model.pinhole part of a loop✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.types uses a type in brush_render.kernels.camera_model.pinhole.
- The types involved
brush_render.kernels.types.ProjectUniforms→brush_render.kernels.camera_model.pinhole.PinholeParams
- Direction
- brush_render.kernels.types uses brush_render.kernels.camera_model.pinhole, so a change to brush_render.kernels.camera_model.pinhole can break brush_render.kernels.types, while a change to brush_render.kernels.types can't break brush_render.kernels.camera_model.pinhole.
- 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→10 brush_render.kernels.types uses brush_render.kernels.camera_model part of a loop✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.types uses a type in brush_render.kernels.camera_model.
- The types involved
brush_render.kernels.types.ProjectUniforms→brush_render.kernels.camera_model.JacobianClampLimits
- Direction
- brush_render.kernels.types uses brush_render.kernels.camera_model, so a change to brush_render.kernels.camera_model can break brush_render.kernels.types, while a change to brush_render.kernels.types can't break brush_render.kernels.camera_model.
- 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→2 brush_render.kernels.camera_model.pinhole uses brush_cube✕
- Connections
- 5 pairs of types, where a type in brush_render.kernels.camera_model.pinhole uses a type in brush_cube.
- The types involved
brush_render.kernels.camera_model.pinhole.pinhole$module→brush_cube.Mat2x3brush_render.kernels.camera_model.pinhole.pinhole$module→brush_cube.Sym2brush_render.kernels.camera_model.pinhole.pinhole$module→brush_cube.Sym3brush_render.kernels.camera_model.pinhole.pinhole$module→brush_cube.Vec2brush_render.kernels.camera_model.pinhole.pinhole$module→brush_cube.Vec3A
- Direction
- brush_render.kernels.camera_model.pinhole uses brush_cube, so a change to brush_cube can break brush_render.kernels.camera_model.pinhole, while a change to brush_render.kernels.camera_model.pinhole can't break brush_cube.
- Position
- Below the diagonal: brush_render.kernels.camera_model.pinhole uses a module listed above it, which is the healthy direction.
9→8 brush_render.kernels.camera_model.pinhole uses brush_render.kernels.types✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.camera_model.pinhole uses a type in brush_render.kernels.types.
- The types involved
brush_render.kernels.camera_model.pinhole.pinhole$module→brush_render.kernels.types.ProjectUniforms
- Direction
- brush_render.kernels.camera_model.pinhole uses brush_render.kernels.types, so a change to brush_render.kernels.types can break brush_render.kernels.camera_model.pinhole, while a change to brush_render.kernels.camera_model.pinhole can't break brush_render.kernels.types.
- Position
- Below the diagonal: brush_render.kernels.camera_model.pinhole uses a module listed above it, which is the healthy direction.
9→10 brush_render.kernels.camera_model.pinhole uses brush_render.kernels.camera_model part of a loop✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.camera_model.pinhole uses a type in brush_render.kernels.camera_model.
- The types involved
brush_render.kernels.camera_model.pinhole.pinhole$module→brush_render.kernels.camera_model.JacobianClampLimits
- Direction
- brush_render.kernels.camera_model.pinhole uses brush_render.kernels.camera_model, so a change to brush_render.kernels.camera_model can break brush_render.kernels.camera_model.pinhole, while a change to brush_render.kernels.camera_model.pinhole can't break brush_render.kernels.camera_model.
- 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 brush_render.kernels.camera_model uses brush_cube✕
- Connections
- 5 pairs of types, where a type in brush_render.kernels.camera_model uses a type in brush_cube.
- The types involved
brush_render.kernels.camera_model.camera_model$module→brush_cube.Mat2x3brush_render.kernels.camera_model.camera_model$module→brush_cube.Sym2brush_render.kernels.camera_model.camera_model$module→brush_cube.Sym3brush_render.kernels.camera_model.camera_model$module→brush_cube.Vec2brush_render.kernels.camera_model.camera_model$module→brush_cube.Vec3A
- Direction
- brush_render.kernels.camera_model uses brush_cube, so a change to brush_cube can break brush_render.kernels.camera_model, while a change to brush_render.kernels.camera_model can't break brush_cube.
- Position
- Below the diagonal: brush_render.kernels.camera_model uses a module listed above it, which is the healthy direction.
10→8 brush_render.kernels.camera_model uses brush_render.kernels.types✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.camera_model uses a type in brush_render.kernels.types.
- The types involved
brush_render.kernels.camera_model.camera_model$module→brush_render.kernels.types.ProjectUniforms
- Direction
- brush_render.kernels.camera_model uses brush_render.kernels.types, so a change to brush_render.kernels.types can break brush_render.kernels.camera_model, while a change to brush_render.kernels.camera_model can't break brush_render.kernels.types.
- Position
- Below the diagonal: brush_render.kernels.camera_model uses a module listed above it, which is the healthy direction.
10→9 brush_render.kernels.camera_model uses brush_render.kernels.camera_model.pinhole✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.camera_model uses a type in brush_render.kernels.camera_model.pinhole.
- The types involved
brush_render.kernels.camera_model.camera_model$module→brush_render.kernels.camera_model.pinhole.PinholeParams
- Direction
- brush_render.kernels.camera_model uses brush_render.kernels.camera_model.pinhole, so a change to brush_render.kernels.camera_model.pinhole can break brush_render.kernels.camera_model, while a change to brush_render.kernels.camera_model can't break brush_render.kernels.camera_model.pinhole.
- Position
- Below the diagonal: brush_render.kernels.camera_model uses a module listed above it, which is the healthy direction.
11→2 brush_render.kernels.camera_model.kannala_brandt_4 uses brush_cube✕
- Connections
- 5 pairs of types, where a type in brush_render.kernels.camera_model.kannala_brandt_4 uses a type in brush_cube.
- The types involved
brush_render.kernels.camera_model.kannala_brandt_4.kannala_brandt_4$module→brush_cube.Mat2x3brush_render.kernels.camera_model.kannala_brandt_4.kannala_brandt_4$module→brush_cube.Sym2brush_render.kernels.camera_model.kannala_brandt_4.kannala_brandt_4$module→brush_cube.Sym3brush_render.kernels.camera_model.kannala_brandt_4.kannala_brandt_4$module→brush_cube.Vec2brush_render.kernels.camera_model.kannala_brandt_4.kannala_brandt_4$module→brush_cube.Vec3A
- Direction
- brush_render.kernels.camera_model.kannala_brandt_4 uses brush_cube, so a change to brush_cube can break brush_render.kernels.camera_model.kannala_brandt_4, while a change to brush_render.kernels.camera_model.kannala_brandt_4 can't break brush_cube.
- Position
- Below the diagonal: brush_render.kernels.camera_model.kannala_brandt_4 uses a module listed above it, which is the healthy direction.
11→8 brush_render.kernels.camera_model.kannala_brandt_4 uses brush_render.kernels.types✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.camera_model.kannala_brandt_4 uses a type in brush_render.kernels.types.
- The types involved
brush_render.kernels.camera_model.kannala_brandt_4.kannala_brandt_4$module→brush_render.kernels.types.ProjectUniforms
- Direction
- brush_render.kernels.camera_model.kannala_brandt_4 uses brush_render.kernels.types, so a change to brush_render.kernels.types can break brush_render.kernels.camera_model.kannala_brandt_4, while a change to brush_render.kernels.camera_model.kannala_brandt_4 can't break brush_render.kernels.types.
- Position
- Below the diagonal: brush_render.kernels.camera_model.kannala_brandt_4 uses a module listed above it, which is the healthy direction.
11→9 brush_render.kernels.camera_model.kannala_brandt_4 uses brush_render.kernels.camera_model.pinhole✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.camera_model.kannala_brandt_4 uses a type in brush_render.kernels.camera_model.pinhole.
- The types involved
brush_render.kernels.camera_model.kannala_brandt_4.kannala_brandt_4$module→brush_render.kernels.camera_model.pinhole.PinholeParams
- Direction
- brush_render.kernels.camera_model.kannala_brandt_4 uses brush_render.kernels.camera_model.pinhole, so a change to brush_render.kernels.camera_model.pinhole can break brush_render.kernels.camera_model.kannala_brandt_4, while a change to brush_render.kernels.camera_model.kannala_brandt_4 can't break brush_render.kernels.camera_model.pinhole.
- Position
- Below the diagonal: brush_render.kernels.camera_model.kannala_brandt_4 uses a module listed above it, which is the healthy direction.
12→2 brush_render.kernels.camera_model.radial_tangential_8 uses brush_cube✕
- Connections
- 5 pairs of types, where a type in brush_render.kernels.camera_model.radial_tangential_8 uses a type in brush_cube.
- The types involved
brush_render.kernels.camera_model.radial_tangential_8.radial_tangential_8$module→brush_cube.Mat2x3brush_render.kernels.camera_model.radial_tangential_8.radial_tangential_8$module→brush_cube.Sym2brush_render.kernels.camera_model.radial_tangential_8.radial_tangential_8$module→brush_cube.Sym3brush_render.kernels.camera_model.radial_tangential_8.radial_tangential_8$module→brush_cube.Vec2brush_render.kernels.camera_model.radial_tangential_8.radial_tangential_8$module→brush_cube.Vec3A
- Direction
- brush_render.kernels.camera_model.radial_tangential_8 uses brush_cube, so a change to brush_cube can break brush_render.kernels.camera_model.radial_tangential_8, while a change to brush_render.kernels.camera_model.radial_tangential_8 can't break brush_cube.
- Position
- Below the diagonal: brush_render.kernels.camera_model.radial_tangential_8 uses a module listed above it, which is the healthy direction.
12→8 brush_render.kernels.camera_model.radial_tangential_8 uses brush_render.kernels.types✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.camera_model.radial_tangential_8 uses a type in brush_render.kernels.types.
- The types involved
brush_render.kernels.camera_model.radial_tangential_8.radial_tangential_8$module→brush_render.kernels.types.ProjectUniforms
- Direction
- brush_render.kernels.camera_model.radial_tangential_8 uses brush_render.kernels.types, so a change to brush_render.kernels.types can break brush_render.kernels.camera_model.radial_tangential_8, while a change to brush_render.kernels.camera_model.radial_tangential_8 can't break brush_render.kernels.types.
- Position
- Below the diagonal: brush_render.kernels.camera_model.radial_tangential_8 uses a module listed above it, which is the healthy direction.
12→9 brush_render.kernels.camera_model.radial_tangential_8 uses brush_render.kernels.camera_model.pinhole✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.camera_model.radial_tangential_8 uses a type in brush_render.kernels.camera_model.pinhole.
- The types involved
brush_render.kernels.camera_model.radial_tangential_8.radial_tangential_8$module→brush_render.kernels.camera_model.pinhole.PinholeParams
- Direction
- brush_render.kernels.camera_model.radial_tangential_8 uses brush_render.kernels.camera_model.pinhole, so a change to brush_render.kernels.camera_model.pinhole can break brush_render.kernels.camera_model.radial_tangential_8, while a change to brush_render.kernels.camera_model.radial_tangential_8 can't break brush_render.kernels.camera_model.pinhole.
- Position
- Below the diagonal: brush_render.kernels.camera_model.radial_tangential_8 uses a module listed above it, which is the healthy direction.
12→10 brush_render.kernels.camera_model.radial_tangential_8 uses brush_render.kernels.camera_model✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.camera_model.radial_tangential_8 uses a type in brush_render.kernels.camera_model.
- The types involved
brush_render.kernels.camera_model.radial_tangential_8.radial_tangential_8$module→brush_render.kernels.camera_model.JacobianClampLimits
- Direction
- brush_render.kernels.camera_model.radial_tangential_8 uses brush_render.kernels.camera_model, so a change to brush_render.kernels.camera_model can break brush_render.kernels.camera_model.radial_tangential_8, while a change to brush_render.kernels.camera_model.radial_tangential_8 can't break brush_render.kernels.camera_model.
- Position
- Below the diagonal: brush_render.kernels.camera_model.radial_tangential_8 uses a module listed above it, which is the healthy direction.
13→2 brush_render.kernels.camera_model.thin_prism_fisheye uses brush_cube✕
- Connections
- 5 pairs of types, where a type in brush_render.kernels.camera_model.thin_prism_fisheye uses a type in brush_cube.
- The types involved
brush_render.kernels.camera_model.thin_prism_fisheye.thin_prism_fisheye$module→brush_cube.Mat2x3brush_render.kernels.camera_model.thin_prism_fisheye.thin_prism_fisheye$module→brush_cube.Sym2brush_render.kernels.camera_model.thin_prism_fisheye.thin_prism_fisheye$module→brush_cube.Sym3brush_render.kernels.camera_model.thin_prism_fisheye.thin_prism_fisheye$module→brush_cube.Vec2brush_render.kernels.camera_model.thin_prism_fisheye.thin_prism_fisheye$module→brush_cube.Vec3A
- Direction
- brush_render.kernels.camera_model.thin_prism_fisheye uses brush_cube, so a change to brush_cube can break brush_render.kernels.camera_model.thin_prism_fisheye, while a change to brush_render.kernels.camera_model.thin_prism_fisheye can't break brush_cube.
- Position
- Below the diagonal: brush_render.kernels.camera_model.thin_prism_fisheye uses a module listed above it, which is the healthy direction.
13→8 brush_render.kernels.camera_model.thin_prism_fisheye uses brush_render.kernels.types✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.camera_model.thin_prism_fisheye uses a type in brush_render.kernels.types.
- The types involved
brush_render.kernels.camera_model.thin_prism_fisheye.thin_prism_fisheye$module→brush_render.kernels.types.ProjectUniforms
- Direction
- brush_render.kernels.camera_model.thin_prism_fisheye uses brush_render.kernels.types, so a change to brush_render.kernels.types can break brush_render.kernels.camera_model.thin_prism_fisheye, while a change to brush_render.kernels.camera_model.thin_prism_fisheye can't break brush_render.kernels.types.
- Position
- Below the diagonal: brush_render.kernels.camera_model.thin_prism_fisheye uses a module listed above it, which is the healthy direction.
13→9 brush_render.kernels.camera_model.thin_prism_fisheye uses brush_render.kernels.camera_model.pinhole✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.camera_model.thin_prism_fisheye uses a type in brush_render.kernels.camera_model.pinhole.
- The types involved
brush_render.kernels.camera_model.thin_prism_fisheye.thin_prism_fisheye$module→brush_render.kernels.camera_model.pinhole.PinholeParams
- Direction
- brush_render.kernels.camera_model.thin_prism_fisheye uses brush_render.kernels.camera_model.pinhole, so a change to brush_render.kernels.camera_model.pinhole can break brush_render.kernels.camera_model.thin_prism_fisheye, while a change to brush_render.kernels.camera_model.thin_prism_fisheye can't break brush_render.kernels.camera_model.pinhole.
- Position
- Below the diagonal: brush_render.kernels.camera_model.thin_prism_fisheye uses a module listed above it, which is the healthy direction.
13→11 brush_render.kernels.camera_model.thin_prism_fisheye uses brush_render.kernels.camera_model.kannala_brandt_4✕
- Connections
- 1 pair of types, where a type in brush_render.kernels.camera_model.thin_prism_fisheye uses a type in brush_render.kernels.camera_model.kannala_brandt_4.
- The types involved
brush_render.kernels.camera_model.thin_prism_fisheye.ThinPrismFisheyeParams→brush_render.kernels.camera_model.kannala_brandt_4.KannalaBrandt4Params
- Direction
- brush_render.kernels.camera_model.thin_prism_fisheye uses brush_render.kernels.camera_model.kannala_brandt_4, so a change to brush_render.kernels.camera_model.kannala_brandt_4 can break brush_render.kernels.camera_model.thin_prism_fisheye, while a change to brush_render.kernels.camera_model.thin_prism_fisheye can't break brush_render.kernels.camera_model.kannala_brandt_4.
- Position
- Below the diagonal: brush_render.kernels.camera_model.thin_prism_fisheye uses a module listed above it, which is the healthy direction.
14→2 brush_render.camera uses brush_cube✕
- Connections
- 2 pairs of types, where a type in brush_render.camera uses a type in brush_cube.
- The types involved
brush_render.camera.Camera→brush_cube.Quatbrush_render.camera.Camera→brush_cube.Vec2
- Direction
- brush_render.camera uses brush_cube, so a change to brush_cube can break brush_render.camera, while a change to brush_render.camera can't break brush_cube.
- Position
- Below the diagonal: brush_render.camera uses a module listed above it, which is the healthy direction.
14→9 brush_render.camera uses brush_render.kernels.camera_model.pinhole✕
- Connections
- 2 pairs of types, where a type in brush_render.camera uses a type in brush_render.kernels.camera_model.pinhole.
- The types involved
brush_render.camera.Camera→brush_render.kernels.camera_model.pinhole.PinholeParamsbrush_render.camera.camera$module→brush_render.kernels.camera_model.pinhole.PinholeParams
- Direction
- brush_render.camera uses brush_render.kernels.camera_model.pinhole, so a change to brush_render.kernels.camera_model.pinhole can break brush_render.camera, while a change to brush_render.camera can't break brush_render.kernels.camera_model.pinhole.
- Position
- Below the diagonal: brush_render.camera uses a module listed above it, which is the healthy direction.
14→10 brush_render.camera uses brush_render.kernels.camera_model✕
- Connections
- 3 pairs of types, where a type in brush_render.camera uses a type in brush_render.kernels.camera_model.
- The types involved
brush_render.camera.Camera→brush_render.kernels.camera_model.CameraModelbrush_render.camera.camera$module→brush_render.kernels.camera_model.CameraModelbrush_render.camera.camera$module→brush_render.kernels.camera_model.JacobianClampLimits
- Direction
- brush_render.camera uses brush_render.kernels.camera_model, so a change to brush_render.kernels.camera_model can break brush_render.camera, while a change to brush_render.camera can't break brush_render.kernels.camera_model.
- Position
- Below the diagonal: brush_render.camera uses a module listed above it, which is the healthy direction.
14→11 brush_render.camera uses brush_render.kernels.camera_model.kannala_brandt_4✕
- Connections
- 1 pair of types, where a type in brush_render.camera uses a type in brush_render.kernels.camera_model.kannala_brandt_4.
- The types involved
brush_render.camera.camera$module→brush_render.kernels.camera_model.kannala_brandt_4.KannalaBrandt4Params
- Direction
- brush_render.camera uses brush_render.kernels.camera_model.kannala_brandt_4, so a change to brush_render.kernels.camera_model.kannala_brandt_4 can break brush_render.camera, while a change to brush_render.camera can't break brush_render.kernels.camera_model.kannala_brandt_4.
- Position
- Below the diagonal: brush_render.camera uses a module listed above it, which is the healthy direction.
14→12 brush_render.camera uses brush_render.kernels.camera_model.radial_tangential_8✕
- Connections
- 1 pair of types, where a type in brush_render.camera uses a type in brush_render.kernels.camera_model.radial_tangential_8.
- The types involved
brush_render.camera.camera$module→brush_render.kernels.camera_model.radial_tangential_8.RadialTangential8Params
- Direction
- brush_render.camera uses brush_render.kernels.camera_model.radial_tangential_8, so a change to brush_render.kernels.camera_model.radial_tangential_8 can break brush_render.camera, while a change to brush_render.camera can't break brush_render.kernels.camera_model.radial_tangential_8.
- Position
- Below the diagonal: brush_render.camera uses a module listed above it, which is the healthy direction.
15→4 brush_app.ui.splat_backbuffer uses brush_process.slot✕
- Connections
- 2 pairs of types, where a type in brush_app.ui.splat_backbuffer uses a type in brush_process.slot.
- The types involved
brush_app.ui.splat_backbuffer.RenderRequest→brush_process.slot.Slotbrush_app.ui.splat_backbuffer.SplatBackbuffer→brush_process.slot.Slot
- Direction
- brush_app.ui.splat_backbuffer uses brush_process.slot, so a change to brush_process.slot can break brush_app.ui.splat_backbuffer, while a change to brush_app.ui.splat_backbuffer can't break brush_process.slot.
- Position
- Below the diagonal: brush_app.ui.splat_backbuffer uses a module listed above it, which is the healthy direction.
15→14 brush_app.ui.splat_backbuffer uses brush_render.camera✕
- Connections
- 2 pairs of types, where a type in brush_app.ui.splat_backbuffer uses a type in brush_render.camera.
- The types involved
brush_app.ui.splat_backbuffer.LastRenderState→brush_render.camera.Camerabrush_app.ui.splat_backbuffer.SplatBackbuffer→brush_render.camera.Camera
- Direction
- brush_app.ui.splat_backbuffer uses brush_render.camera, so a change to brush_render.camera can break brush_app.ui.splat_backbuffer, while a change to brush_app.ui.splat_backbuffer can't break brush_render.camera.
- Position
- Below the diagonal: brush_app.ui.splat_backbuffer uses a module listed above it, which is the healthy direction.
16→1 brush_app.ui.ui_process uses brush_async.native✕
- Connections
- 1 pair of types, where a type in brush_app.ui.ui_process uses a type in brush_async.native.
- The types involved
brush_app.ui.ui_process.UiProcessInner→brush_async.native.Actor
- Direction
- brush_app.ui.ui_process uses brush_async.native, so a change to brush_async.native can break brush_app.ui.ui_process, while a change to brush_app.ui.ui_process can't break brush_async.native.
- Position
- Below the diagonal: brush_app.ui.ui_process uses a module listed above it, which is the healthy direction.
16→2 brush_app.ui.ui_process uses brush_cube✕
- Connections
- 2 pairs of types, where a type in brush_app.ui.ui_process uses a type in brush_cube.
- The types involved
brush_app.ui.ui_process.UiProcess→brush_cube.Quatbrush_app.ui.ui_process.UiProcessInner→brush_cube.Quat
- Direction
- brush_app.ui.ui_process uses brush_cube, so a change to brush_cube can break brush_app.ui.ui_process, while a change to brush_app.ui.ui_process can't break brush_cube.
- Position
- Below the diagonal: brush_app.ui.ui_process uses a module listed above it, which is the healthy direction.
16→4 brush_app.ui.ui_process uses brush_process.slot✕
- Connections
- 2 pairs of types, where a type in brush_app.ui.ui_process uses a type in brush_process.slot.
- The types involved
brush_app.ui.ui_process.ProcessHandle→brush_process.slot.Slotbrush_app.ui.ui_process.UiProcess→brush_process.slot.Slot
- Direction
- brush_app.ui.ui_process uses brush_process.slot, so a change to brush_process.slot can break brush_app.ui.ui_process, while a change to brush_app.ui.ui_process can't break brush_process.slot.
- Position
- Below the diagonal: brush_app.ui.ui_process uses a module listed above it, which is the healthy direction.
16→6 brush_app.ui.ui_process uses brush_app.ui.camera_controls✕
- Connections
- 1 pair of types, where a type in brush_app.ui.ui_process uses a type in brush_app.ui.camera_controls.
- The types involved
brush_app.ui.ui_process.UiProcessInner→brush_app.ui.camera_controls.CameraController
- Direction
- brush_app.ui.ui_process uses brush_app.ui.camera_controls, so a change to brush_app.ui.camera_controls can break brush_app.ui.ui_process, while a change to brush_app.ui.ui_process can't break brush_app.ui.camera_controls.
- Position
- Below the diagonal: brush_app.ui.ui_process uses a module listed above it, which is the healthy direction.
16→7 brush_app.ui.ui_process uses brush_process✕
- Connections
- 1 pair of types, where a type in brush_app.ui.ui_process uses a type in brush_process.
- The types involved
brush_app.ui.ui_process.UiProcess→brush_process.RunningProcess
- Direction
- brush_app.ui.ui_process uses brush_process, so a change to brush_process can break brush_app.ui.ui_process, while a change to brush_app.ui.ui_process can't break brush_process.
- Position
- Below the diagonal: brush_app.ui.ui_process uses a module listed above it, which is the healthy direction.
16→14 brush_app.ui.ui_process uses brush_render.camera✕
- Connections
- 2 pairs of types, where a type in brush_app.ui.ui_process uses a type in brush_render.camera.
- The types involved
brush_app.ui.ui_process.UiProcess→brush_render.camera.Camerabrush_app.ui.ui_process.UiProcessInner→brush_render.camera.Camera
- Direction
- brush_app.ui.ui_process uses brush_render.camera, so a change to brush_render.camera can break brush_app.ui.ui_process, while a change to brush_app.ui.ui_process can't break brush_render.camera.
- Position
- Below the diagonal: brush_app.ui.ui_process uses a module listed above it, which is the healthy direction.
16→18 brush_app.ui.ui_process uses brush_app.ui.app part of a loop✕
- Connections
- 1 pair of types, where a type in brush_app.ui.ui_process uses a type in brush_app.ui.app.
- The types involved
brush_app.ui.ui_process.UiProcess→brush_app.ui.app.CameraSettings
- Direction
- brush_app.ui.ui_process uses brush_app.ui.app, so a change to brush_app.ui.app can break brush_app.ui.ui_process, while a change to brush_app.ui.ui_process can't break brush_app.ui.app.
- 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.
17→14 brush_render.gaussian_splats uses brush_render.camera✕
- Connections
- 1 pair of types, where a type in brush_render.gaussian_splats uses a type in brush_render.camera.
- The types involved
brush_render.gaussian_splats.gaussian_splats$module→brush_render.camera.Camera
- Direction
- brush_render.gaussian_splats uses brush_render.camera, so a change to brush_render.camera can break brush_render.gaussian_splats, while a change to brush_render.gaussian_splats can't break brush_render.camera.
- Position
- Below the diagonal: brush_render.gaussian_splats uses a module listed above it, which is the healthy direction.
18→6 brush_app.ui.app uses brush_app.ui.camera_controls✕
- Connections
- 1 pair of types, where a type in brush_app.ui.app uses a type in brush_app.ui.camera_controls.
- The types involved
brush_app.ui.app.CameraSettings→brush_app.ui.camera_controls.CameraClamping
- Direction
- brush_app.ui.app uses brush_app.ui.camera_controls, so a change to brush_app.ui.camera_controls can break brush_app.ui.app, while a change to brush_app.ui.app can't break brush_app.ui.camera_controls.
- Position
- Below the diagonal: brush_app.ui.app uses a module listed above it, which is the healthy direction.
18→7 brush_app.ui.app uses brush_process✕
- Connections
- 1 pair of types, where a type in brush_app.ui.app uses a type in brush_process.
- The types involved
brush_app.ui.app.App→brush_process.RunningProcess
- Direction
- brush_app.ui.app uses brush_process, so a change to brush_process can break brush_app.ui.app, while a change to brush_app.ui.app can't break brush_process.
- Position
- Below the diagonal: brush_app.ui.app uses a module listed above it, which is the healthy direction.
18→15 brush_app.ui.app uses brush_app.ui.splat_backbuffer✕
- Connections
- 1 pair of types, where a type in brush_app.ui.app uses a type in brush_app.ui.splat_backbuffer.
- The types involved
brush_app.ui.app.App→brush_app.ui.splat_backbuffer.Frame
- Direction
- brush_app.ui.app uses brush_app.ui.splat_backbuffer, so a change to brush_app.ui.splat_backbuffer can break brush_app.ui.app, while a change to brush_app.ui.app can't break brush_app.ui.splat_backbuffer.
- Position
- Below the diagonal: brush_app.ui.app uses a module listed above it, which is the healthy direction.
18→16 brush_app.ui.app uses brush_app.ui.ui_process✕
- Connections
- 2 pairs of types, where a type in brush_app.ui.app uses a type in brush_app.ui.ui_process.
- The types involved
brush_app.ui.app.App→brush_app.ui.ui_process.UiProcessbrush_app.ui.app.AppTree→brush_app.ui.ui_process.UiProcess
- Direction
- brush_app.ui.app uses brush_app.ui.ui_process, so a change to brush_app.ui.ui_process can break brush_app.ui.app, while a change to brush_app.ui.app can't break brush_app.ui.ui_process.
- Position
- Below the diagonal: brush_app.ui.app uses a module listed above it, which is the healthy direction.
19→3 brush_app.ui.panels uses brush_process.message✕
- Connections
- 1 pair of types, where a type in brush_app.ui.panels uses a type in brush_process.message.
- The types involved
brush_app.ui.panels.AppPane→brush_process.message.ProcessMessage
- Direction
- brush_app.ui.panels uses brush_process.message, so a change to brush_process.message can break brush_app.ui.panels, while a change to brush_app.ui.panels can't break brush_process.message.
- Position
- Below the diagonal: brush_app.ui.panels uses a module listed above it, which is the healthy direction.
19→16 brush_app.ui.panels uses brush_app.ui.ui_process✕
- Connections
- 1 pair of types, where a type in brush_app.ui.panels uses a type in brush_app.ui.ui_process.
- The types involved
brush_app.ui.panels.AppPane→brush_app.ui.ui_process.UiProcess
- Direction
- brush_app.ui.panels uses brush_app.ui.ui_process, so a change to brush_app.ui.ui_process can break brush_app.ui.panels, while a change to brush_app.ui.panels can't break brush_app.ui.ui_process.
- Position
- Below the diagonal: brush_app.ui.panels uses a module listed above it, which is the healthy direction.
20→14 brush_render uses brush_render.camera✕
- Connections
- 1 pair of types, where a type in brush_render uses a type in brush_render.camera.
- The types involved
brush_render.SplatOps→brush_render.camera.Camera
- Direction
- brush_render uses brush_render.camera, so a change to brush_render.camera can break brush_render, while a change to brush_render can't break brush_render.camera.
- Position
- Below the diagonal: brush_render uses a module listed above it, which is the healthy direction.
20→17 brush_render uses brush_render.gaussian_splats✕
- Connections
- 2 pairs of types, where a type in brush_render uses a type in brush_render.gaussian_splats.
- The types involved
brush_render.SplatOps→brush_render.gaussian_splats.RasterPassbrush_render.SplatOps→brush_render.gaussian_splats.SplatRenderMode
- Direction
- brush_render uses brush_render.gaussian_splats, so a change to brush_render.gaussian_splats can break brush_render, while a change to brush_render can't break brush_render.gaussian_splats.
- Position
- Below the diagonal: brush_render uses a module listed above it, which is the healthy direction.
21→8 brush_render.bwd.burn_glue uses brush_render.kernels.types✕
- Connections
- 2 pairs of types, where a type in brush_render.bwd.burn_glue uses a type in brush_render.kernels.types.
- The types involved
brush_render.bwd.burn_glue.GaussianBackwardState→brush_render.kernels.types.ProjectUniformsbrush_render.bwd.burn_glue.burn_glue$module→brush_render.kernels.types.ProjectUniforms
- Direction
- brush_render.bwd.burn_glue uses brush_render.kernels.types, so a change to brush_render.kernels.types can break brush_render.bwd.burn_glue, while a change to brush_render.bwd.burn_glue can't break brush_render.kernels.types.
- Position
- Below the diagonal: brush_render.bwd.burn_glue uses a module listed above it, which is the healthy direction.
21→14 brush_render.bwd.burn_glue uses brush_render.camera✕
- Connections
- 1 pair of types, where a type in brush_render.bwd.burn_glue uses a type in brush_render.camera.
- The types involved
brush_render.bwd.burn_glue.burn_glue$module→brush_render.camera.Camera
- Direction
- brush_render.bwd.burn_glue uses brush_render.camera, so a change to brush_render.camera can break brush_render.bwd.burn_glue, while a change to brush_render.bwd.burn_glue can't break brush_render.camera.
- Position
- Below the diagonal: brush_render.bwd.burn_glue uses a module listed above it, which is the healthy direction.
21→17 brush_render.bwd.burn_glue uses brush_render.gaussian_splats✕
- Connections
- 5 pairs of types, where a type in brush_render.bwd.burn_glue uses a type in brush_render.gaussian_splats.
- The types involved
brush_render.bwd.burn_glue.GaussianBackwardState→brush_render.gaussian_splats.RasterPassbrush_render.bwd.burn_glue.GaussianBackwardState→brush_render.gaussian_splats.SplatRenderModebrush_render.bwd.burn_glue.burn_glue$module→brush_render.gaussian_splats.RasterPassbrush_render.bwd.burn_glue.burn_glue$module→brush_render.gaussian_splats.SplatRenderModebrush_render.bwd.burn_glue.burn_glue$module→brush_render.gaussian_splats.Splats
- Direction
- brush_render.bwd.burn_glue uses brush_render.gaussian_splats, so a change to brush_render.gaussian_splats can break brush_render.bwd.burn_glue, while a change to brush_render.bwd.burn_glue can't break brush_render.gaussian_splats.
- Position
- Below the diagonal: brush_render.bwd.burn_glue uses a module listed above it, which is the healthy direction.
22→2 brush_train.splat_init uses brush_cube✕
- Connections
- 1 pair of types, where a type in brush_train.splat_init uses a type in brush_cube.
- The types involved
brush_train.splat_init.BallPoint→brush_cube.Vec3A
- Direction
- brush_train.splat_init uses brush_cube, so a change to brush_cube can break brush_train.splat_init, while a change to brush_train.splat_init can't break brush_cube.
- Position
- Below the diagonal: brush_train.splat_init uses a module listed above it, which is the healthy direction.
22→17 brush_train.splat_init uses brush_render.gaussian_splats✕
- Connections
- 2 pairs of types, where a type in brush_train.splat_init uses a type in brush_render.gaussian_splats.
- The types involved
brush_train.splat_init.splat_init$module→brush_render.gaussian_splats.SplatRenderModebrush_train.splat_init.splat_init$module→brush_render.gaussian_splats.Splats
- Direction
- brush_train.splat_init uses brush_render.gaussian_splats, so a change to brush_render.gaussian_splats can break brush_train.splat_init, while a change to brush_train.splat_init can't break brush_render.gaussian_splats.
- Position
- Below the diagonal: brush_train.splat_init uses a module listed above it, which is the healthy direction.
23→3 brush_app.ui.stats uses brush_process.message✕
- Connections
- 1 pair of types, where a type in brush_app.ui.stats uses a type in brush_process.message.
- The types involved
brush_app.ui.stats.StatsPanel→brush_process.message.ProcessMessage
- Direction
- brush_app.ui.stats uses brush_process.message, so a change to brush_process.message can break brush_app.ui.stats, while a change to brush_app.ui.stats can't break brush_process.message.
- Position
- Below the diagonal: brush_app.ui.stats uses a module listed above it, which is the healthy direction.
23→16 brush_app.ui.stats uses brush_app.ui.ui_process✕
- Connections
- 1 pair of types, where a type in brush_app.ui.stats uses a type in brush_app.ui.ui_process.
- The types involved
brush_app.ui.stats.StatsPanel→brush_app.ui.ui_process.UiProcess
- Direction
- brush_app.ui.stats uses brush_app.ui.ui_process, so a change to brush_app.ui.ui_process can break brush_app.ui.stats, while a change to brush_app.ui.stats can't break brush_app.ui.ui_process.
- Position
- Below the diagonal: brush_app.ui.stats uses a module listed above it, which is the healthy direction.
23→19 brush_app.ui.stats uses brush_app.ui.panels✕
- Connections
- 1 pair of types, where a type in brush_app.ui.stats uses a type in brush_app.ui.panels.
- The types involved
brush_app.ui.stats.StatsPanel→brush_app.ui.panels.AppPane
- Direction
- brush_app.ui.stats uses brush_app.ui.panels, so a change to brush_app.ui.panels can break brush_app.ui.stats, while a change to brush_app.ui.stats can't break brush_app.ui.panels.
- Position
- Below the diagonal: brush_app.ui.stats uses a module listed above it, which is the healthy direction.
24→20 brush_dataset.config uses brush_render✕
- Connections
- 1 pair of types, where a type in brush_dataset.config uses a type in brush_render.
- The types involved
brush_dataset.config.LoadDatasetConfig→brush_render.AlphaMode
- Direction
- brush_dataset.config uses brush_render, so a change to brush_render can break brush_dataset.config, while a change to brush_dataset.config can't break brush_render.
- Position
- Below the diagonal: brush_dataset.config uses a module listed above it, which is the healthy direction.
25→5 brush_dataset.load_image uses brush_vfs✕
- Connections
- 1 pair of types, where a type in brush_dataset.load_image uses a type in brush_vfs.
- The types involved
brush_dataset.load_image.LoadImage→brush_vfs.BrushVfs
- Direction
- brush_dataset.load_image uses brush_vfs, so a change to brush_vfs can break brush_dataset.load_image, while a change to brush_dataset.load_image can't break brush_vfs.
- Position
- Below the diagonal: brush_dataset.load_image uses a module listed above it, which is the healthy direction.
25→20 brush_dataset.load_image uses brush_render✕
- Connections
- 1 pair of types, where a type in brush_dataset.load_image uses a type in brush_render.
- The types involved
brush_dataset.load_image.LoadImage→brush_render.AlphaMode
- Direction
- brush_dataset.load_image uses brush_render, so a change to brush_render can break brush_dataset.load_image, while a change to brush_dataset.load_image can't break brush_render.
- Position
- Below the diagonal: brush_dataset.load_image uses a module listed above it, which is the healthy direction.
26→14 brush_train.eval uses brush_render.camera✕
- Connections
- 1 pair of types, where a type in brush_train.eval uses a type in brush_render.camera.
- The types involved
brush_train.eval.eval$module→brush_render.camera.Camera
- Direction
- brush_train.eval uses brush_render.camera, so a change to brush_render.camera can break brush_train.eval, while a change to brush_train.eval can't break brush_render.camera.
- Position
- Below the diagonal: brush_train.eval uses a module listed above it, which is the healthy direction.
26→17 brush_train.eval uses brush_render.gaussian_splats✕
- Connections
- 1 pair of types, where a type in brush_train.eval uses a type in brush_render.gaussian_splats.
- The types involved
brush_train.eval.eval$module→brush_render.gaussian_splats.Splats
- Direction
- brush_train.eval uses brush_render.gaussian_splats, so a change to brush_render.gaussian_splats can break brush_train.eval, while a change to brush_train.eval can't break brush_render.gaussian_splats.
- Position
- Below the diagonal: brush_train.eval uses a module listed above it, which is the healthy direction.
26→20 brush_train.eval uses brush_render✕
- Connections
- 1 pair of types, where a type in brush_train.eval uses a type in brush_render.
- The types involved
brush_train.eval.eval$module→brush_render.AlphaMode
- Direction
- brush_train.eval uses brush_render, so a change to brush_render can break brush_train.eval, while a change to brush_train.eval can't break brush_render.
- Position
- Below the diagonal: brush_train.eval uses a module listed above it, which is the healthy direction.
27→5 brush_dataset.formats.colmap uses brush_vfs✕
- Connections
- 1 pair of types, where a type in brush_dataset.formats.colmap uses a type in brush_vfs.
- The types involved
brush_dataset.formats.colmap.colmap$module→brush_vfs.BrushVfs
- Direction
- brush_dataset.formats.colmap uses brush_vfs, so a change to brush_vfs can break brush_dataset.formats.colmap, while a change to brush_dataset.formats.colmap can't break brush_vfs.
- Position
- Below the diagonal: brush_dataset.formats.colmap uses a module listed above it, which is the healthy direction.
27→10 brush_dataset.formats.colmap uses brush_render.kernels.camera_model✕
- Connections
- 1 pair of types, where a type in brush_dataset.formats.colmap uses a type in brush_render.kernels.camera_model.
- The types involved
brush_dataset.formats.colmap.colmap$module→brush_render.kernels.camera_model.CameraModel
- Direction
- brush_dataset.formats.colmap uses brush_render.kernels.camera_model, so a change to brush_render.kernels.camera_model can break brush_dataset.formats.colmap, while a change to brush_dataset.formats.colmap can't break brush_render.kernels.camera_model.
- Position
- Below the diagonal: brush_dataset.formats.colmap uses a module listed above it, which is the healthy direction.
27→24 brush_dataset.formats.colmap uses brush_dataset.config✕
- Connections
- 1 pair of types, where a type in brush_dataset.formats.colmap uses a type in brush_dataset.config.
- The types involved
brush_dataset.formats.colmap.colmap$module→brush_dataset.config.LoadDatasetConfig
- Direction
- brush_dataset.formats.colmap uses brush_dataset.config, so a change to brush_dataset.config can break brush_dataset.formats.colmap, while a change to brush_dataset.formats.colmap can't break brush_dataset.config.
- Position
- Below the diagonal: brush_dataset.formats.colmap uses a module listed above it, which is the healthy direction.
28→5 brush_dataset.formats.realitycapture uses brush_vfs✕
- Connections
- 1 pair of types, where a type in brush_dataset.formats.realitycapture uses a type in brush_vfs.
- The types involved
brush_dataset.formats.realitycapture.realitycapture$module→brush_vfs.BrushVfs
- Direction
- brush_dataset.formats.realitycapture uses brush_vfs, so a change to brush_vfs can break brush_dataset.formats.realitycapture, while a change to brush_dataset.formats.realitycapture can't break brush_vfs.
- Position
- Below the diagonal: brush_dataset.formats.realitycapture uses a module listed above it, which is the healthy direction.
28→10 brush_dataset.formats.realitycapture uses brush_render.kernels.camera_model✕
- Connections
- 1 pair of types, where a type in brush_dataset.formats.realitycapture uses a type in brush_render.kernels.camera_model.
- The types involved
brush_dataset.formats.realitycapture.realitycapture$module→brush_render.kernels.camera_model.CameraModel
- Direction
- brush_dataset.formats.realitycapture uses brush_render.kernels.camera_model, so a change to brush_render.kernels.camera_model can break brush_dataset.formats.realitycapture, while a change to brush_dataset.formats.realitycapture can't break brush_render.kernels.camera_model.
- Position
- Below the diagonal: brush_dataset.formats.realitycapture uses a module listed above it, which is the healthy direction.
28→14 brush_dataset.formats.realitycapture uses brush_render.camera✕
- Connections
- 1 pair of types, where a type in brush_dataset.formats.realitycapture uses a type in brush_render.camera.
- The types involved
brush_dataset.formats.realitycapture.realitycapture$module→brush_render.camera.Camera
- Direction
- brush_dataset.formats.realitycapture uses brush_render.camera, so a change to brush_render.camera can break brush_dataset.formats.realitycapture, while a change to brush_dataset.formats.realitycapture can't break brush_render.camera.
- Position
- Below the diagonal: brush_dataset.formats.realitycapture uses a module listed above it, which is the healthy direction.
28→24 brush_dataset.formats.realitycapture uses brush_dataset.config✕
- Connections
- 1 pair of types, where a type in brush_dataset.formats.realitycapture uses a type in brush_dataset.config.
- The types involved
brush_dataset.formats.realitycapture.realitycapture$module→brush_dataset.config.LoadDatasetConfig
- Direction
- brush_dataset.formats.realitycapture uses brush_dataset.config, so a change to brush_dataset.config can break brush_dataset.formats.realitycapture, while a change to brush_dataset.formats.realitycapture can't break brush_dataset.config.
- Position
- Below the diagonal: brush_dataset.formats.realitycapture uses a module listed above it, which is the healthy direction.
29→14 brush_dataset.scene uses brush_render.camera✕
- Connections
- 2 pairs of types, where a type in brush_dataset.scene uses a type in brush_render.camera.
- The types involved
brush_dataset.scene.SceneBatch→brush_render.camera.Camerabrush_dataset.scene.SceneView→brush_render.camera.Camera
- Direction
- brush_dataset.scene uses brush_render.camera, so a change to brush_render.camera can break brush_dataset.scene, while a change to brush_dataset.scene can't break brush_render.camera.
- Position
- Below the diagonal: brush_dataset.scene uses a module listed above it, which is the healthy direction.
29→20 brush_dataset.scene uses brush_render✕
- Connections
- 2 pairs of types, where a type in brush_dataset.scene uses a type in brush_render.
- The types involved
brush_dataset.scene.SceneBatch→brush_render.AlphaModebrush_dataset.scene.scene$module→brush_render.AlphaMode
- Direction
- brush_dataset.scene uses brush_render, so a change to brush_render can break brush_dataset.scene, while a change to brush_dataset.scene can't break brush_render.
- Position
- Below the diagonal: brush_dataset.scene uses a module listed above it, which is the healthy direction.
29→25 brush_dataset.scene uses brush_dataset.load_image✕
- Connections
- 1 pair of types, where a type in brush_dataset.scene uses a type in brush_dataset.load_image.
- The types involved
brush_dataset.scene.SceneView→brush_dataset.load_image.LoadImage
- Direction
- brush_dataset.scene uses brush_dataset.load_image, so a change to brush_dataset.load_image can break brush_dataset.scene, while a change to brush_dataset.scene can't break brush_dataset.load_image.
- Position
- Below the diagonal: brush_dataset.scene uses a module listed above it, which is the healthy direction.
30→24 brush_process.config uses brush_dataset.config✕
- Connections
- 2 pairs of types, where a type in brush_process.config uses a type in brush_dataset.config.
- The types involved
brush_process.config.TrainStreamConfig→brush_dataset.config.LoadDatasetConfigbrush_process.config.TrainStreamConfig→brush_dataset.config.ModelConfig
- Direction
- brush_process.config uses brush_dataset.config, so a change to brush_dataset.config can break brush_process.config, while a change to brush_process.config can't break brush_dataset.config.
- Position
- Below the diagonal: brush_process.config uses a module listed above it, which is the healthy direction.
31→3 brush_app.ui.settings_panel uses brush_process.message✕
- Connections
- 1 pair of types, where a type in brush_app.ui.settings_panel uses a type in brush_process.message.
- The types involved
brush_app.ui.settings_panel.SettingsPanel→brush_process.message.ProcessMessage
- Direction
- brush_app.ui.settings_panel uses brush_process.message, so a change to brush_process.message can break brush_app.ui.settings_panel, while a change to brush_app.ui.settings_panel can't break brush_process.message.
- Position
- Below the diagonal: brush_app.ui.settings_panel uses a module listed above it, which is the healthy direction.
31→16 brush_app.ui.settings_panel uses brush_app.ui.ui_process✕
- Connections
- 1 pair of types, where a type in brush_app.ui.settings_panel uses a type in brush_app.ui.ui_process.
- The types involved
brush_app.ui.settings_panel.SettingsPanel→brush_app.ui.ui_process.UiProcess
- Direction
- brush_app.ui.settings_panel uses brush_app.ui.ui_process, so a change to brush_app.ui.ui_process can break brush_app.ui.settings_panel, while a change to brush_app.ui.settings_panel can't break brush_app.ui.ui_process.
- Position
- Below the diagonal: brush_app.ui.settings_panel uses a module listed above it, which is the healthy direction.
31→19 brush_app.ui.settings_panel uses brush_app.ui.panels✕
- Connections
- 1 pair of types, where a type in brush_app.ui.settings_panel uses a type in brush_app.ui.panels.
- The types involved
brush_app.ui.settings_panel.SettingsPanel→brush_app.ui.panels.AppPane
- Direction
- brush_app.ui.settings_panel uses brush_app.ui.panels, so a change to brush_app.ui.panels can break brush_app.ui.settings_panel, while a change to brush_app.ui.settings_panel can't break brush_app.ui.panels.
- Position
- Below the diagonal: brush_app.ui.settings_panel uses a module listed above it, which is the healthy direction.
31→30 brush_app.ui.settings_panel uses brush_process.config✕
- Connections
- 1 pair of types, where a type in brush_app.ui.settings_panel uses a type in brush_process.config.
- The types involved
brush_app.ui.settings_panel.SettingsPanel→brush_process.config.TrainStreamConfig
- Direction
- brush_app.ui.settings_panel uses brush_process.config, so a change to brush_process.config can break brush_app.ui.settings_panel, while a change to brush_app.ui.settings_panel can't break brush_process.config.
- Position
- Below the diagonal: brush_app.ui.settings_panel uses a module listed above it, which is the healthy direction.
32→1 brush_app.ui.training_panel uses brush_async.native✕
- Connections
- 1 pair of types, where a type in brush_app.ui.training_panel uses a type in brush_async.native.
- The types involved
brush_app.ui.training_panel.TrainingPanel→brush_async.native.Actor
- Direction
- brush_app.ui.training_panel uses brush_async.native, so a change to brush_async.native can break brush_app.ui.training_panel, while a change to brush_app.ui.training_panel can't break brush_async.native.
- Position
- Below the diagonal: brush_app.ui.training_panel uses a module listed above it, which is the healthy direction.
32→3 brush_app.ui.training_panel uses brush_process.message✕
- Connections
- 2 pairs of types, where a type in brush_app.ui.training_panel uses a type in brush_process.message.
- The types involved
brush_app.ui.training_panel.TrainingPanel→brush_process.message.ProcessMessagebrush_app.ui.training_panel.TrainingPanel→brush_process.message.TrainMessage
- Direction
- brush_app.ui.training_panel uses brush_process.message, so a change to brush_process.message can break brush_app.ui.training_panel, while a change to brush_app.ui.training_panel can't break brush_process.message.
- Position
- Below the diagonal: brush_app.ui.training_panel uses a module listed above it, which is the healthy direction.
32→16 brush_app.ui.training_panel uses brush_app.ui.ui_process✕
- Connections
- 1 pair of types, where a type in brush_app.ui.training_panel uses a type in brush_app.ui.ui_process.
- The types involved
brush_app.ui.training_panel.TrainingPanel→brush_app.ui.ui_process.UiProcess
- Direction
- brush_app.ui.training_panel uses brush_app.ui.ui_process, so a change to brush_app.ui.ui_process can break brush_app.ui.training_panel, while a change to brush_app.ui.training_panel can't break brush_app.ui.ui_process.
- Position
- Below the diagonal: brush_app.ui.training_panel uses a module listed above it, which is the healthy direction.
32→17 brush_app.ui.training_panel uses brush_render.gaussian_splats✕
- Connections
- 1 pair of types, where a type in brush_app.ui.training_panel uses a type in brush_render.gaussian_splats.
- The types involved
brush_app.ui.training_panel.training_panel$module→brush_render.gaussian_splats.Splats
- Direction
- brush_app.ui.training_panel uses brush_render.gaussian_splats, so a change to brush_render.gaussian_splats can break brush_app.ui.training_panel, while a change to brush_app.ui.training_panel can't break brush_render.gaussian_splats.
- Position
- Below the diagonal: brush_app.ui.training_panel uses a module listed above it, which is the healthy direction.
32→19 brush_app.ui.training_panel uses brush_app.ui.panels✕
- Connections
- 1 pair of types, where a type in brush_app.ui.training_panel uses a type in brush_app.ui.panels.
- The types involved
brush_app.ui.training_panel.TrainingPanel→brush_app.ui.panels.AppPane
- Direction
- brush_app.ui.training_panel uses brush_app.ui.panels, so a change to brush_app.ui.panels can break brush_app.ui.training_panel, while a change to brush_app.ui.training_panel can't break brush_app.ui.panels.
- Position
- Below the diagonal: brush_app.ui.training_panel uses a module listed above it, which is the healthy direction.
32→30 brush_app.ui.training_panel uses brush_process.config✕
- Connections
- 1 pair of types, where a type in brush_app.ui.training_panel uses a type in brush_process.config.
- The types involved
brush_app.ui.training_panel.TrainingPanel→brush_process.config.TrainStreamConfig
- Direction
- brush_app.ui.training_panel uses brush_process.config, so a change to brush_process.config can break brush_app.ui.training_panel, while a change to brush_app.ui.training_panel can't break brush_process.config.
- Position
- Below the diagonal: brush_app.ui.training_panel uses a module listed above it, which is the healthy direction.
33→2 brush_dataset uses brush_cube✕
- Connections
- 1 pair of types, where a type in brush_dataset uses a type in brush_cube.
- The types involved
brush_dataset.brush_dataset$module→brush_cube.Mat3
- Direction
- brush_dataset uses brush_cube, so a change to brush_cube can break brush_dataset, while a change to brush_dataset can't break brush_cube.
- Position
- Below the diagonal: brush_dataset uses a module listed above it, which is the healthy direction.
33→29 brush_dataset uses brush_dataset.scene✕
- Connections
- 2 pairs of types, where a type in brush_dataset uses a type in brush_dataset.scene.
- The types involved
brush_dataset.Dataset→brush_dataset.scene.Scenebrush_dataset.Dataset→brush_dataset.scene.SceneView
- Direction
- brush_dataset uses brush_dataset.scene, so a change to brush_dataset.scene can break brush_dataset, while a change to brush_dataset can't break brush_dataset.scene.
- Position
- Below the diagonal: brush_dataset uses a module listed above it, which is the healthy direction.
34→3 brush_js uses brush_process.message✕
- Connections
- 1 pair of types, where a type in brush_js uses a type in brush_process.message.
- The types involved
brush_js.BrushMessage→brush_process.message.ProcessMessage
- Direction
- brush_js uses brush_process.message, so a change to brush_process.message can break brush_js, while a change to brush_js can't break brush_process.message.
- Position
- Below the diagonal: brush_js uses a module listed above it, which is the healthy direction.
34→4 brush_js uses brush_process.slot✕
- Connections
- 1 pair of types, where a type in brush_js uses a type in brush_process.slot.
- The types involved
brush_js.Training→brush_process.slot.Slot
- Direction
- brush_js uses brush_process.slot, so a change to brush_process.slot can break brush_js, while a change to brush_js can't break brush_process.slot.
- Position
- Below the diagonal: brush_js uses a module listed above it, which is the healthy direction.
34→17 brush_js uses brush_render.gaussian_splats✕
- Connections
- 1 pair of types, where a type in brush_js uses a type in brush_render.gaussian_splats.
- The types involved
brush_js.BrushSplats→brush_render.gaussian_splats.Splats
- Direction
- brush_js uses brush_render.gaussian_splats, so a change to brush_render.gaussian_splats can break brush_js, while a change to brush_js can't break brush_render.gaussian_splats.
- Position
- Below the diagonal: brush_js uses a module listed above it, which is the healthy direction.
34→30 brush_js uses brush_process.config✕
- Connections
- 1 pair of types, where a type in brush_js uses a type in brush_process.config.
- The types involved
brush_js.brush_js$module→brush_process.config.TrainStreamConfig
- Direction
- brush_js uses brush_process.config, so a change to brush_process.config can break brush_js, while a change to brush_js can't break brush_process.config.
- Position
- Below the diagonal: brush_js uses a module listed above it, which is the healthy direction.
35→17 brush_rerun.visualize_tools uses brush_render.gaussian_splats✕
- Connections
- 1 pair of types, where a type in brush_rerun.visualize_tools uses a type in brush_render.gaussian_splats.
- The types involved
brush_rerun.visualize_tools.VisualizeTools→brush_render.gaussian_splats.Splats
- Direction
- brush_rerun.visualize_tools uses brush_render.gaussian_splats, so a change to brush_render.gaussian_splats can break brush_rerun.visualize_tools, while a change to brush_rerun.visualize_tools can't break brush_render.gaussian_splats.
- Position
- Below the diagonal: brush_rerun.visualize_tools uses a module listed above it, which is the healthy direction.
35→26 brush_rerun.visualize_tools uses brush_train.eval✕
- Connections
- 1 pair of types, where a type in brush_rerun.visualize_tools uses a type in brush_train.eval.
- The types involved
brush_rerun.visualize_tools.VisualizeTools→brush_train.eval.EvalSample
- Direction
- brush_rerun.visualize_tools uses brush_train.eval, so a change to brush_train.eval can break brush_rerun.visualize_tools, while a change to brush_rerun.visualize_tools can't break brush_train.eval.
- Position
- Below the diagonal: brush_rerun.visualize_tools uses a module listed above it, which is the healthy direction.
35→29 brush_rerun.visualize_tools uses brush_dataset.scene✕
- Connections
- 1 pair of types, where a type in brush_rerun.visualize_tools uses a type in brush_dataset.scene.
- The types involved
brush_rerun.visualize_tools.VisualizeTools→brush_dataset.scene.Scene
- Direction
- brush_rerun.visualize_tools uses brush_dataset.scene, so a change to brush_dataset.scene can break brush_rerun.visualize_tools, while a change to brush_rerun.visualize_tools can't break brush_dataset.scene.
- Position
- Below the diagonal: brush_rerun.visualize_tools uses a module listed above it, which is the healthy direction.
36→17 brush_train.train uses brush_render.gaussian_splats✕
- Connections
- 2 pairs of types, where a type in brush_train.train uses a type in brush_render.gaussian_splats.
- The types involved
brush_train.train.SplatTrainer→brush_render.gaussian_splats.Splatsbrush_train.train.train$module→brush_render.gaussian_splats.Splats
- Direction
- brush_train.train uses brush_render.gaussian_splats, so a change to brush_render.gaussian_splats can break brush_train.train, while a change to brush_train.train can't break brush_render.gaussian_splats.
- Position
- Below the diagonal: brush_train.train uses a module listed above it, which is the healthy direction.
36→29 brush_train.train uses brush_dataset.scene✕
- Connections
- 1 pair of types, where a type in brush_train.train uses a type in brush_dataset.scene.
- The types involved
brush_train.train.SplatTrainer→brush_dataset.scene.SceneBatch
- Direction
- brush_train.train uses brush_dataset.scene, so a change to brush_dataset.scene can break brush_train.train, while a change to brush_train.train can't break brush_dataset.scene.
- Position
- Below the diagonal: brush_train.train uses a module listed above it, which is the healthy direction.
37→1 brush_app.ui.datasets uses brush_async.native✕
- Connections
- 1 pair of types, where a type in brush_app.ui.datasets uses a type in brush_async.native.
- The types involved
brush_app.ui.datasets.PreviewLoader→brush_async.native.Actor
- Direction
- brush_app.ui.datasets uses brush_async.native, so a change to brush_async.native can break brush_app.ui.datasets, while a change to brush_app.ui.datasets can't break brush_async.native.
- Position
- Below the diagonal: brush_app.ui.datasets uses a module listed above it, which is the healthy direction.
37→3 brush_app.ui.datasets uses brush_process.message✕
- Connections
- 1 pair of types, where a type in brush_app.ui.datasets uses a type in brush_process.message.
- The types involved
brush_app.ui.datasets.DatasetPanel→brush_process.message.ProcessMessage
- Direction
- brush_app.ui.datasets uses brush_process.message, so a change to brush_process.message can break brush_app.ui.datasets, while a change to brush_app.ui.datasets can't break brush_process.message.
- Position
- Below the diagonal: brush_app.ui.datasets uses a module listed above it, which is the healthy direction.
37→16 brush_app.ui.datasets uses brush_app.ui.ui_process✕
- Connections
- 3 pairs of types, where a type in brush_app.ui.datasets uses a type in brush_app.ui.ui_process.
- The types involved
brush_app.ui.datasets.DatasetPanel→brush_app.ui.ui_process.UiProcessbrush_app.ui.datasets.PreviewLoader→brush_app.ui.ui_process.TexHandlebrush_app.ui.datasets.datasets$module→brush_app.ui.ui_process.TexHandle
- Direction
- brush_app.ui.datasets uses brush_app.ui.ui_process, so a change to brush_app.ui.ui_process can break brush_app.ui.datasets, while a change to brush_app.ui.datasets can't break brush_app.ui.ui_process.
- Position
- Below the diagonal: brush_app.ui.datasets uses a module listed above it, which is the healthy direction.
37→19 brush_app.ui.datasets uses brush_app.ui.panels✕
- Connections
- 1 pair of types, where a type in brush_app.ui.datasets uses a type in brush_app.ui.panels.
- The types involved
brush_app.ui.datasets.DatasetPanel→brush_app.ui.panels.AppPane
- Direction
- brush_app.ui.datasets uses brush_app.ui.panels, so a change to brush_app.ui.panels can break brush_app.ui.datasets, while a change to brush_app.ui.datasets can't break brush_app.ui.panels.
- Position
- Below the diagonal: brush_app.ui.datasets uses a module listed above it, which is the healthy direction.
37→25 brush_app.ui.datasets uses brush_dataset.load_image✕
- Connections
- 1 pair of types, where a type in brush_app.ui.datasets uses a type in brush_dataset.load_image.
- The types involved
brush_app.ui.datasets.PreviewLoader→brush_dataset.load_image.LoadImage
- Direction
- brush_app.ui.datasets uses brush_dataset.load_image, so a change to brush_dataset.load_image can break brush_app.ui.datasets, while a change to brush_app.ui.datasets can't break brush_dataset.load_image.
- Position
- Below the diagonal: brush_app.ui.datasets uses a module listed above it, which is the healthy direction.
37→29 brush_app.ui.datasets uses brush_dataset.scene✕
- Connections
- 6 pairs of types, where a type in brush_app.ui.datasets uses a type in brush_dataset.scene.
- The types involved
brush_app.ui.datasets.DatasetPanel→brush_dataset.scene.ViewTypebrush_app.ui.datasets.PreviewJob→brush_dataset.scene.SceneViewbrush_app.ui.datasets.PreviewLoader→brush_dataset.scene.SceneViewbrush_app.ui.datasets.datasets$module→brush_dataset.scene.Scenebrush_app.ui.datasets.datasets$module→brush_dataset.scene.SceneViewbrush_app.ui.datasets.datasets$module→brush_dataset.scene.ViewType
- Direction
- brush_app.ui.datasets uses brush_dataset.scene, so a change to brush_dataset.scene can break brush_app.ui.datasets, while a change to brush_app.ui.datasets can't break brush_dataset.scene.
- Position
- Below the diagonal: brush_app.ui.datasets uses a module listed above it, which is the healthy direction.
37→33 brush_app.ui.datasets uses brush_dataset✕
- Connections
- 2 pairs of types, where a type in brush_app.ui.datasets uses a type in brush_dataset.
- The types involved
brush_app.ui.datasets.DatasetPanel→brush_dataset.Datasetbrush_app.ui.datasets.datasets$module→brush_dataset.Dataset
- Direction
- brush_app.ui.datasets uses brush_dataset, so a change to brush_dataset can break brush_app.ui.datasets, while a change to brush_app.ui.datasets can't break brush_dataset.
- Position
- Below the diagonal: brush_app.ui.datasets uses a module listed above it, which is the healthy direction.
38→3 brush_app.ui.scene uses brush_process.message✕
- Connections
- 1 pair of types, where a type in brush_app.ui.scene uses a type in brush_process.message.
- The types involved
brush_app.ui.scene.ScenePanel→brush_process.message.ProcessMessage
- Direction
- brush_app.ui.scene uses brush_process.message, so a change to brush_process.message can break brush_app.ui.scene, while a change to brush_app.ui.scene can't break brush_process.message.
- Position
- Below the diagonal: brush_app.ui.scene uses a module listed above it, which is the healthy direction.
38→14 brush_app.ui.scene uses brush_render.camera✕
- Connections
- 1 pair of types, where a type in brush_app.ui.scene uses a type in brush_render.camera.
- The types involved
brush_app.ui.scene.ScenePanel→brush_render.camera.Camera
- Direction
- brush_app.ui.scene uses brush_render.camera, so a change to brush_render.camera can break brush_app.ui.scene, while a change to brush_app.ui.scene can't break brush_render.camera.
- Position
- Below the diagonal: brush_app.ui.scene uses a module listed above it, which is the healthy direction.
38→15 brush_app.ui.scene uses brush_app.ui.splat_backbuffer✕
- Connections
- 1 pair of types, where a type in brush_app.ui.scene uses a type in brush_app.ui.splat_backbuffer.
- The types involved
brush_app.ui.scene.ScenePanel→brush_app.ui.splat_backbuffer.SplatBackbuffer
- Direction
- brush_app.ui.scene uses brush_app.ui.splat_backbuffer, so a change to brush_app.ui.splat_backbuffer can break brush_app.ui.scene, while a change to brush_app.ui.scene can't break brush_app.ui.splat_backbuffer.
- Position
- Below the diagonal: brush_app.ui.scene uses a module listed above it, which is the healthy direction.
38→16 brush_app.ui.scene uses brush_app.ui.ui_process✕
- Connections
- 1 pair of types, where a type in brush_app.ui.scene uses a type in brush_app.ui.ui_process.
- The types involved
brush_app.ui.scene.ScenePanel→brush_app.ui.ui_process.UiProcess
- Direction
- brush_app.ui.scene uses brush_app.ui.ui_process, so a change to brush_app.ui.ui_process can break brush_app.ui.scene, while a change to brush_app.ui.scene can't break brush_app.ui.ui_process.
- Position
- Below the diagonal: brush_app.ui.scene uses a module listed above it, which is the healthy direction.
38→19 brush_app.ui.scene uses brush_app.ui.panels✕
- Connections
- 1 pair of types, where a type in brush_app.ui.scene uses a type in brush_app.ui.panels.
- The types involved
brush_app.ui.scene.ScenePanel→brush_app.ui.panels.AppPane
- Direction
- brush_app.ui.scene uses brush_app.ui.panels, so a change to brush_app.ui.panels can break brush_app.ui.scene, while a change to brush_app.ui.scene can't break brush_app.ui.panels.
- Position
- Below the diagonal: brush_app.ui.scene uses a module listed above it, which is the healthy direction.
38→33 brush_app.ui.scene uses brush_dataset✕
- Connections
- 1 pair of types, where a type in brush_app.ui.scene uses a type in brush_dataset.
- The types involved
brush_app.ui.scene.ScenePanel→brush_dataset.Dataset
- Direction
- brush_app.ui.scene uses brush_dataset, so a change to brush_dataset can break brush_app.ui.scene, while a change to brush_app.ui.scene can't break brush_dataset.
- Position
- Below the diagonal: brush_app.ui.scene uses a module listed above it, which is the healthy direction.
39→5 brush_dataset.formats uses brush_vfs✕
- Connections
- 1 pair of types, where a type in brush_dataset.formats uses a type in brush_vfs.
- The types involved
brush_dataset.formats.formats$module→brush_vfs.BrushVfs
- Direction
- brush_dataset.formats uses brush_vfs, so a change to brush_vfs can break brush_dataset.formats, while a change to brush_dataset.formats can't break brush_vfs.
- Position
- Below the diagonal: brush_dataset.formats uses a module listed above it, which is the healthy direction.
39→24 brush_dataset.formats uses brush_dataset.config✕
- Connections
- 1 pair of types, where a type in brush_dataset.formats uses a type in brush_dataset.config.
- The types involved
brush_dataset.formats.formats$module→brush_dataset.config.LoadDatasetConfig
- Direction
- brush_dataset.formats uses brush_dataset.config, so a change to brush_dataset.config can break brush_dataset.formats, while a change to brush_dataset.formats can't break brush_dataset.config.
- Position
- Below the diagonal: brush_dataset.formats uses a module listed above it, which is the healthy direction.
39→29 brush_dataset.formats uses brush_dataset.scene✕
- Connections
- 1 pair of types, where a type in brush_dataset.formats uses a type in brush_dataset.scene.
- The types involved
brush_dataset.formats.formats$module→brush_dataset.scene.SceneView
- Direction
- brush_dataset.formats uses brush_dataset.scene, so a change to brush_dataset.scene can break brush_dataset.formats, while a change to brush_dataset.formats can't break brush_dataset.scene.
- Position
- Below the diagonal: brush_dataset.formats uses a module listed above it, which is the healthy direction.
39→33 brush_dataset.formats uses brush_dataset✕
- Connections
- 1 pair of types, where a type in brush_dataset.formats uses a type in brush_dataset.
- The types involved
brush_dataset.formats.DatasetLoadResult→brush_dataset.Dataset
- Direction
- brush_dataset.formats uses brush_dataset, so a change to brush_dataset can break brush_dataset.formats, while a change to brush_dataset.formats can't break brush_dataset.
- Position
- Below the diagonal: brush_dataset.formats uses a module listed above it, which is the healthy direction.
40→4 brush_process.train_stream uses brush_process.slot✕
- Connections
- 1 pair of types, where a type in brush_process.train_stream uses a type in brush_process.slot.
- The types involved
brush_process.train_stream.train_stream$module→brush_process.slot.SlotSender
- Direction
- brush_process.train_stream uses brush_process.slot, so a change to brush_process.slot can break brush_process.train_stream, while a change to brush_process.train_stream can't break brush_process.slot.
- Position
- Below the diagonal: brush_process.train_stream uses a module listed above it, which is the healthy direction.
40→5 brush_process.train_stream uses brush_vfs✕
- Connections
- 1 pair of types, where a type in brush_process.train_stream uses a type in brush_vfs.
- The types involved
brush_process.train_stream.train_stream$module→brush_vfs.BrushVfs
- Direction
- brush_process.train_stream uses brush_vfs, so a change to brush_vfs can break brush_process.train_stream, while a change to brush_process.train_stream can't break brush_vfs.
- Position
- Below the diagonal: brush_process.train_stream uses a module listed above it, which is the healthy direction.
40→17 brush_process.train_stream uses brush_render.gaussian_splats✕
- Connections
- 1 pair of types, where a type in brush_process.train_stream uses a type in brush_render.gaussian_splats.
- The types involved
brush_process.train_stream.train_stream$module→brush_render.gaussian_splats.Splats
- Direction
- brush_process.train_stream uses brush_render.gaussian_splats, so a change to brush_render.gaussian_splats can break brush_process.train_stream, while a change to brush_process.train_stream can't break brush_render.gaussian_splats.
- Position
- Below the diagonal: brush_process.train_stream uses a module listed above it, which is the healthy direction.
40→29 brush_process.train_stream uses brush_dataset.scene✕
- Connections
- 1 pair of types, where a type in brush_process.train_stream uses a type in brush_dataset.scene.
- The types involved
brush_process.train_stream.train_stream$module→brush_dataset.scene.Scene
- Direction
- brush_process.train_stream uses brush_dataset.scene, so a change to brush_dataset.scene can break brush_process.train_stream, while a change to brush_process.train_stream can't break brush_dataset.scene.
- Position
- Below the diagonal: brush_process.train_stream uses a module listed above it, which is the healthy direction.
40→30 brush_process.train_stream uses brush_process.config✕
- Connections
- 1 pair of types, where a type in brush_process.train_stream uses a type in brush_process.config.
- The types involved
brush_process.train_stream.train_stream$module→brush_process.config.TrainStreamConfig
- Direction
- brush_process.train_stream uses brush_process.config, so a change to brush_process.config can break brush_process.train_stream, while a change to brush_process.train_stream can't break brush_process.config.
- Position
- Below the diagonal: brush_process.train_stream uses a module listed above it, which is the healthy direction.
40→35 brush_process.train_stream uses brush_rerun.visualize_tools✕
- Connections
- 1 pair of types, where a type in brush_process.train_stream uses a type in brush_rerun.visualize_tools.
- The types involved
brush_process.train_stream.train_stream$module→brush_rerun.visualize_tools.VisualizeTools
- Direction
- brush_process.train_stream uses brush_rerun.visualize_tools, so a change to brush_rerun.visualize_tools can break brush_process.train_stream, while a change to brush_process.train_stream can't break brush_rerun.visualize_tools.
- Position
- Below the diagonal: brush_process.train_stream uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 51 | High / Critical |
| A05:2025 — Injection | 36 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | Medium |
Roadmap
First, ensure all media elements have appropriate text alternatives and captions to support users with disabilities. Second, integrate accessibility checks into your development toolchain and CI pipeline to enforce standards automatically. Third, correct page structure issues by adding proper language attributes, titles, and landmarks while maintaining logical heading order. Finally, establish a practice of documenting significant architectural decisions to improve long-term codebase understanding and maintainability.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +10.0 pts | Medium | Text alternatives |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.4 pts | Low | ADR Quality |
| Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI. | +5.9 pts | Medium | A11y enforcement |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +4.8 pts | Medium | Page structure |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.2 pts | Medium | Architecture documentation |
| 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.5 pts | Medium | Documentation (README) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.5 pts | Low | Static Analysis (SAST) |
| Resolve the 19 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (19). | +0.9 pts | Medium | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| apps/brush-app/src/ui/scene.rs | 5.5 | Mixed | Cyclomatic Complexity: ScenePanel::ui (cyclomatic 21) |
| crates/brush-train/src/train.rs | 5.6 | Mixed | Cognitive Complexity: SplatTrainer::refine (cognitive 22) |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| crates/brush-process/src/train_stream.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/colmap-reader/src/lib.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/brush-vfs/src/data_source.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| crates/brush-loss/src/lib.rs | 7.0 | Near-clean | Cyclomatic Complexity: brush_loss::kernels::image_loss_backward_kernel (cyclomatic 35) |
| crates/brush-dataset/src/formats/colmap.rs | 7.0 | Near-clean | God Classes: FunctionTooLong: brush_dataset::formats::colmap::load_dataset_inner |
| crates/brush-render/src/kernels/sh.rs | 7.0 | Near-clean | God Classes: FunctionTooLong: brush_render::kernels::sh::sh_color_viewdir_vjp |
| crates/brush-render/src/kernels/camera_model/kannala_brandt_4.rs | 7.0 | Near-clean | God Classes: FunctionTooLong: brush_render::kernels::camera_model::kannala_brandt_4::calculate_projection_vjp_kb4 |
| apps/brush-app/src/ui/settings_popup.rs | 7.1 | Near-clean | Cyclomatic Complexity: brush_app::ui::settings_popup::draw_dataset (cyclomatic 23) |
| crates/brush-render/src/bwd/kernels/rasterize_backwards.rs | 7.2 | Near-clean | Cognitive Complexity: brush_render::bwd::kernels::rasterize_backwards::accumulate_grads_for_batch (cognitive 36) |
| apps/brush-app/src/ui/splat_backbuffer.rs | 7.2 | Near-clean | Code Duplication: Near-duplicate member pair (27 shared lines) |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| apps/brush-app/src/ui/camera_controls.rs | 7.4 | Near-clean | Cyclomatic Complexity: CameraController::tick (cyclomatic 32) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 75 of 75 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 75 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, 218 of 236 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 34 test files), but it was not re-run: its build outgrew the 6 GB scratch ceiling (6.075 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 4 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (22 contributor(s) across 1227 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 21 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was brush_process::train_stream::train_stream at 43. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ColmapCamera::principal_point at 21 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/colmap-reader/src/lib.rs (ColmapCamera::principal_point at 21). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 13 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with brush_process::train_stream::train_stream (cyclomatic 43), brush_loss::kernels::image_loss_backward_kernel (cyclomatic 35), CameraController::tick (cyclomatic 32). — 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 13 together lifts Cyclomatic Complexity from 7.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
26 method(s) exceeded the cognitive complexity threshold of 15; the worst was brush_loss::kernels::image_loss_backward_kernel at 77.
What to do
- Bring the 26 bodies over 15 down to 15 or less in Cognitive Complexity — start with brush_loss::kernels::image_loss_backward_kernel (cognitive 77), brush_process::train_stream::train_stream (cognitive 77), TrainingPanel::ui (cognitive 63). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 26 together lifts Cognitive Complexity from 5.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
27 god class(es) detected.
What to do
- Resolve the 13 FunctionTooLong finding(s) in God Classes — start with lib.rs (3), train_stream.rs, radial_tangential_8.rs. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 7 MethodTooLong finding(s) in God Classes — start with train.rs (2), scene.rs (2), camera_controls.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 4 FileTooLong finding(s) in God Classes — start with lib.rs, scene.rs, visualize_tools.rs. — One of this dimension's main actionable groups (4 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
43 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 6 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with lib.rs, pinhole.rs, helpers.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with lib.rs (2), project_backwards.rs, rasterize_backwards.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with lib.rs (2), sh.rs (2). — One of this dimension's main actionable groups (4 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
25 production modules (Gradle+Cargo+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 4 module(s) off the main sequence, with abstractness counted on 21 of the 25 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 40 classes have LCOM4 above 3.
D9 · Test Distribution
161 test methods: 112 unit, 49 integration, 0 BDD, 0 e2e. The Rust suite contributes 161 `#[test]` function(s) across 34 file(s) declaring at least one; its unit/integration split is Cargo's own — 6 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 898 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 74 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: crates/brush-process/src/train_stream.rs (9×43=387); crates/brush-loss/src/lib.rs (5×35=175); apps/brush-app/src/ui/settings_popup.rs (4×23=92)
What to do
- Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with lib.rs (2), train_stream.rs, settings_popup.rs. — One of this dimension's main actionable groups (5 warning-level).
D17 · Explicit Debt
5 deducted task-comment markers across 25676 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 5 TodoComment finding(s) in Explicit Debt — start with lib.rs (2), data_source.rs, quat_vec.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 7 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 24 build units (Cargo, Gradle, npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
36 finding(s): 0 critical, 36 high, 0 medium, 0 low. 32 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `apps/brush-app/src/ui/splat_backbuffer.rs` (line 54) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 32 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 (32 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
41 finding(s): 0 critical, 5 high, 34 medium, 2 low.
What to do
- Resolve the 19 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (19). — One of this dimension's main actionable groups (19 warning-level).
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 8 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 91 of the 124 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: render_bwd.rs↔render.rs 82%; burn_glue.rs↔burn_glue.rs 75%; burn_glue.rs↔render.rs 72%
What to do
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with burn_glue.rs, colmap.rs, lib.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with render.rs, train.rs. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 6 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×2) — apps/brush-app/web/src/BrushViewer.tsx:102, apps/brush-js/web/index.html:46
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — apps/brush-app/web/index.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — apps/brush-js/web/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 5 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 20 of 26 project(s) that lack one — worth up to 1.5 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 13/15 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/brush-bench-test/test_cases`, `crates/lpips-convert`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `npm`, `pip`, `gradle` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
R2 · Cyclomatic Complexity
- applyMessage has cyclomatic complexity 25 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/brush-js/web/src/main.ts:387
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- apps/brush-js/web/src/main.ts has 485 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/brush-js/web/src/main.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- 3 file(s) (~823 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: apps/brush-js/web/src/main.ts imports '../pkg/brush_js', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — apps/brush-js/web
R8 · Dependency Hygiene
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- ~2.0 `!` null assertions per 1k TypeScript source lines — 2 assertion(s) across the 991 source line(s) of the 5 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: apps/brush-app/web/src/main.tsx (1), apps/brush-js/web/src/main.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 73% | Adequate — gated by R3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 97% | Exemplary | Strongest area. |
| Maturity | 60% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 77% | Strong | Solid. |
| Security | 65% | Adequate — gated by D30, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 40% | Weak — gated by AC1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 91% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 55 check(s) not relevant to this codebase
- AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's Java 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; this repository's Python 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; this repository's TypeScript 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.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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 — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility (rendered) — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — ~4131 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 4 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, JavaScript, Python, Rust, TypeScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .java, .py, .rs, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (6 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 JVM, 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Java code has 107 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (5 production file(s)) has no JavaScript/TypeScript test, but it is 3.54% of this repository's production source and the other 96.46% carries 4,131 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- S1 Web-Security Posture — No web surface: 107 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 41 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 182 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: brush_process::train_stream::train_stream crates/brush-process/src/train_stream.rs:31
- FunctionTooLong: brush_loss::kernels::image_loss_backward_kernel crates/brush-loss/src/lib.rs:449
- FunctionTooLong: brush_render::kernels::camera_model::radial_tangential_8::calculate_projection_vjp_rt8 crates/brush-render/src/kernels/camera_model/radial_tangential_8.rs:151
- FunctionTooLong: brush_loss::kernels::image_loss_forward_kernel crates/brush-loss/src/lib.rs:230
- FunctionTooLong: brush_cli::run_cli_ui apps/brush-cli/src/lib.rs:77
- FunctionTooLong: brush_app::ui::settings_popup::draw_training apps/brush-app/src/ui/settings_popup.rs:62
- FunctionTooLong: brush_render::bwd::kernels::project_backwards::project_backwards_kernel crates/brush-render/src/bwd/kernels/project_backwards.rs:126
- FunctionTooLong: brush_serde::import::parse_compressed_ply crates/brush-serde/src/import.rs:408
- FunctionTooLong: brush_dataset::formats::colmap::load_dataset_inner crates/brush-dataset/src/formats/colmap.rs:122
- FunctionTooLong: brush_render::kernels::rasterize::rasterize_kernel crates/brush-render/src/kernels/rasterize.rs:27
- FunctionTooLong: brush_render::kernels::sh::sh_color_viewdir_vjp crates/brush-render/src/kernels/sh.rs:143
- FunctionTooLong: brush_render::kernels::camera_model::kannala_brandt_4::calculate_projection_vjp_kb4 crates/brush-render/src/kernels/camera_model/kannala_brandt_4.rs:155
- FunctionTooLong: brush_render::bwd::kernels::rasterize_backwards::accumulate_grads_for_batch crates/brush-render/src/bwd/kernels/rasterize_backwards.rs:252
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: CameraController.tick apps/brush-app/src/ui/camera_controls.rs:126
- MethodTooLong: SplatTrainer.step crates/brush-train/src/train.rs:214
- MethodTooLong: TrainingPanel.ui apps/brush-app/src/ui/training_panel.rs:211
- MethodTooLong: ScenePanel.ui apps/brush-app/src/ui/scene.rs:908
- MethodTooLong: SplatTrainer.refine crates/brush-train/src/train.rs:465
- MethodTooLong: VisualizeTools.send_default_blueprint crates/brush-rerun/src/visualize_tools.rs:160
- MethodTooLong: ScenePanel.top_bar_right_ui apps/brush-app/src/ui/scene.rs:629
- Duplicated block (7 lines × 2) crates/brush-loss/src/lib.rs:625
- Duplicated block (7 lines × 2) crates/brush-render/src/kernels/camera_model/pinhole.rs:78
- Duplicated block (7 lines × 2) crates/brush-render/src/kernels/helpers.rs:211
- Duplicated block (7 lines × 2) crates/brush-render/src/kernels/sh.rs:88
- Duplicated block (7 lines × 2) apps/brush-app/src/ui/splat_backbuffer.rs:158
- Duplicated block (7 lines × 2) apps/brush-app/src/ui/scene.rs:665
- Hotspot: crates/brush-process/src/train_stream.rs crates/brush-process/src/train_stream.rs:31
- Hotspot: crates/brush-loss/src/lib.rs crates/brush-loss/src/lib.rs:449
- Hotspot: apps/brush-app/src/ui/settings_popup.rs apps/brush-app/src/ui/settings_popup.rs:311
- Hotspot: apps/brush-cli/src/lib.rs apps/brush-cli/src/lib.rs:77
- Hotspot: crates/brush-render/src/kernels/project_forward.rs crates/brush-render/src/kernels/project_forward.rs:22
- TodoComment crates/lpips/src/lib.rs:89
- TodoComment crates/colmap-reader/src/lib.rs:6
- TodoComment crates/brush-vfs/src/data_source.rs:27
- TodoComment crates/brush-train/src/quat_vec.rs:3
- TodoComment crates/brush-process/src/train_stream.rs:626
- brush_render::kernels::rasterize::rasterize_kernel (cognitive 49) crates/brush-render/src/kernels/rasterize.rs:27
- brush_render::bwd::kernels::rasterize_backwards::accumulate_grads_for_batch (cognitive 36) crates/brush-render/src/bwd/kernels/rasterize_backwards.rs:252
- brush_render::get_tile_offset::get_tile_offsets (cognitive 26) crates/brush-render/src/get_tile_offset.rs:11
- brush_render::kernels::project_forward::project_forward_kernel (cognitive 19) crates/brush-render/src/kernels/project_forward.rs:22
- brush_render::validation::validate_tensor_val (cognitive 17) crates/brush-render/src/validation.rs:61
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (6 lines × 2) crates/brush-loss/src/lib.rs:312
- Duplicated block (6 lines × 2) crates/brush-loss/src/lib.rs:390
- Duplicated block (6 lines × 2) crates/brush-render/src/bwd/kernels/project_backwards.rs:163
- Duplicated block (6 lines × 2) crates/brush-render/src/bwd/kernels/rasterize_backwards.rs:208
- Duplicated block (6 lines × 2) crates/brush-render/src/kernels/sh.rs:69
- FileTooLong: src/lib.rs crates/brush-loss/src/lib.rs
- FileTooLong: ui/scene.rs apps/brush-app/src/ui/scene.rs
- FileTooLong: src/visualize_tools.rs crates/brush-rerun/src/visualize_tools.rs
- FileTooLong: src/train.rs crates/brush-train/src/train.rs
- Change coupling: burn_glue.rs ↔ burn_glue.rs crates/brush-render/src/burn_glue.rs:1
- Change coupling: colmap.rs ↔ nerfstudio.rs crates/brush-dataset/src/formats/colmap.rs:1
- Change coupling: lib.rs ↔ lib.rs crates/brush-scan/src/lib.rs:1
- Change coupling: scene.rs ↔ stats.rs apps/brush-app/src/ui/scene.rs:1
- Duplicated block (5 lines × 2) crates/brush-loss/src/lib.rs:346
- Duplicated block (5 lines × 2) crates/brush-render/src/kernels/sh.rs:82
- Duplicated block (5 lines × 2) crates/brush-render/src/kernels/sh.rs:104
- Duplicated block (5 lines × 2) crates/brush-loss/src/lib.rs:941
- Off the main sequence: brush-async
- Off the main sequence: brush-cube
- Off the main sequence: lpips
- Off the main sequence: rrfd
- brush_process::train_stream::train_stream (cognitive 77) crates/brush-process/src/train_stream.rs:31
- brush_process::run_process (cognitive 20) crates/brush-process/src/lib.rs:111
- brush_process::args_file::config_to_args (cognitive 20) crates/brush-process/src/args_file.rs:53
- ScenePanel::top_bar_right_ui (cognitive 36) apps/brush-app/src/ui/scene.rs:629
- ScenePanel::ui (cognitive 36) apps/brush-app/src/ui/scene.rs:908
- ScenePanel::on_message (cognitive 21) apps/brush-app/src/ui/scene.rs:815
- Duplicated block (10 lines × 2) apps/brush-app/src/ui/settings_popup.rs:366
- Duplicated block (10 lines × 2) crates/brush-loss/src/lib.rs:399
- Duplicated block (10 lines × 2) crates/brush-scan/src/kernels.rs:133
- Duplicated block (8 lines × 2) crates/brush-render/src/kernels/sh.rs:112
- Duplicated block (8 lines × 2) apps/brush-app/src/ui/splat_backbuffer.rs:194
- Duplicated block (8 lines × 2) apps/brush-app/src/ui/scene.rs:524
- <canvas> without a text alternative apps/brush-app/web/src/BrushViewer.tsx:102
- <canvas> without a text alternative apps/brush-js/web/index.html:46
- Page without a main landmark apps/brush-app/web/index.html:2
- Page without a main landmark apps/brush-js/web/index.html:2
- brush_loss::kernels::image_loss_backward_kernel (cyclomatic 35) crates/brush-loss/src/lib.rs:449
- brush_loss::kernels::image_loss_forward_kernel (cyclomatic 23) crates/brush-loss/src/lib.rs:230
- brush_render::kernels::rasterize::rasterize_kernel (cyclomatic 25) crates/brush-render/src/kernels/rasterize.rs:27
- brush_render::kernels::project_forward::project_forward_kernel (cyclomatic 18) crates/brush-render/src/kernels/project_forward.rs:22
- ScenePanel::ui (cyclomatic 21) apps/brush-app/src/ui/scene.rs:908
- ScenePanel::top_bar_right_ui (cyclomatic 20) apps/brush-app/src/ui/scene.rs:629
- brush_loss::kernels::image_loss_backward_kernel (cognitive 77) crates/brush-loss/src/lib.rs:449
- brush_loss::kernels::image_loss_forward_kernel (cognitive 40) crates/brush-loss/src/lib.rs:230
- brush_serde::import::parse_compressed_ply (cognitive 21) crates/brush-serde/src/import.rs:408
- brush_serde::import::parse_ply (cognitive 19) crates/brush-serde/src/import.rs:299
- ClassTooLong: ScenePanel apps/brush-app/src/ui/scene.rs:76
- ClassTooLong: SplatTrainer crates/brush-train/src/train.rs:68
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change-coupling hub: render.rs → burn_glue.rs, burn_glue.rs, render_bwd.rs crates/brush-render/src/render.rs
- Change-coupling hub: train.rs → render_aux.rs, visualize_tools.rs, eval.rs crates/brush-train/src/train.rs
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2) apps/brush-app/src/ui/splat_backbuffer.rs:218
- Duplicated block (12 lines × 2) apps/brush-app/src/ui/settings_popup.rs:353
- Duplicated block (9 lines × 2) apps/brush-app/src/ui/app.rs:32
- Duplicated block (9 lines × 2) crates/brush-render/src/bwd/kernels/rasterize_backwards.rs:303
- Duplicated block (6 lines × 4) crates/brush-render/src/kernels/camera_model/kannala_brandt_4.rs:272
- Duplicated block (6 lines × 4) apps/brush-app/src/ui/settings_popup.rs:332
- Duplicated block (6 lines × 3) crates/brush-render/src/kernels/camera_model/kannala_brandt_4.rs:310
- Duplicated block (6 lines × 3) crates/brush-render/src/kernels/camera_model/kannala_brandt_4.rs:226
- Accessibility enforcement below the top rung
- brush_process::train_stream::train_stream (cyclomatic 43) crates/brush-process/src/train_stream.rs:31
- CameraController::tick (cyclomatic 32) apps/brush-app/src/ui/camera_controls.rs:126
- TrainingPanel::ui (cyclomatic 29) apps/brush-app/src/ui/training_panel.rs:211
- brush_app::ui::settings_popup::draw_dataset (cyclomatic 23) apps/brush-app/src/ui/settings_popup.rs:311
- brush_cli::run_cli_ui (cyclomatic 20) apps/brush-cli/src/lib.rs:77
- main.applyMessage (cyclomatic 18) apps/brush-js/web/src/main.ts:387
- App::ui (cyclomatic 16) apps/brush-app/src/ui/app.rs:300
- TrainingPanel::ui (cognitive 63) apps/brush-app/src/ui/training_panel.rs:211
- CameraController::tick (cognitive 43) apps/brush-app/src/ui/camera_controls.rs:126
- brush_app::ui::settings_popup::draw_dataset (cognitive 33) apps/brush-app/src/ui/settings_popup.rs:311
- brush_dataset::find_eigenvector (cognitive 26) crates/brush-dataset/src/lib.rs:32
- brush_cli::run_cli_ui (cognitive 25) apps/brush-cli/src/lib.rs:77
- brush_sort::kernels::sort_scatter_kernel (cognitive 25) crates/brush-sort/src/kernels.rs:183
- SplatTrainer::refine (cognitive 22) crates/brush-train/src/train.rs:465
- App::ui (cognitive 20) apps/brush-app/src/ui/app.rs:300
- colmap_reader::read_images_text (cognitive 19) crates/colmap-reader/src/lib.rs:309
- BrushViewer.BrushViewer (cognitive 19) apps/brush-app/web/src/BrushViewer.tsx:17
- DatasetPanel::ui (cognitive 17) apps/brush-app/src/ui/datasets.rs:290
- TooManyMethods: UiProcess apps/brush-app/src/ui/ui_process.rs:31
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (54 shared lines) crates/brush-loss/src/lib.rs:248
- Near-duplicate member pair (31 shared lines) crates/brush-render/src/kernels/sh.rs:52
- Near-duplicate member pair (27 shared lines) apps/brush-app/src/ui/splat_backbuffer.rs:154
- Duplicated block (18 lines × 2) crates/brush-process/src/train_stream.rs:230
- Duplicated block (12–15 lines × 2) crates/brush-render/src/kernels/camera_model/radial_tangential_8.rs:126
- Duplicated block (14 lines × 2) crates/brush-render/src/kernels/camera_model/kannala_brandt_4.rs:280
- Duplicated block (12–13 lines × 2) crates/brush-sort/src/kernels.rs:66
- Duplicated block (12 lines × 3) crates/colmap-reader/src/lib.rs:119
- Duplicated block (11 lines × 2) crates/brush-loss/src/lib.rs:289
- Duplicated block (9–10 lines × 2) crates/brush-loss/src/lib.rs:556
- Duplicated block (8–10 lines × 2) crates/brush-vfs/src/data_source.rs:145
- Duplicated block (6–8 lines × 2) crates/brush-render/src/bwd/kernels/project_backwards.rs:205
- Duplicated block (7–8 lines × 2) crates/brush-render/src/kernels/camera_model/kannala_brandt_4.rs:87
- Duplicated block (7 lines × 4) crates/brush-loss/src/lib.rs:331
- Duplicated block (6–7 lines × 3) crates/brush-render/src/kernels/camera_model/kannala_brandt_4.rs:37
- Duplicated block (6 lines × 6) crates/brush-loss/src/lib.rs:333
- Duplicated block (2–5 lines × 3) crates/brush-render/src/kernels/sh.rs:76
- Complex function applyMessage (cyclomatic 25, cognitive 21) apps/brush-js/web/src/main.ts:387
- apps/brush-js/web/src/main.ts: 485 lines of code apps/brush-js/web/src/main.ts:1
- Unused dependency 'baseline-browser-mapping'
Minor — 13 finding(s)
- No ADRs found
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No release approval gate
- Duplicated predicate apps/brush-app/src/ui/datasets.rs:259
- Null assertions (`!`) reduce the strict null checking score
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ac90ec044a0b4b6c96097afc2720bdb1/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ac90ec044a0b4b6c96097afc2720bdb1/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 36 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 41 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |