Executive summary
cross-rs/cross falls short of our standard for a preview release, in part because it has unsafe settings in infrastructure or container files. It scores 54 out of 100 and is rated Adequate, and 115 of its 116 critical findings are security problems.
Security and Compliance, at 40, is the weakest lens and counts most in the score. The best first steps are recording design decisions and adding tests for untested code, each worth about 5 points. Raising Security and Compliance to 68 would lift the score to about 63.
Forty-six settings leave the servers or containers unsafe. Thirty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and twenty-eight pipeline steps run downloads nobody checks. Correcting the unsafe settings, pinning each tool to an exact version and checking each download against a checksum would close these risks. Passing outside input through environment variables would fix the three pipeline steps that put outside input straight into a shell command, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The part of the code nobody has worked on for a long time needs someone to learn and document it before anyone changes it.
The product code is 15,346 lines, about €16,000 to rebuild.
If Security and Compliance rose from 40 to 68, the lowest score rated Strong, the score would rise from 54 to about 63.
New since the last survey: 34 findings
- Code Duplication · Edited copies of one member (3 members, 50+ corresponding lines) src/cross_toml.rs
- Code Duplication · Edited copy of a member (19 corresponding lines) xtask/src/hooks.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) src/bin/commands/containers.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) xtask/src/hooks.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/temp.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) xtask/src/ci/target_matrix.rs
- Code Duplication · Edited copy of a member (8 corresponding lines) src/bin/cross-util.rs
- Code Duplication · Duplicated block (27 lines × 2) src/cross_toml.rs
- Code Coverage · Low coverage: src/cargo.rs src/cargo.rs
- Code Coverage · Low coverage: src/cli.rs src/cli.rs
- Code Coverage · Low coverage: src/docker/custom.rs src/docker/custom.rs
- Code Coverage · Low coverage: src/docker/local.rs src/docker/local.rs
- Code Coverage · Low coverage: src/docker/mod.rs src/docker/mod.rs
- Code Coverage · Low coverage: src/docker/remote.rs src/docker/remote.rs
- Code Coverage · Low coverage: src/docker/shared.rs src/docker/shared.rs
- Code Coverage · Low coverage: src/errors.rs src/errors.rs
- Code Coverage · Low coverage: src/extensions.rs src/extensions.rs
- Code Coverage · Low coverage: src/id.rs src/id.rs
- Code Coverage · Low coverage: src/interpreter.rs src/interpreter.rs
- Code Coverage · Low coverage: src/lib.rs src/lib.rs
- Code Coverage · Low coverage: src/rustup.rs src/rustup.rs
- Code Coverage · Low coverage: src/shell.rs src/shell.rs
- Code Coverage · Low coverage: src/temp.rs src/temp.rs
- Code Coverage · Low coverage: xtask/src/build_docker_image.rs xtask/src/build_docker_image.rs
- Code Coverage · Low coverage: xtask/src/ci.rs xtask/src/ci.rs
- Code Coverage · Low coverage: xtask/src/ci/target_matrix.rs xtask/src/ci/target_matrix.rs
- Code Coverage · Low coverage: xtask/src/crosstool.rs xtask/src/crosstool.rs
- Code Coverage · Low coverage: xtask/src/hooks.rs xtask/src/hooks.rs
- Code Coverage · Low coverage: xtask/src/install_git_hooks.rs xtask/src/install_git_hooks.rs
- Code Coverage · Low coverage: xtask/src/main.rs xtask/src/main.rs
- Code Coverage · Low coverage: xtask/src/target_info.rs xtask/src/target_info.rs
- Code Coverage · Low coverage: xtask/src/util.rs xtask/src/util.rs
- Dependency Vulnerabilities · REDACTED
- Knowledge Freshness · Orphaned knowledge src/config.rs
Fixed since the last survey: 1 finding
- Code Duplication · Duplicated block (27 lines × 2) src/cross_toml.rs
Rebuild cost: about €16,000 · Estimate
| Cost to rebuild | €5,300 to €27,000, for 88 to 279 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 15,346 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 cross.bin.cross | 2 cross.errors | 3 cross.file | 4 cross.id | 5 cross.shell | 6 cross.temp | 7 docker.android.android | 8 docker.android.android.make | 9 cross.cli | 10 cross.docker.image | 11 cross.extensions | 12 xtask | 13 xtask.changelog | 14 xtask.crosstool | 15 xtask.install_git_hooks | 16 cross.cargo | 17 cross.docker.engine | 18 cross.bin.commands.clean | 19 cross.docker.docker_ignore | 20 xtask.ci | 21 xtask.hooks | 22 xtask.util | 23 cross.docker.shared | 24 xtask.build_docker_image | 25 xtask.ci.target_matrix | 26 xtask.target_info | 27 cross.docker | 28 cross.docker.custom | 29 cross.docker.local | 30 cross.docker.remote | 31 cross.cross_toml | 32 cross.config | 33 cross.rustc | 34 cross.bin.commands.containers | 35 cross.bin.commands.images | 36 cross.bin.cross-util | 37 cross | 38 cross.bin.commands.run | 39 cross.interpreter | 40 cross.rustup |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cross.bin.cross | ||||||||||||||||||||||||||||||||||||||||
| 2 cross.errors | ||||||||||||||||||||||||||||||||||||||||
| 3 cross.file | ||||||||||||||||||||||||||||||||||||||||
| 4 cross.id | ||||||||||||||||||||||||||||||||||||||||
| 5 cross.shell | ||||||||||||||||||||||||||||||||||||||||
| 6 cross.temp | ||||||||||||||||||||||||||||||||||||||||
| 7 docker.android.android | ||||||||||||||||||||||||||||||||||||||||
| 8 docker.android.android.make | ||||||||||||||||||||||||||||||||||||||||
| 9 cross.cli | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 10 cross.docker.image | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 11 cross.extensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 xtask | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 xtask.changelog | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 xtask.crosstool | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 xtask.install_git_hooks | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 cross.cargo | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 cross.docker.engine | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 cross.bin.commands.clean | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 cross.docker.docker_ignore | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 xtask.ci | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 xtask.hooks | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 xtask.util | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 cross.docker.shared | 11 | 1 | 4 | 10 | 1 | 2 | 4 | 1 | 6 | |||||||||||||||||||||||||||||||
| 24 xtask.build_docker_image | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 25 xtask.ci.target_matrix | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 xtask.target_info | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 27 cross.docker | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 28 cross.docker.custom | 1 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 29 cross.docker.local | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 cross.docker.remote | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 31 cross.cross_toml | 1 | 3 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 32 cross.config | 1 | 1 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 33 cross.rustc | 2 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 34 cross.bin.commands.containers | 10 | 10 | 4 | |||||||||||||||||||||||||||||||||||||
| 35 cross.bin.commands.images | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 cross.bin.cross-util | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 cross | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||
| 38 cross.bin.commands.run | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 cross.interpreter | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 cross.rustup | 1 | 1 | 1 | 2 |
9→5 cross.cli uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.cli uses a type in cross.shell.
- The types involved
cross.cli.cli$module→cross.shell.MessageInfo
- Direction
- cross.cli uses cross.shell, so a change to cross.shell can break cross.cli, while a change to cross.cli can't break cross.shell.
- Position
- Below the diagonal: cross.cli uses a module listed above it, which is the healthy direction.
9→16 cross.cli uses cross.cargo part of a loop✕
- Connections
- 1 pair of types, where a type in cross.cli uses a type in cross.cargo.
- The types involved
cross.cli.Args→cross.cargo.Subcommand
- Direction
- cross.cli uses cross.cargo, so a change to cross.cargo can break cross.cli, while a change to cross.cli can't break cross.cargo.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→33 cross.cli uses cross.rustc part of a loop✕
- Connections
- 1 pair of types, where a type in cross.cli uses a type in cross.rustc.
- The types involved
cross.cli.cli$module→cross.rustc.TargetList
- Direction
- cross.cli uses cross.rustc, so a change to cross.rustc can break cross.cli, while a change to cross.cli can't break cross.rustc.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→37 cross.cli uses cross part of a loop✕
- Connections
- 1 pair of types, where a type in cross.cli uses a type in cross.
- The types involved
cross.cli.Args→cross.Target
- Direction
- cross.cli uses cross, so a change to cross can break cross.cli, while a change to cross.cli can't break cross.
- 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→5 cross.docker.image uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.docker.image uses a type in cross.shell.
- The types involved
cross.docker.image.PossibleImage→cross.shell.MessageInfo
- Direction
- cross.docker.image uses cross.shell, so a change to cross.shell can break cross.docker.image, while a change to cross.docker.image can't break cross.shell.
- Position
- Below the diagonal: cross.docker.image uses a module listed above it, which is the healthy direction.
10→17 cross.docker.image uses cross.docker.engine part of a loop✕
- Connections
- 2 pairs of types, where a type in cross.docker.image uses a type in cross.docker.engine.
- The types involved
cross.docker.image.ImagePlatform→cross.docker.engine.Enginecross.docker.image.PossibleImage→cross.docker.engine.Engine
- Direction
- cross.docker.image uses cross.docker.engine, so a change to cross.docker.engine can break cross.docker.image, while a change to cross.docker.image can't break cross.docker.engine.
- 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→37 cross.docker.image uses cross part of a loop✕
- Connections
- 3 pairs of types, where a type in cross.docker.image uses a type in cross.
- The types involved
cross.docker.image.Architecture→cross.TargetTriplecross.docker.image.ImagePlatform→cross.TargetTriplecross.docker.image.Os→cross.TargetTriple
- Direction
- cross.docker.image uses cross, so a change to cross can break cross.docker.image, while a change to cross.docker.image can't break cross.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→5 cross.extensions uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.extensions uses a type in cross.shell.
- The types involved
cross.extensions.CommandExt→cross.shell.MessageInfo
- Direction
- cross.extensions uses cross.shell, so a change to cross.shell can break cross.extensions, while a change to cross.extensions can't break cross.shell.
- Position
- Below the diagonal: cross.extensions uses a module listed above it, which is the healthy direction.
12→5 xtask uses cross.shell✕
- Connections
- 1 pair of types, where a type in xtask uses a type in cross.shell.
- The types involved
xtask.xtask$module→cross.shell.MessageInfo
- Direction
- xtask uses cross.shell, so a change to cross.shell can break xtask, while a change to xtask can't break cross.shell.
- Position
- Below the diagonal: xtask uses a module listed above it, which is the healthy direction.
13→5 xtask.changelog uses cross.shell✕
- Connections
- 1 pair of types, where a type in xtask.changelog uses a type in cross.shell.
- The types involved
xtask.changelog.changelog$module→cross.shell.MessageInfo
- Direction
- xtask.changelog uses cross.shell, so a change to cross.shell can break xtask.changelog, while a change to xtask.changelog can't break cross.shell.
- Position
- Below the diagonal: xtask.changelog uses a module listed above it, which is the healthy direction.
14→5 xtask.crosstool uses cross.shell✕
- Connections
- 1 pair of types, where a type in xtask.crosstool uses a type in cross.shell.
- The types involved
xtask.crosstool.crosstool$module→cross.shell.MessageInfo
- Direction
- xtask.crosstool uses cross.shell, so a change to cross.shell can break xtask.crosstool, while a change to xtask.crosstool can't break cross.shell.
- Position
- Below the diagonal: xtask.crosstool uses a module listed above it, which is the healthy direction.
15→5 xtask.install_git_hooks uses cross.shell✕
- Connections
- 1 pair of types, where a type in xtask.install_git_hooks uses a type in cross.shell.
- The types involved
xtask.install_git_hooks.install_git_hooks$module→cross.shell.MessageInfo
- Direction
- xtask.install_git_hooks uses cross.shell, so a change to cross.shell can break xtask.install_git_hooks, while a change to xtask.install_git_hooks can't break cross.shell.
- Position
- Below the diagonal: xtask.install_git_hooks uses a module listed above it, which is the healthy direction.
16→5 cross.cargo uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.cargo uses a type in cross.shell.
- The types involved
cross.cargo.cargo$module→cross.shell.MessageInfo
- Direction
- cross.cargo uses cross.shell, so a change to cross.shell can break cross.cargo, while a change to cross.cargo can't break cross.shell.
- Position
- Below the diagonal: cross.cargo uses a module listed above it, which is the healthy direction.
16→9 cross.cargo uses cross.cli✕
- Connections
- 1 pair of types, where a type in cross.cargo uses a type in cross.cli.
- The types involved
cross.cargo.cargo$module→cross.cli.Args
- Direction
- cross.cargo uses cross.cli, so a change to cross.cli can break cross.cargo, while a change to cross.cargo can't break cross.cli.
- Position
- Below the diagonal: cross.cargo uses a module listed above it, which is the healthy direction.
17→5 cross.docker.engine uses cross.shell✕
- Connections
- 2 pairs of types, where a type in cross.docker.engine uses a type in cross.shell.
- The types involved
cross.docker.engine.Engine→cross.shell.MessageInfocross.docker.engine.engine$module→cross.shell.MessageInfo
- Direction
- cross.docker.engine uses cross.shell, so a change to cross.shell can break cross.docker.engine, while a change to cross.docker.engine can't break cross.shell.
- Position
- Below the diagonal: cross.docker.engine uses a module listed above it, which is the healthy direction.
17→10 cross.docker.engine uses cross.docker.image✕
- Connections
- 1 pair of types, where a type in cross.docker.engine uses a type in cross.docker.image.
- The types involved
cross.docker.engine.Engine→cross.docker.image.Architecture
- Direction
- cross.docker.engine uses cross.docker.image, so a change to cross.docker.image can break cross.docker.engine, while a change to cross.docker.engine can't break cross.docker.image.
- Position
- Below the diagonal: cross.docker.engine uses a module listed above it, which is the healthy direction.
17→37 cross.docker.engine uses cross part of a loop✕
- Connections
- 1 pair of types, where a type in cross.docker.engine uses a type in cross.
- The types involved
cross.docker.engine.Engine→cross.Target
- Direction
- cross.docker.engine uses cross, so a change to cross can break cross.docker.engine, while a change to cross.docker.engine can't break cross.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→5 cross.bin.commands.clean uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.bin.commands.clean uses a type in cross.shell.
- The types involved
cross.bin.commands.clean.Clean→cross.shell.MessageInfo
- Direction
- cross.bin.commands.clean uses cross.shell, so a change to cross.shell can break cross.bin.commands.clean, while a change to cross.bin.commands.clean can't break cross.shell.
- Position
- Below the diagonal: cross.bin.commands.clean uses a module listed above it, which is the healthy direction.
18→17 cross.bin.commands.clean uses cross.docker.engine✕
- Connections
- 1 pair of types, where a type in cross.bin.commands.clean uses a type in cross.docker.engine.
- The types involved
cross.bin.commands.clean.Clean→cross.docker.engine.Engine
- Direction
- cross.bin.commands.clean uses cross.docker.engine, so a change to cross.docker.engine can break cross.bin.commands.clean, while a change to cross.bin.commands.clean can't break cross.docker.engine.
- Position
- Below the diagonal: cross.bin.commands.clean uses a module listed above it, which is the healthy direction.
19→5 cross.docker.docker_ignore uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.docker.docker_ignore uses a type in cross.shell.
- The types involved
cross.docker.docker_ignore.DockerIgnore→cross.shell.MessageInfo
- Direction
- cross.docker.docker_ignore uses cross.shell, so a change to cross.shell can break cross.docker.docker_ignore, while a change to cross.docker.docker_ignore can't break cross.shell.
- Position
- Below the diagonal: cross.docker.docker_ignore uses a module listed above it, which is the healthy direction.
19→17 cross.docker.docker_ignore uses cross.docker.engine✕
- Connections
- 1 pair of types, where a type in cross.docker.docker_ignore uses a type in cross.docker.engine.
- The types involved
cross.docker.docker_ignore.DockerIgnore→cross.docker.engine.EngineType
- Direction
- cross.docker.docker_ignore uses cross.docker.engine, so a change to cross.docker.engine can break cross.docker.docker_ignore, while a change to cross.docker.docker_ignore can't break cross.docker.engine.
- Position
- Below the diagonal: cross.docker.docker_ignore uses a module listed above it, which is the healthy direction.
20→16 xtask.ci uses cross.cargo✕
- Connections
- 1 pair of types, where a type in xtask.ci uses a type in cross.cargo.
- The types involved
xtask.ci.ci$module→cross.cargo.CargoMetadata
- Direction
- xtask.ci uses cross.cargo, so a change to cross.cargo can break xtask.ci, while a change to xtask.ci can't break cross.cargo.
- Position
- Below the diagonal: xtask.ci uses a module listed above it, which is the healthy direction.
21→5 xtask.hooks uses cross.shell✕
- Connections
- 1 pair of types, where a type in xtask.hooks uses a type in cross.shell.
- The types involved
xtask.hooks.hooks$module→cross.shell.MessageInfo
- Direction
- xtask.hooks uses cross.shell, so a change to cross.shell can break xtask.hooks, while a change to xtask.hooks can't break cross.shell.
- Position
- Below the diagonal: xtask.hooks uses a module listed above it, which is the healthy direction.
21→16 xtask.hooks uses cross.cargo✕
- Connections
- 1 pair of types, where a type in xtask.hooks uses a type in cross.cargo.
- The types involved
xtask.hooks.hooks$module→cross.cargo.CargoMetadata
- Direction
- xtask.hooks uses cross.cargo, so a change to cross.cargo can break xtask.hooks, while a change to xtask.hooks can't break cross.cargo.
- Position
- Below the diagonal: xtask.hooks uses a module listed above it, which is the healthy direction.
22→5 xtask.util uses cross.shell✕
- Connections
- 1 pair of types, where a type in xtask.util uses a type in cross.shell.
- The types involved
xtask.util.util$module→cross.shell.MessageInfo
- Direction
- xtask.util uses cross.shell, so a change to cross.shell can break xtask.util, while a change to xtask.util can't break cross.shell.
- Position
- Below the diagonal: xtask.util uses a module listed above it, which is the healthy direction.
22→17 xtask.util uses cross.docker.engine✕
- Connections
- 1 pair of types, where a type in xtask.util uses a type in cross.docker.engine.
- The types involved
xtask.util.util$module→cross.docker.engine.Engine
- Direction
- xtask.util uses cross.docker.engine, so a change to cross.docker.engine can break xtask.util, while a change to xtask.util can't break cross.docker.engine.
- Position
- Below the diagonal: xtask.util uses a module listed above it, which is the healthy direction.
23→5 cross.docker.shared uses cross.shell✕
- Connections
- 11 pairs of types, where a type in cross.docker.shared uses a type in cross.shell.
- The types involved
cross.docker.shared.ChildContainer→cross.shell.MessageInfocross.docker.shared.ChildContainerInfo→cross.shell.ColorChoicecross.docker.shared.ChildContainerInfo→cross.shell.Verbositycross.docker.shared.ContainerDataVolume→cross.shell.MessageInfocross.docker.shared.DockerCommandExt→cross.shell.MessageInfocross.docker.shared.DockerContainer→cross.shell.MessageInfocross.docker.shared.DockerOptions→cross.shell.MessageInfocross.docker.shared.DockerPaths→cross.shell.MessageInfocross.docker.shared.DockerVolume→cross.shell.MessageInfocross.docker.shared.MountFinder→cross.shell.MessageInfocross.docker.shared.shared$module→cross.shell.MessageInfo
- Direction
- cross.docker.shared uses cross.shell, so a change to cross.shell can break cross.docker.shared, while a change to cross.docker.shared can't break cross.shell.
- Position
- Below the diagonal: cross.docker.shared uses a module listed above it, which is the healthy direction.
23→11 cross.docker.shared uses cross.extensions✕
- Connections
- 1 pair of types, where a type in cross.docker.shared uses a type in cross.extensions.
- The types involved
cross.docker.shared.DockerCommandExt→cross.extensions.SafeCommand
- Direction
- cross.docker.shared uses cross.extensions, so a change to cross.extensions can break cross.docker.shared, while a change to cross.docker.shared can't break cross.extensions.
- Position
- Below the diagonal: cross.docker.shared uses a module listed above it, which is the healthy direction.
23→16 cross.docker.shared uses cross.cargo✕
- Connections
- 4 pairs of types, where a type in cross.docker.shared uses a type in cross.cargo.
- The types involved
cross.docker.shared.Directories→cross.cargo.CargoMetadatacross.docker.shared.DockerCommandExt→cross.cargo.CargoMetadatacross.docker.shared.DockerPaths→cross.cargo.CargoMetadatacross.docker.shared.PackageDirectories→cross.cargo.CargoMetadata
- Direction
- cross.docker.shared uses cross.cargo, so a change to cross.cargo can break cross.docker.shared, while a change to cross.docker.shared can't break cross.cargo.
- Position
- Below the diagonal: cross.docker.shared uses a module listed above it, which is the healthy direction.
23→17 cross.docker.shared uses cross.docker.engine✕
- Connections
- 10 pairs of types, where a type in cross.docker.shared uses a type in cross.docker.engine.
- The types involved
cross.docker.shared.ChildContainer→cross.docker.engine.Enginecross.docker.shared.ChildContainerInfo→cross.docker.engine.Enginecross.docker.shared.ContainerDataVolume→cross.docker.engine.Enginecross.docker.shared.DockerCommandExt→cross.docker.engine.EngineTypecross.docker.shared.DockerContainer→cross.docker.engine.Enginecross.docker.shared.DockerOptions→cross.docker.engine.Enginecross.docker.shared.DockerPaths→cross.docker.engine.Enginecross.docker.shared.DockerVolume→cross.docker.engine.Enginecross.docker.shared.MountFinder→cross.docker.engine.Enginecross.docker.shared.shared$module→cross.docker.engine.Engine
- Direction
- cross.docker.shared uses cross.docker.engine, so a change to cross.docker.engine can break cross.docker.shared, while a change to cross.docker.shared can't break cross.docker.engine.
- Position
- Below the diagonal: cross.docker.shared uses a module listed above it, which is the healthy direction.
23→19 cross.docker.shared uses cross.docker.docker_ignore✕
- Connections
- 1 pair of types, where a type in cross.docker.shared uses a type in cross.docker.docker_ignore.
- The types involved
cross.docker.shared.ContainerDataVolume→cross.docker.docker_ignore.DockerIgnore
- Direction
- cross.docker.shared uses cross.docker.docker_ignore, so a change to cross.docker.docker_ignore can break cross.docker.shared, while a change to cross.docker.shared can't break cross.docker.docker_ignore.
- Position
- Below the diagonal: cross.docker.shared uses a module listed above it, which is the healthy direction.
23→32 cross.docker.shared uses cross.config part of a loop✕
- Connections
- 2 pairs of types, where a type in cross.docker.shared uses a type in cross.config.
- The types involved
cross.docker.shared.DockerOptions→cross.config.Configcross.docker.shared.shared$module→cross.config.Config
- Direction
- cross.docker.shared uses cross.config, so a change to cross.config can break cross.docker.shared, while a change to cross.docker.shared can't break cross.config.
- 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.
23→33 cross.docker.shared uses cross.rustc part of a loop✕
- Connections
- 4 pairs of types, where a type in cross.docker.shared uses a type in cross.rustc.
- The types involved
cross.docker.shared.Directories→cross.rustc.QualifiedToolchaincross.docker.shared.DockerPaths→cross.rustc.QualifiedToolchaincross.docker.shared.DockerVolume→cross.rustc.QualifiedToolchaincross.docker.shared.ToolchainDirectories→cross.rustc.QualifiedToolchain
- Direction
- cross.docker.shared uses cross.rustc, so a change to cross.rustc can break cross.docker.shared, while a change to cross.docker.shared can't break cross.rustc.
- 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.
23→35 cross.docker.shared uses cross.bin.commands.images part of a loop✕
- Connections
- 1 pair of types, where a type in cross.docker.shared uses a type in cross.bin.commands.images.
- The types involved
cross.docker.shared.DockerOptions→cross.bin.commands.images.Image
- Direction
- cross.docker.shared uses cross.bin.commands.images, so a change to cross.bin.commands.images can break cross.docker.shared, while a change to cross.docker.shared can't break cross.bin.commands.images.
- 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.
23→37 cross.docker.shared uses cross part of a loop✕
- Connections
- 6 pairs of types, where a type in cross.docker.shared uses a type in cross.
- The types involved
cross.docker.shared.ContainerDataVolume→cross.TargetTriplecross.docker.shared.DockerCommandExt→cross.Targetcross.docker.shared.DockerOptions→cross.CommandVariantcross.docker.shared.DockerOptions→cross.Targetcross.docker.shared.ToolchainDirectories→cross.TargetTriplecross.docker.shared.shared$module→cross.Target
- Direction
- cross.docker.shared uses cross, so a change to cross can break cross.docker.shared, while a change to cross.docker.shared can't break cross.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→5 xtask.build_docker_image uses cross.shell✕
- Connections
- 1 pair of types, where a type in xtask.build_docker_image uses a type in cross.shell.
- The types involved
xtask.build_docker_image.build_docker_image$module→cross.shell.MessageInfo
- Direction
- xtask.build_docker_image uses cross.shell, so a change to cross.shell can break xtask.build_docker_image, while a change to xtask.build_docker_image can't break cross.shell.
- Position
- Below the diagonal: xtask.build_docker_image uses a module listed above it, which is the healthy direction.
24→10 xtask.build_docker_image uses cross.docker.image✕
- Connections
- 1 pair of types, where a type in xtask.build_docker_image uses a type in cross.docker.image.
- The types involved
xtask.build_docker_image.BuildDockerImage→cross.docker.image.ImagePlatform
- Direction
- xtask.build_docker_image uses cross.docker.image, so a change to cross.docker.image can break xtask.build_docker_image, while a change to xtask.build_docker_image can't break cross.docker.image.
- Position
- Below the diagonal: xtask.build_docker_image uses a module listed above it, which is the healthy direction.
24→17 xtask.build_docker_image uses cross.docker.engine✕
- Connections
- 1 pair of types, where a type in xtask.build_docker_image uses a type in cross.docker.engine.
- The types involved
xtask.build_docker_image.build_docker_image$module→cross.docker.engine.Engine
- Direction
- xtask.build_docker_image uses cross.docker.engine, so a change to cross.docker.engine can break xtask.build_docker_image, while a change to xtask.build_docker_image can't break cross.docker.engine.
- Position
- Below the diagonal: xtask.build_docker_image uses a module listed above it, which is the healthy direction.
24→22 xtask.build_docker_image uses xtask.util✕
- Connections
- 2 pairs of types, where a type in xtask.build_docker_image uses a type in xtask.util.
- The types involved
xtask.build_docker_image.BuildDockerImage→xtask.util.ImageTargetxtask.build_docker_image.build_docker_image$module→xtask.util.ImageTarget
- Direction
- xtask.build_docker_image uses xtask.util, so a change to xtask.util can break xtask.build_docker_image, while a change to xtask.build_docker_image can't break xtask.util.
- Position
- Below the diagonal: xtask.build_docker_image uses a module listed above it, which is the healthy direction.
25→22 xtask.ci.target_matrix uses xtask.util✕
- Connections
- 1 pair of types, where a type in xtask.ci.target_matrix uses a type in xtask.util.
- The types involved
xtask.ci.target_matrix.TargetMatrixArgs→xtask.util.CiTarget
- Direction
- xtask.ci.target_matrix uses xtask.util, so a change to xtask.util can break xtask.ci.target_matrix, while a change to xtask.ci.target_matrix can't break xtask.util.
- Position
- Below the diagonal: xtask.ci.target_matrix uses a module listed above it, which is the healthy direction.
26→5 xtask.target_info uses cross.shell✕
- Connections
- 1 pair of types, where a type in xtask.target_info uses a type in cross.shell.
- The types involved
xtask.target_info.target_info$module→cross.shell.MessageInfo
- Direction
- xtask.target_info uses cross.shell, so a change to cross.shell can break xtask.target_info, while a change to xtask.target_info can't break cross.shell.
- Position
- Below the diagonal: xtask.target_info uses a module listed above it, which is the healthy direction.
26→17 xtask.target_info uses cross.docker.engine✕
- Connections
- 1 pair of types, where a type in xtask.target_info uses a type in cross.docker.engine.
- The types involved
xtask.target_info.target_info$module→cross.docker.engine.Engine
- Direction
- xtask.target_info uses cross.docker.engine, so a change to cross.docker.engine can break xtask.target_info, while a change to xtask.target_info can't break cross.docker.engine.
- Position
- Below the diagonal: xtask.target_info uses a module listed above it, which is the healthy direction.
26→22 xtask.target_info uses xtask.util✕
- Connections
- 2 pairs of types, where a type in xtask.target_info uses a type in xtask.util.
- The types involved
xtask.target_info.TargetInfo→xtask.util.ImageTargetxtask.target_info.target_info$module→xtask.util.ImageTarget
- Direction
- xtask.target_info uses xtask.util, so a change to xtask.util can break xtask.target_info, while a change to xtask.target_info can't break xtask.util.
- Position
- Below the diagonal: xtask.target_info uses a module listed above it, which is the healthy direction.
27→5 cross.docker uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.docker uses a type in cross.shell.
- The types involved
cross.docker.docker$module→cross.shell.MessageInfo
- Direction
- cross.docker uses cross.shell, so a change to cross.shell can break cross.docker, while a change to cross.docker can't break cross.shell.
- Position
- Below the diagonal: cross.docker uses a module listed above it, which is the healthy direction.
27→16 cross.docker uses cross.cargo✕
- Connections
- 1 pair of types, where a type in cross.docker uses a type in cross.cargo.
- The types involved
cross.docker.docker$module→cross.cargo.Subcommand
- Direction
- cross.docker uses cross.cargo, so a change to cross.cargo can break cross.docker, while a change to cross.docker can't break cross.cargo.
- Position
- Below the diagonal: cross.docker uses a module listed above it, which is the healthy direction.
27→23 cross.docker uses cross.docker.shared✕
- Connections
- 2 pairs of types, where a type in cross.docker uses a type in cross.docker.shared.
- The types involved
cross.docker.docker$module→cross.docker.shared.DockerOptionscross.docker.docker$module→cross.docker.shared.DockerPaths
- Direction
- cross.docker uses cross.docker.shared, so a change to cross.docker.shared can break cross.docker, while a change to cross.docker can't break cross.docker.shared.
- Position
- Below the diagonal: cross.docker uses a module listed above it, which is the healthy direction.
28→5 cross.docker.custom uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.docker.custom uses a type in cross.shell.
- The types involved
cross.docker.custom.Dockerfile→cross.shell.MessageInfo
- Direction
- cross.docker.custom uses cross.shell, so a change to cross.shell can break cross.docker.custom, while a change to cross.docker.custom can't break cross.shell.
- Position
- Below the diagonal: cross.docker.custom uses a module listed above it, which is the healthy direction.
28→10 cross.docker.custom uses cross.docker.image✕
- Connections
- 1 pair of types, where a type in cross.docker.custom uses a type in cross.docker.image.
- The types involved
cross.docker.custom.Dockerfile→cross.docker.image.ImagePlatform
- Direction
- cross.docker.custom uses cross.docker.image, so a change to cross.docker.image can break cross.docker.custom, while a change to cross.docker.custom can't break cross.docker.image.
- Position
- Below the diagonal: cross.docker.custom uses a module listed above it, which is the healthy direction.
28→16 cross.docker.custom uses cross.cargo✕
- Connections
- 2 pairs of types, where a type in cross.docker.custom uses a type in cross.cargo.
- The types involved
cross.docker.custom.Dockerfile→cross.cargo.CargoMetadatacross.docker.custom.custom$module→cross.cargo.CargoMetadata
- Direction
- cross.docker.custom uses cross.cargo, so a change to cross.cargo can break cross.docker.custom, while a change to cross.docker.custom can't break cross.cargo.
- Position
- Below the diagonal: cross.docker.custom uses a module listed above it, which is the healthy direction.
28→23 cross.docker.custom uses cross.docker.shared✕
- Connections
- 2 pairs of types, where a type in cross.docker.custom uses a type in cross.docker.shared.
- The types involved
cross.docker.custom.Dockerfile→cross.docker.shared.DockerOptionscross.docker.custom.Dockerfile→cross.docker.shared.DockerPaths
- Direction
- cross.docker.custom uses cross.docker.shared, so a change to cross.docker.shared can break cross.docker.custom, while a change to cross.docker.custom can't break cross.docker.shared.
- Position
- Below the diagonal: cross.docker.custom uses a module listed above it, which is the healthy direction.
28→37 cross.docker.custom uses cross part of a loop✕
- Connections
- 1 pair of types, where a type in cross.docker.custom uses a type in cross.
- The types involved
cross.docker.custom.Dockerfile→cross.TargetTriple
- Direction
- cross.docker.custom uses cross, so a change to cross can break cross.docker.custom, while a change to cross.docker.custom can't break cross.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→5 cross.docker.local uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.docker.local uses a type in cross.shell.
- The types involved
cross.docker.local.local$module→cross.shell.MessageInfo
- Direction
- cross.docker.local uses cross.shell, so a change to cross.shell can break cross.docker.local, while a change to cross.docker.local can't break cross.shell.
- Position
- Below the diagonal: cross.docker.local uses a module listed above it, which is the healthy direction.
29→23 cross.docker.local uses cross.docker.shared✕
- Connections
- 2 pairs of types, where a type in cross.docker.local uses a type in cross.docker.shared.
- The types involved
cross.docker.local.local$module→cross.docker.shared.DockerOptionscross.docker.local.local$module→cross.docker.shared.DockerPaths
- Direction
- cross.docker.local uses cross.docker.shared, so a change to cross.docker.shared can break cross.docker.local, while a change to cross.docker.local can't break cross.docker.shared.
- Position
- Below the diagonal: cross.docker.local uses a module listed above it, which is the healthy direction.
30→5 cross.docker.remote uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.docker.remote uses a type in cross.shell.
- The types involved
cross.docker.remote.remote$module→cross.shell.MessageInfo
- Direction
- cross.docker.remote uses cross.shell, so a change to cross.shell can break cross.docker.remote, while a change to cross.docker.remote can't break cross.shell.
- Position
- Below the diagonal: cross.docker.remote uses a module listed above it, which is the healthy direction.
30→16 cross.docker.remote uses cross.cargo✕
- Connections
- 1 pair of types, where a type in cross.docker.remote uses a type in cross.cargo.
- The types involved
cross.docker.remote.remote$module→cross.cargo.Subcommand
- Direction
- cross.docker.remote uses cross.cargo, so a change to cross.cargo can break cross.docker.remote, while a change to cross.docker.remote can't break cross.cargo.
- Position
- Below the diagonal: cross.docker.remote uses a module listed above it, which is the healthy direction.
30→17 cross.docker.remote uses cross.docker.engine✕
- Connections
- 1 pair of types, where a type in cross.docker.remote uses a type in cross.docker.engine.
- The types involved
cross.docker.remote.remote$module→cross.docker.engine.Engine
- Direction
- cross.docker.remote uses cross.docker.engine, so a change to cross.docker.engine can break cross.docker.remote, while a change to cross.docker.remote can't break cross.docker.engine.
- Position
- Below the diagonal: cross.docker.remote uses a module listed above it, which is the healthy direction.
30→19 cross.docker.remote uses cross.docker.docker_ignore✕
- Connections
- 1 pair of types, where a type in cross.docker.remote uses a type in cross.docker.docker_ignore.
- The types involved
cross.docker.remote.Fingerprint→cross.docker.docker_ignore.DockerIgnore
- Direction
- cross.docker.remote uses cross.docker.docker_ignore, so a change to cross.docker.docker_ignore can break cross.docker.remote, while a change to cross.docker.remote can't break cross.docker.docker_ignore.
- Position
- Below the diagonal: cross.docker.remote uses a module listed above it, which is the healthy direction.
30→23 cross.docker.remote uses cross.docker.shared✕
- Connections
- 2 pairs of types, where a type in cross.docker.remote uses a type in cross.docker.shared.
- The types involved
cross.docker.remote.remote$module→cross.docker.shared.DockerOptionscross.docker.remote.remote$module→cross.docker.shared.DockerPaths
- Direction
- cross.docker.remote uses cross.docker.shared, so a change to cross.docker.shared can break cross.docker.remote, while a change to cross.docker.remote can't break cross.docker.shared.
- Position
- Below the diagonal: cross.docker.remote uses a module listed above it, which is the healthy direction.
31→5 cross.cross_toml uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.cross_toml uses a type in cross.shell.
- The types involved
cross.cross_toml.CrossToml→cross.shell.MessageInfo
- Direction
- cross.cross_toml uses cross.shell, so a change to cross.shell can break cross.cross_toml, while a change to cross.cross_toml can't break cross.shell.
- Position
- Below the diagonal: cross.cross_toml uses a module listed above it, which is the healthy direction.
31→10 cross.cross_toml uses cross.docker.image✕
- Connections
- 3 pairs of types, where a type in cross.cross_toml uses a type in cross.docker.image.
- The types involved
cross.cross_toml.CrossTargetConfig→cross.docker.image.PossibleImagecross.cross_toml.CrossToml→cross.docker.image.PossibleImagecross.cross_toml.CrossZigConfig→cross.docker.image.PossibleImage
- Direction
- cross.cross_toml uses cross.docker.image, so a change to cross.docker.image can break cross.cross_toml, while a change to cross.cross_toml can't break cross.docker.image.
- Position
- Below the diagonal: cross.cross_toml uses a module listed above it, which is the healthy direction.
31→28 cross.cross_toml uses cross.docker.custom✕
- Connections
- 2 pairs of types, where a type in cross.cross_toml uses a type in cross.docker.custom.
- The types involved
cross.cross_toml.CrossBuildConfig→cross.docker.custom.PreBuildcross.cross_toml.CrossTargetConfig→cross.docker.custom.PreBuild
- Direction
- cross.cross_toml uses cross.docker.custom, so a change to cross.docker.custom can break cross.cross_toml, while a change to cross.cross_toml can't break cross.docker.custom.
- Position
- Below the diagonal: cross.cross_toml uses a module listed above it, which is the healthy direction.
31→32 cross.cross_toml uses cross.config part of a loop✕
- Connections
- 1 pair of types, where a type in cross.cross_toml uses a type in cross.config.
- The types involved
cross.cross_toml.CrossToml→cross.config.ConfVal
- Direction
- cross.cross_toml uses cross.config, so a change to cross.config can break cross.cross_toml, while a change to cross.cross_toml can't break cross.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→33 cross.cross_toml uses cross.rustc part of a loop✕
- Connections
- 1 pair of types, where a type in cross.cross_toml uses a type in cross.rustc.
- The types involved
cross.cross_toml.CrossToml→cross.rustc.TargetList
- Direction
- cross.cross_toml uses cross.rustc, so a change to cross.rustc can break cross.cross_toml, while a change to cross.cross_toml can't break cross.rustc.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→37 cross.cross_toml uses cross part of a loop✕
- Connections
- 1 pair of types, where a type in cross.cross_toml uses a type in cross.
- The types involved
cross.cross_toml.CrossToml→cross.Target
- Direction
- cross.cross_toml uses cross, so a change to cross can break cross.cross_toml, while a change to cross.cross_toml can't break cross.
- 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.
32→5 cross.config uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.config uses a type in cross.shell.
- The types involved
cross.config.Config→cross.shell.MessageInfo
- Direction
- cross.config uses cross.shell, so a change to cross.shell can break cross.config, while a change to cross.config can't break cross.shell.
- Position
- Below the diagonal: cross.config uses a module listed above it, which is the healthy direction.
32→28 cross.config uses cross.docker.custom✕
- Connections
- 1 pair of types, where a type in cross.config uses a type in cross.docker.custom.
- The types involved
cross.config.Config→cross.docker.custom.PreBuild
- Direction
- cross.config uses cross.docker.custom, so a change to cross.docker.custom can break cross.config, while a change to cross.config can't break cross.docker.custom.
- Position
- Below the diagonal: cross.config uses a module listed above it, which is the healthy direction.
32→31 cross.config uses cross.cross_toml✕
- Connections
- 2 pairs of types, where a type in cross.config uses a type in cross.cross_toml.
- The types involved
cross.config.Config→cross.cross_toml.BuildStdcross.config.Config→cross.cross_toml.CrossToml
- Direction
- cross.config uses cross.cross_toml, so a change to cross.cross_toml can break cross.config, while a change to cross.config can't break cross.cross_toml.
- Position
- Below the diagonal: cross.config uses a module listed above it, which is the healthy direction.
32→33 cross.config uses cross.rustc part of a loop✕
- Connections
- 1 pair of types, where a type in cross.config uses a type in cross.rustc.
- The types involved
cross.config.Config→cross.rustc.TargetList
- Direction
- cross.config uses cross.rustc, so a change to cross.rustc can break cross.config, while a change to cross.config can't break cross.rustc.
- 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.
32→37 cross.config uses cross part of a loop✕
- Connections
- 2 pairs of types, where a type in cross.config uses a type in cross.
- The types involved
cross.config.Config→cross.Targetcross.config.Environment→cross.Target
- Direction
- cross.config uses cross, so a change to cross can break cross.config, while a change to cross.config can't break cross.
- 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.
33→5 cross.rustc uses cross.shell✕
- Connections
- 2 pairs of types, where a type in cross.rustc uses a type in cross.shell.
- The types involved
cross.rustc.QualifiedToolchain→cross.shell.MessageInfocross.rustc.rustc$module→cross.shell.MessageInfo
- Direction
- cross.rustc uses cross.shell, so a change to cross.shell can break cross.rustc, while a change to cross.rustc can't break cross.shell.
- Position
- Below the diagonal: cross.rustc uses a module listed above it, which is the healthy direction.
33→10 cross.rustc uses cross.docker.image✕
- Connections
- 1 pair of types, where a type in cross.rustc uses a type in cross.docker.image.
- The types involved
cross.rustc.QualifiedToolchain→cross.docker.image.ImagePlatform
- Direction
- cross.rustc uses cross.docker.image, so a change to cross.docker.image can break cross.rustc, while a change to cross.rustc can't break cross.docker.image.
- Position
- Below the diagonal: cross.rustc uses a module listed above it, which is the healthy direction.
33→32 cross.rustc uses cross.config✕
- Connections
- 1 pair of types, where a type in cross.rustc uses a type in cross.config.
- The types involved
cross.rustc.QualifiedToolchain→cross.config.Config
- Direction
- cross.rustc uses cross.config, so a change to cross.config can break cross.rustc, while a change to cross.rustc can't break cross.config.
- Position
- Below the diagonal: cross.rustc uses a module listed above it, which is the healthy direction.
33→37 cross.rustc uses cross part of a loop✕
- Connections
- 3 pairs of types, where a type in cross.rustc uses a type in cross.
- The types involved
cross.rustc.QualifiedToolchain→cross.TargetTriplecross.rustc.Toolchain→cross.TargetTriplecross.rustc.VersionMetaExt→cross.TargetTriple
- Direction
- cross.rustc uses cross, so a change to cross can break cross.rustc, while a change to cross.rustc can't break cross.
- 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.
34→5 cross.bin.commands.containers uses cross.shell✕
- Connections
- 10 pairs of types, where a type in cross.bin.commands.containers uses a type in cross.shell.
- The types involved
cross.bin.commands.containers.Containers→cross.shell.MessageInfocross.bin.commands.containers.CreateVolume→cross.shell.MessageInfocross.bin.commands.containers.ListContainers→cross.shell.MessageInfocross.bin.commands.containers.ListVolumes→cross.shell.MessageInfocross.bin.commands.containers.PruneVolumes→cross.shell.MessageInfocross.bin.commands.containers.RemoveAllContainers→cross.shell.MessageInfocross.bin.commands.containers.RemoveAllVolumes→cross.shell.MessageInfocross.bin.commands.containers.RemoveVolume→cross.shell.MessageInfocross.bin.commands.containers.Volumes→cross.shell.MessageInfocross.bin.commands.containers.containers$module→cross.shell.MessageInfo
- Direction
- cross.bin.commands.containers uses cross.shell, so a change to cross.shell can break cross.bin.commands.containers, while a change to cross.bin.commands.containers can't break cross.shell.
- Position
- Below the diagonal: cross.bin.commands.containers uses a module listed above it, which is the healthy direction.
34→17 cross.bin.commands.containers uses cross.docker.engine✕
- Connections
- 10 pairs of types, where a type in cross.bin.commands.containers uses a type in cross.docker.engine.
- The types involved
cross.bin.commands.containers.Containers→cross.docker.engine.Enginecross.bin.commands.containers.CreateVolume→cross.docker.engine.Enginecross.bin.commands.containers.ListContainers→cross.docker.engine.Enginecross.bin.commands.containers.ListVolumes→cross.docker.engine.Enginecross.bin.commands.containers.PruneVolumes→cross.docker.engine.Enginecross.bin.commands.containers.RemoveAllContainers→cross.docker.engine.Enginecross.bin.commands.containers.RemoveAllVolumes→cross.docker.engine.Enginecross.bin.commands.containers.RemoveVolume→cross.docker.engine.Enginecross.bin.commands.containers.Volumes→cross.docker.engine.Enginecross.bin.commands.containers.containers$module→cross.docker.engine.Engine
- Direction
- cross.bin.commands.containers uses cross.docker.engine, so a change to cross.docker.engine can break cross.bin.commands.containers, while a change to cross.bin.commands.containers can't break cross.docker.engine.
- Position
- Below the diagonal: cross.bin.commands.containers uses a module listed above it, which is the healthy direction.
34→33 cross.bin.commands.containers uses cross.rustc✕
- Connections
- 4 pairs of types, where a type in cross.bin.commands.containers uses a type in cross.rustc.
- The types involved
cross.bin.commands.containers.CreateVolume→cross.rustc.Toolchaincross.bin.commands.containers.RemoveVolume→cross.rustc.Toolchaincross.bin.commands.containers.Volumes→cross.rustc.Toolchaincross.bin.commands.containers.containers$module→cross.rustc.Toolchain
- Direction
- cross.bin.commands.containers uses cross.rustc, so a change to cross.rustc can break cross.bin.commands.containers, while a change to cross.bin.commands.containers can't break cross.rustc.
- Position
- Below the diagonal: cross.bin.commands.containers uses a module listed above it, which is the healthy direction.
35→5 cross.bin.commands.images uses cross.shell✕
- Connections
- 4 pairs of types, where a type in cross.bin.commands.images uses a type in cross.shell.
- The types involved
cross.bin.commands.images.Images→cross.shell.MessageInfocross.bin.commands.images.ListImages→cross.shell.MessageInfocross.bin.commands.images.RemoveImages→cross.shell.MessageInfocross.bin.commands.images.images$module→cross.shell.MessageInfo
- Direction
- cross.bin.commands.images uses cross.shell, so a change to cross.shell can break cross.bin.commands.images, while a change to cross.bin.commands.images can't break cross.shell.
- Position
- Below the diagonal: cross.bin.commands.images uses a module listed above it, which is the healthy direction.
35→17 cross.bin.commands.images uses cross.docker.engine✕
- Connections
- 4 pairs of types, where a type in cross.bin.commands.images uses a type in cross.docker.engine.
- The types involved
cross.bin.commands.images.Images→cross.docker.engine.Enginecross.bin.commands.images.ListImages→cross.docker.engine.Enginecross.bin.commands.images.RemoveImages→cross.docker.engine.Enginecross.bin.commands.images.images$module→cross.docker.engine.Engine
- Direction
- cross.bin.commands.images uses cross.docker.engine, so a change to cross.docker.engine can break cross.bin.commands.images, while a change to cross.bin.commands.images can't break cross.docker.engine.
- Position
- Below the diagonal: cross.bin.commands.images uses a module listed above it, which is the healthy direction.
35→33 cross.bin.commands.images uses cross.rustc✕
- Connections
- 1 pair of types, where a type in cross.bin.commands.images uses a type in cross.rustc.
- The types involved
cross.bin.commands.images.images$module→cross.rustc.TargetList
- Direction
- cross.bin.commands.images uses cross.rustc, so a change to cross.rustc can break cross.bin.commands.images, while a change to cross.bin.commands.images can't break cross.rustc.
- Position
- Below the diagonal: cross.bin.commands.images uses a module listed above it, which is the healthy direction.
36→5 cross.bin.cross-util uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.bin.cross-util uses a type in cross.shell.
- The types involved
cross.bin.cross-util.cross-util$module→cross.shell.MessageInfo
- Direction
- cross.bin.cross-util uses cross.shell, so a change to cross.shell can break cross.bin.cross-util, while a change to cross.bin.cross-util can't break cross.shell.
- Position
- Below the diagonal: cross.bin.cross-util uses a module listed above it, which is the healthy direction.
36→33 cross.bin.cross-util uses cross.rustc✕
- Connections
- 1 pair of types, where a type in cross.bin.cross-util uses a type in cross.rustc.
- The types involved
cross.bin.cross-util.Cli→cross.rustc.Toolchain
- Direction
- cross.bin.cross-util uses cross.rustc, so a change to cross.rustc can break cross.bin.cross-util, while a change to cross.bin.cross-util can't break cross.rustc.
- Position
- Below the diagonal: cross.bin.cross-util uses a module listed above it, which is the healthy direction.
37→5 cross uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross uses a type in cross.shell.
- The types involved
cross.cross$module→cross.shell.MessageInfo
- Direction
- cross uses cross.shell, so a change to cross.shell can break cross, while a change to cross can't break cross.shell.
- Position
- Below the diagonal: cross uses a module listed above it, which is the healthy direction.
37→9 cross uses cross.cli✕
- Connections
- 1 pair of types, where a type in cross uses a type in cross.cli.
- The types involved
cross.cross$module→cross.cli.Args
- Direction
- cross uses cross.cli, so a change to cross.cli can break cross, while a change to cross can't break cross.cli.
- Position
- Below the diagonal: cross uses a module listed above it, which is the healthy direction.
37→11 cross uses cross.extensions✕
- Connections
- 1 pair of types, where a type in cross uses a type in cross.extensions.
- The types involved
cross.CommandVariant→cross.extensions.SafeCommand
- Direction
- cross uses cross.extensions, so a change to cross.extensions can break cross, while a change to cross can't break cross.extensions.
- Position
- Below the diagonal: cross uses a module listed above it, which is the healthy direction.
37→16 cross uses cross.cargo✕
- Connections
- 1 pair of types, where a type in cross uses a type in cross.cargo.
- The types involved
cross.cross$module→cross.cargo.CargoMetadata
- Direction
- cross uses cross.cargo, so a change to cross.cargo can break cross, while a change to cross can't break cross.cargo.
- Position
- Below the diagonal: cross uses a module listed above it, which is the healthy direction.
37→17 cross uses cross.docker.engine✕
- Connections
- 1 pair of types, where a type in cross uses a type in cross.docker.engine.
- The types involved
cross.CrossSetup→cross.docker.engine.Engine
- Direction
- cross uses cross.docker.engine, so a change to cross.docker.engine can break cross, while a change to cross can't break cross.docker.engine.
- Position
- Below the diagonal: cross uses a module listed above it, which is the healthy direction.
37→23 cross uses cross.docker.shared✕
- Connections
- 1 pair of types, where a type in cross uses a type in cross.docker.shared.
- The types involved
cross.cross$module→cross.docker.shared.DockerOptions
- Direction
- cross uses cross.docker.shared, so a change to cross.docker.shared can break cross, while a change to cross can't break cross.docker.shared.
- Position
- Below the diagonal: cross uses a module listed above it, which is the healthy direction.
37→31 cross uses cross.cross_toml✕
- Connections
- 2 pairs of types, where a type in cross uses a type in cross.cross_toml.
- The types involved
cross.CrossSetup→cross.cross_toml.BuildStdcross.cross$module→cross.cross_toml.BuildStd
- Direction
- cross uses cross.cross_toml, so a change to cross.cross_toml can break cross, while a change to cross can't break cross.cross_toml.
- Position
- Below the diagonal: cross uses a module listed above it, which is the healthy direction.
37→32 cross uses cross.config✕
- Connections
- 2 pairs of types, where a type in cross uses a type in cross.config.
- The types involved
cross.CrossSetup→cross.config.Configcross.cross$module→cross.config.Config
- Direction
- cross uses cross.config, so a change to cross.config can break cross, while a change to cross can't break cross.config.
- Position
- Below the diagonal: cross uses a module listed above it, which is the healthy direction.
37→33 cross uses cross.rustc✕
- Connections
- 4 pairs of types, where a type in cross uses a type in cross.rustc.
- The types involved
cross.CrossSetup→cross.rustc.QualifiedToolchaincross.Target→cross.rustc.TargetListcross.cross$module→cross.rustc.QualifiedToolchaincross.cross$module→cross.rustc.TargetList
- Direction
- cross uses cross.rustc, so a change to cross.rustc can break cross, while a change to cross can't break cross.rustc.
- Position
- Below the diagonal: cross uses a module listed above it, which is the healthy direction.
37→35 cross uses cross.bin.commands.images✕
- Connections
- 1 pair of types, where a type in cross uses a type in cross.bin.commands.images.
- The types involved
cross.CrossSetup→cross.bin.commands.images.Image
- Direction
- cross uses cross.bin.commands.images, so a change to cross.bin.commands.images can break cross, while a change to cross can't break cross.bin.commands.images.
- Position
- Below the diagonal: cross uses a module listed above it, which is the healthy direction.
38→5 cross.bin.commands.run uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.bin.commands.run uses a type in cross.shell.
- The types involved
cross.bin.commands.run.Run→cross.shell.MessageInfo
- Direction
- cross.bin.commands.run uses cross.shell, so a change to cross.shell can break cross.bin.commands.run, while a change to cross.bin.commands.run can't break cross.shell.
- Position
- Below the diagonal: cross.bin.commands.run uses a module listed above it, which is the healthy direction.
38→17 cross.bin.commands.run uses cross.docker.engine✕
- Connections
- 1 pair of types, where a type in cross.bin.commands.run uses a type in cross.docker.engine.
- The types involved
cross.bin.commands.run.Run→cross.docker.engine.Engine
- Direction
- cross.bin.commands.run uses cross.docker.engine, so a change to cross.docker.engine can break cross.bin.commands.run, while a change to cross.bin.commands.run can't break cross.docker.engine.
- Position
- Below the diagonal: cross.bin.commands.run uses a module listed above it, which is the healthy direction.
38→36 cross.bin.commands.run uses cross.bin.cross-util✕
- Connections
- 1 pair of types, where a type in cross.bin.commands.run uses a type in cross.bin.cross-util.
- The types involved
cross.bin.commands.run.Run→cross.bin.cross-util.Cli
- Direction
- cross.bin.commands.run uses cross.bin.cross-util, so a change to cross.bin.cross-util can break cross.bin.commands.run, while a change to cross.bin.commands.run can't break cross.bin.cross-util.
- Position
- Below the diagonal: cross.bin.commands.run uses a module listed above it, which is the healthy direction.
39→37 cross.interpreter uses cross✕
- Connections
- 1 pair of types, where a type in cross.interpreter uses a type in cross.
- The types involved
cross.interpreter.interpreter$module→cross.Target
- Direction
- cross.interpreter uses cross, so a change to cross can break cross.interpreter, while a change to cross.interpreter can't break cross.
- Position
- Below the diagonal: cross.interpreter uses a module listed above it, which is the healthy direction.
40→5 cross.rustup uses cross.shell✕
- Connections
- 1 pair of types, where a type in cross.rustup uses a type in cross.shell.
- The types involved
cross.rustup.rustup$module→cross.shell.MessageInfo
- Direction
- cross.rustup uses cross.shell, so a change to cross.shell can break cross.rustup, while a change to cross.rustup can't break cross.shell.
- Position
- Below the diagonal: cross.rustup uses a module listed above it, which is the healthy direction.
40→9 cross.rustup uses cross.cli✕
- Connections
- 1 pair of types, where a type in cross.rustup uses a type in cross.cli.
- The types involved
cross.rustup.rustup$module→cross.cli.Args
- Direction
- cross.rustup uses cross.cli, so a change to cross.cli can break cross.rustup, while a change to cross.rustup can't break cross.cli.
- Position
- Below the diagonal: cross.rustup uses a module listed above it, which is the healthy direction.
40→33 cross.rustup uses cross.rustc✕
- Connections
- 1 pair of types, where a type in cross.rustup uses a type in cross.rustc.
- The types involved
cross.rustup.rustup$module→cross.rustc.QualifiedToolchain
- Direction
- cross.rustup uses cross.rustc, so a change to cross.rustc can break cross.rustup, while a change to cross.rustup can't break cross.rustc.
- Position
- Below the diagonal: cross.rustup uses a module listed above it, which is the healthy direction.
40→37 cross.rustup uses cross✕
- Connections
- 2 pairs of types, where a type in cross.rustup uses a type in cross.
- The types involved
cross.rustup.AvailableTargets→cross.Targetcross.rustup.rustup$module→cross.Target
- Direction
- cross.rustup uses cross, so a change to cross can break cross.rustup, while a change to cross.rustup can't break cross.
- Position
- Below the diagonal: cross.rustup 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 |
|---|---|---|
| A02:2025 — Security Misconfiguration | 129 | High / Critical |
| A05:2025 — Injection | 70 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with cross-util.rs; Resolve the 24 Low coverage finding(s) in Code Coverage — start with cargo.rs, cli.rs, custom.rs; Resolve the 28 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (4), REDACTED (4).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with cross-util.rs. | +5.1 pts | Low | ADR Quality |
| Resolve the 24 Low coverage finding(s) in Code Coverage — start with cargo.rs, cli.rs, custom.rs. | +5.0 pts | Medium | Code Coverage |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +2.5 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 28 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (4), REDACTED (4). | +4.5 pts | Medium | Static Analysis (SAST) |
| Resolve the 83 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (4), REDACTED (3). | +4.3 pts | Medium | IaC & Container Security |
| 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. | +4.3 pts | Medium | Architecture documentation |
| 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. | +3.3 pts | Medium | Observability |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. | +1.4 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.3 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.3 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
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 41 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 41 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, 301 of 326 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- 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, .py) and this repository declares a Python test suite (docker/android, 4 test files), but it was not re-run: its dependency install failed (pip exit 1: no error line printed), so its suite was not run against dependencies it does not declare. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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.
- D31 IaC & Container Security — 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. Docker/Dockerfile.x86_64-unknown-linux-gnu.centos carries no `FROM` instruction, so it declares no build stage and every Dockerfile rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 67 of 68 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
- 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.
- AXR1 Runtime accessibility — 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. Render strategy: boot via Dockerfile (REDACTED). docker build failed (exit 1) — 82.83 /tmp/tmp.zDaitQSQmR / 82.86 curl: (22) The requested URL returned error: 403 ------ REDACTED:14 -------------------- 12 | 13 | COPY REDACTED / 14 | >>> RUN /qemu.sh aarch64 15 | 16 | ARG ANDROID_NDK=r25b -------------------- ERROR: failed to solve: process "/bin/sh -c /qemu.sh aarch64" did not complete successfully: exit code: 22; runtime evidence skipped.
- 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, zig 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, zig is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- 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 Python, Rust, Zig is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was xtask::build_docker_image::build_docker_image at 43. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being TargetTriple::deb_arch at 57 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with xtask::build_docker_image::build_docker_image (cyclomatic 43), cross::docker::remote::run (cyclomatic 39), xtask::crosstool::configure_target (cyclomatic 33). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
16 method(s) exceeded the cognitive complexity threshold of 15; the worst was xtask::build_docker_image::build_docker_image at 80.
What to do
- Bring the 16 bodies over 15 down to 15 or less in Cognitive Complexity — start with xtask::build_docker_image::build_docker_image (cognitive 80), cross::docker::remote::run (cognitive 67), cross::run (cognitive 41). — 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 16 together lifts Cognitive Complexity from 7.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
6 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 FunctionTooLong finding(s) in God Classes — start with remote.rs, cli.rs, lib.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes — start with shared.rs, remote.rs, lib.rs. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
9 duplicated block group(s) detected. 2.2 % of the production lines (345 of 15,346) are in a reported copy. A further 7 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with containers.rs, cross_toml.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copies of one member (3 members, 50+ corresponding lines) finding(s) in Code Duplication — start with cross_toml.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (19 corresponding lines) finding(s) in Code Duplication — start with hooks.rs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
3 production modules (Cargo+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 24 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 30.7% — 24 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 40 production file(s), 4 test binaries and 0 doc-test binaries).
What to do
- Resolve the 24 Low coverage finding(s) in Code Coverage — start with cargo.rs, cli.rs, custom.rs. — One of this dimension's main actionable groups (24 warning-level).
D12 · Dependency Hygiene
12 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 144 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 OR Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/docker/remote.rs (9×39=351)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with remote.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/docker/docker_ignore.rs. Counted over 32 of the 39 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 15346 LoC (0.1/KLoC) → score 9.8. 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 10 FixmeComment finding(s) in Explicit Debt — start with shared.rs (2), build_docker_image.rs, config.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 7 TodoComment finding(s) in Explicit Debt — start with build_docker_image.rs (2), ci.rs, cargo.rs. — One of this dimension's main actionable groups (7 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 13 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with cross-util.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 3 build units (Cargo, Python) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
70 finding(s): 0 critical, 69 high, 1 medium, 0 low. 28 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 5 file(s) — `docker/crosstool-ng.sh` (line 88), `docker/linux-runner` (line 58), `docker/solaris.sh` (line 143), `src/cli.rs` (line 183), `src/rustup.rs` (line 65) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 28 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (4), REDACTED (4). — One of this dimension's main actionable groups (28 issue-level).
- Resolve the 7 REDACTED finding(s) charged to Static Analysis (SAST) — the other 28 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (35 issue-level, 7 of them charged here).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
129 finding(s): 0 critical, 46 high, 83 medium, 0 low.
What to do
- Resolve the 83 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (83 warning-level).
- Resolve the 46 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (46 issue-level).
D34 · Knowledge Freshness
10 of 32 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/config.rs. Counted over 32 of the 39 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with soong.py, crosstool.rs, make.py. — One of this dimension's main actionable groups (9 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with config.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 2 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- 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
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `cargo`, `pip`, `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `cargo`, `pip`, `gitsubmodule` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
X21 · Side-effecting pattern guard
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 90% | Exemplary | Solid. |
| Architecture | 96% | Exemplary | Strongest area. |
| Maturity | 59% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 57% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 40% | Weak — gated by D29, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 73 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 82.83 /tmp/tmp.zDaitQSQmR / 82.86 curl: (22) The requested URL returned error: 403 ------ REDACTED:14 -------------------- 12 | 13 | COPY REDACTED / 14 | >>> RUN /qemu.sh aarch64 15 | 16 | ARG ANDROID_NDK=r25b -------------------- ERROR: failed to solve: process "/bin/sh -c /qemu.sh aarch64" did not complete successfully: exit code: 22; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~910 lines of test source are present (.rs, .py) 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 .py 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.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (2467 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.
- 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
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and 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
- 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 data present for 40 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 40 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — X12 reached only 7% of this repository's production lines — rust (14,254 lines), zig (17 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 — X19 reached only 7% of this repository's production lines — rust (14,254 lines), zig (17 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- 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 — 116 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge src/config.rs:1
Serious — 177 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low coverage: src/cargo.rs src/cargo.rs:1
- Low coverage: src/cli.rs src/cli.rs:1
- Low coverage: src/docker/custom.rs src/docker/custom.rs:1
- Low coverage: src/docker/local.rs src/docker/local.rs:1
- Low coverage: src/docker/mod.rs src/docker/mod.rs:1
- Low coverage: src/docker/remote.rs src/docker/remote.rs:1
- Low coverage: src/docker/shared.rs src/docker/shared.rs:1
- Low coverage: src/errors.rs src/errors.rs:1
- Low coverage: src/extensions.rs src/extensions.rs:1
- Low coverage: src/id.rs src/id.rs:1
- Low coverage: src/interpreter.rs src/interpreter.rs:1
- Low coverage: src/lib.rs src/lib.rs:1
- Low coverage: src/rustup.rs src/rustup.rs:1
- Low coverage: src/shell.rs src/shell.rs:1
- Low coverage: src/temp.rs src/temp.rs:1
- Low coverage: xtask/src/build_docker_image.rs xtask/src/build_docker_image.rs:1
- Low coverage: xtask/src/ci.rs xtask/src/ci.rs:1
- Low coverage: xtask/src/ci/target_matrix.rs xtask/src/ci/target_matrix.rs:1
- Low coverage: xtask/src/crosstool.rs xtask/src/crosstool.rs:1
- Low coverage: xtask/src/hooks.rs xtask/src/hooks.rs:1
- Low coverage: xtask/src/install_git_hooks.rs xtask/src/install_git_hooks.rs:1
- Low coverage: xtask/src/main.rs xtask/src/main.rs:1
- Low coverage: xtask/src/target_info.rs xtask/src/target_info.rs:1
- Low coverage: xtask/src/util.rs xtask/src/util.rs:1
- FixmeComment xtask/src/build_docker_image.rs:370
- FixmeComment src/config.rs:447
- FixmeComment src/errors.rs:108
- FixmeComment src/docker/shared.rs:1
- FixmeComment src/shell.rs:382
- FixmeComment src/temp.rs:1
- FixmeComment src/docker/custom.rs:172
- FixmeComment src/docker/engine.rs:126
- FixmeComment src/docker/image.rs:77
- FixmeComment src/docker/shared.rs:1038
- cross::docker::remote::run (cognitive 67) src/docker/remote.rs:815
- cross::run (cognitive 41) src/lib.rs:505
- cross::cli::parse (cognitive 39) src/cli.rs:160
- cross::docker::remote::parse_artifact_filenames (cognitive 32) src/docker/remote.rs:602
- cross::get_filtered_args (cognitive 27) src/lib.rs:672
- cross::bin::commands::images::list_images (cognitive 24) src/bin/commands/images.rs:245
- cross::docker::remote::copy_dir_with_rel (cognitive 23) src/docker/remote.rs:480
- cross::warn_host_version_mismatch (cognitive 19) src/lib.rs:857
- cross::docker::shared::docker_inspect_self (cognitive 17) src/docker/shared.rs:1355
- TodoComment xtask/src/build_docker_image.rs:319
- TodoComment xtask/src/build_docker_image.rs:455
- TodoComment xtask/src/ci.rs:48
- TodoComment src/cargo.rs:90
- TodoComment src/file.rs:226
- TodoComment src/tests/toml.rs:79
- TodoComment src/docker/mod.rs:54
- cross::docker::remote::run (cyclomatic 39) src/docker/remote.rs:815
- cross::cli::parse (cyclomatic 23) src/cli.rs:160
- cross::run (cyclomatic 18) src/lib.rs:505
- xtask::build_docker_image::build_docker_image (cognitive 80) xtask/src/build_docker_image.rs:102
- xtask::crosstool::configure_target (cognitive 41) xtask/src/crosstool.rs:287
- xtask::ci::ci (cognitive 18) xtask/src/ci.rs:32
- FunctionTooLong: cross::docker::remote::run src/docker/remote.rs:815
- FunctionTooLong: cross::cli::parse src/cli.rs:160
- FunctionTooLong: cross::run src/lib.rs:505
- FileTooLong: docker/shared.rs src/docker/shared.rs
- FileTooLong: docker/remote.rs src/docker/remote.rs
- FileTooLong: src/lib.rs src/lib.rs
- REDACTED
- REDACTED
- REDACTED
- xtask::build_docker_image::build_docker_image (cyclomatic 43) xtask/src/build_docker_image.rs:102
- xtask::crosstool::configure_target (cyclomatic 33) xtask/src/crosstool.rs:287
- DockerIgnore::is_ignored (cognitive 25) src/docker/docker_ignore.rs:136
- DockerIgnore::parse (cognitive 23) src/docker/docker_ignore.rs:71
- Duplicated block (9 lines × 2) src/bin/commands/containers.rs:314
- Duplicated block (9 lines × 2) src/cross_toml.rs:428
- Hotspot: src/docker/remote.rs src/docker/remote.rs:815
- Fingerprint::_read_dir (cognitive 20) src/docker/remote.rs:711
- build-system.remove_soong_tests (cognitive 19) docker/android/scripts/build-system.py:69
- REDACTED
- REDACTED
- REDACTED
- Edited copies of one member (3 members, 50+ corresponding lines) src/cross_toml.rs:414
- Edited copy of a member (19 corresponding lines) xtask/src/hooks.rs:137
- Edited copy of a member (15 corresponding lines) src/bin/commands/containers.rs:222
- Edited copy of a member (16 corresponding lines) xtask/src/hooks.rs:189
- Edited copy of a member (11 corresponding lines) src/temp.rs:48
- Edited copy of a member (10 corresponding lines) xtask/src/ci/target_matrix.rs:153
- Edited copy of a member (8 corresponding lines) src/bin/cross-util.rs:55
- Duplicated block (27 lines × 2) src/cross_toml.rs:431
- Duplicated block (14 lines × 3) src/cross_toml.rs:447
- Duplicated block (8 lines × 2) src/bin/commands/containers.rs:229
- Duplicated block (7 lines × 3) xtask/src/crosstool.rs:254
- Duplicated block (6 lines × 2) xtask/src/hooks.rs:138
- Duplicated block (5 lines × 5) xtask/src/crosstool.rs:87
- Duplicated block (6 lines × 3) xtask/src/crosstool.rs:134
- Off the main sequence: cross
- Coverage collected but not gated
- No structured logging
Minor — 21 finding(s)
- Orphaned file docker/android/android/soong.py:1
- Orphaned file xtask/src/crosstool.rs:1
- Orphaned file docker/android/android/make.py:1
- Orphaned file src/shell.rs:1
- Orphaned file src/cli.rs:1
- Orphaned file xtask/src/hooks.rs:1
- Orphaned file docker/android/scripts/build-system.py:1
- Orphaned file src/docker/local.rs:1
- Orphaned file src/temp.rs:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found src/bin/cross-util.rs:1
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Dependabot does not watch cargo/pip/gitsubmodule REDACTED:2
- Duplicated predicate src/docker/local.rs:132
Minor — 12 finding(s)
- Outdated: chrono
- Outdated: clap
- Outdated: eyre
- Outdated: home
- Outdated: libc
- Outdated: owo-colors
- Outdated: serde
- Outdated: serde_json
- Outdated: signal-hook
- Outdated: thiserror
- Outdated: which
- Outdated: wildmatch
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-b6aad73a49144a58bef10a0f9611a423/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-b6aad73a49144a58bef10a0f9611a423/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 . | 70 | 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 . | 1 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 129 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 |