Executive summary
clap-rs/clap is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because we found no recorded design decisions and no architecture document or diagram. It scores 68 out of 100, which the At risk rating leaves unchanged.
Maturity, at 56, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 11 points. Completing the README is another step, worth about 5 points. Raising Maturity to 70 would lift the score to about 74.
Three known security holes in the packages the code depends on can be used by attackers. One pipeline step installs packages that can change without warning. Updating the vulnerable packages and pinning what the pipeline installs would close both risks.
The product code is 38,706 lines, about €95,000 to rebuild.
If Maturity rose from 56 to 70, the lowest score rated Strong, the score would rise from 68 to about 74.
New since the last survey: 55 findings
- Code Duplication · Near-duplicate member pair (44 shared lines) clap_builder/src/builder/command.rs
- Code Duplication · Near-duplicate member pair (39 shared lines) clap_builder/src/output/usage.rs
- Code Duplication · Edited copy of a member (45 corresponding lines) clap_builder/src/builder/value_parser.rs
- Code Duplication · Edited copy of a member (21 corresponding lines) clap_builder/src/builder/value_parser.rs
- Code Duplication · Edited copy of a member (22 corresponding lines) clap_complete/src/aot/generator/utils.rs
- Code Duplication · Edited copy of a member (30 corresponding lines) clap_builder/src/error/mod.rs
- Code Duplication · Edited copy of a member (16 corresponding lines) clap_complete/src/env/shells.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) clap_complete/src/engine/complete.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) clap_complete/src/engine/complete.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) clap_builder/src/builder/command.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) clap_builder/src/builder/action.rs
- Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) clap_complete/src/env/shells.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) clap_builder/src/util/flat_map.rs
- Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) clap_builder/src/builder/action.rs
- Code Duplication · Edited copies of one member (7 members, 15+ corresponding lines) clap_builder/src/error/mod.rs
- Code Duplication · Edited copy of a member (13 corresponding lines) clap_builder/src/derive.rs
- Code Duplication · Edited copies of one member (5 members, 13+ corresponding lines) clap_builder/src/parser/matches/arg_matches.rs
- Code Duplication · Edited copy of a member (9 corresponding lines) clap_builder/src/builder/command.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) clap_builder/src/builder/arg.rs
- Code Duplication · Edited copy of a member (5 corresponding lines) clap_complete/src/engine/complete.rs
- Code Duplication · Edited copy of a member (7 corresponding lines) clap_complete/src/aot/generator/utils.rs
- Code Duplication · Edited copy of a member (34 corresponding lines) clap_complete/src/aot/shells/elvish.rs
- Code Duplication · Duplicated block (28 lines × 2) clap_complete/src/aot/shells/bash.rs
- Code Duplication · Duplicated block (17 lines × 2) clap_builder/src/builder/command.rs
- Code Duplication · Duplicated block (12–14 lines × 2) clap_builder/src/output/usage.rs
- Code Duplication · Duplicated block (7–9 lines × 2) clap_builder/src/output/usage.rs
- Code Duplication · Duplicated block (7 lines × 2) clap_builder/src/error/format.rs
- Code Coverage · Low coverage: clap_builder/src/builder/os_str.rs clap_builder/src/builder/os_str.rs
- Code Coverage · Low coverage: clap_builder/src/builder/str.rs clap_builder/src/builder/str.rs
- Code Coverage · Low coverage: clap_builder/src/builder/value_hint.rs clap_builder/src/builder/value_hint.rs
- Code Coverage · Low coverage: clap_builder/src/derive.rs clap_builder/src/derive.rs
- Code Coverage · Low coverage: clap_builder/src/error/context.rs clap_builder/src/error/context.rs
- Code Coverage · Low coverage: clap_builder/src/error/kind.rs clap_builder/src/error/kind.rs
- Code Coverage · Low coverage: clap_builder/src/util/color.rs clap_builder/src/util/color.rs
- Code Coverage · Low coverage: clap_complete/src/aot/generator/mod.rs clap_complete/src/aot/generator/mod.rs
- Code Coverage · Low coverage: clap_complete/src/aot/shells/shell.rs clap_complete/src/aot/shells/shell.rs
- Code Coverage · Low coverage: clap_derive/src/attr.rs clap_derive/src/attr.rs
- Code Coverage · Low coverage: clap_derive/src/derives/args.rs clap_derive/src/derives/args.rs
- Code Coverage · Low coverage: clap_derive/src/derives/into_app.rs clap_derive/src/derives/into_app.rs
- Code Coverage · Low coverage: clap_derive/src/derives/parser.rs clap_derive/src/derives/parser.rs
- Code Coverage · Low coverage: clap_derive/src/derives/subcommand.rs clap_derive/src/derives/subcommand.rs
- Code Coverage · Low coverage: clap_derive/src/derives/value_enum.rs clap_derive/src/derives/value_enum.rs
- Code Coverage · Low coverage: clap_derive/src/dummies.rs clap_derive/src/dummies.rs
- Code Coverage · Low coverage: clap_derive/src/item.rs clap_derive/src/item.rs
- Code Coverage · Low coverage: clap_derive/src/lib.rs clap_derive/src/lib.rs
- Code Coverage · Low coverage: clap_derive/src/utils/doc_comments.rs clap_derive/src/utils/doc_comments.rs
- Code Coverage · Low coverage: clap_derive/src/utils/error.rs clap_derive/src/utils/error.rs
- Code Coverage · Low coverage: clap_derive/src/utils/spanned.rs clap_derive/src/utils/spanned.rs
- Code Coverage · Low coverage: clap_derive/src/utils/ty.rs clap_derive/src/utils/ty.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 33 findings
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) clap_derive/src/derives/args.rs
- Code Duplication · Duplicated block (31 lines × 2) clap_derive/src/derives/args.rs
- Code Duplication · Duplicated block (17 lines × 4) clap_derive/src/derives/args.rs
- Code Duplication · Duplicated block (16 lines × 2) clap_derive/src/item.rs
- Code Duplication · Duplicated block (15 lines × 2) clap_derive/src/derives/args.rs
- Code Duplication · Duplicated block (13 lines × 2) clap_derive/src/item.rs
- Code Duplication · Duplicated block (12 lines × 2) clap_builder/src/output/help_template.rs
- Code Duplication · Duplicated block (12 lines × 2) clap_derive/src/derives/parser.rs
- Code Duplication · Duplicated block (11 lines × 2) clap_derive/src/derives/args.rs
- Code Duplication · Duplicated block (10 lines × 2) clap_derive/src/item.rs
- Code Duplication · Duplicated block (6–9 lines × 4) clap_derive/src/item.rs
- Code Duplication · Duplicated block (9 lines × 2) clap_complete/src/aot/shells/bash.rs
- Code Duplication · Duplicated block (8 lines × 2) clap_builder/src/output/help_template.rs
- Code Duplication · Duplicated block (8 lines × 2) clap_derive/src/derives/args.rs
- Code Duplication · Duplicated block (8 lines × 2) clap_derive/src/derives/args.rs
- Code Duplication · Duplicated block (8 lines × 2) clap_derive/src/derives/subcommand.rs
- Code Duplication · Duplicated block (8 lines × 2) clap_derive/src/item.rs
- Code Duplication · Duplicated block (8 lines × 2) clap_derive/src/item.rs
- Code Duplication · Duplicated block (7 lines × 2) clap_builder/src/error/format.rs
- Code Duplication · Duplicated block (6 lines × 2) clap_derive/src/item.rs
- Code Duplication · Duplicated block (6 lines × 2) clap_derive/src/item.rs
- Code Duplication · Duplicated block (5 lines × 3) clap_derive/src/item.rs
- Code Duplication · Duplicated block (5 lines × 2) clap_derive/src/derives/subcommand.rs
- Code Duplication · Duplicated block (5 lines × 2) clap_derive/src/item.rs
- Code Duplication · Duplicated block (5 lines × 2) clap_derive/src/item.rs
- Code Duplication · Duplicated block (5 lines × 2) clap_derive/src/item.rs
- Code Duplication · Duplicated block (8 lines × 2) clap_builder/src/util/color.rs
- Code Duplication · Duplicated block (15 lines × 2) clap_derive/src/item.rs
- Code Duplication · Duplicated block (6 lines × 3) clap_derive/src/item.rs
- Code Duplication · Duplicated block (6 lines × 2) clap_complete/src/aot/shells/bash.rs
- Code Duplication · Duplicated block (5 lines × 2) clap_derive/src/derives/subcommand.rs
- Churn × Complexity Hotspots · Hotspot: clap_derive/src/attr.rs clap_derive/src/attr.rs
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0367 REDACTED
Rebuild cost: about €95,000 · Estimate
| Cost to rebuild | €31,000 to €160,000, for 524 to 1,662 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 | ×1.0 at a score of 68. 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: 38,706 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 clap_builder.builder.styled_str | 2 clap_builder.parser.matches.value_source | 3 clap_builder.util.any_value | 4 clap_builder.util.flat_map | 5 clap_derive.utils.spanned | 6 clap_builder.builder.ext | 7 clap_builder.builder.os_str.inner | 8 clap_builder.builder.value_hint | 9 clap_builder.parser.matches.matched_arg | 10 clap_builder.util.id | 11 clap_derive.item | 12 clap_builder.builder.arg_group | 13 clap_builder.builder.str | 14 clap_builder.builder.os_str | 15 clap_builder.builder.possible_value | 16 clap_builder.parser.matches.arg_matches | 17 clap_complete.engine.candidate | 18 clap_builder.derive | 19 clap_builder.builder.value_parser.impl_prelude | 20 clap_builder.util.color | 21 clap_builder.error | 22 clap_builder.builder.command | 23 clap_builder.builder.styling | 24 clap_complete.aot.generator | 25 clap_builder.builder.arg | 26 clap_builder.error.format | 27 clap_complete.aot.shells.shell | 28 clap_builder.builder.value_parser | 29 clap_builder.parser.parser | 30 clap_complete.aot.shells.fish | 31 clap_complete.aot.shells.powershell | 32 clap_complete.engine.complete | 33 clap_complete.engine.custom | 34 clap_complete_nushell | 35 clap_mangen.render | 36 clap_builder.builder.action | 37 clap_builder.parser.arg_matcher | 38 clap_builder.output.usage | 39 clap_builder.parser.validator | 40 clap_builder.output.help_template |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 clap_builder.builder.styled_str | ||||||||||||||||||||||||||||||||||||||||
| 2 clap_builder.parser.matches.value_source | ||||||||||||||||||||||||||||||||||||||||
| 3 clap_builder.util.any_value | ||||||||||||||||||||||||||||||||||||||||
| 4 clap_builder.util.flat_map | ||||||||||||||||||||||||||||||||||||||||
| 5 clap_derive.utils.spanned | ||||||||||||||||||||||||||||||||||||||||
| 6 clap_builder.builder.ext | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 clap_builder.builder.os_str.inner | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 clap_builder.builder.value_hint | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 clap_builder.parser.matches.matched_arg | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 10 clap_builder.util.id | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 clap_derive.item | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 clap_builder.builder.arg_group | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 clap_builder.builder.str | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 14 clap_builder.builder.os_str | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 clap_builder.builder.possible_value | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 clap_builder.parser.matches.arg_matches | 1 | 1 | 2 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 17 clap_complete.engine.candidate | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 clap_builder.derive | 1 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 19 clap_builder.builder.value_parser.impl_prelude | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 20 clap_builder.util.color | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 clap_builder.error | 2 | 1 | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 22 clap_builder.builder.command | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 23 clap_builder.builder.styling | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 clap_complete.aot.generator | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 clap_builder.builder.arg | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 26 clap_builder.error.format | 4 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 clap_complete.aot.shells.shell | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 clap_builder.builder.value_parser | 1 | 4 | 2 | 1 | 17 | 1 | 2 | 7 | 17 | 17 | ||||||||||||||||||||||||||||||
| 29 clap_builder.parser.parser | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 30 clap_complete.aot.shells.fish | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 clap_complete.aot.shells.powershell | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 clap_complete.engine.complete | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 clap_complete.engine.custom | 4 | 7 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 clap_complete_nushell | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 clap_mangen.render | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 clap_builder.builder.action | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 clap_builder.parser.arg_matcher | 1 | 1 | 3 | 1 | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 38 clap_builder.output.usage | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 clap_builder.parser.validator | 1 | 1 | 3 | 1 | 1 | 3 | 2 | 2 | ||||||||||||||||||||||||||||||||
| 40 clap_builder.output.help_template | 2 | 3 | 1 | 2 | 2 |
6→4 clap_builder.builder.ext uses clap_builder.util.flat_map✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.ext uses a type in clap_builder.util.flat_map.
- The types involved
clap_builder.builder.ext.Extensions→clap_builder.util.flat_map.FlatMap
- Direction
- clap_builder.builder.ext uses clap_builder.util.flat_map, so a change to clap_builder.util.flat_map can break clap_builder.builder.ext, while a change to clap_builder.builder.ext can't break clap_builder.util.flat_map.
- Position
- Below the diagonal: clap_builder.builder.ext uses a module listed above it, which is the healthy direction.
7→14 clap_builder.builder.os_str.inner uses clap_builder.builder.os_str part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.os_str.inner uses a type in clap_builder.builder.os_str.
- The types involved
clap_builder.builder.os_str.inner.Inner→clap_builder.builder.os_str.OsStr
- Direction
- clap_builder.builder.os_str.inner uses clap_builder.builder.os_str, so a change to clap_builder.builder.os_str can break clap_builder.builder.os_str.inner, while a change to clap_builder.builder.os_str.inner can't break clap_builder.builder.os_str.
- 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→25 clap_builder.builder.value_hint uses clap_builder.builder.arg part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.value_hint uses a type in clap_builder.builder.arg.
- The types involved
clap_builder.builder.value_hint.ValueHint→clap_builder.builder.arg.ArgExt
- Direction
- clap_builder.builder.value_hint uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_builder.builder.value_hint, while a change to clap_builder.builder.value_hint can't break clap_builder.builder.arg.
- 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→2 clap_builder.parser.matches.matched_arg uses clap_builder.parser.matches.value_source✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.matches.matched_arg uses a type in clap_builder.parser.matches.value_source.
- The types involved
clap_builder.parser.matches.matched_arg.MatchedArg→clap_builder.parser.matches.value_source.ValueSource
- Direction
- clap_builder.parser.matches.matched_arg uses clap_builder.parser.matches.value_source, so a change to clap_builder.parser.matches.value_source can break clap_builder.parser.matches.matched_arg, while a change to clap_builder.parser.matches.matched_arg can't break clap_builder.parser.matches.value_source.
- Position
- Below the diagonal: clap_builder.parser.matches.matched_arg uses a module listed above it, which is the healthy direction.
9→3 clap_builder.parser.matches.matched_arg uses clap_builder.util.any_value✕
- Connections
- 2 pairs of types, where a type in clap_builder.parser.matches.matched_arg uses a type in clap_builder.util.any_value.
- The types involved
clap_builder.parser.matches.matched_arg.MatchedArg→clap_builder.util.any_value.AnyValueclap_builder.parser.matches.matched_arg.MatchedArg→clap_builder.util.any_value.AnyValueId
- Direction
- clap_builder.parser.matches.matched_arg uses clap_builder.util.any_value, so a change to clap_builder.util.any_value can break clap_builder.parser.matches.matched_arg, while a change to clap_builder.parser.matches.matched_arg can't break clap_builder.util.any_value.
- Position
- Below the diagonal: clap_builder.parser.matches.matched_arg uses a module listed above it, which is the healthy direction.
9→4 clap_builder.parser.matches.matched_arg uses clap_builder.util.flat_map✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.matches.matched_arg uses a type in clap_builder.util.flat_map.
- The types involved
clap_builder.parser.matches.matched_arg.MatchedArg→clap_builder.util.flat_map.Iter
- Direction
- clap_builder.parser.matches.matched_arg uses clap_builder.util.flat_map, so a change to clap_builder.util.flat_map can break clap_builder.parser.matches.matched_arg, while a change to clap_builder.parser.matches.matched_arg can't break clap_builder.util.flat_map.
- Position
- Below the diagonal: clap_builder.parser.matches.matched_arg uses a module listed above it, which is the healthy direction.
9→22 clap_builder.parser.matches.matched_arg uses clap_builder.builder.command part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.matches.matched_arg uses a type in clap_builder.builder.command.
- The types involved
clap_builder.parser.matches.matched_arg.MatchedArg→clap_builder.builder.command.Command
- Direction
- clap_builder.parser.matches.matched_arg uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_builder.parser.matches.matched_arg, while a change to clap_builder.parser.matches.matched_arg can't break clap_builder.builder.command.
- 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→25 clap_builder.parser.matches.matched_arg uses clap_builder.builder.arg part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.matches.matched_arg uses a type in clap_builder.builder.arg.
- The types involved
clap_builder.parser.matches.matched_arg.MatchedArg→clap_builder.builder.arg.Arg
- Direction
- clap_builder.parser.matches.matched_arg uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_builder.parser.matches.matched_arg, while a change to clap_builder.parser.matches.matched_arg can't break clap_builder.builder.arg.
- 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→13 clap_builder.util.id uses clap_builder.builder.str part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.util.id uses a type in clap_builder.builder.str.
- The types involved
clap_builder.util.id.Id→clap_builder.builder.str.Str
- Direction
- clap_builder.util.id uses clap_builder.builder.str, so a change to clap_builder.builder.str can break clap_builder.util.id, while a change to clap_builder.util.id can't break clap_builder.builder.str.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→5 clap_derive.item uses clap_derive.utils.spanned✕
- Connections
- 2 pairs of types, where a type in clap_derive.item uses a type in clap_derive.utils.spanned.
- The types involved
clap_derive.item.Item→clap_derive.utils.spanned.Spclap_derive.item.Kind→clap_derive.utils.spanned.Sp
- Direction
- clap_derive.item uses clap_derive.utils.spanned, so a change to clap_derive.utils.spanned can break clap_derive.item, while a change to clap_derive.item can't break clap_derive.utils.spanned.
- Position
- Below the diagonal: clap_derive.item uses a module listed above it, which is the healthy direction.
12→10 clap_builder.builder.arg_group uses clap_builder.util.id✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.arg_group uses a type in clap_builder.util.id.
- The types involved
clap_builder.builder.arg_group.ArgGroup→clap_builder.util.id.Id
- Direction
- clap_builder.builder.arg_group uses clap_builder.util.id, so a change to clap_builder.util.id can break clap_builder.builder.arg_group, while a change to clap_builder.builder.arg_group can't break clap_builder.util.id.
- Position
- Below the diagonal: clap_builder.builder.arg_group uses a module listed above it, which is the healthy direction.
13→7 clap_builder.builder.str uses clap_builder.builder.os_str.inner✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.str uses a type in clap_builder.builder.os_str.inner.
- The types involved
clap_builder.builder.str.Str→clap_builder.builder.os_str.inner.Inner
- Direction
- clap_builder.builder.str uses clap_builder.builder.os_str.inner, so a change to clap_builder.builder.os_str.inner can break clap_builder.builder.str, while a change to clap_builder.builder.str can't break clap_builder.builder.os_str.inner.
- Position
- Below the diagonal: clap_builder.builder.str uses a module listed above it, which is the healthy direction.
13→10 clap_builder.builder.str uses clap_builder.util.id✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.str uses a type in clap_builder.util.id.
- The types involved
clap_builder.builder.str.Str→clap_builder.util.id.Id
- Direction
- clap_builder.builder.str uses clap_builder.util.id, so a change to clap_builder.util.id can break clap_builder.builder.str, while a change to clap_builder.builder.str can't break clap_builder.util.id.
- Position
- Below the diagonal: clap_builder.builder.str uses a module listed above it, which is the healthy direction.
13→14 clap_builder.builder.str uses clap_builder.builder.os_str part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.str uses a type in clap_builder.builder.os_str.
- The types involved
clap_builder.builder.str.Str→clap_builder.builder.os_str.OsStr
- Direction
- clap_builder.builder.str uses clap_builder.builder.os_str, so a change to clap_builder.builder.os_str can break clap_builder.builder.str, while a change to clap_builder.builder.str can't break clap_builder.builder.os_str.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→7 clap_builder.builder.os_str uses clap_builder.builder.os_str.inner✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.os_str uses a type in clap_builder.builder.os_str.inner.
- The types involved
clap_builder.builder.os_str.OsStr→clap_builder.builder.os_str.inner.Inner
- Direction
- clap_builder.builder.os_str uses clap_builder.builder.os_str.inner, so a change to clap_builder.builder.os_str.inner can break clap_builder.builder.os_str, while a change to clap_builder.builder.os_str can't break clap_builder.builder.os_str.inner.
- Position
- Below the diagonal: clap_builder.builder.os_str uses a module listed above it, which is the healthy direction.
14→13 clap_builder.builder.os_str uses clap_builder.builder.str✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.os_str uses a type in clap_builder.builder.str.
- The types involved
clap_builder.builder.os_str.OsStr→clap_builder.builder.str.Str
- Direction
- clap_builder.builder.os_str uses clap_builder.builder.str, so a change to clap_builder.builder.str can break clap_builder.builder.os_str, while a change to clap_builder.builder.os_str can't break clap_builder.builder.str.
- Position
- Below the diagonal: clap_builder.builder.os_str uses a module listed above it, which is the healthy direction.
15→1 clap_builder.builder.possible_value uses clap_builder.builder.styled_str✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.possible_value uses a type in clap_builder.builder.styled_str.
- The types involved
clap_builder.builder.possible_value.PossibleValue→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_builder.builder.possible_value uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_builder.builder.possible_value, while a change to clap_builder.builder.possible_value can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_builder.builder.possible_value uses a module listed above it, which is the healthy direction.
15→13 clap_builder.builder.possible_value uses clap_builder.builder.str✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.possible_value uses a type in clap_builder.builder.str.
- The types involved
clap_builder.builder.possible_value.PossibleValue→clap_builder.builder.str.Str
- Direction
- clap_builder.builder.possible_value uses clap_builder.builder.str, so a change to clap_builder.builder.str can break clap_builder.builder.possible_value, while a change to clap_builder.builder.possible_value can't break clap_builder.builder.str.
- Position
- Below the diagonal: clap_builder.builder.possible_value uses a module listed above it, which is the healthy direction.
16→2 clap_builder.parser.matches.arg_matches uses clap_builder.parser.matches.value_source✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.matches.arg_matches uses a type in clap_builder.parser.matches.value_source.
- The types involved
clap_builder.parser.matches.arg_matches.ArgMatches→clap_builder.parser.matches.value_source.ValueSource
- Direction
- clap_builder.parser.matches.arg_matches uses clap_builder.parser.matches.value_source, so a change to clap_builder.parser.matches.value_source can break clap_builder.parser.matches.arg_matches, while a change to clap_builder.parser.matches.arg_matches can't break clap_builder.parser.matches.value_source.
- Position
- Below the diagonal: clap_builder.parser.matches.arg_matches uses a module listed above it, which is the healthy direction.
16→3 clap_builder.parser.matches.arg_matches uses clap_builder.util.any_value✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.matches.arg_matches uses a type in clap_builder.util.any_value.
- The types involved
clap_builder.parser.matches.arg_matches.arg_matches$module→clap_builder.util.any_value.AnyValue
- Direction
- clap_builder.parser.matches.arg_matches uses clap_builder.util.any_value, so a change to clap_builder.util.any_value can break clap_builder.parser.matches.arg_matches, while a change to clap_builder.parser.matches.arg_matches can't break clap_builder.util.any_value.
- Position
- Below the diagonal: clap_builder.parser.matches.arg_matches uses a module listed above it, which is the healthy direction.
16→4 clap_builder.parser.matches.arg_matches uses clap_builder.util.flat_map✕
- Connections
- 2 pairs of types, where a type in clap_builder.parser.matches.arg_matches uses a type in clap_builder.util.flat_map.
- The types involved
clap_builder.parser.matches.arg_matches.ArgMatches→clap_builder.util.flat_map.FlatMapclap_builder.parser.matches.arg_matches.IdsRef→clap_builder.util.flat_map.Iter
- Direction
- clap_builder.parser.matches.arg_matches uses clap_builder.util.flat_map, so a change to clap_builder.util.flat_map can break clap_builder.parser.matches.arg_matches, while a change to clap_builder.parser.matches.arg_matches can't break clap_builder.util.flat_map.
- Position
- Below the diagonal: clap_builder.parser.matches.arg_matches uses a module listed above it, which is the healthy direction.
16→9 clap_builder.parser.matches.arg_matches uses clap_builder.parser.matches.matched_arg✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.matches.arg_matches uses a type in clap_builder.parser.matches.matched_arg.
- The types involved
clap_builder.parser.matches.arg_matches.ArgMatches→clap_builder.parser.matches.matched_arg.MatchedArg
- Direction
- clap_builder.parser.matches.arg_matches uses clap_builder.parser.matches.matched_arg, so a change to clap_builder.parser.matches.matched_arg can break clap_builder.parser.matches.arg_matches, while a change to clap_builder.parser.matches.arg_matches can't break clap_builder.parser.matches.matched_arg.
- Position
- Below the diagonal: clap_builder.parser.matches.arg_matches uses a module listed above it, which is the healthy direction.
16→10 clap_builder.parser.matches.arg_matches uses clap_builder.util.id✕
- Connections
- 2 pairs of types, where a type in clap_builder.parser.matches.arg_matches uses a type in clap_builder.util.id.
- The types involved
clap_builder.parser.matches.arg_matches.ArgMatches→clap_builder.util.id.Idclap_builder.parser.matches.arg_matches.IdsRef→clap_builder.util.id.Id
- Direction
- clap_builder.parser.matches.arg_matches uses clap_builder.util.id, so a change to clap_builder.util.id can break clap_builder.parser.matches.arg_matches, while a change to clap_builder.parser.matches.arg_matches can't break clap_builder.util.id.
- Position
- Below the diagonal: clap_builder.parser.matches.arg_matches uses a module listed above it, which is the healthy direction.
16→13 clap_builder.parser.matches.arg_matches uses clap_builder.builder.str✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.matches.arg_matches uses a type in clap_builder.builder.str.
- The types involved
clap_builder.parser.matches.arg_matches.ArgMatches→clap_builder.builder.str.Str
- Direction
- clap_builder.parser.matches.arg_matches uses clap_builder.builder.str, so a change to clap_builder.builder.str can break clap_builder.parser.matches.arg_matches, while a change to clap_builder.parser.matches.arg_matches can't break clap_builder.builder.str.
- Position
- Below the diagonal: clap_builder.parser.matches.arg_matches uses a module listed above it, which is the healthy direction.
16→14 clap_builder.parser.matches.arg_matches uses clap_builder.builder.os_str✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.matches.arg_matches uses a type in clap_builder.builder.os_str.
- The types involved
clap_builder.parser.matches.arg_matches.RawValues→clap_builder.builder.os_str.OsStr
- Direction
- clap_builder.parser.matches.arg_matches uses clap_builder.builder.os_str, so a change to clap_builder.builder.os_str can break clap_builder.parser.matches.arg_matches, while a change to clap_builder.parser.matches.arg_matches can't break clap_builder.builder.os_str.
- Position
- Below the diagonal: clap_builder.parser.matches.arg_matches uses a module listed above it, which is the healthy direction.
17→1 clap_complete.engine.candidate uses clap_builder.builder.styled_str✕
- Connections
- 1 pair of types, where a type in clap_complete.engine.candidate uses a type in clap_builder.builder.styled_str.
- The types involved
clap_complete.engine.candidate.CompletionCandidate→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_complete.engine.candidate uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_complete.engine.candidate, while a change to clap_complete.engine.candidate can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_complete.engine.candidate uses a module listed above it, which is the healthy direction.
17→14 clap_complete.engine.candidate uses clap_builder.builder.os_str✕
- Connections
- 1 pair of types, where a type in clap_complete.engine.candidate uses a type in clap_builder.builder.os_str.
- The types involved
clap_complete.engine.candidate.CompletionCandidate→clap_builder.builder.os_str.OsStr
- Direction
- clap_complete.engine.candidate uses clap_builder.builder.os_str, so a change to clap_builder.builder.os_str can break clap_complete.engine.candidate, while a change to clap_complete.engine.candidate can't break clap_builder.builder.os_str.
- Position
- Below the diagonal: clap_complete.engine.candidate uses a module listed above it, which is the healthy direction.
18→10 clap_builder.derive uses clap_builder.util.id✕
- Connections
- 1 pair of types, where a type in clap_builder.derive uses a type in clap_builder.util.id.
- The types involved
clap_builder.derive.Args→clap_builder.util.id.Id
- Direction
- clap_builder.derive uses clap_builder.util.id, so a change to clap_builder.util.id can break clap_builder.derive, while a change to clap_builder.derive can't break clap_builder.util.id.
- Position
- Below the diagonal: clap_builder.derive uses a module listed above it, which is the healthy direction.
18→15 clap_builder.derive uses clap_builder.builder.possible_value✕
- Connections
- 1 pair of types, where a type in clap_builder.derive uses a type in clap_builder.builder.possible_value.
- The types involved
clap_builder.derive.ValueEnum→clap_builder.builder.possible_value.PossibleValue
- Direction
- clap_builder.derive uses clap_builder.builder.possible_value, so a change to clap_builder.builder.possible_value can break clap_builder.derive, while a change to clap_builder.derive can't break clap_builder.builder.possible_value.
- Position
- Below the diagonal: clap_builder.derive uses a module listed above it, which is the healthy direction.
18→16 clap_builder.derive uses clap_builder.parser.matches.arg_matches✕
- Connections
- 1 pair of types, where a type in clap_builder.derive uses a type in clap_builder.parser.matches.arg_matches.
- The types involved
clap_builder.derive.FromArgMatches→clap_builder.parser.matches.arg_matches.ArgMatches
- Direction
- clap_builder.derive uses clap_builder.parser.matches.arg_matches, so a change to clap_builder.parser.matches.arg_matches can break clap_builder.derive, while a change to clap_builder.derive can't break clap_builder.parser.matches.arg_matches.
- Position
- Below the diagonal: clap_builder.derive uses a module listed above it, which is the healthy direction.
18→21 clap_builder.derive uses clap_builder.error part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.derive uses a type in clap_builder.error.
- The types involved
clap_builder.derive.derive$module→clap_builder.error.Error
- Direction
- clap_builder.derive uses clap_builder.error, so a change to clap_builder.error can break clap_builder.derive, while a change to clap_builder.derive can't break clap_builder.error.
- 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→22 clap_builder.derive uses clap_builder.builder.command part of a loop✕
- Connections
- 3 pairs of types, where a type in clap_builder.derive uses a type in clap_builder.builder.command.
- The types involved
clap_builder.derive.Args→clap_builder.builder.command.Commandclap_builder.derive.CommandFactory→clap_builder.builder.command.Commandclap_builder.derive.Subcommand→clap_builder.builder.command.Command
- Direction
- clap_builder.derive uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_builder.derive, while a change to clap_builder.derive can't break clap_builder.builder.command.
- 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→18 clap_builder.builder.value_parser.impl_prelude uses clap_builder.derive✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.value_parser.impl_prelude uses a type in clap_builder.derive.
- The types involved
clap_builder.builder.value_parser.impl_prelude._impls_ValueParserFactory→clap_builder.derive.Parser
- Direction
- clap_builder.builder.value_parser.impl_prelude uses clap_builder.derive, so a change to clap_builder.derive can break clap_builder.builder.value_parser.impl_prelude, while a change to clap_builder.builder.value_parser.impl_prelude can't break clap_builder.derive.
- Position
- Below the diagonal: clap_builder.builder.value_parser.impl_prelude uses a module listed above it, which is the healthy direction.
19→28 clap_builder.builder.value_parser.impl_prelude uses clap_builder.builder.value_parser part of a loop✕
- Connections
- 5 pairs of types, where a type in clap_builder.builder.value_parser.impl_prelude uses a type in clap_builder.builder.value_parser.
- The types involved
clap_builder.builder.value_parser.impl_prelude._impls_FromStr→clap_builder.builder.value_parser._AnonymousValueParserclap_builder.builder.value_parser.impl_prelude._impls_From_OsStr→clap_builder.builder.value_parser._AnonymousValueParserclap_builder.builder.value_parser.impl_prelude._impls_From_OsString→clap_builder.builder.value_parser._AnonymousValueParserclap_builder.builder.value_parser.impl_prelude._impls_From_String→clap_builder.builder.value_parser._AnonymousValueParserclap_builder.builder.value_parser.impl_prelude._impls_From_str→clap_builder.builder.value_parser._AnonymousValueParser
- Direction
- clap_builder.builder.value_parser.impl_prelude uses clap_builder.builder.value_parser, so a change to clap_builder.builder.value_parser can break clap_builder.builder.value_parser.impl_prelude, while a change to clap_builder.builder.value_parser.impl_prelude can't break clap_builder.builder.value_parser.
- 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→15 clap_builder.util.color uses clap_builder.builder.possible_value✕
- Connections
- 1 pair of types, where a type in clap_builder.util.color uses a type in clap_builder.builder.possible_value.
- The types involved
clap_builder.util.color.ColorChoice→clap_builder.builder.possible_value.PossibleValue
- Direction
- clap_builder.util.color uses clap_builder.builder.possible_value, so a change to clap_builder.builder.possible_value can break clap_builder.util.color, while a change to clap_builder.util.color can't break clap_builder.builder.possible_value.
- Position
- Below the diagonal: clap_builder.util.color uses a module listed above it, which is the healthy direction.
20→18 clap_builder.util.color uses clap_builder.derive✕
- Connections
- 1 pair of types, where a type in clap_builder.util.color uses a type in clap_builder.derive.
- The types involved
clap_builder.util.color.ColorChoice→clap_builder.derive.ValueEnum
- Direction
- clap_builder.util.color uses clap_builder.derive, so a change to clap_builder.derive can break clap_builder.util.color, while a change to clap_builder.util.color can't break clap_builder.derive.
- Position
- Below the diagonal: clap_builder.util.color uses a module listed above it, which is the healthy direction.
21→1 clap_builder.error uses clap_builder.builder.styled_str✕
- Connections
- 2 pairs of types, where a type in clap_builder.error uses a type in clap_builder.builder.styled_str.
- The types involved
clap_builder.error.Error→clap_builder.builder.styled_str.StyledStrclap_builder.error.Message→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_builder.error uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_builder.error, while a change to clap_builder.error can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_builder.error uses a module listed above it, which is the healthy direction.
21→4 clap_builder.error uses clap_builder.util.flat_map✕
- Connections
- 1 pair of types, where a type in clap_builder.error uses a type in clap_builder.util.flat_map.
- The types involved
clap_builder.error.ErrorInner→clap_builder.util.flat_map.FlatMap
- Direction
- clap_builder.error uses clap_builder.util.flat_map, so a change to clap_builder.util.flat_map can break clap_builder.error, while a change to clap_builder.error can't break clap_builder.util.flat_map.
- Position
- Below the diagonal: clap_builder.error uses a module listed above it, which is the healthy direction.
21→20 clap_builder.error uses clap_builder.util.color✕
- Connections
- 2 pairs of types, where a type in clap_builder.error uses a type in clap_builder.util.color.
- The types involved
clap_builder.error.Error→clap_builder.util.color.ColorChoiceclap_builder.error.ErrorInner→clap_builder.util.color.ColorChoice
- Direction
- clap_builder.error uses clap_builder.util.color, so a change to clap_builder.util.color can break clap_builder.error, while a change to clap_builder.error can't break clap_builder.util.color.
- Position
- Below the diagonal: clap_builder.error uses a module listed above it, which is the healthy direction.
21→22 clap_builder.error uses clap_builder.builder.command part of a loop✕
- Connections
- 2 pairs of types, where a type in clap_builder.error uses a type in clap_builder.builder.command.
- The types involved
clap_builder.error.Error→clap_builder.builder.command.Commandclap_builder.error.Message→clap_builder.builder.command.Command
- Direction
- clap_builder.error uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_builder.error, while a change to clap_builder.error can't break clap_builder.builder.command.
- 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→23 clap_builder.error uses clap_builder.builder.styling part of a loop✕
- Connections
- 3 pairs of types, where a type in clap_builder.error uses a type in clap_builder.builder.styling.
- The types involved
clap_builder.error.Error→clap_builder.builder.styling.Stylesclap_builder.error.ErrorInner→clap_builder.builder.styling.Stylesclap_builder.error.Message→clap_builder.builder.styling.Styles
- Direction
- clap_builder.error uses clap_builder.builder.styling, so a change to clap_builder.builder.styling can break clap_builder.error, while a change to clap_builder.error can't break clap_builder.builder.styling.
- 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→1 clap_builder.builder.command uses clap_builder.builder.styled_str✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.command uses a type in clap_builder.builder.styled_str.
- The types involved
clap_builder.builder.command.Command→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_builder.builder.command uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_builder.builder.command, while a change to clap_builder.builder.command can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_builder.builder.command uses a module listed above it, which is the healthy direction.
22→6 clap_builder.builder.command uses clap_builder.builder.ext✕
- Connections
- 3 pairs of types, where a type in clap_builder.builder.command uses a type in clap_builder.builder.ext.
- The types involved
clap_builder.builder.command.AppExt→clap_builder.builder.ext.Extensionclap_builder.builder.command.Command→clap_builder.builder.ext.Extensionsclap_builder.builder.command.CommandExt→clap_builder.builder.ext.Extension
- Direction
- clap_builder.builder.command uses clap_builder.builder.ext, so a change to clap_builder.builder.ext can break clap_builder.builder.command, while a change to clap_builder.builder.command can't break clap_builder.builder.ext.
- Position
- Below the diagonal: clap_builder.builder.command uses a module listed above it, which is the healthy direction.
22→10 clap_builder.builder.command uses clap_builder.util.id✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.command uses a type in clap_builder.util.id.
- The types involved
clap_builder.builder.command.Command→clap_builder.util.id.Id
- Direction
- clap_builder.builder.command uses clap_builder.util.id, so a change to clap_builder.util.id can break clap_builder.builder.command, while a change to clap_builder.builder.command can't break clap_builder.util.id.
- Position
- Below the diagonal: clap_builder.builder.command uses a module listed above it, which is the healthy direction.
22→12 clap_builder.builder.command uses clap_builder.builder.arg_group✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.command uses a type in clap_builder.builder.arg_group.
- The types involved
clap_builder.builder.command.Command→clap_builder.builder.arg_group.ArgGroup
- Direction
- clap_builder.builder.command uses clap_builder.builder.arg_group, so a change to clap_builder.builder.arg_group can break clap_builder.builder.command, while a change to clap_builder.builder.command can't break clap_builder.builder.arg_group.
- Position
- Below the diagonal: clap_builder.builder.command uses a module listed above it, which is the healthy direction.
22→13 clap_builder.builder.command uses clap_builder.builder.str✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.command uses a type in clap_builder.builder.str.
- The types involved
clap_builder.builder.command.Command→clap_builder.builder.str.Str
- Direction
- clap_builder.builder.command uses clap_builder.builder.str, so a change to clap_builder.builder.str can break clap_builder.builder.command, while a change to clap_builder.builder.command can't break clap_builder.builder.str.
- Position
- Below the diagonal: clap_builder.builder.command uses a module listed above it, which is the healthy direction.
22→16 clap_builder.builder.command uses clap_builder.parser.matches.arg_matches✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.command uses a type in clap_builder.parser.matches.arg_matches.
- The types involved
clap_builder.builder.command.Command→clap_builder.parser.matches.arg_matches.ArgMatches
- Direction
- clap_builder.builder.command uses clap_builder.parser.matches.arg_matches, so a change to clap_builder.parser.matches.arg_matches can break clap_builder.builder.command, while a change to clap_builder.builder.command can't break clap_builder.parser.matches.arg_matches.
- Position
- Below the diagonal: clap_builder.builder.command uses a module listed above it, which is the healthy direction.
22→20 clap_builder.builder.command uses clap_builder.util.color✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.command uses a type in clap_builder.util.color.
- The types involved
clap_builder.builder.command.Command→clap_builder.util.color.ColorChoice
- Direction
- clap_builder.builder.command uses clap_builder.util.color, so a change to clap_builder.util.color can break clap_builder.builder.command, while a change to clap_builder.builder.command can't break clap_builder.util.color.
- Position
- Below the diagonal: clap_builder.builder.command uses a module listed above it, which is the healthy direction.
22→21 clap_builder.builder.command uses clap_builder.error✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.command uses a type in clap_builder.error.
- The types involved
clap_builder.builder.command.Command→clap_builder.error.Error
- Direction
- clap_builder.builder.command uses clap_builder.error, so a change to clap_builder.error can break clap_builder.builder.command, while a change to clap_builder.builder.command can't break clap_builder.error.
- Position
- Below the diagonal: clap_builder.builder.command uses a module listed above it, which is the healthy direction.
22→23 clap_builder.builder.command uses clap_builder.builder.styling part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.command uses a type in clap_builder.builder.styling.
- The types involved
clap_builder.builder.command.Command→clap_builder.builder.styling.Styles
- Direction
- clap_builder.builder.command uses clap_builder.builder.styling, so a change to clap_builder.builder.styling can break clap_builder.builder.command, while a change to clap_builder.builder.command can't break clap_builder.builder.styling.
- 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→25 clap_builder.builder.command uses clap_builder.builder.arg part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.command uses a type in clap_builder.builder.arg.
- The types involved
clap_builder.builder.command.Command→clap_builder.builder.arg.Arg
- Direction
- clap_builder.builder.command uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_builder.builder.command, while a change to clap_builder.builder.command can't break clap_builder.builder.arg.
- 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→28 clap_builder.builder.command uses clap_builder.builder.value_parser part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.command uses a type in clap_builder.builder.value_parser.
- The types involved
clap_builder.builder.command.Command→clap_builder.builder.value_parser.ValueParser
- Direction
- clap_builder.builder.command uses clap_builder.builder.value_parser, so a change to clap_builder.builder.value_parser can break clap_builder.builder.command, while a change to clap_builder.builder.command can't break clap_builder.builder.value_parser.
- 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→22 clap_builder.builder.styling uses clap_builder.builder.command✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.styling uses a type in clap_builder.builder.command.
- The types involved
clap_builder.builder.styling.Styles→clap_builder.builder.command.AppExt
- Direction
- clap_builder.builder.styling uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_builder.builder.styling, while a change to clap_builder.builder.styling can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_builder.builder.styling uses a module listed above it, which is the healthy direction.
24→22 clap_complete.aot.generator uses clap_builder.builder.command✕
- Connections
- 2 pairs of types, where a type in clap_complete.aot.generator uses a type in clap_builder.builder.command.
- The types involved
clap_complete.aot.generator.Generator→clap_builder.builder.command.Commandclap_complete.aot.generator.generator$module→clap_builder.builder.command.Command
- Direction
- clap_complete.aot.generator uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_complete.aot.generator, while a change to clap_complete.aot.generator can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_complete.aot.generator uses a module listed above it, which is the healthy direction.
25→1 clap_builder.builder.arg uses clap_builder.builder.styled_str✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.arg uses a type in clap_builder.builder.styled_str.
- The types involved
clap_builder.builder.arg.Arg→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_builder.builder.arg uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_builder.builder.arg, while a change to clap_builder.builder.arg can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_builder.builder.arg uses a module listed above it, which is the healthy direction.
25→6 clap_builder.builder.arg uses clap_builder.builder.ext✕
- Connections
- 2 pairs of types, where a type in clap_builder.builder.arg uses a type in clap_builder.builder.ext.
- The types involved
clap_builder.builder.arg.Arg→clap_builder.builder.ext.Extensionsclap_builder.builder.arg.ArgExt→clap_builder.builder.ext.Extension
- Direction
- clap_builder.builder.arg uses clap_builder.builder.ext, so a change to clap_builder.builder.ext can break clap_builder.builder.arg, while a change to clap_builder.builder.arg can't break clap_builder.builder.ext.
- Position
- Below the diagonal: clap_builder.builder.arg uses a module listed above it, which is the healthy direction.
25→8 clap_builder.builder.arg uses clap_builder.builder.value_hint✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.arg uses a type in clap_builder.builder.value_hint.
- The types involved
clap_builder.builder.arg.Arg→clap_builder.builder.value_hint.ValueHint
- Direction
- clap_builder.builder.arg uses clap_builder.builder.value_hint, so a change to clap_builder.builder.value_hint can break clap_builder.builder.arg, while a change to clap_builder.builder.arg can't break clap_builder.builder.value_hint.
- Position
- Below the diagonal: clap_builder.builder.arg uses a module listed above it, which is the healthy direction.
25→10 clap_builder.builder.arg uses clap_builder.util.id✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.arg uses a type in clap_builder.util.id.
- The types involved
clap_builder.builder.arg.Arg→clap_builder.util.id.Id
- Direction
- clap_builder.builder.arg uses clap_builder.util.id, so a change to clap_builder.util.id can break clap_builder.builder.arg, while a change to clap_builder.builder.arg can't break clap_builder.util.id.
- Position
- Below the diagonal: clap_builder.builder.arg uses a module listed above it, which is the healthy direction.
25→13 clap_builder.builder.arg uses clap_builder.builder.str✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.arg uses a type in clap_builder.builder.str.
- The types involved
clap_builder.builder.arg.Arg→clap_builder.builder.str.Str
- Direction
- clap_builder.builder.arg uses clap_builder.builder.str, so a change to clap_builder.builder.str can break clap_builder.builder.arg, while a change to clap_builder.builder.arg can't break clap_builder.builder.str.
- Position
- Below the diagonal: clap_builder.builder.arg uses a module listed above it, which is the healthy direction.
25→14 clap_builder.builder.arg uses clap_builder.builder.os_str✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.arg uses a type in clap_builder.builder.os_str.
- The types involved
clap_builder.builder.arg.Arg→clap_builder.builder.os_str.OsStr
- Direction
- clap_builder.builder.arg uses clap_builder.builder.os_str, so a change to clap_builder.builder.os_str can break clap_builder.builder.arg, while a change to clap_builder.builder.arg can't break clap_builder.builder.os_str.
- Position
- Below the diagonal: clap_builder.builder.arg uses a module listed above it, which is the healthy direction.
25→15 clap_builder.builder.arg uses clap_builder.builder.possible_value✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.arg uses a type in clap_builder.builder.possible_value.
- The types involved
clap_builder.builder.arg.Arg→clap_builder.builder.possible_value.PossibleValue
- Direction
- clap_builder.builder.arg uses clap_builder.builder.possible_value, so a change to clap_builder.builder.possible_value can break clap_builder.builder.arg, while a change to clap_builder.builder.arg can't break clap_builder.builder.possible_value.
- Position
- Below the diagonal: clap_builder.builder.arg uses a module listed above it, which is the healthy direction.
25→23 clap_builder.builder.arg uses clap_builder.builder.styling✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.arg uses a type in clap_builder.builder.styling.
- The types involved
clap_builder.builder.arg.Arg→clap_builder.builder.styling.Styles
- Direction
- clap_builder.builder.arg uses clap_builder.builder.styling, so a change to clap_builder.builder.styling can break clap_builder.builder.arg, while a change to clap_builder.builder.arg can't break clap_builder.builder.styling.
- Position
- Below the diagonal: clap_builder.builder.arg uses a module listed above it, which is the healthy direction.
25→28 clap_builder.builder.arg uses clap_builder.builder.value_parser part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.arg uses a type in clap_builder.builder.value_parser.
- The types involved
clap_builder.builder.arg.Arg→clap_builder.builder.value_parser.ValueParser
- Direction
- clap_builder.builder.arg uses clap_builder.builder.value_parser, so a change to clap_builder.builder.value_parser can break clap_builder.builder.arg, while a change to clap_builder.builder.arg can't break clap_builder.builder.value_parser.
- 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→36 clap_builder.builder.arg uses clap_builder.builder.action part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.arg uses a type in clap_builder.builder.action.
- The types involved
clap_builder.builder.arg.Arg→clap_builder.builder.action.ArgAction
- Direction
- clap_builder.builder.arg uses clap_builder.builder.action, so a change to clap_builder.builder.action can break clap_builder.builder.arg, while a change to clap_builder.builder.arg can't break clap_builder.builder.action.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→1 clap_builder.error.format uses clap_builder.builder.styled_str✕
- Connections
- 4 pairs of types, where a type in clap_builder.error.format uses a type in clap_builder.builder.styled_str.
- The types involved
clap_builder.error.format.ErrorFormatter→clap_builder.builder.styled_str.StyledStrclap_builder.error.format.KindFormatter→clap_builder.builder.styled_str.StyledStrclap_builder.error.format.RichFormatter→clap_builder.builder.styled_str.StyledStrclap_builder.error.format.format$module→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_builder.error.format uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_builder.error.format, while a change to clap_builder.error.format can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_builder.error.format uses a module listed above it, which is the healthy direction.
26→21 clap_builder.error.format uses clap_builder.error✕
- Connections
- 4 pairs of types, where a type in clap_builder.error.format uses a type in clap_builder.error.
- The types involved
clap_builder.error.format.ErrorFormatter→clap_builder.error.Errorclap_builder.error.format.KindFormatter→clap_builder.error.Errorclap_builder.error.format.RichFormatter→clap_builder.error.Errorclap_builder.error.format.format$module→clap_builder.error.Error
- Direction
- clap_builder.error.format uses clap_builder.error, so a change to clap_builder.error can break clap_builder.error.format, while a change to clap_builder.error.format can't break clap_builder.error.
- Position
- Below the diagonal: clap_builder.error.format uses a module listed above it, which is the healthy direction.
26→22 clap_builder.error.format uses clap_builder.builder.command✕
- Connections
- 1 pair of types, where a type in clap_builder.error.format uses a type in clap_builder.builder.command.
- The types involved
clap_builder.error.format.format$module→clap_builder.builder.command.Command
- Direction
- clap_builder.error.format uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_builder.error.format, while a change to clap_builder.error.format can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_builder.error.format uses a module listed above it, which is the healthy direction.
26→23 clap_builder.error.format uses clap_builder.builder.styling✕
- Connections
- 1 pair of types, where a type in clap_builder.error.format uses a type in clap_builder.builder.styling.
- The types involved
clap_builder.error.format.format$module→clap_builder.builder.styling.Styles
- Direction
- clap_builder.error.format uses clap_builder.builder.styling, so a change to clap_builder.builder.styling can break clap_builder.error.format, while a change to clap_builder.error.format can't break clap_builder.builder.styling.
- Position
- Below the diagonal: clap_builder.error.format uses a module listed above it, which is the healthy direction.
27→15 clap_complete.aot.shells.shell uses clap_builder.builder.possible_value✕
- Connections
- 1 pair of types, where a type in clap_complete.aot.shells.shell uses a type in clap_builder.builder.possible_value.
- The types involved
clap_complete.aot.shells.shell.Shell→clap_builder.builder.possible_value.PossibleValue
- Direction
- clap_complete.aot.shells.shell uses clap_builder.builder.possible_value, so a change to clap_builder.builder.possible_value can break clap_complete.aot.shells.shell, while a change to clap_complete.aot.shells.shell can't break clap_builder.builder.possible_value.
- Position
- Below the diagonal: clap_complete.aot.shells.shell uses a module listed above it, which is the healthy direction.
27→18 clap_complete.aot.shells.shell uses clap_builder.derive✕
- Connections
- 1 pair of types, where a type in clap_complete.aot.shells.shell uses a type in clap_builder.derive.
- The types involved
clap_complete.aot.shells.shell.Shell→clap_builder.derive.ValueEnum
- Direction
- clap_complete.aot.shells.shell uses clap_builder.derive, so a change to clap_builder.derive can break clap_complete.aot.shells.shell, while a change to clap_complete.aot.shells.shell can't break clap_builder.derive.
- Position
- Below the diagonal: clap_complete.aot.shells.shell uses a module listed above it, which is the healthy direction.
27→22 clap_complete.aot.shells.shell uses clap_builder.builder.command✕
- Connections
- 1 pair of types, where a type in clap_complete.aot.shells.shell uses a type in clap_builder.builder.command.
- The types involved
clap_complete.aot.shells.shell.Shell→clap_builder.builder.command.Command
- Direction
- clap_complete.aot.shells.shell uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_complete.aot.shells.shell, while a change to clap_complete.aot.shells.shell can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_complete.aot.shells.shell uses a module listed above it, which is the healthy direction.
27→24 clap_complete.aot.shells.shell uses clap_complete.aot.generator✕
- Connections
- 1 pair of types, where a type in clap_complete.aot.shells.shell uses a type in clap_complete.aot.generator.
- The types involved
clap_complete.aot.shells.shell.Shell→clap_complete.aot.generator.Generator
- Direction
- clap_complete.aot.shells.shell uses clap_complete.aot.generator, so a change to clap_complete.aot.generator can break clap_complete.aot.shells.shell, while a change to clap_complete.aot.shells.shell can't break clap_complete.aot.generator.
- Position
- Below the diagonal: clap_complete.aot.shells.shell uses a module listed above it, which is the healthy direction.
28→1 clap_builder.builder.value_parser uses clap_builder.builder.styled_str✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.value_parser uses a type in clap_builder.builder.styled_str.
- The types involved
clap_builder.builder.value_parser.UnknownArgumentValueParser→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_builder.builder.value_parser uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_builder.builder.value_parser, while a change to clap_builder.builder.value_parser can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_builder.builder.value_parser uses a module listed above it, which is the healthy direction.
28→2 clap_builder.builder.value_parser uses clap_builder.parser.matches.value_source✕
- Connections
- 4 pairs of types, where a type in clap_builder.builder.value_parser uses a type in clap_builder.parser.matches.value_source.
- The types involved
clap_builder.builder.value_parser.AnyValueParser→clap_builder.parser.matches.value_source.ValueSourceclap_builder.builder.value_parser.TypedValueParser→clap_builder.parser.matches.value_source.ValueSourceclap_builder.builder.value_parser.UnknownArgumentValueParser→clap_builder.parser.matches.value_source.ValueSourceclap_builder.builder.value_parser.ValueParser→clap_builder.parser.matches.value_source.ValueSource
- Direction
- clap_builder.builder.value_parser uses clap_builder.parser.matches.value_source, so a change to clap_builder.parser.matches.value_source can break clap_builder.builder.value_parser, while a change to clap_builder.builder.value_parser can't break clap_builder.parser.matches.value_source.
- Position
- Below the diagonal: clap_builder.builder.value_parser uses a module listed above it, which is the healthy direction.
28→3 clap_builder.builder.value_parser uses clap_builder.util.any_value✕
- Connections
- 2 pairs of types, where a type in clap_builder.builder.value_parser uses a type in clap_builder.util.any_value.
- The types involved
clap_builder.builder.value_parser.AnyValueParser→clap_builder.util.any_value.AnyValueIdclap_builder.builder.value_parser.ValueParser→clap_builder.util.any_value.AnyValueId
- Direction
- clap_builder.builder.value_parser uses clap_builder.util.any_value, so a change to clap_builder.util.any_value can break clap_builder.builder.value_parser, while a change to clap_builder.builder.value_parser can't break clap_builder.util.any_value.
- Position
- Below the diagonal: clap_builder.builder.value_parser uses a module listed above it, which is the healthy direction.
28→13 clap_builder.builder.value_parser uses clap_builder.builder.str✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.value_parser uses a type in clap_builder.builder.str.
- The types involved
clap_builder.builder.value_parser.UnknownArgumentValueParser→clap_builder.builder.str.Str
- Direction
- clap_builder.builder.value_parser uses clap_builder.builder.str, so a change to clap_builder.builder.str can break clap_builder.builder.value_parser, while a change to clap_builder.builder.value_parser can't break clap_builder.builder.str.
- Position
- Below the diagonal: clap_builder.builder.value_parser uses a module listed above it, which is the healthy direction.
28→14 clap_builder.builder.value_parser uses clap_builder.builder.os_str✕
- Connections
- 17 pairs of types, where a type in clap_builder.builder.value_parser uses a type in clap_builder.builder.os_str.
- The types involved
clap_builder.builder.value_parser.AnyValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.BoolValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.BoolishValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.EnumValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.FalseyValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.MapValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.NonEmptyStringValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.OsStringValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.PathBufValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.PossibleValuesParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.RangedI64ValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.RangedU64ValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.StringValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.TryMapValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.TypedValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.UnknownArgumentValueParser→clap_builder.builder.os_str.OsStrclap_builder.builder.value_parser.ValueParser→clap_builder.builder.os_str.OsStr
- Direction
- clap_builder.builder.value_parser uses clap_builder.builder.os_str, so a change to clap_builder.builder.os_str can break clap_builder.builder.value_parser, while a change to clap_builder.builder.value_parser can't break clap_builder.builder.os_str.
- Position
- Below the diagonal: clap_builder.builder.value_parser uses a module listed above it, which is the healthy direction.
28→15 clap_builder.builder.value_parser uses clap_builder.builder.possible_value✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.value_parser uses a type in clap_builder.builder.possible_value.
- The types involved
clap_builder.builder.value_parser.PossibleValuesParser→clap_builder.builder.possible_value.PossibleValue
- Direction
- clap_builder.builder.value_parser uses clap_builder.builder.possible_value, so a change to clap_builder.builder.possible_value can break clap_builder.builder.value_parser, while a change to clap_builder.builder.value_parser can't break clap_builder.builder.possible_value.
- Position
- Below the diagonal: clap_builder.builder.value_parser uses a module listed above it, which is the healthy direction.
28→18 clap_builder.builder.value_parser uses clap_builder.derive✕
- Connections
- 2 pairs of types, where a type in clap_builder.builder.value_parser uses a type in clap_builder.derive.
- The types involved
clap_builder.builder.value_parser.ValueParserFactory→clap_builder.derive.Parserclap_builder.builder.value_parser._infer_ValueParser_for→clap_builder.derive.Parser
- Direction
- clap_builder.builder.value_parser uses clap_builder.derive, so a change to clap_builder.derive can break clap_builder.builder.value_parser, while a change to clap_builder.builder.value_parser can't break clap_builder.derive.
- Position
- Below the diagonal: clap_builder.builder.value_parser uses a module listed above it, which is the healthy direction.
28→19 clap_builder.builder.value_parser uses clap_builder.builder.value_parser.impl_prelude✕
- Connections
- 7 pairs of types, where a type in clap_builder.builder.value_parser uses a type in clap_builder.builder.value_parser.impl_prelude.
- The types involved
clap_builder.builder.value_parser._infer_ValueParser_for→clap_builder.builder.value_parser.impl_prelude._impls_FromStrclap_builder.builder.value_parser._infer_ValueParser_for→clap_builder.builder.value_parser.impl_prelude._impls_From_OsStrclap_builder.builder.value_parser._infer_ValueParser_for→clap_builder.builder.value_parser.impl_prelude._impls_From_OsStringclap_builder.builder.value_parser._infer_ValueParser_for→clap_builder.builder.value_parser.impl_prelude._impls_From_Stringclap_builder.builder.value_parser._infer_ValueParser_for→clap_builder.builder.value_parser.impl_prelude._impls_From_strclap_builder.builder.value_parser._infer_ValueParser_for→clap_builder.builder.value_parser.impl_prelude._impls_ValueEnumclap_builder.builder.value_parser._infer_ValueParser_for→clap_builder.builder.value_parser.impl_prelude._impls_ValueParserFactory
- Direction
- clap_builder.builder.value_parser uses clap_builder.builder.value_parser.impl_prelude, so a change to clap_builder.builder.value_parser.impl_prelude can break clap_builder.builder.value_parser, while a change to clap_builder.builder.value_parser can't break clap_builder.builder.value_parser.impl_prelude.
- Position
- Below the diagonal: clap_builder.builder.value_parser uses a module listed above it, which is the healthy direction.
28→22 clap_builder.builder.value_parser uses clap_builder.builder.command✕
- Connections
- 17 pairs of types, where a type in clap_builder.builder.value_parser uses a type in clap_builder.builder.command.
- The types involved
clap_builder.builder.value_parser.AnyValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.BoolValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.BoolishValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.EnumValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.FalseyValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.MapValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.NonEmptyStringValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.OsStringValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.PathBufValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.PossibleValuesParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.RangedI64ValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.RangedU64ValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.StringValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.TryMapValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.TypedValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.UnknownArgumentValueParser→clap_builder.builder.command.Commandclap_builder.builder.value_parser.ValueParser→clap_builder.builder.command.Command
- Direction
- clap_builder.builder.value_parser uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_builder.builder.value_parser, while a change to clap_builder.builder.value_parser can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_builder.builder.value_parser uses a module listed above it, which is the healthy direction.
28→25 clap_builder.builder.value_parser uses clap_builder.builder.arg✕
- Connections
- 17 pairs of types, where a type in clap_builder.builder.value_parser uses a type in clap_builder.builder.arg.
- The types involved
clap_builder.builder.value_parser.AnyValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.BoolValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.BoolishValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.EnumValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.FalseyValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.MapValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.NonEmptyStringValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.OsStringValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.PathBufValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.PossibleValuesParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.RangedI64ValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.RangedU64ValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.StringValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.TryMapValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.TypedValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.UnknownArgumentValueParser→clap_builder.builder.arg.Argclap_builder.builder.value_parser.ValueParser→clap_builder.builder.arg.Arg
- Direction
- clap_builder.builder.value_parser uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_builder.builder.value_parser, while a change to clap_builder.builder.value_parser can't break clap_builder.builder.arg.
- Position
- Below the diagonal: clap_builder.builder.value_parser uses a module listed above it, which is the healthy direction.
29→2 clap_builder.parser.parser uses clap_builder.parser.matches.value_source✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.parser uses a type in clap_builder.parser.matches.value_source.
- The types involved
clap_builder.parser.parser.Parser→clap_builder.parser.matches.value_source.ValueSource
- Direction
- clap_builder.parser.parser uses clap_builder.parser.matches.value_source, so a change to clap_builder.parser.matches.value_source can break clap_builder.parser.parser, while a change to clap_builder.parser.parser can't break clap_builder.parser.matches.value_source.
- Position
- Below the diagonal: clap_builder.parser.parser uses a module listed above it, which is the healthy direction.
29→10 clap_builder.parser.parser uses clap_builder.util.id✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.parser uses a type in clap_builder.util.id.
- The types involved
clap_builder.parser.parser.PendingArg→clap_builder.util.id.Id
- Direction
- clap_builder.parser.parser uses clap_builder.util.id, so a change to clap_builder.util.id can break clap_builder.parser.parser, while a change to clap_builder.parser.parser can't break clap_builder.util.id.
- Position
- Below the diagonal: clap_builder.parser.parser uses a module listed above it, which is the healthy direction.
29→14 clap_builder.parser.parser uses clap_builder.builder.os_str✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.parser uses a type in clap_builder.builder.os_str.
- The types involved
clap_builder.parser.parser.Parser→clap_builder.builder.os_str.OsStr
- Direction
- clap_builder.parser.parser uses clap_builder.builder.os_str, so a change to clap_builder.builder.os_str can break clap_builder.parser.parser, while a change to clap_builder.parser.parser can't break clap_builder.builder.os_str.
- Position
- Below the diagonal: clap_builder.parser.parser uses a module listed above it, which is the healthy direction.
29→22 clap_builder.parser.parser uses clap_builder.builder.command✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.parser uses a type in clap_builder.builder.command.
- The types involved
clap_builder.parser.parser.Parser→clap_builder.builder.command.Command
- Direction
- clap_builder.parser.parser uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_builder.parser.parser, while a change to clap_builder.parser.parser can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_builder.parser.parser uses a module listed above it, which is the healthy direction.
29→25 clap_builder.parser.parser uses clap_builder.builder.arg✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.parser uses a type in clap_builder.builder.arg.
- The types involved
clap_builder.parser.parser.Parser→clap_builder.builder.arg.Arg
- Direction
- clap_builder.parser.parser uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_builder.parser.parser, while a change to clap_builder.parser.parser can't break clap_builder.builder.arg.
- Position
- Below the diagonal: clap_builder.parser.parser uses a module listed above it, which is the healthy direction.
29→37 clap_builder.parser.parser uses clap_builder.parser.arg_matcher part of a loop✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.parser uses a type in clap_builder.parser.arg_matcher.
- The types involved
clap_builder.parser.parser.Parser→clap_builder.parser.arg_matcher.ArgMatcher
- Direction
- clap_builder.parser.parser uses clap_builder.parser.arg_matcher, so a change to clap_builder.parser.arg_matcher can break clap_builder.parser.parser, while a change to clap_builder.parser.parser can't break clap_builder.parser.arg_matcher.
- 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.
30→1 clap_complete.aot.shells.fish uses clap_builder.builder.styled_str✕
- Connections
- 1 pair of types, where a type in clap_complete.aot.shells.fish uses a type in clap_builder.builder.styled_str.
- The types involved
clap_complete.aot.shells.fish.fish$module→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_complete.aot.shells.fish uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_complete.aot.shells.fish, while a change to clap_complete.aot.shells.fish can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_complete.aot.shells.fish uses a module listed above it, which is the healthy direction.
30→22 clap_complete.aot.shells.fish uses clap_builder.builder.command✕
- Connections
- 2 pairs of types, where a type in clap_complete.aot.shells.fish uses a type in clap_builder.builder.command.
- The types involved
clap_complete.aot.shells.fish.Fish→clap_builder.builder.command.Commandclap_complete.aot.shells.fish.fish$module→clap_builder.builder.command.Command
- Direction
- clap_complete.aot.shells.fish uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_complete.aot.shells.fish, while a change to clap_complete.aot.shells.fish can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_complete.aot.shells.fish uses a module listed above it, which is the healthy direction.
30→24 clap_complete.aot.shells.fish uses clap_complete.aot.generator✕
- Connections
- 1 pair of types, where a type in clap_complete.aot.shells.fish uses a type in clap_complete.aot.generator.
- The types involved
clap_complete.aot.shells.fish.Fish→clap_complete.aot.generator.Generator
- Direction
- clap_complete.aot.shells.fish uses clap_complete.aot.generator, so a change to clap_complete.aot.generator can break clap_complete.aot.shells.fish, while a change to clap_complete.aot.shells.fish can't break clap_complete.aot.generator.
- Position
- Below the diagonal: clap_complete.aot.shells.fish uses a module listed above it, which is the healthy direction.
30→25 clap_complete.aot.shells.fish uses clap_builder.builder.arg✕
- Connections
- 1 pair of types, where a type in clap_complete.aot.shells.fish uses a type in clap_builder.builder.arg.
- The types involved
clap_complete.aot.shells.fish.fish$module→clap_builder.builder.arg.Arg
- Direction
- clap_complete.aot.shells.fish uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_complete.aot.shells.fish, while a change to clap_complete.aot.shells.fish can't break clap_builder.builder.arg.
- Position
- Below the diagonal: clap_complete.aot.shells.fish uses a module listed above it, which is the healthy direction.
31→1 clap_complete.aot.shells.powershell uses clap_builder.builder.styled_str✕
- Connections
- 1 pair of types, where a type in clap_complete.aot.shells.powershell uses a type in clap_builder.builder.styled_str.
- The types involved
clap_complete.aot.shells.powershell.powershell$module→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_complete.aot.shells.powershell uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_complete.aot.shells.powershell, while a change to clap_complete.aot.shells.powershell can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_complete.aot.shells.powershell uses a module listed above it, which is the healthy direction.
31→22 clap_complete.aot.shells.powershell uses clap_builder.builder.command✕
- Connections
- 2 pairs of types, where a type in clap_complete.aot.shells.powershell uses a type in clap_builder.builder.command.
- The types involved
clap_complete.aot.shells.powershell.PowerShell→clap_builder.builder.command.Commandclap_complete.aot.shells.powershell.powershell$module→clap_builder.builder.command.Command
- Direction
- clap_complete.aot.shells.powershell uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_complete.aot.shells.powershell, while a change to clap_complete.aot.shells.powershell can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_complete.aot.shells.powershell uses a module listed above it, which is the healthy direction.
31→24 clap_complete.aot.shells.powershell uses clap_complete.aot.generator✕
- Connections
- 1 pair of types, where a type in clap_complete.aot.shells.powershell uses a type in clap_complete.aot.generator.
- The types involved
clap_complete.aot.shells.powershell.PowerShell→clap_complete.aot.generator.Generator
- Direction
- clap_complete.aot.shells.powershell uses clap_complete.aot.generator, so a change to clap_complete.aot.generator can break clap_complete.aot.shells.powershell, while a change to clap_complete.aot.shells.powershell can't break clap_complete.aot.generator.
- Position
- Below the diagonal: clap_complete.aot.shells.powershell uses a module listed above it, which is the healthy direction.
31→25 clap_complete.aot.shells.powershell uses clap_builder.builder.arg✕
- Connections
- 1 pair of types, where a type in clap_complete.aot.shells.powershell uses a type in clap_builder.builder.arg.
- The types involved
clap_complete.aot.shells.powershell.powershell$module→clap_builder.builder.arg.Arg
- Direction
- clap_complete.aot.shells.powershell uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_complete.aot.shells.powershell, while a change to clap_complete.aot.shells.powershell can't break clap_builder.builder.arg.
- Position
- Below the diagonal: clap_complete.aot.shells.powershell uses a module listed above it, which is the healthy direction.
32→14 clap_complete.engine.complete uses clap_builder.builder.os_str✕
- Connections
- 1 pair of types, where a type in clap_complete.engine.complete uses a type in clap_builder.builder.os_str.
- The types involved
clap_complete.engine.complete.complete$module→clap_builder.builder.os_str.OsStr
- Direction
- clap_complete.engine.complete uses clap_builder.builder.os_str, so a change to clap_builder.builder.os_str can break clap_complete.engine.complete, while a change to clap_complete.engine.complete can't break clap_builder.builder.os_str.
- Position
- Below the diagonal: clap_complete.engine.complete uses a module listed above it, which is the healthy direction.
32→17 clap_complete.engine.complete uses clap_complete.engine.candidate✕
- Connections
- 1 pair of types, where a type in clap_complete.engine.complete uses a type in clap_complete.engine.candidate.
- The types involved
clap_complete.engine.complete.complete$module→clap_complete.engine.candidate.CompletionCandidate
- Direction
- clap_complete.engine.complete uses clap_complete.engine.candidate, so a change to clap_complete.engine.candidate can break clap_complete.engine.complete, while a change to clap_complete.engine.complete can't break clap_complete.engine.candidate.
- Position
- Below the diagonal: clap_complete.engine.complete uses a module listed above it, which is the healthy direction.
32→22 clap_complete.engine.complete uses clap_builder.builder.command✕
- Connections
- 1 pair of types, where a type in clap_complete.engine.complete uses a type in clap_builder.builder.command.
- The types involved
clap_complete.engine.complete.complete$module→clap_builder.builder.command.Command
- Direction
- clap_complete.engine.complete uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_complete.engine.complete, while a change to clap_complete.engine.complete can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_complete.engine.complete uses a module listed above it, which is the healthy direction.
32→25 clap_complete.engine.complete uses clap_builder.builder.arg✕
- Connections
- 1 pair of types, where a type in clap_complete.engine.complete uses a type in clap_builder.builder.arg.
- The types involved
clap_complete.engine.complete.complete$module→clap_builder.builder.arg.Arg
- Direction
- clap_complete.engine.complete uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_complete.engine.complete, while a change to clap_complete.engine.complete can't break clap_builder.builder.arg.
- Position
- Below the diagonal: clap_complete.engine.complete uses a module listed above it, which is the healthy direction.
33→14 clap_complete.engine.custom uses clap_builder.builder.os_str✕
- Connections
- 4 pairs of types, where a type in clap_complete.engine.custom uses a type in clap_builder.builder.os_str.
- The types involved
clap_complete.engine.custom.ArgValueCompleter→clap_builder.builder.os_str.OsStrclap_complete.engine.custom.PathCompleter→clap_builder.builder.os_str.OsStrclap_complete.engine.custom.ValueCompleter→clap_builder.builder.os_str.OsStrclap_complete.engine.custom.custom$module→clap_builder.builder.os_str.OsStr
- Direction
- clap_complete.engine.custom uses clap_builder.builder.os_str, so a change to clap_builder.builder.os_str can break clap_complete.engine.custom, while a change to clap_complete.engine.custom can't break clap_builder.builder.os_str.
- Position
- Below the diagonal: clap_complete.engine.custom uses a module listed above it, which is the healthy direction.
33→17 clap_complete.engine.custom uses clap_complete.engine.candidate✕
- Connections
- 7 pairs of types, where a type in clap_complete.engine.custom uses a type in clap_complete.engine.candidate.
- The types involved
clap_complete.engine.custom.ArgValueCandidates→clap_complete.engine.candidate.CompletionCandidateclap_complete.engine.custom.ArgValueCompleter→clap_complete.engine.candidate.CompletionCandidateclap_complete.engine.custom.PathCompleter→clap_complete.engine.candidate.CompletionCandidateclap_complete.engine.custom.SubcommandCandidates→clap_complete.engine.candidate.CompletionCandidateclap_complete.engine.custom.ValueCandidates→clap_complete.engine.candidate.CompletionCandidateclap_complete.engine.custom.ValueCompleter→clap_complete.engine.candidate.CompletionCandidateclap_complete.engine.custom.custom$module→clap_complete.engine.candidate.CompletionCandidate
- Direction
- clap_complete.engine.custom uses clap_complete.engine.candidate, so a change to clap_complete.engine.candidate can break clap_complete.engine.custom, while a change to clap_complete.engine.custom can't break clap_complete.engine.candidate.
- Position
- Below the diagonal: clap_complete.engine.custom uses a module listed above it, which is the healthy direction.
33→22 clap_complete.engine.custom uses clap_builder.builder.command✕
- Connections
- 1 pair of types, where a type in clap_complete.engine.custom uses a type in clap_builder.builder.command.
- The types involved
clap_complete.engine.custom.SubcommandCandidates→clap_builder.builder.command.CommandExt
- Direction
- clap_complete.engine.custom uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_complete.engine.custom, while a change to clap_complete.engine.custom can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_complete.engine.custom uses a module listed above it, which is the healthy direction.
33→25 clap_complete.engine.custom uses clap_builder.builder.arg✕
- Connections
- 2 pairs of types, where a type in clap_complete.engine.custom uses a type in clap_builder.builder.arg.
- The types involved
clap_complete.engine.custom.ArgValueCandidates→clap_builder.builder.arg.ArgExtclap_complete.engine.custom.ArgValueCompleter→clap_builder.builder.arg.ArgExt
- Direction
- clap_complete.engine.custom uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_complete.engine.custom, while a change to clap_complete.engine.custom can't break clap_builder.builder.arg.
- Position
- Below the diagonal: clap_complete.engine.custom uses a module listed above it, which is the healthy direction.
34→1 clap_complete_nushell uses clap_builder.builder.styled_str✕
- Connections
- 1 pair of types, where a type in clap_complete_nushell uses a type in clap_builder.builder.styled_str.
- The types involved
clap_complete_nushell.clap_complete_nushell$module→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_complete_nushell uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_complete_nushell, while a change to clap_complete_nushell can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_complete_nushell uses a module listed above it, which is the healthy direction.
34→22 clap_complete_nushell uses clap_builder.builder.command✕
- Connections
- 2 pairs of types, where a type in clap_complete_nushell uses a type in clap_builder.builder.command.
- The types involved
clap_complete_nushell.Nushell→clap_builder.builder.command.Commandclap_complete_nushell.clap_complete_nushell$module→clap_builder.builder.command.Command
- Direction
- clap_complete_nushell uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_complete_nushell, while a change to clap_complete_nushell can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_complete_nushell uses a module listed above it, which is the healthy direction.
34→24 clap_complete_nushell uses clap_complete.aot.generator✕
- Connections
- 1 pair of types, where a type in clap_complete_nushell uses a type in clap_complete.aot.generator.
- The types involved
clap_complete_nushell.Nushell→clap_complete.aot.generator.Generator
- Direction
- clap_complete_nushell uses clap_complete.aot.generator, so a change to clap_complete.aot.generator can break clap_complete_nushell, while a change to clap_complete_nushell can't break clap_complete.aot.generator.
- Position
- Below the diagonal: clap_complete_nushell uses a module listed above it, which is the healthy direction.
34→25 clap_complete_nushell uses clap_builder.builder.arg✕
- Connections
- 1 pair of types, where a type in clap_complete_nushell uses a type in clap_builder.builder.arg.
- The types involved
clap_complete_nushell.clap_complete_nushell$module→clap_builder.builder.arg.Arg
- Direction
- clap_complete_nushell uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_complete_nushell, while a change to clap_complete_nushell can't break clap_builder.builder.arg.
- Position
- Below the diagonal: clap_complete_nushell uses a module listed above it, which is the healthy direction.
35→1 clap_mangen.render uses clap_builder.builder.styled_str✕
- Connections
- 1 pair of types, where a type in clap_mangen.render uses a type in clap_builder.builder.styled_str.
- The types involved
clap_mangen.render.render$module→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_mangen.render uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_mangen.render, while a change to clap_mangen.render can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_mangen.render uses a module listed above it, which is the healthy direction.
35→10 clap_mangen.render uses clap_builder.util.id✕
- Connections
- 1 pair of types, where a type in clap_mangen.render uses a type in clap_builder.util.id.
- The types involved
clap_mangen.render.render$module→clap_builder.util.id.Id
- Direction
- clap_mangen.render uses clap_builder.util.id, so a change to clap_builder.util.id can break clap_mangen.render, while a change to clap_mangen.render can't break clap_builder.util.id.
- Position
- Below the diagonal: clap_mangen.render uses a module listed above it, which is the healthy direction.
35→15 clap_mangen.render uses clap_builder.builder.possible_value✕
- Connections
- 1 pair of types, where a type in clap_mangen.render uses a type in clap_builder.builder.possible_value.
- The types involved
clap_mangen.render.render$module→clap_builder.builder.possible_value.PossibleValue
- Direction
- clap_mangen.render uses clap_builder.builder.possible_value, so a change to clap_builder.builder.possible_value can break clap_mangen.render, while a change to clap_mangen.render can't break clap_builder.builder.possible_value.
- Position
- Below the diagonal: clap_mangen.render uses a module listed above it, which is the healthy direction.
35→22 clap_mangen.render uses clap_builder.builder.command✕
- Connections
- 1 pair of types, where a type in clap_mangen.render uses a type in clap_builder.builder.command.
- The types involved
clap_mangen.render.render$module→clap_builder.builder.command.Command
- Direction
- clap_mangen.render uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_mangen.render, while a change to clap_mangen.render can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_mangen.render uses a module listed above it, which is the healthy direction.
35→25 clap_mangen.render uses clap_builder.builder.arg✕
- Connections
- 1 pair of types, where a type in clap_mangen.render uses a type in clap_builder.builder.arg.
- The types involved
clap_mangen.render.render$module→clap_builder.builder.arg.Arg
- Direction
- clap_mangen.render uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_mangen.render, while a change to clap_mangen.render can't break clap_builder.builder.arg.
- Position
- Below the diagonal: clap_mangen.render uses a module listed above it, which is the healthy direction.
36→3 clap_builder.builder.action uses clap_builder.util.any_value✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.action uses a type in clap_builder.util.any_value.
- The types involved
clap_builder.builder.action.ArgAction→clap_builder.util.any_value.AnyValueId
- Direction
- clap_builder.builder.action uses clap_builder.util.any_value, so a change to clap_builder.util.any_value can break clap_builder.builder.action, while a change to clap_builder.builder.action can't break clap_builder.util.any_value.
- Position
- Below the diagonal: clap_builder.builder.action uses a module listed above it, which is the healthy direction.
36→14 clap_builder.builder.action uses clap_builder.builder.os_str✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.action uses a type in clap_builder.builder.os_str.
- The types involved
clap_builder.builder.action.ArgAction→clap_builder.builder.os_str.OsStr
- Direction
- clap_builder.builder.action uses clap_builder.builder.os_str, so a change to clap_builder.builder.os_str can break clap_builder.builder.action, while a change to clap_builder.builder.action can't break clap_builder.builder.os_str.
- Position
- Below the diagonal: clap_builder.builder.action uses a module listed above it, which is the healthy direction.
36→28 clap_builder.builder.action uses clap_builder.builder.value_parser✕
- Connections
- 1 pair of types, where a type in clap_builder.builder.action uses a type in clap_builder.builder.value_parser.
- The types involved
clap_builder.builder.action.ArgAction→clap_builder.builder.value_parser.ValueParser
- Direction
- clap_builder.builder.action uses clap_builder.builder.value_parser, so a change to clap_builder.builder.value_parser can break clap_builder.builder.action, while a change to clap_builder.builder.action can't break clap_builder.builder.value_parser.
- Position
- Below the diagonal: clap_builder.builder.action uses a module listed above it, which is the healthy direction.
37→2 clap_builder.parser.arg_matcher uses clap_builder.parser.matches.value_source✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.arg_matcher uses a type in clap_builder.parser.matches.value_source.
- The types involved
clap_builder.parser.arg_matcher.ArgMatcher→clap_builder.parser.matches.value_source.ValueSource
- Direction
- clap_builder.parser.arg_matcher uses clap_builder.parser.matches.value_source, so a change to clap_builder.parser.matches.value_source can break clap_builder.parser.arg_matcher, while a change to clap_builder.parser.arg_matcher can't break clap_builder.parser.matches.value_source.
- Position
- Below the diagonal: clap_builder.parser.arg_matcher uses a module listed above it, which is the healthy direction.
37→3 clap_builder.parser.arg_matcher uses clap_builder.util.any_value✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.arg_matcher uses a type in clap_builder.util.any_value.
- The types involved
clap_builder.parser.arg_matcher.ArgMatcher→clap_builder.util.any_value.AnyValue
- Direction
- clap_builder.parser.arg_matcher uses clap_builder.util.any_value, so a change to clap_builder.util.any_value can break clap_builder.parser.arg_matcher, while a change to clap_builder.parser.arg_matcher can't break clap_builder.util.any_value.
- Position
- Below the diagonal: clap_builder.parser.arg_matcher uses a module listed above it, which is the healthy direction.
37→4 clap_builder.parser.arg_matcher uses clap_builder.util.flat_map✕
- Connections
- 3 pairs of types, where a type in clap_builder.parser.arg_matcher uses a type in clap_builder.util.flat_map.
- The types involved
clap_builder.parser.arg_matcher.ArgMatcher→clap_builder.util.flat_map.Entryclap_builder.parser.arg_matcher.ArgMatcher→clap_builder.util.flat_map.FlatMapclap_builder.parser.arg_matcher.ArgMatcher→clap_builder.util.flat_map.Iter
- Direction
- clap_builder.parser.arg_matcher uses clap_builder.util.flat_map, so a change to clap_builder.util.flat_map can break clap_builder.parser.arg_matcher, while a change to clap_builder.parser.arg_matcher can't break clap_builder.util.flat_map.
- Position
- Below the diagonal: clap_builder.parser.arg_matcher uses a module listed above it, which is the healthy direction.
37→9 clap_builder.parser.arg_matcher uses clap_builder.parser.matches.matched_arg✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.arg_matcher uses a type in clap_builder.parser.matches.matched_arg.
- The types involved
clap_builder.parser.arg_matcher.ArgMatcher→clap_builder.parser.matches.matched_arg.MatchedArg
- Direction
- clap_builder.parser.arg_matcher uses clap_builder.parser.matches.matched_arg, so a change to clap_builder.parser.matches.matched_arg can break clap_builder.parser.arg_matcher, while a change to clap_builder.parser.arg_matcher can't break clap_builder.parser.matches.matched_arg.
- Position
- Below the diagonal: clap_builder.parser.arg_matcher uses a module listed above it, which is the healthy direction.
37→10 clap_builder.parser.arg_matcher uses clap_builder.util.id✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.arg_matcher uses a type in clap_builder.util.id.
- The types involved
clap_builder.parser.arg_matcher.ArgMatcher→clap_builder.util.id.Id
- Direction
- clap_builder.parser.arg_matcher uses clap_builder.util.id, so a change to clap_builder.util.id can break clap_builder.parser.arg_matcher, while a change to clap_builder.parser.arg_matcher can't break clap_builder.util.id.
- Position
- Below the diagonal: clap_builder.parser.arg_matcher uses a module listed above it, which is the healthy direction.
37→16 clap_builder.parser.arg_matcher uses clap_builder.parser.matches.arg_matches✕
- Connections
- 2 pairs of types, where a type in clap_builder.parser.arg_matcher uses a type in clap_builder.parser.matches.arg_matches.
- The types involved
clap_builder.parser.arg_matcher.ArgMatcher→clap_builder.parser.matches.arg_matches.ArgMatchesclap_builder.parser.arg_matcher.ArgMatcher→clap_builder.parser.matches.arg_matches.SubCommand
- Direction
- clap_builder.parser.arg_matcher uses clap_builder.parser.matches.arg_matches, so a change to clap_builder.parser.matches.arg_matches can break clap_builder.parser.arg_matcher, while a change to clap_builder.parser.arg_matcher can't break clap_builder.parser.matches.arg_matches.
- Position
- Below the diagonal: clap_builder.parser.arg_matcher uses a module listed above it, which is the healthy direction.
37→22 clap_builder.parser.arg_matcher uses clap_builder.builder.command✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.arg_matcher uses a type in clap_builder.builder.command.
- The types involved
clap_builder.parser.arg_matcher.ArgMatcher→clap_builder.builder.command.Command
- Direction
- clap_builder.parser.arg_matcher uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_builder.parser.arg_matcher, while a change to clap_builder.parser.arg_matcher can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_builder.parser.arg_matcher uses a module listed above it, which is the healthy direction.
37→25 clap_builder.parser.arg_matcher uses clap_builder.builder.arg✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.arg_matcher uses a type in clap_builder.builder.arg.
- The types involved
clap_builder.parser.arg_matcher.ArgMatcher→clap_builder.builder.arg.Arg
- Direction
- clap_builder.parser.arg_matcher uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_builder.parser.arg_matcher, while a change to clap_builder.parser.arg_matcher can't break clap_builder.builder.arg.
- Position
- Below the diagonal: clap_builder.parser.arg_matcher uses a module listed above it, which is the healthy direction.
37→29 clap_builder.parser.arg_matcher uses clap_builder.parser.parser✕
- Connections
- 2 pairs of types, where a type in clap_builder.parser.arg_matcher uses a type in clap_builder.parser.parser.
- The types involved
clap_builder.parser.arg_matcher.ArgMatcher→clap_builder.parser.parser.Identifierclap_builder.parser.arg_matcher.ArgMatcher→clap_builder.parser.parser.PendingArg
- Direction
- clap_builder.parser.arg_matcher uses clap_builder.parser.parser, so a change to clap_builder.parser.parser can break clap_builder.parser.arg_matcher, while a change to clap_builder.parser.arg_matcher can't break clap_builder.parser.parser.
- Position
- Below the diagonal: clap_builder.parser.arg_matcher uses a module listed above it, which is the healthy direction.
38→1 clap_builder.output.usage uses clap_builder.builder.styled_str✕
- Connections
- 1 pair of types, where a type in clap_builder.output.usage uses a type in clap_builder.builder.styled_str.
- The types involved
clap_builder.output.usage.Usage→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_builder.output.usage uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_builder.output.usage, while a change to clap_builder.output.usage can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_builder.output.usage uses a module listed above it, which is the healthy direction.
38→22 clap_builder.output.usage uses clap_builder.builder.command✕
- Connections
- 1 pair of types, where a type in clap_builder.output.usage uses a type in clap_builder.builder.command.
- The types involved
clap_builder.output.usage.Usage→clap_builder.builder.command.Command
- Direction
- clap_builder.output.usage uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_builder.output.usage, while a change to clap_builder.output.usage can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_builder.output.usage uses a module listed above it, which is the healthy direction.
38→23 clap_builder.output.usage uses clap_builder.builder.styling✕
- Connections
- 1 pair of types, where a type in clap_builder.output.usage uses a type in clap_builder.builder.styling.
- The types involved
clap_builder.output.usage.Usage→clap_builder.builder.styling.Styles
- Direction
- clap_builder.output.usage uses clap_builder.builder.styling, so a change to clap_builder.builder.styling can break clap_builder.output.usage, while a change to clap_builder.output.usage can't break clap_builder.builder.styling.
- Position
- Below the diagonal: clap_builder.output.usage uses a module listed above it, which is the healthy direction.
38→37 clap_builder.output.usage uses clap_builder.parser.arg_matcher✕
- Connections
- 1 pair of types, where a type in clap_builder.output.usage uses a type in clap_builder.parser.arg_matcher.
- The types involved
clap_builder.output.usage.Usage→clap_builder.parser.arg_matcher.ArgMatcher
- Direction
- clap_builder.output.usage uses clap_builder.parser.arg_matcher, so a change to clap_builder.parser.arg_matcher can break clap_builder.output.usage, while a change to clap_builder.output.usage can't break clap_builder.parser.arg_matcher.
- Position
- Below the diagonal: clap_builder.output.usage uses a module listed above it, which is the healthy direction.
39→1 clap_builder.parser.validator uses clap_builder.builder.styled_str✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.validator uses a type in clap_builder.builder.styled_str.
- The types involved
clap_builder.parser.validator.Validator→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_builder.parser.validator uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_builder.parser.validator, while a change to clap_builder.parser.validator can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_builder.parser.validator uses a module listed above it, which is the healthy direction.
39→4 clap_builder.parser.validator uses clap_builder.util.flat_map✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.validator uses a type in clap_builder.util.flat_map.
- The types involved
clap_builder.parser.validator.Conflicts→clap_builder.util.flat_map.FlatMap
- Direction
- clap_builder.parser.validator uses clap_builder.util.flat_map, so a change to clap_builder.util.flat_map can break clap_builder.parser.validator, while a change to clap_builder.parser.validator can't break clap_builder.util.flat_map.
- Position
- Below the diagonal: clap_builder.parser.validator uses a module listed above it, which is the healthy direction.
39→10 clap_builder.parser.validator uses clap_builder.util.id✕
- Connections
- 3 pairs of types, where a type in clap_builder.parser.validator uses a type in clap_builder.util.id.
- The types involved
clap_builder.parser.validator.Conflicts→clap_builder.util.id.Idclap_builder.parser.validator.Validator→clap_builder.util.id.Idclap_builder.parser.validator.validator$module→clap_builder.util.id.Id
- Direction
- clap_builder.parser.validator uses clap_builder.util.id, so a change to clap_builder.util.id can break clap_builder.parser.validator, while a change to clap_builder.parser.validator can't break clap_builder.util.id.
- Position
- Below the diagonal: clap_builder.parser.validator uses a module listed above it, which is the healthy direction.
39→12 clap_builder.parser.validator uses clap_builder.builder.arg_group✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.validator uses a type in clap_builder.builder.arg_group.
- The types involved
clap_builder.parser.validator.validator$module→clap_builder.builder.arg_group.ArgGroup
- Direction
- clap_builder.parser.validator uses clap_builder.builder.arg_group, so a change to clap_builder.builder.arg_group can break clap_builder.parser.validator, while a change to clap_builder.parser.validator can't break clap_builder.builder.arg_group.
- Position
- Below the diagonal: clap_builder.parser.validator uses a module listed above it, which is the healthy direction.
39→15 clap_builder.parser.validator uses clap_builder.builder.possible_value✕
- Connections
- 1 pair of types, where a type in clap_builder.parser.validator uses a type in clap_builder.builder.possible_value.
- The types involved
clap_builder.parser.validator.validator$module→clap_builder.builder.possible_value.PossibleValue
- Direction
- clap_builder.parser.validator uses clap_builder.builder.possible_value, so a change to clap_builder.builder.possible_value can break clap_builder.parser.validator, while a change to clap_builder.parser.validator can't break clap_builder.builder.possible_value.
- Position
- Below the diagonal: clap_builder.parser.validator uses a module listed above it, which is the healthy direction.
39→22 clap_builder.parser.validator uses clap_builder.builder.command✕
- Connections
- 3 pairs of types, where a type in clap_builder.parser.validator uses a type in clap_builder.builder.command.
- The types involved
clap_builder.parser.validator.Conflicts→clap_builder.builder.command.Commandclap_builder.parser.validator.Validator→clap_builder.builder.command.Commandclap_builder.parser.validator.validator$module→clap_builder.builder.command.Command
- Direction
- clap_builder.parser.validator uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_builder.parser.validator, while a change to clap_builder.parser.validator can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_builder.parser.validator uses a module listed above it, which is the healthy direction.
39→25 clap_builder.parser.validator uses clap_builder.builder.arg✕
- Connections
- 2 pairs of types, where a type in clap_builder.parser.validator uses a type in clap_builder.builder.arg.
- The types involved
clap_builder.parser.validator.Validator→clap_builder.builder.arg.Argclap_builder.parser.validator.validator$module→clap_builder.builder.arg.Arg
- Direction
- clap_builder.parser.validator uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_builder.parser.validator, while a change to clap_builder.parser.validator can't break clap_builder.builder.arg.
- Position
- Below the diagonal: clap_builder.parser.validator uses a module listed above it, which is the healthy direction.
39→37 clap_builder.parser.validator uses clap_builder.parser.arg_matcher✕
- Connections
- 2 pairs of types, where a type in clap_builder.parser.validator uses a type in clap_builder.parser.arg_matcher.
- The types involved
clap_builder.parser.validator.Conflicts→clap_builder.parser.arg_matcher.ArgMatcherclap_builder.parser.validator.Validator→clap_builder.parser.arg_matcher.ArgMatcher
- Direction
- clap_builder.parser.validator uses clap_builder.parser.arg_matcher, so a change to clap_builder.parser.arg_matcher can break clap_builder.parser.validator, while a change to clap_builder.parser.validator can't break clap_builder.parser.arg_matcher.
- Position
- Below the diagonal: clap_builder.parser.validator uses a module listed above it, which is the healthy direction.
40→1 clap_builder.output.help_template uses clap_builder.builder.styled_str✕
- Connections
- 2 pairs of types, where a type in clap_builder.output.help_template uses a type in clap_builder.builder.styled_str.
- The types involved
clap_builder.output.help_template.AutoHelp→clap_builder.builder.styled_str.StyledStrclap_builder.output.help_template.HelpTemplate→clap_builder.builder.styled_str.StyledStr
- Direction
- clap_builder.output.help_template uses clap_builder.builder.styled_str, so a change to clap_builder.builder.styled_str can break clap_builder.output.help_template, while a change to clap_builder.output.help_template can't break clap_builder.builder.styled_str.
- Position
- Below the diagonal: clap_builder.output.help_template uses a module listed above it, which is the healthy direction.
40→22 clap_builder.output.help_template uses clap_builder.builder.command✕
- Connections
- 3 pairs of types, where a type in clap_builder.output.help_template uses a type in clap_builder.builder.command.
- The types involved
clap_builder.output.help_template.AutoHelp→clap_builder.builder.command.Commandclap_builder.output.help_template.HelpTemplate→clap_builder.builder.command.Commandclap_builder.output.help_template.help_template$module→clap_builder.builder.command.Command
- Direction
- clap_builder.output.help_template uses clap_builder.builder.command, so a change to clap_builder.builder.command can break clap_builder.output.help_template, while a change to clap_builder.output.help_template can't break clap_builder.builder.command.
- Position
- Below the diagonal: clap_builder.output.help_template uses a module listed above it, which is the healthy direction.
40→23 clap_builder.output.help_template uses clap_builder.builder.styling✕
- Connections
- 1 pair of types, where a type in clap_builder.output.help_template uses a type in clap_builder.builder.styling.
- The types involved
clap_builder.output.help_template.HelpTemplate→clap_builder.builder.styling.Styles
- Direction
- clap_builder.output.help_template uses clap_builder.builder.styling, so a change to clap_builder.builder.styling can break clap_builder.output.help_template, while a change to clap_builder.output.help_template can't break clap_builder.builder.styling.
- Position
- Below the diagonal: clap_builder.output.help_template uses a module listed above it, which is the healthy direction.
40→25 clap_builder.output.help_template uses clap_builder.builder.arg✕
- Connections
- 2 pairs of types, where a type in clap_builder.output.help_template uses a type in clap_builder.builder.arg.
- The types involved
clap_builder.output.help_template.HelpTemplate→clap_builder.builder.arg.Argclap_builder.output.help_template.help_template$module→clap_builder.builder.arg.Arg
- Direction
- clap_builder.output.help_template uses clap_builder.builder.arg, so a change to clap_builder.builder.arg can break clap_builder.output.help_template, while a change to clap_builder.output.help_template can't break clap_builder.builder.arg.
- Position
- Below the diagonal: clap_builder.output.help_template uses a module listed above it, which is the healthy direction.
40→38 clap_builder.output.help_template uses clap_builder.output.usage✕
- Connections
- 2 pairs of types, where a type in clap_builder.output.help_template uses a type in clap_builder.output.usage.
- The types involved
clap_builder.output.help_template.AutoHelp→clap_builder.output.usage.Usageclap_builder.output.help_template.HelpTemplate→clap_builder.output.usage.Usage
- Direction
- clap_builder.output.help_template uses clap_builder.output.usage, so a change to clap_builder.output.usage can break clap_builder.output.help_template, while a change to clap_builder.output.help_template can't break clap_builder.output.usage.
- Position
- Below the diagonal: clap_builder.output.help_template 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 | 34 | High / Critical |
| A05:2025 — Injection | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with stdio-fixture.rs; 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; Expand the README with getting-started, architecture overview and a project map.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with stdio-fixture.rs. | +10.8 pts | Low | ADR Quality |
| 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. | +10.1 pts | Medium | Architecture documentation |
| Expand the README with getting-started, architecture overview and a project map. | +4.8 pts | Medium | Documentation (README) |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.9 pts | Low | Bus Factor |
| Enable Dependabot/Renovate or a dependency-review gate. | +1.7 pts | Medium | Security & performance tooling |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +1.4 pts | Medium | Observability |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +0.5 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| clap_builder/src/parser/parser.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| clap_derive/src/utils/doc_comments.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| clap_builder/src/builder/debug_asserts.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| clap_complete/src/aot/shells/fish.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| clap_builder/src/builder/command.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| clap_complete/src/engine/complete.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| clap_builder/src/builder/arg.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| clap_derive/src/derives/args.rs | 6.7 | Mixed | Explicit Debt: HackComment |
| clap_builder/src/derive.rs | 7.0 | Mixed | Code Duplication: Edited copy of a member (13 corresponding lines) |
| clap_builder/src/builder/os_str.rs | 7.0 | Mixed | Code Duplication: Duplicated block (6 lines × 3) |
| clap_builder/src/output/usage.rs | 7.0 | Mixed | Cyclomatic Complexity: Usage::write_args (cyclomatic 25) |
| clap_builder/src/error/mod.rs | 7.0 | Mixed | God Classes: TooManyMethods: Error |
| clap_builder/src/error/format.rs | 7.0 | Mixed | Cyclomatic Complexity: clap_builder::error::format::write_dynamic_context (cyclomatic 33) |
| clap_complete/src/aot/shells/elvish.rs | 7.1 | Mixed | Cyclomatic Complexity: clap_complete::aot::shells::elvish::generate_inner (cyclomatic 17) |
| clap_builder/src/builder/value_parser.rs | 7.1 | Mixed | God Classes: FileTooLong: builder/value_parser.rs |
| clap_complete/src/env/shells.rs | 7.1 | Mixed | Code Duplication: Edited copy of a member (16 corresponding lines) |
| clap_mangen/src/render.rs | 7.2 | Mixed | Cyclomatic Complexity: clap_mangen::render::options (cyclomatic 19) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| clap_complete_nushell/tests/common.rs | 7.3 | Mixed | Explicit Debt: HackComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 41 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 41 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 217 of 234 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
- D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each 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.
- D19 Documentation Quality — 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- 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.
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
15 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Parser::parse at 61. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ClapAttr::parse at 30 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: clap_derive/src/attr.rs (ClapAttr::parse at 30), clap_complete_nushell/src/lib.rs (clap_complete_nushell::append_value_completion_and_help at 18), clap_builder/src/error/context.rs (ContextKind::as_str at 17), clap_builder/src/error/kind.rs (ErrorKind::as_str at 17), clap_complete/src/aot/shells/zsh.rs (clap_complete::aot::shells::zsh::value_completion at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 15 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Parser::parse (cyclomatic 61), Parser::react (cyclomatic 45), clap_derive::utils::doc_comments::markdown::parse_markdown (cyclomatic 38). — 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 15 together lifts Cyclomatic Complexity from 7.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
36 method(s) exceeded the cognitive complexity threshold of 15; the worst was Parser::parse at 119.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with Parser::parse (cognitive 119), clap_builder::builder::debug_asserts::assert_app (cognitive 67). — 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 2 together lifts Cognitive Complexity from 5.7 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
23 god class(es) detected.
What to do
- Resolve the 8 FileTooLong finding(s) in God Classes — start with command.rs, value_parser.rs, parser.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with command.rs, arg.rs, mod.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 ClassTooLong finding(s) in God Classes — start with command.rs, parser.rs, arg.rs. — One of this dimension's main actionable groups (4 warning-level).
D4 · Code Duplication
43 duplicated block group(s) detected. 4.6 % of the production lines (1,763 of 38,706) are in a reported copy. A further 22 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 5 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with arg.rs (2), format.rs, parser.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with format.rs (2), arg.rs (2). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with arg.rs (3), mod.rs. — One of this dimension's main actionable groups (4 warning-level).
D5 · Coupling
8 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 6 of the 8 (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).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
2 of 43 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with command.rs, styling.rs. — One of this dimension's main actionable groups (2 warning-level).
D8 · Code Coverage
Line coverage 70.2% — 22 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 74 production file(s), 24 test binaries and 1 doc-test binaries).
What to do
- Resolve the 22 Low coverage finding(s) in Code Coverage — start with os_str.rs, str.rs, value_hint.rs. — One of this dimension's main actionable groups (22 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 155 test files): measured (0 flaky).
D12 · Dependency Hygiene
6 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 421 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
8 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is clap_builder/src/builder/arg_group.rs. Counted over 64 of the 111 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
19 deducted task-comment markers across 38706 LoC (0.0/KLoC) → score 9.9. 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 14 HackComment finding(s) in Explicit Debt — start with common.rs (4), complete.rs (2), arg.rs (2). — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with doc_comments.rs, complete.rs, debug_asserts.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with command.rs (2). — One of this dimension's main actionable groups (2 warning-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with stdio-fixture.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 8 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
29 finding(s): 1 critical, 2 high, 24 medium, 2 low.
What to do
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 64 of the 111 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: _tutorial.rs↔_tutorial.rs 67%; arg.rs↔kind.rs 52%; command.rs↔_features.rs 50%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with _tutorial.rs, arg.rs, command.rs. — One of this dimension's main actionable groups (3 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
- The root README is 91 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF1 · Benchmark discipline
X21 · Side-effecting pattern guard
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 85% | Strong | Solid. |
| Architecture | 98% | Exemplary | Strongest area. |
| Maturity | 56% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 73% | Strong | Solid. |
| Security | 77% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 73 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — 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 — ~37278 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.
- 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.
- D19 Documentation Quality — D19 reads .NET projects and npm packages as units; 8 folder(s) declared by Cargo.toml were not judged for an overview, an example or the map.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (3561 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (27 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 74 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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: 116 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
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 4 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 211 finding(s)
- Low coverage: clap_builder/src/builder/os_str.rs clap_builder/src/builder/os_str.rs:1
- Low coverage: clap_builder/src/builder/str.rs clap_builder/src/builder/str.rs:1
- Low coverage: clap_builder/src/builder/value_hint.rs clap_builder/src/builder/value_hint.rs:1
- Low coverage: clap_builder/src/derive.rs clap_builder/src/derive.rs:1
- Low coverage: clap_builder/src/error/context.rs clap_builder/src/error/context.rs:1
- Low coverage: clap_builder/src/error/kind.rs clap_builder/src/error/kind.rs:1
- Low coverage: clap_builder/src/util/color.rs clap_builder/src/util/color.rs:1
- Low coverage: clap_complete/src/aot/generator/mod.rs clap_complete/src/aot/generator/mod.rs:1
- Low coverage: clap_complete/src/aot/shells/shell.rs clap_complete/src/aot/shells/shell.rs:1
- Low coverage: clap_derive/src/attr.rs clap_derive/src/attr.rs:1
- Low coverage: clap_derive/src/derives/args.rs clap_derive/src/derives/args.rs:1
- Low coverage: clap_derive/src/derives/into_app.rs clap_derive/src/derives/into_app.rs:1
- Low coverage: clap_derive/src/derives/parser.rs clap_derive/src/derives/parser.rs:1
- Low coverage: clap_derive/src/derives/subcommand.rs clap_derive/src/derives/subcommand.rs:1
- Low coverage: clap_derive/src/derives/value_enum.rs clap_derive/src/derives/value_enum.rs:1
- Low coverage: clap_derive/src/dummies.rs clap_derive/src/dummies.rs:1
- Low coverage: clap_derive/src/item.rs clap_derive/src/item.rs:1
- Low coverage: clap_derive/src/lib.rs clap_derive/src/lib.rs:1
- Low coverage: clap_derive/src/utils/doc_comments.rs clap_derive/src/utils/doc_comments.rs:1
- Low coverage: clap_derive/src/utils/error.rs clap_derive/src/utils/error.rs:1
- Low coverage: clap_derive/src/utils/spanned.rs clap_derive/src/utils/spanned.rs:1
- Low coverage: clap_derive/src/utils/ty.rs clap_derive/src/utils/ty.rs:1
- HackComment clap_derive/src/derives/args.rs:409
- HackComment clap_complete_nushell/tests/common.rs:447
- HackComment clap_complete/tests/testsuite/common.rs:462
- HackComment clap_complete_nushell/tests/common.rs:490
- HackComment clap_complete/tests/testsuite/common.rs:505
- HackComment clap_complete/tests/testsuite/engine.rs:1545
- HackComment clap_complete/src/engine/complete.rs:268
- HackComment clap_complete/src/engine/complete.rs:283
- HackComment clap_complete/src/aot/shells/fish.rs:119
- HackComment clap_builder/src/parser/parser.rs:738
- HackComment clap_builder/src/output/help_template.rs:1
- HackComment clap_builder/src/builder/arg.rs:1393
- HackComment clap_builder/src/builder/arg.rs:4373
- HackComment clap_builder/src/builder/debug_asserts.rs:764
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- clap_complete::aot::shells::fish::gen_fish_inner (cognitive 48) clap_complete/src/aot/shells/fish.rs:72
- clap_complete::engine::complete::complete (cognitive 44) clap_complete/src/engine/complete.rs:15
- clap_complete::engine::complete::complete_option (cognitive 37) clap_complete/src/engine/complete.rs:246
- clap_complete::aot::shells::elvish::generate_inner (cognitive 31) clap_complete/src/aot/shells/elvish.rs:71
- clap_complete::aot::shells::zsh::write_flags_of (cognitive 22) clap_complete/src/aot/shells/zsh.rs:546
- clap_complete::engine::custom::complete_path (cognitive 22) clap_complete/src/engine/custom.rs:327
- clap_complete::aot::shells::bash::option_details_for_path (cognitive 21) clap_complete/src/aot/shells/bash.rs:172
- clap_complete::aot::shells::zsh::write_opts_of (cognitive 20) clap_complete/src/aot/shells/zsh.rs:457
- clap_complete::engine::complete::complete_arg (cognitive 19) clap_complete/src/engine/complete.rs:137
- clap_complete::engine::complete::parse_positional (cognitive 18) clap_complete/src/engine/complete.rs:658
- FileTooLong: builder/command.rs clap_builder/src/builder/command.rs
- FileTooLong: builder/value_parser.rs clap_builder/src/builder/value_parser.rs
- FileTooLong: parser/parser.rs clap_builder/src/parser/parser.rs
- FileTooLong: builder/arg.rs clap_builder/src/builder/arg.rs
- FileTooLong: matches/arg_matches.rs clap_builder/src/parser/matches/arg_matches.rs
- FileTooLong: error/mod.rs clap_builder/src/error/mod.rs
- FileTooLong: builder/debug_asserts.rs clap_builder/src/builder/debug_asserts.rs
- FileTooLong: engine/complete.rs clap_complete/src/engine/complete.rs
- Parser::parse (cognitive 119) clap_builder/src/parser/parser.rs:77
- Parser::react (cognitive 56) clap_builder/src/parser/parser.rs:1141
- Parser::add_default_value (cognitive 31) clap_builder/src/parser/parser.rs:1455
- Parser::parse_short_arg (cognitive 27) clap_builder/src/parser/parser.rs:882
- Parser::parse_long_arg (cognitive 21) clap_builder/src/parser/parser.rs:763
- Parser::possible_subcommand (cognitive 16) clap_builder/src/parser/parser.rs:584
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (7 lines × 2) clap_builder/src/error/format.rs:46
- Duplicated block (7 lines × 2) clap_builder/src/parser/parser.rs:1201
- Duplicated block (7 lines × 2) clap_complete/src/env/shells.rs:257
- Duplicated block (7 lines × 2) clap_builder/src/builder/arg.rs:346
- Duplicated block (7 lines × 2) clap_builder/src/builder/arg.rs:461
- clap_builder::builder::debug_asserts::assert_app (cyclomatic 37) clap_builder/src/builder/debug_asserts.rs:11
- clap_builder::error::format::write_dynamic_context (cyclomatic 33) clap_builder/src/error/format.rs:140
- clap_builder::builder::debug_asserts::_verify_positionals (cyclomatic 26) clap_builder/src/builder/debug_asserts.rs:508
- clap_builder::builder::debug_asserts::assert_arg_flags (cyclomatic 25) clap_builder/src/builder/debug_asserts.rs:804
- clap_builder::builder::debug_asserts::assert_app (cognitive 67) clap_builder/src/builder/debug_asserts.rs:11
- clap_builder::error::format::write_dynamic_context (cognitive 58) clap_builder/src/error/format.rs:140
- clap_builder::builder::debug_asserts::_verify_positionals (cognitive 41) clap_builder/src/builder/debug_asserts.rs:508
- clap_builder::builder::debug_asserts::assert_arg_flags (cognitive 40) clap_builder/src/builder/debug_asserts.rs:804
- Command::_build_self (cognitive 44) clap_builder/src/builder/command.rs:4397
- Command::_build_bin_names_internal (cognitive 42) clap_builder/src/builder/command.rs:4580
- Command::try_get_matches_from_mut (cognitive 21) clap_builder/src/builder/command.rs:861
- Command::unroll_arg_requires (cognitive 17) clap_builder/src/builder/command.rs:5087
- TooManyMethods: Command clap_builder/src/builder/command.rs:74
- TooManyMethods: Arg clap_builder/src/builder/arg.rs:60
- TooManyMethods: Error clap_builder/src/error/mod.rs:60
- TooManyMethods: ArgMatches clap_builder/src/parser/matches/arg_matches.rs:67
- ClassTooLong: Command clap_builder/src/builder/command.rs:74
- ClassTooLong: Parser clap_builder/src/parser/parser.rs:23
- ClassTooLong: Arg clap_builder/src/builder/arg.rs:60
- ClassTooLong: Error clap_builder/src/error/mod.rs:60
- FunctionTooLong: clap_builder::builder::debug_asserts::assert_app clap_builder/src/builder/debug_asserts.rs:11
- FunctionTooLong: clap_builder::error::format::write_dynamic_context clap_builder/src/error/format.rs:140
- FunctionTooLong: clap_derive::utils::doc_comments::markdown::parse_markdown clap_derive/src/utils/doc_comments.rs:232
- FunctionTooLong: clap_builder::builder::debug_asserts::_verify_positionals clap_builder/src/builder/debug_asserts.rs:508
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) clap_builder/src/error/format.rs:277
- Duplicated block (9 lines × 2) clap_builder/src/error/format.rs:297
- Duplicated block (9 lines × 2) clap_builder/src/builder/arg.rs:284
- Duplicated block (9 lines × 2) clap_builder/src/builder/arg.rs:404
- Duplicated block (8 lines × 2) clap_builder/src/error/mod.rs:724
- Duplicated block (8 lines × 2) clap_builder/src/builder/arg.rs:254
- Duplicated block (8 lines × 2) clap_builder/src/builder/arg.rs:375
- Duplicated block (8 lines × 2) clap_builder/src/builder/arg.rs:4007
- clap_complete::aot::shells::fish::gen_fish_inner (cyclomatic 26) clap_complete/src/aot/shells/fish.rs:72
- clap_complete::engine::complete::complete (cyclomatic 21) clap_complete/src/engine/complete.rs:15
- clap_complete::aot::shells::elvish::generate_inner (cyclomatic 17) clap_complete/src/aot/shells/elvish.rs:71
- TodoComment clap_derive/src/utils/doc_comments.rs:210
- TodoComment clap_complete/src/engine/complete.rs:35
- TodoComment clap_builder/src/builder/debug_asserts.rs:698
- Usage::write_args (cognitive 52) clap_builder/src/output/usage.rs:254
- Usage::get_required_usage_from (cognitive 43) clap_builder/src/output/usage.rs:378
- Usage::needs_options_tag (cognitive 16) clap_builder/src/output/usage.rs:204
- Change coupling: _tutorial.rs ↔ _tutorial.rs src/_derive/_tutorial.rs:1
- Change coupling: arg.rs ↔ kind.rs clap_builder/src/builder/arg.rs:1
- Change coupling: command.rs ↔ _features.rs clap_builder/src/builder/command.rs:1
- Edited copy of a member (13 corresponding lines) clap_complete/src/engine/complete.rs:555
- Edited copy of a member (13 corresponding lines) clap_builder/src/builder/action.rs:375
- Edited copy of a member (13 corresponding lines) clap_builder/src/derive.rs:31
- Duplicated block (17 lines × 2) clap_builder/src/builder/command.rs:4551
- Duplicated block (17 lines × 2) clap_complete/src/aot/shells/fish.rs:131
- Duplicated block (17 lines × 2) clap_complete/src/aot/shells/elvish.rs:132
- Duplicated block (5 lines × 2) clap_builder/src/builder/arg.rs:317
- Duplicated block (5 lines × 2) clap_builder/src/builder/arg.rs:435
- Duplicated block (5 lines × 2) clap_complete/src/env/shells.rs:180
- Parser::parse (cyclomatic 61) clap_builder/src/parser/parser.rs:77
- Parser::react (cyclomatic 45) clap_builder/src/parser/parser.rs:1141
- Usage::write_args (cyclomatic 25) clap_builder/src/output/usage.rs:254
- Usage::get_required_usage_from (cyclomatic 18) clap_builder/src/output/usage.rs:378
- FixmeComment clap_builder/src/builder/command.rs:4036
- FixmeComment clap_builder/src/builder/command.rs:4070
- clap_mangen::render::options (cognitive 39) clap_mangen/src/render.rs:221
- clap_mangen::render::synopsis (cognitive 17) clap_mangen/src/render.rs:32
- Arg::_build (cognitive 26) clap_builder/src/builder/arg.rs:4578
- Arg::render_arg_val (cognitive 17) clap_builder/src/builder/arg.rs:4707
- MethodTooLong: Parser.parse clap_builder/src/parser/parser.rs:77
- MethodTooLong: Parser.react clap_builder/src/parser/parser.rs:1141
- Edited copy of a member (10 corresponding lines) clap_builder/src/util/flat_map.rs:156
- Edited copy of a member (10 corresponding lines) clap_builder/src/builder/arg.rs:4320
- Duplicated block (16 lines × 2) clap_complete/src/aot/shells/elvish.rs:87
- Duplicated block (16 lines × 2) clap_complete/src/env/shells.rs:231
- Duplicated block (11 lines × 2) clap_builder/src/builder/value_parser.rs:1382
- Duplicated block (11 lines × 2) clap_builder/src/error/mod.rs:498
- Duplicated block (10 lines × 2) clap_builder/src/parser/validator.rs:169
- Duplicated block (10 lines × 2) clap_complete/src/engine/complete.rs:257
- Low cohesion: Command (LCOM4 12) clap_builder/src/builder/command.rs:74
- Low cohesion: Styles (LCOM4 8) clap_builder/src/builder/styling.rs:23
- clap_derive::utils::doc_comments::markdown::parse_markdown (cyclomatic 38) clap_derive/src/utils/doc_comments.rs:232
- Command::_build_self (cyclomatic 24) clap_builder/src/builder/command.rs:4397
- Validator::validate_required (cyclomatic 23) clap_builder/src/parser/validator.rs:221
- clap_mangen::render::options (cyclomatic 19) clap_mangen/src/render.rs:221
- Validator::validate_required (cognitive 41) clap_builder/src/parser/validator.rs:221
- clap_complete_nushell::append_argument (cognitive 26) clap_complete_nushell/src/lib.rs:134
- clap_derive::utils::doc_comments::markdown::parse_markdown (cognitive 21) clap_derive/src/utils/doc_comments.rs:232
- RichFormatter::format_error (cognitive 20) clap_builder/src/error/format.rs:67
- LineWrapper::wrap (cognitive 18) clap_builder/src/output/textwrap/wrap_algorithms.rs:24
- TooManyFields: Command clap_builder/src/builder/command.rs:74
- Near-duplicate member pair (44 shared lines) clap_builder/src/builder/command.rs:4495
- Near-duplicate member pair (39 shared lines) clap_builder/src/output/usage.rs:254
- Edited copy of a member (45 corresponding lines) clap_builder/src/builder/value_parser.rs:1411
- Edited copy of a member (21 corresponding lines) clap_builder/src/builder/value_parser.rs:1377
- Edited copy of a member (22 corresponding lines) clap_complete/src/aot/generator/utils.rs:70
- Edited copy of a member (30 corresponding lines) clap_builder/src/error/mod.rs:491
- Edited copy of a member (16 corresponding lines) clap_complete/src/env/shells.rs:256
- Edited copy of a member (14 corresponding lines) clap_complete/src/engine/complete.rs:503
- Edited copy of a member (11 corresponding lines) clap_builder/src/builder/command.rs:934
- Edited copies of one member (3 members, 20+ corresponding lines) clap_complete/src/env/shells.rs:24
- Edited copies of one member (3 members, 13+ corresponding lines) clap_builder/src/builder/action.rs:403
- Edited copies of one member (7 members, 15+ corresponding lines) clap_builder/src/error/mod.rs:438
- Edited copies of one member (5 members, 13+ corresponding lines) clap_builder/src/parser/matches/arg_matches.rs:1102
- Edited copy of a member (9 corresponding lines) clap_builder/src/builder/command.rs:1051
- Edited copy of a member (5 corresponding lines) clap_complete/src/engine/complete.rs:448
- Edited copy of a member (7 corresponding lines) clap_complete/src/aot/generator/utils.rs:134
- Edited copy of a member (34 corresponding lines) clap_complete/src/aot/shells/elvish.rs:23
- Duplicated block (45 lines × 2) clap_builder/src/builder/value_parser.rs:1331
- Duplicated block (37 lines × 2) clap_builder/src/builder/value_parser.rs:1419
- Duplicated block (28 lines × 2) clap_complete/src/aot/shells/bash.rs:190
- Duplicated block (21 lines × 2) clap_builder/src/error/mod.rs:384
- Duplicated block (15 lines × 2) clap_builder/src/builder/command.rs:4514
- Duplicated block (14–15 lines × 2) clap_builder/src/parser/parser.rs:174
- Duplicated block (12–14 lines × 2) clap_builder/src/output/usage.rs:259
- Duplicated block (12–13 lines × 2) clap_builder/src/builder/command.rs:4498
- Duplicated block (12 lines × 3) clap_builder/src/parser/parser.rs:1208
- Duplicated block (12 lines × 2) clap_complete/src/aot/shells/elvish.rs:72
- Duplicated block (9–11 lines × 2) clap_builder/src/parser/parser.rs:1216
- Duplicated block (7–9 lines × 2) clap_builder/src/output/usage.rs:301
- Duplicated block (4–7 lines × 3) clap_complete/src/env/shells.rs:94
- Duplicated block (6–7 lines × 2) clap_mangen/src/render.rs:86
- Duplicated block (62 lines × 2) clap_builder/src/builder/app_settings.rs:10
- Duplicated block (6 lines × 3) clap_builder/src/builder/os_str.rs:133
- Duplicated block (8 lines × 4) clap_builder/src/builder/arg.rs:2892
- Duplicated block (20 lines × 2) clap_builder/src/output/usage.rs:273
- Off the main sequence: clap_lex
- Coverage collected but not gated
Minor — 13 finding(s)
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- No ADRs found src/bin/stdio-fixture.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- Logging is not universal
Minor — 6 finding(s)
- Outdated: backtrace
- Outdated: is_executable
- Outdated: pulldown-cmark
- Outdated: syn
- Outdated: unicase
- Outdated: unicode-width
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-bbee50c5c80944cfb37706cdf7495439/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-bbee50c5c80944cfb37706cdf7495439/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 . | 1 | 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 . | 29 | 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 |