Executive summary
sharkdp/pastel falls short of our standard for a preview release because three files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 60 out of 100 and is rated Adequate, and 17 of its 20 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Maturity, at 53, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Having someone learn and document the three files no active contributor knows is another step, worth about 3 points. Raising Maturity to 62 would lift the score to about 64.
Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three parts of the code are no longer understood by anyone working on it, and two secrets can leak from the build pipeline. Having someone learn the forgotten files, pinning each tool to an exact version and limiting each secret to its own step would close these risks. Correcting the flagged pipeline settings would fix the two weaknesses in the build pipeline's configuration, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once.
The product code is 6,199 lines, about €6,900 to rebuild.
If Maturity rose from 53 to 62, the lowest score rated Strong, the score would rise from 60 to about 64.
New since the last survey: 30 findings
- Code Duplication · Edited copy of a member (16 corresponding lines) src/lib.rs
- Code Duplication · Edited copies of one member (4 members, 24+ corresponding lines) src/lib.rs
- Code Duplication · Edited copies of one member (4 members, 20+ corresponding lines) src/lib.rs
- Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) src/lib.rs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/lib.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/lib.rs
- Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) src/lib.rs
- Code Coverage · Low coverage: src/cli/colorpicker.rs src/cli/colorpicker.rs
- Code Coverage · Low coverage: src/cli/colorspace.rs src/cli/colorspace.rs
- Code Coverage · Low coverage: src/cli/commands/color_commands.rs src/cli/commands/color_commands.rs
- Code Coverage · Low coverage: src/cli/commands/colorcheck.rs src/cli/commands/colorcheck.rs
- Code Coverage · Low coverage: src/cli/commands/distinct.rs src/cli/commands/distinct.rs
- Code Coverage · Low coverage: src/cli/commands/format.rs src/cli/commands/format.rs
- Code Coverage · Low coverage: src/cli/commands/gradient.rs src/cli/commands/gradient.rs
- Code Coverage · Low coverage: src/cli/commands/gray.rs src/cli/commands/gray.rs
- Code Coverage · Low coverage: src/cli/commands/io.rs src/cli/commands/io.rs
- Code Coverage · Low coverage: src/cli/commands/list.rs src/cli/commands/list.rs
- Code Coverage · Low coverage: src/cli/commands/mod.rs src/cli/commands/mod.rs
- Code Coverage · Low coverage: src/cli/commands/paint.rs src/cli/commands/paint.rs
- Code Coverage · Low coverage: src/cli/commands/pick.rs src/cli/commands/pick.rs
- Code Coverage · Low coverage: src/cli/commands/random.rs src/cli/commands/random.rs
- Code Coverage · Low coverage: src/cli/commands/show.rs src/cli/commands/show.rs
- Code Coverage · Low coverage: src/cli/commands/sort.rs src/cli/commands/sort.rs
- Code Coverage · Low coverage: src/cli/error.rs src/cli/error.rs
- Code Coverage · Low coverage: src/cli/hdcanvas.rs src/cli/hdcanvas.rs
- Code Coverage · Low coverage: src/cli/main.rs src/cli/main.rs
- Code Coverage · Low coverage: src/cli/output.rs src/cli/output.rs
- Code Coverage · Low coverage: src/cli/utility.rs src/cli/utility.rs
- Code Coverage · Low coverage: src/random.rs src/random.rs
- Dependency Vulnerabilities · REDACTED
Rebuild cost: about €6,900 · Estimate
| Cost to rebuild | €2,300 to €12,000, for 38 to 121 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 60. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 6,199 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 cli.colorpicker_tools | 2 cli.colorspace | 3 helper | 4 types | 5 ansi | 6 colorspace | 7 pastel | 8 cli.config | 9 cli.error | 10 cli.colorpicker | 11 cli.commands | 12 cli.commands.io | 13 cli.hdcanvas | 14 cli.main | 15 cli.output | 16 delta_e | 17 distinct | 18 named | 19 parser | 20 random | 21 cli.cli | 22 cli.commands.traits | 23 cli.utility | 24 random.strategies | 25 cli.commands.color_commands | 26 cli.commands.colorcheck | 27 cli.commands.distinct | 28 cli.commands.format | 29 cli.commands.gradient | 30 cli.commands.gray | 31 cli.commands.list | 32 cli.commands.paint | 33 cli.commands.pick | 34 cli.commands.random | 35 cli.commands.show | 36 cli.commands.sort |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cli.colorpicker_tools | ||||||||||||||||||||||||||||||||||||
| 2 cli.colorspace | ||||||||||||||||||||||||||||||||||||
| 3 helper | ||||||||||||||||||||||||||||||||||||
| 4 types | ||||||||||||||||||||||||||||||||||||
| 5 ansi | 1 | |||||||||||||||||||||||||||||||||||
| 6 colorspace | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 7 pastel | 10 | 1 | 4 | 7 | ||||||||||||||||||||||||||||||||
| 8 cli.config | 1 | |||||||||||||||||||||||||||||||||||
| 9 cli.error | 1 | |||||||||||||||||||||||||||||||||||
| 10 cli.colorpicker | 1 | |||||||||||||||||||||||||||||||||||
| 11 cli.commands | 1 | |||||||||||||||||||||||||||||||||||
| 12 cli.commands.io | 1 | |||||||||||||||||||||||||||||||||||
| 13 cli.hdcanvas | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 14 cli.main | 1 | |||||||||||||||||||||||||||||||||||
| 15 cli.output | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 16 delta_e | 1 | |||||||||||||||||||||||||||||||||||
| 17 distinct | 5 | |||||||||||||||||||||||||||||||||||
| 18 named | 1 | |||||||||||||||||||||||||||||||||||
| 19 parser | 1 | |||||||||||||||||||||||||||||||||||
| 20 random | 1 | |||||||||||||||||||||||||||||||||||
| 21 cli.cli | 1 | |||||||||||||||||||||||||||||||||||
| 22 cli.commands.traits | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 23 cli.utility | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 24 random.strategies | 4 | 4 | ||||||||||||||||||||||||||||||||||
| 25 cli.commands.color_commands | 11 | 11 | 11 | 11 | ||||||||||||||||||||||||||||||||
| 26 cli.commands.colorcheck | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 27 cli.commands.distinct | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||
| 28 cli.commands.format | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 29 cli.commands.gradient | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 30 cli.commands.gray | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 31 cli.commands.list | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 32 cli.commands.paint | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 33 cli.commands.pick | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 34 cli.commands.random | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 35 cli.commands.show | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 36 cli.commands.sort | 1 | 1 | 1 | 1 |
5→7 ansi uses pastel part of a loop✕
- Connections
- 1 pair of types, where a type in ansi uses a type in pastel.
- The types involved
pastel.ansi.Style→pastel.Color
- Direction
- ansi uses pastel, so a change to pastel can break ansi, while a change to ansi can't break pastel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→3 colorspace uses helper✕
- Connections
- 1 pair of types, where a type in colorspace uses a type in helper.
- The types involved
pastel.colorspace.ColorSpace→pastel.helper.Fraction
- Direction
- colorspace uses helper, so a change to helper can break colorspace, while a change to colorspace can't break helper.
- Position
- Below the diagonal: colorspace uses a module listed above it, which is the healthy direction.
6→7 colorspace uses pastel part of a loop✕
- Connections
- 1 pair of types, where a type in colorspace uses a type in pastel.
- The types involved
pastel.colorspace.ColorSpace→pastel.Color
- Direction
- colorspace uses pastel, so a change to pastel can break colorspace, while a change to colorspace can't break pastel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→3 pastel uses helper✕
- Connections
- 10 pairs of types, where a type in pastel uses a type in helper.
- The types involved
pastel.Color→pastel.helper.Fractionpastel.ColorScale→pastel.helper.Fractionpastel.ColorStop→pastel.helper.Fractionpastel.HSLA→pastel.helper.Fractionpastel.HSVA→pastel.helper.Fractionpastel.LCh→pastel.helper.Fractionpastel.Lab→pastel.helper.Fractionpastel.OkLCh→pastel.helper.Fractionpastel.OkLab→pastel.helper.Fractionpastel.RGBA→pastel.helper.Fraction
- Direction
- pastel uses helper, so a change to helper can break pastel, while a change to pastel can't break helper.
- Position
- Below the diagonal: pastel uses a module listed above it, which is the healthy direction.
7→4 pastel uses types✕
- Connections
- 1 pair of types, where a type in pastel uses a type in types.
- The types involved
pastel.Color→pastel.types.Hue
- Direction
- pastel uses types, so a change to types can break pastel, while a change to pastel can't break types.
- Position
- Below the diagonal: pastel uses a module listed above it, which is the healthy direction.
7→5 pastel uses ansi✕
- Connections
- 4 pairs of types, where a type in pastel uses a type in ansi.
- The types involved
pastel.Color→pastel.ansi.AnsiColorpastel.Color→pastel.ansi.Modepastel.Color→pastel.ansi.Stylepastel.Color→pastel.ansi.ToAnsiStyle
- Direction
- pastel uses ansi, so a change to ansi can break pastel, while a change to pastel can't break ansi.
- Position
- Below the diagonal: pastel uses a module listed above it, which is the healthy direction.
7→6 pastel uses colorspace✕
- Connections
- 7 pairs of types, where a type in pastel uses a type in colorspace.
- The types involved
pastel.HSLA→pastel.colorspace.ColorSpacepastel.HSVA→pastel.colorspace.ColorSpacepastel.LCh→pastel.colorspace.ColorSpacepastel.Lab→pastel.colorspace.ColorSpacepastel.OkLCh→pastel.colorspace.ColorSpacepastel.OkLab→pastel.colorspace.ColorSpacepastel.RGBA→pastel.colorspace.ColorSpace
- Direction
- pastel uses colorspace, so a change to colorspace can break pastel, while a change to pastel can't break colorspace.
- Position
- Below the diagonal: pastel uses a module listed above it, which is the healthy direction.
8→5 cli.config uses ansi✕
- Connections
- 1 pair of types, where a type in cli.config uses a type in ansi.
- The types involved
pastel.cli.config.Config→pastel.ansi.Brush
- Direction
- cli.config uses ansi, so a change to ansi can break cli.config, while a change to cli.config can't break ansi.
- Position
- Below the diagonal: cli.config uses a module listed above it, which is the healthy direction.
9→5 cli.error uses ansi✕
- Connections
- 1 pair of types, where a type in cli.error uses a type in ansi.
- The types involved
pastel.cli.error.PastelError→pastel.ansi.UnknownColorModeError
- Direction
- cli.error uses ansi, so a change to ansi can break cli.error, while a change to cli.error can't break ansi.
- Position
- Below the diagonal: cli.error uses a module listed above it, which is the healthy direction.
10→8 cli.colorpicker uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.colorpicker uses a type in cli.config.
- The types involved
pastel.cli.colorpicker.colorpicker$module→pastel.cli.config.Config
- Direction
- cli.colorpicker uses cli.config, so a change to cli.config can break cli.colorpicker, while a change to cli.colorpicker can't break cli.config.
- Position
- Below the diagonal: cli.colorpicker uses a module listed above it, which is the healthy direction.
11→8 cli.commands uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands uses a type in cli.config.
- The types involved
pastel.cli.commands.Command→pastel.cli.config.Config
- Direction
- cli.commands uses cli.config, so a change to cli.config can break cli.commands, while a change to cli.commands can't break cli.config.
- Position
- Below the diagonal: cli.commands uses a module listed above it, which is the healthy direction.
12→8 cli.commands.io uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.io uses a type in cli.config.
- The types involved
pastel.cli.commands.io.ColorArgIterator→pastel.cli.config.Config
- Direction
- cli.commands.io uses cli.config, so a change to cli.config can break cli.commands.io, while a change to cli.commands.io can't break cli.config.
- Position
- Below the diagonal: cli.commands.io uses a module listed above it, which is the healthy direction.
13→5 cli.hdcanvas uses ansi✕
- Connections
- 1 pair of types, where a type in cli.hdcanvas uses a type in ansi.
- The types involved
pastel.cli.hdcanvas.Canvas→pastel.ansi.Brush
- Direction
- cli.hdcanvas uses ansi, so a change to ansi can break cli.hdcanvas, while a change to cli.hdcanvas can't break ansi.
- Position
- Below the diagonal: cli.hdcanvas uses a module listed above it, which is the healthy direction.
13→7 cli.hdcanvas uses pastel✕
- Connections
- 1 pair of types, where a type in cli.hdcanvas uses a type in pastel.
- The types involved
pastel.cli.hdcanvas.Canvas→pastel.Color
- Direction
- cli.hdcanvas uses pastel, so a change to pastel can break cli.hdcanvas, while a change to cli.hdcanvas can't break pastel.
- Position
- Below the diagonal: cli.hdcanvas uses a module listed above it, which is the healthy direction.
14→7 cli.main uses pastel✕
- Connections
- 1 pair of types, where a type in cli.main uses a type in pastel.
- The types involved
pastel.cli.main.main$module→pastel.Color
- Direction
- cli.main uses pastel, so a change to pastel can break cli.main, while a change to cli.main can't break pastel.
- Position
- Below the diagonal: cli.main uses a module listed above it, which is the healthy direction.
15→7 cli.output uses pastel✕
- Connections
- 1 pair of types, where a type in cli.output uses a type in pastel.
- The types involved
pastel.cli.output.Output→pastel.Color
- Direction
- cli.output uses pastel, so a change to pastel can break cli.output, while a change to cli.output can't break pastel.
- Position
- Below the diagonal: cli.output uses a module listed above it, which is the healthy direction.
15→8 cli.output uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.output uses a type in cli.config.
- The types involved
pastel.cli.output.Output→pastel.cli.config.Config
- Direction
- cli.output uses cli.config, so a change to cli.config can break cli.output, while a change to cli.output can't break cli.config.
- Position
- Below the diagonal: cli.output uses a module listed above it, which is the healthy direction.
16→7 delta_e uses pastel✕
- Connections
- 1 pair of types, where a type in delta_e uses a type in pastel.
- The types involved
pastel.delta_e.delta_e$module→pastel.Lab
- Direction
- delta_e uses pastel, so a change to pastel can break delta_e, while a change to delta_e can't break pastel.
- Position
- Below the diagonal: delta_e uses a module listed above it, which is the healthy direction.
17→7 distinct uses pastel✕
- Connections
- 5 pairs of types, where a type in distinct uses a type in pastel.
- The types involved
pastel.distinct.DistanceResult→pastel.Labpastel.distinct.IterationStatistics→pastel.Colorpastel.distinct.SimulatedAnnealing→pastel.Colorpastel.distinct.SimulatedAnnealing→pastel.Labpastel.distinct.distinct$module→pastel.Color
- Direction
- distinct uses pastel, so a change to pastel can break distinct, while a change to distinct can't break pastel.
- Position
- Below the diagonal: distinct uses a module listed above it, which is the healthy direction.
18→7 named uses pastel✕
- Connections
- 1 pair of types, where a type in named uses a type in pastel.
- The types involved
pastel.named.NamedColor→pastel.Color
- Direction
- named uses pastel, so a change to pastel can break named, while a change to named can't break pastel.
- Position
- Below the diagonal: named uses a module listed above it, which is the healthy direction.
19→7 parser uses pastel✕
- Connections
- 1 pair of types, where a type in parser uses a type in pastel.
- The types involved
pastel.parser.parser$module→pastel.Color
- Direction
- parser uses pastel, so a change to pastel can break parser, while a change to parser can't break pastel.
- Position
- Below the diagonal: parser uses a module listed above it, which is the healthy direction.
20→7 random uses pastel✕
- Connections
- 1 pair of types, where a type in random uses a type in pastel.
- The types involved
pastel.random.RandomizationStrategy→pastel.Color
- Direction
- random uses pastel, so a change to pastel can break random, while a change to random can't break pastel.
- Position
- Below the diagonal: random uses a module listed above it, which is the healthy direction.
21→11 cli.cli uses cli.commands✕
- Connections
- 1 pair of types, where a type in cli.cli uses a type in cli.commands.
- The types involved
pastel.cli.cli.cli$module→pastel.cli.commands.Command
- Direction
- cli.cli uses cli.commands, so a change to cli.commands can break cli.cli, while a change to cli.cli can't break cli.commands.
- Position
- Below the diagonal: cli.cli uses a module listed above it, which is the healthy direction.
22→7 cli.commands.traits uses pastel✕
- Connections
- 1 pair of types, where a type in cli.commands.traits uses a type in pastel.
- The types involved
pastel.cli.commands.traits.ColorCommand→pastel.Color
- Direction
- cli.commands.traits uses pastel, so a change to pastel can break cli.commands.traits, while a change to cli.commands.traits can't break pastel.
- Position
- Below the diagonal: cli.commands.traits uses a module listed above it, which is the healthy direction.
22→8 cli.commands.traits uses cli.config✕
- Connections
- 2 pairs of types, where a type in cli.commands.traits uses a type in cli.config.
- The types involved
pastel.cli.commands.traits.ColorCommand→pastel.cli.config.Configpastel.cli.commands.traits.GenericCommand→pastel.cli.config.Config
- Direction
- cli.commands.traits uses cli.config, so a change to cli.config can break cli.commands.traits, while a change to cli.commands.traits can't break cli.config.
- Position
- Below the diagonal: cli.commands.traits uses a module listed above it, which is the healthy direction.
22→15 cli.commands.traits uses cli.output✕
- Connections
- 2 pairs of types, where a type in cli.commands.traits uses a type in cli.output.
- The types involved
pastel.cli.commands.traits.ColorCommand→pastel.cli.output.Outputpastel.cli.commands.traits.GenericCommand→pastel.cli.output.Output
- Direction
- cli.commands.traits uses cli.output, so a change to cli.output can break cli.commands.traits, while a change to cli.commands.traits can't break cli.output.
- Position
- Below the diagonal: cli.commands.traits uses a module listed above it, which is the healthy direction.
23→7 cli.utility uses pastel✕
- Connections
- 1 pair of types, where a type in cli.utility uses a type in pastel.
- The types involved
pastel.cli.utility.utility$module→pastel.Color
- Direction
- cli.utility uses pastel, so a change to pastel can break cli.utility, while a change to cli.utility can't break pastel.
- Position
- Below the diagonal: cli.utility uses a module listed above it, which is the healthy direction.
23→18 cli.utility uses named✕
- Connections
- 1 pair of types, where a type in cli.utility uses a type in named.
- The types involved
pastel.cli.utility.utility$module→pastel.named.NamedColor
- Direction
- cli.utility uses named, so a change to named can break cli.utility, while a change to cli.utility can't break named.
- Position
- Below the diagonal: cli.utility uses a module listed above it, which is the healthy direction.
24→7 random.strategies uses pastel✕
- Connections
- 4 pairs of types, where a type in random.strategies uses a type in pastel.
- The types involved
pastel.random.strategies.UniformGray→pastel.Colorpastel.random.strategies.UniformHueLCh→pastel.Colorpastel.random.strategies.UniformRGB→pastel.Colorpastel.random.strategies.Vivid→pastel.Color
- Direction
- random.strategies uses pastel, so a change to pastel can break random.strategies, while a change to random.strategies can't break pastel.
- Position
- Below the diagonal: random.strategies uses a module listed above it, which is the healthy direction.
24→20 random.strategies uses random✕
- Connections
- 4 pairs of types, where a type in random.strategies uses a type in random.
- The types involved
pastel.random.strategies.UniformGray→pastel.random.RandomizationStrategypastel.random.strategies.UniformHueLCh→pastel.random.RandomizationStrategypastel.random.strategies.UniformRGB→pastel.random.RandomizationStrategypastel.random.strategies.Vivid→pastel.random.RandomizationStrategy
- Direction
- random.strategies uses random, so a change to random can break random.strategies, while a change to random.strategies can't break random.
- Position
- Below the diagonal: random.strategies uses a module listed above it, which is the healthy direction.
25→7 cli.commands.color_commands uses pastel✕
- Connections
- 11 pairs of types, where a type in cli.commands.color_commands uses a type in pastel.
- The types involved
pastel.cli.commands.color_commands.ColorblindCommand→pastel.Colorpastel.cli.commands.color_commands.ComplementCommand→pastel.Colorpastel.cli.commands.color_commands.DarkenCommand→pastel.Colorpastel.cli.commands.color_commands.DesaturateCommand→pastel.Colorpastel.cli.commands.color_commands.LightenCommand→pastel.Colorpastel.cli.commands.color_commands.MixCommand→pastel.Colorpastel.cli.commands.color_commands.RotateCommand→pastel.Colorpastel.cli.commands.color_commands.SaturateCommand→pastel.Colorpastel.cli.commands.color_commands.SetCommand→pastel.Colorpastel.cli.commands.color_commands.TextColorCommand→pastel.Colorpastel.cli.commands.color_commands.ToGrayCommand→pastel.Color
- Direction
- cli.commands.color_commands uses pastel, so a change to pastel can break cli.commands.color_commands, while a change to cli.commands.color_commands can't break pastel.
- Position
- Below the diagonal: cli.commands.color_commands uses a module listed above it, which is the healthy direction.
25→8 cli.commands.color_commands uses cli.config✕
- Connections
- 11 pairs of types, where a type in cli.commands.color_commands uses a type in cli.config.
- The types involved
pastel.cli.commands.color_commands.ColorblindCommand→pastel.cli.config.Configpastel.cli.commands.color_commands.ComplementCommand→pastel.cli.config.Configpastel.cli.commands.color_commands.DarkenCommand→pastel.cli.config.Configpastel.cli.commands.color_commands.DesaturateCommand→pastel.cli.config.Configpastel.cli.commands.color_commands.LightenCommand→pastel.cli.config.Configpastel.cli.commands.color_commands.MixCommand→pastel.cli.config.Configpastel.cli.commands.color_commands.RotateCommand→pastel.cli.config.Configpastel.cli.commands.color_commands.SaturateCommand→pastel.cli.config.Configpastel.cli.commands.color_commands.SetCommand→pastel.cli.config.Configpastel.cli.commands.color_commands.TextColorCommand→pastel.cli.config.Configpastel.cli.commands.color_commands.ToGrayCommand→pastel.cli.config.Config
- Direction
- cli.commands.color_commands uses cli.config, so a change to cli.config can break cli.commands.color_commands, while a change to cli.commands.color_commands can't break cli.config.
- Position
- Below the diagonal: cli.commands.color_commands uses a module listed above it, which is the healthy direction.
25→15 cli.commands.color_commands uses cli.output✕
- Connections
- 11 pairs of types, where a type in cli.commands.color_commands uses a type in cli.output.
- The types involved
pastel.cli.commands.color_commands.ColorblindCommand→pastel.cli.output.Outputpastel.cli.commands.color_commands.ComplementCommand→pastel.cli.output.Outputpastel.cli.commands.color_commands.DarkenCommand→pastel.cli.output.Outputpastel.cli.commands.color_commands.DesaturateCommand→pastel.cli.output.Outputpastel.cli.commands.color_commands.LightenCommand→pastel.cli.output.Outputpastel.cli.commands.color_commands.MixCommand→pastel.cli.output.Outputpastel.cli.commands.color_commands.RotateCommand→pastel.cli.output.Outputpastel.cli.commands.color_commands.SaturateCommand→pastel.cli.output.Outputpastel.cli.commands.color_commands.SetCommand→pastel.cli.output.Outputpastel.cli.commands.color_commands.TextColorCommand→pastel.cli.output.Outputpastel.cli.commands.color_commands.ToGrayCommand→pastel.cli.output.Output
- Direction
- cli.commands.color_commands uses cli.output, so a change to cli.output can break cli.commands.color_commands, while a change to cli.commands.color_commands can't break cli.output.
- Position
- Below the diagonal: cli.commands.color_commands uses a module listed above it, which is the healthy direction.
25→22 cli.commands.color_commands uses cli.commands.traits✕
- Connections
- 11 pairs of types, where a type in cli.commands.color_commands uses a type in cli.commands.traits.
- The types involved
pastel.cli.commands.color_commands.ColorblindCommand→pastel.cli.commands.traits.ColorCommandpastel.cli.commands.color_commands.ComplementCommand→pastel.cli.commands.traits.ColorCommandpastel.cli.commands.color_commands.DarkenCommand→pastel.cli.commands.traits.ColorCommandpastel.cli.commands.color_commands.DesaturateCommand→pastel.cli.commands.traits.ColorCommandpastel.cli.commands.color_commands.LightenCommand→pastel.cli.commands.traits.ColorCommandpastel.cli.commands.color_commands.MixCommand→pastel.cli.commands.traits.ColorCommandpastel.cli.commands.color_commands.RotateCommand→pastel.cli.commands.traits.ColorCommandpastel.cli.commands.color_commands.SaturateCommand→pastel.cli.commands.traits.ColorCommandpastel.cli.commands.color_commands.SetCommand→pastel.cli.commands.traits.ColorCommandpastel.cli.commands.color_commands.TextColorCommand→pastel.cli.commands.traits.ColorCommandpastel.cli.commands.color_commands.ToGrayCommand→pastel.cli.commands.traits.ColorCommand
- Direction
- cli.commands.color_commands uses cli.commands.traits, so a change to cli.commands.traits can break cli.commands.color_commands, while a change to cli.commands.color_commands can't break cli.commands.traits.
- Position
- Below the diagonal: cli.commands.color_commands uses a module listed above it, which is the healthy direction.
26→5 cli.commands.colorcheck uses ansi✕
- Connections
- 1 pair of types, where a type in cli.commands.colorcheck uses a type in ansi.
- The types involved
pastel.cli.commands.colorcheck.colorcheck$module→pastel.ansi.Mode
- Direction
- cli.commands.colorcheck uses ansi, so a change to ansi can break cli.commands.colorcheck, while a change to cli.commands.colorcheck can't break ansi.
- Position
- Below the diagonal: cli.commands.colorcheck uses a module listed above it, which is the healthy direction.
26→8 cli.commands.colorcheck uses cli.config✕
- Connections
- 2 pairs of types, where a type in cli.commands.colorcheck uses a type in cli.config.
- The types involved
pastel.cli.commands.colorcheck.ColorCheckCommand→pastel.cli.config.Configpastel.cli.commands.colorcheck.colorcheck$module→pastel.cli.config.Config
- Direction
- cli.commands.colorcheck uses cli.config, so a change to cli.config can break cli.commands.colorcheck, while a change to cli.commands.colorcheck can't break cli.config.
- Position
- Below the diagonal: cli.commands.colorcheck uses a module listed above it, which is the healthy direction.
26→15 cli.commands.colorcheck uses cli.output✕
- Connections
- 2 pairs of types, where a type in cli.commands.colorcheck uses a type in cli.output.
- The types involved
pastel.cli.commands.colorcheck.ColorCheckCommand→pastel.cli.output.Outputpastel.cli.commands.colorcheck.colorcheck$module→pastel.cli.output.Output
- Direction
- cli.commands.colorcheck uses cli.output, so a change to cli.output can break cli.commands.colorcheck, while a change to cli.commands.colorcheck can't break cli.output.
- Position
- Below the diagonal: cli.commands.colorcheck uses a module listed above it, which is the healthy direction.
26→22 cli.commands.colorcheck uses cli.commands.traits✕
- Connections
- 1 pair of types, where a type in cli.commands.colorcheck uses a type in cli.commands.traits.
- The types involved
pastel.cli.commands.colorcheck.ColorCheckCommand→pastel.cli.commands.traits.GenericCommand
- Direction
- cli.commands.colorcheck uses cli.commands.traits, so a change to cli.commands.traits can break cli.commands.colorcheck, while a change to cli.commands.colorcheck can't break cli.commands.traits.
- Position
- Below the diagonal: cli.commands.colorcheck uses a module listed above it, which is the healthy direction.
27→5 cli.commands.distinct uses ansi✕
- Connections
- 1 pair of types, where a type in cli.commands.distinct uses a type in ansi.
- The types involved
pastel.cli.commands.distinct.distinct$module→pastel.ansi.Brush
- Direction
- cli.commands.distinct uses ansi, so a change to ansi can break cli.commands.distinct, while a change to cli.commands.distinct can't break ansi.
- Position
- Below the diagonal: cli.commands.distinct uses a module listed above it, which is the healthy direction.
27→7 cli.commands.distinct uses pastel✕
- Connections
- 1 pair of types, where a type in cli.commands.distinct uses a type in pastel.
- The types involved
pastel.cli.commands.distinct.distinct$module→pastel.Color
- Direction
- cli.commands.distinct uses pastel, so a change to pastel can break cli.commands.distinct, while a change to cli.commands.distinct can't break pastel.
- Position
- Below the diagonal: cli.commands.distinct uses a module listed above it, which is the healthy direction.
27→8 cli.commands.distinct uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.distinct uses a type in cli.config.
- The types involved
pastel.cli.commands.distinct.DistinctCommand→pastel.cli.config.Config
- Direction
- cli.commands.distinct uses cli.config, so a change to cli.config can break cli.commands.distinct, while a change to cli.commands.distinct can't break cli.config.
- Position
- Below the diagonal: cli.commands.distinct uses a module listed above it, which is the healthy direction.
27→15 cli.commands.distinct uses cli.output✕
- Connections
- 1 pair of types, where a type in cli.commands.distinct uses a type in cli.output.
- The types involved
pastel.cli.commands.distinct.DistinctCommand→pastel.cli.output.Output
- Direction
- cli.commands.distinct uses cli.output, so a change to cli.output can break cli.commands.distinct, while a change to cli.commands.distinct can't break cli.output.
- Position
- Below the diagonal: cli.commands.distinct uses a module listed above it, which is the healthy direction.
27→17 cli.commands.distinct uses distinct✕
- Connections
- 2 pairs of types, where a type in cli.commands.distinct uses a type in distinct.
- The types involved
pastel.cli.commands.distinct.distinct$module→pastel.distinct.DistanceMetricpastel.cli.commands.distinct.distinct$module→pastel.distinct.IterationStatistics
- Direction
- cli.commands.distinct uses distinct, so a change to distinct can break cli.commands.distinct, while a change to cli.commands.distinct can't break distinct.
- Position
- Below the diagonal: cli.commands.distinct uses a module listed above it, which is the healthy direction.
27→22 cli.commands.distinct uses cli.commands.traits✕
- Connections
- 1 pair of types, where a type in cli.commands.distinct uses a type in cli.commands.traits.
- The types involved
pastel.cli.commands.distinct.DistinctCommand→pastel.cli.commands.traits.GenericCommand
- Direction
- cli.commands.distinct uses cli.commands.traits, so a change to cli.commands.traits can break cli.commands.distinct, while a change to cli.commands.distinct can't break cli.commands.traits.
- Position
- Below the diagonal: cli.commands.distinct uses a module listed above it, which is the healthy direction.
28→7 cli.commands.format uses pastel✕
- Connections
- 1 pair of types, where a type in cli.commands.format uses a type in pastel.
- The types involved
pastel.cli.commands.format.FormatCommand→pastel.Color
- Direction
- cli.commands.format uses pastel, so a change to pastel can break cli.commands.format, while a change to cli.commands.format can't break pastel.
- Position
- Below the diagonal: cli.commands.format uses a module listed above it, which is the healthy direction.
28→8 cli.commands.format uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.format uses a type in cli.config.
- The types involved
pastel.cli.commands.format.FormatCommand→pastel.cli.config.Config
- Direction
- cli.commands.format uses cli.config, so a change to cli.config can break cli.commands.format, while a change to cli.commands.format can't break cli.config.
- Position
- Below the diagonal: cli.commands.format uses a module listed above it, which is the healthy direction.
28→15 cli.commands.format uses cli.output✕
- Connections
- 1 pair of types, where a type in cli.commands.format uses a type in cli.output.
- The types involved
pastel.cli.commands.format.FormatCommand→pastel.cli.output.Output
- Direction
- cli.commands.format uses cli.output, so a change to cli.output can break cli.commands.format, while a change to cli.commands.format can't break cli.output.
- Position
- Below the diagonal: cli.commands.format uses a module listed above it, which is the healthy direction.
28→22 cli.commands.format uses cli.commands.traits✕
- Connections
- 1 pair of types, where a type in cli.commands.format uses a type in cli.commands.traits.
- The types involved
pastel.cli.commands.format.FormatCommand→pastel.cli.commands.traits.ColorCommand
- Direction
- cli.commands.format uses cli.commands.traits, so a change to cli.commands.traits can break cli.commands.format, while a change to cli.commands.format can't break cli.commands.traits.
- Position
- Below the diagonal: cli.commands.format uses a module listed above it, which is the healthy direction.
29→8 cli.commands.gradient uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.gradient uses a type in cli.config.
- The types involved
pastel.cli.commands.gradient.GradientCommand→pastel.cli.config.Config
- Direction
- cli.commands.gradient uses cli.config, so a change to cli.config can break cli.commands.gradient, while a change to cli.commands.gradient can't break cli.config.
- Position
- Below the diagonal: cli.commands.gradient uses a module listed above it, which is the healthy direction.
29→15 cli.commands.gradient uses cli.output✕
- Connections
- 1 pair of types, where a type in cli.commands.gradient uses a type in cli.output.
- The types involved
pastel.cli.commands.gradient.GradientCommand→pastel.cli.output.Output
- Direction
- cli.commands.gradient uses cli.output, so a change to cli.output can break cli.commands.gradient, while a change to cli.commands.gradient can't break cli.output.
- Position
- Below the diagonal: cli.commands.gradient uses a module listed above it, which is the healthy direction.
29→22 cli.commands.gradient uses cli.commands.traits✕
- Connections
- 1 pair of types, where a type in cli.commands.gradient uses a type in cli.commands.traits.
- The types involved
pastel.cli.commands.gradient.GradientCommand→pastel.cli.commands.traits.GenericCommand
- Direction
- cli.commands.gradient uses cli.commands.traits, so a change to cli.commands.traits can break cli.commands.gradient, while a change to cli.commands.gradient can't break cli.commands.traits.
- Position
- Below the diagonal: cli.commands.gradient uses a module listed above it, which is the healthy direction.
30→8 cli.commands.gray uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.gray uses a type in cli.config.
- The types involved
pastel.cli.commands.gray.GrayCommand→pastel.cli.config.Config
- Direction
- cli.commands.gray uses cli.config, so a change to cli.config can break cli.commands.gray, while a change to cli.commands.gray can't break cli.config.
- Position
- Below the diagonal: cli.commands.gray uses a module listed above it, which is the healthy direction.
30→15 cli.commands.gray uses cli.output✕
- Connections
- 1 pair of types, where a type in cli.commands.gray uses a type in cli.output.
- The types involved
pastel.cli.commands.gray.GrayCommand→pastel.cli.output.Output
- Direction
- cli.commands.gray uses cli.output, so a change to cli.output can break cli.commands.gray, while a change to cli.commands.gray can't break cli.output.
- Position
- Below the diagonal: cli.commands.gray uses a module listed above it, which is the healthy direction.
30→22 cli.commands.gray uses cli.commands.traits✕
- Connections
- 1 pair of types, where a type in cli.commands.gray uses a type in cli.commands.traits.
- The types involved
pastel.cli.commands.gray.GrayCommand→pastel.cli.commands.traits.GenericCommand
- Direction
- cli.commands.gray uses cli.commands.traits, so a change to cli.commands.traits can break cli.commands.gray, while a change to cli.commands.gray can't break cli.commands.traits.
- Position
- Below the diagonal: cli.commands.gray uses a module listed above it, which is the healthy direction.
31→8 cli.commands.list uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.list uses a type in cli.config.
- The types involved
pastel.cli.commands.list.ListCommand→pastel.cli.config.Config
- Direction
- cli.commands.list uses cli.config, so a change to cli.config can break cli.commands.list, while a change to cli.commands.list can't break cli.config.
- Position
- Below the diagonal: cli.commands.list uses a module listed above it, which is the healthy direction.
31→15 cli.commands.list uses cli.output✕
- Connections
- 1 pair of types, where a type in cli.commands.list uses a type in cli.output.
- The types involved
pastel.cli.commands.list.ListCommand→pastel.cli.output.Output
- Direction
- cli.commands.list uses cli.output, so a change to cli.output can break cli.commands.list, while a change to cli.commands.list can't break cli.output.
- Position
- Below the diagonal: cli.commands.list uses a module listed above it, which is the healthy direction.
31→22 cli.commands.list uses cli.commands.traits✕
- Connections
- 1 pair of types, where a type in cli.commands.list uses a type in cli.commands.traits.
- The types involved
pastel.cli.commands.list.ListCommand→pastel.cli.commands.traits.GenericCommand
- Direction
- cli.commands.list uses cli.commands.traits, so a change to cli.commands.traits can break cli.commands.list, while a change to cli.commands.list can't break cli.commands.traits.
- Position
- Below the diagonal: cli.commands.list uses a module listed above it, which is the healthy direction.
32→8 cli.commands.paint uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.paint uses a type in cli.config.
- The types involved
pastel.cli.commands.paint.PaintCommand→pastel.cli.config.Config
- Direction
- cli.commands.paint uses cli.config, so a change to cli.config can break cli.commands.paint, while a change to cli.commands.paint can't break cli.config.
- Position
- Below the diagonal: cli.commands.paint uses a module listed above it, which is the healthy direction.
32→15 cli.commands.paint uses cli.output✕
- Connections
- 1 pair of types, where a type in cli.commands.paint uses a type in cli.output.
- The types involved
pastel.cli.commands.paint.PaintCommand→pastel.cli.output.Output
- Direction
- cli.commands.paint uses cli.output, so a change to cli.output can break cli.commands.paint, while a change to cli.commands.paint can't break cli.output.
- Position
- Below the diagonal: cli.commands.paint uses a module listed above it, which is the healthy direction.
32→22 cli.commands.paint uses cli.commands.traits✕
- Connections
- 1 pair of types, where a type in cli.commands.paint uses a type in cli.commands.traits.
- The types involved
pastel.cli.commands.paint.PaintCommand→pastel.cli.commands.traits.GenericCommand
- Direction
- cli.commands.paint uses cli.commands.traits, so a change to cli.commands.traits can break cli.commands.paint, while a change to cli.commands.paint can't break cli.commands.traits.
- Position
- Below the diagonal: cli.commands.paint uses a module listed above it, which is the healthy direction.
33→8 cli.commands.pick uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.pick uses a type in cli.config.
- The types involved
pastel.cli.commands.pick.PickCommand→pastel.cli.config.Config
- Direction
- cli.commands.pick uses cli.config, so a change to cli.config can break cli.commands.pick, while a change to cli.commands.pick can't break cli.config.
- Position
- Below the diagonal: cli.commands.pick uses a module listed above it, which is the healthy direction.
33→15 cli.commands.pick uses cli.output✕
- Connections
- 1 pair of types, where a type in cli.commands.pick uses a type in cli.output.
- The types involved
pastel.cli.commands.pick.PickCommand→pastel.cli.output.Output
- Direction
- cli.commands.pick uses cli.output, so a change to cli.output can break cli.commands.pick, while a change to cli.commands.pick can't break cli.output.
- Position
- Below the diagonal: cli.commands.pick uses a module listed above it, which is the healthy direction.
33→22 cli.commands.pick uses cli.commands.traits✕
- Connections
- 1 pair of types, where a type in cli.commands.pick uses a type in cli.commands.traits.
- The types involved
pastel.cli.commands.pick.PickCommand→pastel.cli.commands.traits.GenericCommand
- Direction
- cli.commands.pick uses cli.commands.traits, so a change to cli.commands.traits can break cli.commands.pick, while a change to cli.commands.pick can't break cli.commands.traits.
- Position
- Below the diagonal: cli.commands.pick uses a module listed above it, which is the healthy direction.
34→8 cli.commands.random uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.random uses a type in cli.config.
- The types involved
pastel.cli.commands.random.RandomCommand→pastel.cli.config.Config
- Direction
- cli.commands.random uses cli.config, so a change to cli.config can break cli.commands.random, while a change to cli.commands.random can't break cli.config.
- Position
- Below the diagonal: cli.commands.random uses a module listed above it, which is the healthy direction.
34→15 cli.commands.random uses cli.output✕
- Connections
- 1 pair of types, where a type in cli.commands.random uses a type in cli.output.
- The types involved
pastel.cli.commands.random.RandomCommand→pastel.cli.output.Output
- Direction
- cli.commands.random uses cli.output, so a change to cli.output can break cli.commands.random, while a change to cli.commands.random can't break cli.output.
- Position
- Below the diagonal: cli.commands.random uses a module listed above it, which is the healthy direction.
34→22 cli.commands.random uses cli.commands.traits✕
- Connections
- 1 pair of types, where a type in cli.commands.random uses a type in cli.commands.traits.
- The types involved
pastel.cli.commands.random.RandomCommand→pastel.cli.commands.traits.GenericCommand
- Direction
- cli.commands.random uses cli.commands.traits, so a change to cli.commands.traits can break cli.commands.random, while a change to cli.commands.random can't break cli.commands.traits.
- Position
- Below the diagonal: cli.commands.random uses a module listed above it, which is the healthy direction.
35→7 cli.commands.show uses pastel✕
- Connections
- 1 pair of types, where a type in cli.commands.show uses a type in pastel.
- The types involved
pastel.cli.commands.show.ShowCommand→pastel.Color
- Direction
- cli.commands.show uses pastel, so a change to pastel can break cli.commands.show, while a change to cli.commands.show can't break pastel.
- Position
- Below the diagonal: cli.commands.show uses a module listed above it, which is the healthy direction.
35→8 cli.commands.show uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.show uses a type in cli.config.
- The types involved
pastel.cli.commands.show.ShowCommand→pastel.cli.config.Config
- Direction
- cli.commands.show uses cli.config, so a change to cli.config can break cli.commands.show, while a change to cli.commands.show can't break cli.config.
- Position
- Below the diagonal: cli.commands.show uses a module listed above it, which is the healthy direction.
35→15 cli.commands.show uses cli.output✕
- Connections
- 1 pair of types, where a type in cli.commands.show uses a type in cli.output.
- The types involved
pastel.cli.commands.show.ShowCommand→pastel.cli.output.Output
- Direction
- cli.commands.show uses cli.output, so a change to cli.output can break cli.commands.show, while a change to cli.commands.show can't break cli.output.
- Position
- Below the diagonal: cli.commands.show uses a module listed above it, which is the healthy direction.
35→22 cli.commands.show uses cli.commands.traits✕
- Connections
- 1 pair of types, where a type in cli.commands.show uses a type in cli.commands.traits.
- The types involved
pastel.cli.commands.show.ShowCommand→pastel.cli.commands.traits.ColorCommand
- Direction
- cli.commands.show uses cli.commands.traits, so a change to cli.commands.traits can break cli.commands.show, while a change to cli.commands.show can't break cli.commands.traits.
- Position
- Below the diagonal: cli.commands.show uses a module listed above it, which is the healthy direction.
36→7 cli.commands.sort uses pastel✕
- Connections
- 1 pair of types, where a type in cli.commands.sort uses a type in pastel.
- The types involved
pastel.cli.commands.sort.sort$module→pastel.Color
- Direction
- cli.commands.sort uses pastel, so a change to pastel can break cli.commands.sort, while a change to cli.commands.sort can't break pastel.
- Position
- Below the diagonal: cli.commands.sort uses a module listed above it, which is the healthy direction.
36→8 cli.commands.sort uses cli.config✕
- Connections
- 1 pair of types, where a type in cli.commands.sort uses a type in cli.config.
- The types involved
pastel.cli.commands.sort.SortCommand→pastel.cli.config.Config
- Direction
- cli.commands.sort uses cli.config, so a change to cli.config can break cli.commands.sort, while a change to cli.commands.sort can't break cli.config.
- Position
- Below the diagonal: cli.commands.sort uses a module listed above it, which is the healthy direction.
36→15 cli.commands.sort uses cli.output✕
- Connections
- 1 pair of types, where a type in cli.commands.sort uses a type in cli.output.
- The types involved
pastel.cli.commands.sort.SortCommand→pastel.cli.output.Output
- Direction
- cli.commands.sort uses cli.output, so a change to cli.output can break cli.commands.sort, while a change to cli.commands.sort can't break cli.output.
- Position
- Below the diagonal: cli.commands.sort uses a module listed above it, which is the healthy direction.
36→22 cli.commands.sort uses cli.commands.traits✕
- Connections
- 1 pair of types, where a type in cli.commands.sort uses a type in cli.commands.traits.
- The types involved
pastel.cli.commands.sort.SortCommand→pastel.cli.commands.traits.GenericCommand
- Direction
- cli.commands.sort uses cli.commands.traits, so a change to cli.commands.traits can break cli.commands.sort, while a change to cli.commands.sort can't break cli.commands.traits.
- Position
- Below the diagonal: cli.commands.sort 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 |
|---|---|---|
| A05:2025 — Injection | 17 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml; 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; Resolve the 16 Orphaned file finding(s) in Knowledge Freshness — start with distinct.rs (2), ansi.rs, delta_e.rs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. | +7.2 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. | +6.0 pts | Medium | Architecture documentation |
| Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with lib.rs, parser.rs, cli.rs. | +3.0 pts | Low | Knowledge Freshness |
| Resolve the 16 Orphaned file finding(s) in Knowledge Freshness — start with distinct.rs (2), ansi.rs, delta_e.rs. | +5.9 pts | Medium | Knowledge Freshness |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +3.2 pts | Medium | Observability |
| 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. | +2.8 pts | Medium | Documentation (README) |
| Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. | +0.8 pts | Low | Knowledge Freshness |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.4 pts | Medium | Deployment & Rollback |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| src/lib.rs | 5.5 | Mixed | God Classes: TooManyMethods: Color |
| src/cli/commands/distinct.rs | 6.3 | Mixed | Cognitive Complexity: pastel::cli::commands::distinct::print_distance_matrix (cognitive 23) |
| REDACTED | 6.3 | Mixed | Dependency Vulnerabilities: Medium vulnerability: REDACTED |
| src/cli/commands/color_commands.rs | 7.0 | Near-clean | Cyclomatic Complexity: SetCommand::run (cyclomatic 21) |
| src/cli/main.rs | 7.0 | Near-clean | Cognitive Complexity: pastel::cli::main::run (cognitive 20) |
| src/cli/hdcanvas.rs | 7.0 | Near-clean | Cognitive Complexity: Canvas::print (cognitive 17) |
| src/parser.rs | 7.1 | Near-clean | Code Duplication: Edited copy of a member (12 corresponding lines) |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| src/distinct.rs | 8.5 | Near-clean | Cognitive Complexity: SimulatedAnnealing::run (cognitive 23) |
| src/cli/cli.rs | 8.5 | Near-clean | God Classes: FunctionTooLong: pastel::cli::cli::build_cli |
| src/ansi.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| src/cli/colorpicker.rs | 8.5 | Near-clean | Code Coverage: Low coverage: src/cli/colorpicker.rs |
| src/cli/colorspace.rs | 8.5 | Near-clean | Code Coverage: Low coverage: src/cli/colorspace.rs |
| src/cli/commands/colorcheck.rs | 8.5 | Near-clean | Code Coverage: Low coverage: src/cli/commands/colorcheck.rs |
| src/cli/commands/format.rs | 8.5 | Near-clean | Code Coverage: Low coverage: src/cli/commands/format.rs |
| src/cli/commands/gradient.rs | 8.5 | Near-clean | Code Coverage: Low coverage: src/cli/commands/gradient.rs |
| src/cli/commands/gray.rs | 8.5 | Near-clean | Code Coverage: Low coverage: src/cli/commands/gray.rs |
| src/cli/commands/io.rs | 8.5 | Near-clean | Code Coverage: Low coverage: src/cli/commands/io.rs |
| src/cli/commands/list.rs | 8.5 | Near-clean | Code Coverage: Low coverage: src/cli/commands/list.rs |
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 38 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 — 38 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, 94 of 108 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- 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.
- 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.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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
1 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was SetCommand::run at 21. A further 3 function(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 FormatCommand::run at 40 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/cli/commands/format.rs (FormatCommand::run at 40), src/cli/commands/mod.rs (Command::from_string at 23), src/ansi.rs (Color::from_ansi_8bit at 18). 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 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with SetCommand::run (cyclomatic 21). — Refactoring it lifts Cyclomatic Complexity from 9.6 to about 10.0/10.
D2 · Cognitive Complexity
4 function(s) exceeded the cognitive complexity threshold of 15; the worst was SimulatedAnnealing::run at 23.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with SimulatedAnnealing::run (cognitive 23), pastel::cli::commands::distinct::print_distance_matrix (cognitive 23), pastel::cli::main::run (cognitive 20). — 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 4 together lifts Cognitive Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
4 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with cli.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with lib.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with lib.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
12 duplicated block group(s) detected. 6.8 % of the production lines (419 of 6,199) are in a reported copy. A further 9 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with parser.rs (2), lib.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with lib.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with distinct.rs, lib.rs. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
1 of 18 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with lib.rs. — One of this dimension's main actionable groups (1 warning-level).
D8 · Code Coverage
Line coverage 60.9% — 22 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 32 production file(s), 3 test binaries and 0 doc-test binaries).
What to do
- Resolve the 22 Low coverage finding(s) in Code Coverage — start with random.rs (2), colorpicker.rs, colorspace.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, 9 test files): measured (0 flaky).
D12 · Dependency Hygiene
4 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 70 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/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
No source file's living knowledge is concentrated in a single author. Counted over 19 of the 36 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
0 deducted task-comment markers across 6199 LoC (0.0/KLoC) → score 10.0. 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
17 finding(s): 0 critical, 17 high, 0 medium, 0 low. 12 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 12 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (12 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 0 high, 3 medium, 0 low.
What to do
- Resolve the 2 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
19 of 19 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/lib.rs. Counted over 19 of the 36 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 16 Orphaned file finding(s) in Knowledge Freshness — start with distinct.rs (2), ansi.rs, delta_e.rs. — One of this dimension's main actionable groups (16 recommendation-level).
- Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with lib.rs, parser.rs, cli.rs. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
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)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF1 · Benchmark discipline
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 93% | Exemplary | Solid. |
| Architecture | 99% | Exemplary | Strongest area. |
| Maturity | 53% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 60% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 80% | Strong | Solid. |
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 — 77 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 — ~169 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.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (873 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
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (6199 LoC, 86 module-visible types across 3 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- 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.
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 32 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: 36 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.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 20 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge src/lib.rs:1
- Orphaned knowledge src/parser.rs:1
- Orphaned knowledge src/cli/cli.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 59 finding(s)
- Low coverage: src/cli/colorpicker.rs src/cli/colorpicker.rs:1
- Low coverage: src/cli/colorspace.rs src/cli/colorspace.rs:1
- Low coverage: src/cli/commands/color_commands.rs src/cli/commands/color_commands.rs:1
- Low coverage: src/cli/commands/colorcheck.rs src/cli/commands/colorcheck.rs:1
- Low coverage: src/cli/commands/distinct.rs src/cli/commands/distinct.rs:1
- Low coverage: src/cli/commands/format.rs src/cli/commands/format.rs:1
- Low coverage: src/cli/commands/gradient.rs src/cli/commands/gradient.rs:1
- Low coverage: src/cli/commands/gray.rs src/cli/commands/gray.rs:1
- Low coverage: src/cli/commands/io.rs src/cli/commands/io.rs:1
- Low coverage: src/cli/commands/list.rs src/cli/commands/list.rs:1
- Low coverage: src/cli/commands/mod.rs src/cli/commands/mod.rs:1
- Low coverage: src/cli/commands/paint.rs src/cli/commands/paint.rs:1
- Low coverage: src/cli/commands/pick.rs src/cli/commands/pick.rs:1
- Low coverage: src/cli/commands/random.rs src/cli/commands/random.rs:1
- Low coverage: src/cli/commands/show.rs src/cli/commands/show.rs:1
- Low coverage: src/cli/commands/sort.rs src/cli/commands/sort.rs:1
- Low coverage: src/cli/error.rs src/cli/error.rs:1
- Low coverage: src/cli/hdcanvas.rs src/cli/hdcanvas.rs:1
- Low coverage: src/cli/main.rs src/cli/main.rs:1
- Low coverage: src/cli/output.rs src/cli/output.rs:1
- Low coverage: src/cli/utility.rs src/cli/utility.rs:1
- Low coverage: src/random.rs src/random.rs:1
- Duplicated block (6 lines × 2) src/lib.rs:1148
- Duplicated block (6 lines × 2) src/parser.rs:91
- Duplicated block (6 lines × 2) src/parser.rs:95
- pastel::cli::commands::distinct::print_distance_matrix (cognitive 23) src/cli/commands/distinct.rs:60
- pastel::cli::main::run (cognitive 20) src/cli/main.rs:59
- REDACTED
- REDACTED
- Duplicated block (15 lines × 2) src/lib.rs:392
- Duplicated block (15 lines × 2) src/lib.rs:452
- Duplicated block (7 lines × 2) src/cli/commands/distinct.rs:134
- Duplicated block (7 lines × 2) src/lib.rs:1323
- SetCommand::run (cyclomatic 21) src/cli/commands/color_commands.rs:16
- SimulatedAnnealing::run (cognitive 23) src/distinct.rs:124
- Canvas::print (cognitive 17) src/cli/hdcanvas.rs:85
- FunctionTooLong: pastel::cli::cli::build_cli src/cli/cli.rs:11
- TooManyMethods: Color src/lib.rs:28
- FileTooLong: src/lib.rs src/lib.rs
- ClassTooLong: Color src/lib.rs:28
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (12 corresponding lines) src/parser.rs:169
- Members sharing a duplicated core (5 members, 50+ identical tokens) src/parser.rs:130
- Edited copy of a member (16 corresponding lines) src/lib.rs:972
- Edited copies of one member (4 members, 24+ corresponding lines) src/lib.rs:180
- Edited copies of one member (4 members, 20+ corresponding lines) src/lib.rs:387
- Edited copies of one member (4 members, 12+ corresponding lines) src/lib.rs:1146
- Edited copy of a member (10 corresponding lines) src/lib.rs:1465
- Edited copy of a member (14 corresponding lines) src/lib.rs:991
- Edited copies of one member (3 members, 8+ corresponding lines) src/lib.rs:1058
- Duplicated block (14 lines × 2) src/lib.rs:250
- Duplicated block (10 lines × 2) src/lib.rs:1452
- Duplicated block (8 lines × 2) src/ansi.rs:162
- Duplicated block (5 lines × 5) src/parser.rs:133
- Duplicated block (6 lines × 3) src/parser.rs:156
- Low cohesion: Color (LCOM4 6) src/lib.rs:28
- No structured logging
Minor — 25 finding(s)
- Orphaned file src/distinct.rs:1
- Orphaned file src/ansi.rs:1
- Orphaned file src/delta_e.rs:1
- Orphaned file src/named.rs:1
- Orphaned file src/cli/commands/color_commands.rs:1
- Orphaned file src/cli/commands/distinct.rs:1
- Orphaned file src/cli/colorpicker_tools.rs:1
- Orphaned file src/cli/hdcanvas.rs:1
- Orphaned file src/cli/main.rs:1
- Orphaned file src/cli/commands/format.rs:1
- Orphaned file src/cli/output.rs:1
- Orphaned file src/cli/commands/io.rs:1
- Orphaned file src/helper.rs:1
- Orphaned file src/cli/commands/mod.rs:1
- Orphaned file src/cli/error.rs:1
- Orphaned file src/cli/colorpicker.rs:1
- No ADRs found Cargo.toml:37
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No release approval gate
Minor — 4 finding(s)
- Outdated: clap
- Outdated: clap_complete
- Outdated: once_cell
- Outdated: regex
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-75b664ae450e4a5bbb6bf9d2fc3b3e4a/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-75b664ae450e4a5bbb6bf9d2fc3b3e4a/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 . | 17 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 3 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |