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 63 out of 100 and is rated Adequate, and it has no critical findings.
Code Health, at 51, is the weakest lens and counts most in the score. The best first step is writing log messages as searchable templates, worth about 10 points. Recording design decisions comes next, worth about 4 points. Raising Code Health to 70 would lift the score to about 71.
Most of the 311 serious findings are in Code Health.
The product code is 34,005 lines, about €110,000 to rebuild.
If Code Health rose from 51 to 70, the lowest score rated Strong, the score would rise from 63 to about 71.
New since the last survey: 22 findings
- Code Duplication · Edited copy of a member (59 corresponding lines) src/parse/macros/cfg_if.rs
- Code Duplication · Edited copy of a member (36 corresponding lines) check_diff/src/lib.rs
- Code Duplication · Edited copy of a member (20 corresponding lines) src/header.rs
- Code Duplication · Edited copy of a member (18 corresponding lines) src/modules.rs
- Code Duplication · Edited copy of a member (32 corresponding lines) src/sort.rs
- Code Duplication · Edited copy of a member (25 corresponding lines) src/modules.rs
- Code Duplication · Edited copy of a member (28 corresponding lines) src/modules/visitor.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/closures.rs
- Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) src/parse/macros/cfg_if.rs
- Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) check_diff/src/lib.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/source_map.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/macros.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) src/modules.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) check_diff/src/lib.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/bin/main.rs
- Code Duplication · Duplicated block (16 lines × 2) src/modules.rs
- Code Duplication · Duplicated block (14 lines × 2) check_diff/src/lib.rs
- Code Duplication · Duplicated block (13 lines × 2) src/items.rs
- Code Duplication · Duplicated block (8–9 lines × 2) src/matches.rs
- Code Duplication · Duplicated block (6 lines × 2) src/parse/macros/cfg_if.rs
- Churn × Complexity Hotspots · Hotspot: src/items.rs src/items.rs
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 11 findings
- Code Duplication · Duplicated block (16 lines × 2) src/modules.rs
- Code Duplication · Duplicated block (13 lines × 2) src/items.rs
- Code Duplication · Duplicated block (8–9 lines × 2) src/matches.rs
- Code Duplication · Duplicated block (6 lines × 2) src/parse/macros/cfg_if.rs
- Churn × Complexity Hotspots · Hotspot: src/macros.rs src/macros.rs
- Churn × Complexity Hotspots · Hotspot: src/bin/main.rs src/bin/main.rs
- Churn × Complexity Hotspots · Hotspot: src/chains.rs src/chains.rs
- Static Analysis (SAST) · High: run-shell-injection .github/workflows/check_diff.yml
- Static Analysis (SAST) · High: watchdog-release-tag-name-into-run-shell .github/workflows/upload-assets.yml
- Static Analysis (SAST) · High: watchdog-release-tag-name-into-run-shell .github/workflows/upload-assets.yml
- Supply-chain Provenance & Signing · Release-publishing job runs with an unscoped token .github/workflows/upload-assets.yml
Rebuild cost: about €110,000 · Estimate
| Cost to rebuild | €35,000 to €180,000, for 583 to 1,850 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 63. 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: 34,005 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 config.config_type | 2 spanned | 3 config.file_lines | 4 config.lists | 5 parse.macros.cfg_select | 6 parse.parser | 7 config.options | 8 emitter | 9 modules | 10 cargo-fmt.main | 11 git-rustfmt.main | 12 ignore_path | 13 rustfmt_diff | 14 shape | 15 emitter.checkstyle | 16 emitter.json | 17 expr | 18 lists | 19 imports | 20 overflow | 21 stmt | 22 macros | 23 reorder | 24 visitor | 25 parse.session | 26 rewrite | 27 attr | 28 closures | 29 items | 30 matches | 31 pairs | 32 parse.macros | 33 patterns | 34 types | 35 comment | 36 modules.visitor | 37 formatting | 38 utils | 39 rustfmt_nightly | 40 bin.main |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 config.config_type | ||||||||||||||||||||||||||||||||||||||||
| 2 spanned | ||||||||||||||||||||||||||||||||||||||||
| 3 config.file_lines | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 config.lists | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 parse.macros.cfg_select | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 6 parse.parser | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 7 config.options | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 8 emitter | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 modules | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 10 cargo-fmt.main | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 git-rustfmt.main | 7 | |||||||||||||||||||||||||||||||||||||||
| 12 ignore_path | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 rustfmt_diff | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 shape | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 emitter.checkstyle | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 emitter.json | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 expr | 1 | 1 | 1 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 18 lists | 5 | 1 | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 19 imports | 1 | 3 | 3 | 1 | 5 | 1 | ||||||||||||||||||||||||||||||||||
| 20 overflow | 2 | 3 | 2 | 3 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 21 stmt | 1 | 2 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 22 macros | 1 | 1 | 6 | 2 | 6 | |||||||||||||||||||||||||||||||||||
| 23 reorder | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 24 visitor | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 6 | 1 | ||||||||||||||||||||||||||||
| 25 parse.session | 2 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 26 rewrite | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 27 attr | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 closures | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 items | 1 | 1 | 2 | 7 | 10 | |||||||||||||||||||||||||||||||||||
| 30 matches | 1 | 1 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 31 pairs | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 32 parse.macros | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 patterns | 1 | 2 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 34 types | 1 | 1 | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 35 comment | 2 | 4 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 36 modules.visitor | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 formatting | 6 | 2 | 3 | 3 | 1 | 6 | ||||||||||||||||||||||||||||||||||
| 38 utils | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 rustfmt_nightly | 3 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 40 bin.main | 1 | 6 | 1 | 2 |
3→1 config.file_lines uses config.config_type✕
- Connections
- 1 pair of types, where a type in config.file_lines uses a type in config.config_type.
- The types involved
rustfmt_nightly.config.file_lines.FileLines→rustfmt_nightly.config.config_type.ConfigType
- Direction
- config.file_lines uses config.config_type, so a change to config.config_type can break config.file_lines, while a change to config.file_lines can't break config.config_type.
- Position
- Below the diagonal: config.file_lines uses a module listed above it, which is the healthy direction.
4→7 config.lists uses config.options part of a loop✕
- Connections
- 1 pair of types, where a type in config.lists uses a type in config.options.
- The types involved
rustfmt_nightly.config.lists.DefinitiveListTactic→rustfmt_nightly.config.options.IndentStyle
- Direction
- config.lists uses config.options, so a change to config.options can break config.lists, while a change to config.lists can't break 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.
5→2 parse.macros.cfg_select uses spanned✕
- Connections
- 2 pairs of types, where a type in parse.macros.cfg_select uses a type in 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
- parse.macros.cfg_select uses spanned, so a change to spanned can break parse.macros.cfg_select, while a change to parse.macros.cfg_select can't break spanned.
- Position
- Below the diagonal: parse.macros.cfg_select uses a module listed above it, which is the healthy direction.
5→25 parse.macros.cfg_select uses parse.session part of a loop✕
- Connections
- 1 pair of types, where a type in parse.macros.cfg_select uses a type in parse.session.
- The types involved
rustfmt_nightly.parse.macros.cfg_select.cfg_select$module→rustfmt_nightly.parse.session.ParseSess
- Direction
- parse.macros.cfg_select uses parse.session, so a change to parse.session can break parse.macros.cfg_select, while a change to parse.macros.cfg_select can't break 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.
5→26 parse.macros.cfg_select uses rewrite part of a loop✕
- Connections
- 1 pair of types, where a type in parse.macros.cfg_select uses a type in rewrite.
- The types involved
rustfmt_nightly.parse.macros.cfg_select.CfgSelectArm→rustfmt_nightly.rewrite.RewriteContext
- Direction
- parse.macros.cfg_select uses rewrite, so a change to rewrite can break parse.macros.cfg_select, while a change to parse.macros.cfg_select can't break 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.
6→25 parse.parser uses parse.session part of a loop✕
- Connections
- 2 pairs of types, where a type in parse.parser uses a type in 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
- parse.parser uses parse.session, so a change to parse.session can break parse.parser, while a change to parse.parser can't break 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.
6→39 parse.parser uses rustfmt_nightly part of a loop✕
- Connections
- 2 pairs of types, where a type in 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
- parse.parser uses rustfmt_nightly, so a change to rustfmt_nightly can break parse.parser, while a change to 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.
7→1 config.options uses config.config_type✕
- Connections
- 2 pairs of types, where a type in config.options uses a type in 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
- config.options uses config.config_type, so a change to config.config_type can break config.options, while a change to config.options can't break config.config_type.
- Position
- Below the diagonal: config.options uses a module listed above it, which is the healthy direction.
7→4 config.options uses config.lists✕
- Connections
- 1 pair of types, where a type in config.options uses a type in config.lists.
- The types involved
rustfmt_nightly.config.options.Density→rustfmt_nightly.config.lists.ListTactic
- Direction
- config.options uses config.lists, so a change to config.lists can break config.options, while a change to config.options can't break config.lists.
- Position
- Below the diagonal: config.options uses a module listed above it, which is the healthy direction.
7→11 config.options uses git-rustfmt.main part of a loop✕
- Connections
- 1 pair of types, where a type in config.options uses a type in git-rustfmt.main.
- The types involved
rustfmt_nightly.config.options.CliOptions→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- config.options uses git-rustfmt.main, so a change to git-rustfmt.main can break config.options, while a change to config.options can't break 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.
8→3 emitter uses config.file_lines✕
- Connections
- 2 pairs of types, where a type in emitter uses a type in 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
- emitter uses config.file_lines, so a change to config.file_lines can break emitter, while a change to emitter can't break config.file_lines.
- Position
- Below the diagonal: emitter uses a module listed above it, which is the healthy direction.
9→6 modules uses parse.parser✕
- Connections
- 1 pair of types, where a type in modules uses a type in parse.parser.
- The types involved
rustfmt_nightly.modules.ModResolver→rustfmt_nightly.parse.parser.Directory
- Direction
- modules uses parse.parser, so a change to parse.parser can break modules, while a change to modules can't break parse.parser.
- Position
- Below the diagonal: modules uses a module listed above it, which is the healthy direction.
9→25 modules uses parse.session part of a loop✕
- Connections
- 1 pair of types, where a type in modules uses a type in parse.session.
- The types involved
rustfmt_nightly.modules.ModResolver→rustfmt_nightly.parse.session.ParseSess
- Direction
- modules uses parse.session, so a change to parse.session can break modules, while a change to modules can't break 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.
9→29 modules uses items part of a loop✕
- Connections
- 2 pairs of types, where a type in modules uses a type in items.
- The types involved
rustfmt_nightly.modules.ModResolver→rustfmt_nightly.items.Itemrustfmt_nightly.modules.modules$module→rustfmt_nightly.items.Item
- Direction
- modules uses items, so a change to items can break modules, while a change to modules can't break 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.
10→7 cargo-fmt.main uses config.options✕
- Connections
- 1 pair of types, where a type in cargo-fmt.main uses a type in config.options.
- The types involved
rustfmt_nightly.cargo-fmt.main.Target→rustfmt_nightly.config.options.Edition
- Direction
- cargo-fmt.main uses config.options, so a change to config.options can break cargo-fmt.main, while a change to cargo-fmt.main can't break config.options.
- Position
- Below the diagonal: cargo-fmt.main uses a module listed above it, which is the healthy direction.
11→7 git-rustfmt.main uses config.options✕
- Connections
- 7 pairs of types, where a type in git-rustfmt.main uses a type in config.options.
- The types involved
rustfmt_nightly.git-rustfmt.main.Config→rustfmt_nightly.config.options.Editionrustfmt_nightly.git-rustfmt.main.Config→rustfmt_nightly.config.options.StyleEditionrustfmt_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.Editionrustfmt_nightly.git-rustfmt.main.NullOptions→rustfmt_nightly.config.options.StyleEditionrustfmt_nightly.git-rustfmt.main.NullOptions→rustfmt_nightly.config.options.Version
- Direction
- git-rustfmt.main uses config.options, so a change to config.options can break git-rustfmt.main, while a change to git-rustfmt.main can't break config.options.
- Position
- Below the diagonal: git-rustfmt.main uses a module listed above it, which is the healthy direction.
12→3 ignore_path uses config.file_lines✕
- Connections
- 1 pair of types, where a type in ignore_path uses a type in config.file_lines.
- The types involved
rustfmt_nightly.ignore_path.IgnorePathSet→rustfmt_nightly.config.file_lines.FileName
- Direction
- ignore_path uses config.file_lines, so a change to config.file_lines can break ignore_path, while a change to ignore_path can't break config.file_lines.
- Position
- Below the diagonal: ignore_path uses a module listed above it, which is the healthy direction.
12→7 ignore_path uses config.options✕
- Connections
- 1 pair of types, where a type in ignore_path uses a type in config.options.
- The types involved
rustfmt_nightly.ignore_path.IgnorePathSet→rustfmt_nightly.config.options.IgnoreList
- Direction
- ignore_path uses config.options, so a change to config.options can break ignore_path, while a change to ignore_path can't break config.options.
- Position
- Below the diagonal: ignore_path uses a module listed above it, which is the healthy direction.
13→7 rustfmt_diff uses config.options✕
- Connections
- 1 pair of types, where a type in rustfmt_diff uses a type in config.options.
- The types involved
rustfmt_nightly.rustfmt_diff.OutputWriter→rustfmt_nightly.config.options.Color
- Direction
- rustfmt_diff uses config.options, so a change to config.options can break rustfmt_diff, while a change to rustfmt_diff can't break config.options.
- Position
- Below the diagonal: rustfmt_diff uses a module listed above it, which is the healthy direction.
13→11 rustfmt_diff uses git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in rustfmt_diff uses a type in git-rustfmt.main.
- The types involved
rustfmt_nightly.rustfmt_diff.rustfmt_diff$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rustfmt_diff uses git-rustfmt.main, so a change to git-rustfmt.main can break rustfmt_diff, while a change to rustfmt_diff can't break git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_diff uses a module listed above it, which is the healthy direction.
14→11 shape uses git-rustfmt.main✕
- Connections
- 2 pairs of types, where a type in shape uses a type in 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
- shape uses git-rustfmt.main, so a change to git-rustfmt.main can break shape, while a change to shape can't break git-rustfmt.main.
- Position
- Below the diagonal: shape uses a module listed above it, which is the healthy direction.
14→26 shape uses rewrite part of a loop✕
- Connections
- 1 pair of types, where a type in shape uses a type in rewrite.
- The types involved
rustfmt_nightly.shape.Shape→rustfmt_nightly.rewrite.ExceedsMaxWidthError
- Direction
- shape uses rewrite, so a change to rewrite can break shape, while a change to shape can't break 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.
15→3 emitter.checkstyle uses config.file_lines✕
- Connections
- 1 pair of types, where a type in emitter.checkstyle uses a type in config.file_lines.
- The types involved
rustfmt_nightly.emitter.checkstyle.checkstyle$module→rustfmt_nightly.config.file_lines.FileName
- Direction
- emitter.checkstyle uses config.file_lines, so a change to config.file_lines can break emitter.checkstyle, while a change to emitter.checkstyle can't break config.file_lines.
- Position
- Below the diagonal: emitter.checkstyle uses a module listed above it, which is the healthy direction.
15→8 emitter.checkstyle uses emitter✕
- Connections
- 2 pairs of types, where a type in emitter.checkstyle uses a type in emitter.
- The types involved
rustfmt_nightly.emitter.checkstyle.CheckstyleEmitter→rustfmt_nightly.emitter.Emitterrustfmt_nightly.emitter.checkstyle.CheckstyleEmitter→rustfmt_nightly.emitter.FormattedFile
- Direction
- emitter.checkstyle uses emitter, so a change to emitter can break emitter.checkstyle, while a change to emitter.checkstyle can't break emitter.
- Position
- Below the diagonal: emitter.checkstyle uses a module listed above it, which is the healthy direction.
15→13 emitter.checkstyle uses rustfmt_diff✕
- Connections
- 1 pair of types, where a type in emitter.checkstyle uses a type in rustfmt_diff.
- The types involved
rustfmt_nightly.emitter.checkstyle.checkstyle$module→rustfmt_nightly.rustfmt_diff.Mismatch
- Direction
- emitter.checkstyle uses rustfmt_diff, so a change to rustfmt_diff can break emitter.checkstyle, while a change to emitter.checkstyle can't break rustfmt_diff.
- Position
- Below the diagonal: emitter.checkstyle uses a module listed above it, which is the healthy direction.
16→3 emitter.json uses config.file_lines✕
- Connections
- 1 pair of types, where a type in emitter.json uses a type in config.file_lines.
- The types involved
rustfmt_nightly.emitter.json.JsonEmitter→rustfmt_nightly.config.file_lines.FileName
- Direction
- emitter.json uses config.file_lines, so a change to config.file_lines can break emitter.json, while a change to emitter.json can't break config.file_lines.
- Position
- Below the diagonal: emitter.json uses a module listed above it, which is the healthy direction.
16→8 emitter.json uses emitter✕
- Connections
- 2 pairs of types, where a type in emitter.json uses a type in emitter.
- The types involved
rustfmt_nightly.emitter.json.JsonEmitter→rustfmt_nightly.emitter.Emitterrustfmt_nightly.emitter.json.JsonEmitter→rustfmt_nightly.emitter.FormattedFile
- Direction
- emitter.json uses emitter, so a change to emitter can break emitter.json, while a change to emitter.json can't break emitter.
- Position
- Below the diagonal: emitter.json uses a module listed above it, which is the healthy direction.
16→13 emitter.json uses rustfmt_diff✕
- Connections
- 1 pair of types, where a type in emitter.json uses a type in rustfmt_diff.
- The types involved
rustfmt_nightly.emitter.json.JsonEmitter→rustfmt_nightly.rustfmt_diff.Mismatch
- Direction
- emitter.json uses rustfmt_diff, so a change to rustfmt_diff can break emitter.json, while a change to emitter.json can't break rustfmt_diff.
- Position
- Below the diagonal: emitter.json uses a module listed above it, which is the healthy direction.
17→4 expr uses config.lists✕
- Connections
- 1 pair of types, where a type in expr uses a type in config.lists.
- The types involved
rustfmt_nightly.expr.expr$module→rustfmt_nightly.config.lists.SeparatorTactic
- Direction
- expr uses config.lists, so a change to config.lists can break expr, while a change to expr can't break config.lists.
- Position
- Below the diagonal: expr uses a module listed above it, which is the healthy direction.
17→7 expr uses config.options✕
- Connections
- 1 pair of types, where a type in expr uses a type in config.options.
- The types involved
rustfmt_nightly.expr.expr$module→rustfmt_nightly.config.options.FloatLiteralTrailingZero
- Direction
- expr uses config.options, so a change to config.options can break expr, while a change to expr can't break config.options.
- Position
- Below the diagonal: expr uses a module listed above it, which is the healthy direction.
17→11 expr uses git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in expr uses a type in git-rustfmt.main.
- The types involved
rustfmt_nightly.expr.expr$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- expr uses git-rustfmt.main, so a change to git-rustfmt.main can break expr, while a change to expr can't break git-rustfmt.main.
- Position
- Below the diagonal: expr uses a module listed above it, which is the healthy direction.
17→14 expr uses shape✕
- Connections
- 2 pairs of types, where a type in expr uses a type in shape.
- The types involved
rustfmt_nightly.expr.ControlFlow→rustfmt_nightly.shape.Shaperustfmt_nightly.expr.expr$module→rustfmt_nightly.shape.Shape
- Direction
- expr uses shape, so a change to shape can break expr, while a change to expr can't break shape.
- Position
- Below the diagonal: expr uses a module listed above it, which is the healthy direction.
17→21 expr uses stmt part of a loop✕
- Connections
- 1 pair of types, where a type in expr uses a type in stmt.
- The types involved
rustfmt_nightly.expr.expr$module→rustfmt_nightly.stmt.Stmt
- Direction
- expr uses stmt, so a change to stmt can break expr, while a change to expr can't break 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.
17→26 expr uses rewrite part of a loop✕
- Connections
- 3 pairs of types, where a type in expr uses a type in 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
- expr uses rewrite, so a change to rewrite can break expr, while a change to expr can't break 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.
18→4 lists uses config.lists✕
- Connections
- 5 pairs of types, where a type in lists uses a type in 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
- lists uses config.lists, so a change to config.lists can break lists, while a change to lists can't break config.lists.
- Position
- Below the diagonal: lists uses a module listed above it, which is the healthy direction.
18→11 lists uses git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in lists uses a type in git-rustfmt.main.
- The types involved
rustfmt_nightly.lists.ListFormatting→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- lists uses git-rustfmt.main, so a change to git-rustfmt.main can break lists, while a change to lists can't break git-rustfmt.main.
- Position
- Below the diagonal: lists uses a module listed above it, which is the healthy direction.
18→14 lists uses shape✕
- Connections
- 2 pairs of types, where a type in lists uses a type in shape.
- The types involved
rustfmt_nightly.lists.ListFormatting→rustfmt_nightly.shape.Shaperustfmt_nightly.lists.lists$module→rustfmt_nightly.shape.Shape
- Direction
- lists uses shape, so a change to shape can break lists, while a change to lists can't break shape.
- Position
- Below the diagonal: lists uses a module listed above it, which is the healthy direction.
18→24 lists uses visitor part of a loop✕
- Connections
- 2 pairs of types, where a type in lists uses a type in visitor.
- The types involved
rustfmt_nightly.lists.ListItems→rustfmt_nightly.visitor.SnippetProviderrustfmt_nightly.lists.lists$module→rustfmt_nightly.visitor.SnippetProvider
- Direction
- lists uses visitor, so a change to visitor can break lists, while a change to lists can't break 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.
18→26 lists uses rewrite part of a loop✕
- Connections
- 1 pair of types, where a type in lists uses a type in rewrite.
- The types involved
rustfmt_nightly.lists.lists$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- lists uses rewrite, so a change to rewrite can break lists, while a change to lists can't break 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.
18→29 lists uses items part of a loop✕
- Connections
- 1 pair of types, where a type in lists uses a type in items.
- The types involved
rustfmt_nightly.lists.ListItems→rustfmt_nightly.items.Item
- Direction
- lists uses items, so a change to items can break lists, while a change to lists can't break 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.
19→2 imports uses spanned✕
- Connections
- 1 pair of types, where a type in imports uses a type in spanned.
- The types involved
rustfmt_nightly.imports.UseTree→rustfmt_nightly.spanned.Spanned
- Direction
- imports uses spanned, so a change to spanned can break imports, while a change to imports can't break spanned.
- Position
- Below the diagonal: imports uses a module listed above it, which is the healthy direction.
19→7 imports uses config.options✕
- Connections
- 3 pairs of types, where a type in imports uses a type in config.options.
- The types involved
rustfmt_nightly.imports.UseSegment→rustfmt_nightly.config.options.StyleEditionrustfmt_nightly.imports.UseTree→rustfmt_nightly.config.options.ImportGranularityrustfmt_nightly.imports.imports$module→rustfmt_nightly.config.options.ImportGranularity
- Direction
- imports uses config.options, so a change to config.options can break imports, while a change to imports can't break config.options.
- Position
- Below the diagonal: imports uses a module listed above it, which is the healthy direction.
19→14 imports uses shape✕
- Connections
- 3 pairs of types, where a type in imports uses a type in 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
- imports uses shape, so a change to shape can break imports, while a change to imports can't break shape.
- Position
- Below the diagonal: imports uses a module listed above it, which is the healthy direction.
19→18 imports uses lists✕
- Connections
- 1 pair of types, where a type in imports uses a type in lists.
- The types involved
rustfmt_nightly.imports.UseTree→rustfmt_nightly.lists.ListItem
- Direction
- imports uses lists, so a change to lists can break imports, while a change to imports can't break lists.
- Position
- Below the diagonal: imports uses a module listed above it, which is the healthy direction.
19→26 imports uses rewrite part of a loop✕
- Connections
- 5 pairs of types, where a type in imports uses a type in 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
- imports uses rewrite, so a change to rewrite can break imports, while a change to imports can't break 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→29 imports uses items part of a loop✕
- Connections
- 1 pair of types, where a type in imports uses a type in items.
- The types involved
rustfmt_nightly.imports.UseTree→rustfmt_nightly.items.Item
- Direction
- imports uses items, so a change to items can break imports, while a change to imports can't break 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→2 overflow uses spanned✕
- Connections
- 2 pairs of types, where a type in overflow uses a type in spanned.
- The types involved
rustfmt_nightly.overflow.IntoOverflowableItem→rustfmt_nightly.spanned.Spannedrustfmt_nightly.overflow.OverflowableItem→rustfmt_nightly.spanned.Spanned
- Direction
- overflow uses spanned, so a change to spanned can break overflow, while a change to overflow can't break spanned.
- Position
- Below the diagonal: overflow uses a module listed above it, which is the healthy direction.
20→4 overflow uses config.lists✕
- Connections
- 3 pairs of types, where a type in overflow uses a type in 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
- overflow uses config.lists, so a change to config.lists can break overflow, while a change to overflow can't break config.lists.
- Position
- Below the diagonal: overflow uses a module listed above it, which is the healthy direction.
20→11 overflow uses git-rustfmt.main✕
- Connections
- 2 pairs of types, where a type in overflow uses a type in 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
- overflow uses git-rustfmt.main, so a change to git-rustfmt.main can break overflow, while a change to overflow can't break git-rustfmt.main.
- Position
- Below the diagonal: overflow uses a module listed above it, which is the healthy direction.
20→14 overflow uses shape✕
- Connections
- 3 pairs of types, where a type in overflow uses a type in 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
- overflow uses shape, so a change to shape can break overflow, while a change to overflow can't break shape.
- Position
- Below the diagonal: overflow uses a module listed above it, which is the healthy direction.
20→18 overflow uses lists✕
- Connections
- 1 pair of types, where a type in overflow uses a type in lists.
- The types involved
rustfmt_nightly.overflow.Context→rustfmt_nightly.lists.ListItem
- Direction
- overflow uses lists, so a change to lists can break overflow, while a change to overflow can't break lists.
- Position
- Below the diagonal: overflow uses a module listed above it, which is the healthy direction.
20→26 overflow uses rewrite part of a loop✕
- Connections
- 5 pairs of types, where a type in overflow uses a type in 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
- overflow uses rewrite, so a change to rewrite can break overflow, while a change to overflow can't break 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.
21→2 stmt uses spanned✕
- Connections
- 1 pair of types, where a type in stmt uses a type in spanned.
- The types involved
rustfmt_nightly.stmt.Stmt→rustfmt_nightly.spanned.Spanned
- Direction
- stmt uses spanned, so a change to spanned can break stmt, while a change to stmt can't break spanned.
- Position
- Below the diagonal: stmt uses a module listed above it, which is the healthy direction.
21→14 stmt uses shape✕
- Connections
- 2 pairs of types, where a type in stmt uses a type in shape.
- The types involved
rustfmt_nightly.stmt.Stmt→rustfmt_nightly.shape.Shaperustfmt_nightly.stmt.stmt$module→rustfmt_nightly.shape.Shape
- Direction
- stmt uses shape, so a change to shape can break stmt, while a change to stmt can't break shape.
- Position
- Below the diagonal: stmt uses a module listed above it, which is the healthy direction.
21→17 stmt uses expr✕
- Connections
- 1 pair of types, where a type in stmt uses a type in expr.
- The types involved
rustfmt_nightly.stmt.stmt$module→rustfmt_nightly.expr.ExprType
- Direction
- stmt uses expr, so a change to expr can break stmt, while a change to stmt can't break expr.
- Position
- Below the diagonal: stmt uses a module listed above it, which is the healthy direction.
21→26 stmt uses rewrite part of a loop✕
- Connections
- 3 pairs of types, where a type in stmt uses a type in 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
- stmt uses rewrite, so a change to rewrite can break stmt, while a change to stmt can't break 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.
21→29 stmt uses items part of a loop✕
- Connections
- 1 pair of types, where a type in stmt uses a type in items.
- The types involved
rustfmt_nightly.stmt.Stmt→rustfmt_nightly.items.Item
- Direction
- stmt uses items, so a change to items can break stmt, while a change to stmt can't break 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.
22→2 macros uses spanned✕
- Connections
- 1 pair of types, where a type in macros uses a type in spanned.
- The types involved
rustfmt_nightly.macros.MacroArg→rustfmt_nightly.spanned.Spanned
- Direction
- macros uses spanned, so a change to spanned can break macros, while a change to macros can't break spanned.
- Position
- Below the diagonal: macros uses a module listed above it, which is the healthy direction.
22→5 macros uses parse.macros.cfg_select✕
- Connections
- 1 pair of types, where a type in macros uses a type in parse.macros.cfg_select.
- The types involved
rustfmt_nightly.macros.macros$module→rustfmt_nightly.parse.macros.cfg_select.CfgSelectArm
- Direction
- macros uses parse.macros.cfg_select, so a change to parse.macros.cfg_select can break macros, while a change to macros can't break parse.macros.cfg_select.
- Position
- Below the diagonal: macros uses a module listed above it, which is the healthy direction.
22→14 macros uses shape✕
- Connections
- 6 pairs of types, where a type in macros uses a type in 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
- macros uses shape, so a change to shape can break macros, while a change to macros can't break shape.
- Position
- Below the diagonal: macros uses a module listed above it, which is the healthy direction.
22→20 macros uses overflow✕
- Connections
- 2 pairs of types, where a type in macros uses a type in overflow.
- The types involved
rustfmt_nightly.macros.MacroArg→rustfmt_nightly.overflow.IntoOverflowableItemrustfmt_nightly.macros.MacroArg→rustfmt_nightly.overflow.OverflowableItem
- Direction
- macros uses overflow, so a change to overflow can break macros, while a change to macros can't break overflow.
- Position
- Below the diagonal: macros uses a module listed above it, which is the healthy direction.
22→26 macros uses rewrite part of a loop✕
- Connections
- 6 pairs of types, where a type in macros uses a type in 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
- macros uses rewrite, so a change to rewrite can break macros, while a change to macros can't break 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.
23→11 reorder uses git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in reorder uses a type in git-rustfmt.main.
- The types involved
rustfmt_nightly.reorder.ReorderableItemKind→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- reorder uses git-rustfmt.main, so a change to git-rustfmt.main can break reorder, while a change to reorder can't break git-rustfmt.main.
- Position
- Below the diagonal: reorder uses a module listed above it, which is the healthy direction.
23→14 reorder uses shape✕
- Connections
- 1 pair of types, where a type in reorder uses a type in shape.
- The types involved
rustfmt_nightly.reorder.reorder$module→rustfmt_nightly.shape.Shape
- Direction
- reorder uses shape, so a change to shape can break reorder, while a change to reorder can't break shape.
- Position
- Below the diagonal: reorder uses a module listed above it, which is the healthy direction.
23→19 reorder uses imports✕
- Connections
- 1 pair of types, where a type in reorder uses a type in imports.
- The types involved
rustfmt_nightly.reorder.reorder$module→rustfmt_nightly.imports.UseTree
- Direction
- reorder uses imports, so a change to imports can break reorder, while a change to reorder can't break imports.
- Position
- Below the diagonal: reorder uses a module listed above it, which is the healthy direction.
23→26 reorder uses rewrite part of a loop✕
- Connections
- 1 pair of types, where a type in reorder uses a type in rewrite.
- The types involved
rustfmt_nightly.reorder.reorder$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- reorder uses rewrite, so a change to rewrite can break reorder, while a change to reorder can't break 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.
23→29 reorder uses items part of a loop✕
- Connections
- 2 pairs of types, where a type in reorder uses a type in items.
- The types involved
rustfmt_nightly.reorder.ReorderableItemKind→rustfmt_nightly.items.Itemrustfmt_nightly.reorder.reorder$module→rustfmt_nightly.items.Item
- Direction
- reorder uses items, so a change to items can break reorder, while a change to reorder can't break 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.
24→3 visitor uses config.file_lines✕
- Connections
- 1 pair of types, where a type in visitor uses a type in config.file_lines.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.config.file_lines.FileName
- Direction
- visitor uses config.file_lines, so a change to config.file_lines can break visitor, while a change to visitor can't break config.file_lines.
- Position
- Below the diagonal: visitor uses a module listed above it, which is the healthy direction.
24→9 visitor uses modules✕
- Connections
- 1 pair of types, where a type in visitor uses a type in modules.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.modules.Module
- Direction
- visitor uses modules, so a change to modules can break visitor, while a change to visitor can't break modules.
- Position
- Below the diagonal: visitor uses a module listed above it, which is the healthy direction.
24→11 visitor uses git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in visitor uses a type in git-rustfmt.main.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- visitor uses git-rustfmt.main, so a change to git-rustfmt.main can break visitor, while a change to visitor can't break git-rustfmt.main.
- Position
- Below the diagonal: visitor uses a module listed above it, which is the healthy direction.
24→14 visitor uses shape✕
- Connections
- 2 pairs of types, where a type in visitor uses a type in shape.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.shape.Indentrustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.shape.Shape
- Direction
- visitor uses shape, so a change to shape can break visitor, while a change to visitor can't break shape.
- Position
- Below the diagonal: visitor uses a module listed above it, which is the healthy direction.
24→19 visitor uses imports✕
- Connections
- 1 pair of types, where a type in visitor uses a type in imports.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.imports.UseTree
- Direction
- visitor uses imports, so a change to imports can break visitor, while a change to visitor can't break imports.
- Position
- Below the diagonal: visitor uses a module listed above it, which is the healthy direction.
24→21 visitor uses stmt✕
- Connections
- 1 pair of types, where a type in visitor uses a type in stmt.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.stmt.Stmt
- Direction
- visitor uses stmt, so a change to stmt can break visitor, while a change to visitor can't break stmt.
- Position
- Below the diagonal: visitor uses a module listed above it, which is the healthy direction.
24→22 visitor uses macros✕
- Connections
- 1 pair of types, where a type in visitor uses a type in macros.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.macros.MacroPosition
- Direction
- visitor uses macros, so a change to macros can break visitor, while a change to visitor can't break macros.
- Position
- Below the diagonal: visitor uses a module listed above it, which is the healthy direction.
24→23 visitor uses reorder✕
- Connections
- 1 pair of types, where a type in visitor uses a type in reorder.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.reorder.ReorderableItemKind
- Direction
- visitor uses reorder, so a change to reorder can break visitor, while a change to visitor can't break reorder.
- Position
- Below the diagonal: visitor uses a module listed above it, which is the healthy direction.
24→25 visitor uses parse.session part of a loop✕
- Connections
- 1 pair of types, where a type in visitor uses a type in parse.session.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.parse.session.ParseSess
- Direction
- visitor uses parse.session, so a change to parse.session can break visitor, while a change to visitor can't break 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.
24→26 visitor uses rewrite part of a loop✕
- Connections
- 1 pair of types, where a type in visitor uses a type in rewrite.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.rewrite.RewriteContext
- Direction
- visitor uses rewrite, so a change to rewrite can break visitor, while a change to visitor can't break 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→29 visitor uses items part of a loop✕
- Connections
- 6 pairs of types, where a type in visitor uses a type in 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
- visitor uses items, so a change to items can break visitor, while a change to visitor can't break 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.
24→39 visitor uses rustfmt_nightly part of a loop✕
- Connections
- 1 pair of types, where a type in visitor uses a type in rustfmt_nightly.
- The types involved
rustfmt_nightly.visitor.FmtVisitor→rustfmt_nightly.FormatReport
- Direction
- visitor uses rustfmt_nightly, so a change to rustfmt_nightly can break visitor, while a change to 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.
25→3 parse.session uses config.file_lines✕
- Connections
- 2 pairs of types, where a type in parse.session uses a type in 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
- parse.session uses config.file_lines, so a change to config.file_lines can break parse.session, while a change to parse.session can't break config.file_lines.
- Position
- Below the diagonal: parse.session uses a module listed above it, which is the healthy direction.
25→7 parse.session uses config.options✕
- Connections
- 1 pair of types, where a type in parse.session uses a type in config.options.
- The types involved
rustfmt_nightly.parse.session.session$module→rustfmt_nightly.config.options.Color
- Direction
- parse.session uses config.options, so a change to config.options can break parse.session, while a change to parse.session can't break config.options.
- Position
- Below the diagonal: parse.session uses a module listed above it, which is the healthy direction.
25→8 parse.session uses emitter✕
- Connections
- 1 pair of types, where a type in parse.session uses a type in emitter.
- The types involved
rustfmt_nightly.parse.session.SilentOnIgnoredFilesEmitter→rustfmt_nightly.emitter.Emitter
- Direction
- parse.session uses emitter, so a change to emitter can break parse.session, while a change to parse.session can't break emitter.
- Position
- Below the diagonal: parse.session uses a module listed above it, which is the healthy direction.
25→11 parse.session uses git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in parse.session uses a type in git-rustfmt.main.
- The types involved
rustfmt_nightly.parse.session.ParseSess→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- parse.session uses git-rustfmt.main, so a change to git-rustfmt.main can break parse.session, while a change to parse.session can't break git-rustfmt.main.
- Position
- Below the diagonal: parse.session uses a module listed above it, which is the healthy direction.
25→12 parse.session uses ignore_path✕
- Connections
- 2 pairs of types, where a type in parse.session uses a type in 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
- parse.session uses ignore_path, so a change to ignore_path can break parse.session, while a change to parse.session can't break ignore_path.
- Position
- Below the diagonal: parse.session uses a module listed above it, which is the healthy direction.
25→24 parse.session uses visitor✕
- Connections
- 1 pair of types, where a type in parse.session uses a type in visitor.
- The types involved
rustfmt_nightly.parse.session.ParseSess→rustfmt_nightly.visitor.SnippetProvider
- Direction
- parse.session uses visitor, so a change to visitor can break parse.session, while a change to parse.session can't break visitor.
- Position
- Below the diagonal: parse.session uses a module listed above it, which is the healthy direction.
26→11 rewrite uses git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in rewrite uses a type in git-rustfmt.main.
- The types involved
rustfmt_nightly.rewrite.RewriteContext→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- rewrite uses git-rustfmt.main, so a change to git-rustfmt.main can break rewrite, while a change to rewrite can't break git-rustfmt.main.
- Position
- Below the diagonal: rewrite uses a module listed above it, which is the healthy direction.
26→14 rewrite uses shape✕
- Connections
- 1 pair of types, where a type in rewrite uses a type in shape.
- The types involved
rustfmt_nightly.rewrite.Rewrite→rustfmt_nightly.shape.Shape
- Direction
- rewrite uses shape, so a change to shape can break rewrite, while a change to rewrite can't break shape.
- Position
- Below the diagonal: rewrite uses a module listed above it, which is the healthy direction.
26→24 rewrite uses visitor✕
- Connections
- 1 pair of types, where a type in rewrite uses a type in visitor.
- The types involved
rustfmt_nightly.rewrite.RewriteContext→rustfmt_nightly.visitor.SnippetProvider
- Direction
- rewrite uses visitor, so a change to visitor can break rewrite, while a change to rewrite can't break visitor.
- Position
- Below the diagonal: rewrite uses a module listed above it, which is the healthy direction.
26→25 rewrite uses parse.session✕
- Connections
- 1 pair of types, where a type in rewrite uses a type in parse.session.
- The types involved
rustfmt_nightly.rewrite.RewriteContext→rustfmt_nightly.parse.session.ParseSess
- Direction
- rewrite uses parse.session, so a change to parse.session can break rewrite, while a change to rewrite can't break parse.session.
- Position
- Below the diagonal: rewrite uses a module listed above it, which is the healthy direction.
26→39 rewrite uses rustfmt_nightly part of a loop✕
- Connections
- 1 pair of types, where a type in rewrite uses a type in rustfmt_nightly.
- The types involved
rustfmt_nightly.rewrite.RewriteContext→rustfmt_nightly.FormatReport
- Direction
- rewrite uses rustfmt_nightly, so a change to rustfmt_nightly can break rewrite, while a change to 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.
27→14 attr uses shape✕
- Connections
- 1 pair of types, where a type in attr uses a type in shape.
- The types involved
rustfmt_nightly.attr.attr$module→rustfmt_nightly.shape.Shape
- Direction
- attr uses shape, so a change to shape can break attr, while a change to attr can't break shape.
- Position
- Below the diagonal: attr uses a module listed above it, which is the healthy direction.
27→21 attr uses stmt✕
- Connections
- 1 pair of types, where a type in attr uses a type in stmt.
- The types involved
rustfmt_nightly.attr.attr$module→rustfmt_nightly.stmt.Stmt
- Direction
- attr uses stmt, so a change to stmt can break attr, while a change to attr can't break stmt.
- Position
- Below the diagonal: attr uses a module listed above it, which is the healthy direction.
27→26 attr uses rewrite✕
- Connections
- 1 pair of types, where a type in attr uses a type in rewrite.
- The types involved
rustfmt_nightly.attr.attr$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- attr uses rewrite, so a change to rewrite can break attr, while a change to attr can't break rewrite.
- Position
- Below the diagonal: attr uses a module listed above it, which is the healthy direction.
28→7 closures uses config.options✕
- Connections
- 1 pair of types, where a type in closures uses a type in config.options.
- The types involved
rustfmt_nightly.closures.closures$module→rustfmt_nightly.config.options.StyleEdition
- Direction
- closures uses config.options, so a change to config.options can break closures, while a change to closures can't break config.options.
- Position
- Below the diagonal: closures uses a module listed above it, which is the healthy direction.
28→14 closures uses shape✕
- Connections
- 1 pair of types, where a type in closures uses a type in shape.
- The types involved
rustfmt_nightly.closures.closures$module→rustfmt_nightly.shape.Shape
- Direction
- closures uses shape, so a change to shape can break closures, while a change to closures can't break shape.
- Position
- Below the diagonal: closures uses a module listed above it, which is the healthy direction.
28→26 closures uses rewrite✕
- Connections
- 1 pair of types, where a type in closures uses a type in rewrite.
- The types involved
rustfmt_nightly.closures.closures$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- closures uses rewrite, so a change to rewrite can break closures, while a change to closures can't break rewrite.
- Position
- Below the diagonal: closures uses a module listed above it, which is the healthy direction.
29→2 items uses spanned✕
- Connections
- 1 pair of types, where a type in items uses a type in spanned.
- The types involved
rustfmt_nightly.items.Item→rustfmt_nightly.spanned.Spanned
- Direction
- items uses spanned, so a change to spanned can break items, while a change to items can't break spanned.
- Position
- Below the diagonal: items uses a module listed above it, which is the healthy direction.
29→7 items uses config.options✕
- Connections
- 1 pair of types, where a type in items uses a type in config.options.
- The types involved
rustfmt_nightly.items.items$module→rustfmt_nightly.config.options.BraceStyle
- Direction
- items uses config.options, so a change to config.options can break items, while a change to items can't break config.options.
- Position
- Below the diagonal: items uses a module listed above it, which is the healthy direction.
29→11 items uses git-rustfmt.main✕
- Connections
- 2 pairs of types, where a type in items uses a type in 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
- items uses git-rustfmt.main, so a change to git-rustfmt.main can break items, while a change to items can't break git-rustfmt.main.
- Position
- Below the diagonal: items uses a module listed above it, which is the healthy direction.
29→14 items uses shape✕
- Connections
- 7 pairs of types, where a type in items uses a type in 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
- items uses shape, so a change to shape can break items, while a change to items can't break shape.
- Position
- Below the diagonal: items uses a module listed above it, which is the healthy direction.
29→26 items uses rewrite✕
- Connections
- 10 pairs of types, where a type in items uses a type in 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
- items uses rewrite, so a change to rewrite can break items, while a change to items can't break rewrite.
- Position
- Below the diagonal: items uses a module listed above it, which is the healthy direction.
30→2 matches uses spanned✕
- Connections
- 1 pair of types, where a type in matches uses a type in spanned.
- The types involved
rustfmt_nightly.matches.ArmWrapper→rustfmt_nightly.spanned.Spanned
- Direction
- matches uses spanned, so a change to spanned can break matches, while a change to matches can't break spanned.
- Position
- Below the diagonal: matches uses a module listed above it, which is the healthy direction.
30→11 matches uses git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in matches uses a type in git-rustfmt.main.
- The types involved
rustfmt_nightly.matches.matches$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- matches uses git-rustfmt.main, so a change to git-rustfmt.main can break matches, while a change to matches can't break git-rustfmt.main.
- Position
- Below the diagonal: matches uses a module listed above it, which is the healthy direction.
30→14 matches uses shape✕
- Connections
- 2 pairs of types, where a type in matches uses a type in shape.
- The types involved
rustfmt_nightly.matches.ArmWrapper→rustfmt_nightly.shape.Shaperustfmt_nightly.matches.matches$module→rustfmt_nightly.shape.Shape
- Direction
- matches uses shape, so a change to shape can break matches, while a change to matches can't break shape.
- Position
- Below the diagonal: matches uses a module listed above it, which is the healthy direction.
30→21 matches uses stmt✕
- Connections
- 1 pair of types, where a type in matches uses a type in stmt.
- The types involved
rustfmt_nightly.matches.matches$module→rustfmt_nightly.stmt.Stmt
- Direction
- matches uses stmt, so a change to stmt can break matches, while a change to matches can't break stmt.
- Position
- Below the diagonal: matches uses a module listed above it, which is the healthy direction.
30→26 matches uses rewrite✕
- Connections
- 3 pairs of types, where a type in matches uses a type in 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
- matches uses rewrite, so a change to rewrite can break matches, while a change to matches can't break rewrite.
- Position
- Below the diagonal: matches uses a module listed above it, which is the healthy direction.
31→4 pairs uses config.lists✕
- Connections
- 1 pair of types, where a type in pairs uses a type in config.lists.
- The types involved
rustfmt_nightly.pairs.pairs$module→rustfmt_nightly.config.lists.SeparatorPlace
- Direction
- pairs uses config.lists, so a change to config.lists can break pairs, while a change to pairs can't break config.lists.
- Position
- Below the diagonal: pairs uses a module listed above it, which is the healthy direction.
31→14 pairs uses shape✕
- Connections
- 2 pairs of types, where a type in pairs uses a type in shape.
- The types involved
rustfmt_nightly.pairs.FlattenPair→rustfmt_nightly.shape.Shaperustfmt_nightly.pairs.pairs$module→rustfmt_nightly.shape.Shape
- Direction
- pairs uses shape, so a change to shape can break pairs, while a change to pairs can't break shape.
- Position
- Below the diagonal: pairs uses a module listed above it, which is the healthy direction.
31→26 pairs uses rewrite✕
- Connections
- 3 pairs of types, where a type in pairs uses a type in rewrite.
- The types involved
rustfmt_nightly.pairs.FlattenPair→rustfmt_nightly.rewrite.Rewriterustfmt_nightly.pairs.FlattenPair→rustfmt_nightly.rewrite.RewriteContextrustfmt_nightly.pairs.pairs$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- pairs uses rewrite, so a change to rewrite can break pairs, while a change to pairs can't break rewrite.
- Position
- Below the diagonal: pairs uses a module listed above it, which is the healthy direction.
32→6 parse.macros uses parse.parser✕
- Connections
- 1 pair of types, where a type in parse.macros uses a type in parse.parser.
- The types involved
rustfmt_nightly.parse.macros.macros$module→rustfmt_nightly.parse.parser.Parser
- Direction
- parse.macros uses parse.parser, so a change to parse.parser can break parse.macros, while a change to parse.macros can't break parse.parser.
- Position
- Below the diagonal: parse.macros uses a module listed above it, which is the healthy direction.
32→22 parse.macros uses macros✕
- Connections
- 2 pairs of types, where a type in parse.macros uses a type in macros.
- The types involved
rustfmt_nightly.parse.macros.ParsedMacroArgs→rustfmt_nightly.macros.MacroArgrustfmt_nightly.parse.macros.macros$module→rustfmt_nightly.macros.MacroArg
- Direction
- parse.macros uses macros, so a change to macros can break parse.macros, while a change to parse.macros can't break macros.
- Position
- Below the diagonal: parse.macros uses a module listed above it, which is the healthy direction.
32→25 parse.macros uses parse.session✕
- Connections
- 1 pair of types, where a type in parse.macros uses a type in parse.session.
- The types involved
rustfmt_nightly.parse.macros.macros$module→rustfmt_nightly.parse.session.ParseSess
- Direction
- parse.macros uses parse.session, so a change to parse.session can break parse.macros, while a change to parse.macros can't break parse.session.
- Position
- Below the diagonal: parse.macros uses a module listed above it, which is the healthy direction.
32→26 parse.macros uses rewrite✕
- Connections
- 1 pair of types, where a type in parse.macros uses a type in rewrite.
- The types involved
rustfmt_nightly.parse.macros.macros$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- parse.macros uses rewrite, so a change to rewrite can break parse.macros, while a change to parse.macros can't break rewrite.
- Position
- Below the diagonal: parse.macros uses a module listed above it, which is the healthy direction.
33→2 patterns uses spanned✕
- Connections
- 1 pair of types, where a type in patterns uses a type in spanned.
- The types involved
rustfmt_nightly.patterns.TuplePatField→rustfmt_nightly.spanned.Spanned
- Direction
- patterns uses spanned, so a change to spanned can break patterns, while a change to patterns can't break spanned.
- Position
- Below the diagonal: patterns uses a module listed above it, which is the healthy direction.
33→14 patterns uses shape✕
- Connections
- 2 pairs of types, where a type in patterns uses a type in shape.
- The types involved
rustfmt_nightly.patterns.TuplePatField→rustfmt_nightly.shape.Shaperustfmt_nightly.patterns.patterns$module→rustfmt_nightly.shape.Shape
- Direction
- patterns uses shape, so a change to shape can break patterns, while a change to patterns can't break shape.
- Position
- Below the diagonal: patterns uses a module listed above it, which is the healthy direction.
33→20 patterns uses overflow✕
- Connections
- 2 pairs of types, where a type in patterns uses a type in overflow.
- The types involved
rustfmt_nightly.patterns.TuplePatField→rustfmt_nightly.overflow.IntoOverflowableItemrustfmt_nightly.patterns.TuplePatField→rustfmt_nightly.overflow.OverflowableItem
- Direction
- patterns uses overflow, so a change to overflow can break patterns, while a change to patterns can't break overflow.
- Position
- Below the diagonal: patterns uses a module listed above it, which is the healthy direction.
33→26 patterns uses rewrite✕
- Connections
- 3 pairs of types, where a type in patterns uses a type in 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
- patterns uses rewrite, so a change to rewrite can break patterns, while a change to patterns can't break rewrite.
- Position
- Below the diagonal: patterns uses a module listed above it, which is the healthy direction.
34→2 types uses spanned✕
- Connections
- 1 pair of types, where a type in types uses a type in spanned.
- The types involved
rustfmt_nightly.types.SegmentParam→rustfmt_nightly.spanned.Spanned
- Direction
- types uses spanned, so a change to spanned can break types, while a change to types can't break spanned.
- Position
- Below the diagonal: types uses a module listed above it, which is the healthy direction.
34→4 types uses config.lists✕
- Connections
- 1 pair of types, where a type in types uses a type in config.lists.
- The types involved
rustfmt_nightly.types.types$module→rustfmt_nightly.config.lists.DefinitiveListTactic
- Direction
- types uses config.lists, so a change to config.lists can break types, while a change to types can't break config.lists.
- Position
- Below the diagonal: types uses a module listed above it, which is the healthy direction.
34→14 types uses shape✕
- Connections
- 2 pairs of types, where a type in types uses a type in shape.
- The types involved
rustfmt_nightly.types.SegmentParam→rustfmt_nightly.shape.Shaperustfmt_nightly.types.types$module→rustfmt_nightly.shape.Shape
- Direction
- types uses shape, so a change to shape can break types, while a change to types can't break shape.
- Position
- Below the diagonal: types uses a module listed above it, which is the healthy direction.
34→20 types uses overflow✕
- Connections
- 2 pairs of types, where a type in types uses a type in overflow.
- The types involved
rustfmt_nightly.types.SegmentParam→rustfmt_nightly.overflow.IntoOverflowableItemrustfmt_nightly.types.SegmentParam→rustfmt_nightly.overflow.OverflowableItem
- Direction
- types uses overflow, so a change to overflow can break types, while a change to types can't break overflow.
- Position
- Below the diagonal: types uses a module listed above it, which is the healthy direction.
34→26 types uses rewrite✕
- Connections
- 3 pairs of types, where a type in types uses a type in 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
- types uses rewrite, so a change to rewrite can break types, while a change to types can't break rewrite.
- Position
- Below the diagonal: types uses a module listed above it, which is the healthy direction.
35→11 comment uses git-rustfmt.main✕
- Connections
- 2 pairs of types, where a type in comment uses a type in 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
- comment uses git-rustfmt.main, so a change to git-rustfmt.main can break comment, while a change to comment can't break git-rustfmt.main.
- Position
- Below the diagonal: comment uses a module listed above it, which is the healthy direction.
35→14 comment uses shape✕
- Connections
- 4 pairs of types, where a type in comment uses a type in 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
- comment uses shape, so a change to shape can break comment, while a change to comment can't break shape.
- Position
- Below the diagonal: comment uses a module listed above it, which is the healthy direction.
35→26 comment uses rewrite✕
- Connections
- 1 pair of types, where a type in comment uses a type in rewrite.
- The types involved
rustfmt_nightly.comment.comment$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- comment uses rewrite, so a change to rewrite can break comment, while a change to comment can't break rewrite.
- Position
- Below the diagonal: comment uses a module listed above it, which is the healthy direction.
35→29 comment uses items✕
- Connections
- 4 pairs of types, where a type in comment uses a type in 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
- comment uses items, so a change to items can break comment, while a change to comment can't break items.
- Position
- Below the diagonal: comment uses a module listed above it, which is the healthy direction.
36→25 modules.visitor uses parse.session✕
- Connections
- 2 pairs of types, where a type in modules.visitor uses a type in 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
- modules.visitor uses parse.session, so a change to parse.session can break modules.visitor, while a change to modules.visitor can't break parse.session.
- Position
- Below the diagonal: modules.visitor uses a module listed above it, which is the healthy direction.
36→27 modules.visitor uses attr✕
- Connections
- 1 pair of types, where a type in modules.visitor uses a type in attr.
- The types involved
rustfmt_nightly.modules.visitor.PathVisitor→rustfmt_nightly.attr.MetaVisitor
- Direction
- modules.visitor uses attr, so a change to attr can break modules.visitor, while a change to modules.visitor can't break attr.
- Position
- Below the diagonal: modules.visitor uses a module listed above it, which is the healthy direction.
36→29 modules.visitor uses items✕
- Connections
- 1 pair of types, where a type in modules.visitor uses a type in items.
- The types involved
rustfmt_nightly.modules.visitor.ModItem→rustfmt_nightly.items.Item
- Direction
- modules.visitor uses items, so a change to items can break modules.visitor, while a change to modules.visitor can't break items.
- Position
- Below the diagonal: modules.visitor uses a module listed above it, which is the healthy direction.
37→3 formatting uses config.file_lines✕
- Connections
- 6 pairs of types, where a type in formatting uses a type in 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
- formatting uses config.file_lines, so a change to config.file_lines can break formatting, while a change to formatting can't break config.file_lines.
- Position
- Below the diagonal: formatting uses a module listed above it, which is the healthy direction.
37→9 formatting uses modules✕
- Connections
- 2 pairs of types, where a type in formatting uses a type in modules.
- The types involved
rustfmt_nightly.formatting.FormatContext→rustfmt_nightly.modules.Modulerustfmt_nightly.formatting.formatting$module→rustfmt_nightly.modules.Module
- Direction
- formatting uses modules, so a change to modules can break formatting, while a change to formatting can't break modules.
- Position
- Below the diagonal: formatting uses a module listed above it, which is the healthy direction.
37→11 formatting uses git-rustfmt.main✕
- Connections
- 3 pairs of types, where a type in formatting uses a type in 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
- formatting uses git-rustfmt.main, so a change to git-rustfmt.main can break formatting, while a change to formatting can't break git-rustfmt.main.
- Position
- Below the diagonal: formatting uses a module listed above it, which is the healthy direction.
37→25 formatting uses parse.session✕
- Connections
- 3 pairs of types, where a type in formatting uses a type in 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
- formatting uses parse.session, so a change to parse.session can break formatting, while a change to formatting can't break parse.session.
- Position
- Below the diagonal: formatting uses a module listed above it, which is the healthy direction.
37→35 formatting uses comment✕
- Connections
- 1 pair of types, where a type in formatting uses a type in comment.
- The types involved
rustfmt_nightly.formatting.FormatLines→rustfmt_nightly.comment.FullCodeCharKind
- Direction
- formatting uses comment, so a change to comment can break formatting, while a change to formatting can't break comment.
- Position
- Below the diagonal: formatting uses a module listed above it, which is the healthy direction.
37→39 formatting uses rustfmt_nightly part of a loop✕
- Connections
- 6 pairs of types, where a type in 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
- formatting uses rustfmt_nightly, so a change to rustfmt_nightly can break formatting, while a change to 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→11 utils uses git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in utils uses a type in git-rustfmt.main.
- The types involved
rustfmt_nightly.utils.utils$module→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- utils uses git-rustfmt.main, so a change to git-rustfmt.main can break utils, while a change to utils can't break git-rustfmt.main.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
38→14 utils uses shape✕
- Connections
- 2 pairs of types, where a type in utils uses a type in shape.
- The types involved
rustfmt_nightly.utils.utils$module→rustfmt_nightly.shape.Indentrustfmt_nightly.utils.utils$module→rustfmt_nightly.shape.Shape
- Direction
- utils uses shape, so a change to shape can break utils, while a change to utils can't break shape.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
38→21 utils uses stmt✕
- Connections
- 1 pair of types, where a type in utils uses a type in stmt.
- The types involved
rustfmt_nightly.utils.utils$module→rustfmt_nightly.stmt.Stmt
- Direction
- utils uses stmt, so a change to stmt can break utils, while a change to utils can't break stmt.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
38→26 utils uses rewrite✕
- Connections
- 1 pair of types, where a type in utils uses a type in rewrite.
- The types involved
rustfmt_nightly.utils.utils$module→rustfmt_nightly.rewrite.RewriteContext
- Direction
- utils uses rewrite, so a change to rewrite can break utils, while a change to utils can't break rewrite.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
38→35 utils uses comment✕
- Connections
- 1 pair of types, where a type in utils uses a type in comment.
- The types involved
rustfmt_nightly.utils.utils$module→rustfmt_nightly.comment.FullCodeCharKind
- Direction
- utils uses comment, so a change to comment can break utils, while a change to utils can't break comment.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
39→3 rustfmt_nightly uses config.file_lines✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly uses a type in 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 config.file_lines, so a change to config.file_lines can break rustfmt_nightly, while a change to rustfmt_nightly can't break config.file_lines.
- Position
- Below the diagonal: rustfmt_nightly uses a module listed above it, which is the healthy direction.
39→11 rustfmt_nightly uses git-rustfmt.main✕
- Connections
- 2 pairs of types, where a type in rustfmt_nightly uses a type in 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 git-rustfmt.main, so a change to git-rustfmt.main can break rustfmt_nightly, while a change to rustfmt_nightly can't break git-rustfmt.main.
- Position
- Below the diagonal: rustfmt_nightly uses a module listed above it, which is the healthy direction.
39→25 rustfmt_nightly uses parse.session✕
- Connections
- 1 pair of types, where a type in rustfmt_nightly uses a type in parse.session.
- The types involved
rustfmt_nightly.Session→rustfmt_nightly.parse.session.ParseSess
- Direction
- rustfmt_nightly uses parse.session, so a change to parse.session can break rustfmt_nightly, while a change to rustfmt_nightly can't break parse.session.
- Position
- Below the diagonal: rustfmt_nightly uses a module listed above it, which is the healthy direction.
39→37 rustfmt_nightly uses formatting✕
- Connections
- 3 pairs of types, where a type in rustfmt_nightly uses a type in 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 formatting, so a change to formatting can break rustfmt_nightly, while a change to rustfmt_nightly can't break formatting.
- Position
- Below the diagonal: rustfmt_nightly uses a module listed above it, which is the healthy direction.
40→3 bin.main uses config.file_lines✕
- Connections
- 1 pair of types, where a type in bin.main uses a type in config.file_lines.
- The types involved
rustfmt_nightly.bin.main.GetOptsOptions→rustfmt_nightly.config.file_lines.FileLines
- Direction
- bin.main uses config.file_lines, so a change to config.file_lines can break bin.main, while a change to bin.main can't break config.file_lines.
- Position
- Below the diagonal: bin.main uses a module listed above it, which is the healthy direction.
40→7 bin.main uses config.options✕
- Connections
- 6 pairs of types, where a type in bin.main uses a type in 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.Editionrustfmt_nightly.bin.main.GetOptsOptions→rustfmt_nightly.config.options.EmitModerustfmt_nightly.bin.main.GetOptsOptions→rustfmt_nightly.config.options.StyleEditionrustfmt_nightly.bin.main.GetOptsOptions→rustfmt_nightly.config.options.Version
- Direction
- bin.main uses config.options, so a change to config.options can break bin.main, while a change to bin.main can't break config.options.
- Position
- Below the diagonal: bin.main uses a module listed above it, which is the healthy direction.
40→11 bin.main uses git-rustfmt.main✕
- Connections
- 1 pair of types, where a type in bin.main uses a type in git-rustfmt.main.
- The types involved
rustfmt_nightly.bin.main.GetOptsOptions→rustfmt_nightly.git-rustfmt.main.Config
- Direction
- bin.main uses git-rustfmt.main, so a change to git-rustfmt.main can break bin.main, while a change to bin.main can't break git-rustfmt.main.
- Position
- Below the diagonal: bin.main uses a module listed above it, which is the healthy direction.
40→39 bin.main uses rustfmt_nightly✕
- Connections
- 2 pairs of types, where a type in 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
- bin.main uses rustfmt_nightly, so a change to rustfmt_nightly can break bin.main, while a change to bin.main can't break rustfmt_nightly.
- Position
- Below the diagonal: 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 | 3 | Medium |
Roadmap
Top priorities: Interpolated log message defeats structured logging; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml; 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 49).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Interpolated log message defeats structured logging | +9.8 pts | Medium | Structured logging |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. | +4.5 pts | Low | ADR Quality |
| 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 49). | +4.1 pts | High | Cyclomatic Complexity |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.9 pts | Medium | Architecture documentation |
| 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 |
| Enable Dependabot/Renovate or a dependency-review gate. | +1.9 pts | Medium | Security & performance tooling |
| 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 104), CommentRewrite::handle_line (cognitive 69). | +1.9 pts | High | Cognitive Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| 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/closures.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| 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
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 40 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, 368 of 390 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 119 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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 49). — 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.
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 104), 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.
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).
D4 · Code Duplication
17 duplicated block group(s) detected. 2.4 % of the production lines (800 of 34,005) are in a reported copy. A further 15 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 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 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with closures.rs, source_map.rs. — One of this dimension's main actionable groups (2 warning-level).
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).
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.
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 (10×58=580); src/items.rs (11×49=539); src/comment.rs (8×40=320) Repeated repair below the complexity floor: src/parse/macros/cfg_select.rs (5 of 7 changes were fixes)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with expr.rs, items.rs, comment.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with 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 34005 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).
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 — start with Cargo.toml. — 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)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 0 high, 3 medium, 0 low.
What to do
- Resolve the 2 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 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.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
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.
P6 · Release Hygiene
PF1 · Benchmark discipline
X21 · Side-effecting pattern guard
X28 · Index access outside its own emptiness guard
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 1826 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:1826
- `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 1687 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:1687
- `debug!` at line 1837 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:1837
- `debug!` at line 2056 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:2056
- `debug!` at line 2141 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:2141
- `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 2949 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:2949
- `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 1423 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:1423
- `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 | 51% | Adequate — gated by D2, X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 73% | Strong | Solid. |
| Security | 100% | Exemplary | Strongest area. |
| 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 — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: 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 — ~58336 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 does not read html yet; 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+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .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.
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Rust suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (4 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 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.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not 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.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not 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)
Serious — 311 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 104) 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:360
- 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 49) 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:1596
- 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:1827
- 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
- FmtVisitor::close_block (cognitive 48) src/visitor.rs:263
- FmtVisitor::visit_item (cognitive 25) src/visitor.rs:443
- FmtVisitor::process_comment (cognitive 20) src/missed_spans.rs:235
- FmtVisitor::visit_stmt (cognitive 20) src/visitor.rs:118
- FmtVisitor::visit_impl_items (cognitive 19) src/items.rs:736
- FmtVisitor::process_missing_code (cognitive 16) src/missed_spans.rs:338
- HackComment src/comment.rs:1486
- HackComment src/expr.rs:701
- HackComment src/imports.rs:556
- HackComment src/missed_spans.rs:39
- HackComment src/types.rs:292
- Hotspot: src/expr.rs src/expr.rs:86
- Hotspot: src/items.rs src/items.rs:2483
- Hotspot: src/comment.rs src/comment.rs:713
- Hotspot: src/lists.rs src/lists.rs:264
- 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:1407
- 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:291
- 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:590
- GetOptsOptions::apply_to (cognitive 17) src/bin/main.rs:737
- REDACTED
- REDACTED
- Edited copy of a member (10 corresponding lines) src/closures.rs:464
- Edited copy of a member (10 corresponding lines) src/source_map.rs:39
- Edited copy of a member (9 corresponding lines) check_diff/src/lib.rs:40
- Edited copy of a member (9 corresponding lines) src/bin/main.rs:823
- 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:3167
- 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:1407
- CommentRewrite::handle_line (cyclomatic 40) src/comment.rs:713
- GetOptsOptions::from_matches (cyclomatic 30) src/bin/main.rs:590
- 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:1407
- 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:1711
- 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
- Edited copy of a member (59 corresponding lines) src/parse/macros/cfg_if.rs:30
- Edited copy of a member (36 corresponding lines) check_diff/src/lib.rs:319
- Edited copy of a member (20 corresponding lines) src/header.rs:82
- Edited copy of a member (18 corresponding lines) src/modules.rs:151
- Edited copy of a member (32 corresponding lines) src/sort.rs:18
- Edited copy of a member (25 corresponding lines) src/modules.rs:196
- Edited copy of a member (28 corresponding lines) src/modules/visitor.rs:44
- Edited copies of one member (3 members, 11+ corresponding lines) src/parse/macros/cfg_if.rs:15
- Edited copies of one member (3 members, 18+ corresponding lines) check_diff/src/lib.rs:482
- Edited copy of a member (11 corresponding lines) src/macros.rs:788
- Edited copy of a member (13 corresponding lines) src/modules.rs:607
- Duplicated block (18–19 lines × 2) src/comment.rs:684
- Duplicated block (19 lines × 2) src/items.rs:2068
- Duplicated block (15 lines × 2) src/parse/macros/cfg_if.rs:76
- Duplicated block (14 lines × 2) check_diff/src/lib.rs:341
- Duplicated block (8 lines × 2) src/matches.rs:461
- Low cohesion: ListFormatting (LCOM4 6) src/lists.rs:19
Minor — 63 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:1826
- 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:1687
- Interpolated log message defeats structured logging src/expr.rs:1837
- Interpolated log message defeats structured logging src/expr.rs:2056
- Interpolated log message defeats structured logging src/expr.rs:2141
- 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:2949
- 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:1423
- 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 Cargo.toml:11
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- 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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-857b039e357e49eea589f824affab7f1/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-857b039e357e49eea589f824affab7f1/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | 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 . | 3 | 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 |