Executive summary
LaurentMazare/tch-rs meets our standard for a preview release, though we found no logging, tracing or health checks in the code. It scores 66 out of 100 and is rated Strong, and all 14 of its critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 54, is the weakest lens and counts most in the score. The best first step is adding a diagnostic log, worth about 8 points. Recording design decisions comes next, worth about 7 points. Raising Production Readiness to 62 would lift the score to about 69.
Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks.
The product code is 10,935 lines, about €23,000 to rebuild.
If Production Readiness rose from 54 to 62, the lowest score rated Strong, the score would rise from 66 to about 69.
New since the last survey: 35 findings
- Code Duplication · Edited copy of a member (9 corresponding lines) src/vision/efficientnet.rs
- Code Duplication · Edited copy of a member (28 corresponding lines) src/vision/inception.rs
- Code Duplication · Edited copy of a member (22 corresponding lines) src/vision/resnet.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/vision/inception.rs
- Code Duplication · Edited copy of a member (17 corresponding lines) src/wrappers/tensor.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/vision/resnet.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/nn/sequential.rs
- Code Duplication · Edited copy of a member (21 corresponding lines) src/nn/rnn.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) src/nn/var_store.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/nn/var_store.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) src/vision/inception.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/nn/batch_norm.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/wrappers/tensor.rs
- Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) src/wrappers/jit.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/nn/conv.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/nn/var_store.rs
- Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) src/tensor/index.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) src/wrappers/jit.rs
- Code Duplication · Edited copy of a member (6 corresponding lines) src/wrappers/jit.rs
- Code Duplication · Edited copy of a member (6 corresponding lines) src/nn/rnn.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) src/nn/sequential.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) src/wrappers/jit.rs
- Code Duplication · Edited copy of a member (6 corresponding lines) src/wrappers/tensor.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) torch-sys/src/io.rs
- Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) src/wrappers/tensor.rs
- Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) src/vision/rust_image.rs
- Code Duplication · Edited copy of a member (4 corresponding lines) src/nn/optimizer.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/nn/group_norm.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/nn/group_norm.rs
- Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) src/vision/alexnet.rs
- Code Duplication · Edited copy of a member (4 corresponding lines) src/vision/cifar.rs
- Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) src/tensor/mod.rs
- Code Duplication · Duplicated block (6 lines × 2) src/wrappers/jit.rs
- Code Duplication · Duplicated block (5 lines × 2) src/vision/efficientnet.rs
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 17 findings
- Code Duplication · Duplicated block (23 lines × 2) src/wrappers/kind.rs
- Code Duplication · Duplicated block (6 lines × 2) src/wrappers/jit.rs
- Code Duplication · Duplicated block (5 lines × 2) src/vision/resnet.rs
- Dependency Vulnerabilities · High vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0395 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0397 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0399 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0400 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0401 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0402 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0404 REDACTED
- Dependency Vulnerabilities · Medium advisory (unsound): RUSTSEC-2026-0406 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0367 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0403 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0410 REDACTED
Rebuild cost: about €23,000 · Estimate
| Cost to rebuild | €7,800 to €39,000, for 129 to 410 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 66. 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: 10,935 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 tch.error | 2 tch.wrappers.kind | 3 tch.nn.module | 4 tch.nn.var_store | 5 tch.tensor.index | 6 tch.tensor.npy | 7 tch.wrappers.jit | 8 tch.wrappers.device | 9 tch.nn.init | 10 tch.wrappers.tensor | 11 pyo3_tch | 12 tch.data | 13 tch.nn | 14 tch.nn.batch_norm | 15 tch.nn.conv | 16 tch.nn.conv_transpose | 17 tch.nn.func | 18 tch.nn.group_norm | 19 tch.nn.layer_norm | 20 tch.nn.linear | 21 tch.nn.rnn | 22 tch.nn.sequential | 23 tch.nn.sparse | 24 tch.tensor.display | 25 tch.tensor.iter | 26 tch.tensor.ops | 27 tch.tensor.safetensors | 28 tch.vision.alexnet | 29 tch.vision.image | 30 tch.vision.inception | 31 tch.vision.rust_image | 32 tch.vision.squeezenet | 33 tch.wrappers.optimizer | 34 tch.nn.optimizer | 35 tch.vision.convmixer | 36 tch.vision.dataset | 37 tch.vision.dinov2 | 38 tch.vision.efficientnet | 39 tch.vision.resnet | 40 tch.vision.vgg |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 tch.error | ||||||||||||||||||||||||||||||||||||||||
| 2 tch.wrappers.kind | ||||||||||||||||||||||||||||||||||||||||
| 3 tch.nn.module | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 4 tch.nn.var_store | 2 | 2 | 2 | 4 | ||||||||||||||||||||||||||||||||||||
| 5 tch.tensor.index | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 tch.tensor.npy | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 tch.wrappers.jit | 1 | 2 | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 8 tch.wrappers.device | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 tch.nn.init | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 10 tch.wrappers.tensor | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 11 pyo3_tch | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 tch.data | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 13 tch.nn | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 tch.nn.batch_norm | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 tch.nn.conv | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 tch.nn.conv_transpose | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 tch.nn.func | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 tch.nn.group_norm | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 tch.nn.layer_norm | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 tch.nn.linear | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 tch.nn.rnn | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 22 tch.nn.sequential | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 tch.nn.sparse | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 tch.tensor.display | 6 | |||||||||||||||||||||||||||||||||||||||
| 25 tch.tensor.iter | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 tch.tensor.ops | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 tch.tensor.safetensors | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 tch.vision.alexnet | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 tch.vision.image | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 tch.vision.inception | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 tch.vision.rust_image | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 tch.vision.squeezenet | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 tch.wrappers.optimizer | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 tch.nn.optimizer | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 tch.vision.convmixer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 tch.vision.dataset | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 tch.vision.dinov2 | 6 | 7 | 6 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 38 tch.vision.efficientnet | 5 | 6 | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 tch.vision.resnet | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 tch.vision.vgg | 1 | 1 |
3→8 tch.nn.module uses tch.wrappers.device part of a loop✕
- Connections
- 1 pair of types, where a type in tch.nn.module uses a type in tch.wrappers.device.
- The types involved
tch.nn.module.ModuleT→tch.wrappers.device.Device
- Direction
- tch.nn.module uses tch.wrappers.device, so a change to tch.wrappers.device can break tch.nn.module, while a change to tch.nn.module can't break tch.wrappers.device.
- 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.
3→10 tch.nn.module uses tch.wrappers.tensor part of a loop✕
- Connections
- 2 pairs of types, where a type in tch.nn.module uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.module.Module→tch.wrappers.tensor.Tensortch.nn.module.ModuleT→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.module uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.module, while a change to tch.nn.module can't break tch.wrappers.tensor.
- 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.
4→2 tch.nn.var_store uses tch.wrappers.kind✕
- Connections
- 2 pairs of types, where a type in tch.nn.var_store uses a type in tch.wrappers.kind.
- The types involved
tch.nn.var_store.Path→tch.wrappers.kind.Kindtch.nn.var_store.VarStore→tch.wrappers.kind.Kind
- Direction
- tch.nn.var_store uses tch.wrappers.kind, so a change to tch.wrappers.kind can break tch.nn.var_store, while a change to tch.nn.var_store can't break tch.wrappers.kind.
- Position
- Below the diagonal: tch.nn.var_store uses a module listed above it, which is the healthy direction.
4→8 tch.nn.var_store uses tch.wrappers.device part of a loop✕
- Connections
- 2 pairs of types, where a type in tch.nn.var_store uses a type in tch.wrappers.device.
- The types involved
tch.nn.var_store.Path→tch.wrappers.device.Devicetch.nn.var_store.VarStore→tch.wrappers.device.Device
- Direction
- tch.nn.var_store uses tch.wrappers.device, so a change to tch.wrappers.device can break tch.nn.var_store, while a change to tch.nn.var_store can't break tch.wrappers.device.
- 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.
4→9 tch.nn.var_store uses tch.nn.init part of a loop✕
- Connections
- 2 pairs of types, where a type in tch.nn.var_store uses a type in tch.nn.init.
- The types involved
tch.nn.var_store.Entry→tch.nn.init.Inittch.nn.var_store.Path→tch.nn.init.Init
- Direction
- tch.nn.var_store uses tch.nn.init, so a change to tch.nn.init can break tch.nn.var_store, while a change to tch.nn.var_store can't break tch.nn.init.
- 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.
4→10 tch.nn.var_store uses tch.wrappers.tensor part of a loop✕
- Connections
- 4 pairs of types, where a type in tch.nn.var_store uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.var_store.Entry→tch.wrappers.tensor.Tensortch.nn.var_store.Path→tch.wrappers.tensor.Tensortch.nn.var_store.Var→tch.wrappers.tensor.Tensortch.nn.var_store.VarStore→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.var_store uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.var_store, while a change to tch.nn.var_store can't break tch.wrappers.tensor.
- 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.
5→10 tch.tensor.index uses tch.wrappers.tensor part of a loop✕
- Connections
- 2 pairs of types, where a type in tch.tensor.index uses a type in tch.wrappers.tensor.
- The types involved
tch.tensor.index.IndexOp→tch.wrappers.tensor.Tensortch.tensor.index.TensorIndexer→tch.wrappers.tensor.Tensor
- Direction
- tch.tensor.index uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.tensor.index, while a change to tch.tensor.index can't break tch.wrappers.tensor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→2 tch.tensor.npy uses tch.wrappers.kind✕
- Connections
- 1 pair of types, where a type in tch.tensor.npy uses a type in tch.wrappers.kind.
- The types involved
tch.tensor.npy.Header→tch.wrappers.kind.Kind
- Direction
- tch.tensor.npy uses tch.wrappers.kind, so a change to tch.wrappers.kind can break tch.tensor.npy, while a change to tch.tensor.npy can't break tch.wrappers.kind.
- Position
- Below the diagonal: tch.tensor.npy uses a module listed above it, which is the healthy direction.
7→2 tch.wrappers.jit uses tch.wrappers.kind✕
- Connections
- 1 pair of types, where a type in tch.wrappers.jit uses a type in tch.wrappers.kind.
- The types involved
tch.wrappers.jit.CModule→tch.wrappers.kind.Kind
- Direction
- tch.wrappers.jit uses tch.wrappers.kind, so a change to tch.wrappers.kind can break tch.wrappers.jit, while a change to tch.wrappers.jit can't break tch.wrappers.kind.
- Position
- Below the diagonal: tch.wrappers.jit uses a module listed above it, which is the healthy direction.
7→3 tch.wrappers.jit uses tch.nn.module✕
- Connections
- 2 pairs of types, where a type in tch.wrappers.jit uses a type in tch.nn.module.
- The types involved
tch.wrappers.jit.CModule→tch.nn.module.Moduletch.wrappers.jit.TrainableCModule→tch.nn.module.ModuleT
- Direction
- tch.wrappers.jit uses tch.nn.module, so a change to tch.nn.module can break tch.wrappers.jit, while a change to tch.wrappers.jit can't break tch.nn.module.
- Position
- Below the diagonal: tch.wrappers.jit uses a module listed above it, which is the healthy direction.
7→4 tch.wrappers.jit uses tch.nn.var_store✕
- Connections
- 1 pair of types, where a type in tch.wrappers.jit uses a type in tch.nn.var_store.
- The types involved
tch.wrappers.jit.TrainableCModule→tch.nn.var_store.Path
- Direction
- tch.wrappers.jit uses tch.nn.var_store, so a change to tch.nn.var_store can break tch.wrappers.jit, while a change to tch.wrappers.jit can't break tch.nn.var_store.
- Position
- Below the diagonal: tch.wrappers.jit uses a module listed above it, which is the healthy direction.
7→8 tch.wrappers.jit uses tch.wrappers.device part of a loop✕
- Connections
- 2 pairs of types, where a type in tch.wrappers.jit uses a type in tch.wrappers.device.
- The types involved
tch.wrappers.jit.CModule→tch.wrappers.device.Devicetch.wrappers.jit.IValue→tch.wrappers.device.Device
- Direction
- tch.wrappers.jit uses tch.wrappers.device, so a change to tch.wrappers.device can break tch.wrappers.jit, while a change to tch.wrappers.jit can't break tch.wrappers.device.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→10 tch.wrappers.jit uses tch.wrappers.tensor part of a loop✕
- Connections
- 3 pairs of types, where a type in tch.wrappers.jit uses a type in tch.wrappers.tensor.
- The types involved
tch.wrappers.jit.CModule→tch.wrappers.tensor.Tensortch.wrappers.jit.IValue→tch.wrappers.tensor.Tensortch.wrappers.jit.TrainableCModule→tch.wrappers.tensor.Tensor
- Direction
- tch.wrappers.jit uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.wrappers.jit, while a change to tch.wrappers.jit can't break tch.wrappers.tensor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→7 tch.wrappers.device uses tch.wrappers.jit✕
- Connections
- 1 pair of types, where a type in tch.wrappers.device uses a type in tch.wrappers.jit.
- The types involved
tch.wrappers.device.Device→tch.wrappers.jit.IValue
- Direction
- tch.wrappers.device uses tch.wrappers.jit, so a change to tch.wrappers.jit can break tch.wrappers.device, while a change to tch.wrappers.device can't break tch.wrappers.jit.
- Position
- Below the diagonal: tch.wrappers.device uses a module listed above it, which is the healthy direction.
9→2 tch.nn.init uses tch.wrappers.kind✕
- Connections
- 1 pair of types, where a type in tch.nn.init uses a type in tch.wrappers.kind.
- The types involved
tch.nn.init.init$module→tch.wrappers.kind.Kind
- Direction
- tch.nn.init uses tch.wrappers.kind, so a change to tch.wrappers.kind can break tch.nn.init, while a change to tch.nn.init can't break tch.wrappers.kind.
- Position
- Below the diagonal: tch.nn.init uses a module listed above it, which is the healthy direction.
9→8 tch.nn.init uses tch.wrappers.device✕
- Connections
- 1 pair of types, where a type in tch.nn.init uses a type in tch.wrappers.device.
- The types involved
tch.nn.init.init$module→tch.wrappers.device.Device
- Direction
- tch.nn.init uses tch.wrappers.device, so a change to tch.wrappers.device can break tch.nn.init, while a change to tch.nn.init can't break tch.wrappers.device.
- Position
- Below the diagonal: tch.nn.init uses a module listed above it, which is the healthy direction.
9→10 tch.nn.init uses tch.wrappers.tensor part of a loop✕
- Connections
- 2 pairs of types, where a type in tch.nn.init uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.init.Init→tch.wrappers.tensor.Tensortch.nn.init.init$module→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.init uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.init, while a change to tch.nn.init can't break tch.wrappers.tensor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 tch.wrappers.tensor uses tch.wrappers.kind✕
- Connections
- 1 pair of types, where a type in tch.wrappers.tensor uses a type in tch.wrappers.kind.
- The types involved
tch.wrappers.tensor.Tensor→tch.wrappers.kind.Kind
- Direction
- tch.wrappers.tensor uses tch.wrappers.kind, so a change to tch.wrappers.kind can break tch.wrappers.tensor, while a change to tch.wrappers.tensor can't break tch.wrappers.kind.
- Position
- Below the diagonal: tch.wrappers.tensor uses a module listed above it, which is the healthy direction.
10→5 tch.wrappers.tensor uses tch.tensor.index✕
- Connections
- 1 pair of types, where a type in tch.wrappers.tensor uses a type in tch.tensor.index.
- The types involved
tch.wrappers.tensor.Tensor→tch.tensor.index.IndexOp
- Direction
- tch.wrappers.tensor uses tch.tensor.index, so a change to tch.tensor.index can break tch.wrappers.tensor, while a change to tch.wrappers.tensor can't break tch.tensor.index.
- Position
- Below the diagonal: tch.wrappers.tensor uses a module listed above it, which is the healthy direction.
10→7 tch.wrappers.tensor uses tch.wrappers.jit✕
- Connections
- 1 pair of types, where a type in tch.wrappers.tensor uses a type in tch.wrappers.jit.
- The types involved
tch.wrappers.tensor.Tensor→tch.wrappers.jit.IValue
- Direction
- tch.wrappers.tensor uses tch.wrappers.jit, so a change to tch.wrappers.jit can break tch.wrappers.tensor, while a change to tch.wrappers.tensor can't break tch.wrappers.jit.
- Position
- Below the diagonal: tch.wrappers.tensor uses a module listed above it, which is the healthy direction.
10→8 tch.wrappers.tensor uses tch.wrappers.device✕
- Connections
- 1 pair of types, where a type in tch.wrappers.tensor uses a type in tch.wrappers.device.
- The types involved
tch.wrappers.tensor.Tensor→tch.wrappers.device.Device
- Direction
- tch.wrappers.tensor uses tch.wrappers.device, so a change to tch.wrappers.device can break tch.wrappers.tensor, while a change to tch.wrappers.tensor can't break tch.wrappers.device.
- Position
- Below the diagonal: tch.wrappers.tensor uses a module listed above it, which is the healthy direction.
10→9 tch.wrappers.tensor uses tch.nn.init✕
- Connections
- 1 pair of types, where a type in tch.wrappers.tensor uses a type in tch.nn.init.
- The types involved
tch.wrappers.tensor.Tensor→tch.nn.init.Init
- Direction
- tch.wrappers.tensor uses tch.nn.init, so a change to tch.nn.init can break tch.wrappers.tensor, while a change to tch.wrappers.tensor can't break tch.nn.init.
- Position
- Below the diagonal: tch.wrappers.tensor uses a module listed above it, which is the healthy direction.
11→1 pyo3_tch uses tch.error✕
- Connections
- 1 pair of types, where a type in pyo3_tch uses a type in tch.error.
- The types involved
pyo3_tch.pyo3_tch$module→tch.error.TchError
- Direction
- pyo3_tch uses tch.error, so a change to tch.error can break pyo3_tch, while a change to pyo3_tch can't break tch.error.
- Position
- Below the diagonal: pyo3_tch uses a module listed above it, which is the healthy direction.
11→10 pyo3_tch uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in pyo3_tch uses a type in tch.wrappers.tensor.
- The types involved
pyo3_tch.PyTensor→tch.wrappers.tensor.Tensor
- Direction
- pyo3_tch uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break pyo3_tch, while a change to pyo3_tch can't break tch.wrappers.tensor.
- Position
- Below the diagonal: pyo3_tch uses a module listed above it, which is the healthy direction.
12→8 tch.data uses tch.wrappers.device✕
- Connections
- 1 pair of types, where a type in tch.data uses a type in tch.wrappers.device.
- The types involved
tch.data.Iter2→tch.wrappers.device.Device
- Direction
- tch.data uses tch.wrappers.device, so a change to tch.wrappers.device can break tch.data, while a change to tch.data can't break tch.wrappers.device.
- Position
- Below the diagonal: tch.data uses a module listed above it, which is the healthy direction.
12→10 tch.data uses tch.wrappers.tensor✕
- Connections
- 3 pairs of types, where a type in tch.data uses a type in tch.wrappers.tensor.
- The types involved
tch.data.Iter2→tch.wrappers.tensor.Tensortch.data.TextData→tch.wrappers.tensor.Tensortch.data.TextDataIter→tch.wrappers.tensor.Tensor
- Direction
- tch.data uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.data, while a change to tch.data can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.data uses a module listed above it, which is the healthy direction.
13→3 tch.nn uses tch.nn.module✕
- Connections
- 1 pair of types, where a type in tch.nn uses a type in tch.nn.module.
- The types involved
tch.nn.Id→tch.nn.module.ModuleT
- Direction
- tch.nn uses tch.nn.module, so a change to tch.nn.module can break tch.nn, while a change to tch.nn can't break tch.nn.module.
- Position
- Below the diagonal: tch.nn uses a module listed above it, which is the healthy direction.
13→10 tch.nn uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.nn uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.Id→tch.wrappers.tensor.Tensor
- Direction
- tch.nn uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn, while a change to tch.nn can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.nn uses a module listed above it, which is the healthy direction.
14→3 tch.nn.batch_norm uses tch.nn.module✕
- Connections
- 1 pair of types, where a type in tch.nn.batch_norm uses a type in tch.nn.module.
- The types involved
tch.nn.batch_norm.BatchNorm→tch.nn.module.ModuleT
- Direction
- tch.nn.batch_norm uses tch.nn.module, so a change to tch.nn.module can break tch.nn.batch_norm, while a change to tch.nn.batch_norm can't break tch.nn.module.
- Position
- Below the diagonal: tch.nn.batch_norm uses a module listed above it, which is the healthy direction.
14→9 tch.nn.batch_norm uses tch.nn.init✕
- Connections
- 1 pair of types, where a type in tch.nn.batch_norm uses a type in tch.nn.init.
- The types involved
tch.nn.batch_norm.BatchNormConfig→tch.nn.init.Init
- Direction
- tch.nn.batch_norm uses tch.nn.init, so a change to tch.nn.init can break tch.nn.batch_norm, while a change to tch.nn.batch_norm can't break tch.nn.init.
- Position
- Below the diagonal: tch.nn.batch_norm uses a module listed above it, which is the healthy direction.
14→10 tch.nn.batch_norm uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.nn.batch_norm uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.batch_norm.BatchNorm→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.batch_norm uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.batch_norm, while a change to tch.nn.batch_norm can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.nn.batch_norm uses a module listed above it, which is the healthy direction.
15→9 tch.nn.conv uses tch.nn.init✕
- Connections
- 1 pair of types, where a type in tch.nn.conv uses a type in tch.nn.init.
- The types involved
tch.nn.conv.ConvConfigND→tch.nn.init.Init
- Direction
- tch.nn.conv uses tch.nn.init, so a change to tch.nn.init can break tch.nn.conv, while a change to tch.nn.conv can't break tch.nn.init.
- Position
- Below the diagonal: tch.nn.conv uses a module listed above it, which is the healthy direction.
15→10 tch.nn.conv uses tch.wrappers.tensor✕
- Connections
- 2 pairs of types, where a type in tch.nn.conv uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.conv.Conv→tch.wrappers.tensor.Tensortch.nn.conv.PaddingMode→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.conv uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.conv, while a change to tch.nn.conv can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.nn.conv uses a module listed above it, which is the healthy direction.
16→9 tch.nn.conv_transpose uses tch.nn.init✕
- Connections
- 1 pair of types, where a type in tch.nn.conv_transpose uses a type in tch.nn.init.
- The types involved
tch.nn.conv_transpose.ConvTransposeConfigND→tch.nn.init.Init
- Direction
- tch.nn.conv_transpose uses tch.nn.init, so a change to tch.nn.init can break tch.nn.conv_transpose, while a change to tch.nn.conv_transpose can't break tch.nn.init.
- Position
- Below the diagonal: tch.nn.conv_transpose uses a module listed above it, which is the healthy direction.
16→10 tch.nn.conv_transpose uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.nn.conv_transpose uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.conv_transpose.ConvTransposeND→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.conv_transpose uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.conv_transpose, while a change to tch.nn.conv_transpose can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.nn.conv_transpose uses a module listed above it, which is the healthy direction.
17→3 tch.nn.func uses tch.nn.module✕
- Connections
- 2 pairs of types, where a type in tch.nn.func uses a type in tch.nn.module.
- The types involved
tch.nn.func.Func→tch.nn.module.Moduletch.nn.func.FuncT→tch.nn.module.ModuleT
- Direction
- tch.nn.func uses tch.nn.module, so a change to tch.nn.module can break tch.nn.func, while a change to tch.nn.func can't break tch.nn.module.
- Position
- Below the diagonal: tch.nn.func uses a module listed above it, which is the healthy direction.
17→10 tch.nn.func uses tch.wrappers.tensor✕
- Connections
- 2 pairs of types, where a type in tch.nn.func uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.func.Func→tch.wrappers.tensor.Tensortch.nn.func.FuncT→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.func uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.func, while a change to tch.nn.func can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.nn.func uses a module listed above it, which is the healthy direction.
18→3 tch.nn.group_norm uses tch.nn.module✕
- Connections
- 1 pair of types, where a type in tch.nn.group_norm uses a type in tch.nn.module.
- The types involved
tch.nn.group_norm.GroupNorm→tch.nn.module.Module
- Direction
- tch.nn.group_norm uses tch.nn.module, so a change to tch.nn.module can break tch.nn.group_norm, while a change to tch.nn.group_norm can't break tch.nn.module.
- Position
- Below the diagonal: tch.nn.group_norm uses a module listed above it, which is the healthy direction.
18→9 tch.nn.group_norm uses tch.nn.init✕
- Connections
- 1 pair of types, where a type in tch.nn.group_norm uses a type in tch.nn.init.
- The types involved
tch.nn.group_norm.GroupNormConfig→tch.nn.init.Init
- Direction
- tch.nn.group_norm uses tch.nn.init, so a change to tch.nn.init can break tch.nn.group_norm, while a change to tch.nn.group_norm can't break tch.nn.init.
- Position
- Below the diagonal: tch.nn.group_norm uses a module listed above it, which is the healthy direction.
18→10 tch.nn.group_norm uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.nn.group_norm uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.group_norm.GroupNorm→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.group_norm uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.group_norm, while a change to tch.nn.group_norm can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.nn.group_norm uses a module listed above it, which is the healthy direction.
19→3 tch.nn.layer_norm uses tch.nn.module✕
- Connections
- 1 pair of types, where a type in tch.nn.layer_norm uses a type in tch.nn.module.
- The types involved
tch.nn.layer_norm.LayerNorm→tch.nn.module.Module
- Direction
- tch.nn.layer_norm uses tch.nn.module, so a change to tch.nn.module can break tch.nn.layer_norm, while a change to tch.nn.layer_norm can't break tch.nn.module.
- Position
- Below the diagonal: tch.nn.layer_norm uses a module listed above it, which is the healthy direction.
19→9 tch.nn.layer_norm uses tch.nn.init✕
- Connections
- 1 pair of types, where a type in tch.nn.layer_norm uses a type in tch.nn.init.
- The types involved
tch.nn.layer_norm.LayerNormConfig→tch.nn.init.Init
- Direction
- tch.nn.layer_norm uses tch.nn.init, so a change to tch.nn.init can break tch.nn.layer_norm, while a change to tch.nn.layer_norm can't break tch.nn.init.
- Position
- Below the diagonal: tch.nn.layer_norm uses a module listed above it, which is the healthy direction.
19→10 tch.nn.layer_norm uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.nn.layer_norm uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.layer_norm.LayerNorm→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.layer_norm uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.layer_norm, while a change to tch.nn.layer_norm can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.nn.layer_norm uses a module listed above it, which is the healthy direction.
20→3 tch.nn.linear uses tch.nn.module✕
- Connections
- 1 pair of types, where a type in tch.nn.linear uses a type in tch.nn.module.
- The types involved
tch.nn.linear.Linear→tch.nn.module.Module
- Direction
- tch.nn.linear uses tch.nn.module, so a change to tch.nn.module can break tch.nn.linear, while a change to tch.nn.linear can't break tch.nn.module.
- Position
- Below the diagonal: tch.nn.linear uses a module listed above it, which is the healthy direction.
20→9 tch.nn.linear uses tch.nn.init✕
- Connections
- 1 pair of types, where a type in tch.nn.linear uses a type in tch.nn.init.
- The types involved
tch.nn.linear.LinearConfig→tch.nn.init.Init
- Direction
- tch.nn.linear uses tch.nn.init, so a change to tch.nn.init can break tch.nn.linear, while a change to tch.nn.linear can't break tch.nn.init.
- Position
- Below the diagonal: tch.nn.linear uses a module listed above it, which is the healthy direction.
20→10 tch.nn.linear uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.nn.linear uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.linear.Linear→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.linear uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.linear, while a change to tch.nn.linear can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.nn.linear uses a module listed above it, which is the healthy direction.
21→8 tch.nn.rnn uses tch.wrappers.device✕
- Connections
- 2 pairs of types, where a type in tch.nn.rnn uses a type in tch.wrappers.device.
- The types involved
tch.nn.rnn.GRU→tch.wrappers.device.Devicetch.nn.rnn.LSTM→tch.wrappers.device.Device
- Direction
- tch.nn.rnn uses tch.wrappers.device, so a change to tch.wrappers.device can break tch.nn.rnn, while a change to tch.nn.rnn can't break tch.wrappers.device.
- Position
- Below the diagonal: tch.nn.rnn uses a module listed above it, which is the healthy direction.
21→9 tch.nn.rnn uses tch.nn.init✕
- Connections
- 1 pair of types, where a type in tch.nn.rnn uses a type in tch.nn.init.
- The types involved
tch.nn.rnn.RNNConfig→tch.nn.init.Init
- Direction
- tch.nn.rnn uses tch.nn.init, so a change to tch.nn.init can break tch.nn.rnn, while a change to tch.nn.rnn can't break tch.nn.init.
- Position
- Below the diagonal: tch.nn.rnn uses a module listed above it, which is the healthy direction.
21→10 tch.nn.rnn uses tch.wrappers.tensor✕
- Connections
- 6 pairs of types, where a type in tch.nn.rnn uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.rnn.GRU→tch.wrappers.tensor.Tensortch.nn.rnn.GRUState→tch.wrappers.tensor.Tensortch.nn.rnn.LSTM→tch.wrappers.tensor.Tensortch.nn.rnn.LSTMState→tch.wrappers.tensor.Tensortch.nn.rnn.RNN→tch.wrappers.tensor.Tensortch.nn.rnn.rnn$module→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.rnn uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.rnn, while a change to tch.nn.rnn can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.nn.rnn uses a module listed above it, which is the healthy direction.
22→3 tch.nn.sequential uses tch.nn.module✕
- Connections
- 2 pairs of types, where a type in tch.nn.sequential uses a type in tch.nn.module.
- The types involved
tch.nn.sequential.Sequential→tch.nn.module.Moduletch.nn.sequential.SequentialT→tch.nn.module.ModuleT
- Direction
- tch.nn.sequential uses tch.nn.module, so a change to tch.nn.module can break tch.nn.sequential, while a change to tch.nn.sequential can't break tch.nn.module.
- Position
- Below the diagonal: tch.nn.sequential uses a module listed above it, which is the healthy direction.
22→10 tch.nn.sequential uses tch.wrappers.tensor✕
- Connections
- 2 pairs of types, where a type in tch.nn.sequential uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.sequential.Sequential→tch.wrappers.tensor.Tensortch.nn.sequential.SequentialT→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.sequential uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.sequential, while a change to tch.nn.sequential can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.nn.sequential uses a module listed above it, which is the healthy direction.
23→3 tch.nn.sparse uses tch.nn.module✕
- Connections
- 1 pair of types, where a type in tch.nn.sparse uses a type in tch.nn.module.
- The types involved
tch.nn.sparse.Embedding→tch.nn.module.Module
- Direction
- tch.nn.sparse uses tch.nn.module, so a change to tch.nn.module can break tch.nn.sparse, while a change to tch.nn.sparse can't break tch.nn.module.
- Position
- Below the diagonal: tch.nn.sparse uses a module listed above it, which is the healthy direction.
23→9 tch.nn.sparse uses tch.nn.init✕
- Connections
- 1 pair of types, where a type in tch.nn.sparse uses a type in tch.nn.init.
- The types involved
tch.nn.sparse.EmbeddingConfig→tch.nn.init.Init
- Direction
- tch.nn.sparse uses tch.nn.init, so a change to tch.nn.init can break tch.nn.sparse, while a change to tch.nn.sparse can't break tch.nn.init.
- Position
- Below the diagonal: tch.nn.sparse uses a module listed above it, which is the healthy direction.
23→10 tch.nn.sparse uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.nn.sparse uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.sparse.Embedding→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.sparse uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.sparse, while a change to tch.nn.sparse can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.nn.sparse uses a module listed above it, which is the healthy direction.
24→10 tch.tensor.display uses tch.wrappers.tensor✕
- Connections
- 6 pairs of types, where a type in tch.tensor.display uses a type in tch.wrappers.tensor.
- The types involved
tch.tensor.display.BasicKind→tch.wrappers.tensor.Tensortch.tensor.display.BoolFormatter→tch.wrappers.tensor.Tensortch.tensor.display.FloatFormatter→tch.wrappers.tensor.Tensortch.tensor.display.IntFormatter→tch.wrappers.tensor.Tensortch.tensor.display.TensorFormatter→tch.wrappers.tensor.Tensortch.tensor.display.display$module→tch.wrappers.tensor.Tensor
- Direction
- tch.tensor.display uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.tensor.display, while a change to tch.tensor.display can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.tensor.display uses a module listed above it, which is the healthy direction.
25→10 tch.tensor.iter uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.tensor.iter uses a type in tch.wrappers.tensor.
- The types involved
tch.tensor.iter.Iter→tch.wrappers.tensor.Tensor
- Direction
- tch.tensor.iter uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.tensor.iter, while a change to tch.tensor.iter can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.tensor.iter uses a module listed above it, which is the healthy direction.
26→10 tch.tensor.ops uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.tensor.ops uses a type in tch.wrappers.tensor.
- The types involved
tch.tensor.ops.ops$module→tch.wrappers.tensor.Tensor
- Direction
- tch.tensor.ops uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.tensor.ops, while a change to tch.tensor.ops can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.tensor.ops uses a module listed above it, which is the healthy direction.
27→1 tch.tensor.safetensors uses tch.error✕
- Connections
- 1 pair of types, where a type in tch.tensor.safetensors uses a type in tch.error.
- The types involved
tch.tensor.safetensors.safetensors$module→tch.error.TchError
- Direction
- tch.tensor.safetensors uses tch.error, so a change to tch.error can break tch.tensor.safetensors, while a change to tch.tensor.safetensors can't break tch.error.
- Position
- Below the diagonal: tch.tensor.safetensors uses a module listed above it, which is the healthy direction.
27→10 tch.tensor.safetensors uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.tensor.safetensors uses a type in tch.wrappers.tensor.
- The types involved
tch.tensor.safetensors.SafeView→tch.wrappers.tensor.Tensor
- Direction
- tch.tensor.safetensors uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.tensor.safetensors, while a change to tch.tensor.safetensors can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.tensor.safetensors uses a module listed above it, which is the healthy direction.
28→4 tch.vision.alexnet uses tch.nn.var_store✕
- Connections
- 1 pair of types, where a type in tch.vision.alexnet uses a type in tch.nn.var_store.
- The types involved
tch.vision.alexnet.alexnet$module→tch.nn.var_store.Path
- Direction
- tch.vision.alexnet uses tch.nn.var_store, so a change to tch.nn.var_store can break tch.vision.alexnet, while a change to tch.vision.alexnet can't break tch.nn.var_store.
- Position
- Below the diagonal: tch.vision.alexnet uses a module listed above it, which is the healthy direction.
28→10 tch.vision.alexnet uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.vision.alexnet uses a type in tch.wrappers.tensor.
- The types involved
tch.vision.alexnet.alexnet$module→tch.wrappers.tensor.Tensor
- Direction
- tch.vision.alexnet uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.vision.alexnet, while a change to tch.vision.alexnet can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.vision.alexnet uses a module listed above it, which is the healthy direction.
29→4 tch.vision.image uses tch.nn.var_store✕
- Connections
- 1 pair of types, where a type in tch.vision.image uses a type in tch.nn.var_store.
- The types involved
tch.vision.image.image$module→tch.nn.var_store.Path
- Direction
- tch.vision.image uses tch.nn.var_store, so a change to tch.nn.var_store can break tch.vision.image, while a change to tch.vision.image can't break tch.nn.var_store.
- Position
- Below the diagonal: tch.vision.image uses a module listed above it, which is the healthy direction.
29→10 tch.vision.image uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.vision.image uses a type in tch.wrappers.tensor.
- The types involved
tch.vision.image.image$module→tch.wrappers.tensor.Tensor
- Direction
- tch.vision.image uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.vision.image, while a change to tch.vision.image can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.vision.image uses a module listed above it, which is the healthy direction.
30→4 tch.vision.inception uses tch.nn.var_store✕
- Connections
- 1 pair of types, where a type in tch.vision.inception uses a type in tch.nn.var_store.
- The types involved
tch.vision.inception.inception$module→tch.nn.var_store.Path
- Direction
- tch.vision.inception uses tch.nn.var_store, so a change to tch.nn.var_store can break tch.vision.inception, while a change to tch.vision.inception can't break tch.nn.var_store.
- Position
- Below the diagonal: tch.vision.inception uses a module listed above it, which is the healthy direction.
30→10 tch.vision.inception uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.vision.inception uses a type in tch.wrappers.tensor.
- The types involved
tch.vision.inception.inception$module→tch.wrappers.tensor.Tensor
- Direction
- tch.vision.inception uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.vision.inception, while a change to tch.vision.inception can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.vision.inception uses a module listed above it, which is the healthy direction.
31→2 tch.vision.rust_image uses tch.wrappers.kind✕
- Connections
- 1 pair of types, where a type in tch.vision.rust_image uses a type in tch.wrappers.kind.
- The types involved
tch.vision.rust_image.rust_image$module→tch.wrappers.kind.Kind
- Direction
- tch.vision.rust_image uses tch.wrappers.kind, so a change to tch.wrappers.kind can break tch.vision.rust_image, while a change to tch.vision.rust_image can't break tch.wrappers.kind.
- Position
- Below the diagonal: tch.vision.rust_image uses a module listed above it, which is the healthy direction.
31→10 tch.vision.rust_image uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.vision.rust_image uses a type in tch.wrappers.tensor.
- The types involved
tch.vision.rust_image.rust_image$module→tch.wrappers.tensor.Tensor
- Direction
- tch.vision.rust_image uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.vision.rust_image, while a change to tch.vision.rust_image can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.vision.rust_image uses a module listed above it, which is the healthy direction.
32→4 tch.vision.squeezenet uses tch.nn.var_store✕
- Connections
- 1 pair of types, where a type in tch.vision.squeezenet uses a type in tch.nn.var_store.
- The types involved
tch.vision.squeezenet.squeezenet$module→tch.nn.var_store.Path
- Direction
- tch.vision.squeezenet uses tch.nn.var_store, so a change to tch.nn.var_store can break tch.vision.squeezenet, while a change to tch.vision.squeezenet can't break tch.nn.var_store.
- Position
- Below the diagonal: tch.vision.squeezenet uses a module listed above it, which is the healthy direction.
32→10 tch.vision.squeezenet uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.vision.squeezenet uses a type in tch.wrappers.tensor.
- The types involved
tch.vision.squeezenet.squeezenet$module→tch.wrappers.tensor.Tensor
- Direction
- tch.vision.squeezenet uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.vision.squeezenet, while a change to tch.vision.squeezenet can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.vision.squeezenet uses a module listed above it, which is the healthy direction.
33→10 tch.wrappers.optimizer uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.wrappers.optimizer uses a type in tch.wrappers.tensor.
- The types involved
tch.wrappers.optimizer.COptimizer→tch.wrappers.tensor.Tensor
- Direction
- tch.wrappers.optimizer uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.wrappers.optimizer, while a change to tch.wrappers.optimizer can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.wrappers.optimizer uses a module listed above it, which is the healthy direction.
34→4 tch.nn.optimizer uses tch.nn.var_store✕
- Connections
- 2 pairs of types, where a type in tch.nn.optimizer uses a type in tch.nn.var_store.
- The types involved
tch.nn.optimizer.Optimizer→tch.nn.var_store.Variablestch.nn.optimizer.OptimizerConfig→tch.nn.var_store.VarStore
- Direction
- tch.nn.optimizer uses tch.nn.var_store, so a change to tch.nn.var_store can break tch.nn.optimizer, while a change to tch.nn.optimizer can't break tch.nn.var_store.
- Position
- Below the diagonal: tch.nn.optimizer uses a module listed above it, which is the healthy direction.
34→10 tch.nn.optimizer uses tch.wrappers.tensor✕
- Connections
- 1 pair of types, where a type in tch.nn.optimizer uses a type in tch.wrappers.tensor.
- The types involved
tch.nn.optimizer.Optimizer→tch.wrappers.tensor.Tensor
- Direction
- tch.nn.optimizer uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.nn.optimizer, while a change to tch.nn.optimizer can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.nn.optimizer uses a module listed above it, which is the healthy direction.
34→33 tch.nn.optimizer uses tch.wrappers.optimizer✕
- Connections
- 1 pair of types, where a type in tch.nn.optimizer uses a type in tch.wrappers.optimizer.
- The types involved
tch.nn.optimizer.Optimizer→tch.wrappers.optimizer.COptimizer
- Direction
- tch.nn.optimizer uses tch.wrappers.optimizer, so a change to tch.wrappers.optimizer can break tch.nn.optimizer, while a change to tch.nn.optimizer can't break tch.wrappers.optimizer.
- Position
- Below the diagonal: tch.nn.optimizer uses a module listed above it, which is the healthy direction.
35→4 tch.vision.convmixer uses tch.nn.var_store✕
- Connections
- 1 pair of types, where a type in tch.vision.convmixer uses a type in tch.nn.var_store.
- The types involved
tch.vision.convmixer.convmixer$module→tch.nn.var_store.Path
- Direction
- tch.vision.convmixer uses tch.nn.var_store, so a change to tch.nn.var_store can break tch.vision.convmixer, while a change to tch.vision.convmixer can't break tch.nn.var_store.
- Position
- Below the diagonal: tch.vision.convmixer uses a module listed above it, which is the healthy direction.
35→17 tch.vision.convmixer uses tch.nn.func✕
- Connections
- 1 pair of types, where a type in tch.vision.convmixer uses a type in tch.nn.func.
- The types involved
tch.vision.convmixer.convmixer$module→tch.nn.func.FuncT
- Direction
- tch.vision.convmixer uses tch.nn.func, so a change to tch.nn.func can break tch.vision.convmixer, while a change to tch.vision.convmixer can't break tch.nn.func.
- Position
- Below the diagonal: tch.vision.convmixer uses a module listed above it, which is the healthy direction.
36→10 tch.vision.dataset uses tch.wrappers.tensor✕
- Connections
- 2 pairs of types, where a type in tch.vision.dataset uses a type in tch.wrappers.tensor.
- The types involved
tch.vision.dataset.Dataset→tch.wrappers.tensor.Tensortch.vision.dataset.dataset$module→tch.wrappers.tensor.Tensor
- Direction
- tch.vision.dataset uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.vision.dataset, while a change to tch.vision.dataset can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.vision.dataset uses a module listed above it, which is the healthy direction.
36→12 tch.vision.dataset uses tch.data✕
- Connections
- 1 pair of types, where a type in tch.vision.dataset uses a type in tch.data.
- The types involved
tch.vision.dataset.Dataset→tch.data.Iter2
- Direction
- tch.vision.dataset uses tch.data, so a change to tch.data can break tch.vision.dataset, while a change to tch.vision.dataset can't break tch.data.
- Position
- Below the diagonal: tch.vision.dataset uses a module listed above it, which is the healthy direction.
37→3 tch.vision.dinov2 uses tch.nn.module✕
- Connections
- 6 pairs of types, where a type in tch.vision.dinov2 uses a type in tch.nn.module.
- The types involved
tch.vision.dinov2.Attention→tch.nn.module.Moduletch.vision.dinov2.Block→tch.nn.module.Moduletch.vision.dinov2.DinoVisionTransformer→tch.nn.module.Moduletch.vision.dinov2.LayerScale→tch.nn.module.Moduletch.vision.dinov2.Mlp→tch.nn.module.Moduletch.vision.dinov2.PatchEmbed→tch.nn.module.Module
- Direction
- tch.vision.dinov2 uses tch.nn.module, so a change to tch.nn.module can break tch.vision.dinov2, while a change to tch.vision.dinov2 can't break tch.nn.module.
- Position
- Below the diagonal: tch.vision.dinov2 uses a module listed above it, which is the healthy direction.
37→4 tch.vision.dinov2 uses tch.nn.var_store✕
- Connections
- 7 pairs of types, where a type in tch.vision.dinov2 uses a type in tch.nn.var_store.
- The types involved
tch.vision.dinov2.Attention→tch.nn.var_store.Pathtch.vision.dinov2.Block→tch.nn.var_store.Pathtch.vision.dinov2.DinoVisionTransformer→tch.nn.var_store.Pathtch.vision.dinov2.LayerScale→tch.nn.var_store.Pathtch.vision.dinov2.Mlp→tch.nn.var_store.Pathtch.vision.dinov2.PatchEmbed→tch.nn.var_store.Pathtch.vision.dinov2.dinov2$module→tch.nn.var_store.Path
- Direction
- tch.vision.dinov2 uses tch.nn.var_store, so a change to tch.nn.var_store can break tch.vision.dinov2, while a change to tch.vision.dinov2 can't break tch.nn.var_store.
- Position
- Below the diagonal: tch.vision.dinov2 uses a module listed above it, which is the healthy direction.
37→10 tch.vision.dinov2 uses tch.wrappers.tensor✕
- Connections
- 6 pairs of types, where a type in tch.vision.dinov2 uses a type in tch.wrappers.tensor.
- The types involved
tch.vision.dinov2.Attention→tch.wrappers.tensor.Tensortch.vision.dinov2.Block→tch.wrappers.tensor.Tensortch.vision.dinov2.DinoVisionTransformer→tch.wrappers.tensor.Tensortch.vision.dinov2.LayerScale→tch.wrappers.tensor.Tensortch.vision.dinov2.Mlp→tch.wrappers.tensor.Tensortch.vision.dinov2.PatchEmbed→tch.wrappers.tensor.Tensor
- Direction
- tch.vision.dinov2 uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.vision.dinov2, while a change to tch.vision.dinov2 can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.vision.dinov2 uses a module listed above it, which is the healthy direction.
37→19 tch.vision.dinov2 uses tch.nn.layer_norm✕
- Connections
- 2 pairs of types, where a type in tch.vision.dinov2 uses a type in tch.nn.layer_norm.
- The types involved
tch.vision.dinov2.Block→tch.nn.layer_norm.LayerNormtch.vision.dinov2.DinoVisionTransformer→tch.nn.layer_norm.LayerNorm
- Direction
- tch.vision.dinov2 uses tch.nn.layer_norm, so a change to tch.nn.layer_norm can break tch.vision.dinov2, while a change to tch.vision.dinov2 can't break tch.nn.layer_norm.
- Position
- Below the diagonal: tch.vision.dinov2 uses a module listed above it, which is the healthy direction.
37→20 tch.vision.dinov2 uses tch.nn.linear✕
- Connections
- 3 pairs of types, where a type in tch.vision.dinov2 uses a type in tch.nn.linear.
- The types involved
tch.vision.dinov2.Attention→tch.nn.linear.Lineartch.vision.dinov2.DinoVisionTransformer→tch.nn.linear.Lineartch.vision.dinov2.Mlp→tch.nn.linear.Linear
- Direction
- tch.vision.dinov2 uses tch.nn.linear, so a change to tch.nn.linear can break tch.vision.dinov2, while a change to tch.vision.dinov2 can't break tch.nn.linear.
- Position
- Below the diagonal: tch.vision.dinov2 uses a module listed above it, which is the healthy direction.
38→3 tch.vision.efficientnet uses tch.nn.module✕
- Connections
- 5 pairs of types, where a type in tch.vision.efficientnet uses a type in tch.nn.module.
- The types involved
tch.vision.efficientnet.Conv2DSame→tch.nn.module.Moduletch.vision.efficientnet.ConvNormActivation→tch.nn.module.ModuleTtch.vision.efficientnet.EfficientNet→tch.nn.module.ModuleTtch.vision.efficientnet.MBConv→tch.nn.module.ModuleTtch.vision.efficientnet.SqueezeExcitation→tch.nn.module.ModuleT
- Direction
- tch.vision.efficientnet uses tch.nn.module, so a change to tch.nn.module can break tch.vision.efficientnet, while a change to tch.vision.efficientnet can't break tch.nn.module.
- Position
- Below the diagonal: tch.vision.efficientnet uses a module listed above it, which is the healthy direction.
38→4 tch.vision.efficientnet uses tch.nn.var_store✕
- Connections
- 6 pairs of types, where a type in tch.vision.efficientnet uses a type in tch.nn.var_store.
- The types involved
tch.vision.efficientnet.Conv2DSame→tch.nn.var_store.Pathtch.vision.efficientnet.ConvNormActivation→tch.nn.var_store.Pathtch.vision.efficientnet.EfficientNet→tch.nn.var_store.Pathtch.vision.efficientnet.MBConv→tch.nn.var_store.Pathtch.vision.efficientnet.SqueezeExcitation→tch.nn.var_store.Pathtch.vision.efficientnet.efficientnet$module→tch.nn.var_store.Path
- Direction
- tch.vision.efficientnet uses tch.nn.var_store, so a change to tch.nn.var_store can break tch.vision.efficientnet, while a change to tch.vision.efficientnet can't break tch.nn.var_store.
- Position
- Below the diagonal: tch.vision.efficientnet uses a module listed above it, which is the healthy direction.
38→10 tch.vision.efficientnet uses tch.wrappers.tensor✕
- Connections
- 5 pairs of types, where a type in tch.vision.efficientnet uses a type in tch.wrappers.tensor.
- The types involved
tch.vision.efficientnet.Conv2DSame→tch.wrappers.tensor.Tensortch.vision.efficientnet.ConvNormActivation→tch.wrappers.tensor.Tensortch.vision.efficientnet.EfficientNet→tch.wrappers.tensor.Tensortch.vision.efficientnet.MBConv→tch.wrappers.tensor.Tensortch.vision.efficientnet.SqueezeExcitation→tch.wrappers.tensor.Tensor
- Direction
- tch.vision.efficientnet uses tch.wrappers.tensor, so a change to tch.wrappers.tensor can break tch.vision.efficientnet, while a change to tch.vision.efficientnet can't break tch.wrappers.tensor.
- Position
- Below the diagonal: tch.vision.efficientnet uses a module listed above it, which is the healthy direction.
38→14 tch.vision.efficientnet uses tch.nn.batch_norm✕
- Connections
- 1 pair of types, where a type in tch.vision.efficientnet uses a type in tch.nn.batch_norm.
- The types involved
tch.vision.efficientnet.ConvNormActivation→tch.nn.batch_norm.BatchNorm
- Direction
- tch.vision.efficientnet uses tch.nn.batch_norm, so a change to tch.nn.batch_norm can break tch.vision.efficientnet, while a change to tch.vision.efficientnet can't break tch.nn.batch_norm.
- Position
- Below the diagonal: tch.vision.efficientnet uses a module listed above it, which is the healthy direction.
38→20 tch.vision.efficientnet uses tch.nn.linear✕
- Connections
- 1 pair of types, where a type in tch.vision.efficientnet uses a type in tch.nn.linear.
- The types involved
tch.vision.efficientnet.EfficientNet→tch.nn.linear.Linear
- Direction
- tch.vision.efficientnet uses tch.nn.linear, so a change to tch.nn.linear can break tch.vision.efficientnet, while a change to tch.vision.efficientnet can't break tch.nn.linear.
- Position
- Below the diagonal: tch.vision.efficientnet uses a module listed above it, which is the healthy direction.
39→4 tch.vision.resnet uses tch.nn.var_store✕
- Connections
- 1 pair of types, where a type in tch.vision.resnet uses a type in tch.nn.var_store.
- The types involved
tch.vision.resnet.resnet$module→tch.nn.var_store.Path
- Direction
- tch.vision.resnet uses tch.nn.var_store, so a change to tch.nn.var_store can break tch.vision.resnet, while a change to tch.vision.resnet can't break tch.nn.var_store.
- Position
- Below the diagonal: tch.vision.resnet uses a module listed above it, which is the healthy direction.
39→17 tch.vision.resnet uses tch.nn.func✕
- Connections
- 1 pair of types, where a type in tch.vision.resnet uses a type in tch.nn.func.
- The types involved
tch.vision.resnet.resnet$module→tch.nn.func.FuncT
- Direction
- tch.vision.resnet uses tch.nn.func, so a change to tch.nn.func can break tch.vision.resnet, while a change to tch.vision.resnet can't break tch.nn.func.
- Position
- Below the diagonal: tch.vision.resnet uses a module listed above it, which is the healthy direction.
40→4 tch.vision.vgg uses tch.nn.var_store✕
- Connections
- 1 pair of types, where a type in tch.vision.vgg uses a type in tch.nn.var_store.
- The types involved
tch.vision.vgg.vgg$module→tch.nn.var_store.Path
- Direction
- tch.vision.vgg uses tch.nn.var_store, so a change to tch.nn.var_store can break tch.vision.vgg, while a change to tch.vision.vgg can't break tch.nn.var_store.
- Position
- Below the diagonal: tch.vision.vgg uses a module listed above it, which is the healthy direction.
40→22 tch.vision.vgg uses tch.nn.sequential✕
- Connections
- 1 pair of types, where a type in tch.vision.vgg uses a type in tch.nn.sequential.
- The types involved
tch.vision.vgg.vgg$module→tch.nn.sequential.SequentialT
- Direction
- tch.vision.vgg uses tch.nn.sequential, so a change to tch.nn.sequential can break tch.vision.vgg, while a change to tch.vision.vgg can't break tch.nn.sequential.
- Position
- Below the diagonal: tch.vision.vgg uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 22 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 15 | High / Critical |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. 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; Enable Dependabot/Renovate or a dependency-review gate.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +7.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. | +6.6 pts | Medium | Architecture documentation |
| Enable Dependabot/Renovate or a dependency-review gate. | +4.8 pts | Medium | Security & performance tooling |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.9 pts | Medium | Documentation (README) |
| Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge. | +1.5 pts | Medium | CI/CD gates |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. | +0.5 pts | Low | Dependency Vulnerabilities |
| Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED (2). | +0.4 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.2 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/tensor/npy.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| src/wrappers/jit.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| examples/stable-diffusion/main.rs | 6.5 | Mixed | Explicit Debt: TodoComment |
| torch-sys/build.rs | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/wrappers/tensor.rs | 7.0 | Near-clean | God Classes: TooManyMethods: Tensor |
| src/nn/var_store.rs | 7.0 | Near-clean | Cognitive Complexity: VarStore::merge (cognitive 17) |
| src/tensor/convert.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| src/tensor/index.rs | 7.4 | Near-clean | Cyclomatic Complexity: Tensor::f_indexer (cyclomatic 22) |
| src/tensor/display.rs | 7.4 | Near-clean | Cyclomatic Complexity: TensorFormatter::fmt_tensor (cyclomatic 17) |
| src/vision/inception.rs | 7.4 | Near-clean | Code Duplication: Edited copy of a member (28 corresponding lines) |
| src/vision/resnet.rs | 7.4 | Near-clean | Code Duplication: Edited copy of a member (22 corresponding lines) |
| src/nn/rnn.rs | 7.4 | Near-clean | Code Duplication: Edited copy of a member (21 corresponding lines) |
| src/vision/efficientnet.rs | 7.8 | Near-clean | Code Duplication: Edited copy of a member (9 corresponding lines) |
| src/nn/sequential.rs | 7.8 | Near-clean | Code Duplication: Edited copy of a member (16 corresponding lines) |
| src/nn/batch_norm.rs | 7.8 | Near-clean | Code Duplication: Edited copy of a member (11 corresponding lines) |
| src/nn/conv.rs | 7.8 | Near-clean | Code Duplication: Edited copy of a member (13 corresponding lines) |
| src/vision/rust_image.rs | 7.8 | Near-clean | Code Duplication: Edited copies of one member (3 members, 6+ 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 34 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 — 34 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, 114 of 130 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
- 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 Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — 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. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 16 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — 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 repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- C4 Data Retention — 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 retention 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 retention controls.
- C5 Data-Subject Rights — 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 data-subject rights 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 data-subject rights 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 and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Rust, c, cpp, ocaml is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, Rust, c, cpp, ocaml 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.
- 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.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Cpp, Ocaml, Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Header::parse at 32. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Kind::from_c_int at 21 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/wrappers/kind.rs (Kind::from_c_int at 21), src/wrappers/jit.rs (IValue::from_c at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Header::parse (cyclomatic 32), Tensor::f_indexer (cyclomatic 22), TensorFormatter::fmt_tensor (cyclomatic 17). — 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 Cyclomatic Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
5 method(s) exceeded the cognitive complexity threshold of 15; the worst was TensorFormatter::fmt_tensor at 37.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with TensorFormatter::fmt_tensor (cognitive 37), Header::parse (cognitive 28), Tensor::f_indexer (cognitive 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with tensor.rs, var_store.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with jit.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with tensor.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
14 duplicated block group(s) detected. 7.4 % of the production lines (807 of 10,935) are in a reported copy. A further 32 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with efficientnet.rs, rust_image.rs, jit.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with efficientnet.rs, var_store.rs, group_norm.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with inception.rs, jit.rs, sequential.rs. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
5 production modules (Cargo+Python+CMake), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 3 of the 5 (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)
0 of 27 classes have LCOM4 above 3.
D12 · Dependency Hygiene
8 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 193 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT/Apache-2.0, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/tensor/npy.rs. Counted over 39 of the 64 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
17 deducted task-comment markers across 10935 LoC (0.1/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 16 TodoComment finding(s) in Explicit Debt — start with main.rs (7), build.rs (4), convert.rs (2). — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with npy.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 3 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
22 finding(s): 0 critical, 12 high, 10 medium, 0 low. 12 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `torch-sys/libtch/stb_image.h`, `torch-sys/libtch/stb_image_resize.h` (line 225, line 229, line 250, …), `torch-sys/libtch/stb_image_write.h` (line 180, line 181, line 182, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 12 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 (12 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
15 finding(s): 0 critical, 2 high, 13 medium, 0 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
1 of 39 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is torch-sys/src/io.rs. Counted over 39 of the 64 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
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
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
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: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. 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
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
X21 · Side-effecting pattern guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 90% | Exemplary | Solid. |
| Architecture | 94% | Exemplary | Strongest area. |
| Maturity | 63% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 54% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 86% | Checked 4 of 10 | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 5 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.
- C4 Data Retention — Not assessed: these retention 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 retention 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.
- C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 76 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; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — 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. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — 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.
- D10 Test Quality — ~8640 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (2409 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 — Rust suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 2 claim(s) of kinds M4 does not check were not checked (environment variable 2); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 3% of this repository's production lines — rust (10,486 lines), cpp (1,189 lines), ocaml (856 lines), c (265 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 14 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 100 finding(s)
- TodoComment torch-sys/build.rs:392
- TodoComment torch-sys/build.rs:412
- TodoComment torch-sys/build.rs:440
- TodoComment torch-sys/build.rs:475
- TodoComment src/wrappers/jit.rs:29
- TodoComment src/vision/dinov2.rs:5
- TodoComment src/tensor/convert.rs:31
- TodoComment src/tensor/convert.rs:47
- TodoComment examples/stable-diffusion/main.rs:39
- TodoComment examples/stable-diffusion/main.rs:40
- TodoComment examples/stable-diffusion/main.rs:2313
- TodoComment examples/stable-diffusion/main.rs:2402
- TodoComment examples/stable-diffusion/main.rs:2453
- TodoComment examples/llama/main.rs:179
- TodoComment examples/llama/sentencepiece.rs:7
- TodoComment examples/gan/main.rs:4
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) src/vision/efficientnet.rs:102
- Duplicated block (5 lines × 2) src/vision/rust_image.rs:94
- Duplicated block (5 lines × 2) src/wrappers/jit.rs:585
- Duplicated block (5 lines × 2) src/nn/conv.rs:121
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (9 corresponding lines) src/vision/efficientnet.rs:99
- Edited copy of a member (9 corresponding lines) src/nn/var_store.rs:443
- Edited copy of a member (9 corresponding lines) src/nn/group_norm.rs:17
- Edited copy of a member (8 corresponding lines) src/vision/inception.rs:4
- Edited copy of a member (8 corresponding lines) src/wrappers/jit.rs:647
- Edited copy of a member (8 corresponding lines) src/nn/sequential.rs:29
- Edited copy of a member (13 corresponding lines) src/wrappers/tensor.rs:702
- Edited copy of a member (13 corresponding lines) src/nn/conv.rs:145
- Edited copy of a member (13 corresponding lines) torch-sys/src/io.rs:20
- Edited copy of a member (6 corresponding lines) src/wrappers/jit.rs:481
- Edited copy of a member (6 corresponding lines) src/nn/rnn.rs:173
- Edited copy of a member (6 corresponding lines) src/wrappers/tensor.rs:131
- Duplicated block (7 lines × 2) src/tensor/npy.rs:171
- Duplicated block (7 lines × 2) src/wrappers/tensor.rs:703
- Duplicated block (7 lines × 2) src/wrappers/tensor.rs:587
- TooManyMethods: Tensor src/wrappers/tensor.rs:18
- TooManyMethods: Path src/nn/var_store.rs:41
- Edited copy of a member (16 corresponding lines) src/vision/inception.rs:27
- Edited copy of a member (16 corresponding lines) src/nn/sequential.rs:56
- Edited copy of a member (11 corresponding lines) src/vision/resnet.rs:24
- Edited copy of a member (11 corresponding lines) src/nn/batch_norm.rs:45
- Edited copy of a member (4 corresponding lines) src/nn/optimizer.rs:310
- Edited copy of a member (4 corresponding lines) src/vision/cifar.rs:37
- Header::parse (cyclomatic 32) src/tensor/npy.rs:68
- Tensor::f_indexer (cyclomatic 22) src/tensor/index.rs:293
- TensorFormatter::fmt_tensor (cyclomatic 17) src/tensor/display.rs:165
- HackComment src/tensor/npy.rs:66
- TensorFormatter::fmt_tensor (cognitive 37) src/tensor/display.rs:165
- Header::parse (cognitive 28) src/tensor/npy.rs:68
- Tensor::f_indexer (cognitive 20) src/tensor/index.rs:293
- tch::nn::init::f_init (cognitive 19) src/nn/init.rs:104
- VarStore::merge (cognitive 17) src/nn/var_store.rs:64
- REDACTED
- REDACTED
- FileTooLong: wrappers/jit.rs src/wrappers/jit.rs
- ClassTooLong: Tensor src/wrappers/tensor.rs:18
- REDACTED
- REDACTED
- Edited copy of a member (28 corresponding lines) src/vision/inception.rs:57
- Edited copy of a member (22 corresponding lines) src/vision/resnet.rs:51
- Edited copy of a member (17 corresponding lines) src/wrappers/tensor.rs:585
- Edited copy of a member (21 corresponding lines) src/nn/rnn.rs:148
- Edited copy of a member (19 corresponding lines) src/nn/var_store.rs:204
- Edited copy of a member (14 corresponding lines) src/nn/var_store.rs:499
- Edited copies of one member (4 members, 9+ corresponding lines) src/wrappers/jit.rs:490
- Edited copies of one member (3 members, 8+ corresponding lines) src/tensor/index.rs:232
- Edited copy of a member (7 corresponding lines) src/wrappers/jit.rs:455
- Edited copies of one member (4 members, 10+ corresponding lines) src/wrappers/tensor.rs:631
- Edited copies of one member (3 members, 6+ corresponding lines) src/vision/rust_image.rs:65
- Edited copy of a member (10 corresponding lines) src/nn/group_norm.rs:56
- Edited copies of one member (3 members, 4+ corresponding lines) src/vision/alexnet.rs:5
- Edited copies of one member (3 members, 3+ corresponding lines) src/tensor/mod.rs:211
- Duplicated block (18 lines × 2) src/nn/rnn.rs:149
- Duplicated block (14 lines × 2) src/vision/resnet.rs:59
- Duplicated block (10 lines × 2) src/nn/var_store.rs:206
- Duplicated block (7 lines × 3) src/nn/var_store.rs:207
- Duplicated block (6–7 lines × 2) src/tensor/display.rs:214
- Duplicated block (8 lines × 2) src/nn/batch_norm.rs:46
- Duplicated block (6 lines × 2) src/wrappers/jit.rs:649
- No structured logging
Minor — 8 finding(s)
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- Orphaned file torch-sys/src/io.rs:1
- REDACTED
- No ADRs
- CI build step not evidenced
Minor — 8 finding(s)
- Outdated: anyhow
- Outdated: cc
- Outdated: clap
- Outdated: half
- Outdated: lazy_static
- Outdated: regex
- Outdated: serde_json
- Outdated: zip
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-dba85065435f42f9b0ec7f7a6cb192ee/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-dba85065435f42f9b0ec7f7a6cb192ee/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 . | 22 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 15 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |