Executive summary
ZimengXiong/Modelr falls short of our standard for production, in part because we found no logging, tracing or health checks in the code. It scores 63.5 out of 100 and is rated Adequate, and both of its critical findings are security problems in the build pipeline.
Production Readiness, at 46.3, is the weakest lens and counts most in the score. The best first step is adding a diagnostic log, worth about 8.9 points. Recording design decisions comes next, worth about 3.8 points. Raising Production Readiness to 70 would lift the score to about 74.5.
Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 11,434 lines, about €16,000 to rebuild.
If Production Readiness rose from 46.3 to 70, the lowest score rated Strong, the score would rise from 63.5 to about 74.5.
Rebuild cost: about €16,000 · Estimate
| Cost to rebuild | €5,200 to €26,000, for 87 to 276 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 64. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 11,434 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 Packages.HunyuanPaintMLX | 2 vendor.mlx-swift.Source.Cmlx.fmt.support | 3 vendor.mlx-swift.Source.Cmlx.fmt.support.docopt | 4 vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers.cxx | 5 vendor.mlx-swift.Source.Cmlx.fmt.support.release | 6 vendor.mlx-swift.Source.Cmlx.metal-cpp.SingleHeader | 7 vendor.mlx-swift.Source.Cmlx.metal-cpp.SingleHeader.MakeSingleHeader | 8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base | 9 vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers | 10 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn | 11 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers | 12 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations | 13 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.containers | 14 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution | 15 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution_transpose | 16 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed | 17 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.dropout | 18 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.embedding | 19 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.linear | 20 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization | 21 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.pooling | 22 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.positional_encoding | 23 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.quantized | 24 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.recurrent | 25 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer | 26 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.upsample | 27 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.optimizers.optimizers | 28 vendor~swift-numerics~ComplexModule | 29 vendor~swift-numerics~RealModule | 30 vendor~mlx-swift~MLX | 31 Core | 32 Packages~Hy3DMLX~Hy3DMLX | 33 vendor~mlx-swift~MLXFFT | 34 vendor~mlx-swift~MLXFast | 35 vendor~mlx-swift~MLXLinalg | 36 vendor~mlx-swift~MLXNN | 37 vendor~mlx-swift~MLXRandom | 38 Packages~HunyuanPaintMLX~HunyuanPaintMLX | 39 vendor~mlx-swift~MLXOptimizers | 40 repository |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Packages.HunyuanPaintMLX | ||||||||||||||||||||||||||||||||||||||||
| 2 vendor.mlx-swift.Source.Cmlx.fmt.support | ||||||||||||||||||||||||||||||||||||||||
| 3 vendor.mlx-swift.Source.Cmlx.fmt.support.docopt | ||||||||||||||||||||||||||||||||||||||||
| 4 vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers.cxx | ||||||||||||||||||||||||||||||||||||||||
| 5 vendor.mlx-swift.Source.Cmlx.fmt.support.release | ||||||||||||||||||||||||||||||||||||||||
| 6 vendor.mlx-swift.Source.Cmlx.metal-cpp.SingleHeader | ||||||||||||||||||||||||||||||||||||||||
| 7 vendor.mlx-swift.Source.Cmlx.metal-cpp.SingleHeader.MakeSingleHeader | ||||||||||||||||||||||||||||||||||||||||
| 8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base | ||||||||||||||||||||||||||||||||||||||||
| 9 vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations | 25 | |||||||||||||||||||||||||||||||||||||||
| 13 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.containers | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution | 3 | |||||||||||||||||||||||||||||||||||||||
| 15 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution_transpose | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed | 4 | |||||||||||||||||||||||||||||||||||||||
| 17 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.dropout | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.embedding | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.linear | 3 | |||||||||||||||||||||||||||||||||||||||
| 20 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization | 5 | |||||||||||||||||||||||||||||||||||||||
| 21 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.pooling | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.positional_encoding | 3 | |||||||||||||||||||||||||||||||||||||||
| 23 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.quantized | 3 | |||||||||||||||||||||||||||||||||||||||
| 24 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.recurrent | 3 | |||||||||||||||||||||||||||||||||||||||
| 25 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer | 6 | |||||||||||||||||||||||||||||||||||||||
| 26 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.upsample | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.optimizers.optimizers | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 vendor~swift-numerics~ComplexModule | 4 | |||||||||||||||||||||||||||||||||||||||
| 29 vendor~swift-numerics~RealModule | 7 | |||||||||||||||||||||||||||||||||||||||
| 30 vendor~mlx-swift~MLX | 1 | 15 | 3 | |||||||||||||||||||||||||||||||||||||
| 31 Core | 9 | 34 | ||||||||||||||||||||||||||||||||||||||
| 32 Packages~Hy3DMLX~Hy3DMLX | 10 | 26 | ||||||||||||||||||||||||||||||||||||||
| 33 vendor~mlx-swift~MLXFFT | 3 | |||||||||||||||||||||||||||||||||||||||
| 34 vendor~mlx-swift~MLXFast | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 35 vendor~mlx-swift~MLXLinalg | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 36 vendor~mlx-swift~MLXNN | 27 | 166 | ||||||||||||||||||||||||||||||||||||||
| 37 vendor~mlx-swift~MLXRandom | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 38 Packages~HunyuanPaintMLX~HunyuanPaintMLX | 28 | 66 | 4 | |||||||||||||||||||||||||||||||||||||
| 39 vendor~mlx-swift~MLXOptimizers | 10 | 24 | 2 | |||||||||||||||||||||||||||||||||||||
| 40 repository | 9 | 66 | 27 | 2 | 2 |
9→4 vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers uses vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers.cxx✕
- Connections
- 2 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers uses a type in vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers.cxx.
- The types involved
vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers.cxx→vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers.cxx.CxxHandlervendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers.cxx→vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers.cxx.Definition
- Direction
- vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers uses vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers.cxx, so a change to vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers.cxx can break vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers, while a change to vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers can't break vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers.cxx.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.fmt.support.python.mkdocstrings_handlers uses a module listed above it, which is the healthy direction.
10→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 1 pair of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.utils→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn uses a module listed above it, which is the healthy direction.
11→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 2 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.quantized→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers uses a module listed above it, which is the healthy direction.
12→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 25 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.CELU→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.ELU→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.GELU→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.GLU→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.HardShrink→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.HardTanh→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.Hardswish→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.LeakyReLU→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.LogSigmoid→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.LogSoftmax→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.Mish→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.PReLU→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.ReLU→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.ReLU2→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.ReLU6→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.SELU→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.SiLU→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.Sigmoid→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.Softmax→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.Softmin→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.Softplus→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.Softshrink→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.Softsign→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.Step→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations.Tanh→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.activations uses a module listed above it, which is the healthy direction.
13→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.containers uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 1 pair of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.containers uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.containers.Sequential→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.containers uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.containers, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.containers can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.containers uses a module listed above it, which is the healthy direction.
14→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 3 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution.Conv1d→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution.Conv2d→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution.Conv3d→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution uses a module listed above it, which is the healthy direction.
15→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution_transpose uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 3 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution_transpose uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution_transpose.ConvTranspose1d→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution_transpose.ConvTranspose2d→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution_transpose.ConvTranspose3d→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution_transpose uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution_transpose, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution_transpose can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.convolution_transpose uses a module listed above it, which is the healthy direction.
16→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 4 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed.AllToShardedLinear→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed.QuantizedAllToShardedLinear→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed.QuantizedShardedToAllLinear→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed.ShardedToAllLinear→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.distributed uses a module listed above it, which is the healthy direction.
17→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.dropout uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 3 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.dropout uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.dropout.Dropout→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.dropout.Dropout2d→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.dropout.Dropout3d→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.dropout uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.dropout, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.dropout can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.dropout uses a module listed above it, which is the healthy direction.
18→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.embedding uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 1 pair of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.embedding uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.embedding.Embedding→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.embedding uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.embedding, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.embedding can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.embedding uses a module listed above it, which is the healthy direction.
19→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.linear uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 3 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.linear uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.linear.Bilinear→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.linear.Identity→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.linear.Linear→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.linear uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.linear, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.linear can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.linear uses a module listed above it, which is the healthy direction.
20→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 5 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization.BatchNorm→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization.GroupNorm→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization.InstanceNorm→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization.LayerNorm→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization.RMSNorm→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.normalization uses a module listed above it, which is the healthy direction.
21→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.pooling uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 1 pair of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.pooling uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.pooling._Pool→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.pooling uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.pooling, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.pooling can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.pooling uses a module listed above it, which is the healthy direction.
22→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.positional_encoding uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 3 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.positional_encoding uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.positional_encoding.ALiBi→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.positional_encoding.RoPE→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.positional_encoding.SinusoidalPositionalEncoding→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.positional_encoding uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.positional_encoding, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.positional_encoding can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.positional_encoding uses a module listed above it, which is the healthy direction.
23→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.quantized uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 3 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.quantized uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.quantized.QQLinear→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.quantized.QuantizedEmbedding→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.quantized.QuantizedLinear→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.quantized uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.quantized, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.quantized can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.quantized uses a module listed above it, which is the healthy direction.
24→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.recurrent uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 3 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.recurrent uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.recurrent.GRU→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.recurrent.LSTM→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.recurrent.RNN→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.recurrent uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.recurrent, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.recurrent can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.recurrent uses a module listed above it, which is the healthy direction.
25→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 6 pairs of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer.MultiHeadAttention→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer.Transformer→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer.TransformerDecoder→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer.TransformerDecoderLayer→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer.TransformerEncoder→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Modulevendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer.TransformerEncoderLayer→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.transformer uses a module listed above it, which is the healthy direction.
26→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.upsample uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 1 pair of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.upsample uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.upsample.Upsample→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.upsample uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.upsample, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.upsample can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.upsample uses a module listed above it, which is the healthy direction.
27→8 vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.optimizers.optimizers uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base✕
- Connections
- 1 pair of types, where a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.optimizers.optimizers uses a type in vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- The types involved
vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.optimizers.optimizers.Optimizer→vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.Module
- Direction
- vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.optimizers.optimizers uses vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base, so a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base can break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.optimizers.optimizers, while a change to vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.optimizers.optimizers can't break vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.nn.layers.base.
- Position
- Below the diagonal: vendor.mlx-swift.Source.Cmlx.mlx.python.mlx.optimizers.optimizers uses a module listed above it, which is the healthy direction.
28→30 vendor~swift-numerics~ComplexModule uses vendor~mlx-swift~MLX part of a loop✕
- Connections
- 4 pairs of types, where a type in vendor~swift-numerics~ComplexModule uses a type in vendor~mlx-swift~MLX.
- The types involved
vendor~swift-numerics~ComplexModule.Complex→vendor~mlx-swift~MLX.Boolvendor~swift-numerics~ComplexModule.Complex→vendor~mlx-swift~MLX.DTypevendor~swift-numerics~ComplexModule.Complex→vendor~mlx-swift~MLX.Intvendor~swift-numerics~ComplexModule.Complex→vendor~mlx-swift~MLX.MLXArray
- Direction
- vendor~swift-numerics~ComplexModule uses vendor~mlx-swift~MLX, so a change to vendor~mlx-swift~MLX can break vendor~swift-numerics~ComplexModule, while a change to vendor~swift-numerics~ComplexModule can't break vendor~mlx-swift~MLX.
- 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.
29→30 vendor~swift-numerics~RealModule uses vendor~mlx-swift~MLX part of a loop✕
- Connections
- 7 pairs of types, where a type in vendor~swift-numerics~RealModule uses a type in vendor~mlx-swift~MLX.
- The types involved
vendor~swift-numerics~RealModule.AdditiveArithmetic→vendor~mlx-swift~MLX.Boolvendor~swift-numerics~RealModule.Double→vendor~mlx-swift~MLX.Intvendor~swift-numerics~RealModule.ElementaryFunctions→vendor~mlx-swift~MLX.Intvendor~swift-numerics~RealModule.Float→vendor~mlx-swift~MLX.Intvendor~swift-numerics~RealModule.Float80→vendor~mlx-swift~MLX.Intvendor~swift-numerics~RealModule.Numeric→vendor~mlx-swift~MLX.Boolvendor~swift-numerics~RealModule.Real→vendor~mlx-swift~MLX.Bool
- Direction
- vendor~swift-numerics~RealModule uses vendor~mlx-swift~MLX, so a change to vendor~mlx-swift~MLX can break vendor~swift-numerics~RealModule, while a change to vendor~swift-numerics~RealModule can't break vendor~mlx-swift~MLX.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→28 vendor~mlx-swift~MLX uses vendor~swift-numerics~ComplexModule✕
- Connections
- 1 pair of types, where a type in vendor~mlx-swift~MLX uses a type in vendor~swift-numerics~ComplexModule.
- The types involved
vendor~mlx-swift~MLX.MLXArray→vendor~swift-numerics~ComplexModule.Complex
- Direction
- vendor~mlx-swift~MLX uses vendor~swift-numerics~ComplexModule, so a change to vendor~swift-numerics~ComplexModule can break vendor~mlx-swift~MLX, while a change to vendor~mlx-swift~MLX can't break vendor~swift-numerics~ComplexModule.
- Position
- Below the diagonal: vendor~mlx-swift~MLX uses a module listed above it, which is the healthy direction.
30→29 vendor~mlx-swift~MLX uses vendor~swift-numerics~RealModule✕
- Connections
- 15 pairs of types, where a type in vendor~mlx-swift~MLX uses a type in vendor~swift-numerics~RealModule.
- The types involved
vendor~mlx-swift~MLX.FInfo→vendor~swift-numerics~RealModule.Doublevendor~mlx-swift~MLX.Factory.swift→vendor~swift-numerics~RealModule.Doublevendor~mlx-swift~MLX.FloatOrArray→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLX.Linalg.swift→vendor~swift-numerics~RealModule.Doublevendor~mlx-swift~MLX.MLXArray→vendor~swift-numerics~RealModule.Doublevendor~mlx-swift~MLX.MLXArray→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLX.MLXFast→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLX.MLXFast.swift→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLX.MLXLinalg→vendor~swift-numerics~RealModule.Doublevendor~mlx-swift~MLX.MLXRandom→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLX.Ops+Array.swift→vendor~swift-numerics~RealModule.Doublevendor~mlx-swift~MLX.Ops.swift→vendor~swift-numerics~RealModule.Doublevendor~mlx-swift~MLX.Ops.swift→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLX.Random.swift→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLX.WiredMemoryManagerConfiguration→vendor~swift-numerics~RealModule.Double
- Direction
- vendor~mlx-swift~MLX uses vendor~swift-numerics~RealModule, so a change to vendor~swift-numerics~RealModule can break vendor~mlx-swift~MLX, while a change to vendor~mlx-swift~MLX can't break vendor~swift-numerics~RealModule.
- Position
- Below the diagonal: vendor~mlx-swift~MLX uses a module listed above it, which is the healthy direction.
30→31 vendor~mlx-swift~MLX uses Core part of a loop✕
- Connections
- 3 pairs of types, where a type in vendor~mlx-swift~MLX uses a type in Core.
- The types involved
vendor~mlx-swift~MLX.IO.swift→Core.Datavendor~mlx-swift~MLX.IOState→Core.Datavendor~mlx-swift~MLX.MLXArray→Core.Data
- Direction
- vendor~mlx-swift~MLX uses Core, so a change to Core can break vendor~mlx-swift~MLX, while a change to vendor~mlx-swift~MLX can't break Core.
- 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.
31→29 Core uses vendor~swift-numerics~RealModule✕
- Connections
- 9 pairs of types, where a type in Core uses a type in vendor~swift-numerics~RealModule.
- The types involved
Core.Data→vendor~swift-numerics~RealModule.FloatCore.DownloadProgress→vendor~swift-numerics~RealModule.DoubleCore.HeapEntry→vendor~swift-numerics~RealModule.DoubleCore.MeshData→vendor~swift-numerics~RealModule.FloatCore.MeshDecimator→vendor~swift-numerics~RealModule.FloatCore.MeshExporter→vendor~swift-numerics~RealModule.FloatCore.PaintJob→vendor~swift-numerics~RealModule.DoubleCore.Quadric→vendor~swift-numerics~RealModule.DoubleCore.ShapeJob→vendor~swift-numerics~RealModule.Double
- Direction
- Core uses vendor~swift-numerics~RealModule, so a change to vendor~swift-numerics~RealModule can break Core, while a change to Core can't break vendor~swift-numerics~RealModule.
- Position
- Below the diagonal: Core uses a module listed above it, which is the healthy direction.
31→30 Core uses vendor~mlx-swift~MLX✕
- Connections
- 34 pairs of types, where a type in Core uses a type in vendor~mlx-swift~MLX. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Core.AppState→vendor~mlx-swift~MLX.UInt64Core.BootReport→vendor~mlx-swift~MLX.BoolCore.CatalogFile→vendor~mlx-swift~MLX.Int64Core.CatalogModel→vendor~mlx-swift~MLX.Int64Core.Configuration→vendor~mlx-swift~MLX.Int64Core.Data→vendor~mlx-swift~MLX.UInt16Core.Data→vendor~mlx-swift~MLX.UInt32Core.DownloadManager→vendor~mlx-swift~MLX.BoolCore.DownloadManager→vendor~mlx-swift~MLX.IntCore.DownloadManager→vendor~mlx-swift~MLX.Int64Core.DownloadManager→vendor~mlx-swift~MLX.UInt64Core.DownloadProgress→vendor~mlx-swift~MLX.IntCore.DownloadProgress→vendor~mlx-swift~MLX.Int64Core.Engine→vendor~mlx-swift~MLX.BoolCore.Engine→vendor~mlx-swift~MLX.IntCore.HeapEntry→vendor~mlx-swift~MLX.IntCore.HeapEntry→vendor~mlx-swift~MLX.UInt64Core.JobKey→vendor~mlx-swift~MLX.UInt64Core.MeshData→vendor~mlx-swift~MLX.IntCore.MeshData→vendor~mlx-swift~MLX.UInt32Core.MeshDecimator→vendor~mlx-swift~MLX.IntCore.MeshDecimator→vendor~mlx-swift~MLX.Int32Core.MeshDecimator→vendor~mlx-swift~MLX.UInt32Core.MeshDecimator.swift→vendor~mlx-swift~MLX.IntCore.MeshDecimator.swift→vendor~mlx-swift~MLX.UInt64
- Direction
- Core uses vendor~mlx-swift~MLX, so a change to vendor~mlx-swift~MLX can break Core, while a change to Core can't break vendor~mlx-swift~MLX.
- Position
- Below the diagonal: Core uses a module listed above it, which is the healthy direction.
32→29 Packages~Hy3DMLX~Hy3DMLX uses vendor~swift-numerics~RealModule✕
- Connections
- 10 pairs of types, where a type in Packages~Hy3DMLX~Hy3DMLX uses a type in vendor~swift-numerics~RealModule.
- The types involved
Packages~Hy3DMLX~Hy3DMLX.DiT→vendor~swift-numerics~RealModule.FloatPackages~Hy3DMLX~Hy3DMLX.Layers→vendor~swift-numerics~RealModule.FloatPackages~Hy3DMLX~Hy3DMLX.MarchingCubes→vendor~swift-numerics~RealModule.FloatPackages~Hy3DMLX~Hy3DMLX.ModelConfig→vendor~swift-numerics~RealModule.FloatPackages~Hy3DMLX~Hy3DMLX.Pipeline→vendor~swift-numerics~RealModule.FloatPackages~Hy3DMLX~Hy3DMLX.Preprocess→vendor~swift-numerics~RealModule.FloatPackages~Hy3DMLX~Hy3DMLX.Progress→vendor~swift-numerics~RealModule.FloatPackages~Hy3DMLX~Hy3DMLX.Sampler→vendor~swift-numerics~RealModule.FloatPackages~Hy3DMLX~Hy3DMLX.ShapeGenerator→vendor~swift-numerics~RealModule.FloatPackages~Hy3DMLX~Hy3DMLX.VAE→vendor~swift-numerics~RealModule.Float
- Direction
- Packages~Hy3DMLX~Hy3DMLX uses vendor~swift-numerics~RealModule, so a change to vendor~swift-numerics~RealModule can break Packages~Hy3DMLX~Hy3DMLX, while a change to Packages~Hy3DMLX~Hy3DMLX can't break vendor~swift-numerics~RealModule.
- Position
- Below the diagonal: Packages~Hy3DMLX~Hy3DMLX uses a module listed above it, which is the healthy direction.
32→30 Packages~Hy3DMLX~Hy3DMLX uses vendor~mlx-swift~MLX✕
- Connections
- 26 pairs of types, where a type in Packages~Hy3DMLX~Hy3DMLX uses a type in vendor~mlx-swift~MLX. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Packages~Hy3DMLX~Hy3DMLX.DINOv2→vendor~mlx-swift~MLX.IntPackages~Hy3DMLX~Hy3DMLX.DINOv2→vendor~mlx-swift~MLX.MLXArrayPackages~Hy3DMLX~Hy3DMLX.DiT→vendor~mlx-swift~MLX.BoolPackages~Hy3DMLX~Hy3DMLX.DiT→vendor~mlx-swift~MLX.IntPackages~Hy3DMLX~Hy3DMLX.DiT→vendor~mlx-swift~MLX.MLXArrayPackages~Hy3DMLX~Hy3DMLX.Layers→vendor~mlx-swift~MLX.IntPackages~Hy3DMLX~Hy3DMLX.Layers→vendor~mlx-swift~MLX.MLXArrayPackages~Hy3DMLX~Hy3DMLX.MCTables→vendor~mlx-swift~MLX.IntPackages~Hy3DMLX~Hy3DMLX.MarchingCubes→vendor~mlx-swift~MLX.IntPackages~Hy3DMLX~Hy3DMLX.MarchingCubes→vendor~mlx-swift~MLX.MLXArrayPackages~Hy3DMLX~Hy3DMLX.ModelConfig→vendor~mlx-swift~MLX.BoolPackages~Hy3DMLX~Hy3DMLX.ModelConfig→vendor~mlx-swift~MLX.IntPackages~Hy3DMLX~Hy3DMLX.Pipeline→vendor~mlx-swift~MLX.BoolPackages~Hy3DMLX~Hy3DMLX.Pipeline→vendor~mlx-swift~MLX.IntPackages~Hy3DMLX~Hy3DMLX.Pipeline→vendor~mlx-swift~MLX.MLXArrayPackages~Hy3DMLX~Hy3DMLX.Preprocess→vendor~mlx-swift~MLX.IntPackages~Hy3DMLX~Hy3DMLX.Preprocess→vendor~mlx-swift~MLX.MLXArrayPackages~Hy3DMLX~Hy3DMLX.Sampler→vendor~mlx-swift~MLX.IntPackages~Hy3DMLX~Hy3DMLX.Sampler→vendor~mlx-swift~MLX.MLXArrayPackages~Hy3DMLX~Hy3DMLX.Sampler→vendor~mlx-swift~MLX.UInt64Packages~Hy3DMLX~Hy3DMLX.ShapeGenerator→vendor~mlx-swift~MLX.BoolPackages~Hy3DMLX~Hy3DMLX.ShapeGenerator→vendor~mlx-swift~MLX.DTypePackages~Hy3DMLX~Hy3DMLX.ShapeGenerator→vendor~mlx-swift~MLX.IntPackages~Hy3DMLX~Hy3DMLX.ShapeGenerator→vendor~mlx-swift~MLX.UInt64Packages~Hy3DMLX~Hy3DMLX.VAE→vendor~mlx-swift~MLX.Int
- Direction
- Packages~Hy3DMLX~Hy3DMLX uses vendor~mlx-swift~MLX, so a change to vendor~mlx-swift~MLX can break Packages~Hy3DMLX~Hy3DMLX, while a change to Packages~Hy3DMLX~Hy3DMLX can't break vendor~mlx-swift~MLX.
- Position
- Below the diagonal: Packages~Hy3DMLX~Hy3DMLX uses a module listed above it, which is the healthy direction.
33→30 vendor~mlx-swift~MLXFFT uses vendor~mlx-swift~MLX✕
- Connections
- 3 pairs of types, where a type in vendor~mlx-swift~MLXFFT uses a type in vendor~mlx-swift~MLX.
- The types involved
vendor~mlx-swift~MLXFFT.FFT.swift→vendor~mlx-swift~MLX.Intvendor~mlx-swift~MLXFFT.FFT.swift→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXFFT.FFT.swift→vendor~mlx-swift~MLX.StreamOrDevice
- Direction
- vendor~mlx-swift~MLXFFT uses vendor~mlx-swift~MLX, so a change to vendor~mlx-swift~MLX can break vendor~mlx-swift~MLXFFT, while a change to vendor~mlx-swift~MLXFFT can't break vendor~mlx-swift~MLX.
- Position
- Below the diagonal: vendor~mlx-swift~MLXFFT uses a module listed above it, which is the healthy direction.
34→29 vendor~mlx-swift~MLXFast uses vendor~swift-numerics~RealModule✕
- Connections
- 1 pair of types, where a type in vendor~mlx-swift~MLXFast uses a type in vendor~swift-numerics~RealModule.
- The types involved
vendor~mlx-swift~MLXFast.MLXFast.swift→vendor~swift-numerics~RealModule.Float
- Direction
- vendor~mlx-swift~MLXFast uses vendor~swift-numerics~RealModule, so a change to vendor~swift-numerics~RealModule can break vendor~mlx-swift~MLXFast, while a change to vendor~mlx-swift~MLXFast can't break vendor~swift-numerics~RealModule.
- Position
- Below the diagonal: vendor~mlx-swift~MLXFast uses a module listed above it, which is the healthy direction.
34→30 vendor~mlx-swift~MLXFast uses vendor~mlx-swift~MLX✕
- Connections
- 5 pairs of types, where a type in vendor~mlx-swift~MLXFast uses a type in vendor~mlx-swift~MLX.
- The types involved
vendor~mlx-swift~MLXFast.MLXFast.swift→vendor~mlx-swift~MLX.Boolvendor~mlx-swift~MLXFast.MLXFast.swift→vendor~mlx-swift~MLX.Intvendor~mlx-swift~MLXFast.MLXFast.swift→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXFast.MLXFast.swift→vendor~mlx-swift~MLX.StreamOrDevicevendor~mlx-swift~MLXFast.MLXFastKernel.swift→vendor~mlx-swift~MLX.Bool
- Direction
- vendor~mlx-swift~MLXFast uses vendor~mlx-swift~MLX, so a change to vendor~mlx-swift~MLX can break vendor~mlx-swift~MLXFast, while a change to vendor~mlx-swift~MLXFast can't break vendor~mlx-swift~MLX.
- Position
- Below the diagonal: vendor~mlx-swift~MLXFast uses a module listed above it, which is the healthy direction.
35→29 vendor~mlx-swift~MLXLinalg uses vendor~swift-numerics~RealModule✕
- Connections
- 1 pair of types, where a type in vendor~mlx-swift~MLXLinalg uses a type in vendor~swift-numerics~RealModule.
- The types involved
vendor~mlx-swift~MLXLinalg.Linalg.swift→vendor~swift-numerics~RealModule.Double
- Direction
- vendor~mlx-swift~MLXLinalg uses vendor~swift-numerics~RealModule, so a change to vendor~swift-numerics~RealModule can break vendor~mlx-swift~MLXLinalg, while a change to vendor~mlx-swift~MLXLinalg can't break vendor~swift-numerics~RealModule.
- Position
- Below the diagonal: vendor~mlx-swift~MLXLinalg uses a module listed above it, which is the healthy direction.
35→30 vendor~mlx-swift~MLXLinalg uses vendor~mlx-swift~MLX✕
- Connections
- 6 pairs of types, where a type in vendor~mlx-swift~MLXLinalg uses a type in vendor~mlx-swift~MLX.
- The types involved
vendor~mlx-swift~MLXLinalg.Linalg.swift→vendor~mlx-swift~MLX.Boolvendor~mlx-swift~MLXLinalg.Linalg.swift→vendor~mlx-swift~MLX.Intvendor~mlx-swift~MLXLinalg.Linalg.swift→vendor~mlx-swift~MLX.IntOrArrayvendor~mlx-swift~MLXLinalg.Linalg.swift→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXLinalg.Linalg.swift→vendor~mlx-swift~MLX.NormKindvendor~mlx-swift~MLXLinalg.Linalg.swift→vendor~mlx-swift~MLX.StreamOrDevice
- Direction
- vendor~mlx-swift~MLXLinalg uses vendor~mlx-swift~MLX, so a change to vendor~mlx-swift~MLX can break vendor~mlx-swift~MLXLinalg, while a change to vendor~mlx-swift~MLXLinalg can't break vendor~mlx-swift~MLX.
- Position
- Below the diagonal: vendor~mlx-swift~MLXLinalg uses a module listed above it, which is the healthy direction.
36→29 vendor~mlx-swift~MLXNN uses vendor~swift-numerics~RealModule✕
- Connections
- 27 pairs of types, where a type in vendor~mlx-swift~MLXNN uses a type in vendor~swift-numerics~RealModule. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
vendor~mlx-swift~MLXNN.Activations.swift→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.BatchNorm→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.CELU→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.Dropout→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.Dropout2d→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.Dropout3d→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.ELU→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.GroupNorm→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.HardShrink→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.HardTanh→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.InstanceNorm→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.LayerNorm→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.LeakyReLU→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.Losses.swift→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.PReLU→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.Pool→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.RMSNorm→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.RoPE→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.SinusoidalPositionalEncoding→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.Softshrink→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.Step→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.Transformer→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.TransformerDecoder→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.TransformerDecoderLayer→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXNN.TransformerEncoder→vendor~swift-numerics~RealModule.Float
- Direction
- vendor~mlx-swift~MLXNN uses vendor~swift-numerics~RealModule, so a change to vendor~swift-numerics~RealModule can break vendor~mlx-swift~MLXNN, while a change to vendor~mlx-swift~MLXNN can't break vendor~swift-numerics~RealModule.
- Position
- Below the diagonal: vendor~mlx-swift~MLXNN uses a module listed above it, which is the healthy direction.
36→30 vendor~mlx-swift~MLXNN uses vendor~mlx-swift~MLX✕
- Connections
- 166 pairs of types, where a type in vendor~mlx-swift~MLXNN uses a type in vendor~mlx-swift~MLX. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
vendor~mlx-swift~MLXNN.ALiBi→vendor~mlx-swift~MLX.Intvendor~mlx-swift~MLXNN.ALiBi→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXNN.Activations.swift→vendor~mlx-swift~MLX.Intvendor~mlx-swift~MLXNN.Activations.swift→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXNN.ArrayOffsetLayer→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXNN.AvgPool1d→vendor~mlx-swift~MLX.Intvendor~mlx-swift~MLXNN.AvgPool2d→vendor~mlx-swift~MLX.IntOrPairvendor~mlx-swift~MLXNN.AvgPool3d→vendor~mlx-swift~MLX.IntOrTriplevendor~mlx-swift~MLXNN.BatchNorm→vendor~mlx-swift~MLX.Boolvendor~mlx-swift~MLXNN.BatchNorm→vendor~mlx-swift~MLX.Intvendor~mlx-swift~MLXNN.BatchNorm→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXNN.Bilinear→vendor~mlx-swift~MLX.Boolvendor~mlx-swift~MLXNN.Bilinear→vendor~mlx-swift~MLX.Intvendor~mlx-swift~MLXNN.Bilinear→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXNN.CELU→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXNN.Cache→vendor~mlx-swift~MLX.Intvendor~mlx-swift~MLXNN.Conv1d→vendor~mlx-swift~MLX.Boolvendor~mlx-swift~MLXNN.Conv1d→vendor~mlx-swift~MLX.Intvendor~mlx-swift~MLXNN.Conv1d→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXNN.Conv2d→vendor~mlx-swift~MLX.Boolvendor~mlx-swift~MLXNN.Conv2d→vendor~mlx-swift~MLX.Intvendor~mlx-swift~MLXNN.Conv2d→vendor~mlx-swift~MLX.IntOrPairvendor~mlx-swift~MLXNN.Conv2d→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXNN.Conv3d→vendor~mlx-swift~MLX.Boolvendor~mlx-swift~MLXNN.Conv3d→vendor~mlx-swift~MLX.Int
- Direction
- vendor~mlx-swift~MLXNN uses vendor~mlx-swift~MLX, so a change to vendor~mlx-swift~MLX can break vendor~mlx-swift~MLXNN, while a change to vendor~mlx-swift~MLXNN can't break vendor~mlx-swift~MLX.
- Position
- Below the diagonal: vendor~mlx-swift~MLXNN uses a module listed above it, which is the healthy direction.
37→29 vendor~mlx-swift~MLXRandom uses vendor~swift-numerics~RealModule✕
- Connections
- 1 pair of types, where a type in vendor~mlx-swift~MLXRandom uses a type in vendor~swift-numerics~RealModule.
- The types involved
vendor~mlx-swift~MLXRandom.Random.swift→vendor~swift-numerics~RealModule.Float
- Direction
- vendor~mlx-swift~MLXRandom uses vendor~swift-numerics~RealModule, so a change to vendor~swift-numerics~RealModule can break vendor~mlx-swift~MLXRandom, while a change to vendor~mlx-swift~MLXRandom can't break vendor~swift-numerics~RealModule.
- Position
- Below the diagonal: vendor~mlx-swift~MLXRandom uses a module listed above it, which is the healthy direction.
37→30 vendor~mlx-swift~MLXRandom uses vendor~mlx-swift~MLX✕
- Connections
- 7 pairs of types, where a type in vendor~mlx-swift~MLXRandom uses a type in vendor~mlx-swift~MLX.
- The types involved
vendor~mlx-swift~MLXRandom.Random.swift→vendor~mlx-swift~MLX.DTypevendor~mlx-swift~MLXRandom.Random.swift→vendor~mlx-swift~MLX.Intvendor~mlx-swift~MLXRandom.Random.swift→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXRandom.Random.swift→vendor~mlx-swift~MLX.Rangevendor~mlx-swift~MLXRandom.Random.swift→vendor~mlx-swift~MLX.ScalarOrArrayvendor~mlx-swift~MLXRandom.Random.swift→vendor~mlx-swift~MLX.StreamOrDevicevendor~mlx-swift~MLXRandom.Random.swift→vendor~mlx-swift~MLX.UInt64
- Direction
- vendor~mlx-swift~MLXRandom uses vendor~mlx-swift~MLX, so a change to vendor~mlx-swift~MLX can break vendor~mlx-swift~MLXRandom, while a change to vendor~mlx-swift~MLXRandom can't break vendor~mlx-swift~MLX.
- Position
- Below the diagonal: vendor~mlx-swift~MLXRandom uses a module listed above it, which is the healthy direction.
38→29 Packages~HunyuanPaintMLX~HunyuanPaintMLX uses vendor~swift-numerics~RealModule✕
- Connections
- 28 pairs of types, where a type in Packages~HunyuanPaintMLX~HunyuanPaintMLX uses a type in vendor~swift-numerics~RealModule. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Packages~HunyuanPaintMLX~HunyuanPaintMLX.Attn→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.DDIMScheduler→vendor~swift-numerics~RealModule.DoublePackages~HunyuanPaintMLX~HunyuanPaintMLX.Decoded→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.GLB.swift→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.Heap→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.ImageX→vendor~swift-numerics~RealModule.DoublePackages~HunyuanPaintMLX~HunyuanPaintMLX.ImageX→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.Inpaint→vendor~swift-numerics~RealModule.DoublePackages~HunyuanPaintMLX~HunyuanPaintMLX.Inpaint→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.L2D→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.LoadedMesh→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.MeshIO.swift→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.MeshRender→vendor~swift-numerics~RealModule.DoublePackages~HunyuanPaintMLX~HunyuanPaintMLX.MeshRender→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.PBR→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.PBRPaintResult→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.PBRWrapper→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.Paint20Wrapper→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.PaintPipeline→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.PaintResult→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.PaintVAE→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.Scheduler.swift→vendor~swift-numerics~RealModule.DoublePackages~HunyuanPaintMLX~HunyuanPaintMLX.SwiftRaster→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.UVUnwrap→vendor~swift-numerics~RealModule.FloatPackages~HunyuanPaintMLX~HunyuanPaintMLX.UniPCScheduler→vendor~swift-numerics~RealModule.Double
- Direction
- Packages~HunyuanPaintMLX~HunyuanPaintMLX uses vendor~swift-numerics~RealModule, so a change to vendor~swift-numerics~RealModule can break Packages~HunyuanPaintMLX~HunyuanPaintMLX, while a change to Packages~HunyuanPaintMLX~HunyuanPaintMLX can't break vendor~swift-numerics~RealModule.
- Position
- Below the diagonal: Packages~HunyuanPaintMLX~HunyuanPaintMLX uses a module listed above it, which is the healthy direction.
38→30 Packages~HunyuanPaintMLX~HunyuanPaintMLX uses vendor~mlx-swift~MLX✕
- Connections
- 66 pairs of types, where a type in Packages~HunyuanPaintMLX~HunyuanPaintMLX uses a type in vendor~mlx-swift~MLX. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Packages~HunyuanPaintMLX~HunyuanPaintMLX.Attn→vendor~mlx-swift~MLX.BoolPackages~HunyuanPaintMLX~HunyuanPaintMLX.Attn→vendor~mlx-swift~MLX.IntPackages~HunyuanPaintMLX~HunyuanPaintMLX.Attn→vendor~mlx-swift~MLX.MLXArrayPackages~HunyuanPaintMLX~HunyuanPaintMLX.DDIMScheduler→vendor~mlx-swift~MLX.IntPackages~HunyuanPaintMLX~HunyuanPaintMLX.DDIMScheduler→vendor~mlx-swift~MLX.MLXArrayPackages~HunyuanPaintMLX~HunyuanPaintMLX.Decoded→vendor~mlx-swift~MLX.BoolPackages~HunyuanPaintMLX~HunyuanPaintMLX.Decoded→vendor~mlx-swift~MLX.IntPackages~HunyuanPaintMLX~HunyuanPaintMLX.Dinov2→vendor~mlx-swift~MLX.IntPackages~HunyuanPaintMLX~HunyuanPaintMLX.Dinov2→vendor~mlx-swift~MLX.MLXArrayPackages~HunyuanPaintMLX~HunyuanPaintMLX.GLB.swift→vendor~mlx-swift~MLX.IntPackages~HunyuanPaintMLX~HunyuanPaintMLX.GLB.swift→vendor~mlx-swift~MLX.UInt32Packages~HunyuanPaintMLX~HunyuanPaintMLX.GLB.swift→vendor~mlx-swift~MLX.UInt8Packages~HunyuanPaintMLX~HunyuanPaintMLX.Heap→vendor~mlx-swift~MLX.BoolPackages~HunyuanPaintMLX~HunyuanPaintMLX.Heap→vendor~mlx-swift~MLX.IntPackages~HunyuanPaintMLX~HunyuanPaintMLX.Heap→vendor~mlx-swift~MLX.Int32Packages~HunyuanPaintMLX~HunyuanPaintMLX.ImageX→vendor~mlx-swift~MLX.BoolPackages~HunyuanPaintMLX~HunyuanPaintMLX.ImageX→vendor~mlx-swift~MLX.IntPackages~HunyuanPaintMLX~HunyuanPaintMLX.ImageX.swift→vendor~mlx-swift~MLX.IntPackages~HunyuanPaintMLX~HunyuanPaintMLX.ImageX.swift→vendor~mlx-swift~MLX.MLXArrayPackages~HunyuanPaintMLX~HunyuanPaintMLX.Inpaint→vendor~mlx-swift~MLX.BoolPackages~HunyuanPaintMLX~HunyuanPaintMLX.Inpaint→vendor~mlx-swift~MLX.IntPackages~HunyuanPaintMLX~HunyuanPaintMLX.Inpaint→vendor~mlx-swift~MLX.UInt8Packages~HunyuanPaintMLX~HunyuanPaintMLX.L2D→vendor~mlx-swift~MLX.IntPackages~HunyuanPaintMLX~HunyuanPaintMLX.L2D→vendor~mlx-swift~MLX.MLXArrayPackages~HunyuanPaintMLX~HunyuanPaintMLX.LoadedMesh→vendor~mlx-swift~MLX.Int
- Direction
- Packages~HunyuanPaintMLX~HunyuanPaintMLX uses vendor~mlx-swift~MLX, so a change to vendor~mlx-swift~MLX can break Packages~HunyuanPaintMLX~HunyuanPaintMLX, while a change to Packages~HunyuanPaintMLX~HunyuanPaintMLX can't break vendor~mlx-swift~MLX.
- Position
- Below the diagonal: Packages~HunyuanPaintMLX~HunyuanPaintMLX uses a module listed above it, which is the healthy direction.
38→31 Packages~HunyuanPaintMLX~HunyuanPaintMLX uses Core✕
- Connections
- 4 pairs of types, where a type in Packages~HunyuanPaintMLX~HunyuanPaintMLX uses a type in Core.
- The types involved
Packages~HunyuanPaintMLX~HunyuanPaintMLX.GLB.swift→Core.DataPackages~HunyuanPaintMLX~HunyuanPaintMLX.ImageX.swift→Core.DataPackages~HunyuanPaintMLX~HunyuanPaintMLX.PBRPaintResult→Core.DataPackages~HunyuanPaintMLX~HunyuanPaintMLX.PaintResult→Core.Data
- Direction
- Packages~HunyuanPaintMLX~HunyuanPaintMLX uses Core, so a change to Core can break Packages~HunyuanPaintMLX~HunyuanPaintMLX, while a change to Packages~HunyuanPaintMLX~HunyuanPaintMLX can't break Core.
- Position
- Below the diagonal: Packages~HunyuanPaintMLX~HunyuanPaintMLX uses a module listed above it, which is the healthy direction.
39→29 vendor~mlx-swift~MLXOptimizers uses vendor~swift-numerics~RealModule✕
- Connections
- 10 pairs of types, where a type in vendor~mlx-swift~MLXOptimizers uses a type in vendor~swift-numerics~RealModule.
- The types involved
vendor~mlx-swift~MLXOptimizers.AdaDelta→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXOptimizers.AdaGrad→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXOptimizers.Adafactor→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXOptimizers.Adam→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXOptimizers.AdamW→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXOptimizers.Adamax→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXOptimizers.Lion→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXOptimizers.Optimizers.swift→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXOptimizers.RMSprop→vendor~swift-numerics~RealModule.Floatvendor~mlx-swift~MLXOptimizers.SGD→vendor~swift-numerics~RealModule.Float
- Direction
- vendor~mlx-swift~MLXOptimizers uses vendor~swift-numerics~RealModule, so a change to vendor~swift-numerics~RealModule can break vendor~mlx-swift~MLXOptimizers, while a change to vendor~mlx-swift~MLXOptimizers can't break vendor~swift-numerics~RealModule.
- Position
- Below the diagonal: vendor~mlx-swift~MLXOptimizers uses a module listed above it, which is the healthy direction.
39→30 vendor~mlx-swift~MLXOptimizers uses vendor~mlx-swift~MLX✕
- Connections
- 24 pairs of types, where a type in vendor~mlx-swift~MLXOptimizers uses a type in vendor~mlx-swift~MLX.
- The types involved
vendor~mlx-swift~MLXOptimizers.AdaDelta→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.AdaGrad→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.Adafactor→vendor~mlx-swift~MLX.Boolvendor~mlx-swift~MLXOptimizers.Adafactor→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.Adam→vendor~mlx-swift~MLX.Boolvendor~mlx-swift~MLXOptimizers.Adam→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.AdamState→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.AdamState→vendor~mlx-swift~MLX.Updatablevendor~mlx-swift~MLXOptimizers.AdamW→vendor~mlx-swift~MLX.Boolvendor~mlx-swift~MLXOptimizers.AdamW→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.Adamax→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.Lion→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.Optimizer→vendor~mlx-swift~MLX.Evaluatablevendor~mlx-swift~MLXOptimizers.Optimizer→vendor~mlx-swift~MLX.Updatablevendor~mlx-swift~MLXOptimizers.OptimizerBase→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.OptimizerBase→vendor~mlx-swift~MLX.NestedDictionaryvendor~mlx-swift~MLXOptimizers.OptimizerBaseArrayState→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.RMSprop→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.SGD→vendor~mlx-swift~MLX.Boolvendor~mlx-swift~MLXOptimizers.SGD→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.State→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.State→vendor~mlx-swift~MLX.Updatablevendor~mlx-swift~MLXOptimizers.TupleState→vendor~mlx-swift~MLX.MLXArrayvendor~mlx-swift~MLXOptimizers.TupleState→vendor~mlx-swift~MLX.Updatable
- Direction
- vendor~mlx-swift~MLXOptimizers uses vendor~mlx-swift~MLX, so a change to vendor~mlx-swift~MLX can break vendor~mlx-swift~MLXOptimizers, while a change to vendor~mlx-swift~MLXOptimizers can't break vendor~mlx-swift~MLX.
- Position
- Below the diagonal: vendor~mlx-swift~MLXOptimizers uses a module listed above it, which is the healthy direction.
39→36 vendor~mlx-swift~MLXOptimizers uses vendor~mlx-swift~MLXNN✕
- Connections
- 2 pairs of types, where a type in vendor~mlx-swift~MLXOptimizers uses a type in vendor~mlx-swift~MLXNN.
- The types involved
vendor~mlx-swift~MLXOptimizers.Optimizer→vendor~mlx-swift~MLXNN.Modulevendor~mlx-swift~MLXOptimizers.OptimizerBase→vendor~mlx-swift~MLXNN.Module
- Direction
- vendor~mlx-swift~MLXOptimizers uses vendor~mlx-swift~MLXNN, so a change to vendor~mlx-swift~MLXNN can break vendor~mlx-swift~MLXOptimizers, while a change to vendor~mlx-swift~MLXOptimizers can't break vendor~mlx-swift~MLXNN.
- Position
- Below the diagonal: vendor~mlx-swift~MLXOptimizers uses a module listed above it, which is the healthy direction.
40→29 repository uses vendor~swift-numerics~RealModule✕
- Connections
- 9 pairs of types, where a type in repository uses a type in vendor~swift-numerics~RealModule.
- The types involved
repository.Generation→vendor~swift-numerics~RealModule.Doublerepository.PaintMeshWriter→vendor~swift-numerics~RealModule.Floatrepository.Project→vendor~swift-numerics~RealModule.Doublerepository.ProjectDetailView→vendor~swift-numerics~RealModule.Doublerepository.ProjectStore→vendor~swift-numerics~RealModule.Doublerepository.RunSettings→vendor~swift-numerics~RealModule.Doublerepository.ShapeEngine→vendor~swift-numerics~RealModule.Floatrepository.ShapeMeshWriter→vendor~swift-numerics~RealModule.Floatrepository.SmoothProgressBar→vendor~swift-numerics~RealModule.Double
- Direction
- repository uses vendor~swift-numerics~RealModule, so a change to vendor~swift-numerics~RealModule can break repository, while a change to repository can't break vendor~swift-numerics~RealModule.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
40→30 repository uses vendor~mlx-swift~MLX✕
- Connections
- 66 pairs of types, where a type in repository uses a type in vendor~mlx-swift~MLX. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
repository.AppDelegate→vendor~mlx-swift~MLX.Boolrepository.AppRuntime→vendor~mlx-swift~MLX.Boolrepository.AppRuntime→vendor~mlx-swift~MLX.Intrepository.AppRuntime→vendor~mlx-swift~MLX.UInt64repository.BackgroundRemover→vendor~mlx-swift~MLX.Intrepository.Choice→vendor~mlx-swift~MLX.Int64repository.DiskSpace→vendor~mlx-swift~MLX.Int64repository.FailurePill→vendor~mlx-swift~MLX.Boolrepository.FailurePill→vendor~mlx-swift~MLX.UInt64repository.Generation→vendor~mlx-swift~MLX.Boolrepository.Generation→vendor~mlx-swift~MLX.Intrepository.Generation→vendor~mlx-swift~MLX.UInt64repository.HostedCanvas→vendor~mlx-swift~MLX.Boolrepository.ImageDropView→vendor~mlx-swift~MLX.Boolrepository.ImageDropView→vendor~mlx-swift~MLX.Intrepository.ManifestFile→vendor~mlx-swift~MLX.Int64repository.MaskCanvas→vendor~mlx-swift~MLX.Boolrepository.MaskEditorOverlay→vendor~mlx-swift~MLX.Boolrepository.MeshViewer→vendor~mlx-swift~MLX.Boolrepository.MeshViewer→vendor~mlx-swift~MLX.Intrepository.ModelSettingsPopover→vendor~mlx-swift~MLX.ClosedRangerepository.ModelSettingsPopover→vendor~mlx-swift~MLX.Intrepository.ModelSettingsPopover→vendor~mlx-swift~MLX.UInt64repository.ModelStore→vendor~mlx-swift~MLX.Boolrepository.ModelStore→vendor~mlx-swift~MLX.Int64
- Direction
- repository uses vendor~mlx-swift~MLX, so a change to vendor~mlx-swift~MLX can break repository, while a change to repository can't break vendor~mlx-swift~MLX.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
40→31 repository uses Core✕
- Connections
- 27 pairs of types, where a type in repository uses a type in Core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
repository.AppRuntime→Core.AppEffectrepository.AppRuntime→Core.AppEventrepository.AppRuntime→Core.AppStaterepository.AppRuntime→Core.BootReportrepository.AppRuntime→Core.DownloadManagerrepository.AppRuntime→Core.EngineArbiterrepository.AppRuntime→Core.ModelIDrepository.AppRuntime→Core.PaintStagerepository.AppRuntime→Core.ShapeStagerepository.BackgroundRemover→Core.Datarepository.EventBridge→Core.AppEventrepository.ModelManagerView→Core.ModelIDrepository.ModelRow→Core.CatalogModelrepository.ModelRow→Core.ModelIDrepository.ModelRow→Core.ModelInstallStaterepository.ModelStore→Core.ModelIDrepository.NSImage→Core.Datarepository.OnboardingView→Core.ModelIDrepository.OnboardingView→Core.ModelInstallStaterepository.PaintMeshWriter→Core.Datarepository.PaintModel→Core.ModelIDrepository.ProjectDetailView→Core.MeshExportFormatrepository.ProjectDetailView→Core.PaintJobStaterepository.ProjectDetailView→Core.ShapeJobStaterepository.ShapeMeshWriter→Core.Data
- Direction
- repository uses Core, so a change to Core can break repository, while a change to repository can't break Core.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
40→32 repository uses Packages~Hy3DMLX~Hy3DMLX✕
- Connections
- 2 pairs of types, where a type in repository uses a type in Packages~Hy3DMLX~Hy3DMLX.
- The types involved
repository.ShapeEngine→Packages~Hy3DMLX~Hy3DMLX.ShapeGeneratorrepository.ShapeMeshWriter→Packages~Hy3DMLX~Hy3DMLX.Mesh
- Direction
- repository uses Packages~Hy3DMLX~Hy3DMLX, so a change to Packages~Hy3DMLX~Hy3DMLX can break repository, while a change to repository can't break Packages~Hy3DMLX~Hy3DMLX.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
40→38 repository uses Packages~HunyuanPaintMLX~HunyuanPaintMLX✕
- Connections
- 2 pairs of types, where a type in repository uses a type in Packages~HunyuanPaintMLX~HunyuanPaintMLX.
- The types involved
repository.PaintEngine→Packages~HunyuanPaintMLX~HunyuanPaintMLX.LoadedMeshrepository.PaintEngine→Packages~HunyuanPaintMLX~HunyuanPaintMLX.PaintPipeline
- Direction
- repository uses Packages~HunyuanPaintMLX~HunyuanPaintMLX, so a change to Packages~HunyuanPaintMLX~HunyuanPaintMLX can break repository, while a change to repository can't break Packages~HunyuanPaintMLX~HunyuanPaintMLX.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
| A05:2025 — Injection | 2 | High / Critical |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; 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; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +8.9 pts | Medium | Observability |
| 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.8 pts | Medium | Architecture documentation |
| 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. | +3.1 pts | Medium | Deployment & Rollback |
| Run the test suite in CI via an explicit runner step (`xcodebuild test` for the toolchain this pipeline already uses) and gate merges on it. | +1.6 pts | Medium | CI/CD gates |
| Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with AppReducer.swift, AppRuntime.swift, Pipeline.swift. | +1.4 pts | High | Churn × Complexity Hotspots |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +0.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.3 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| Sources/Core/MeshDecimator.swift | 7.0 | Mixed | Cyclomatic Complexity: Engine.collapse (cyclomatic 22) |
| Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift | 7.0 | Mixed | Cyclomatic Complexity: PaintPipeline.paintPBR (cyclomatic 20) |
| Sources/ProjectStore.swift | 7.0 | Mixed | Cyclomatic Complexity: ProjectStore.applyImage (cyclomatic 16) |
| Sources/EffortSlider.swift | 7.0 | Mixed | Code Duplication: Edited copy of a member (29 corresponding lines) |
| Sources/Core/AppReducer.swift | 7.0 | Mixed | Cyclomatic Complexity: AppReducer.reduce (cyclomatic 132) |
| Sources/AppRuntime.swift | 7.1 | Mixed | Cyclomatic Complexity: AppRuntime.perform (cyclomatic 37) |
| Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/MeshIO.swift | 7.1 | Mixed | Cyclomatic Complexity: MeshIO.swift.loadGLB (cyclomatic 27) |
| Packages/Hy3DMLX/Sources/Hy3DMLX/Pipeline.swift | 7.1 | Mixed | Cyclomatic Complexity: Pipeline.nearSurfaceMask (cyclomatic 20) |
| Sources/Core/MeshExporter.swift | 7.1 | Mixed | Cyclomatic Complexity: MeshExporter.encodeGLB (cyclomatic 19) |
| Sources/PaintEngine.swift | 7.1 | Mixed | Code Duplication: Edited copy of a member (54 corresponding lines) |
| Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Inpaint.swift | 7.2 | Mixed | Cyclomatic Complexity: Inpaint.navierStokes (cyclomatic 46) |
| Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/ImageX.swift | 7.2 | Mixed | Cyclomatic Complexity: ImageX.decodeStraightRGBA (cyclomatic 34) |
| Sources/SmokeRunner.swift | 7.4 | Mixed | Cyclomatic Complexity: SmokeRunner.run (cyclomatic 47) |
| Sources/Core/DownloadManager.swift | 7.4 | Mixed | Cyclomatic Complexity: DownloadManager.downloadFile (cyclomatic 16) |
| Sources/MeshViewer.swift | 7.4 | Mixed | Cognitive Complexity: MeshViewer.loadPoints (cognitive 16) |
| Packages/Hy3DMLX/Sources/Hy3DMLX/DINOv2.swift | 7.4 | Mixed | Code Duplication: Edited copy of a member (8 corresponding lines) |
| Packages/Hy3DMLX/Sources/Hy3DMLX/GLB.swift | 7.8 | Mixed | Cyclomatic Complexity: GLB.read (cyclomatic 22) |
| Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/GLB.swift | 7.8 | Mixed | Cognitive Complexity: GLB.swift.writeGLB (cognitive 22) |
| Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Scheduler.swift | 7.8 | Mixed | Code Duplication: Edited copy of a member (24 corresponding lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 36 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 36 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 154 of 163 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D4 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 18 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .cpp (9,675 lines, 46% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in vendor/swift-numerics produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 0 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — none of the 0 package(s) this repository's SwiftPM files bring in could be read at a pinned revision or is a repository the public index (api.deps.dev) knows, so no licence could be read for any of them: they are private, self-hosted, or unpinned and too little-referenced to be indexed. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- 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-contributor repository — bus factor is not applicable (1 contributor(s) across 40 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Project size and spread are measured over build units whose source a code model reads. This repository's .cpp source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
- D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 931 sampled here came from .swift files. This repository's .cpp source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/SwiftRaster.swift` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (40 commit(s) sampled).
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Swift, c, cpp is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Swift, c, cpp 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust, Dart, F# and Elixir source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust, Dart, F# or Elixir was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala, PHP and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala, PHP or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# and Visual Basic syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin, PHP, F# and Visual Basic source only, and no C# was loaded, and this repository's C, C++, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin, PHP and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin, PHP or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart, Ruby and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart, Ruby or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala, Kotlin, PHP and Go source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala, Kotlin, PHP or Go was found, and this repository's C++ is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Scala, JavaScript/TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart, Ruby and Erlang source only, and no C# was loaded and no Scala, JavaScript, TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart, Ruby or Erlang was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, Kotlin source, and Rust source only, and no C# was loaded, no TypeScript was found, and this repository's C, Cpp, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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").
- 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.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- 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").
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
20 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AppReducer.reduce at 132.
What to do
- Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with AppReducer.reduce (cyclomatic 132). — Refactoring it lifts Cyclomatic Complexity from 5.6 to about 6.6/10.
D2 · Cognitive Complexity
29 method(s) exceeded the cognitive complexity threshold of 15; the worst was AppReducer.reduce at 160.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with AppReducer.reduce (cognitive 160), Inpaint.navierStokes (cognitive 140), ImageX.decodeStraightRGBA (cognitive 66). — 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 3 together lifts Cognitive Complexity from 3.6 to about 5.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
9 god class(es) detected.
What to do
- Resolve the 4 MethodTooLong finding(s) in God Classes — start with AppReducer.swift, AppRuntime.swift, SmokeRunner.swift. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 ClassTooLong finding(s) in God Classes — start with ProjectStore.swift, AppReducer.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with ProjectStore.swift. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
18 duplicated block group(s) detected. 9.2 % of the production lines (1,055 of 11,434) are in a reported copy. A further 38 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .cpp (46% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
What to do
- Resolve the 6 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Pipeline.swift (2), MeshViewer.swift (2), AppRuntime.swift. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 4 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with Attention.swift, EffortSlider.swift, MeshExporter.swift. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Edited copy of a member (3 corresponding lines) finding(s) in Code Duplication — start with Pipeline.swift, DINOv2.swift, DownloadManager.swift. — One of this dimension's main actionable groups (4 warning-level).
D5 · Coupling
4 production modules (SwiftPM+XcodeGen), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; an XcodeGen target's dependency on a local Swift package or on a target of another project is not visible there; 0 module(s) off the main sequence, with abstractness counted on 3 of the 4 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
2 of 37 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with MLXArray.swift, Module.swift. — One of this dimension's main actionable groups (2 warning-level).
D10 · Test Quality
0 skipped, 29 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 147 tests (2 harness-style project(s) excluded from the assertion penalty).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Swift (swift-numerics): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: Sources/Core/AppReducer.swift (2×132=264); Sources/AppRuntime.swift (2×37=74); Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift (4×17=68)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with AppReducer.swift, AppRuntime.swift, Pipeline.swift. — One of this dimension's main actionable groups (3 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 11434 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.
D26 · Project Cohesion
1 of 3 build units (SwiftPM, XcodeGen) flagged as possibly oversized/incoherent. This repository's .cpp source was read by no build unit, so this covers part of the tree, not all of it.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with project.yml. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
19 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .swift source only — this repository's .cpp was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- No action in Static Analysis (SAST) — all 2 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 (2 issue-level, 0 of them charged here).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
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.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no test-runner invocation (your stack's test command, or a test job) was found — changes may merge without the suite running.
What to do
- Run the test suite in CI via an explicit runner step (`xcodebuild test` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- 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. — REDACTED:52
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
PF3 · Async & latency hygiene
X3 · Exception handling
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81.9 | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 95.0 | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 71.0 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 46.3 | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 81.2 | Checked 4 of 9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Not evidenced — 2 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 78 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's 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; this repository's Swift 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 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. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads.
- 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported 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 property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D12 Dependency Hygiene — Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 0 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 — SwiftPM package licences not graded — no dependency repository could be read
- D16 Bus Factor — single-contributor 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.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 7 candidate(s) found and not reported.
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Swift surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .swift, 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
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Swift suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 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 this analysis resolves a call's owner only where the receiver's type is written down 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, Scala, Rust and Java, 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 Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. In C a `case` label must be a constant expression, and a switch has no guards, so no label can change state. In C++ a `case` label must be a constant expression, and a switch has no guards, so no label can change state. Swift has no `++` or `--`, and an assignment yields `()`, which cannot be an operand of `&&`, `||` or `?:` nor the Bool a `case … where` clause needs. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — 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
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not 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 Swift was read, and it logs through none: `print` and `NSLog` take one finished line, and os's `Logger` keeps each interpolated value as its own argument, so an assembled message there loses nothing the API could have kept (as with log4net in C#). Calls through swift-log (`import Logging`) and `os_log` calls would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 2 finding(s)
- REDACTED
- REDACTED
Serious — 123 finding(s)
- Duplicated block (5 lines × 2) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift:79
- Duplicated block (5 lines × 2) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift:135
- Duplicated block (5 lines × 2) Sources/AppRuntime.swift:436
- Duplicated block (5 lines × 2) Sources/MeshViewer.swift:146
- Duplicated block (5 lines × 2) Packages/Hy3DMLX/Sources/Hy3DMLX/DINOv2.swift:29
- Duplicated block (5 lines × 2) Sources/MeshViewer.swift:175
- MethodTooLong: AppReducer.reduce Sources/Core/AppReducer.swift:20
- MethodTooLong: AppRuntime.perform Sources/AppRuntime.swift:160
- MethodTooLong: SmokeRunner.run Sources/SmokeRunner.swift:57
- MethodTooLong: MeshExporter.encodeGLB Sources/Core/MeshExporter.swift:268
- Edited copy of a member (7 corresponding lines) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Attention.swift:30
- Edited copy of a member (7 corresponding lines) Sources/EffortSlider.swift:226
- Edited copy of a member (7 corresponding lines) Sources/Core/MeshExporter.swift:126
- Edited copy of a member (7 corresponding lines) Sources/ProjectStore.swift:27
- Edited copy of a member (3 corresponding lines) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift:66
- Edited copy of a member (3 corresponding lines) Packages/Hy3DMLX/Sources/Hy3DMLX/DINOv2.swift:34
- Edited copy of a member (3 corresponding lines) Sources/Core/DownloadManager.swift:61
- Edited copy of a member (3 corresponding lines) Sources/EffortSlider.swift:160
- Hotspot: Sources/Core/AppReducer.swift Sources/Core/AppReducer.swift:20
- Hotspot: Sources/AppRuntime.swift Sources/AppRuntime.swift:160
- Hotspot: Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift:128
- Edited copy of a member (4 corresponding lines) Packages/Hy3DMLX/Sources/Hy3DMLX/Preprocess.swift:39
- Edited copy of a member (4 corresponding lines) Sources/EffortSlider.swift:214
- Edited copy of a member (4 corresponding lines) Sources/EffortSlider.swift:198
- Edited copies of one member (3 members, 3+ corresponding lines) Sources/Core/MeshDecimator.swift:151
- Edited copies of one member (3 members, 3+ corresponding lines) Sources/Core/MeshDecimator.swift:154
- Edited copies of one member (3 members, 3+ corresponding lines) Sources/Core/MeshDecimator.swift:157
- Duplicated block (10 lines × 2) Sources/Core/AppReducer.swift:376
- Duplicated block (10 lines × 2) Sources/PaintEngine.swift:176
- Duplicated block (10 lines × 2) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift:142
- ClassTooLong: ProjectStore Sources/ProjectStore.swift:10
- ClassTooLong: AppReducer Sources/Core/AppReducer.swift:18
- Edited copy of a member (20 corresponding lines) Sources/Core/MeshDecimator.swift:130
- Edited copy of a member (20 corresponding lines) Sources/EffortSlider.swift:51
- Edited copy of a member (10 corresponding lines) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Attention.swift:43
- Edited copy of a member (10 corresponding lines) Sources/AppRuntime.swift:434
- Edited copy of a member (11 corresponding lines) Packages/Hy3DMLX/Sources/Hy3DMLX/VAE.swift:35
- Edited copy of a member (11 corresponding lines) Sources/ProjectStore.swift:261
- Edited copy of a member (18 corresponding lines) Sources/ProjectDetailView.swift:167
- Edited copy of a member (18 corresponding lines) Sources/ProjectDetailView.swift:349
- Edited copy of a member (17 corresponding lines) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift:70
- Edited copy of a member (17 corresponding lines) Sources/EffortSlider.swift:74
- Edited copy of a member (5 corresponding lines) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Layers2D.swift:70
- Edited copy of a member (5 corresponding lines) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Layers2D.swift:32
- Duplicated block (15–16 lines × 2) Sources/EffortSlider.swift:142
- Duplicated block (15–16 lines × 2) Sources/PaintEngine.swift:26
- Low cohesion: MLXArray (LCOM4 5) vendor/mlx-swift/Source/MLX/MLXArray.swift:7
- Low cohesion: Module (LCOM4 4) vendor/mlx-swift/Source/MLXNN/Module.swift:97
- AppReducer.reduce (cyclomatic 132) Sources/Core/AppReducer.swift:20
- SmokeRunner.run (cyclomatic 47) Sources/SmokeRunner.swift:57
- Inpaint.navierStokes (cyclomatic 46) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Inpaint.swift:133
- AppRuntime.perform (cyclomatic 37) Sources/AppRuntime.swift:160
- ImageX.decodeStraightRGBA (cyclomatic 34) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/ImageX.swift:142
- MeshIO.swift.loadGLB (cyclomatic 27) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/MeshIO.swift:48
- Engine.collapse (cyclomatic 22) Sources/Core/MeshDecimator.swift:336
- GLB.read (cyclomatic 22) Packages/Hy3DMLX/Sources/Hy3DMLX/GLB.swift:10
- AppReducer.advancedPaintState (cyclomatic 20) Sources/Core/AppReducer.swift:566
- ImageX.resampleAxis (cyclomatic 20) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/ImageX.swift:37
- PaintPipeline.paintPBR (cyclomatic 20) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift:202
- Pipeline.nearSurfaceMask (cyclomatic 20) Packages/Hy3DMLX/Sources/Hy3DMLX/Pipeline.swift:153
- MeshExporter.encodeGLB (cyclomatic 19) Sources/Core/MeshExporter.swift:268
- Inpaint.edtIndices (cyclomatic 18) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Inpaint.swift:20
- MeshIO.swift.loadOBJ (cyclomatic 18) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/MeshIO.swift:118
- PaintPipeline.paintRGB (cyclomatic 17) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift:128
- Pipeline.gridSDFOctree (cyclomatic 17) Packages/Hy3DMLX/Sources/Hy3DMLX/Pipeline.swift:88
- AppReducer.advancedShapeState (cyclomatic 16) Sources/Core/AppReducer.swift:540
- DownloadManager.downloadFile (cyclomatic 16) Sources/Core/DownloadManager.swift:168
- ProjectStore.applyImage (cyclomatic 16) Sources/ProjectStore.swift:385
- AppReducer.reduce (cognitive 160) Sources/Core/AppReducer.swift:20
- Inpaint.navierStokes (cognitive 140) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Inpaint.swift:133
- ImageX.decodeStraightRGBA (cognitive 66) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/ImageX.swift:142
- SmokeRunner.run (cognitive 50) Sources/SmokeRunner.swift:57
- Pipeline.nearSurfaceMask (cognitive 47) Packages/Hy3DMLX/Sources/Hy3DMLX/Pipeline.swift:153
- ImageX.resampleAxis (cognitive 46) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/ImageX.swift:37
- Inpaint.edtIndices (cognitive 43) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Inpaint.swift:20
- MeshIO.swift.loadGLB (cognitive 43) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/MeshIO.swift:48
- MeshIO.swift.loadOBJ (cognitive 42) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/MeshIO.swift:118
- MarchingCubes.extract (cognitive 39) Packages/Hy3DMLX/Sources/Hy3DMLX/MarchingCubes.swift:16
- PBRWrapper.voxelIndices (cognitive 36) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/PBRWrapper.swift:55
- Pipeline.gridSDFOctree (cognitive 35) Packages/Hy3DMLX/Sources/Hy3DMLX/Pipeline.swift:88
- ProjectStore.load (cognitive 30) Sources/ProjectStore.swift:718
- Engine.collapse (cognitive 28) Sources/Core/MeshDecimator.swift:336
- MeshExporter.encodeGLB (cognitive 26) Sources/Core/MeshExporter.swift:268
- PaintPipeline.paintPBR (cognitive 23) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift:202
- GLB.read (cognitive 23) Packages/Hy3DMLX/Sources/Hy3DMLX/GLB.swift:10
- Engine.wouldFlip (cognitive 22) Sources/Core/MeshDecimator.swift:398
- GLB.swift.writeGLB (cognitive 22) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/GLB.swift:53
- AppRuntime.perform (cognitive 22) Sources/AppRuntime.swift:160
- Pipeline.dilate (cognitive 21) Packages/Hy3DMLX/Sources/Hy3DMLX/Pipeline.swift:176
- PaintPipeline.paintRGB (cognitive 20) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift:128
- ProjectStore.applyImage (cognitive 20) Sources/ProjectStore.swift:385
- DownloadManager.downloadFile (cognitive 18) Sources/Core/DownloadManager.swift:168
- PaintUNet.callAsFunction (cognitive 18) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/UNet.swift:27
- Engine.build (cognitive 17) Sources/Core/MeshDecimator.swift:246
- MeshExporter.encodeOBJ (cognitive 17) Sources/Core/MeshExporter.swift:175
- MeshIO.swift.readIndices (cognitive 16) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/MeshIO.swift:304
- MeshViewer.loadPoints (cognitive 16) Sources/MeshViewer.swift:253
- TooManyMethods: ProjectStore Sources/ProjectStore.swift:10
- FunctionTooLong: GLB.swift.writeGLB Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/GLB.swift:53
- FileTooLong: Sources/ProjectStore.swift Sources/ProjectStore.swift
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (23 shared lines) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift:128
- Edited copy of a member (54 corresponding lines) Sources/PaintEngine.swift:23
- Edited copy of a member (24 corresponding lines) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Scheduler.swift:144
- Edited copy of a member (16 corresponding lines) Sources/Core/MeshDecimator.swift:100
- Edited copy of a member (29 corresponding lines) Sources/EffortSlider.swift:125
- Edited copy of a member (23 corresponding lines) Sources/Core/AppReducer.swift:540
- Edited copy of a member (22 corresponding lines) Sources/OnboardingView.swift:61
- Edited copy of a member (14 corresponding lines) Sources/ProjectStore.swift:344
- Edited copy of a member (8 corresponding lines) Packages/Hy3DMLX/Sources/Hy3DMLX/DINOv2.swift:26
- Edited copy of a member (15 corresponding lines) Sources/Core/AppReducer.swift:596
- Edited copy of a member (6 corresponding lines) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/MeshRender.swift:228
- Edited copies of one member (3 members, 7+ corresponding lines) Sources/ProjectStore.swift:51
- Duplicated block (21 lines × 2) Sources/PaintEngine.swift:44
- Duplicated block (16 lines × 2) Sources/EffortSlider.swift:166
- Duplicated block (12 lines × 2) Sources/EffortSlider.swift:183
- Duplicated block (8 lines × 2) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Pipeline.swift:171
- Duplicated block (6 lines × 3) Sources/PaintEngine.swift:27
- Duplicated block (6 lines × 2) Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/Scheduler.swift:154
- Duplicated block (9 lines × 2) Sources/Core/MeshDecimator.swift:138
- No structured logging
Minor — 38 finding(s)
- No direct assertions: testFloat vendor/swift-numerics/Tests/ComplexTests/ApproximateEqualityTests.swift:55
- No direct assertions: testDouble vendor/swift-numerics/Tests/ComplexTests/ApproximateEqualityTests.swift:59
- No direct assertions: testFloat80 vendor/swift-numerics/Tests/ComplexTests/ApproximateEqualityTests.swift:64
- No direct assertions: testPolar vendor/swift-numerics/Tests/ComplexTests/ArithmeticTests.swift:169
- No direct assertions: testFloat vendor/swift-numerics/Tests/ComplexTests/ElementaryFunctionTests.swift:415
- No direct assertions: testDouble vendor/swift-numerics/Tests/ComplexTests/ElementaryFunctionTests.swift:430
- No direct assertions: testFloat80 vendor/swift-numerics/Tests/ComplexTests/ElementaryFunctionTests.swift:446
- No direct assertions: testProperties vendor/swift-numerics/Tests/ComplexTests/PropertyTests.swift:42
- No direct assertions: testEquatableHashable vendor/swift-numerics/Tests/ComplexTests/PropertyTests.swift:98
- No direct assertions: testCodable vendor/swift-numerics/Tests/ComplexTests/PropertyTests.swift:127
- No direct assertions: testFloat vendor/swift-numerics/Tests/RealTests/ApproximateEqualityTests.swift:126
- No direct assertions: testDouble vendor/swift-numerics/Tests/RealTests/ApproximateEqualityTests.swift:132
- No direct assertions: testFloat80 vendor/swift-numerics/Tests/RealTests/ApproximateEqualityTests.swift:139
- No direct assertions: testTwoSum vendor/swift-numerics/Tests/RealTests/AugmentedArithmeticTests.swift:146
- No direct assertions: testFloat16 vendor/swift-numerics/Tests/RealTests/ElementaryFunctionChecks.swift:150
- No direct assertions: testFloat vendor/swift-numerics/Tests/RealTests/ElementaryFunctionChecks.swift:159
- No direct assertions: testDouble vendor/swift-numerics/Tests/RealTests/ElementaryFunctionChecks.swift:165
- No direct assertions: testFloat80 vendor/swift-numerics/Tests/RealTests/ElementaryFunctionChecks.swift:172
- No direct assertions: testFloat16 vendor/swift-numerics/Tests/RealTests/IntegerExponentTests.swift:178
- No direct assertions: testFloat vendor/swift-numerics/Tests/RealTests/IntegerExponentTests.swift:185
- No direct assertions: testDouble vendor/swift-numerics/Tests/RealTests/IntegerExponentTests.swift:189
- No direct assertions: testFloat80 vendor/swift-numerics/Tests/RealTests/IntegerExponentTests.swift:194
- No direct assertions: testStrictSumPerformance vendor/swift-numerics/Tests/RealTests/RelaxedArithmeticTests.swift:56
- No direct assertions: testRelaxedSumPerformance vendor/swift-numerics/Tests/RealTests/RelaxedArithmeticTests.swift:60
- No direct assertions: testvDSPSumPerformance vendor/swift-numerics/Tests/RealTests/RelaxedArithmeticTests.swift:67
- Test project verifies nothing: RealTests vendor/swift-numerics/Tests/RealTests/ApproximateEqualityTests.swift:126
- Projects may be oversized for their cohesion project.yml:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- CI test execution not evidenced
- No SAST
- No release approval gate REDACTED:52
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cac3e17d14c44f7cbf2639a4dd726def/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cac3e17d14c44f7cbf2639a4dd726def/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 2 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `Packages/HunyuanPaintMLX/Sources/HunyuanPaintMLX/SwiftRaster.swift` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |