Executive summary
rust-lang/rustfmt falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 65 out of 100 and is rated Adequate, and all three of its critical findings are security problems in the build pipeline.
Code Health, at 59, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 3 points. Writing log messages as searchable templates would lift Code Health itself, worth about 5 points. Raising Code Health to 70 would lift the score to about 69.
One pipeline step puts outside input straight into a shell command, so an attacker can run commands in the build pipeline. Passing outside input through environment variables would close this risk. Correcting the flagged pipeline settings would fix the two weaknesses in the build pipeline's configuration.
The product code is 33,993 lines, about €110,000 to rebuild.
If Code Health rose from 59 to 70, the lowest score rated Strong, the score would rise from 65 to about 69.
New since the last survey: 18 findings
- Cognitive Complexity · rustfmt_nightly::macros::rewrite_cfg_select_arm (cognitive 17) src/macros.rs
- Code Duplication · Duplicated block (6 lines × 2) src/parse/macros/cfg_if.rs
- Churn × Complexity Hotspots · Hotspot: src/lists.rs src/lists.rs
- Explicit Debt · FixmeComment tests/target/cfg_select/cfg_select.rs
- Explicit Debt · FixmeComment tests/target/cfg_select/cfg_select.rs
- Explicit Debt · FixmeComment tests/target/cfg_select/cfg_select.rs
- Explicit Debt · FixmeComment tests/target/cfg_select/cfg_select.rs
- Explicit Debt · FixmeComment tests/source/cfg_select/cfg_select.rs
- Explicit Debt · FixmeComment tests/source/cfg_select/cfg_select.rs
- Explicit Debt · FixmeComment tests/source/cfg_select/cfg_select.rs
- Explicit Debt · FixmeComment tests/source/cfg_select/cfg_select.rs
- Explicit Debt · FixmeComment tests/target/cfg_select/cfg_select.rs
- Explicit Debt · FixmeComment tests/source/cfg_select/cfg_select.rs
- Explicit Debt · FixmeComment tests/target/cfg_select/issue_7045.rs
- Explicit Debt · FixmeComment tests/source/cfg_select/issue_7045.rs
- Explicit Debt · FixmeComment tests/rustfmt/main.rs
- Explicit Debt · FixmeComment src/macros.rs
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 10 findings
- Churn × Complexity Hotspots · Hotspot: src/items.rs src/items.rs
- Explicit Debt · FixmeComment tests/source/cfg_select.rs
- Explicit Debt · FixmeComment tests/source/cfg_select.rs
- Explicit Debt · FixmeComment tests/source/cfg_select.rs
- Explicit Debt · FixmeComment tests/source/cfg_select.rs
- Explicit Debt · FixmeComment tests/target/cfg_select.rs
- Explicit Debt · FixmeComment tests/target/cfg_select.rs
- Explicit Debt · FixmeComment tests/target/cfg_select.rs
- Explicit Debt · FixmeComment tests/target/cfg_select.rs
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €110,000 · Estimate
| Cost to rebuild | €36,000 to €180,000, for 594 to 1,885 hours of work, about 0.7 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 65. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 33,993 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 check_diff | 2 rustfmt_nightly.config.config_type | 3 rustfmt_nightly.spanned | 4 rustfmt_nightly.cargo-fmt.main | 5 rustfmt_nightly.config.file_lines | 6 rustfmt_nightly.config.lists | 7 rustfmt_nightly.parse.macros.cfg_select | 8 rustfmt_nightly.parse.parser | 9 rustfmt_nightly.config.options | 10 rustfmt_nightly.emitter | 11 rustfmt_nightly.modules | 12 rustfmt_nightly.git-rustfmt.main | 13 rustfmt_nightly.ignore_path | 14 rustfmt_nightly.rustfmt_diff | 15 rustfmt_nightly.shape | 16 rustfmt_nightly.emitter.checkstyle | 17 rustfmt_nightly.emitter.json | 18 rustfmt_nightly.expr | 19 rustfmt_nightly.lists | 20 rustfmt_nightly.imports | 21 rustfmt_nightly.overflow | 22 rustfmt_nightly.stmt | 23 rustfmt_nightly.macros | 24 rustfmt_nightly.reorder | 25 rustfmt_nightly.visitor | 26 rustfmt_nightly.parse.session | 27 rustfmt_nightly.rewrite | 28 rustfmt_nightly.attr | 29 rustfmt_nightly.closures | 30 rustfmt_nightly.items | 31 rustfmt_nightly.matches | 32 rustfmt_nightly.parse.macros | 33 rustfmt_nightly.patterns | 34 rustfmt_nightly.types | 35 rustfmt_nightly.comment | 36 rustfmt_nightly.modules.visitor | 37 rustfmt_nightly.formatting | 38 rustfmt_nightly.utils | 39 rustfmt_nightly | 40 rustfmt_nightly.bin.main |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 check_diff | ||||||||||||||||||||||||||||||||||||||||
| 2 rustfmt_nightly.config.config_type | ||||||||||||||||||||||||||||||||||||||||
| 3 rustfmt_nightly.spanned | ||||||||||||||||||||||||||||||||||||||||
| 4 rustfmt_nightly.cargo-fmt.main | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 rustfmt_nightly.config.file_lines | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 rustfmt_nightly.config.lists | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 rustfmt_nightly.parse.macros.cfg_select | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 8 rustfmt_nightly.parse.parser | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 9 rustfmt_nightly.config.options | 7 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 10 rustfmt_nightly.emitter | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 rustfmt_nightly.modules | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 12 rustfmt_nightly.git-rustfmt.main | 4 | 3 | ||||||||||||||||||||||||||||||||||||||
| 13 rustfmt_nightly.ignore_path | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 rustfmt_nightly.rustfmt_diff | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 rustfmt_nightly.shape | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 rustfmt_nightly.emitter.checkstyle | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 rustfmt_nightly.emitter.json | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 rustfmt_nightly.expr | 1 | 1 | 1 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 19 rustfmt_nightly.lists | 5 | 1 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 20 rustfmt_nightly.imports | 1 | 1 | 2 | 3 | 1 | 5 | 1 | |||||||||||||||||||||||||||||||||
| 21 rustfmt_nightly.overflow | 2 | 3 | 2 | 3 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 22 rustfmt_nightly.stmt | 1 | 2 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 23 rustfmt_nightly.macros | 1 | 1 | 6 | 2 | 6 | |||||||||||||||||||||||||||||||||||
| 24 rustfmt_nightly.reorder | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 25 rustfmt_nightly.visitor | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 6 | 1 | ||||||||||||||||||||||||||||
| 26 rustfmt_nightly.parse.session | 2 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 27 rustfmt_nightly.rewrite | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 rustfmt_nightly.attr | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 rustfmt_nightly.closures | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 rustfmt_nightly.items | 1 | 1 | 2 | 7 | 10 | |||||||||||||||||||||||||||||||||||
| 31 rustfmt_nightly.matches | 1 | 1 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 32 rustfmt_nightly.parse.macros | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 rustfmt_nightly.patterns | 1 | 2 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 34 rustfmt_nightly.types | 1 | 1 | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 35 rustfmt_nightly.comment | 2 | 4 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 36 rustfmt_nightly.modules.visitor | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 rustfmt_nightly.formatting | 6 | 2 | 3 | 3 | 1 | 6 | ||||||||||||||||||||||||||||||||||
| 38 rustfmt_nightly.utils | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 rustfmt_nightly | 3 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 40 rustfmt_nightly.bin.main | 2 | 1 | 4 | 1 | 2 |
4→1 rustfmt_nightly.cargo-fmt.main uses check_diff✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.cargo-fmt.main uses a type in check_diff.
- The types involved
rustfmt_nightly.cargo-fmt.main.Target→check_diff.Edition
- Direction
- rustfmt_nightly.cargo-fmt.main uses check_diff, so a change to check_diff can break rustfmt_nightly.cargo-fmt.main, while a change to rustfmt_nightly.cargo-fmt.main can't break check_diff.
- Position
- Below the diagonal: rustfmt_nightly.cargo-fmt.main uses a module listed above it, which is the healthy direction.
5→2 rustfmt_nightly.config.file_lines uses rustfmt_nightly.config.config_type✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.config.file_lines uses a type in rustfmt_nightly.config.config_type.
- The types involved
rustfmt_nightly.config.file_lines.FileLines→rustfmt_nightly.config.config_type.ConfigType
- Direction
- rustfmt_nightly.config.file_lines uses rustfmt_nightly.config.config_type, so a change to rustfmt_nightly.config.config_type can break rustfmt_nightly.config.file_lines, while a change to rustfmt_nightly.config.file_lines can't break rustfmt_nightly.config.config_type.
- Position
- Below the diagonal: rustfmt_nightly.config.file_lines uses a module listed above it, which is the healthy direction.
6→9 rustfmt_nightly.config.lists uses rustfmt_nightly.config.options part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.config.lists uses a type in rustfmt_nightly.config.options.
- The types involved
rustfmt_nightly.config.lists.DefinitiveListTactic→rustfmt_nightly.config.options.IndentStyle
- Direction
- rustfmt_nightly.config.lists uses rustfmt_nightly.config.options, so a change to rustfmt_nightly.config.options can break rustfmt_nightly.config.lists, while a change to rustfmt_nightly.config.lists can't break rustfmt_nightly.config.options.
- 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→3 rustfmt_nightly.parse.macros.cfg_select uses rustfmt_nightly.spanned✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.parse.macros.cfg_select uses a type in rustfmt_nightly.spanned.
- The types involved
rustfmt_nightly.parse.macros.cfg_select.CfgSelectArm→rustfmt_nightly.spanned.Spannedrustfmt_nightly.parse.macros.cfg_select.CfgSelectFormatPredicate→rustfmt_nightly.spanned.Spanned
- Direction
- rustfmt_nightly.parse.macros.cfg_select uses rustfmt_nightly.spanned, so a change to rustfmt_nightly.spanned can break rustfmt_nightly.parse.macros.cfg_select, while a change to rustfmt_nightly.parse.macros.cfg_select can't break rustfmt_nightly.spanned.
- Position
- Below the diagonal: rustfmt_nightly.parse.macros.cfg_select uses a module listed above it, which is the healthy direction.
7→26 rustfmt_nightly.parse.macros.cfg_select uses rustfmt_nightly.parse.session part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.parse.macros.cfg_select uses a type in rustfmt_nightly.parse.session.
- The types involved
rustfmt_nightly.parse.macros.cfg_select.cfg_select$module→rustfmt_nightly.parse.session.ParseSess
- Direction
- rustfmt_nightly.parse.macros.cfg_select uses rustfmt_nightly.parse.session, so a change to rustfmt_nightly.parse.session can break rustfmt_nightly.parse.macros.cfg_select, while a change to rustfmt_nightly.parse.macros.cfg_select can't break rustfmt_nightly.parse.session.
- 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→27 rustfmt_nightly.parse.macros.cfg_select uses rustfmt_nightly.rewrite part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.parse.macros.cfg_select uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.parse.macros.cfg_select.CfgSelectArm→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.parse.macros.cfg_select uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.parse.macros.cfg_select, while a change to rustfmt_nightly.parse.macros.cfg_select can't break rustfmt_nightly.rewrite.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→26 rustfmt_nightly.parse.parser uses rustfmt_nightly.parse.session part of a loop✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.parse.parser uses a type in rustfmt_nightly.parse.session.
- The types involved
rustfmt_nightly.parse.parser.Parser→rustfmt_nightly.parse.session.ParseSessrustfmt_nightly.parse.parser.ParserBuilder→rustfmt_nightly.parse.session.ParseSess
- Direction
- rustfmt_nightly.parse.parser uses rustfmt_nightly.parse.session, so a change to rustfmt_nightly.parse.session can break rustfmt_nightly.parse.parser, while a change to rustfmt_nightly.parse.parser can't break rustfmt_nightly.parse.session.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→39 rustfmt_nightly.parse.parser uses rustfmt_nightly part of a loop✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.parse.parser uses a type in rustfmt_nightly.
- The types involved
rustfmt_nightly.parse.parser.Parser→rustfmt_nightly.Inputrustfmt_nightly.parse.parser.ParserBuilder→rustfmt_nightly.Input
- Direction
- rustfmt_nightly.parse.parser uses rustfmt_nightly, so a change to rustfmt_nightly can break rustfmt_nightly.parse.parser, while a change to rustfmt_nightly.parse.parser can't break rustfmt_nightly.
- 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→1 rustfmt_nightly.config.options uses check_diff✕
- Connections
- 7 pairs of types, where a type in rustfmt_nightly.config.options uses a type in check_diff.
- The types involved
rustfmt_nightly.config.options.CliOptions→check_diff.Editionrustfmt_nightly.config.options.CliOptions→check_diff.StyleEditionrustfmt_nightly.config.options.Density→check_diff.StyleEditionrustfmt_nightly.config.options.Edition→check_diff.Editionrustfmt_nightly.config.options.Edition→check_diff.StyleEditionrustfmt_nightly.config.options.StyleEdition→check_diff.Editionrustfmt_nightly.config.options.StyleEdition→check_diff.StyleEdition
- Direction
- rustfmt_nightly.config.options uses check_diff, so a change to check_diff can break rustfmt_nightly.config.options, while a change to rustfmt_nightly.config.options can't break check_diff.
- Position
- Below the diagonal: rustfmt_nightly.config.options uses a module listed above it, which is the healthy direction.
9→2 rustfmt_nightly.config.options uses rustfmt_nightly.config.config_type✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.config.options uses a type in rustfmt_nightly.config.config_type.
- The types involved
rustfmt_nightly.config.options.IgnoreList→rustfmt_nightly.config.config_type.ConfigTyperustfmt_nightly.config.options.WidthHeuristics→rustfmt_nightly.config.config_type.ConfigType
- Direction
- rustfmt_nightly.config.options uses rustfmt_nightly.config.config_type, so a change to rustfmt_nightly.config.config_type can break rustfmt_nightly.config.options, while a change to rustfmt_nightly.config.options can't break rustfmt_nightly.config.config_type.
- Position
- Below the diagonal: rustfmt_nightly.config.options uses a module listed above it, which is the healthy direction.
9→6 rustfmt_nightly.config.options uses rustfmt_nightly.config.lists✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.config.options uses a type in rustfmt_nightly.config.lists.
- The types involved
rustfmt_nightly.config.options.Density→rustfmt_nightly.config.lists.ListTactic
- Direction
- rustfmt_nightly.config.options uses rustfmt_nightly.config.lists, so a change to rustfmt_nightly.config.lists can break rustfmt_nightly.config.options, while a change to rustfmt_nightly.config.options can't break rustfmt_nightly.config.lists.
- Position
- Below the diagonal: rustfmt_nightly.config.options uses a module listed above it, which is the healthy direction.
9→12 rustfmt_nightly.config.options uses rustfmt_nightly.git-rustfmt.main part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.config.options uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.config.options.CliOptions→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.config.options uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.config.options, while a change to rustfmt_nightly.config.options can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→5 rustfmt_nightly.emitter uses rustfmt_nightly.config.file_lines✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.emitter uses a type in rustfmt_nightly.config.file_lines.
- The types involved
rustfmt_nightly.emitter.FormattedFile→rustfmt_nightly.config.file_lines.FileNamerustfmt_nightly.emitter.emitter$module→rustfmt_nightly.config.file_lines.FileName
- Direction
- rustfmt_nightly.emitter uses rustfmt_nightly.config.file_lines, so a change to rustfmt_nightly.config.file_lines can break rustfmt_nightly.emitter, while a change to rustfmt_nightly.emitter can't break rustfmt_nightly.config.file_lines.
- Position
- Below the diagonal: rustfmt_nightly.emitter uses a module listed above it, which is the healthy direction.
11→8 rustfmt_nightly.modules uses rustfmt_nightly.parse.parser✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.modules uses a type in rustfmt_nightly.parse.parser.
- The types involved
rustfmt_nightly.modules.ModResolver→rustfmt_nightly.parse.parser.Directory
- Direction
- rustfmt_nightly.modules uses rustfmt_nightly.parse.parser, so a change to rustfmt_nightly.parse.parser can break rustfmt_nightly.modules, while a change to rustfmt_nightly.modules can't break rustfmt_nightly.parse.parser.
- Position
- Below the diagonal: rustfmt_nightly.modules uses a module listed above it, which is the healthy direction.
11→26 rustfmt_nightly.modules uses rustfmt_nightly.parse.session part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.modules uses a type in rustfmt_nightly.parse.session.
- The types involved
rustfmt_nightly.modules.ModResolver→rustfmt_nightly.parse.session.ParseSess
- Direction
- rustfmt_nightly.modules uses rustfmt_nightly.parse.session, so a change to rustfmt_nightly.parse.session can break rustfmt_nightly.modules, while a change to rustfmt_nightly.modules can't break rustfmt_nightly.parse.session.
- 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→30 rustfmt_nightly.modules uses rustfmt_nightly.items part of a loop✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.modules uses a type in rustfmt_nightly.items.
- The types involved
rustfmt_nightly.modules.ModResolver→rustfmt_nightly.items.Itemrustfmt_nightly.modules.modules$module→rustfmt_nightly.items.Item
- Direction
- rustfmt_nightly.modules uses rustfmt_nightly.items, so a change to rustfmt_nightly.items can break rustfmt_nightly.modules, while a change to rustfmt_nightly.modules can't break rustfmt_nightly.items.
- 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.
12→1 rustfmt_nightly.git-rustfmt.main uses check_diff✕
- Connections
- 4 pairs of types, where a type in rustfmt_nightly.git-rustfmt.main uses a type in check_diff.
- The types involved
rustfmt_nightly.git-rustfmt.main.Config→check_diff.Editionrustfmt_nightly.git-rustfmt.main.Config→check_diff.StyleEditionrustfmt_nightly.git-rustfmt.main.NullOptions→check_diff.Editionrustfmt_nightly.git-rustfmt.main.NullOptions→check_diff.StyleEdition
- Direction
- rustfmt_nightly.git-rustfmt.main uses check_diff, so a change to check_diff can break rustfmt_nightly.git-rustfmt.main, while a change to rustfmt_nightly.git-rustfmt.main can't break check_diff.
- Position
- Below the diagonal: rustfmt_nightly.git-rustfmt.main uses a module listed above it, which is the healthy direction.
12→9 rustfmt_nightly.git-rustfmt.main uses rustfmt_nightly.config.options✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly.git-rustfmt.main uses a type in rustfmt_nightly.config.options.
- The types involved
rustfmt_nightly.git-rustfmt.main.Config→rustfmt_nightly.config.options.Versionrustfmt_nightly.git-rustfmt.main.NullOptions→rustfmt_nightly.config.options.CliOptionsrustfmt_nightly.git-rustfmt.main.NullOptions→rustfmt_nightly.config.options.Version
- Direction
- rustfmt_nightly.git-rustfmt.main uses rustfmt_nightly.config.options, so a change to rustfmt_nightly.config.options can break rustfmt_nightly.git-rustfmt.main, while a change to rustfmt_nightly.git-rustfmt.main can't break rustfmt_nightly.config.options.
- Position
- Below the diagonal: rustfmt_nightly.git-rustfmt.main uses a module listed above it, which is the healthy direction.
13→5 rustfmt_nightly.ignore_path uses rustfmt_nightly.config.file_lines✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.ignore_path uses a type in rustfmt_nightly.config.file_lines.
- The types involved
rustfmt_nightly.ignore_path.IgnorePathSet→rustfmt_nightly.config.file_lines.FileName
- Direction
- rustfmt_nightly.ignore_path uses rustfmt_nightly.config.file_lines, so a change to rustfmt_nightly.config.file_lines can break rustfmt_nightly.ignore_path, while a change to rustfmt_nightly.ignore_path can't break rustfmt_nightly.config.file_lines.
- Position
- Below the diagonal: rustfmt_nightly.ignore_path uses a module listed above it, which is the healthy direction.
13→9 rustfmt_nightly.ignore_path uses rustfmt_nightly.config.options✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.ignore_path uses a type in rustfmt_nightly.config.options.
- The types involved
rustfmt_nightly.ignore_path.IgnorePathSet→rustfmt_nightly.config.options.IgnoreList
- Direction
- rustfmt_nightly.ignore_path uses rustfmt_nightly.config.options, so a change to rustfmt_nightly.config.options can break rustfmt_nightly.ignore_path, while a change to rustfmt_nightly.ignore_path can't break rustfmt_nightly.config.options.
- Position
- Below the diagonal: rustfmt_nightly.ignore_path uses a module listed above it, which is the healthy direction.
14→9 rustfmt_nightly.rustfmt_diff uses rustfmt_nightly.config.options✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.rustfmt_diff uses a type in rustfmt_nightly.config.options.
- The types involved
rustfmt_nightly.rustfmt_diff.OutputWriter→rustfmt_nightly.config.options.Color
- Direction
- rustfmt_nightly.rustfmt_diff uses rustfmt_nightly.config.options, so a change to rustfmt_nightly.config.options can break rustfmt_nightly.rustfmt_diff, while a change to rustfmt_nightly.rustfmt_diff can't break rustfmt_nightly.config.options.
- Position
- Below the diagonal: rustfmt_nightly.rustfmt_diff uses a module listed above it, which is the healthy direction.
14→12 rustfmt_nightly.rustfmt_diff uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.rustfmt_diff uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.rustfmt_diff.rustfmt_diff$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.rustfmt_diff uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.rustfmt_diff, while a change to rustfmt_nightly.rustfmt_diff can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.rustfmt_diff uses a module listed above it, which is the healthy direction.
15→12 rustfmt_nightly.shape uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.shape uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.shape.Indent→rustfmt_nightly.git-rustfmt.main.Configrustfmt_nightly.shape.Shape→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.shape uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.shape, while a change to rustfmt_nightly.shape can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.shape uses a module listed above it, which is the healthy direction.
15→27 rustfmt_nightly.shape uses rustfmt_nightly.rewrite part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.shape uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.shape.Shape→rustfmt_nightly.rewrite.ExceedsMaxWidthError
- Direction
- rustfmt_nightly.shape uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.shape, while a change to rustfmt_nightly.shape can't break rustfmt_nightly.rewrite.
- 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.
16→5 rustfmt_nightly.emitter.checkstyle uses rustfmt_nightly.config.file_lines✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.emitter.checkstyle uses a type in rustfmt_nightly.config.file_lines.
- The types involved
rustfmt_nightly.emitter.checkstyle.checkstyle$module→rustfmt_nightly.config.file_lines.FileName
- Direction
- rustfmt_nightly.emitter.checkstyle uses rustfmt_nightly.config.file_lines, so a change to rustfmt_nightly.config.file_lines can break rustfmt_nightly.emitter.checkstyle, while a change to rustfmt_nightly.emitter.checkstyle can't break rustfmt_nightly.config.file_lines.
- Position
- Below the diagonal: rustfmt_nightly.emitter.checkstyle uses a module listed above it, which is the healthy direction.
16→10 rustfmt_nightly.emitter.checkstyle uses rustfmt_nightly.emitter✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.emitter.checkstyle uses a type in rustfmt_nightly.emitter.
- The types involved
rustfmt_nightly.emitter.checkstyle.CheckstyleEmitter→rustfmt_nightly.emitter.Emitterrustfmt_nightly.emitter.checkstyle.CheckstyleEmitter→rustfmt_nightly.emitter.FormattedFile
- Direction
- rustfmt_nightly.emitter.checkstyle uses rustfmt_nightly.emitter, so a change to rustfmt_nightly.emitter can break rustfmt_nightly.emitter.checkstyle, while a change to rustfmt_nightly.emitter.checkstyle can't break rustfmt_nightly.emitter.
- Position
- Below the diagonal: rustfmt_nightly.emitter.checkstyle uses a module listed above it, which is the healthy direction.
16→14 rustfmt_nightly.emitter.checkstyle uses rustfmt_nightly.rustfmt_diff✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.emitter.checkstyle uses a type in rustfmt_nightly.rustfmt_diff.
- The types involved
rustfmt_nightly.emitter.checkstyle.checkstyle$module→rustfmt_nightly.rustfmt_diff.Mismatch
- Direction
- rustfmt_nightly.emitter.checkstyle uses rustfmt_nightly.rustfmt_diff, so a change to rustfmt_nightly.rustfmt_diff can break rustfmt_nightly.emitter.checkstyle, while a change to rustfmt_nightly.emitter.checkstyle can't break rustfmt_nightly.rustfmt_diff.
- Position
- Below the diagonal: rustfmt_nightly.emitter.checkstyle uses a module listed above it, which is the healthy direction.
17→5 rustfmt_nightly.emitter.json uses rustfmt_nightly.config.file_lines✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.emitter.json uses a type in rustfmt_nightly.config.file_lines.
- The types involved
rustfmt_nightly.emitter.json.JsonEmitter→rustfmt_nightly.config.file_lines.FileName
- Direction
- rustfmt_nightly.emitter.json uses rustfmt_nightly.config.file_lines, so a change to rustfmt_nightly.config.file_lines can break rustfmt_nightly.emitter.json, while a change to rustfmt_nightly.emitter.json can't break rustfmt_nightly.config.file_lines.
- Position
- Below the diagonal: rustfmt_nightly.emitter.json uses a module listed above it, which is the healthy direction.
17→10 rustfmt_nightly.emitter.json uses rustfmt_nightly.emitter✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.emitter.json uses a type in rustfmt_nightly.emitter.
- The types involved
rustfmt_nightly.emitter.json.JsonEmitter→rustfmt_nightly.emitter.Emitterrustfmt_nightly.emitter.json.JsonEmitter→rustfmt_nightly.emitter.FormattedFile
- Direction
- rustfmt_nightly.emitter.json uses rustfmt_nightly.emitter, so a change to rustfmt_nightly.emitter can break rustfmt_nightly.emitter.json, while a change to rustfmt_nightly.emitter.json can't break rustfmt_nightly.emitter.
- Position
- Below the diagonal: rustfmt_nightly.emitter.json uses a module listed above it, which is the healthy direction.
17→14 rustfmt_nightly.emitter.json uses rustfmt_nightly.rustfmt_diff✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.emitter.json uses a type in rustfmt_nightly.rustfmt_diff.
- The types involved
rustfmt_nightly.emitter.json.JsonEmitter→rustfmt_nightly.rustfmt_diff.Mismatch
- Direction
- rustfmt_nightly.emitter.json uses rustfmt_nightly.rustfmt_diff, so a change to rustfmt_nightly.rustfmt_diff can break rustfmt_nightly.emitter.json, while a change to rustfmt_nightly.emitter.json can't break rustfmt_nightly.rustfmt_diff.
- Position
- Below the diagonal: rustfmt_nightly.emitter.json uses a module listed above it, which is the healthy direction.
18→6 rustfmt_nightly.expr uses rustfmt_nightly.config.lists✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.expr uses a type in rustfmt_nightly.config.lists.
- The types involved
rustfmt_nightly.expr.expr$module→rustfmt_nightly.config.lists.SeparatorTactic
- Direction
- rustfmt_nightly.expr uses rustfmt_nightly.config.lists, so a change to rustfmt_nightly.config.lists can break rustfmt_nightly.expr, while a change to rustfmt_nightly.expr can't break rustfmt_nightly.config.lists.
- Position
- Below the diagonal: rustfmt_nightly.expr uses a module listed above it, which is the healthy direction.
18→9 rustfmt_nightly.expr uses rustfmt_nightly.config.options✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.expr uses a type in rustfmt_nightly.config.options.
- The types involved
rustfmt_nightly.expr.expr$module→rustfmt_nightly.config.options.FloatLiteralTrailingZero
- Direction
- rustfmt_nightly.expr uses rustfmt_nightly.config.options, so a change to rustfmt_nightly.config.options can break rustfmt_nightly.expr, while a change to rustfmt_nightly.expr can't break rustfmt_nightly.config.options.
- Position
- Below the diagonal: rustfmt_nightly.expr uses a module listed above it, which is the healthy direction.
18→12 rustfmt_nightly.expr uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.expr uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.expr.expr$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.expr uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.expr, while a change to rustfmt_nightly.expr can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.expr uses a module listed above it, which is the healthy direction.
18→15 rustfmt_nightly.expr uses rustfmt_nightly.shape✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.expr uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.expr.ControlFlow→rustfmt_nightly.shape.Shaperustfmt_nightly.expr.expr$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.expr uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.expr, while a change to rustfmt_nightly.expr can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.expr uses a module listed above it, which is the healthy direction.
18→22 rustfmt_nightly.expr uses rustfmt_nightly.stmt part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.expr uses a type in rustfmt_nightly.stmt.
- The types involved
rustfmt_nightly.expr.expr$module→rustfmt_nightly.stmt.Stmt
- Direction
- rustfmt_nightly.expr uses rustfmt_nightly.stmt, so a change to rustfmt_nightly.stmt can break rustfmt_nightly.expr, while a change to rustfmt_nightly.expr can't break rustfmt_nightly.stmt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→27 rustfmt_nightly.expr uses rustfmt_nightly.rewrite part of a loop✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly.expr uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.expr.ControlFlow→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.expr.ControlFlow→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.expr.expr$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.expr uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.expr, while a change to rustfmt_nightly.expr can't break rustfmt_nightly.rewrite.
- 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→6 rustfmt_nightly.lists uses rustfmt_nightly.config.lists✕
- Connections
- 5 pairs of types, where a type in rustfmt_nightly.lists uses a type in rustfmt_nightly.config.lists.
- The types involved
rustfmt_nightly.lists.ListFormatting→rustfmt_nightly.config.lists.DefinitiveListTacticrustfmt_nightly.lists.ListFormatting→rustfmt_nightly.config.lists.SeparatorPlacerustfmt_nightly.lists.ListFormatting→rustfmt_nightly.config.lists.SeparatorTacticrustfmt_nightly.lists.lists$module→rustfmt_nightly.config.lists.DefinitiveListTacticrustfmt_nightly.lists.lists$module→rustfmt_nightly.config.lists.ListTactic
- Direction
- rustfmt_nightly.lists uses rustfmt_nightly.config.lists, so a change to rustfmt_nightly.config.lists can break rustfmt_nightly.lists, while a change to rustfmt_nightly.lists can't break rustfmt_nightly.config.lists.
- Position
- Below the diagonal: rustfmt_nightly.lists uses a module listed above it, which is the healthy direction.
19→12 rustfmt_nightly.lists uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.lists uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.lists.ListFormatting→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.lists uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.lists, while a change to rustfmt_nightly.lists can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.lists uses a module listed above it, which is the healthy direction.
19→15 rustfmt_nightly.lists uses rustfmt_nightly.shape✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.lists uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.lists.ListFormatting→rustfmt_nightly.shape.Shaperustfmt_nightly.lists.lists$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.lists uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.lists, while a change to rustfmt_nightly.lists can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.lists uses a module listed above it, which is the healthy direction.
19→25 rustfmt_nightly.lists uses rustfmt_nightly.visitor part of a loop✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.lists uses a type in rustfmt_nightly.visitor.
- The types involved
rustfmt_nightly.lists.ListItems→rustfmt_nightly.visitor.SnippetProviderrustfmt_nightly.lists.lists$module→rustfmt_nightly.visitor.SnippetProvider
- Direction
- rustfmt_nightly.lists uses rustfmt_nightly.visitor, so a change to rustfmt_nightly.visitor can break rustfmt_nightly.lists, while a change to rustfmt_nightly.lists can't break rustfmt_nightly.visitor.
- 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→27 rustfmt_nightly.lists uses rustfmt_nightly.rewrite part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.lists uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.lists.lists$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.lists uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.lists, while a change to rustfmt_nightly.lists can't break rustfmt_nightly.rewrite.
- 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→30 rustfmt_nightly.lists uses rustfmt_nightly.items part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.lists uses a type in rustfmt_nightly.items.
- The types involved
rustfmt_nightly.lists.ListItems→rustfmt_nightly.items.Item
- Direction
- rustfmt_nightly.lists uses rustfmt_nightly.items, so a change to rustfmt_nightly.items can break rustfmt_nightly.lists, while a change to rustfmt_nightly.lists can't break rustfmt_nightly.items.
- 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→1 rustfmt_nightly.imports uses check_diff✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.imports uses a type in check_diff.
- The types involved
rustfmt_nightly.imports.UseSegment→check_diff.StyleEdition
- Direction
- rustfmt_nightly.imports uses check_diff, so a change to check_diff can break rustfmt_nightly.imports, while a change to rustfmt_nightly.imports can't break check_diff.
- Position
- Below the diagonal: rustfmt_nightly.imports uses a module listed above it, which is the healthy direction.
20→3 rustfmt_nightly.imports uses rustfmt_nightly.spanned✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.imports uses a type in rustfmt_nightly.spanned.
- The types involved
rustfmt_nightly.imports.UseTree→rustfmt_nightly.spanned.Spanned
- Direction
- rustfmt_nightly.imports uses rustfmt_nightly.spanned, so a change to rustfmt_nightly.spanned can break rustfmt_nightly.imports, while a change to rustfmt_nightly.imports can't break rustfmt_nightly.spanned.
- Position
- Below the diagonal: rustfmt_nightly.imports uses a module listed above it, which is the healthy direction.
20→9 rustfmt_nightly.imports uses rustfmt_nightly.config.options✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.imports uses a type in rustfmt_nightly.config.options.
- The types involved
rustfmt_nightly.imports.UseTree→rustfmt_nightly.config.options.ImportGranularityrustfmt_nightly.imports.imports$module→rustfmt_nightly.config.options.ImportGranularity
- Direction
- rustfmt_nightly.imports uses rustfmt_nightly.config.options, so a change to rustfmt_nightly.config.options can break rustfmt_nightly.imports, while a change to rustfmt_nightly.imports can't break rustfmt_nightly.config.options.
- Position
- Below the diagonal: rustfmt_nightly.imports uses a module listed above it, which is the healthy direction.
20→15 rustfmt_nightly.imports uses rustfmt_nightly.shape✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly.imports uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.imports.UseSegment→rustfmt_nightly.shape.Shaperustfmt_nightly.imports.UseTree→rustfmt_nightly.shape.Shaperustfmt_nightly.imports.imports$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.imports uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.imports, while a change to rustfmt_nightly.imports can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.imports uses a module listed above it, which is the healthy direction.
20→19 rustfmt_nightly.imports uses rustfmt_nightly.lists✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.imports uses a type in rustfmt_nightly.lists.
- The types involved
rustfmt_nightly.imports.UseTree→rustfmt_nightly.lists.ListItem
- Direction
- rustfmt_nightly.imports uses rustfmt_nightly.lists, so a change to rustfmt_nightly.lists can break rustfmt_nightly.imports, while a change to rustfmt_nightly.imports can't break rustfmt_nightly.lists.
- Position
- Below the diagonal: rustfmt_nightly.imports uses a module listed above it, which is the healthy direction.
20→27 rustfmt_nightly.imports uses rustfmt_nightly.rewrite part of a loop✕
- Connections
- 5 pairs of types, where a type in rustfmt_nightly.imports uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.imports.UseSegment→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.imports.UseSegment→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.imports.UseTree→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.imports.UseTree→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.imports.imports$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.imports uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.imports, while a change to rustfmt_nightly.imports can't break rustfmt_nightly.rewrite.
- 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→30 rustfmt_nightly.imports uses rustfmt_nightly.items part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.imports uses a type in rustfmt_nightly.items.
- The types involved
rustfmt_nightly.imports.UseTree→rustfmt_nightly.items.Item
- Direction
- rustfmt_nightly.imports uses rustfmt_nightly.items, so a change to rustfmt_nightly.items can break rustfmt_nightly.imports, while a change to rustfmt_nightly.imports can't break rustfmt_nightly.items.
- 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→3 rustfmt_nightly.overflow uses rustfmt_nightly.spanned✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.overflow uses a type in rustfmt_nightly.spanned.
- The types involved
rustfmt_nightly.overflow.IntoOverflowableItem→rustfmt_nightly.spanned.Spannedrustfmt_nightly.overflow.OverflowableItem→rustfmt_nightly.spanned.Spanned
- Direction
- rustfmt_nightly.overflow uses rustfmt_nightly.spanned, so a change to rustfmt_nightly.spanned can break rustfmt_nightly.overflow, while a change to rustfmt_nightly.overflow can't break rustfmt_nightly.spanned.
- Position
- Below the diagonal: rustfmt_nightly.overflow uses a module listed above it, which is the healthy direction.
21→6 rustfmt_nightly.overflow uses rustfmt_nightly.config.lists✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly.overflow uses a type in rustfmt_nightly.config.lists.
- The types involved
rustfmt_nightly.overflow.Context→rustfmt_nightly.config.lists.DefinitiveListTacticrustfmt_nightly.overflow.Context→rustfmt_nightly.config.lists.SeparatorTacticrustfmt_nightly.overflow.overflow$module→rustfmt_nightly.config.lists.SeparatorTactic
- Direction
- rustfmt_nightly.overflow uses rustfmt_nightly.config.lists, so a change to rustfmt_nightly.config.lists can break rustfmt_nightly.overflow, while a change to rustfmt_nightly.overflow can't break rustfmt_nightly.config.lists.
- Position
- Below the diagonal: rustfmt_nightly.overflow uses a module listed above it, which is the healthy direction.
21→12 rustfmt_nightly.overflow uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.overflow uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.overflow.OverflowableItem→rustfmt_nightly.git-rustfmt.main.Configrustfmt_nightly.overflow.overflow$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.overflow uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.overflow, while a change to rustfmt_nightly.overflow can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.overflow uses a module listed above it, which is the healthy direction.
21→15 rustfmt_nightly.overflow uses rustfmt_nightly.shape✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly.overflow uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.overflow.Context→rustfmt_nightly.shape.Shaperustfmt_nightly.overflow.OverflowableItem→rustfmt_nightly.shape.Shaperustfmt_nightly.overflow.overflow$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.overflow uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.overflow, while a change to rustfmt_nightly.overflow can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.overflow uses a module listed above it, which is the healthy direction.
21→19 rustfmt_nightly.overflow uses rustfmt_nightly.lists✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.overflow uses a type in rustfmt_nightly.lists.
- The types involved
rustfmt_nightly.overflow.Context→rustfmt_nightly.lists.ListItem
- Direction
- rustfmt_nightly.overflow uses rustfmt_nightly.lists, so a change to rustfmt_nightly.lists can break rustfmt_nightly.overflow, while a change to rustfmt_nightly.overflow can't break rustfmt_nightly.lists.
- Position
- Below the diagonal: rustfmt_nightly.overflow uses a module listed above it, which is the healthy direction.
21→27 rustfmt_nightly.overflow uses rustfmt_nightly.rewrite part of a loop✕
- Connections
- 5 pairs of types, where a type in rustfmt_nightly.overflow uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.overflow.Context→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.overflow.IntoOverflowableItem→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.overflow.OverflowableItem→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.overflow.OverflowableItem→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.overflow.overflow$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.overflow uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.overflow, while a change to rustfmt_nightly.overflow can't break rustfmt_nightly.rewrite.
- 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.
22→3 rustfmt_nightly.stmt uses rustfmt_nightly.spanned✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.stmt uses a type in rustfmt_nightly.spanned.
- The types involved
rustfmt_nightly.stmt.Stmt→rustfmt_nightly.spanned.Spanned
- Direction
- rustfmt_nightly.stmt uses rustfmt_nightly.spanned, so a change to rustfmt_nightly.spanned can break rustfmt_nightly.stmt, while a change to rustfmt_nightly.stmt can't break rustfmt_nightly.spanned.
- Position
- Below the diagonal: rustfmt_nightly.stmt uses a module listed above it, which is the healthy direction.
22→15 rustfmt_nightly.stmt uses rustfmt_nightly.shape✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.stmt uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.stmt.Stmt→rustfmt_nightly.shape.Shaperustfmt_nightly.stmt.stmt$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.stmt uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.stmt, while a change to rustfmt_nightly.stmt can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.stmt uses a module listed above it, which is the healthy direction.
22→18 rustfmt_nightly.stmt uses rustfmt_nightly.expr✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.stmt uses a type in rustfmt_nightly.expr.
- The types involved
rustfmt_nightly.stmt.stmt$module→rustfmt_nightly.expr.ExprType
- Direction
- rustfmt_nightly.stmt uses rustfmt_nightly.expr, so a change to rustfmt_nightly.expr can break rustfmt_nightly.stmt, while a change to rustfmt_nightly.stmt can't break rustfmt_nightly.expr.
- Position
- Below the diagonal: rustfmt_nightly.stmt uses a module listed above it, which is the healthy direction.
22→27 rustfmt_nightly.stmt uses rustfmt_nightly.rewrite part of a loop✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly.stmt uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.stmt.Stmt→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.stmt.Stmt→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.stmt.stmt$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.stmt uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.stmt, while a change to rustfmt_nightly.stmt can't break rustfmt_nightly.rewrite.
- 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.
22→30 rustfmt_nightly.stmt uses rustfmt_nightly.items part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.stmt uses a type in rustfmt_nightly.items.
- The types involved
rustfmt_nightly.stmt.Stmt→rustfmt_nightly.items.Item
- Direction
- rustfmt_nightly.stmt uses rustfmt_nightly.items, so a change to rustfmt_nightly.items can break rustfmt_nightly.stmt, while a change to rustfmt_nightly.stmt can't break rustfmt_nightly.items.
- 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→3 rustfmt_nightly.macros uses rustfmt_nightly.spanned✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.macros uses a type in rustfmt_nightly.spanned.
- The types involved
rustfmt_nightly.macros.MacroArg→rustfmt_nightly.spanned.Spanned
- Direction
- rustfmt_nightly.macros uses rustfmt_nightly.spanned, so a change to rustfmt_nightly.spanned can break rustfmt_nightly.macros, while a change to rustfmt_nightly.macros can't break rustfmt_nightly.spanned.
- Position
- Below the diagonal: rustfmt_nightly.macros uses a module listed above it, which is the healthy direction.
23→7 rustfmt_nightly.macros uses rustfmt_nightly.parse.macros.cfg_select✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.macros uses a type in rustfmt_nightly.parse.macros.cfg_select.
- The types involved
rustfmt_nightly.macros.macros$module→rustfmt_nightly.parse.macros.cfg_select.CfgSelectArm
- Direction
- rustfmt_nightly.macros uses rustfmt_nightly.parse.macros.cfg_select, so a change to rustfmt_nightly.parse.macros.cfg_select can break rustfmt_nightly.macros, while a change to rustfmt_nightly.macros can't break rustfmt_nightly.parse.macros.cfg_select.
- Position
- Below the diagonal: rustfmt_nightly.macros uses a module listed above it, which is the healthy direction.
23→15 rustfmt_nightly.macros uses rustfmt_nightly.shape✕
- Connections
- 6 pairs of types, where a type in rustfmt_nightly.macros uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.macros.MacroArg→rustfmt_nightly.shape.Shaperustfmt_nightly.macros.MacroArgKind→rustfmt_nightly.shape.Shaperustfmt_nightly.macros.MacroBranch→rustfmt_nightly.shape.Shaperustfmt_nightly.macros.ParsedMacroArg→rustfmt_nightly.shape.Shaperustfmt_nightly.macros.macros$module→rustfmt_nightly.shape.Indentrustfmt_nightly.macros.macros$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.macros uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.macros, while a change to rustfmt_nightly.macros can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.macros uses a module listed above it, which is the healthy direction.
23→21 rustfmt_nightly.macros uses rustfmt_nightly.overflow✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.macros uses a type in rustfmt_nightly.overflow.
- The types involved
rustfmt_nightly.macros.MacroArg→rustfmt_nightly.overflow.IntoOverflowableItemrustfmt_nightly.macros.MacroArg→rustfmt_nightly.overflow.OverflowableItem
- Direction
- rustfmt_nightly.macros uses rustfmt_nightly.overflow, so a change to rustfmt_nightly.overflow can break rustfmt_nightly.macros, while a change to rustfmt_nightly.macros can't break rustfmt_nightly.overflow.
- Position
- Below the diagonal: rustfmt_nightly.macros uses a module listed above it, which is the healthy direction.
23→27 rustfmt_nightly.macros uses rustfmt_nightly.rewrite part of a loop✕
- Connections
- 6 pairs of types, where a type in rustfmt_nightly.macros uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.macros.MacroArg→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.macros.MacroArg→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.macros.MacroArgKind→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.macros.MacroBranch→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.macros.ParsedMacroArg→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.macros.macros$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.macros uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.macros, while a change to rustfmt_nightly.macros can't break rustfmt_nightly.rewrite.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→12 rustfmt_nightly.reorder uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.reorder uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.reorder.ReorderableItemKind→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.reorder uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.reorder, while a change to rustfmt_nightly.reorder can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.reorder uses a module listed above it, which is the healthy direction.
24→15 rustfmt_nightly.reorder uses rustfmt_nightly.shape✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.reorder uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.reorder.reorder$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.reorder uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.reorder, while a change to rustfmt_nightly.reorder can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.reorder uses a module listed above it, which is the healthy direction.
24→20 rustfmt_nightly.reorder uses rustfmt_nightly.imports✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.reorder uses a type in rustfmt_nightly.imports.
- The types involved
rustfmt_nightly.reorder.reorder$module→rustfmt_nightly.imports.UseTree
- Direction
- rustfmt_nightly.reorder uses rustfmt_nightly.imports, so a change to rustfmt_nightly.imports can break rustfmt_nightly.reorder, while a change to rustfmt_nightly.reorder can't break rustfmt_nightly.imports.
- Position
- Below the diagonal: rustfmt_nightly.reorder uses a module listed above it, which is the healthy direction.
24→27 rustfmt_nightly.reorder uses rustfmt_nightly.rewrite part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.reorder uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.reorder.reorder$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.reorder uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.reorder, while a change to rustfmt_nightly.reorder can't break rustfmt_nightly.rewrite.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→30 rustfmt_nightly.reorder uses rustfmt_nightly.items part of a loop✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.reorder uses a type in rustfmt_nightly.items.
- The types involved
rustfmt_nightly.reorder.ReorderableItemKind→rustfmt_nightly.items.Itemrustfmt_nightly.reorder.reorder$module→rustfmt_nightly.items.Item
- Direction
- rustfmt_nightly.reorder uses rustfmt_nightly.items, so a change to rustfmt_nightly.items can break rustfmt_nightly.reorder, while a change to rustfmt_nightly.reorder can't break rustfmt_nightly.items.
- 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.
25→5 rustfmt_nightly.visitor uses rustfmt_nightly.config.file_lines✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.visitor uses a type in rustfmt_nightly.config.file_lines.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.config.file_lines.FileName
- Direction
- rustfmt_nightly.visitor uses rustfmt_nightly.config.file_lines, so a change to rustfmt_nightly.config.file_lines can break rustfmt_nightly.visitor, while a change to rustfmt_nightly.visitor can't break rustfmt_nightly.config.file_lines.
- Position
- Below the diagonal: rustfmt_nightly.visitor uses a module listed above it, which is the healthy direction.
25→11 rustfmt_nightly.visitor uses rustfmt_nightly.modules✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.visitor uses a type in rustfmt_nightly.modules.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.modules.Module
- Direction
- rustfmt_nightly.visitor uses rustfmt_nightly.modules, so a change to rustfmt_nightly.modules can break rustfmt_nightly.visitor, while a change to rustfmt_nightly.visitor can't break rustfmt_nightly.modules.
- Position
- Below the diagonal: rustfmt_nightly.visitor uses a module listed above it, which is the healthy direction.
25→12 rustfmt_nightly.visitor uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.visitor uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.visitor uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.visitor, while a change to rustfmt_nightly.visitor can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.visitor uses a module listed above it, which is the healthy direction.
25→15 rustfmt_nightly.visitor uses rustfmt_nightly.shape✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.visitor uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.shape.Indentrustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.visitor uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.visitor, while a change to rustfmt_nightly.visitor can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.visitor uses a module listed above it, which is the healthy direction.
25→20 rustfmt_nightly.visitor uses rustfmt_nightly.imports✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.visitor uses a type in rustfmt_nightly.imports.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.imports.UseTree
- Direction
- rustfmt_nightly.visitor uses rustfmt_nightly.imports, so a change to rustfmt_nightly.imports can break rustfmt_nightly.visitor, while a change to rustfmt_nightly.visitor can't break rustfmt_nightly.imports.
- Position
- Below the diagonal: rustfmt_nightly.visitor uses a module listed above it, which is the healthy direction.
25→22 rustfmt_nightly.visitor uses rustfmt_nightly.stmt✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.visitor uses a type in rustfmt_nightly.stmt.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.stmt.Stmt
- Direction
- rustfmt_nightly.visitor uses rustfmt_nightly.stmt, so a change to rustfmt_nightly.stmt can break rustfmt_nightly.visitor, while a change to rustfmt_nightly.visitor can't break rustfmt_nightly.stmt.
- Position
- Below the diagonal: rustfmt_nightly.visitor uses a module listed above it, which is the healthy direction.
25→23 rustfmt_nightly.visitor uses rustfmt_nightly.macros✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.visitor uses a type in rustfmt_nightly.macros.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.macros.MacroPosition
- Direction
- rustfmt_nightly.visitor uses rustfmt_nightly.macros, so a change to rustfmt_nightly.macros can break rustfmt_nightly.visitor, while a change to rustfmt_nightly.visitor can't break rustfmt_nightly.macros.
- Position
- Below the diagonal: rustfmt_nightly.visitor uses a module listed above it, which is the healthy direction.
25→24 rustfmt_nightly.visitor uses rustfmt_nightly.reorder✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.visitor uses a type in rustfmt_nightly.reorder.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.reorder.ReorderableItemKind
- Direction
- rustfmt_nightly.visitor uses rustfmt_nightly.reorder, so a change to rustfmt_nightly.reorder can break rustfmt_nightly.visitor, while a change to rustfmt_nightly.visitor can't break rustfmt_nightly.reorder.
- Position
- Below the diagonal: rustfmt_nightly.visitor uses a module listed above it, which is the healthy direction.
25→26 rustfmt_nightly.visitor uses rustfmt_nightly.parse.session part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.visitor uses a type in rustfmt_nightly.parse.session.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.parse.session.ParseSess
- Direction
- rustfmt_nightly.visitor uses rustfmt_nightly.parse.session, so a change to rustfmt_nightly.parse.session can break rustfmt_nightly.visitor, while a change to rustfmt_nightly.visitor can't break rustfmt_nightly.parse.session.
- 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.
25→27 rustfmt_nightly.visitor uses rustfmt_nightly.rewrite part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.visitor uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.visitor uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.visitor, while a change to rustfmt_nightly.visitor can't break rustfmt_nightly.rewrite.
- 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.
25→30 rustfmt_nightly.visitor uses rustfmt_nightly.items part of a loop✕
- Connections
- 6 pairs of types, where a type in rustfmt_nightly.visitor uses a type in rustfmt_nightly.items.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.items.BodyElementrustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.items.FnSigrustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.items.Itemrustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.items.ItemVisitorKindrustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.items.StaticPartsrustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.items.StructParts
- Direction
- rustfmt_nightly.visitor uses rustfmt_nightly.items, so a change to rustfmt_nightly.items can break rustfmt_nightly.visitor, while a change to rustfmt_nightly.visitor can't break rustfmt_nightly.items.
- 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.
25→39 rustfmt_nightly.visitor uses rustfmt_nightly part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.visitor uses a type in rustfmt_nightly.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.FormatReport
- Direction
- rustfmt_nightly.visitor uses rustfmt_nightly, so a change to rustfmt_nightly can break rustfmt_nightly.visitor, while a change to rustfmt_nightly.visitor can't break rustfmt_nightly.
- 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.
26→5 rustfmt_nightly.parse.session uses rustfmt_nightly.config.file_lines✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.parse.session uses a type in rustfmt_nightly.config.file_lines.
- The types involved
rustfmt_nightly.parse.session.ParseSess→rustfmt_nightly.config.file_lines.FileNamerustfmt_nightly.parse.session.ParseSess→rustfmt_nightly.config.file_lines.LineRange
- Direction
- rustfmt_nightly.parse.session uses rustfmt_nightly.config.file_lines, so a change to rustfmt_nightly.config.file_lines can break rustfmt_nightly.parse.session, while a change to rustfmt_nightly.parse.session can't break rustfmt_nightly.config.file_lines.
- Position
- Below the diagonal: rustfmt_nightly.parse.session uses a module listed above it, which is the healthy direction.
26→9 rustfmt_nightly.parse.session uses rustfmt_nightly.config.options✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.parse.session uses a type in rustfmt_nightly.config.options.
- The types involved
rustfmt_nightly.parse.session.session$module→rustfmt_nightly.config.options.Color
- Direction
- rustfmt_nightly.parse.session uses rustfmt_nightly.config.options, so a change to rustfmt_nightly.config.options can break rustfmt_nightly.parse.session, while a change to rustfmt_nightly.parse.session can't break rustfmt_nightly.config.options.
- Position
- Below the diagonal: rustfmt_nightly.parse.session uses a module listed above it, which is the healthy direction.
26→10 rustfmt_nightly.parse.session uses rustfmt_nightly.emitter✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.parse.session uses a type in rustfmt_nightly.emitter.
- The types involved
rustfmt_nightly.parse.session.SilentOnIgnoredFilesEmitter→rustfmt_nightly.emitter.Emitter
- Direction
- rustfmt_nightly.parse.session uses rustfmt_nightly.emitter, so a change to rustfmt_nightly.emitter can break rustfmt_nightly.parse.session, while a change to rustfmt_nightly.parse.session can't break rustfmt_nightly.emitter.
- Position
- Below the diagonal: rustfmt_nightly.parse.session uses a module listed above it, which is the healthy direction.
26→12 rustfmt_nightly.parse.session uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.parse.session uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.parse.session.ParseSess→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.parse.session uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.parse.session, while a change to rustfmt_nightly.parse.session can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.parse.session uses a module listed above it, which is the healthy direction.
26→13 rustfmt_nightly.parse.session uses rustfmt_nightly.ignore_path✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.parse.session uses a type in rustfmt_nightly.ignore_path.
- The types involved
rustfmt_nightly.parse.session.ParseSess→rustfmt_nightly.ignore_path.IgnorePathSetrustfmt_nightly.parse.session.session$module→rustfmt_nightly.ignore_path.IgnorePathSet
- Direction
- rustfmt_nightly.parse.session uses rustfmt_nightly.ignore_path, so a change to rustfmt_nightly.ignore_path can break rustfmt_nightly.parse.session, while a change to rustfmt_nightly.parse.session can't break rustfmt_nightly.ignore_path.
- Position
- Below the diagonal: rustfmt_nightly.parse.session uses a module listed above it, which is the healthy direction.
26→25 rustfmt_nightly.parse.session uses rustfmt_nightly.visitor✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.parse.session uses a type in rustfmt_nightly.visitor.
- The types involved
rustfmt_nightly.parse.session.ParseSess→rustfmt_nightly.visitor.SnippetProvider
- Direction
- rustfmt_nightly.parse.session uses rustfmt_nightly.visitor, so a change to rustfmt_nightly.visitor can break rustfmt_nightly.parse.session, while a change to rustfmt_nightly.parse.session can't break rustfmt_nightly.visitor.
- Position
- Below the diagonal: rustfmt_nightly.parse.session uses a module listed above it, which is the healthy direction.
27→12 rustfmt_nightly.rewrite uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.rewrite uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.rewrite.RewriteContext→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.rewrite uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.rewrite, while a change to rustfmt_nightly.rewrite can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.rewrite uses a module listed above it, which is the healthy direction.
27→15 rustfmt_nightly.rewrite uses rustfmt_nightly.shape✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.rewrite uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.rewrite.Rewrite→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.rewrite uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.rewrite, while a change to rustfmt_nightly.rewrite can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.rewrite uses a module listed above it, which is the healthy direction.
27→25 rustfmt_nightly.rewrite uses rustfmt_nightly.visitor✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.rewrite uses a type in rustfmt_nightly.visitor.
- The types involved
rustfmt_nightly.rewrite.RewriteContext→rustfmt_nightly.visitor.SnippetProvider
- Direction
- rustfmt_nightly.rewrite uses rustfmt_nightly.visitor, so a change to rustfmt_nightly.visitor can break rustfmt_nightly.rewrite, while a change to rustfmt_nightly.rewrite can't break rustfmt_nightly.visitor.
- Position
- Below the diagonal: rustfmt_nightly.rewrite uses a module listed above it, which is the healthy direction.
27→26 rustfmt_nightly.rewrite uses rustfmt_nightly.parse.session✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.rewrite uses a type in rustfmt_nightly.parse.session.
- The types involved
rustfmt_nightly.rewrite.RewriteContext→rustfmt_nightly.parse.session.ParseSess
- Direction
- rustfmt_nightly.rewrite uses rustfmt_nightly.parse.session, so a change to rustfmt_nightly.parse.session can break rustfmt_nightly.rewrite, while a change to rustfmt_nightly.rewrite can't break rustfmt_nightly.parse.session.
- Position
- Below the diagonal: rustfmt_nightly.rewrite uses a module listed above it, which is the healthy direction.
27→39 rustfmt_nightly.rewrite uses rustfmt_nightly part of a loop✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.rewrite uses a type in rustfmt_nightly.
- The types involved
rustfmt_nightly.rewrite.RewriteContext→rustfmt_nightly.FormatReport
- Direction
- rustfmt_nightly.rewrite uses rustfmt_nightly, so a change to rustfmt_nightly can break rustfmt_nightly.rewrite, while a change to rustfmt_nightly.rewrite can't break rustfmt_nightly.
- 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→15 rustfmt_nightly.attr uses rustfmt_nightly.shape✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.attr uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.attr.attr$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.attr uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.attr, while a change to rustfmt_nightly.attr can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.attr uses a module listed above it, which is the healthy direction.
28→22 rustfmt_nightly.attr uses rustfmt_nightly.stmt✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.attr uses a type in rustfmt_nightly.stmt.
- The types involved
rustfmt_nightly.attr.attr$module→rustfmt_nightly.stmt.Stmt
- Direction
- rustfmt_nightly.attr uses rustfmt_nightly.stmt, so a change to rustfmt_nightly.stmt can break rustfmt_nightly.attr, while a change to rustfmt_nightly.attr can't break rustfmt_nightly.stmt.
- Position
- Below the diagonal: rustfmt_nightly.attr uses a module listed above it, which is the healthy direction.
28→27 rustfmt_nightly.attr uses rustfmt_nightly.rewrite✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.attr uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.attr.attr$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.attr uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.attr, while a change to rustfmt_nightly.attr can't break rustfmt_nightly.rewrite.
- Position
- Below the diagonal: rustfmt_nightly.attr uses a module listed above it, which is the healthy direction.
29→1 rustfmt_nightly.closures uses check_diff✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.closures uses a type in check_diff.
- The types involved
rustfmt_nightly.closures.closures$module→check_diff.StyleEdition
- Direction
- rustfmt_nightly.closures uses check_diff, so a change to check_diff can break rustfmt_nightly.closures, while a change to rustfmt_nightly.closures can't break check_diff.
- Position
- Below the diagonal: rustfmt_nightly.closures uses a module listed above it, which is the healthy direction.
29→15 rustfmt_nightly.closures uses rustfmt_nightly.shape✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.closures uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.closures.closures$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.closures uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.closures, while a change to rustfmt_nightly.closures can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.closures uses a module listed above it, which is the healthy direction.
29→27 rustfmt_nightly.closures uses rustfmt_nightly.rewrite✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.closures uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.closures.closures$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.closures uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.closures, while a change to rustfmt_nightly.closures can't break rustfmt_nightly.rewrite.
- Position
- Below the diagonal: rustfmt_nightly.closures uses a module listed above it, which is the healthy direction.
30→3 rustfmt_nightly.items uses rustfmt_nightly.spanned✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.items uses a type in rustfmt_nightly.spanned.
- The types involved
rustfmt_nightly.items.Item→rustfmt_nightly.spanned.Spanned
- Direction
- rustfmt_nightly.items uses rustfmt_nightly.spanned, so a change to rustfmt_nightly.spanned can break rustfmt_nightly.items, while a change to rustfmt_nightly.items can't break rustfmt_nightly.spanned.
- Position
- Below the diagonal: rustfmt_nightly.items uses a module listed above it, which is the healthy direction.
30→9 rustfmt_nightly.items uses rustfmt_nightly.config.options✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.items uses a type in rustfmt_nightly.config.options.
- The types involved
rustfmt_nightly.items.items$module→rustfmt_nightly.config.options.BraceStyle
- Direction
- rustfmt_nightly.items uses rustfmt_nightly.config.options, so a change to rustfmt_nightly.config.options can break rustfmt_nightly.items, while a change to rustfmt_nightly.items can't break rustfmt_nightly.config.options.
- Position
- Below the diagonal: rustfmt_nightly.items uses a module listed above it, which is the healthy direction.
30→12 rustfmt_nightly.items uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.items uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.items.Item→rustfmt_nightly.git-rustfmt.main.Configrustfmt_nightly.items.items$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.items uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.items, while a change to rustfmt_nightly.items can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.items uses a module listed above it, which is the healthy direction.
30→15 rustfmt_nightly.items uses rustfmt_nightly.shape✕
- Connections
- 7 pairs of types, where a type in rustfmt_nightly.items uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.items.Item→rustfmt_nightly.shape.Shaperustfmt_nightly.items.OpaqueType→rustfmt_nightly.shape.Shaperustfmt_nightly.items.StructParts→rustfmt_nightly.shape.Indentrustfmt_nightly.items.TraitAliasBounds→rustfmt_nightly.shape.Shaperustfmt_nightly.items.TyAliasRewriteInfo→rustfmt_nightly.shape.Indentrustfmt_nightly.items.items$module→rustfmt_nightly.shape.Indentrustfmt_nightly.items.items$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.items uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.items, while a change to rustfmt_nightly.items can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.items uses a module listed above it, which is the healthy direction.
30→27 rustfmt_nightly.items uses rustfmt_nightly.rewrite✕
- Connections
- 10 pairs of types, where a type in rustfmt_nightly.items uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.items.FnSig→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.items.Item→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.items.Item→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.items.OpaqueType→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.items.OpaqueType→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.items.StructParts→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.items.TraitAliasBounds→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.items.TraitAliasBounds→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.items.TyAliasRewriteInfo→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.items.items$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.items uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.items, while a change to rustfmt_nightly.items can't break rustfmt_nightly.rewrite.
- Position
- Below the diagonal: rustfmt_nightly.items uses a module listed above it, which is the healthy direction.
31→3 rustfmt_nightly.matches uses rustfmt_nightly.spanned✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.matches uses a type in rustfmt_nightly.spanned.
- The types involved
rustfmt_nightly.matches.ArmWrapper→rustfmt_nightly.spanned.Spanned
- Direction
- rustfmt_nightly.matches uses rustfmt_nightly.spanned, so a change to rustfmt_nightly.spanned can break rustfmt_nightly.matches, while a change to rustfmt_nightly.matches can't break rustfmt_nightly.spanned.
- Position
- Below the diagonal: rustfmt_nightly.matches uses a module listed above it, which is the healthy direction.
31→12 rustfmt_nightly.matches uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.matches uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.matches.matches$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.matches uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.matches, while a change to rustfmt_nightly.matches can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.matches uses a module listed above it, which is the healthy direction.
31→15 rustfmt_nightly.matches uses rustfmt_nightly.shape✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.matches uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.matches.ArmWrapper→rustfmt_nightly.shape.Shaperustfmt_nightly.matches.matches$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.matches uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.matches, while a change to rustfmt_nightly.matches can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.matches uses a module listed above it, which is the healthy direction.
31→22 rustfmt_nightly.matches uses rustfmt_nightly.stmt✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.matches uses a type in rustfmt_nightly.stmt.
- The types involved
rustfmt_nightly.matches.matches$module→rustfmt_nightly.stmt.Stmt
- Direction
- rustfmt_nightly.matches uses rustfmt_nightly.stmt, so a change to rustfmt_nightly.stmt can break rustfmt_nightly.matches, while a change to rustfmt_nightly.matches can't break rustfmt_nightly.stmt.
- Position
- Below the diagonal: rustfmt_nightly.matches uses a module listed above it, which is the healthy direction.
31→27 rustfmt_nightly.matches uses rustfmt_nightly.rewrite✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly.matches uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.matches.ArmWrapper→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.matches.ArmWrapper→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.matches.matches$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.matches uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.matches, while a change to rustfmt_nightly.matches can't break rustfmt_nightly.rewrite.
- Position
- Below the diagonal: rustfmt_nightly.matches uses a module listed above it, which is the healthy direction.
32→8 rustfmt_nightly.parse.macros uses rustfmt_nightly.parse.parser✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.parse.macros uses a type in rustfmt_nightly.parse.parser.
- The types involved
rustfmt_nightly.parse.macros.macros$module→rustfmt_nightly.parse.parser.Parser
- Direction
- rustfmt_nightly.parse.macros uses rustfmt_nightly.parse.parser, so a change to rustfmt_nightly.parse.parser can break rustfmt_nightly.parse.macros, while a change to rustfmt_nightly.parse.macros can't break rustfmt_nightly.parse.parser.
- Position
- Below the diagonal: rustfmt_nightly.parse.macros uses a module listed above it, which is the healthy direction.
32→23 rustfmt_nightly.parse.macros uses rustfmt_nightly.macros✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.parse.macros uses a type in rustfmt_nightly.macros.
- The types involved
rustfmt_nightly.parse.macros.ParsedMacroArgs→rustfmt_nightly.macros.MacroArgrustfmt_nightly.parse.macros.macros$module→rustfmt_nightly.macros.MacroArg
- Direction
- rustfmt_nightly.parse.macros uses rustfmt_nightly.macros, so a change to rustfmt_nightly.macros can break rustfmt_nightly.parse.macros, while a change to rustfmt_nightly.parse.macros can't break rustfmt_nightly.macros.
- Position
- Below the diagonal: rustfmt_nightly.parse.macros uses a module listed above it, which is the healthy direction.
32→26 rustfmt_nightly.parse.macros uses rustfmt_nightly.parse.session✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.parse.macros uses a type in rustfmt_nightly.parse.session.
- The types involved
rustfmt_nightly.parse.macros.macros$module→rustfmt_nightly.parse.session.ParseSess
- Direction
- rustfmt_nightly.parse.macros uses rustfmt_nightly.parse.session, so a change to rustfmt_nightly.parse.session can break rustfmt_nightly.parse.macros, while a change to rustfmt_nightly.parse.macros can't break rustfmt_nightly.parse.session.
- Position
- Below the diagonal: rustfmt_nightly.parse.macros uses a module listed above it, which is the healthy direction.
32→27 rustfmt_nightly.parse.macros uses rustfmt_nightly.rewrite✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.parse.macros uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.parse.macros.macros$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.parse.macros uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.parse.macros, while a change to rustfmt_nightly.parse.macros can't break rustfmt_nightly.rewrite.
- Position
- Below the diagonal: rustfmt_nightly.parse.macros uses a module listed above it, which is the healthy direction.
33→3 rustfmt_nightly.patterns uses rustfmt_nightly.spanned✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.patterns uses a type in rustfmt_nightly.spanned.
- The types involved
rustfmt_nightly.patterns.TuplePatField→rustfmt_nightly.spanned.Spanned
- Direction
- rustfmt_nightly.patterns uses rustfmt_nightly.spanned, so a change to rustfmt_nightly.spanned can break rustfmt_nightly.patterns, while a change to rustfmt_nightly.patterns can't break rustfmt_nightly.spanned.
- Position
- Below the diagonal: rustfmt_nightly.patterns uses a module listed above it, which is the healthy direction.
33→15 rustfmt_nightly.patterns uses rustfmt_nightly.shape✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.patterns uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.patterns.TuplePatField→rustfmt_nightly.shape.Shaperustfmt_nightly.patterns.patterns$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.patterns uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.patterns, while a change to rustfmt_nightly.patterns can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.patterns uses a module listed above it, which is the healthy direction.
33→21 rustfmt_nightly.patterns uses rustfmt_nightly.overflow✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.patterns uses a type in rustfmt_nightly.overflow.
- The types involved
rustfmt_nightly.patterns.TuplePatField→rustfmt_nightly.overflow.IntoOverflowableItemrustfmt_nightly.patterns.TuplePatField→rustfmt_nightly.overflow.OverflowableItem
- Direction
- rustfmt_nightly.patterns uses rustfmt_nightly.overflow, so a change to rustfmt_nightly.overflow can break rustfmt_nightly.patterns, while a change to rustfmt_nightly.patterns can't break rustfmt_nightly.overflow.
- Position
- Below the diagonal: rustfmt_nightly.patterns uses a module listed above it, which is the healthy direction.
33→27 rustfmt_nightly.patterns uses rustfmt_nightly.rewrite✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly.patterns uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.patterns.TuplePatField→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.patterns.TuplePatField→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.patterns.patterns$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.patterns uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.patterns, while a change to rustfmt_nightly.patterns can't break rustfmt_nightly.rewrite.
- Position
- Below the diagonal: rustfmt_nightly.patterns uses a module listed above it, which is the healthy direction.
34→3 rustfmt_nightly.types uses rustfmt_nightly.spanned✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.types uses a type in rustfmt_nightly.spanned.
- The types involved
rustfmt_nightly.types.SegmentParam→rustfmt_nightly.spanned.Spanned
- Direction
- rustfmt_nightly.types uses rustfmt_nightly.spanned, so a change to rustfmt_nightly.spanned can break rustfmt_nightly.types, while a change to rustfmt_nightly.types can't break rustfmt_nightly.spanned.
- Position
- Below the diagonal: rustfmt_nightly.types uses a module listed above it, which is the healthy direction.
34→6 rustfmt_nightly.types uses rustfmt_nightly.config.lists✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.types uses a type in rustfmt_nightly.config.lists.
- The types involved
rustfmt_nightly.types.types$module→rustfmt_nightly.config.lists.DefinitiveListTactic
- Direction
- rustfmt_nightly.types uses rustfmt_nightly.config.lists, so a change to rustfmt_nightly.config.lists can break rustfmt_nightly.types, while a change to rustfmt_nightly.types can't break rustfmt_nightly.config.lists.
- Position
- Below the diagonal: rustfmt_nightly.types uses a module listed above it, which is the healthy direction.
34→15 rustfmt_nightly.types uses rustfmt_nightly.shape✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.types uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.types.SegmentParam→rustfmt_nightly.shape.Shaperustfmt_nightly.types.types$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.types uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.types, while a change to rustfmt_nightly.types can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.types uses a module listed above it, which is the healthy direction.
34→21 rustfmt_nightly.types uses rustfmt_nightly.overflow✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.types uses a type in rustfmt_nightly.overflow.
- The types involved
rustfmt_nightly.types.SegmentParam→rustfmt_nightly.overflow.IntoOverflowableItemrustfmt_nightly.types.SegmentParam→rustfmt_nightly.overflow.OverflowableItem
- Direction
- rustfmt_nightly.types uses rustfmt_nightly.overflow, so a change to rustfmt_nightly.overflow can break rustfmt_nightly.types, while a change to rustfmt_nightly.types can't break rustfmt_nightly.overflow.
- Position
- Below the diagonal: rustfmt_nightly.types uses a module listed above it, which is the healthy direction.
34→27 rustfmt_nightly.types uses rustfmt_nightly.rewrite✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly.types uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.types.SegmentParam→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.types.SegmentParam→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.types.types$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.types uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.types, while a change to rustfmt_nightly.types can't break rustfmt_nightly.rewrite.
- Position
- Below the diagonal: rustfmt_nightly.types uses a module listed above it, which is the healthy direction.
35→12 rustfmt_nightly.comment uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.comment uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.comment.CommentRewrite→rustfmt_nightly.git-rustfmt.main.Configrustfmt_nightly.comment.comment$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.comment uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.comment, while a change to rustfmt_nightly.comment can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.comment uses a module listed above it, which is the healthy direction.
35→15 rustfmt_nightly.comment uses rustfmt_nightly.shape✕
- Connections
- 4 pairs of types, where a type in rustfmt_nightly.comment uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.comment.CommentRewrite→rustfmt_nightly.shape.Indentrustfmt_nightly.comment.CommentRewrite→rustfmt_nightly.shape.Shaperustfmt_nightly.comment.comment$module→rustfmt_nightly.shape.Indentrustfmt_nightly.comment.comment$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.comment uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.comment, while a change to rustfmt_nightly.comment can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.comment uses a module listed above it, which is the healthy direction.
35→27 rustfmt_nightly.comment uses rustfmt_nightly.rewrite✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.comment uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.comment.comment$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.comment uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.comment, while a change to rustfmt_nightly.comment can't break rustfmt_nightly.rewrite.
- Position
- Below the diagonal: rustfmt_nightly.comment uses a module listed above it, which is the healthy direction.
35→30 rustfmt_nightly.comment uses rustfmt_nightly.items✕
- Connections
- 4 pairs of types, where a type in rustfmt_nightly.comment uses a type in rustfmt_nightly.items.
- The types involved
rustfmt_nightly.comment.CommentCodeSlices→rustfmt_nightly.items.Itemrustfmt_nightly.comment.CommentReducer→rustfmt_nightly.items.Itemrustfmt_nightly.comment.LineClasses→rustfmt_nightly.items.Itemrustfmt_nightly.comment.UngroupedCommentCodeSlices→rustfmt_nightly.items.Item
- Direction
- rustfmt_nightly.comment uses rustfmt_nightly.items, so a change to rustfmt_nightly.items can break rustfmt_nightly.comment, while a change to rustfmt_nightly.comment can't break rustfmt_nightly.items.
- Position
- Below the diagonal: rustfmt_nightly.comment uses a module listed above it, which is the healthy direction.
36→26 rustfmt_nightly.modules.visitor uses rustfmt_nightly.parse.session✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.modules.visitor uses a type in rustfmt_nightly.parse.session.
- The types involved
rustfmt_nightly.modules.visitor.CfgIfVisitor→rustfmt_nightly.parse.session.ParseSessrustfmt_nightly.modules.visitor.CfgSelectVisitor→rustfmt_nightly.parse.session.ParseSess
- Direction
- rustfmt_nightly.modules.visitor uses rustfmt_nightly.parse.session, so a change to rustfmt_nightly.parse.session can break rustfmt_nightly.modules.visitor, while a change to rustfmt_nightly.modules.visitor can't break rustfmt_nightly.parse.session.
- Position
- Below the diagonal: rustfmt_nightly.modules.visitor uses a module listed above it, which is the healthy direction.
36→28 rustfmt_nightly.modules.visitor uses rustfmt_nightly.attr✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.modules.visitor uses a type in rustfmt_nightly.attr.
- The types involved
rustfmt_nightly.modules.visitor.PathVisitor→rustfmt_nightly.attr.MetaVisitor
- Direction
- rustfmt_nightly.modules.visitor uses rustfmt_nightly.attr, so a change to rustfmt_nightly.attr can break rustfmt_nightly.modules.visitor, while a change to rustfmt_nightly.modules.visitor can't break rustfmt_nightly.attr.
- Position
- Below the diagonal: rustfmt_nightly.modules.visitor uses a module listed above it, which is the healthy direction.
36→30 rustfmt_nightly.modules.visitor uses rustfmt_nightly.items✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.modules.visitor uses a type in rustfmt_nightly.items.
- The types involved
rustfmt_nightly.modules.visitor.ModItem→rustfmt_nightly.items.Item
- Direction
- rustfmt_nightly.modules.visitor uses rustfmt_nightly.items, so a change to rustfmt_nightly.items can break rustfmt_nightly.modules.visitor, while a change to rustfmt_nightly.modules.visitor can't break rustfmt_nightly.items.
- Position
- Below the diagonal: rustfmt_nightly.modules.visitor uses a module listed above it, which is the healthy direction.
37→5 rustfmt_nightly.formatting uses rustfmt_nightly.config.file_lines✕
- Connections
- 6 pairs of types, where a type in rustfmt_nightly.formatting uses a type in rustfmt_nightly.config.file_lines.
- The types involved
rustfmt_nightly.formatting.FormatContext→rustfmt_nightly.config.file_lines.FileNamerustfmt_nightly.formatting.FormatHandler→rustfmt_nightly.config.file_lines.FileNamerustfmt_nightly.formatting.FormatLines→rustfmt_nightly.config.file_lines.FileNamerustfmt_nightly.formatting.FormatLines→rustfmt_nightly.config.file_lines.Rangerustfmt_nightly.formatting.FormattingError→rustfmt_nightly.config.file_lines.Rangerustfmt_nightly.formatting.formatting$module→rustfmt_nightly.config.file_lines.FileName
- Direction
- rustfmt_nightly.formatting uses rustfmt_nightly.config.file_lines, so a change to rustfmt_nightly.config.file_lines can break rustfmt_nightly.formatting, while a change to rustfmt_nightly.formatting can't break rustfmt_nightly.config.file_lines.
- Position
- Below the diagonal: rustfmt_nightly.formatting uses a module listed above it, which is the healthy direction.
37→11 rustfmt_nightly.formatting uses rustfmt_nightly.modules✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.formatting uses a type in rustfmt_nightly.modules.
- The types involved
rustfmt_nightly.formatting.FormatContext→rustfmt_nightly.modules.Modulerustfmt_nightly.formatting.formatting$module→rustfmt_nightly.modules.Module
- Direction
- rustfmt_nightly.formatting uses rustfmt_nightly.modules, so a change to rustfmt_nightly.modules can break rustfmt_nightly.formatting, while a change to rustfmt_nightly.formatting can't break rustfmt_nightly.modules.
- Position
- Below the diagonal: rustfmt_nightly.formatting uses a module listed above it, which is the healthy direction.
37→12 rustfmt_nightly.formatting uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly.formatting uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.formatting.FormatContext→rustfmt_nightly.git-rustfmt.main.Configrustfmt_nightly.formatting.FormatLines→rustfmt_nightly.git-rustfmt.main.Configrustfmt_nightly.formatting.formatting$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.formatting uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.formatting, while a change to rustfmt_nightly.formatting can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.formatting uses a module listed above it, which is the healthy direction.
37→26 rustfmt_nightly.formatting uses rustfmt_nightly.parse.session✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly.formatting uses a type in rustfmt_nightly.parse.session.
- The types involved
rustfmt_nightly.formatting.FormatContext→rustfmt_nightly.parse.session.ParseSessrustfmt_nightly.formatting.FormatHandler→rustfmt_nightly.parse.session.ParseSessrustfmt_nightly.formatting.FormattingError→rustfmt_nightly.parse.session.ParseSess
- Direction
- rustfmt_nightly.formatting uses rustfmt_nightly.parse.session, so a change to rustfmt_nightly.parse.session can break rustfmt_nightly.formatting, while a change to rustfmt_nightly.formatting can't break rustfmt_nightly.parse.session.
- Position
- Below the diagonal: rustfmt_nightly.formatting uses a module listed above it, which is the healthy direction.
37→35 rustfmt_nightly.formatting uses rustfmt_nightly.comment✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.formatting uses a type in rustfmt_nightly.comment.
- The types involved
rustfmt_nightly.formatting.FormatLines→rustfmt_nightly.comment.FullCodeCharKind
- Direction
- rustfmt_nightly.formatting uses rustfmt_nightly.comment, so a change to rustfmt_nightly.comment can break rustfmt_nightly.formatting, while a change to rustfmt_nightly.formatting can't break rustfmt_nightly.comment.
- Position
- Below the diagonal: rustfmt_nightly.formatting uses a module listed above it, which is the healthy direction.
37→39 rustfmt_nightly.formatting uses rustfmt_nightly part of a loop✕
- Connections
- 6 pairs of types, where a type in rustfmt_nightly.formatting uses a type in rustfmt_nightly.
- The types involved
rustfmt_nightly.formatting.FormatContext→rustfmt_nightly.FormatReportrustfmt_nightly.formatting.FormatHandler→rustfmt_nightly.FormatReportrustfmt_nightly.formatting.FormatLines→rustfmt_nightly.ErrorKindrustfmt_nightly.formatting.FormattingError→rustfmt_nightly.ErrorKindrustfmt_nightly.formatting.formatting$module→rustfmt_nightly.FormatReportrustfmt_nightly.formatting.formatting$module→rustfmt_nightly.Input
- Direction
- rustfmt_nightly.formatting uses rustfmt_nightly, so a change to rustfmt_nightly can break rustfmt_nightly.formatting, while a change to rustfmt_nightly.formatting can't break rustfmt_nightly.
- 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.
38→12 rustfmt_nightly.utils uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.utils uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.utils.utils$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.utils uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.utils, while a change to rustfmt_nightly.utils can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.utils uses a module listed above it, which is the healthy direction.
38→15 rustfmt_nightly.utils uses rustfmt_nightly.shape✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.utils uses a type in rustfmt_nightly.shape.
- The types involved
rustfmt_nightly.utils.utils$module→rustfmt_nightly.shape.Indentrustfmt_nightly.utils.utils$module→rustfmt_nightly.shape.Shape
- Direction
- rustfmt_nightly.utils uses rustfmt_nightly.shape, so a change to rustfmt_nightly.shape can break rustfmt_nightly.utils, while a change to rustfmt_nightly.utils can't break rustfmt_nightly.shape.
- Position
- Below the diagonal: rustfmt_nightly.utils uses a module listed above it, which is the healthy direction.
38→22 rustfmt_nightly.utils uses rustfmt_nightly.stmt✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.utils uses a type in rustfmt_nightly.stmt.
- The types involved
rustfmt_nightly.utils.utils$module→rustfmt_nightly.stmt.Stmt
- Direction
- rustfmt_nightly.utils uses rustfmt_nightly.stmt, so a change to rustfmt_nightly.stmt can break rustfmt_nightly.utils, while a change to rustfmt_nightly.utils can't break rustfmt_nightly.stmt.
- Position
- Below the diagonal: rustfmt_nightly.utils uses a module listed above it, which is the healthy direction.
38→27 rustfmt_nightly.utils uses rustfmt_nightly.rewrite✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.utils uses a type in rustfmt_nightly.rewrite.
- The types involved
rustfmt_nightly.utils.utils$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- rustfmt_nightly.utils uses rustfmt_nightly.rewrite, so a change to rustfmt_nightly.rewrite can break rustfmt_nightly.utils, while a change to rustfmt_nightly.utils can't break rustfmt_nightly.rewrite.
- Position
- Below the diagonal: rustfmt_nightly.utils uses a module listed above it, which is the healthy direction.
38→35 rustfmt_nightly.utils uses rustfmt_nightly.comment✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.utils uses a type in rustfmt_nightly.comment.
- The types involved
rustfmt_nightly.utils.utils$module→rustfmt_nightly.comment.FullCodeCharKind
- Direction
- rustfmt_nightly.utils uses rustfmt_nightly.comment, so a change to rustfmt_nightly.comment can break rustfmt_nightly.utils, while a change to rustfmt_nightly.utils can't break rustfmt_nightly.comment.
- Position
- Below the diagonal: rustfmt_nightly.utils uses a module listed above it, which is the healthy direction.
39→5 rustfmt_nightly uses rustfmt_nightly.config.file_lines✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly uses a type in rustfmt_nightly.config.file_lines.
- The types involved
rustfmt_nightly.FormatReport→rustfmt_nightly.config.file_lines.FileNamerustfmt_nightly.Input→rustfmt_nightly.config.file_lines.FileNamerustfmt_nightly.Session→rustfmt_nightly.config.file_lines.FileName
- Direction
- rustfmt_nightly uses rustfmt_nightly.config.file_lines, so a change to rustfmt_nightly.config.file_lines can break rustfmt_nightly, while a change to rustfmt_nightly can't break rustfmt_nightly.config.file_lines.
- Position
- Below the diagonal: rustfmt_nightly uses a module listed above it, which is the healthy direction.
39→12 rustfmt_nightly uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.Session→rustfmt_nightly.git-rustfmt.main.Configrustfmt_nightly.rustfmt_nightly$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly, while a change to rustfmt_nightly can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly uses a module listed above it, which is the healthy direction.
39→26 rustfmt_nightly uses rustfmt_nightly.parse.session✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly uses a type in rustfmt_nightly.parse.session.
- The types involved
rustfmt_nightly.Session→rustfmt_nightly.parse.session.ParseSess
- Direction
- rustfmt_nightly uses rustfmt_nightly.parse.session, so a change to rustfmt_nightly.parse.session can break rustfmt_nightly, while a change to rustfmt_nightly can't break rustfmt_nightly.parse.session.
- Position
- Below the diagonal: rustfmt_nightly uses a module listed above it, which is the healthy direction.
39→37 rustfmt_nightly uses rustfmt_nightly.formatting✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly uses a type in rustfmt_nightly.formatting.
- The types involved
rustfmt_nightly.FormatReport→rustfmt_nightly.formatting.FormattingErrorrustfmt_nightly.Session→rustfmt_nightly.formatting.FormatHandlerrustfmt_nightly.Session→rustfmt_nightly.formatting.ReportedErrors
- Direction
- rustfmt_nightly uses rustfmt_nightly.formatting, so a change to rustfmt_nightly.formatting can break rustfmt_nightly, while a change to rustfmt_nightly can't break rustfmt_nightly.formatting.
- Position
- Below the diagonal: rustfmt_nightly uses a module listed above it, which is the healthy direction.
40→1 rustfmt_nightly.bin.main uses check_diff✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.bin.main uses a type in check_diff.
- The types involved
rustfmt_nightly.bin.main.GetOptsOptions→check_diff.Editionrustfmt_nightly.bin.main.GetOptsOptions→check_diff.StyleEdition
- Direction
- rustfmt_nightly.bin.main uses check_diff, so a change to check_diff can break rustfmt_nightly.bin.main, while a change to rustfmt_nightly.bin.main can't break check_diff.
- Position
- Below the diagonal: rustfmt_nightly.bin.main uses a module listed above it, which is the healthy direction.
40→5 rustfmt_nightly.bin.main uses rustfmt_nightly.config.file_lines✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.bin.main uses a type in rustfmt_nightly.config.file_lines.
- The types involved
rustfmt_nightly.bin.main.GetOptsOptions→rustfmt_nightly.config.file_lines.FileLines
- Direction
- rustfmt_nightly.bin.main uses rustfmt_nightly.config.file_lines, so a change to rustfmt_nightly.config.file_lines can break rustfmt_nightly.bin.main, while a change to rustfmt_nightly.bin.main can't break rustfmt_nightly.config.file_lines.
- Position
- Below the diagonal: rustfmt_nightly.bin.main uses a module listed above it, which is the healthy direction.
40→9 rustfmt_nightly.bin.main uses rustfmt_nightly.config.options✕
- Connections
- 4 pairs of types, where a type in rustfmt_nightly.bin.main uses a type in rustfmt_nightly.config.options.
- The types involved
rustfmt_nightly.bin.main.GetOptsOptions→rustfmt_nightly.config.options.CliOptionsrustfmt_nightly.bin.main.GetOptsOptions→rustfmt_nightly.config.options.Colorrustfmt_nightly.bin.main.GetOptsOptions→rustfmt_nightly.config.options.EmitModerustfmt_nightly.bin.main.GetOptsOptions→rustfmt_nightly.config.options.Version
- Direction
- rustfmt_nightly.bin.main uses rustfmt_nightly.config.options, so a change to rustfmt_nightly.config.options can break rustfmt_nightly.bin.main, while a change to rustfmt_nightly.bin.main can't break rustfmt_nightly.config.options.
- Position
- Below the diagonal: rustfmt_nightly.bin.main uses a module listed above it, which is the healthy direction.
40→12 rustfmt_nightly.bin.main uses rustfmt_nightly.git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly.bin.main uses a type in rustfmt_nightly.git-rustfmt.main.
- The types involved
rustfmt_nightly.bin.main.GetOptsOptions→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_nightly.bin.main uses rustfmt_nightly.git-rustfmt.main, so a change to rustfmt_nightly.git-rustfmt.main can break rustfmt_nightly.bin.main, while a change to rustfmt_nightly.bin.main can't break rustfmt_nightly.git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly.bin.main uses a module listed above it, which is the healthy direction.
40→39 rustfmt_nightly.bin.main uses rustfmt_nightly✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly.bin.main uses a type in rustfmt_nightly.
- The types involved
rustfmt_nightly.bin.main.main$module→rustfmt_nightly.Inputrustfmt_nightly.bin.main.main$module→rustfmt_nightly.Session
- Direction
- rustfmt_nightly.bin.main uses rustfmt_nightly, so a change to rustfmt_nightly can break rustfmt_nightly.bin.main, while a change to rustfmt_nightly.bin.main can't break rustfmt_nightly.
- Position
- Below the diagonal: rustfmt_nightly.bin.main uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
| A05:2025 — Injection | 3 | High / Critical |
Roadmap
First, replace interpolated log messages with structured logging to ensure consistent observability. Next, refactor the three most complex functions to reduce cyclomatic complexity, then address the single missing architecture decision record. Finally, resolve the 97 explicit debt comments, prioritizing the files with the highest concentration of technical debt.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.8 pts | Low | ADR Quality |
| Interpolated log message defeats structured logging | +5.2 pts | Medium | Structured logging |
| Resolve the 97 FixmeComment finding(s) in Explicit Debt — start with items.rs (13), cfg_select.rs (11), expr.rs (8). | +2.5 pts | Medium | Explicit Debt |
| Bring the 30 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with rustfmt_nightly::expr::format_expr (cyclomatic 58), rustfmt_nightly::lists::write_list (cyclomatic 58), rustfmt_nightly::items::rewrite_fn_base (cyclomatic 47). | +3.3 pts | High | Cyclomatic Complexity |
| Resolve the 56 TodoComment finding(s) in Explicit Debt — start with struct_field_doc_comment.rs (8), visitor.rs (6), issue-2896.rs (4). | +1.4 pts | Medium | Explicit Debt |
| 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. | +2.5 pts | Medium | Architecture documentation |
| Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with rustfmt_nightly::lists::write_list (cognitive 122), rustfmt_nightly::items::rewrite_fn_base (cognitive 97), CommentRewrite::handle_line (cognitive 69). | +1.9 pts | High | Cognitive Complexity |
| Resolve the 12 FileTooLong finding(s) in God Classes — start with items.rs, expr.rs, comment.rs. | +1.4 pts | High | God Classes |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/expr.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/lists.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/items.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/comment.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| src/macros.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/visitor.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/types.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| src/imports.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/overflow.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/chains.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/string.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/missed_spans.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| src/header.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| tests/target/cfg_select/cfg_select.rs | 6.5 | Mixed | Explicit Debt: FixmeComment |
| tests/source/cfg_select/cfg_select.rs | 6.5 | Mixed | Explicit Debt: FixmeComment |
| tests/target/struct_field_doc_comment.rs | 6.6 | Mixed | Explicit Debt: TodoComment |
| tests/source/struct_field_doc_comment.rs | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/config/options.rs | 6.6 | Mixed | Explicit Debt: FixmeComment |
| src/parse/macros/cfg_select.rs | 6.7 | Mixed | Explicit Debt: FixmeComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 48 of 48 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 48 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, 356 of 384 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 67 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's 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.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's 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.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and 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 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
30 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was rustfmt_nightly::expr::format_expr at 58.
What to do
- Bring the 30 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with rustfmt_nightly::expr::format_expr (cyclomatic 58), rustfmt_nightly::lists::write_list (cyclomatic 58), rustfmt_nightly::items::rewrite_fn_base (cyclomatic 47). — 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 30 together lifts Cyclomatic Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
62 method(s) exceeded the cognitive complexity threshold of 15; the worst was rustfmt_nightly::lists::write_list at 122.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with rustfmt_nightly::lists::write_list (cognitive 122), rustfmt_nightly::items::rewrite_fn_base (cognitive 97), CommentRewrite::handle_line (cognitive 69). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 3.1 to about 4.8/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
20 god class(es) detected.
What to do
- Resolve the 12 FileTooLong finding(s) in God Classes — start with items.rs, expr.rs, comment.rs. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 3 FunctionTooLong finding(s) in God Classes — start with lists.rs, macros.rs, types.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with comment.rs (2), modules.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
16 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with imports.rs, items.rs, rustfmt_diff.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with missed_spans.rs, source_map.rs, cfg_if.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with modules.rs, sort.rs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
4 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 3 of the 4 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
1 of 53 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with lists.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
381 test methods: 291 unit, 90 integration, 0 BDD, 0 e2e. The Rust suite contributes 381 `#[test]` function(s) across 67 file(s) declaring at least one; its unit/integration split is Cargo's own — 36 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
16 outdated, 0 yanked direct Cargo dependencies. 28 of 33 direct crates were graded against crates.io (0 not published there, 5 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 110 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under Apache-2.0 OR MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/expr.rs (12×58=696); src/macros.rs (17×38=646); src/bin/main.rs (7×30=210) Repeated repair below the complexity floor: src/parse/macros/cfg_select.rs (7 of 10 changes were fixes)
What to do
- Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with expr.rs, macros.rs, main.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with cfg_select.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/rustfmt_diff.rs. Counted over 61 of the 81 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
158 deducted task-comment markers across 33993 LoC (0.4/KLoC) → score 9.1. 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 97 FixmeComment finding(s) in Explicit Debt — start with items.rs (13), cfg_select.rs (11), expr.rs (8). — One of this dimension's main actionable groups (97 warning-level).
- Resolve the 56 TodoComment finding(s) in Explicit Debt — start with struct_field_doc_comment.rs (8), visitor.rs (6), issue-2896.rs (4). — One of this dimension's main actionable groups (56 warning-level).
- Resolve the 5 HackComment finding(s) in Explicit Debt — start with comment.rs, expr.rs, imports.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 4 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 1 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
12 of 61 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/config/file_lines.rs. Counted over 61 of the 81 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 12 Orphaned file finding(s) in Knowledge Freshness — start with main.rs (2), file_lines.rs, shape.rs. — One of this dimension's main actionable groups (12 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 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
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 3 of 3 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF1 · Benchmark discipline
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug!` at line 152 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/attr.rs:152
- `debug!` at line 150 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/chains.rs:150
- `debug!` 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: `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/chains.rs:560
- `debug!` at line 43 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/closures.rs:43
- `debug!` at line 363 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/closures.rs:363
- `trace!` at line 162 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/comment.rs:162
- `debug!` at line 1813 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/comment.rs:1813
- `debug!` at line 936 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/expr.rs:936
- `debug!` at line 1201 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/expr.rs:1201
- `debug!` at line 1669 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/expr.rs:1669
- `debug!` at line 1819 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/expr.rs:1819
- `debug!` at line 2038 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/expr.rs:2038
- `debug!` at line 2123 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/expr.rs:2123
- `debug!` at line 476 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/formatting.rs:476
- `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/items.rs:56
- `debug!` at line 2549 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/items.rs:2549
- `debug!` at line 2943 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/items.rs:2943
- `debug!` at line 592 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/macros.rs:592
- `debug!` at line 1094 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/macros.rs:1094
- `debug!` at line 1146 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/macros.rs:1146
- `debug!` at line 1421 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/macros.rs:1421
- `debug!` at line 614 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/matches.rs:614
- `debug!` at line 159 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/missed_spans.rs:159
- `debug!` at line 198 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/missed_spans.rs:198
- `warn!` at line 484 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/modules.rs:484
- `debug!` at line 625 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/overflow.rs:625
- `debug!` at line 641 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/overflow.rs:641
- `debug!` at line 328 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/types.rs:328
- `debug!` at line 1102 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/types.rs:1102
- `debug!` at line 119 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/visitor.rs:119
- `debug!` at line 228 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/visitor.rs:228
- `debug!` at line 289 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/visitor.rs:289
- `debug!` at line 38 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/modules/visitor.rs:38
- `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`. (×2) — src/modules/visitor.rs:98, src/format-diff/main.rs:98
- `debug!` at line 33 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/git-rustfmt/main.rs:33
- `debug!` at line 120 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/git-rustfmt/main.rs:120
- `debug!` at line 203 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/git-rustfmt/main.rs:203
- `debug!` at line 205 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/git-rustfmt/main.rs:205
- `debug!` at line 97 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/format-diff/main.rs:97
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 59% | Adequate — gated by D2, X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 93% | Exemplary | Strongest area. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 67% | Adequate | Acceptable, with room to improve. |
| Security | 76% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- 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 — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — 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 — ~57200 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 — Naming consistency is measured on C# only; Rust, html not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (5 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 82 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not 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
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 3 finding(s)
- REDACTED
- REDACTED
- REDACTED
Serious — 297 finding(s)
- FixmeComment tests/target/enum.rs:139
- FixmeComment tests/source/enum.rs:98
- FixmeComment tests/target/expr.rs:173
- FixmeComment tests/source/expr.rs:124
- FixmeComment tests/target/issue-539.rs:2
- FixmeComment tests/target/issue-683.rs:2
- FixmeComment tests/target/multiple.rs:5
- FixmeComment tests/source/multiple.rs:5
- FixmeComment tests/target/statements.rs:1
- FixmeComment tests/source/statements.rs:1
- FixmeComment tests/target/structs.rs:213
- FixmeComment tests/target/configs/struct_field_align_threshold/20.rs:226
- FixmeComment tests/source/structs.rs:175
- FixmeComment tests/source/configs/struct_field_align_threshold/20.rs:191
- FixmeComment tests/target/issue-2917/packed_simd.rs:21
- FixmeComment tests/source/issue-2917/packed_simd.rs:21
- FixmeComment tests/target/configs/indent_style/block_call.rs:97
- FixmeComment tests/source/configs/indent_style/block_call.rs:77
- FixmeComment tests/target/cfg_select/cfg_select.rs:265
- FixmeComment tests/target/cfg_select/cfg_select.rs:271
- FixmeComment tests/target/cfg_select/cfg_select.rs:694
- FixmeComment tests/target/cfg_select/cfg_select.rs:700
- FixmeComment tests/source/cfg_select/cfg_select.rs:314
- FixmeComment tests/source/cfg_select/cfg_select.rs:321
- FixmeComment tests/source/cfg_select/cfg_select.rs:748
- TodoComment tests/target/enum.rs:150
- TodoComment tests/source/enum.rs:108
- TodoComment tests/target/issue-2896.rs:33
- TodoComment tests/source/issue-2896.rs:36
- TodoComment tests/target/issue-2896.rs:68
- TodoComment tests/source/issue-2896.rs:69
- TodoComment tests/target/issue-691.rs:7
- TodoComment tests/target/match.rs:138
- TodoComment tests/source/match.rs:139
- TodoComment tests/target/match.rs:196
- TodoComment tests/source/match.rs:197
- TodoComment tests/target/struct_field_doc_comment.rs:7
- TodoComment tests/target/struct_field_doc_comment.rs:37
- TodoComment tests/target/struct_field_doc_comment.rs:58
- TodoComment tests/target/struct_field_doc_comment.rs:67
- TodoComment tests/source/struct_field_doc_comment.rs:6
- TodoComment tests/source/struct_field_doc_comment.rs:38
- TodoComment tests/source/struct_field_doc_comment.rs:61
- TodoComment tests/source/struct_field_doc_comment.rs:70
- TodoComment tests/target/structs.rs:47
- TodoComment tests/target/unions.rs:28
- TodoComment tests/target/configs/struct_field_align_threshold/20.rs:60
- TodoComment tests/source/structs.rs:44
- TodoComment tests/source/unions.rs:28
- TodoComment tests/source/configs/struct_field_align_threshold/20.rs:60
- rustfmt_nightly::lists::write_list (cognitive 122) src/lists.rs:264
- rustfmt_nightly::items::rewrite_fn_base (cognitive 97) src/items.rs:2483
- rustfmt_nightly::macros::rewrite_macro_inner (cognitive 58) src/macros.rs:197
- rustfmt_nightly::expr::format_expr (cognitive 46) src/expr.rs:86
- rustfmt_nightly::matches::rewrite_match_body (cognitive 41) src/matches.rs:397
- rustfmt_nightly::items::format_trait (cognitive 37) src/items.rs:1173
- rustfmt_nightly::parse::macros::parse_macro_args (cognitive 37) src/parse/macros/mod.rs:100
- rustfmt_nightly::types::join_bounds_inner (cognitive 37) src/types.rs:1171
- rustfmt_nightly::comment::identify_comment (cognitive 36) src/comment.rs:255
- rustfmt_nightly::string::break_string (cognitive 33) src/string.rs:229
- rustfmt_nightly::parse::macros::parse_macro_arg (cognitive 32) src/parse/macros/mod.rs:24
- rustfmt_nightly::items::format_impl (cognitive 29) src/items.rs:807
- rustfmt_nightly::sort::version_sort (cognitive 28) src/sort.rs:136
- rustfmt_nightly::string::rewrite_string (cognitive 28) src/string.rs:64
- rustfmt_nightly::bin::main::format (cognitive 27) src/bin/main.rs:341
- rustfmt_nightly::comment::combine_strs_with_missing_comments (cognitive 27) src/comment.rs:154
- rustfmt_nightly::parse::macros::cfg_if::parse_cfg_if_inner (cognitive 24) src/parse/macros/cfg_if.rs:27
- rustfmt_nightly::rustfmt_diff::make_diff (cognitive 24) src/rustfmt_diff.rs:180
- rustfmt_nightly::items::format_struct_struct (cognitive 23) src/items.rs:1447
- rustfmt_nightly::matches::rewrite_match (cognitive 23) src/matches.rs:73
- rustfmt_nightly::items::rewrite_ty (cognitive 22) src/items.rs:1767
- rustfmt_nightly::patterns::rewrite_struct_pat (cognitive 22) src/patterns.rs:344
- rustfmt_nightly::format_code_block (cognitive 21) src/lib.rs:346
- rustfmt_nightly::imports::merge_use_trees_inner (cognitive 21) src/imports.rs:847
- rustfmt_nightly::items::format_impl_ref_and_type (cognitive 21) src/items.rs:958
- rustfmt_nightly::expr::format_expr (cyclomatic 58) src/expr.rs:86
- rustfmt_nightly::lists::write_list (cyclomatic 58) src/lists.rs:264
- rustfmt_nightly::items::rewrite_fn_base (cyclomatic 47) src/items.rs:2483
- rustfmt_nightly::macros::rewrite_macro_inner (cyclomatic 38) src/macros.rs:197
- rustfmt_nightly::matches::rewrite_match_body (cyclomatic 33) src/matches.rs:397
- rustfmt_nightly::types::join_bounds_inner (cyclomatic 28) src/types.rs:1171
- rustfmt_nightly::items::format_trait (cyclomatic 24) src/items.rs:1173
- rustfmt_nightly::comment::identify_comment (cyclomatic 21) src/comment.rs:255
- rustfmt_nightly::items::format_impl (cyclomatic 21) src/items.rs:807
- rustfmt_nightly::string::break_string (cyclomatic 20) src/string.rs:229
- rustfmt_nightly::comment::combine_strs_with_missing_comments (cyclomatic 19) src/comment.rs:154
- rustfmt_nightly::expr::can_be_overflowed_expr (cyclomatic 18) src/expr.rs:1578
- rustfmt_nightly::comment::comment_style (cyclomatic 17) src/comment.rs:114
- rustfmt_nightly::parse::macros::parse_macro_arg (cyclomatic 17) src/parse/macros/mod.rs:24
- rustfmt_nightly::sort::version_sort (cyclomatic 17) src/sort.rs:136
- rustfmt_nightly::expr::rewrite_struct_lit (cyclomatic 16) src/expr.rs:1809
- FileTooLong: src/items.rs src/items.rs
- FileTooLong: src/expr.rs src/expr.rs
- FileTooLong: src/comment.rs src/comment.rs
- FileTooLong: src/macros.rs src/macros.rs
- FileTooLong: src/types.rs src/types.rs
- FileTooLong: src/visitor.rs src/visitor.rs
- FileTooLong: src/imports.rs src/imports.rs
- FileTooLong: src/chains.rs src/chains.rs
- FileTooLong: src/lists.rs src/lists.rs
- FileTooLong: src/lib.rs check_diff/src/lib.rs
- FileTooLong: src/overflow.rs src/overflow.rs
- FileTooLong: bin/main.rs src/bin/main.rs
- Hotspot: src/expr.rs src/expr.rs:86
- Hotspot: src/macros.rs src/macros.rs:197
- Hotspot: src/bin/main.rs src/bin/main.rs:564
- Hotspot: src/comment.rs src/comment.rs:713
- Hotspot: src/chains.rs src/chains.rs:387
- Hotspot: src/lists.rs src/lists.rs:264
- FmtVisitor::close_block (cognitive 48) src/visitor.rs:263
- FmtVisitor::visit_item (cognitive 25) src/visitor.rs:443
- FmtVisitor::visit_stmt (cognitive 20) src/visitor.rs:118
- FmtVisitor::visit_impl_items (cognitive 19) src/items.rs:736
- FmtVisitor::process_comment (cognitive 17) src/missed_spans.rs:235
- FmtVisitor::process_missing_code (cognitive 16) src/missed_spans.rs:329
- HackComment src/comment.rs:1473
- HackComment src/expr.rs:701
- HackComment src/imports.rs:556
- HackComment src/missed_spans.rs:39
- HackComment src/types.rs:292
- FmtVisitor::visit_item (cyclomatic 29) src/visitor.rs:443
- FmtVisitor::visit_impl_items (cyclomatic 25) src/items.rs:736
- FmtVisitor::close_block (cyclomatic 22) src/visitor.rs:263
- UseTree::normalize (cognitive 30) src/imports.rs:554
- UseTree::from_ast (cognitive 23) src/imports.rs:423
- UseTree::flatten (cognitive 18) src/imports.rs:699
- FunctionTooLong: rustfmt_nightly::lists::write_list src/lists.rs:264
- FunctionTooLong: rustfmt_nightly::macros::rewrite_macro_inner src/macros.rs:197
- FunctionTooLong: rustfmt_nightly::types::join_bounds_inner src/types.rs:1171
- MethodTooLong: CommentRewrite.handle_line src/comment.rs:713
- MethodTooLong: CharClasses.next src/comment.rs:1394
- MethodTooLong: ModResolver.find_external_module src/modules.rs:361
- Duplicated block (11 lines × 2) src/imports.rs:363
- Duplicated block (11 lines × 2) src/items.rs:863
- Duplicated block (11 lines × 2) src/rustfmt_diff.rs:191
- Duplicated block (6 lines × 2) src/missed_spans.rs:282
- Duplicated block (6 lines × 2) src/source_map.rs:40
- Duplicated block (6 lines × 2) src/parse/macros/cfg_if.rs:17
- UseTree::normalize (cyclomatic 21) src/imports.rs:554
- UseTree::from_ast (cyclomatic 18) src/imports.rs:423
- GetOptsOptions::from_matches (cognitive 50) src/bin/main.rs:564
- GetOptsOptions::apply_to (cognitive 17) src/bin/main.rs:711
- Duplicated block (16 lines × 2) src/modules.rs:153
- Duplicated block (16 lines × 2) src/sort.rs:26
- Duplicated block (13 lines × 2) check_diff/src/lib.rs:321
- Duplicated block (13 lines × 2) src/items.rs:3161
- Duplicated block (8–9 lines × 2) src/header.rs:88
- Duplicated block (8–9 lines × 2) src/matches.rs:232
- CharClasses::next (cyclomatic 44) src/comment.rs:1394
- CommentRewrite::handle_line (cyclomatic 40) src/comment.rs:713
- GetOptsOptions::from_matches (cyclomatic 30) src/bin/main.rs:564
- UseSegment::cmp (cyclomatic 24) src/imports.rs:921
- ModResolver::find_external_module (cyclomatic 23) src/modules.rs:361
- ControlFlow::rewrite_cond (cyclomatic 21) src/expr.rs:981
- Context::try_overflow_last_item (cyclomatic 21) src/overflow.rs:483
- ChainFormatterShared::format_last_child (cyclomatic 20) src/chains.rs:727
- MacroBranch::rewrite (cyclomatic 16) src/macros.rs:1310
- Repeated repair: src/parse/macros/cfg_select.rs src/parse/macros/cfg_select.rs:43
- CommentRewrite::handle_line (cognitive 69) src/comment.rs:713
- CharClasses::next (cognitive 48) src/comment.rs:1394
- Context::try_overflow_last_item (cognitive 35) src/overflow.rs:483
- ChainFormatterShared::format_last_child (cognitive 34) src/chains.rs:727
- ModResolver::find_external_module (cognitive 32) src/modules.rs:361
- ControlFlow::rewrite_cond (cognitive 31) src/expr.rs:981
- Chain::from_ast (cognitive 23) src/chains.rs:387
- UseSegment::cmp (cognitive 22) src/imports.rs:921
- MacroArgParser::parse (cognitive 19) src/macros.rs:943
- MacroBranch::rewrite (cognitive 19) src/macros.rs:1310
- CommentCodeSlices::next (cognitive 18) src/comment.rs:1698
- SilentOnIgnoredFilesEmitter::emit_diagnostic (cognitive 16) src/parse/session.rs:54
- TooManyMethods: FmtVisitor src/visitor.rs:74
- TooManyFunctions: rustfmt_nightly::utils src/utils.rs:19
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (18–19 lines × 2) src/comment.rs:684
- Duplicated block (18 lines × 2) src/items.rs:2069
- Duplicated block (15 lines × 2) src/parse/macros/cfg_if.rs:76
- Duplicated block (8 lines × 2) src/matches.rs:461
- Low cohesion: ListFormatting (LCOM4 6) src/lists.rs:19
Minor — 68 finding(s)
- Interpolated log message defeats structured logging src/attr.rs:152
- Interpolated log message defeats structured logging src/chains.rs:150
- Interpolated log message defeats structured logging src/chains.rs:560
- Interpolated log message defeats structured logging src/closures.rs:43
- Interpolated log message defeats structured logging src/closures.rs:363
- Interpolated log message defeats structured logging src/comment.rs:162
- Interpolated log message defeats structured logging src/comment.rs:1813
- Interpolated log message defeats structured logging src/expr.rs:936
- Interpolated log message defeats structured logging src/expr.rs:1201
- Interpolated log message defeats structured logging src/expr.rs:1669
- Interpolated log message defeats structured logging src/expr.rs:1819
- Interpolated log message defeats structured logging src/expr.rs:2038
- Interpolated log message defeats structured logging src/expr.rs:2123
- Interpolated log message defeats structured logging src/formatting.rs:476
- Interpolated log message defeats structured logging src/items.rs:56
- Interpolated log message defeats structured logging src/items.rs:2549
- Interpolated log message defeats structured logging src/items.rs:2943
- Interpolated log message defeats structured logging src/macros.rs:592
- Interpolated log message defeats structured logging src/macros.rs:1094
- Interpolated log message defeats structured logging src/macros.rs:1146
- Interpolated log message defeats structured logging src/macros.rs:1421
- Interpolated log message defeats structured logging src/matches.rs:614
- Interpolated log message defeats structured logging src/missed_spans.rs:159
- Interpolated log message defeats structured logging src/missed_spans.rs:198
- Interpolated log message defeats structured logging src/modules.rs:484
- Orphaned file src/config/file_lines.rs:1
- Orphaned file src/shape.rs:1
- Orphaned file config_proc_macro/src/item_enum.rs:1
- Orphaned file src/formatting/newline_style.rs:1
- Orphaned file src/format-diff/main.rs:1
- Orphaned file src/git-rustfmt/main.rs:1
- Orphaned file src/stmt.rs:1
- Orphaned file src/skip.rs:1
- Orphaned file src/config/macro_names.rs:1
- Orphaned file src/source_map.rs:1
- Orphaned file config_proc_macro/src/attrs.rs:1
- Orphaned file src/source_file.rs:1
- Duplicated predicate src/imports.rs:365
- Duplicated predicate src/items.rs:2225
- Duplicated predicate src/parse/macros/cfg_if.rs:67
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No release approval gate
- Silent fallback default on Err check_diff/src/lib.rs:698
Minor — 16 finding(s)
- Outdated: annotate-snippets
- Outdated: anyhow
- Outdated: clap
- Outdated: diff
- Outdated: getopts
- Outdated: ignore
- Outdated: proc-macro2
- Outdated: quote
- Outdated: regex
- Outdated: serde
- Outdated: serde_json
- Outdated: tempfile
- Outdated: toml
- Outdated: tracing-subscriber
- Outdated: unicode-properties
- Outdated: unicode-segmentation
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c5f140f8b3a24be68a4a2423f3a1e346/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c5f140f8b3a24be68a4a2423f3a1e346/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 3 | 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 . | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |