Executive summary
rust-lang/rustup falls short of our standard for production, in part because it has unsafe settings in infrastructure or container files. It scores 53 out of 100 and is rated Adequate, and 57 of its 59 critical findings are security problems.
Security and Compliance, at 36, is the weakest lens and counts most in the score. The best first step is improving the documentation, worth about 6 points. Fixing the 48 unsafe settings in infrastructure or container files would lift Security and Compliance itself, worth about 5 points. Raising Security and Compliance to 70 would lift the score to about 65.
Forty-eight settings leave the servers or containers unsafe. Seven pipeline steps run downloads nobody checks, and two passwords or keys are open to anyone who can read the repository. Correcting the unsafe settings, checking each download against a checksum and replacing each exposed password or key would close these risks. The page that doesn't say its language needs its language set.
The product code is 16,237 lines, about €32,000 to rebuild.
If Security and Compliance rose from 36 to 70, the lowest score rated Strong, the score would rise from 53 to about 65.
New since the last survey: 17 findings
- Code Duplication · Edited copy of a member (30 corresponding lines) src/errors.rs
- Code Duplication · Edited copy of a member (27 corresponding lines) src/cli/rustup_mode.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/dist/component/transaction.rs
- Code Duplication · Edited copy of a member (18 corresponding lines) src/dist/temp.rs
- Code Duplication · Edited copy of a member (15 corresponding lines) src/cli/self_update/shell.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/cli/rustup_mode.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/toolchain/names.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/dist/manifestation.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) src/cli/self_update/unix.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/dist/temp.rs
- Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) src/dist/component/transaction.rs
- Code Duplication · Edited copy of a member (12 corresponding lines) src/cli/self_update.rs
- Code Duplication · Duplicated block (15–16 lines × 2) src/toolchain/channels.rs
- Code Duplication · Duplicated block (11 lines × 2) src/diskio/mod.rs
- Code Duplication · Duplicated block (10 lines × 2) src/errors.rs
- Churn × Complexity Hotspots · Repeated repair: src/settings.rs src/settings.rs
- Page structure · <html> without a lang www/index.html
Fixed since the last survey: 10 findings
- Code Duplication · Duplicated block (15–16 lines × 2) src/toolchain/channels.rs
- Code Duplication · Duplicated block (13–15 lines × 2) src/errors.rs
- Code Duplication · Duplicated block (11 lines × 2) src/diskio/mod.rs
- Churn × Complexity Hotspots · Repeated repair: src/cli/self_update/stage.rs src/cli/self_update/stage.rs
- Explicit Debt · TodoComment src/download/mod.rs
- Secrets (history) · Secret: aws-access-token REDACTED
- Secrets (history) · Secret: aws-access-token REDACTED
- Secrets (history) · Secret: aws-access-token REDACTED
- Secrets (history) · Secret: aws-access-token REDACTED
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €32,000 · Estimate
| Cost to rebuild | €11,000 to €53,000, for 177 to 562 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 16,237 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: which parts of the code depend on which
| uses → | 1 cli.job.imp | 2 dist.prefix | 3 dist.temp | 4 process.file_source.test_support | 5 cli.job | 6 cli.log | 7 dist.component.transaction | 8 dist.target_tuple | 9 process.terminal_source | 10 toolchain.names | 11 cli.markdown | 12 dist.component.components | 13 process | 14 toolchain | 15 bin.rustup-init | 16 cli.proxy_mode | 17 cli.self_update.shell | 18 dist.config | 19 dist.download | 20 toolchain.channels | 21 cli.self_update.stage | 22 dist.manifest | 23 download | 24 cli.self_update.unix | 25 diskio | 26 dist | 27 cli.self_update | 28 cli.setup_mode | 29 diskio.immediate | 30 diskio.threaded | 31 dist.component.package | 32 dist.manifestation | 33 cli.self_update.windows | 34 settings | 35 config | 36 cli.common | 37 cli.completions | 38 cli.docs | 39 cli.rustup_mode | 40 errors |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cli.job.imp | ||||||||||||||||||||||||||||||||||||||||
| 2 dist.prefix | ||||||||||||||||||||||||||||||||||||||||
| 3 dist.temp | ||||||||||||||||||||||||||||||||||||||||
| 4 process.file_source.test_support | ||||||||||||||||||||||||||||||||||||||||
| 5 cli.job | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 cli.log | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 dist.component.transaction | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 dist.target_tuple | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 process.terminal_source | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 toolchain.names | 5 | 3 | ||||||||||||||||||||||||||||||||||||||
| 11 cli.markdown | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 dist.component.components | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 13 process | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 14 toolchain | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 15 bin.rustup-init | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 cli.proxy_mode | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 cli.self_update.shell | 10 | |||||||||||||||||||||||||||||||||||||||
| 18 dist.config | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 dist.download | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 toolchain.channels | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 cli.self_update.stage | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 dist.manifest | 4 | 1 | 1 | 6 | ||||||||||||||||||||||||||||||||||||
| 23 download | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 cli.self_update.unix | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 diskio | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 dist | 1 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 27 cli.self_update | 1 | 2 | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 28 cli.setup_mode | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 diskio.immediate | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 30 diskio.threaded | 8 | |||||||||||||||||||||||||||||||||||||||
| 31 dist.component.package | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 32 dist.manifestation | 1 | 2 | 3 | 6 | 3 | 5 | 5 | 4 | ||||||||||||||||||||||||||||||||
| 33 cli.self_update.windows | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 settings | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 config | 4 | 3 | 1 | 5 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 36 cli.common | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 cli.completions | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 cli.docs | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 cli.rustup_mode | 1 | 6 | 1 | 1 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 40 errors | 3 | 3 | 4 | 2 |
5→1 cli.job uses cli.job.imp✕
- Connections
- 1 pair of types, where a type in cli.job uses a type in cli.job.imp.
- The types involved
rustup.cli.job.job$module→rustup.cli.job.imp.Setup
- Direction
- cli.job uses cli.job.imp, so a change to cli.job.imp can break cli.job, while a change to cli.job can't break cli.job.imp.
- Position
- Below the diagonal: cli.job uses a module listed above it, which is the healthy direction.
6→13 cli.log uses process part of a loop✕
- Connections
- 1 pair of types, where a type in cli.log uses a type in process.
- The types involved
rustup.cli.log.log$module→rustup.process.Process
- Direction
- cli.log uses process, so a change to process can break cli.log, while a change to cli.log can't break process.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→2 dist.component.transaction uses dist.prefix✕
- Connections
- 2 pairs of types, where a type in dist.component.transaction uses a type in dist.prefix.
- The types involved
rustup.dist.component.transaction.ChangedItem→rustup.dist.prefix.InstallPrefixrustup.dist.component.transaction.Transaction→rustup.dist.prefix.InstallPrefix
- Direction
- dist.component.transaction uses dist.prefix, so a change to dist.prefix can break dist.component.transaction, while a change to dist.component.transaction can't break dist.prefix.
- Position
- Below the diagonal: dist.component.transaction uses a module listed above it, which is the healthy direction.
7→3 dist.component.transaction uses dist.temp✕
- Connections
- 1 pair of types, where a type in dist.component.transaction uses a type in dist.temp.
- The types involved
rustup.dist.component.transaction.Transaction→rustup.dist.temp.Context
- Direction
- dist.component.transaction uses dist.temp, so a change to dist.temp can break dist.component.transaction, while a change to dist.component.transaction can't break dist.temp.
- Position
- Below the diagonal: dist.component.transaction uses a module listed above it, which is the healthy direction.
8→26 dist.target_tuple uses dist part of a loop✕
- Connections
- 1 pair of types, where a type in dist.target_tuple uses a type in dist.
- The types involved
rustup.dist.target_tuple.PartialTargetTuple→rustup.dist.TargetTuple
- Direction
- dist.target_tuple uses dist, so a change to dist can break dist.target_tuple, while a change to dist.target_tuple can't break dist.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→4 process.terminal_source uses process.file_source.test_support✕
- Connections
- 1 pair of types, where a type in process.terminal_source uses a type in process.file_source.test_support.
- The types involved
rustup.process.terminal_source.ColorableTerminal→rustup.process.file_source.test_support.TestWriter
- Direction
- process.terminal_source uses process.file_source.test_support, so a change to process.file_source.test_support can break process.terminal_source, while a change to process.terminal_source can't break process.file_source.test_support.
- Position
- Below the diagonal: process.terminal_source uses a module listed above it, which is the healthy direction.
9→13 process.terminal_source uses process part of a loop✕
- Connections
- 1 pair of types, where a type in process.terminal_source uses a type in process.
- The types involved
rustup.process.terminal_source.ColorableTerminal→rustup.process.Process
- Direction
- process.terminal_source uses process, so a change to process can break process.terminal_source, while a change to process.terminal_source can't break process.
- 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→26 toolchain.names uses dist part of a loop✕
- Connections
- 5 pairs of types, where a type in toolchain.names uses a type in dist.
- The types involved
rustup.toolchain.names.PartialToolchainName→rustup.dist.PartialChannelToolchainNamerustup.toolchain.names.PartialToolchainName→rustup.dist.TargetTuplerustup.toolchain.names.PartialToolchainNameOrPath→rustup.dist.TargetTuplerustup.toolchain.names.ToolchainName→rustup.dist.ChannelToolchainNamerustup.toolchain.names.ToolchainNameOrPath→rustup.dist.ChannelToolchainName
- Direction
- toolchain.names uses dist, so a change to dist can break toolchain.names, while a change to toolchain.names can't break dist.
- 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→35 toolchain.names uses config part of a loop✕
- Connections
- 3 pairs of types, where a type in toolchain.names uses a type in config.
- The types involved
rustup.toolchain.names.Override→rustup.config.Cfgrustup.toolchain.names.ToolchainNameExt→rustup.config.Cfgrustup.toolchain.names.ToolchainNameOrPath→rustup.config.Cfg
- Direction
- toolchain.names uses config, so a change to config can break toolchain.names, while a change to toolchain.names can't break 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.
11→9 cli.markdown uses process.terminal_source✕
- Connections
- 3 pairs of types, where a type in cli.markdown uses a type in process.terminal_source.
- The types involved
rustup.cli.markdown.LineFormatter→rustup.process.terminal_source.ColorableTerminalrustup.cli.markdown.LineWrapper→rustup.process.terminal_source.ColorableTerminalrustup.cli.markdown.markdown$module→rustup.process.terminal_source.ColorableTerminal
- Direction
- cli.markdown uses process.terminal_source, so a change to process.terminal_source can break cli.markdown, while a change to cli.markdown can't break process.terminal_source.
- Position
- Below the diagonal: cli.markdown uses a module listed above it, which is the healthy direction.
12→2 dist.component.components uses dist.prefix✕
- Connections
- 1 pair of types, where a type in dist.component.components uses a type in dist.prefix.
- The types involved
rustup.dist.component.components.Components→rustup.dist.prefix.InstallPrefix
- Direction
- dist.component.components uses dist.prefix, so a change to dist.prefix can break dist.component.components, while a change to dist.component.components can't break dist.prefix.
- Position
- Below the diagonal: dist.component.components uses a module listed above it, which is the healthy direction.
12→7 dist.component.components uses dist.component.transaction✕
- Connections
- 3 pairs of types, where a type in dist.component.components uses a type in dist.component.transaction.
- The types involved
rustup.dist.component.components.Component→rustup.dist.component.transaction.Transactionrustup.dist.component.components.ComponentBuilder→rustup.dist.component.transaction.Transactionrustup.dist.component.components.Components→rustup.dist.component.transaction.Transaction
- Direction
- dist.component.components uses dist.component.transaction, so a change to dist.component.transaction can break dist.component.components, while a change to dist.component.components can't break dist.component.transaction.
- Position
- Below the diagonal: dist.component.components uses a module listed above it, which is the healthy direction.
13→1 process uses cli.job.imp✕
- Connections
- 1 pair of types, where a type in process uses a type in cli.job.imp.
- The types involved
rustup.process.TestProcess→rustup.cli.job.imp.Handle
- Direction
- process uses cli.job.imp, so a change to cli.job.imp can break process, while a change to process can't break cli.job.imp.
- Position
- Below the diagonal: process uses a module listed above it, which is the healthy direction.
13→6 process uses cli.log✕
- Connections
- 1 pair of types, where a type in process uses a type in cli.log.
- The types involved
rustup.process.TestProcess→rustup.cli.log.GlobalTelemetryGuard
- Direction
- process uses cli.log, so a change to cli.log can break process, while a change to process can't break cli.log.
- Position
- Below the diagonal: process uses a module listed above it, which is the healthy direction.
13→9 process uses process.terminal_source✕
- Connections
- 1 pair of types, where a type in process uses a type in process.terminal_source.
- The types involved
rustup.process.Process→rustup.process.terminal_source.ColorableTerminal
- Direction
- process uses process.terminal_source, so a change to process.terminal_source can break process, while a change to process can't break process.terminal_source.
- Position
- Below the diagonal: process uses a module listed above it, which is the healthy direction.
14→10 toolchain uses toolchain.names✕
- Connections
- 1 pair of types, where a type in toolchain uses a type in toolchain.names.
- The types involved
rustup.toolchain.Toolchain→rustup.toolchain.names.ToolchainNameOrPath
- Direction
- toolchain uses toolchain.names, so a change to toolchain.names can break toolchain, while a change to toolchain can't break toolchain.names.
- Position
- Below the diagonal: toolchain uses a module listed above it, which is the healthy direction.
14→20 toolchain uses toolchain.channels part of a loop✕
- Connections
- 1 pair of types, where a type in toolchain uses a type in toolchain.channels.
- The types involved
rustup.toolchain.Toolchain→rustup.toolchain.channels.ChannelToolchain
- Direction
- toolchain uses toolchain.channels, so a change to toolchain.channels can break toolchain, while a change to toolchain can't break toolchain.channels.
- 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.
14→35 toolchain uses config part of a loop✕
- Connections
- 2 pairs of types, where a type in toolchain uses a type in config.
- The types involved
rustup.toolchain.Toolchain→rustup.config.ActiveSourcerustup.toolchain.Toolchain→rustup.config.Cfg
- Direction
- toolchain uses config, so a change to config can break toolchain, while a change to toolchain can't break 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.
15→1 bin.rustup-init uses cli.job.imp✕
- Connections
- 1 pair of types, where a type in bin.rustup-init uses a type in cli.job.imp.
- The types involved
rustup.bin.rustup-init.rustup-init$module→rustup.cli.job.imp.Handle
- Direction
- bin.rustup-init uses cli.job.imp, so a change to cli.job.imp can break bin.rustup-init, while a change to bin.rustup-init can't break cli.job.imp.
- Position
- Below the diagonal: bin.rustup-init uses a module listed above it, which is the healthy direction.
15→13 bin.rustup-init uses process✕
- Connections
- 1 pair of types, where a type in bin.rustup-init uses a type in process.
- The types involved
rustup.bin.rustup-init.rustup-init$module→rustup.process.Process
- Direction
- bin.rustup-init uses process, so a change to process can break bin.rustup-init, while a change to bin.rustup-init can't break process.
- Position
- Below the diagonal: bin.rustup-init uses a module listed above it, which is the healthy direction.
16→13 cli.proxy_mode uses process✕
- Connections
- 1 pair of types, where a type in cli.proxy_mode uses a type in process.
- The types involved
rustup.cli.proxy_mode.proxy_mode$module→rustup.process.Process
- Direction
- cli.proxy_mode uses process, so a change to process can break cli.proxy_mode, while a change to cli.proxy_mode can't break process.
- Position
- Below the diagonal: cli.proxy_mode uses a module listed above it, which is the healthy direction.
17→13 cli.self_update.shell uses process✕
- Connections
- 10 pairs of types, where a type in cli.self_update.shell uses a type in process.
- The types involved
rustup.cli.self_update.shell.Bash→rustup.process.Processrustup.cli.self_update.shell.Fish→rustup.process.Processrustup.cli.self_update.shell.Nu→rustup.process.Processrustup.cli.self_update.shell.Posix→rustup.process.Processrustup.cli.self_update.shell.Pwsh→rustup.process.Processrustup.cli.self_update.shell.Tcsh→rustup.process.Processrustup.cli.self_update.shell.UnixShell→rustup.process.Processrustup.cli.self_update.shell.Xonsh→rustup.process.Processrustup.cli.self_update.shell.Zsh→rustup.process.Processrustup.cli.self_update.shell.shell$module→rustup.process.Process
- Direction
- cli.self_update.shell uses process, so a change to process can break cli.self_update.shell, while a change to cli.self_update.shell can't break process.
- Position
- Below the diagonal: cli.self_update.shell uses a module listed above it, which is the healthy direction.
18→12 dist.config uses dist.component.components✕
- Connections
- 1 pair of types, where a type in dist.config uses a type in dist.component.components.
- The types involved
rustup.dist.config.Config→rustup.dist.component.components.Component
- Direction
- dist.config uses dist.component.components, so a change to dist.component.components can break dist.config, while a change to dist.config can't break dist.component.components.
- Position
- Below the diagonal: dist.config uses a module listed above it, which is the healthy direction.
19→3 dist.download uses dist.temp✕
- Connections
- 1 pair of types, where a type in dist.download uses a type in dist.temp.
- The types involved
rustup.dist.download.DownloadCfg→rustup.dist.temp.Context
- Direction
- dist.download uses dist.temp, so a change to dist.temp can break dist.download, while a change to dist.download can't break dist.temp.
- Position
- Below the diagonal: dist.download uses a module listed above it, which is the healthy direction.
19→13 dist.download uses process✕
- Connections
- 2 pairs of types, where a type in dist.download uses a type in process.
- The types involved
rustup.dist.download.DownloadCfg→rustup.process.Processrustup.dist.download.DownloadTracker→rustup.process.Process
- Direction
- dist.download uses process, so a change to process can break dist.download, while a change to dist.download can't break process.
- Position
- Below the diagonal: dist.download uses a module listed above it, which is the healthy direction.
19→26 dist.download uses dist part of a loop✕
- Connections
- 1 pair of types, where a type in dist.download uses a type in dist.
- The types involved
rustup.dist.download.DownloadCfg→rustup.dist.ChannelToolchainName
- Direction
- dist.download uses dist, so a change to dist can break dist.download, while a change to dist.download can't break dist.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→35 dist.download uses config part of a loop✕
- Connections
- 1 pair of types, where a type in dist.download uses a type in config.
- The types involved
rustup.dist.download.DownloadCfg→rustup.config.Cfg
- Direction
- dist.download uses config, so a change to config can break dist.download, while a change to dist.download can't break 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.
20→14 toolchain.channels uses toolchain✕
- Connections
- 1 pair of types, where a type in toolchain.channels uses a type in toolchain.
- The types involved
rustup.toolchain.channels.ChannelToolchain→rustup.toolchain.Toolchain
- Direction
- toolchain.channels uses toolchain, so a change to toolchain can break toolchain.channels, while a change to toolchain.channels can't break toolchain.
- Position
- Below the diagonal: toolchain.channels uses a module listed above it, which is the healthy direction.
20→26 toolchain.channels uses dist part of a loop✕
- Connections
- 2 pairs of types, where a type in toolchain.channels uses a type in dist.
- The types involved
rustup.toolchain.channels.ChannelToolchain→rustup.dist.ChannelToolchainNamerustup.toolchain.channels.ChannelToolchain→rustup.dist.DistOptions
- Direction
- toolchain.channels uses dist, so a change to dist can break toolchain.channels, while a change to toolchain.channels can't break dist.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→35 toolchain.channels uses config part of a loop✕
- Connections
- 1 pair of types, where a type in toolchain.channels uses a type in config.
- The types involved
rustup.toolchain.channels.ChannelToolchain→rustup.config.Cfg
- Direction
- toolchain.channels uses config, so a change to config can break toolchain.channels, while a change to toolchain.channels can't break 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.
21→13 cli.self_update.stage uses process✕
- Connections
- 3 pairs of types, where a type in cli.self_update.stage uses a type in process.
- The types involved
rustup.cli.self_update.stage.Marker→rustup.process.Processrustup.cli.self_update.stage.SelfUpdateLock→rustup.process.Processrustup.cli.self_update.stage.stage$module→rustup.process.Process
- Direction
- cli.self_update.stage uses process, so a change to process can break cli.self_update.stage, while a change to cli.self_update.stage can't break process.
- Position
- Below the diagonal: cli.self_update.stage uses a module listed above it, which is the healthy direction.
21→19 cli.self_update.stage uses dist.download✕
- Connections
- 1 pair of types, where a type in cli.self_update.stage uses a type in dist.download.
- The types involved
rustup.cli.self_update.stage.SelfUpdateLock→rustup.dist.download.File
- Direction
- cli.self_update.stage uses dist.download, so a change to dist.download can break cli.self_update.stage, while a change to cli.self_update.stage can't break dist.download.
- Position
- Below the diagonal: cli.self_update.stage uses a module listed above it, which is the healthy direction.
22→12 dist.manifest uses dist.component.components✕
- Connections
- 4 pairs of types, where a type in dist.manifest uses a type in dist.component.components.
- The types involved
rustup.dist.manifest.ComponentStatus→rustup.dist.component.components.Componentrustup.dist.manifest.Manifest→rustup.dist.component.components.Componentrustup.dist.manifest.Target→rustup.dist.component.components.Componentrustup.dist.manifest.TargetedPackage→rustup.dist.component.components.Component
- Direction
- dist.manifest uses dist.component.components, so a change to dist.component.components can break dist.manifest, while a change to dist.manifest can't break dist.component.components.
- Position
- Below the diagonal: dist.manifest uses a module listed above it, which is the healthy direction.
22→18 dist.manifest uses dist.config✕
- Connections
- 1 pair of types, where a type in dist.manifest uses a type in dist.config.
- The types involved
rustup.dist.manifest.Manifest→rustup.dist.config.Config
- Direction
- dist.manifest uses dist.config, so a change to dist.config can break dist.manifest, while a change to dist.manifest can't break dist.config.
- Position
- Below the diagonal: dist.manifest uses a module listed above it, which is the healthy direction.
22→20 dist.manifest uses toolchain.channels✕
- Connections
- 1 pair of types, where a type in dist.manifest uses a type in toolchain.channels.
- The types involved
rustup.dist.manifest.Component→rustup.toolchain.channels.ChannelToolchain
- Direction
- dist.manifest uses toolchain.channels, so a change to toolchain.channels can break dist.manifest, while a change to dist.manifest can't break toolchain.channels.
- Position
- Below the diagonal: dist.manifest uses a module listed above it, which is the healthy direction.
22→26 dist.manifest uses dist part of a loop✕
- Connections
- 6 pairs of types, where a type in dist.manifest uses a type in dist.
- The types involved
rustup.dist.manifest.Component→rustup.dist.TargetTuplerustup.dist.manifest.Manifest→rustup.dist.ChannelToolchainNamerustup.dist.manifest.Manifest→rustup.dist.Profilerustup.dist.manifest.Manifest→rustup.dist.TargetTuplerustup.dist.manifest.Package→rustup.dist.TargetTuplerustup.dist.manifest.PackageTargets→rustup.dist.TargetTuple
- Direction
- dist.manifest uses dist, so a change to dist can break dist.manifest, while a change to dist.manifest can't break dist.
- 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→13 download uses process✕
- Connections
- 1 pair of types, where a type in download uses a type in process.
- The types involved
rustup.download.DownloadOptions→rustup.process.Process
- Direction
- download uses process, so a change to process can break download, while a change to download can't break process.
- Position
- Below the diagonal: download uses a module listed above it, which is the healthy direction.
23→19 download uses dist.download✕
- Connections
- 2 pairs of types, where a type in download uses a type in dist.download.
- The types involved
rustup.download.Download→rustup.dist.download.DownloadStatusrustup.download.Download→rustup.dist.download.File
- Direction
- download uses dist.download, so a change to dist.download can break download, while a change to download can't break dist.download.
- Position
- Below the diagonal: download uses a module listed above it, which is the healthy direction.
24→13 cli.self_update.unix uses process✕
- Connections
- 1 pair of types, where a type in cli.self_update.unix uses a type in process.
- The types involved
rustup.cli.self_update.unix.unix$module→rustup.process.Process
- Direction
- cli.self_update.unix uses process, so a change to process can break cli.self_update.unix, while a change to cli.self_update.unix can't break process.
- Position
- Below the diagonal: cli.self_update.unix uses a module listed above it, which is the healthy direction.
24→21 cli.self_update.unix uses cli.self_update.stage✕
- Connections
- 1 pair of types, where a type in cli.self_update.unix uses a type in cli.self_update.stage.
- The types involved
rustup.cli.self_update.unix.unix$module→rustup.cli.self_update.stage.PreparedUpdater
- Direction
- cli.self_update.unix uses cli.self_update.stage, so a change to cli.self_update.stage can break cli.self_update.unix, while a change to cli.self_update.unix can't break cli.self_update.stage.
- Position
- Below the diagonal: cli.self_update.unix uses a module listed above it, which is the healthy direction.
25→13 diskio uses process✕
- Connections
- 1 pair of types, where a type in diskio uses a type in process.
- The types involved
rustup.diskio.diskio$module→rustup.process.IoThreadCount
- Direction
- diskio uses process, so a change to process can break diskio, while a change to diskio can't break process.
- Position
- Below the diagonal: diskio uses a module listed above it, which is the healthy direction.
25→22 diskio uses dist.manifest✕
- Connections
- 1 pair of types, where a type in diskio uses a type in dist.manifest.
- The types involved
rustup.diskio.FileBuffer→rustup.dist.manifest.Target
- Direction
- diskio uses dist.manifest, so a change to dist.manifest can break diskio, while a change to diskio can't break dist.manifest.
- Position
- Below the diagonal: diskio uses a module listed above it, which is the healthy direction.
26→2 dist uses dist.prefix✕
- Connections
- 1 pair of types, where a type in dist uses a type in dist.prefix.
- The types involved
rustup.dist.DistOptions→rustup.dist.prefix.InstallPrefix
- Direction
- dist uses dist.prefix, so a change to dist.prefix can break dist, while a change to dist can't break dist.prefix.
- Position
- Below the diagonal: dist uses a module listed above it, which is the healthy direction.
26→8 dist uses dist.target_tuple✕
- Connections
- 1 pair of types, where a type in dist uses a type in dist.target_tuple.
- The types involved
rustup.dist.PartialChannelToolchainName→rustup.dist.target_tuple.PartialTargetTuple
- Direction
- dist uses dist.target_tuple, so a change to dist.target_tuple can break dist, while a change to dist can't break dist.target_tuple.
- Position
- Below the diagonal: dist uses a module listed above it, which is the healthy direction.
26→10 dist uses toolchain.names✕
- Connections
- 1 pair of types, where a type in dist uses a type in toolchain.names.
- The types involved
rustup.dist.ChannelToolchainName→rustup.toolchain.names.ToolchainNameExt
- Direction
- dist uses toolchain.names, so a change to toolchain.names can break dist, while a change to dist can't break toolchain.names.
- Position
- Below the diagonal: dist uses a module listed above it, which is the healthy direction.
26→13 dist uses process✕
- Connections
- 2 pairs of types, where a type in dist uses a type in process.
- The types involved
rustup.dist.ChannelToolchainName→rustup.process.Processrustup.dist.TargetTuple→rustup.process.Process
- Direction
- dist uses process, so a change to process can break dist, while a change to dist can't break process.
- Position
- Below the diagonal: dist uses a module listed above it, which is the healthy direction.
26→19 dist uses dist.download✕
- Connections
- 1 pair of types, where a type in dist uses a type in dist.download.
- The types involved
rustup.dist.DistOptions→rustup.dist.download.DownloadCfg
- Direction
- dist uses dist.download, so a change to dist.download can break dist, while a change to dist can't break dist.download.
- Position
- Below the diagonal: dist uses a module listed above it, which is the healthy direction.
26→20 dist uses toolchain.channels✕
- Connections
- 1 pair of types, where a type in dist uses a type in toolchain.channels.
- The types involved
rustup.dist.DistOptions→rustup.toolchain.channels.ChannelToolchain
- Direction
- dist uses toolchain.channels, so a change to toolchain.channels can break dist, while a change to dist can't break toolchain.channels.
- Position
- Below the diagonal: dist uses a module listed above it, which is the healthy direction.
26→22 dist uses dist.manifest✕
- Connections
- 2 pairs of types, where a type in dist uses a type in dist.manifest.
- The types involved
rustup.dist.DistOptions→rustup.dist.manifest.ManifestWithHashrustup.dist.TargetTuple→rustup.dist.manifest.Target
- Direction
- dist uses dist.manifest, so a change to dist.manifest can break dist, while a change to dist can't break dist.manifest.
- Position
- Below the diagonal: dist uses a module listed above it, which is the healthy direction.
26→35 dist uses config part of a loop✕
- Connections
- 1 pair of types, where a type in dist uses a type in config.
- The types involved
rustup.dist.DistOptions→rustup.config.Cfg
- Direction
- dist uses config, so a change to config can break dist, while a change to dist can't break 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.
27→10 cli.self_update uses toolchain.names✕
- Connections
- 1 pair of types, where a type in cli.self_update uses a type in toolchain.names.
- The types involved
rustup.cli.self_update.InstallOpts→rustup.toolchain.names.MaybeChannelToolchainName
- Direction
- cli.self_update uses toolchain.names, so a change to toolchain.names can break cli.self_update, while a change to cli.self_update can't break toolchain.names.
- Position
- Below the diagonal: cli.self_update uses a module listed above it, which is the healthy direction.
27→13 cli.self_update uses process✕
- Connections
- 2 pairs of types, where a type in cli.self_update uses a type in process.
- The types involved
rustup.cli.self_update.InstallOpts→rustup.process.Processrustup.cli.self_update.self_update$module→rustup.process.Process
- Direction
- cli.self_update uses process, so a change to process can break cli.self_update, while a change to cli.self_update can't break process.
- Position
- Below the diagonal: cli.self_update uses a module listed above it, which is the healthy direction.
27→19 cli.self_update uses dist.download✕
- Connections
- 2 pairs of types, where a type in cli.self_update uses a type in dist.download.
- The types involved
rustup.cli.self_update.SelfUpdateMode→rustup.dist.download.DownloadCfgrustup.cli.self_update.self_update$module→rustup.dist.download.DownloadCfg
- Direction
- cli.self_update uses dist.download, so a change to dist.download can break cli.self_update, while a change to cli.self_update can't break dist.download.
- Position
- Below the diagonal: cli.self_update uses a module listed above it, which is the healthy direction.
27→26 cli.self_update uses dist✕
- Connections
- 2 pairs of types, where a type in cli.self_update uses a type in dist.
- The types involved
rustup.cli.self_update.InstallOpts→rustup.dist.Profilerustup.cli.self_update.self_update$module→rustup.dist.ChannelToolchainName
- Direction
- cli.self_update uses dist, so a change to dist can break cli.self_update, while a change to cli.self_update can't break dist.
- Position
- Below the diagonal: cli.self_update uses a module listed above it, which is the healthy direction.
27→35 cli.self_update uses config part of a loop✕
- Connections
- 3 pairs of types, where a type in cli.self_update uses a type in config.
- The types involved
rustup.cli.self_update.InstallOpts→rustup.config.Cfgrustup.cli.self_update.SelfUpdateMode→rustup.config.Cfgrustup.cli.self_update.self_update$module→rustup.config.Cfg
- Direction
- cli.self_update uses config, so a change to config can break cli.self_update, while a change to cli.self_update can't break 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.
28→1 cli.setup_mode uses cli.job.imp✕
- Connections
- 1 pair of types, where a type in cli.setup_mode uses a type in cli.job.imp.
- The types involved
rustup.cli.setup_mode.setup_mode$module→rustup.cli.job.imp.Handle
- Direction
- cli.setup_mode uses cli.job.imp, so a change to cli.job.imp can break cli.setup_mode, while a change to cli.setup_mode can't break cli.job.imp.
- Position
- Below the diagonal: cli.setup_mode uses a module listed above it, which is the healthy direction.
28→10 cli.setup_mode uses toolchain.names✕
- Connections
- 1 pair of types, where a type in cli.setup_mode uses a type in toolchain.names.
- The types involved
rustup.cli.setup_mode.RustupInit→rustup.toolchain.names.MaybeChannelToolchainName
- Direction
- cli.setup_mode uses toolchain.names, so a change to toolchain.names can break cli.setup_mode, while a change to cli.setup_mode can't break toolchain.names.
- Position
- Below the diagonal: cli.setup_mode uses a module listed above it, which is the healthy direction.
28→13 cli.setup_mode uses process✕
- Connections
- 1 pair of types, where a type in cli.setup_mode uses a type in process.
- The types involved
rustup.cli.setup_mode.setup_mode$module→rustup.process.Process
- Direction
- cli.setup_mode uses process, so a change to process can break cli.setup_mode, while a change to cli.setup_mode can't break process.
- Position
- Below the diagonal: cli.setup_mode uses a module listed above it, which is the healthy direction.
28→26 cli.setup_mode uses dist✕
- Connections
- 1 pair of types, where a type in cli.setup_mode uses a type in dist.
- The types involved
rustup.cli.setup_mode.RustupInit→rustup.dist.Profile
- Direction
- cli.setup_mode uses dist, so a change to dist can break cli.setup_mode, while a change to cli.setup_mode can't break dist.
- Position
- Below the diagonal: cli.setup_mode uses a module listed above it, which is the healthy direction.
29→19 diskio.immediate uses dist.download✕
- Connections
- 1 pair of types, where a type in diskio.immediate uses a type in dist.download.
- The types involved
rustup.diskio.immediate.IncrementalFileWriter→rustup.dist.download.File
- Direction
- diskio.immediate uses dist.download, so a change to dist.download can break diskio.immediate, while a change to diskio.immediate can't break dist.download.
- Position
- Below the diagonal: diskio.immediate uses a module listed above it, which is the healthy direction.
29→25 diskio.immediate uses diskio✕
- Connections
- 7 pairs of types, where a type in diskio.immediate uses a type in diskio.
- The types involved
rustup.diskio.immediate.FileState→rustup.diskio.Itemrustup.diskio.immediate.ImmediateUnpacker→rustup.diskio.Executorrustup.diskio.immediate.ImmediateUnpacker→rustup.diskio.FileBufferrustup.diskio.immediate.ImmediateUnpacker→rustup.diskio.IncrementalFileStaterustup.diskio.immediate.ImmediateUnpacker→rustup.diskio.Itemrustup.diskio.immediate.IncrementalFileWriter→rustup.diskio.ChunkWriterrustup.diskio.immediate.IncrementalFileWriter→rustup.diskio.FileBuffer
- Direction
- diskio.immediate uses diskio, so a change to diskio can break diskio.immediate, while a change to diskio.immediate can't break diskio.
- Position
- Below the diagonal: diskio.immediate uses a module listed above it, which is the healthy direction.
30→25 diskio.threaded uses diskio✕
- Connections
- 8 pairs of types, where a type in diskio.threaded uses a type in diskio.
- The types involved
rustup.diskio.threaded.JoinIterator→rustup.diskio.CompletedIorustup.diskio.threaded.SubmitIterator→rustup.diskio.CompletedIorustup.diskio.threaded.SubmitIterator→rustup.diskio.Itemrustup.diskio.threaded.Threaded→rustup.diskio.CompletedIorustup.diskio.threaded.Threaded→rustup.diskio.Executorrustup.diskio.threaded.Threaded→rustup.diskio.FileBufferrustup.diskio.threaded.Threaded→rustup.diskio.IncrementalFileStaterustup.diskio.threaded.Threaded→rustup.diskio.Item
- Direction
- diskio.threaded uses diskio, so a change to diskio can break diskio.threaded, while a change to diskio.threaded can't break diskio.
- Position
- Below the diagonal: diskio.threaded uses a module listed above it, which is the healthy direction.
31→3 dist.component.package uses dist.temp✕
- Connections
- 1 pair of types, where a type in dist.component.package uses a type in dist.temp.
- The types involved
rustup.dist.component.package.DirectoryPackage→rustup.dist.temp.Dir
- Direction
- dist.component.package uses dist.temp, so a change to dist.temp can break dist.component.package, while a change to dist.component.package can't break dist.temp.
- Position
- Below the diagonal: dist.component.package uses a module listed above it, which is the healthy direction.
31→7 dist.component.package uses dist.component.transaction✕
- Connections
- 1 pair of types, where a type in dist.component.package uses a type in dist.component.transaction.
- The types involved
rustup.dist.component.package.DirectoryPackage→rustup.dist.component.transaction.Transaction
- Direction
- dist.component.package uses dist.component.transaction, so a change to dist.component.transaction can break dist.component.package, while a change to dist.component.package can't break dist.component.transaction.
- Position
- Below the diagonal: dist.component.package uses a module listed above it, which is the healthy direction.
31→12 dist.component.package uses dist.component.components✕
- Connections
- 1 pair of types, where a type in dist.component.package uses a type in dist.component.components.
- The types involved
rustup.dist.component.package.DirectoryPackage→rustup.dist.component.components.Components
- Direction
- dist.component.package uses dist.component.components, so a change to dist.component.components can break dist.component.package, while a change to dist.component.package can't break dist.component.components.
- Position
- Below the diagonal: dist.component.package uses a module listed above it, which is the healthy direction.
31→22 dist.component.package uses dist.manifest✕
- Connections
- 1 pair of types, where a type in dist.component.package uses a type in dist.manifest.
- The types involved
rustup.dist.component.package.DirectoryPackage→rustup.dist.manifest.CompressionKind
- Direction
- dist.component.package uses dist.manifest, so a change to dist.manifest can break dist.component.package, while a change to dist.component.package can't break dist.manifest.
- Position
- Below the diagonal: dist.component.package uses a module listed above it, which is the healthy direction.
31→25 dist.component.package uses diskio✕
- Connections
- 1 pair of types, where a type in dist.component.package uses a type in diskio.
- The types involved
rustup.dist.component.package.package$module→rustup.diskio.CompletedIo
- Direction
- dist.component.package uses diskio, so a change to diskio can break dist.component.package, while a change to dist.component.package can't break diskio.
- Position
- Below the diagonal: dist.component.package uses a module listed above it, which is the healthy direction.
32→2 dist.manifestation uses dist.prefix✕
- Connections
- 1 pair of types, where a type in dist.manifestation uses a type in dist.prefix.
- The types involved
rustup.dist.manifestation.Manifestation→rustup.dist.prefix.InstallPrefix
- Direction
- dist.manifestation uses dist.prefix, so a change to dist.prefix can break dist.manifestation, while a change to dist.manifestation can't break dist.prefix.
- Position
- Below the diagonal: dist.manifestation uses a module listed above it, which is the healthy direction.
32→3 dist.manifestation uses dist.temp✕
- Connections
- 2 pairs of types, where a type in dist.manifestation uses a type in dist.temp.
- The types involved
rustup.dist.manifestation.ComponentInstall→rustup.dist.temp.Dirrustup.dist.manifestation.InstallEvents→rustup.dist.temp.Context
- Direction
- dist.manifestation uses dist.temp, so a change to dist.temp can break dist.manifestation, while a change to dist.manifestation can't break dist.temp.
- Position
- Below the diagonal: dist.manifestation uses a module listed above it, which is the healthy direction.
32→7 dist.manifestation uses dist.component.transaction✕
- Connections
- 3 pairs of types, where a type in dist.manifestation uses a type in dist.component.transaction.
- The types involved
rustup.dist.manifestation.ComponentInstall→rustup.dist.component.transaction.Transactionrustup.dist.manifestation.InstallEvents→rustup.dist.component.transaction.Transactionrustup.dist.manifestation.Manifestation→rustup.dist.component.transaction.Transaction
- Direction
- dist.manifestation uses dist.component.transaction, so a change to dist.component.transaction can break dist.manifestation, while a change to dist.manifestation can't break dist.component.transaction.
- Position
- Below the diagonal: dist.manifestation uses a module listed above it, which is the healthy direction.
32→12 dist.manifestation uses dist.component.components✕
- Connections
- 6 pairs of types, where a type in dist.manifestation uses a type in dist.component.components.
- The types involved
rustup.dist.manifestation.Changes→rustup.dist.component.components.Componentrustup.dist.manifestation.ComponentBinary→rustup.dist.component.components.Componentrustup.dist.manifestation.ComponentInstall→rustup.dist.component.components.Componentrustup.dist.manifestation.Manifestation→rustup.dist.component.components.Componentrustup.dist.manifestation.Manifestation→rustup.dist.component.components.Componentsrustup.dist.manifestation.Update→rustup.dist.component.components.Component
- Direction
- dist.manifestation uses dist.component.components, so a change to dist.component.components can break dist.manifestation, while a change to dist.manifestation can't break dist.component.components.
- Position
- Below the diagonal: dist.manifestation uses a module listed above it, which is the healthy direction.
32→18 dist.manifestation uses dist.config✕
- Connections
- 3 pairs of types, where a type in dist.manifestation uses a type in dist.config.
- The types involved
rustup.dist.manifestation.Changes→rustup.dist.config.Configrustup.dist.manifestation.Manifestation→rustup.dist.config.Configrustup.dist.manifestation.Update→rustup.dist.config.Config
- Direction
- dist.manifestation uses dist.config, so a change to dist.config can break dist.manifestation, while a change to dist.manifestation can't break dist.config.
- Position
- Below the diagonal: dist.manifestation uses a module listed above it, which is the healthy direction.
32→19 dist.manifestation uses dist.download✕
- Connections
- 5 pairs of types, where a type in dist.manifestation uses a type in dist.download.
- The types involved
rustup.dist.manifestation.ComponentBinary→rustup.dist.download.DownloadCfgrustup.dist.manifestation.ComponentBinary→rustup.dist.download.DownloadStatusrustup.dist.manifestation.ComponentInstall→rustup.dist.download.DownloadStatusrustup.dist.manifestation.ComponentInstall→rustup.dist.download.Filerustup.dist.manifestation.Manifestation→rustup.dist.download.DownloadCfg
- Direction
- dist.manifestation uses dist.download, so a change to dist.download can break dist.manifestation, while a change to dist.manifestation can't break dist.download.
- Position
- Below the diagonal: dist.manifestation uses a module listed above it, which is the healthy direction.
32→22 dist.manifestation uses dist.manifest✕
- Connections
- 5 pairs of types, where a type in dist.manifestation uses a type in dist.manifest.
- The types involved
rustup.dist.manifestation.ComponentBinary→rustup.dist.manifest.HashedBinaryrustup.dist.manifestation.ComponentBinary→rustup.dist.manifest.Manifestrustup.dist.manifestation.ComponentInstall→rustup.dist.manifest.CompressionKindrustup.dist.manifestation.Manifestation→rustup.dist.manifest.Manifestrustup.dist.manifestation.Update→rustup.dist.manifest.Manifest
- Direction
- dist.manifestation uses dist.manifest, so a change to dist.manifest can break dist.manifestation, while a change to dist.manifestation can't break dist.manifest.
- Position
- Below the diagonal: dist.manifestation uses a module listed above it, which is the healthy direction.
32→26 dist.manifestation uses dist✕
- Connections
- 4 pairs of types, where a type in dist.manifestation uses a type in dist.
- The types involved
rustup.dist.manifestation.ComponentBinary→rustup.dist.TargetTuplerustup.dist.manifestation.Manifestation→rustup.dist.ChannelToolchainNamerustup.dist.manifestation.Manifestation→rustup.dist.TargetTuplerustup.dist.manifestation.Update→rustup.dist.ChannelToolchainName
- Direction
- dist.manifestation uses dist, so a change to dist can break dist.manifestation, while a change to dist.manifestation can't break dist.
- Position
- Below the diagonal: dist.manifestation uses a module listed above it, which is the healthy direction.
33→9 cli.self_update.windows uses process.terminal_source✕
- Connections
- 1 pair of types, where a type in cli.self_update.windows uses a type in process.terminal_source.
- The types involved
rustup.cli.self_update.windows.windows$module→rustup.process.terminal_source.ColorableTerminal
- Direction
- cli.self_update.windows uses process.terminal_source, so a change to process.terminal_source can break cli.self_update.windows, while a change to cli.self_update.windows can't break process.terminal_source.
- Position
- Below the diagonal: cli.self_update.windows uses a module listed above it, which is the healthy direction.
33→13 cli.self_update.windows uses process✕
- Connections
- 1 pair of types, where a type in cli.self_update.windows uses a type in process.
- The types involved
rustup.cli.self_update.windows.windows$module→rustup.process.Process
- Direction
- cli.self_update.windows uses process, so a change to process can break cli.self_update.windows, while a change to cli.self_update.windows can't break process.
- Position
- Below the diagonal: cli.self_update.windows uses a module listed above it, which is the healthy direction.
33→21 cli.self_update.windows uses cli.self_update.stage✕
- Connections
- 1 pair of types, where a type in cli.self_update.windows uses a type in cli.self_update.stage.
- The types involved
rustup.cli.self_update.windows.windows$module→rustup.cli.self_update.stage.PreparedUpdater
- Direction
- cli.self_update.windows uses cli.self_update.stage, so a change to cli.self_update.stage can break cli.self_update.windows, while a change to cli.self_update.windows can't break cli.self_update.stage.
- Position
- Below the diagonal: cli.self_update.windows uses a module listed above it, which is the healthy direction.
33→27 cli.self_update.windows uses cli.self_update✕
- Connections
- 1 pair of types, where a type in cli.self_update.windows uses a type in cli.self_update.
- The types involved
rustup.cli.self_update.windows.windows$module→rustup.cli.self_update.InstallOpts
- Direction
- cli.self_update.windows uses cli.self_update, so a change to cli.self_update can break cli.self_update.windows, while a change to cli.self_update.windows can't break cli.self_update.
- Position
- Below the diagonal: cli.self_update.windows uses a module listed above it, which is the healthy direction.
34→1 settings uses cli.job.imp✕
- Connections
- 1 pair of types, where a type in settings uses a type in cli.job.imp.
- The types involved
rustup.settings.settings$module→rustup.cli.job.imp.Handle
- Direction
- settings uses cli.job.imp, so a change to cli.job.imp can break settings, while a change to settings can't break cli.job.imp.
- Position
- Below the diagonal: settings uses a module listed above it, which is the healthy direction.
34→26 settings uses dist✕
- Connections
- 2 pairs of types, where a type in settings uses a type in dist.
- The types involved
rustup.settings.Settings→rustup.dist.Profilerustup.settings.Settings→rustup.dist.Switch
- Direction
- settings uses dist, so a change to dist can break settings, while a change to settings can't break dist.
- Position
- Below the diagonal: settings uses a module listed above it, which is the healthy direction.
34→27 settings uses cli.self_update✕
- Connections
- 1 pair of types, where a type in settings uses a type in cli.self_update.
- The types involved
rustup.settings.Settings→rustup.cli.self_update.SelfUpdateMode
- Direction
- settings uses cli.self_update, so a change to cli.self_update can break settings, while a change to settings can't break cli.self_update.
- Position
- Below the diagonal: settings uses a module listed above it, which is the healthy direction.
35→10 config uses toolchain.names✕
- Connections
- 4 pairs of types, where a type in config uses a type in toolchain.names.
- The types involved
rustup.config.Cfg→rustup.toolchain.names.Overriderustup.config.Cfg→rustup.toolchain.names.PartialToolchainNamerustup.config.OverrideCfg→rustup.toolchain.names.PartialToolchainNamerustup.config.OverrideCfg→rustup.toolchain.names.PartialToolchainNameOrPath
- Direction
- config uses toolchain.names, so a change to toolchain.names can break config, while a change to config can't break toolchain.names.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
35→13 config uses process✕
- Connections
- 3 pairs of types, where a type in config uses a type in process.
- The types involved
rustup.config.Cfg→rustup.process.Processrustup.config.EnsureInstalled→rustup.process.Processrustup.config.config$module→rustup.process.Process
- Direction
- config uses process, so a change to process can break config, while a change to config can't break process.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
35→22 config uses dist.manifest✕
- Connections
- 1 pair of types, where a type in config uses a type in dist.manifest.
- The types involved
rustup.config.EnsureInstalled→rustup.dist.manifest.Target
- Direction
- config uses dist.manifest, so a change to dist.manifest can break config, while a change to config can't break dist.manifest.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
35→26 config uses dist✕
- Connections
- 5 pairs of types, where a type in config uses a type in dist.
- The types involved
rustup.config.Cfg→rustup.dist.ChannelToolchainNamerustup.config.Cfg→rustup.dist.Profilerustup.config.Cfg→rustup.dist.Switchrustup.config.OverrideCfg→rustup.dist.TargetTuplerustup.config.config$module→rustup.dist.TargetTuple
- Direction
- config uses dist, so a change to dist can break config, while a change to config can't break dist.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
35→27 config uses cli.self_update✕
- Connections
- 1 pair of types, where a type in config uses a type in cli.self_update.
- The types involved
rustup.config.Cfg→rustup.cli.self_update.SelfUpdateMode
- Direction
- config uses cli.self_update, so a change to cli.self_update can break config, while a change to config can't break cli.self_update.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
35→32 config uses dist.manifestation✕
- Connections
- 1 pair of types, where a type in config uses a type in dist.manifestation.
- The types involved
rustup.config.EnsureInstalled→rustup.dist.manifestation.UpdateStatus
- Direction
- config uses dist.manifestation, so a change to dist.manifestation can break config, while a change to config can't break dist.manifestation.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
35→34 config uses settings✕
- Connections
- 3 pairs of types, where a type in config uses a type in settings.
- The types involved
rustup.config.Cfg→rustup.settings.Settingsrustup.config.Cfg→rustup.settings.SettingsFilerustup.config.config$module→rustup.settings.Settings
- Direction
- config uses settings, so a change to settings can break config, while a change to config can't break settings.
- Position
- Below the diagonal: config uses a module listed above it, which is the healthy direction.
36→1 cli.common uses cli.job.imp✕
- Connections
- 1 pair of types, where a type in cli.common uses a type in cli.job.imp.
- The types involved
rustup.cli.common.common$module→rustup.cli.job.imp.Handle
- Direction
- cli.common uses cli.job.imp, so a change to cli.job.imp can break cli.common, while a change to cli.common can't break cli.job.imp.
- Position
- Below the diagonal: cli.common uses a module listed above it, which is the healthy direction.
36→13 cli.common uses process✕
- Connections
- 1 pair of types, where a type in cli.common uses a type in process.
- The types involved
rustup.cli.common.common$module→rustup.process.Process
- Direction
- cli.common uses process, so a change to process can break cli.common, while a change to cli.common can't break process.
- Position
- Below the diagonal: cli.common uses a module listed above it, which is the healthy direction.
36→26 cli.common uses dist✕
- Connections
- 1 pair of types, where a type in cli.common uses a type in dist.
- The types involved
rustup.cli.common.common$module→rustup.dist.TargetTuple
- Direction
- cli.common uses dist, so a change to dist can break cli.common, while a change to cli.common can't break dist.
- Position
- Below the diagonal: cli.common uses a module listed above it, which is the healthy direction.
36→35 cli.common uses config✕
- Connections
- 1 pair of types, where a type in cli.common uses a type in config.
- The types involved
rustup.cli.common.common$module→rustup.config.Cfg
- Direction
- cli.common uses config, so a change to config can break cli.common, while a change to cli.common can't break config.
- Position
- Below the diagonal: cli.common uses a module listed above it, which is the healthy direction.
37→35 cli.completions uses config✕
- Connections
- 1 pair of types, where a type in cli.completions uses a type in config.
- The types involved
rustup.cli.completions.completions$module→rustup.config.Cfg
- Direction
- cli.completions uses config, so a change to config can break cli.completions, while a change to cli.completions can't break config.
- Position
- Below the diagonal: cli.completions uses a module listed above it, which is the healthy direction.
38→26 cli.docs uses dist✕
- Connections
- 1 pair of types, where a type in cli.docs uses a type in dist.
- The types involved
rustup.cli.docs.docs$module→rustup.dist.PartialChannelToolchainName
- Direction
- cli.docs uses dist, so a change to dist can break cli.docs, while a change to cli.docs can't break dist.
- Position
- Below the diagonal: cli.docs uses a module listed above it, which is the healthy direction.
38→35 cli.docs uses config✕
- Connections
- 1 pair of types, where a type in cli.docs uses a type in config.
- The types involved
rustup.cli.docs.docs$module→rustup.config.Cfg
- Direction
- cli.docs uses config, so a change to config can break cli.docs, while a change to cli.docs can't break config.
- Position
- Below the diagonal: cli.docs uses a module listed above it, which is the healthy direction.
39→1 cli.rustup_mode uses cli.job.imp✕
- Connections
- 1 pair of types, where a type in cli.rustup_mode uses a type in cli.job.imp.
- The types involved
rustup.cli.rustup_mode.rustup_mode$module→rustup.cli.job.imp.Handle
- Direction
- cli.rustup_mode uses cli.job.imp, so a change to cli.job.imp can break cli.rustup_mode, while a change to cli.rustup_mode can't break cli.job.imp.
- Position
- Below the diagonal: cli.rustup_mode uses a module listed above it, which is the healthy direction.
39→10 cli.rustup_mode uses toolchain.names✕
- Connections
- 6 pairs of types, where a type in cli.rustup_mode uses a type in toolchain.names.
- The types involved
rustup.cli.rustup_mode.Rustup→rustup.toolchain.names.Overriderustup.cli.rustup_mode.UninstallOpts→rustup.toolchain.names.PartialToolchainNamerustup.cli.rustup_mode.rustup_mode$module→rustup.toolchain.names.CustomToolchainNamerustup.cli.rustup_mode.rustup_mode$module→rustup.toolchain.names.Overriderustup.cli.rustup_mode.rustup_mode$module→rustup.toolchain.names.PartialToolchainNamerustup.cli.rustup_mode.rustup_mode$module→rustup.toolchain.names.PartialToolchainNameOrPath
- Direction
- cli.rustup_mode uses toolchain.names, so a change to toolchain.names can break cli.rustup_mode, while a change to cli.rustup_mode can't break toolchain.names.
- Position
- Below the diagonal: cli.rustup_mode uses a module listed above it, which is the healthy direction.
39→13 cli.rustup_mode uses process✕
- Connections
- 1 pair of types, where a type in cli.rustup_mode uses a type in process.
- The types involved
rustup.cli.rustup_mode.rustup_mode$module→rustup.process.Process
- Direction
- cli.rustup_mode uses process, so a change to process can break cli.rustup_mode, while a change to cli.rustup_mode can't break process.
- Position
- Below the diagonal: cli.rustup_mode uses a module listed above it, which is the healthy direction.
39→20 cli.rustup_mode uses toolchain.channels✕
- Connections
- 1 pair of types, where a type in cli.rustup_mode uses a type in toolchain.channels.
- The types involved
rustup.cli.rustup_mode.rustup_mode$module→rustup.toolchain.channels.ChannelToolchain
- Direction
- cli.rustup_mode uses toolchain.channels, so a change to toolchain.channels can break cli.rustup_mode, while a change to cli.rustup_mode can't break toolchain.channels.
- Position
- Below the diagonal: cli.rustup_mode uses a module listed above it, which is the healthy direction.
39→26 cli.rustup_mode uses dist✕
- Connections
- 4 pairs of types, where a type in cli.rustup_mode uses a type in dist.
- The types involved
rustup.cli.rustup_mode.UpdateOpts→rustup.dist.PartialChannelToolchainNamerustup.cli.rustup_mode.UpdateOpts→rustup.dist.Profilerustup.cli.rustup_mode.rustup_mode$module→rustup.dist.PartialChannelToolchainNamerustup.cli.rustup_mode.rustup_mode$module→rustup.dist.TargetTuple
- Direction
- cli.rustup_mode uses dist, so a change to dist can break cli.rustup_mode, while a change to cli.rustup_mode can't break dist.
- Position
- Below the diagonal: cli.rustup_mode uses a module listed above it, which is the healthy direction.
39→27 cli.rustup_mode uses cli.self_update✕
- Connections
- 1 pair of types, where a type in cli.rustup_mode uses a type in cli.self_update.
- The types involved
rustup.cli.rustup_mode.rustup_mode$module→rustup.cli.self_update.SelfUpdateMode
- Direction
- cli.rustup_mode uses cli.self_update, so a change to cli.self_update can break cli.rustup_mode, while a change to cli.rustup_mode can't break cli.self_update.
- Position
- Below the diagonal: cli.rustup_mode uses a module listed above it, which is the healthy direction.
39→35 cli.rustup_mode uses config✕
- Connections
- 1 pair of types, where a type in cli.rustup_mode uses a type in config.
- The types involved
rustup.cli.rustup_mode.rustup_mode$module→rustup.config.Cfg
- Direction
- cli.rustup_mode uses config, so a change to config can break cli.rustup_mode, while a change to cli.rustup_mode can't break config.
- Position
- Below the diagonal: cli.rustup_mode uses a module listed above it, which is the healthy direction.
40→12 errors uses dist.component.components✕
- Connections
- 3 pairs of types, where a type in errors uses a type in dist.component.components.
- The types involved
rustup.errors.ComponentSuggestion→rustup.dist.component.components.Componentrustup.errors.TargetSuggestion→rustup.dist.component.components.Componentrustup.errors.errors$module→rustup.dist.component.components.Component
- Direction
- errors uses dist.component.components, so a change to dist.component.components can break errors, while a change to errors can't break dist.component.components.
- Position
- Below the diagonal: errors uses a module listed above it, which is the healthy direction.
40→22 errors uses dist.manifest✕
- Connections
- 3 pairs of types, where a type in errors uses a type in dist.manifest.
- The types involved
rustup.errors.ComponentSuggestion→rustup.dist.manifest.Manifestrustup.errors.TargetSuggestion→rustup.dist.manifest.Manifestrustup.errors.errors$module→rustup.dist.manifest.Manifest
- Direction
- errors uses dist.manifest, so a change to dist.manifest can break errors, while a change to errors can't break dist.manifest.
- Position
- Below the diagonal: errors uses a module listed above it, which is the healthy direction.
40→26 errors uses dist✕
- Connections
- 4 pairs of types, where a type in errors uses a type in dist.
- The types involved
rustup.errors.ComponentSuggestion→rustup.dist.ChannelToolchainNamerustup.errors.TargetSuggestion→rustup.dist.ChannelToolchainNamerustup.errors.TargetSuggestion→rustup.dist.TargetTuplerustup.errors.errors$module→rustup.dist.ChannelToolchainName
- Direction
- errors uses dist, so a change to dist can break errors, while a change to errors can't break dist.
- Position
- Below the diagonal: errors uses a module listed above it, which is the healthy direction.
40→35 errors uses config✕
- Connections
- 2 pairs of types, where a type in errors uses a type in config.
- The types involved
rustup.errors.ComponentSuggestion→rustup.config.Cfgrustup.errors.TargetSuggestion→rustup.config.Cfg
- Direction
- errors uses config, so a change to config can break errors, while a change to errors can't break config.
- Position
- Below the diagonal: errors uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 77 | High / Critical |
| A07:2025 — Authentication Failures | 7 | High / Critical |
| A05:2025 — Injection | 7 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | Medium |
Roadmap
Top priorities: Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only; Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with rustup-init.rs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +6.2 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with rustup-init.rs. | +6.2 pts | Low | ADR Quality |
| Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). | +5.4 pts | Low | Static Analysis (SAST) |
| Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only. | +10.0 pts | Medium | Web-Security Posture |
| 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. | +5.7 pts | Medium | Architecture documentation |
| Resolve the 48 High IaC finding(s) in IaC & Container Security — start with REDACTED (48). | +4.6 pts | Medium | IaC & Container Security |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.9 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.9 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | 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 45 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 — 45 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, 241 of 255 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
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 29 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — 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. `(repository root)` (16499 LoC, 110 module-visible types across 13 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- 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. Ci/docker/aarch64-unknown-linux-gnu/Dockerfile carries no `FROM` instruction, so it declares no build stage and every REDACTED 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 28 of 29 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.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 REDACTED (REDACTED). docker build failed (exit 1) — 3 | # Building `aws-lc-rs` for NetBSD on Linux depends on `gcc-multilib`, `libclang` and `bindgen`. -------------------- ERROR: failed to solve: rust-x86_64-unknown-netbsd: failed to resolve source metadata for docker.io/library/rust-x86_64-unknown-netbsd:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed; 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 this repository's Python, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — 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 this repository's Python, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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'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.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X4 Structured logging — 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. 43 further occurrence(s) are not listed individually; the score already reflects all 83.
- 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 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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- 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.
- 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
10 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was rustup::cli::rustup_mode::main at 47. A further 4 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 TargetTuple::from_host::inner at 34 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/cli/markdown.rs (LineFormatter::start_tag at 21), src/cli/self_update/windows.rs (VsInstallError::fmt at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 9 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with rustup::cli::rustup_mode::main (cyclomatic 47), rustup.detect_platform (cyclomatic 39), DistOptions::install_into (cyclomatic 27). — 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 9 together lifts Cyclomatic Complexity from 8.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
21 method(s) exceeded the cognitive complexity threshold of 15; the worst was rustup::dist::component::package::unpack_without_first_dir at 54.
What to do
- Bring the 20 bodies over 15 down to 15 or less in Cognitive Complexity — start with rustup::dist::component::package::unpack_without_first_dir (cognitive 54), rustup.detect_platform (cognitive 46), DistOptions::install_into (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 20 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
12 god class(es) detected.
What to do
- Resolve the 6 FileTooLong finding(s) in God Classes — start with rustup_mode.rs, config.rs, self_update.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with rustup_mode.rs, package.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with manifestation.rs, mod.rs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
8 duplicated block group(s) detected. 2.7 % of the production lines (436 of 16,237) are in a reported copy. A further 12 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 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with rustup_mode.rs, manifestation.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with unix.rs, self_update.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with self_update.rs, common.rs. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 61 classes have LCOM4 above 3.
D12 · Dependency Hygiene
3 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 332 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's Cargo.lock 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/cli/rustup_mode.rs (40×47=1880); src/dist/mod.rs (21×27=567); src/dist/manifestation.rs (8×22=176) Repeated repair below the complexity floor: src/settings.rs (3 of 5 changes were fixes)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with rustup_mode.rs, mod.rs, manifestation.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with settings.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/cli/completions.rs. Counted over 38 of the 46 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
37 deducted task-comment markers across 16237 LoC (0.2/KLoC) → score 9.6. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 16 TodoComment finding(s) in Explicit Debt — start with mod.rs (4), shell.rs (3), cli_exact.rs. — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 10 FixmeComment finding(s) in Explicit Debt — start with cli_exact.rs (3), cli_self_upd.rs, command.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 7 HackComment finding(s) in Explicit Debt — start with cli_paths.rs, config.rs, process.rs. — One of this dimension's main actionable groups (7 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 35 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
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 rustup-init.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
6 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 recommendation-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. semgrep hit a parse error in 1 file(s) — `REDACTED` (line 801) — 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 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
77 finding(s): 0 critical, 48 high, 29 medium, 0 low.
What to do
- Resolve the 48 High IaC finding(s) in IaC & Container Security — start with REDACTED (48). — One of this dimension's main actionable groups (48 issue-level).
- Resolve the 29 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (29). — One of this dimension's main actionable groups (29 warning-level).
D34 · Knowledge Freshness
1 of 38 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is ci/sync-dist.py. Counted over 38 of the 46 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: rustup-init.rs↔notify.rs 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with rustup-init.rs. — One of this dimension's main actionable groups (1 issue-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-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.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — www/index.html:1
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
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
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `.serve_connection(` (src/cli/docs.rs:318).
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `.serve_connection(` (src/cli/docs.rs:318).
- No handler of this repository's Rust server answers 400, 413 or 422 (`StatusCode::BAD_REQUEST`, `HttpResponse::BadRequest()`, `Status::BadRequest`, tonic `Status::invalid_argument`), and nothing declares validation — no `validator`/`garde` derive, no body limit (`DefaultBodyLimit::max`, `RequestBodyLimitLayer`, `JsonConfig::default().limit(…)`, Rocket `Limits`) — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: `.serve_connection(` (src/cli/docs.rs:318).
What to do
- Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
- Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body) before a handler acts on it: derive `validator::Validate` (or `garde::Validate`) on the request types and reject with `StatusCode::BAD_REQUEST`, and cap bodies with `DefaultBodyLimit::max`/`RequestBodyLimitLayer` or actix's `JsonConfig::default().limit(…)`.
X1 · Async correctness
X21 · Side-effecting pattern guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn!` at line 172 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:172
- `debug!` at line 365 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:365
- `info!` at line 443 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:443
- `info!` at line 456 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:456
- `info!` at line 465 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:465
- `info!` at line 474 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:474
- `info!` at line 483 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:483
- `info!` at line 550 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:550
- `info!` at line 554 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:554
- `warn!` at line 724 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:724
- `debug!` at line 923 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:923
- `info!` at line 946 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:946
- `warn!` at line 1013 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:1013
- `warn!` at line 1025 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:1025
- `warn!` at line 1037 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:1037
- `trace!` at line 1169 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:1169
- `trace!` at line 1178 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:1178
- `debug!` at line 45 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/install.rs:45
- `debug!` at line 55 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/install.rs:55
- `debug!` at line 56 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/install.rs:56
- `debug!` at line 63 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/install.rs:63
- `debug!` at line 98 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/install.rs:98
- `info!` at line 126 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/settings.rs:126
- `info!` at line 542 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/toolchain.rs:542
- `info!` at line 560 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/toolchain.rs:560
- `info!` at line 565 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/toolchain.rs:565
- `info!` at line 577 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/toolchain.rs:577
- `warn!` at line 168 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/utils/mod.rs:168
- `debug!` at line 434 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/utils/mod.rs:434
- `debug!` at line 444 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/utils/mod.rs:444
- `warn!` at line 448 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/utils/mod.rs:448
- `info!` at line 495 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/utils/mod.rs:495
- `warn!` at line 523 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/utils/mod.rs:523
- `debug!` at line 477 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/diskio/mod.rs:477
- `error!` at line 500 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/diskio/mod.rs:500
- `warn!` at line 508 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/diskio/mod.rs:508
- `warn!` at line 514 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/diskio/mod.rs:514
- `debug!` at line 258 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/diskio/threaded.rs:258
- `error!` at line 517 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/cli/common.rs:517
- `error!` at line 519 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/cli/common.rs:519
What to do
- Interpolated log message defeats structured logging
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 97% | Exemplary | Solid. |
| Maturity | 54% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 78% | Strong | Solid. |
| Security | 36% | Weak — gated by D29, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 82% | Strong | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 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 — 69 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — 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) — 3 | # Building `aws-lc-rs` for NetBSD on Linux depends on `gcc-multilib`, `libclang` and `bindgen`. -------------------- ERROR: failed to solve: rust-x86_64-unknown-netbsd: failed to resolve source metadata for docker.io/library/rust-x86_64-unknown-netbsd:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed; 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 — ~16906 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (2721 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; comments in this repository's .py, .rs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Rust suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (10 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 35 current-state document(s) make no claim of a kind M4 checks. 52 claim(s) of kinds M4 does not check were not checked (path 8, environment variable 44); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X12 Unreachable branch — X12 reached only 3% of this repository's production lines — rust (16,015 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 — X16 reached only 2% of this repository's production lines — rust (16,015 lines), python (222 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — X3 reached only 3% of this repository's production lines — rust (16,015 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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.
- 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.
- 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 — 59 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
- <html> without a lang www/index.html:1
- Boundary-crossing change coupling: rustup-init.rs ↔ notify.rs src/bin/rustup-init.rs:1
Serious — 132 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
- TodoComment tests/suite/cli_exact.rs:1002
- TodoComment src/command.rs:22
- TodoComment src/config.rs:766
- TodoComment src/test.rs:98
- TodoComment src/toolchain/channels.rs:423
- TodoComment src/toolchain/names.rs:726
- TodoComment src/test/clitools.rs:1300
- TodoComment src/download/mod.rs:183
- TodoComment src/download/mod.rs:210
- TodoComment src/download/mod.rs:240
- TodoComment src/diskio/mod.rs:356
- TodoComment src/cli/self_update.rs:1147
- TodoComment src/cli/self_update/shell.rs:39
- TodoComment src/cli/self_update/shell.rs:88
- TodoComment src/cli/self_update/shell.rs:89
- TodoComment src/cli/self_update/windows.rs:449
- FixmeComment tests/suite/cli_exact.rs:480
- FixmeComment tests/suite/cli_exact.rs:497
- FixmeComment tests/suite/cli_exact.rs:548
- FixmeComment tests/suite/cli_self_upd.rs:355
- FixmeComment src/command.rs:20
- FixmeComment src/toolchain.rs:236
- FixmeComment src/utils/raw.rs:241
- FixmeComment src/cli/job.rs:1
- FixmeComment src/cli/self_update/unix.rs:154
- FixmeComment src/cli/self_update/windows.rs:481
- rustup::dist::component::package::unpack_without_first_dir (cognitive 54) src/dist/component/package.rs:234
- rustup::cli::rustup_mode::check_updates (cognitive 26) src/cli/rustup_mode.rs:950
- rustup::cli::rustup_mode::main (cognitive 25) src/cli/rustup_mode.rs:691
- rustup::cli::rustup_mode::update (cognitive 25) src/cli/rustup_mode.rs:1089
- rustup::cli::self_update::install_proxies_with_opts (cognitive 21) src/cli/self_update.rs:810
- rustup::cli::self_update::windows::maybe_install_msvc (cognitive 19) src/cli/self_update/windows.rs:123
- rustup::cli::rustup_mode::show (cognitive 16) src/cli/rustup_mode.rs:1237
- rustup::cli::self_update::stage::cleanup_at (cognitive 16) src/cli/self_update/stage.rs:185
- HackComment tests/suite/cli_paths.rs:647
- HackComment src/config.rs:1058
- HackComment src/process.rs:152
- HackComment src/download/mod.rs:372
- HackComment src/download/tests.rs:87
- HackComment src/cli/rustup_mode.rs:1058
- HackComment src/cli/self_update.rs:804
- FileTooLong: cli/rustup_mode.rs src/cli/rustup_mode.rs
- FileTooLong: src/config.rs src/config.rs
- FileTooLong: cli/self_update.rs src/cli/self_update.rs
- FileTooLong: dist/mod.rs src/dist/mod.rs
- FileTooLong: self_update/windows.rs src/cli/self_update/windows.rs
- FileTooLong: dist/manifestation.rs src/dist/manifestation.rs
- Hotspot: src/cli/rustup_mode.rs src/cli/rustup_mode.rs:691
- Hotspot: src/dist/mod.rs src/dist/mod.rs:918
- Hotspot: src/dist/manifestation.rs src/dist/manifestation.rs:116
- Hotspot: src/dist/component/components.rs src/dist/component/components.rs:262
- XxxComment src/config.rs:741
- XxxComment src/config.rs:779
- XxxComment src/toolchain.rs:350
- XxxComment src/cli/rustup_mode.rs:1448
- rustup::cli::rustup_mode::main (cyclomatic 47) src/cli/rustup_mode.rs:691
- rustup::dist::component::package::unpack_without_first_dir (cyclomatic 26) src/dist/component/package.rs:234
- rustup::cli::rustup_mode::check_updates (cyclomatic 17) src/cli/rustup_mode.rs:950
- DistOptions::install_into (cyclomatic 27) src/dist/mod.rs:918
- DistOptions::try_update (cyclomatic 19) src/dist/mod.rs:1089
- DistOptions::install_into (cognitive 41) src/dist/mod.rs:918
- DistOptions::try_update (cognitive 33) src/dist/mod.rs:1089
- Cfg::find_override_from_dir_walk (cognitive 25) src/config.rs:685
- Cfg::list_toolchains (cognitive 19) src/config.rs:1002
- FunctionTooLong: rustup::cli::rustup_mode::main src/cli/rustup_mode.rs:691
- FunctionTooLong: rustup::dist::component::package::unpack_without_first_dir src/dist/component/package.rs:234
- MethodTooLong: Manifestation.update src/dist/manifestation.rs:116
- MethodTooLong: TargetTuple.from_host src/dist/mod.rs:460
- Edited copy of a member (14 corresponding lines) src/cli/rustup_mode.rs:1556
- Edited copy of a member (14 corresponding lines) src/dist/manifestation.rs:348
- Edited copy of a member (12 corresponding lines) src/cli/self_update/unix.rs:135
- Edited copy of a member (12 corresponding lines) src/cli/self_update.rs:569
- Duplicated block (6 lines × 2) src/cli/self_update.rs:1354
- Duplicated block (6 lines × 2) src/cli/common.rs:91
- rustup.detect_platform (cyclomatic 39) www/rustup.js:7
- Manifestation::update (cyclomatic 22) src/dist/manifestation.rs:116
- Update::new (cyclomatic 19) src/dist/manifestation.rs:570
- Component::uninstall (cyclomatic 18) src/dist/component/components.rs:262
- Repeated repair: src/settings.rs src/settings.rs:45
- rustup.detect_platform (cognitive 46) www/rustup.js:7
- Manifestation::update (cognitive 38) src/dist/manifestation.rs:116
- Update::new (cognitive 36) src/dist/manifestation.rs:570
- Component::uninstall (cognitive 23) src/dist/component/components.rs:262
- InstallOpts::select_toolchain (cognitive 20) src/cli/self_update.rs:307
- Download::download_impl (cognitive 20) src/download/mod.rs:181
- Toolchain::ensure_removed (cognitive 17) src/toolchain.rs:534
- SubmitIterator::next (cognitive 16) src/diskio/threaded.rs:387
- ClassTooLong: Cfg src/config.rs:325
- TooManyFunctions: rustup::utils src/utils/mod.rs:77
- Edited copy of a member (30 corresponding lines) src/errors.rs:42
- Edited copy of a member (27 corresponding lines) src/cli/rustup_mode.rs:1413
- Edited copy of a member (16 corresponding lines) src/dist/component/transaction.rs:108
- Edited copy of a member (18 corresponding lines) src/dist/temp.rs:97
- Edited copy of a member (15 corresponding lines) src/cli/self_update/shell.rs:343
- Edited copy of a member (11 corresponding lines) src/toolchain/names.rs:182
- Edited copy of a member (10 corresponding lines) src/dist/temp.rs:36
- Edited copies of one member (4 members, 7+ corresponding lines) src/dist/component/transaction.rs:85
- Duplicated block (15–16 lines × 2) src/toolchain/channels.rs:81
- Duplicated block (11 lines × 2) src/diskio/mod.rs:382
- Duplicated block (10 lines × 2) src/errors.rs:48
- Duplicated block (8 lines × 3) src/diskio/immediate.rs:152
- Duplicated block (8 lines × 2) src/toolchain/names.rs:185
- Duplicated block (7 lines × 2) src/cli/rustup_mode.rs:1414
Minor — 61 finding(s)
- Interpolated log message defeats structured logging src/config.rs:172
- Interpolated log message defeats structured logging src/config.rs:365
- Interpolated log message defeats structured logging src/config.rs:443
- Interpolated log message defeats structured logging src/config.rs:456
- Interpolated log message defeats structured logging src/config.rs:465
- Interpolated log message defeats structured logging src/config.rs:474
- Interpolated log message defeats structured logging src/config.rs:483
- Interpolated log message defeats structured logging src/config.rs:550
- Interpolated log message defeats structured logging src/config.rs:554
- Interpolated log message defeats structured logging src/config.rs:724
- Interpolated log message defeats structured logging src/config.rs:923
- Interpolated log message defeats structured logging src/config.rs:946
- Interpolated log message defeats structured logging src/config.rs:1013
- Interpolated log message defeats structured logging src/config.rs:1025
- Interpolated log message defeats structured logging src/config.rs:1037
- Interpolated log message defeats structured logging src/config.rs:1169
- Interpolated log message defeats structured logging src/config.rs:1178
- Interpolated log message defeats structured logging src/install.rs:45
- Interpolated log message defeats structured logging src/install.rs:55
- Interpolated log message defeats structured logging src/install.rs:56
- Interpolated log message defeats structured logging src/install.rs:63
- Interpolated log message defeats structured logging src/install.rs:98
- Interpolated log message defeats structured logging src/settings.rs:126
- Interpolated log message defeats structured logging src/toolchain.rs:542
- Interpolated log message defeats structured logging src/toolchain.rs:560
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Silent fallback default on Err src/dist/download.rs:169
- Silent fallback default on Err src/toolchain.rs:302
- Off-boarding risk: anonymized user #1
- Documentation: no build, run or usage example README.md:1
- No ADRs found src/bin/rustup-init.rs:1
- REDACTED
- Orphaned files with no living knowledge
- Orphaned file ci/sync-dist.py:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No app-layer HTTPS enforcement detected
- No security response headers detected
- No inbound request validation detected
- Duplicated predicate src/cli/completions.rs:30
Minor — 3 finding(s)
- Outdated: cc
- Outdated: clap-cargo
- Outdated: zstd
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-725239605ec9420ab560346e853fa690/history.json --exit-code 0 --source . | 6 | 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-725239605ec9420ab560346e853fa690/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 . | 7 | 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 . /tmp/codehealth-osv-sbom-7245b78a812c4497ad3f4d60a3924a72 | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 77 | 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 . /tmp/codehealth-osv-sbom-7245b78a812c4497ad3f4d60a3924a72 | 0 | artifacts/raw/osv-scanner.json |