Executive summary
lsd-rs/lsd falls short of our standard for production because we found no logging, tracing or health checks in the code. It scores 57 out of 100 and is rated Adequate, and all 16 of its critical findings are security problems in the build pipeline.
Production Readiness, at 43, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points. Adding a diagnostic log would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 67.
Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two pipeline steps run downloads nobody checks, and two secrets can leak from the build pipeline. Pinning each tool to an exact version, checking each download against a checksum and limiting each secret to its own step would close these risks.
The product code is 11,735 lines, about €13,000 to rebuild.
If Production Readiness rose from 43 to 70, the lowest score rated Strong, the score would rise from 57 to about 67.
New since the last survey: 1 finding
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,300 to €22,000, for 72 to 227 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 57. 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: 11,735 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 app | 2 flags.blocks | 3 flags.date | 4 flags.dereference | 5 flags.display | 6 flags.header | 7 flags.hyperlink | 8 flags.ignore_globs | 9 flags.indicators | 10 flags.layout | 11 flags.literal | 12 flags.permission | 13 flags.size | 14 flags.symlinks | 15 flags.total_size | 16 git_theme | 17 meta.inode | 18 meta.links | 19 flags.symlink_arrow | 20 meta.git_file_status | 21 flags | 22 git | 23 flags.color | 24 flags.icons | 25 flags.sorting | 26 meta.date | 27 meta.permissions | 28 meta.size | 29 config_file | 30 meta.filetype | 31 flags.truncate_owner | 32 meta.indicator | 33 theme.color | 34 color | 35 meta.name | 36 meta.owner | 37 meta.permissions_or_attributes | 38 meta | 39 core | 40 display |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 app | ||||||||||||||||||||||||||||||||||||||||
| 2 flags.blocks | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 3 flags.date | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 4 flags.dereference | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 5 flags.display | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 6 flags.header | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 7 flags.hyperlink | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 8 flags.ignore_globs | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 flags.indicators | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 flags.layout | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 11 flags.literal | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 flags.permission | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 flags.size | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 14 flags.symlinks | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 flags.total_size | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 git_theme | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 meta.inode | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 meta.links | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 flags.symlink_arrow | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 meta.git_file_status | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 flags | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 7 | |||||||||||||||||||||||
| 22 git | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 flags.color | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 24 flags.icons | 4 | 3 | 4 | |||||||||||||||||||||||||||||||||||||
| 25 flags.sorting | 4 | 3 | 4 | |||||||||||||||||||||||||||||||||||||
| 26 meta.date | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 meta.permissions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 meta.size | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 config_file | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||
| 30 meta.filetype | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 flags.truncate_owner | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 meta.indicator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 theme.color | 1 | 1 | 1 | 1 | 1 | 14 | 1 | |||||||||||||||||||||||||||||||||
| 34 color | 1 | 3 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 35 meta.name | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 meta.owner | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 meta.permissions_or_attributes | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 meta | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||
| 39 core | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 display | 1 | 1 | 1 | 1 | 1 | 1 |
2→1 flags.blocks uses app✕
- Connections
- 1 pair of types, where a type in flags.blocks uses a type in app.
- The types involved
lsd.flags.blocks.Blocks→lsd.app.Cli
- Direction
- flags.blocks uses app, so a change to app can break flags.blocks, while a change to flags.blocks can't break app.
- Position
- Below the diagonal: flags.blocks uses a module listed above it, which is the healthy direction.
2→21 flags.blocks uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.blocks uses a type in flags.
- The types involved
lsd.flags.blocks.Blocks→lsd.flags.Configurable
- Direction
- flags.blocks uses flags, so a change to flags can break flags.blocks, while a change to flags.blocks can't break flags.
- 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.
2→29 flags.blocks uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.blocks uses a type in config_file.
- The types involved
lsd.flags.blocks.Blocks→lsd.config_file.Config
- Direction
- flags.blocks uses config_file, so a change to config_file can break flags.blocks, while a change to flags.blocks can't break config_file.
- 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.
3→1 flags.date uses app✕
- Connections
- 1 pair of types, where a type in flags.date uses a type in app.
- The types involved
lsd.flags.date.DateFlag→lsd.app.Cli
- Direction
- flags.date uses app, so a change to app can break flags.date, while a change to flags.date can't break app.
- Position
- Below the diagonal: flags.date uses a module listed above it, which is the healthy direction.
3→21 flags.date uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.date uses a type in flags.
- The types involved
lsd.flags.date.DateFlag→lsd.flags.Configurable
- Direction
- flags.date uses flags, so a change to flags can break flags.date, while a change to flags.date can't break flags.
- 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.
3→29 flags.date uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.date uses a type in config_file.
- The types involved
lsd.flags.date.DateFlag→lsd.config_file.Config
- Direction
- flags.date uses config_file, so a change to config_file can break flags.date, while a change to flags.date can't break config_file.
- 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.
4→1 flags.dereference uses app✕
- Connections
- 1 pair of types, where a type in flags.dereference uses a type in app.
- The types involved
lsd.flags.dereference.Dereference→lsd.app.Cli
- Direction
- flags.dereference uses app, so a change to app can break flags.dereference, while a change to flags.dereference can't break app.
- Position
- Below the diagonal: flags.dereference uses a module listed above it, which is the healthy direction.
4→21 flags.dereference uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.dereference uses a type in flags.
- The types involved
lsd.flags.dereference.Dereference→lsd.flags.Configurable
- Direction
- flags.dereference uses flags, so a change to flags can break flags.dereference, while a change to flags.dereference can't break flags.
- 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.
4→29 flags.dereference uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.dereference uses a type in config_file.
- The types involved
lsd.flags.dereference.Dereference→lsd.config_file.Config
- Direction
- flags.dereference uses config_file, so a change to config_file can break flags.dereference, while a change to flags.dereference can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→1 flags.display uses app✕
- Connections
- 1 pair of types, where a type in flags.display uses a type in app.
- The types involved
lsd.flags.display.Display→lsd.app.Cli
- Direction
- flags.display uses app, so a change to app can break flags.display, while a change to flags.display can't break app.
- Position
- Below the diagonal: flags.display uses a module listed above it, which is the healthy direction.
5→21 flags.display uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.display uses a type in flags.
- The types involved
lsd.flags.display.Display→lsd.flags.Configurable
- Direction
- flags.display uses flags, so a change to flags can break flags.display, while a change to flags.display can't break flags.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→29 flags.display uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.display uses a type in config_file.
- The types involved
lsd.flags.display.Display→lsd.config_file.Config
- Direction
- flags.display uses config_file, so a change to config_file can break flags.display, while a change to flags.display can't break config_file.
- 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→1 flags.header uses app✕
- Connections
- 1 pair of types, where a type in flags.header uses a type in app.
- The types involved
lsd.flags.header.Header→lsd.app.Cli
- Direction
- flags.header uses app, so a change to app can break flags.header, while a change to flags.header can't break app.
- Position
- Below the diagonal: flags.header uses a module listed above it, which is the healthy direction.
6→21 flags.header uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.header uses a type in flags.
- The types involved
lsd.flags.header.Header→lsd.flags.Configurable
- Direction
- flags.header uses flags, so a change to flags can break flags.header, while a change to flags.header can't break flags.
- 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→29 flags.header uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.header uses a type in config_file.
- The types involved
lsd.flags.header.Header→lsd.config_file.Config
- Direction
- flags.header uses config_file, so a change to config_file can break flags.header, while a change to flags.header can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→1 flags.hyperlink uses app✕
- Connections
- 1 pair of types, where a type in flags.hyperlink uses a type in app.
- The types involved
lsd.flags.hyperlink.HyperlinkOption→lsd.app.Cli
- Direction
- flags.hyperlink uses app, so a change to app can break flags.hyperlink, while a change to flags.hyperlink can't break app.
- Position
- Below the diagonal: flags.hyperlink uses a module listed above it, which is the healthy direction.
7→21 flags.hyperlink uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.hyperlink uses a type in flags.
- The types involved
lsd.flags.hyperlink.HyperlinkOption→lsd.flags.Configurable
- Direction
- flags.hyperlink uses flags, so a change to flags can break flags.hyperlink, while a change to flags.hyperlink can't break flags.
- 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→29 flags.hyperlink uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.hyperlink uses a type in config_file.
- The types involved
lsd.flags.hyperlink.HyperlinkOption→lsd.config_file.Config
- Direction
- flags.hyperlink uses config_file, so a change to config_file can break flags.hyperlink, while a change to flags.hyperlink can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→1 flags.ignore_globs uses app✕
- Connections
- 1 pair of types, where a type in flags.ignore_globs uses a type in app.
- The types involved
lsd.flags.ignore_globs.IgnoreGlobs→lsd.app.Cli
- Direction
- flags.ignore_globs uses app, so a change to app can break flags.ignore_globs, while a change to flags.ignore_globs can't break app.
- Position
- Below the diagonal: flags.ignore_globs uses a module listed above it, which is the healthy direction.
8→29 flags.ignore_globs uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.ignore_globs uses a type in config_file.
- The types involved
lsd.flags.ignore_globs.IgnoreGlobs→lsd.config_file.Config
- Direction
- flags.ignore_globs uses config_file, so a change to config_file can break flags.ignore_globs, while a change to flags.ignore_globs can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→1 flags.indicators uses app✕
- Connections
- 1 pair of types, where a type in flags.indicators uses a type in app.
- The types involved
lsd.flags.indicators.Indicators→lsd.app.Cli
- Direction
- flags.indicators uses app, so a change to app can break flags.indicators, while a change to flags.indicators can't break app.
- Position
- Below the diagonal: flags.indicators uses a module listed above it, which is the healthy direction.
9→21 flags.indicators uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.indicators uses a type in flags.
- The types involved
lsd.flags.indicators.Indicators→lsd.flags.Configurable
- Direction
- flags.indicators uses flags, so a change to flags can break flags.indicators, while a change to flags.indicators can't break flags.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→29 flags.indicators uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.indicators uses a type in config_file.
- The types involved
lsd.flags.indicators.Indicators→lsd.config_file.Config
- Direction
- flags.indicators uses config_file, so a change to config_file can break flags.indicators, while a change to flags.indicators can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→1 flags.layout uses app✕
- Connections
- 1 pair of types, where a type in flags.layout uses a type in app.
- The types involved
lsd.flags.layout.Layout→lsd.app.Cli
- Direction
- flags.layout uses app, so a change to app can break flags.layout, while a change to flags.layout can't break app.
- Position
- Below the diagonal: flags.layout uses a module listed above it, which is the healthy direction.
10→21 flags.layout uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.layout uses a type in flags.
- The types involved
lsd.flags.layout.Layout→lsd.flags.Configurable
- Direction
- flags.layout uses flags, so a change to flags can break flags.layout, while a change to flags.layout can't break flags.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→29 flags.layout uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.layout uses a type in config_file.
- The types involved
lsd.flags.layout.Layout→lsd.config_file.Config
- Direction
- flags.layout uses config_file, so a change to config_file can break flags.layout, while a change to flags.layout can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→1 flags.literal uses app✕
- Connections
- 1 pair of types, where a type in flags.literal uses a type in app.
- The types involved
lsd.flags.literal.Literal→lsd.app.Cli
- Direction
- flags.literal uses app, so a change to app can break flags.literal, while a change to flags.literal can't break app.
- Position
- Below the diagonal: flags.literal uses a module listed above it, which is the healthy direction.
11→21 flags.literal uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.literal uses a type in flags.
- The types involved
lsd.flags.literal.Literal→lsd.flags.Configurable
- Direction
- flags.literal uses flags, so a change to flags can break flags.literal, while a change to flags.literal can't break flags.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→29 flags.literal uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.literal uses a type in config_file.
- The types involved
lsd.flags.literal.Literal→lsd.config_file.Config
- Direction
- flags.literal uses config_file, so a change to config_file can break flags.literal, while a change to flags.literal can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→1 flags.permission uses app✕
- Connections
- 1 pair of types, where a type in flags.permission uses a type in app.
- The types involved
lsd.flags.permission.PermissionFlag→lsd.app.Cli
- Direction
- flags.permission uses app, so a change to app can break flags.permission, while a change to flags.permission can't break app.
- Position
- Below the diagonal: flags.permission uses a module listed above it, which is the healthy direction.
12→21 flags.permission uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.permission uses a type in flags.
- The types involved
lsd.flags.permission.PermissionFlag→lsd.flags.Configurable
- Direction
- flags.permission uses flags, so a change to flags can break flags.permission, while a change to flags.permission can't break flags.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→29 flags.permission uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.permission uses a type in config_file.
- The types involved
lsd.flags.permission.PermissionFlag→lsd.config_file.Config
- Direction
- flags.permission uses config_file, so a change to config_file can break flags.permission, while a change to flags.permission can't break config_file.
- 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.
13→1 flags.size uses app✕
- Connections
- 1 pair of types, where a type in flags.size uses a type in app.
- The types involved
lsd.flags.size.SizeFlag→lsd.app.Cli
- Direction
- flags.size uses app, so a change to app can break flags.size, while a change to flags.size can't break app.
- Position
- Below the diagonal: flags.size uses a module listed above it, which is the healthy direction.
13→21 flags.size uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.size uses a type in flags.
- The types involved
lsd.flags.size.SizeFlag→lsd.flags.Configurable
- Direction
- flags.size uses flags, so a change to flags can break flags.size, while a change to flags.size can't break flags.
- 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.
13→29 flags.size uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.size uses a type in config_file.
- The types involved
lsd.flags.size.SizeFlag→lsd.config_file.Config
- Direction
- flags.size uses config_file, so a change to config_file can break flags.size, while a change to flags.size can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→1 flags.symlinks uses app✕
- Connections
- 1 pair of types, where a type in flags.symlinks uses a type in app.
- The types involved
lsd.flags.symlinks.NoSymlink→lsd.app.Cli
- Direction
- flags.symlinks uses app, so a change to app can break flags.symlinks, while a change to flags.symlinks can't break app.
- Position
- Below the diagonal: flags.symlinks uses a module listed above it, which is the healthy direction.
14→21 flags.symlinks uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.symlinks uses a type in flags.
- The types involved
lsd.flags.symlinks.NoSymlink→lsd.flags.Configurable
- Direction
- flags.symlinks uses flags, so a change to flags can break flags.symlinks, while a change to flags.symlinks can't break flags.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→29 flags.symlinks uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.symlinks uses a type in config_file.
- The types involved
lsd.flags.symlinks.NoSymlink→lsd.config_file.Config
- Direction
- flags.symlinks uses config_file, so a change to config_file can break flags.symlinks, while a change to flags.symlinks can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→1 flags.total_size uses app✕
- Connections
- 1 pair of types, where a type in flags.total_size uses a type in app.
- The types involved
lsd.flags.total_size.TotalSize→lsd.app.Cli
- Direction
- flags.total_size uses app, so a change to app can break flags.total_size, while a change to flags.total_size can't break app.
- Position
- Below the diagonal: flags.total_size uses a module listed above it, which is the healthy direction.
15→21 flags.total_size uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.total_size uses a type in flags.
- The types involved
lsd.flags.total_size.TotalSize→lsd.flags.Configurable
- Direction
- flags.total_size uses flags, so a change to flags can break flags.total_size, while a change to flags.total_size can't break flags.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→29 flags.total_size uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.total_size uses a type in config_file.
- The types involved
lsd.flags.total_size.TotalSize→lsd.config_file.Config
- Direction
- flags.total_size uses config_file, so a change to config_file can break flags.total_size, while a change to flags.total_size can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→22 git_theme uses git part of a loop✕
- Connections
- 1 pair of types, where a type in git_theme uses a type in git.
- The types involved
lsd.git_theme.GitTheme→lsd.git.GitStatus
- Direction
- git_theme uses git, so a change to git can break git_theme, while a change to git_theme can't break git.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→34 meta.inode uses color part of a loop✕
- Connections
- 1 pair of types, where a type in meta.inode uses a type in color.
- The types involved
lsd.meta.inode.INode→lsd.color.Colors
- Direction
- meta.inode uses color, so a change to color can break meta.inode, while a change to meta.inode can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→34 meta.links uses color part of a loop✕
- Connections
- 1 pair of types, where a type in meta.links uses a type in color.
- The types involved
lsd.meta.links.Links→lsd.color.Colors
- Direction
- meta.links uses color, so a change to color can break meta.links, while a change to meta.links can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→1 flags.symlink_arrow uses app✕
- Connections
- 1 pair of types, where a type in flags.symlink_arrow uses a type in app.
- The types involved
lsd.flags.symlink_arrow.SymlinkArrow→lsd.app.Cli
- Direction
- flags.symlink_arrow uses app, so a change to app can break flags.symlink_arrow, while a change to flags.symlink_arrow can't break app.
- Position
- Below the diagonal: flags.symlink_arrow uses a module listed above it, which is the healthy direction.
19→5 flags.symlink_arrow uses flags.display✕
- Connections
- 1 pair of types, where a type in flags.symlink_arrow uses a type in flags.display.
- The types involved
lsd.flags.symlink_arrow.SymlinkArrow→lsd.flags.display.Display
- Direction
- flags.symlink_arrow uses flags.display, so a change to flags.display can break flags.symlink_arrow, while a change to flags.symlink_arrow can't break flags.display.
- Position
- Below the diagonal: flags.symlink_arrow uses a module listed above it, which is the healthy direction.
19→21 flags.symlink_arrow uses flags part of a loop✕
- Connections
- 1 pair of types, where a type in flags.symlink_arrow uses a type in flags.
- The types involved
lsd.flags.symlink_arrow.SymlinkArrow→lsd.flags.Configurable
- Direction
- flags.symlink_arrow uses flags, so a change to flags can break flags.symlink_arrow, while a change to flags.symlink_arrow can't break flags.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→29 flags.symlink_arrow uses config_file part of a loop✕
- Connections
- 1 pair of types, where a type in flags.symlink_arrow uses a type in config_file.
- The types involved
lsd.flags.symlink_arrow.SymlinkArrow→lsd.config_file.Config
- Direction
- flags.symlink_arrow uses config_file, so a change to config_file can break flags.symlink_arrow, while a change to flags.symlink_arrow can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→16 meta.git_file_status uses git_theme✕
- Connections
- 1 pair of types, where a type in meta.git_file_status uses a type in git_theme.
- The types involved
lsd.meta.git_file_status.GitFileStatus→lsd.git_theme.GitTheme
- Direction
- meta.git_file_status uses git_theme, so a change to git_theme can break meta.git_file_status, while a change to meta.git_file_status can't break git_theme.
- Position
- Below the diagonal: meta.git_file_status uses a module listed above it, which is the healthy direction.
20→22 meta.git_file_status uses git part of a loop✕
- Connections
- 1 pair of types, where a type in meta.git_file_status uses a type in git.
- The types involved
lsd.meta.git_file_status.GitFileStatus→lsd.git.GitStatus
- Direction
- meta.git_file_status uses git, so a change to git can break meta.git_file_status, while a change to meta.git_file_status can't break git.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→34 meta.git_file_status uses color part of a loop✕
- Connections
- 1 pair of types, where a type in meta.git_file_status uses a type in color.
- The types involved
lsd.meta.git_file_status.GitFileStatus→lsd.color.Colors
- Direction
- meta.git_file_status uses color, so a change to color can break meta.git_file_status, while a change to meta.git_file_status can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→1 flags uses app✕
- Connections
- 2 pairs of types, where a type in flags uses a type in app.
- The types involved
lsd.flags.Configurable→lsd.app.Clilsd.flags.Flags→lsd.app.Cli
- Direction
- flags uses app, so a change to app can break flags, while a change to flags can't break app.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→2 flags uses flags.blocks✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.blocks.
- The types involved
lsd.flags.Flags→lsd.flags.blocks.Blocks
- Direction
- flags uses flags.blocks, so a change to flags.blocks can break flags, while a change to flags can't break flags.blocks.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→3 flags uses flags.date✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.date.
- The types involved
lsd.flags.Flags→lsd.flags.date.DateFlag
- Direction
- flags uses flags.date, so a change to flags.date can break flags, while a change to flags can't break flags.date.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→4 flags uses flags.dereference✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.dereference.
- The types involved
lsd.flags.Flags→lsd.flags.dereference.Dereference
- Direction
- flags uses flags.dereference, so a change to flags.dereference can break flags, while a change to flags can't break flags.dereference.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→5 flags uses flags.display✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.display.
- The types involved
lsd.flags.Flags→lsd.flags.display.Display
- Direction
- flags uses flags.display, so a change to flags.display can break flags, while a change to flags can't break flags.display.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→6 flags uses flags.header✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.header.
- The types involved
lsd.flags.Flags→lsd.flags.header.Header
- Direction
- flags uses flags.header, so a change to flags.header can break flags, while a change to flags can't break flags.header.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→7 flags uses flags.hyperlink✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.hyperlink.
- The types involved
lsd.flags.Flags→lsd.flags.hyperlink.HyperlinkOption
- Direction
- flags uses flags.hyperlink, so a change to flags.hyperlink can break flags, while a change to flags can't break flags.hyperlink.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→8 flags uses flags.ignore_globs✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.ignore_globs.
- The types involved
lsd.flags.Flags→lsd.flags.ignore_globs.IgnoreGlobs
- Direction
- flags uses flags.ignore_globs, so a change to flags.ignore_globs can break flags, while a change to flags can't break flags.ignore_globs.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→9 flags uses flags.indicators✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.indicators.
- The types involved
lsd.flags.Flags→lsd.flags.indicators.Indicators
- Direction
- flags uses flags.indicators, so a change to flags.indicators can break flags, while a change to flags can't break flags.indicators.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→10 flags uses flags.layout✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.layout.
- The types involved
lsd.flags.Flags→lsd.flags.layout.Layout
- Direction
- flags uses flags.layout, so a change to flags.layout can break flags, while a change to flags can't break flags.layout.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→11 flags uses flags.literal✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.literal.
- The types involved
lsd.flags.Flags→lsd.flags.literal.Literal
- Direction
- flags uses flags.literal, so a change to flags.literal can break flags, while a change to flags can't break flags.literal.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→12 flags uses flags.permission✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.permission.
- The types involved
lsd.flags.Flags→lsd.flags.permission.PermissionFlag
- Direction
- flags uses flags.permission, so a change to flags.permission can break flags, while a change to flags can't break flags.permission.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→13 flags uses flags.size✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.size.
- The types involved
lsd.flags.Flags→lsd.flags.size.SizeFlag
- Direction
- flags uses flags.size, so a change to flags.size can break flags, while a change to flags can't break flags.size.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→14 flags uses flags.symlinks✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.symlinks.
- The types involved
lsd.flags.Flags→lsd.flags.symlinks.NoSymlink
- Direction
- flags uses flags.symlinks, so a change to flags.symlinks can break flags, while a change to flags can't break flags.symlinks.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→15 flags uses flags.total_size✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.total_size.
- The types involved
lsd.flags.Flags→lsd.flags.total_size.TotalSize
- Direction
- flags uses flags.total_size, so a change to flags.total_size can break flags, while a change to flags can't break flags.total_size.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→19 flags uses flags.symlink_arrow✕
- Connections
- 1 pair of types, where a type in flags uses a type in flags.symlink_arrow.
- The types involved
lsd.flags.Flags→lsd.flags.symlink_arrow.SymlinkArrow
- Direction
- flags uses flags.symlink_arrow, so a change to flags.symlink_arrow can break flags, while a change to flags can't break flags.symlink_arrow.
- Position
- Below the diagonal: flags uses a module listed above it, which is the healthy direction.
21→29 flags uses config_file part of a loop✕
- Connections
- 7 pairs of types, where a type in flags uses a type in config_file.
- The types involved
lsd.flags.Configurable→lsd.config_file.Configlsd.flags.Flags→lsd.config_file.Colorlsd.flags.Flags→lsd.config_file.Configlsd.flags.Flags→lsd.config_file.Iconslsd.flags.Flags→lsd.config_file.Recursionlsd.flags.Flags→lsd.config_file.Sortinglsd.flags.Flags→lsd.config_file.TruncateOwner
- Direction
- flags uses config_file, so a change to config_file can break flags, while a change to flags can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→20 git uses meta.git_file_status✕
- Connections
- 1 pair of types, where a type in git uses a type in meta.git_file_status.
- The types involved
lsd.git.GitCache→lsd.meta.git_file_status.GitFileStatus
- Direction
- git uses meta.git_file_status, so a change to meta.git_file_status can break git, while a change to git can't break meta.git_file_status.
- Position
- Below the diagonal: git uses a module listed above it, which is the healthy direction.
23→1 flags.color uses app✕
- Connections
- 2 pairs of types, where a type in flags.color uses a type in app.
- The types involved
lsd.flags.color.Color→lsd.app.Clilsd.flags.color.ColorOption→lsd.app.Cli
- Direction
- flags.color uses app, so a change to app can break flags.color, while a change to flags.color can't break app.
- Position
- Below the diagonal: flags.color uses a module listed above it, which is the healthy direction.
23→21 flags.color uses flags✕
- Connections
- 1 pair of types, where a type in flags.color uses a type in flags.
- The types involved
lsd.flags.color.ColorOption→lsd.flags.Configurable
- Direction
- flags.color uses flags, so a change to flags can break flags.color, while a change to flags.color can't break flags.
- Position
- Below the diagonal: flags.color uses a module listed above it, which is the healthy direction.
23→29 flags.color uses config_file part of a loop✕
- Connections
- 3 pairs of types, where a type in flags.color uses a type in config_file.
- The types involved
lsd.flags.color.Color→lsd.config_file.Configlsd.flags.color.ColorOption→lsd.config_file.Configlsd.flags.color.ThemeOption→lsd.config_file.Config
- Direction
- flags.color uses config_file, so a change to config_file can break flags.color, while a change to flags.color can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→1 flags.icons uses app✕
- Connections
- 4 pairs of types, where a type in flags.icons uses a type in app.
- The types involved
lsd.flags.icons.IconOption→lsd.app.Clilsd.flags.icons.IconSeparator→lsd.app.Clilsd.flags.icons.IconTheme→lsd.app.Clilsd.flags.icons.Icons→lsd.app.Cli
- Direction
- flags.icons uses app, so a change to app can break flags.icons, while a change to flags.icons can't break app.
- Position
- Below the diagonal: flags.icons uses a module listed above it, which is the healthy direction.
24→21 flags.icons uses flags✕
- Connections
- 3 pairs of types, where a type in flags.icons uses a type in flags.
- The types involved
lsd.flags.icons.IconOption→lsd.flags.Configurablelsd.flags.icons.IconSeparator→lsd.flags.Configurablelsd.flags.icons.IconTheme→lsd.flags.Configurable
- Direction
- flags.icons uses flags, so a change to flags can break flags.icons, while a change to flags.icons can't break flags.
- Position
- Below the diagonal: flags.icons uses a module listed above it, which is the healthy direction.
24→29 flags.icons uses config_file part of a loop✕
- Connections
- 4 pairs of types, where a type in flags.icons uses a type in config_file.
- The types involved
lsd.flags.icons.IconOption→lsd.config_file.Configlsd.flags.icons.IconSeparator→lsd.config_file.Configlsd.flags.icons.IconTheme→lsd.config_file.Configlsd.flags.icons.Icons→lsd.config_file.Config
- Direction
- flags.icons uses config_file, so a change to config_file can break flags.icons, while a change to flags.icons can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→1 flags.sorting uses app✕
- Connections
- 4 pairs of types, where a type in flags.sorting uses a type in app.
- The types involved
lsd.flags.sorting.DirGrouping→lsd.app.Clilsd.flags.sorting.SortColumn→lsd.app.Clilsd.flags.sorting.SortOrder→lsd.app.Clilsd.flags.sorting.Sorting→lsd.app.Cli
- Direction
- flags.sorting uses app, so a change to app can break flags.sorting, while a change to flags.sorting can't break app.
- Position
- Below the diagonal: flags.sorting uses a module listed above it, which is the healthy direction.
25→21 flags.sorting uses flags✕
- Connections
- 3 pairs of types, where a type in flags.sorting uses a type in flags.
- The types involved
lsd.flags.sorting.DirGrouping→lsd.flags.Configurablelsd.flags.sorting.SortColumn→lsd.flags.Configurablelsd.flags.sorting.SortOrder→lsd.flags.Configurable
- Direction
- flags.sorting uses flags, so a change to flags can break flags.sorting, while a change to flags.sorting can't break flags.
- Position
- Below the diagonal: flags.sorting uses a module listed above it, which is the healthy direction.
25→29 flags.sorting uses config_file part of a loop✕
- Connections
- 4 pairs of types, where a type in flags.sorting uses a type in config_file.
- The types involved
lsd.flags.sorting.DirGrouping→lsd.config_file.Configlsd.flags.sorting.SortColumn→lsd.config_file.Configlsd.flags.sorting.SortOrder→lsd.config_file.Configlsd.flags.sorting.Sorting→lsd.config_file.Config
- Direction
- flags.sorting uses config_file, so a change to config_file can break flags.sorting, while a change to flags.sorting can't break config_file.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→21 meta.date uses flags✕
- Connections
- 1 pair of types, where a type in meta.date uses a type in flags.
- The types involved
lsd.meta.date.Date→lsd.flags.Flags
- Direction
- meta.date uses flags, so a change to flags can break meta.date, while a change to meta.date can't break flags.
- Position
- Below the diagonal: meta.date uses a module listed above it, which is the healthy direction.
26→34 meta.date uses color part of a loop✕
- Connections
- 1 pair of types, where a type in meta.date uses a type in color.
- The types involved
lsd.meta.date.Date→lsd.color.Colors
- Direction
- meta.date uses color, so a change to color can break meta.date, while a change to meta.date can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→21 meta.permissions uses flags✕
- Connections
- 1 pair of types, where a type in meta.permissions uses a type in flags.
- The types involved
lsd.meta.permissions.Permissions→lsd.flags.Flags
- Direction
- meta.permissions uses flags, so a change to flags can break meta.permissions, while a change to meta.permissions can't break flags.
- Position
- Below the diagonal: meta.permissions uses a module listed above it, which is the healthy direction.
27→34 meta.permissions uses color part of a loop✕
- Connections
- 1 pair of types, where a type in meta.permissions uses a type in color.
- The types involved
lsd.meta.permissions.Permissions→lsd.color.Colors
- Direction
- meta.permissions uses color, so a change to color can break meta.permissions, while a change to meta.permissions can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→21 meta.size uses flags✕
- Connections
- 1 pair of types, where a type in meta.size uses a type in flags.
- The types involved
lsd.meta.size.Size→lsd.flags.Flags
- Direction
- meta.size uses flags, so a change to flags can break meta.size, while a change to meta.size can't break flags.
- Position
- Below the diagonal: meta.size uses a module listed above it, which is the healthy direction.
28→34 meta.size uses color part of a loop✕
- Connections
- 1 pair of types, where a type in meta.size uses a type in color.
- The types involved
lsd.meta.size.Size→lsd.color.Colors
- Direction
- meta.size uses color, so a change to color can break meta.size, while a change to meta.size can't break color.
- 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.
29→5 config_file uses flags.display✕
- Connections
- 1 pair of types, where a type in config_file uses a type in flags.display.
- The types involved
lsd.config_file.Config→lsd.flags.display.Display
- Direction
- config_file uses flags.display, so a change to flags.display can break config_file, while a change to config_file can't break flags.display.
- Position
- Below the diagonal: config_file uses a module listed above it, which is the healthy direction.
29→7 config_file uses flags.hyperlink✕
- Connections
- 1 pair of types, where a type in config_file uses a type in flags.hyperlink.
- The types involved
lsd.config_file.Config→lsd.flags.hyperlink.HyperlinkOption
- Direction
- config_file uses flags.hyperlink, so a change to flags.hyperlink can break config_file, while a change to config_file can't break flags.hyperlink.
- Position
- Below the diagonal: config_file uses a module listed above it, which is the healthy direction.
29→10 config_file uses flags.layout✕
- Connections
- 1 pair of types, where a type in config_file uses a type in flags.layout.
- The types involved
lsd.config_file.Config→lsd.flags.layout.Layout
- Direction
- config_file uses flags.layout, so a change to flags.layout can break config_file, while a change to config_file can't break flags.layout.
- Position
- Below the diagonal: config_file uses a module listed above it, which is the healthy direction.
29→12 config_file uses flags.permission✕
- Connections
- 1 pair of types, where a type in config_file uses a type in flags.permission.
- The types involved
lsd.config_file.Config→lsd.flags.permission.PermissionFlag
- Direction
- config_file uses flags.permission, so a change to flags.permission can break config_file, while a change to config_file can't break flags.permission.
- Position
- Below the diagonal: config_file uses a module listed above it, which is the healthy direction.
29→13 config_file uses flags.size✕
- Connections
- 1 pair of types, where a type in config_file uses a type in flags.size.
- The types involved
lsd.config_file.Config→lsd.flags.size.SizeFlag
- Direction
- config_file uses flags.size, so a change to flags.size can break config_file, while a change to config_file can't break flags.size.
- Position
- Below the diagonal: config_file uses a module listed above it, which is the healthy direction.
29→23 config_file uses flags.color✕
- Connections
- 2 pairs of types, where a type in config_file uses a type in flags.color.
- The types involved
lsd.config_file.Color→lsd.flags.color.ColorOptionlsd.config_file.Color→lsd.flags.color.ThemeOption
- Direction
- config_file uses flags.color, so a change to flags.color can break config_file, while a change to config_file can't break flags.color.
- Position
- Below the diagonal: config_file uses a module listed above it, which is the healthy direction.
29→24 config_file uses flags.icons✕
- Connections
- 2 pairs of types, where a type in config_file uses a type in flags.icons.
- The types involved
lsd.config_file.Icons→lsd.flags.icons.IconOptionlsd.config_file.Icons→lsd.flags.icons.IconTheme
- Direction
- config_file uses flags.icons, so a change to flags.icons can break config_file, while a change to config_file can't break flags.icons.
- Position
- Below the diagonal: config_file uses a module listed above it, which is the healthy direction.
29→25 config_file uses flags.sorting✕
- Connections
- 2 pairs of types, where a type in config_file uses a type in flags.sorting.
- The types involved
lsd.config_file.Sorting→lsd.flags.sorting.DirGroupinglsd.config_file.Sorting→lsd.flags.sorting.SortColumn
- Direction
- config_file uses flags.sorting, so a change to flags.sorting can break config_file, while a change to config_file can't break flags.sorting.
- Position
- Below the diagonal: config_file uses a module listed above it, which is the healthy direction.
30→27 meta.filetype uses meta.permissions✕
- Connections
- 1 pair of types, where a type in meta.filetype uses a type in meta.permissions.
- The types involved
lsd.meta.filetype.FileType→lsd.meta.permissions.Permissions
- Direction
- meta.filetype uses meta.permissions, so a change to meta.permissions can break meta.filetype, while a change to meta.filetype can't break meta.permissions.
- Position
- Below the diagonal: meta.filetype uses a module listed above it, which is the healthy direction.
30→34 meta.filetype uses color part of a loop✕
- Connections
- 1 pair of types, where a type in meta.filetype uses a type in color.
- The types involved
lsd.meta.filetype.FileType→lsd.color.Colors
- Direction
- meta.filetype uses color, so a change to color can break meta.filetype, while a change to meta.filetype can't break color.
- 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.
31→1 flags.truncate_owner uses app✕
- Connections
- 1 pair of types, where a type in flags.truncate_owner uses a type in app.
- The types involved
lsd.flags.truncate_owner.TruncateOwner→lsd.app.Cli
- Direction
- flags.truncate_owner uses app, so a change to app can break flags.truncate_owner, while a change to flags.truncate_owner can't break app.
- Position
- Below the diagonal: flags.truncate_owner uses a module listed above it, which is the healthy direction.
31→21 flags.truncate_owner uses flags✕
- Connections
- 1 pair of types, where a type in flags.truncate_owner uses a type in flags.
- The types involved
lsd.flags.truncate_owner.TruncateOwner→lsd.flags.Configurable
- Direction
- flags.truncate_owner uses flags, so a change to flags can break flags.truncate_owner, while a change to flags.truncate_owner can't break flags.
- Position
- Below the diagonal: flags.truncate_owner uses a module listed above it, which is the healthy direction.
31→29 flags.truncate_owner uses config_file✕
- Connections
- 1 pair of types, where a type in flags.truncate_owner uses a type in config_file.
- The types involved
lsd.flags.truncate_owner.TruncateOwner→lsd.config_file.Config
- Direction
- flags.truncate_owner uses config_file, so a change to config_file can break flags.truncate_owner, while a change to flags.truncate_owner can't break config_file.
- Position
- Below the diagonal: flags.truncate_owner uses a module listed above it, which is the healthy direction.
32→21 meta.indicator uses flags✕
- Connections
- 1 pair of types, where a type in meta.indicator uses a type in flags.
- The types involved
lsd.meta.indicator.Indicator→lsd.flags.Flags
- Direction
- meta.indicator uses flags, so a change to flags can break meta.indicator, while a change to meta.indicator can't break flags.
- Position
- Below the diagonal: meta.indicator uses a module listed above it, which is the healthy direction.
32→30 meta.indicator uses meta.filetype✕
- Connections
- 1 pair of types, where a type in meta.indicator uses a type in meta.filetype.
- The types involved
lsd.meta.indicator.Indicator→lsd.meta.filetype.FileType
- Direction
- meta.indicator uses meta.filetype, so a change to meta.filetype can break meta.indicator, while a change to meta.indicator can't break meta.filetype.
- Position
- Below the diagonal: meta.indicator uses a module listed above it, which is the healthy direction.
33→17 theme.color uses meta.inode✕
- Connections
- 1 pair of types, where a type in theme.color uses a type in meta.inode.
- The types involved
lsd.theme.color.ColorTheme→lsd.meta.inode.INode
- Direction
- theme.color uses meta.inode, so a change to meta.inode can break theme.color, while a change to theme.color can't break meta.inode.
- Position
- Below the diagonal: theme.color uses a module listed above it, which is the healthy direction.
33→18 theme.color uses meta.links✕
- Connections
- 1 pair of types, where a type in theme.color uses a type in meta.links.
- The types involved
lsd.theme.color.ColorTheme→lsd.meta.links.Links
- Direction
- theme.color uses meta.links, so a change to meta.links can break theme.color, while a change to theme.color can't break meta.links.
- Position
- Below the diagonal: theme.color uses a module listed above it, which is the healthy direction.
33→22 theme.color uses git✕
- Connections
- 1 pair of types, where a type in theme.color uses a type in git.
- The types involved
lsd.theme.color.ColorTheme→lsd.git.GitStatus
- Direction
- theme.color uses git, so a change to git can break theme.color, while a change to theme.color can't break git.
- Position
- Below the diagonal: theme.color uses a module listed above it, which is the healthy direction.
33→26 theme.color uses meta.date✕
- Connections
- 1 pair of types, where a type in theme.color uses a type in meta.date.
- The types involved
lsd.theme.color.ColorTheme→lsd.meta.date.Date
- Direction
- theme.color uses meta.date, so a change to meta.date can break theme.color, while a change to theme.color can't break meta.date.
- Position
- Below the diagonal: theme.color uses a module listed above it, which is the healthy direction.
33→28 theme.color uses meta.size✕
- Connections
- 1 pair of types, where a type in theme.color uses a type in meta.size.
- The types involved
lsd.theme.color.ColorTheme→lsd.meta.size.Size
- Direction
- theme.color uses meta.size, so a change to meta.size can break theme.color, while a change to theme.color can't break meta.size.
- Position
- Below the diagonal: theme.color uses a module listed above it, which is the healthy direction.
33→29 theme.color uses config_file✕
- Connections
- 14 pairs of types, where a type in theme.color uses a type in config_file.
- The types involved
lsd.theme.color.AbsoluteTimeColor→lsd.config_file.Colorlsd.theme.color.Attributes→lsd.config_file.Colorlsd.theme.color.ColorTheme→lsd.config_file.Colorlsd.theme.color.Date→lsd.config_file.Colorlsd.theme.color.Dir→lsd.config_file.Colorlsd.theme.color.File→lsd.config_file.Colorlsd.theme.color.FileType→lsd.config_file.Colorlsd.theme.color.GitStatus→lsd.config_file.Colorlsd.theme.color.INode→lsd.config_file.Colorlsd.theme.color.Links→lsd.config_file.Colorlsd.theme.color.Permission→lsd.config_file.Colorlsd.theme.color.RelativeTimeColor→lsd.config_file.Colorlsd.theme.color.Size→lsd.config_file.Colorlsd.theme.color.Symlink→lsd.config_file.Color
- Direction
- theme.color uses config_file, so a change to config_file can break theme.color, while a change to theme.color can't break config_file.
- Position
- Below the diagonal: theme.color uses a module listed above it, which is the healthy direction.
33→30 theme.color uses meta.filetype✕
- Connections
- 1 pair of types, where a type in theme.color uses a type in meta.filetype.
- The types involved
lsd.theme.color.ColorTheme→lsd.meta.filetype.FileType
- Direction
- theme.color uses meta.filetype, so a change to meta.filetype can break theme.color, while a change to theme.color can't break meta.filetype.
- Position
- Below the diagonal: theme.color uses a module listed above it, which is the healthy direction.
34→23 color uses flags.color✕
- Connections
- 1 pair of types, where a type in color uses a type in flags.color.
- The types involved
lsd.color.Colors→lsd.flags.color.ThemeOption
- Direction
- color uses flags.color, so a change to flags.color can break color, while a change to color can't break flags.color.
- Position
- Below the diagonal: color uses a module listed above it, which is the healthy direction.
34→29 color uses config_file✕
- Connections
- 3 pairs of types, where a type in color uses a type in config_file.
- The types involved
lsd.color.Colors→lsd.config_file.Colorlsd.color.Elem→lsd.config_file.Colorlsd.color.TimestampColorEntry→lsd.config_file.Color
- Direction
- color uses config_file, so a change to config_file can break color, while a change to color can't break config_file.
- Position
- Below the diagonal: color uses a module listed above it, which is the healthy direction.
34→32 color uses meta.indicator✕
- Connections
- 1 pair of types, where a type in color uses a type in meta.indicator.
- The types involved
lsd.color.Colors→lsd.meta.indicator.Indicator
- Direction
- color uses meta.indicator, so a change to meta.indicator can break color, while a change to color can't break meta.indicator.
- Position
- Below the diagonal: color uses a module listed above it, which is the healthy direction.
34→33 color uses theme.color✕
- Connections
- 2 pairs of types, where a type in color uses a type in theme.color.
- The types involved
lsd.color.Colors→lsd.theme.color.ColorThemelsd.color.Elem→lsd.theme.color.ColorTheme
- Direction
- color uses theme.color, so a change to theme.color can break color, while a change to color can't break theme.color.
- Position
- Below the diagonal: color uses a module listed above it, which is the healthy direction.
35→7 meta.name uses flags.hyperlink✕
- Connections
- 1 pair of types, where a type in meta.name uses a type in flags.hyperlink.
- The types involved
lsd.meta.name.Name→lsd.flags.hyperlink.HyperlinkOption
- Direction
- meta.name uses flags.hyperlink, so a change to flags.hyperlink can break meta.name, while a change to meta.name can't break flags.hyperlink.
- Position
- Below the diagonal: meta.name uses a module listed above it, which is the healthy direction.
35→29 meta.name uses config_file✕
- Connections
- 1 pair of types, where a type in meta.name uses a type in config_file.
- The types involved
lsd.meta.name.Name→lsd.config_file.Icons
- Direction
- meta.name uses config_file, so a change to config_file can break meta.name, while a change to meta.name can't break config_file.
- Position
- Below the diagonal: meta.name uses a module listed above it, which is the healthy direction.
35→30 meta.name uses meta.filetype✕
- Connections
- 1 pair of types, where a type in meta.name uses a type in meta.filetype.
- The types involved
lsd.meta.name.Name→lsd.meta.filetype.FileType
- Direction
- meta.name uses meta.filetype, so a change to meta.filetype can break meta.name, while a change to meta.name can't break meta.filetype.
- Position
- Below the diagonal: meta.name uses a module listed above it, which is the healthy direction.
35→34 meta.name uses color✕
- Connections
- 1 pair of types, where a type in meta.name uses a type in color.
- The types involved
lsd.meta.name.Name→lsd.color.Colors
- Direction
- meta.name uses color, so a change to color can break meta.name, while a change to meta.name can't break color.
- Position
- Below the diagonal: meta.name uses a module listed above it, which is the healthy direction.
36→21 meta.owner uses flags✕
- Connections
- 1 pair of types, where a type in meta.owner uses a type in flags.
- The types involved
lsd.meta.owner.Owner→lsd.flags.Flags
- Direction
- meta.owner uses flags, so a change to flags can break meta.owner, while a change to meta.owner can't break flags.
- Position
- Below the diagonal: meta.owner uses a module listed above it, which is the healthy direction.
36→34 meta.owner uses color✕
- Connections
- 1 pair of types, where a type in meta.owner uses a type in color.
- The types involved
lsd.meta.owner.Owner→lsd.color.Colors
- Direction
- meta.owner uses color, so a change to color can break meta.owner, while a change to meta.owner can't break color.
- Position
- Below the diagonal: meta.owner uses a module listed above it, which is the healthy direction.
37→21 meta.permissions_or_attributes uses flags✕
- Connections
- 1 pair of types, where a type in meta.permissions_or_attributes uses a type in flags.
- The types involved
lsd.meta.permissions_or_attributes.PermissionsOrAttributes→lsd.flags.Flags
- Direction
- meta.permissions_or_attributes uses flags, so a change to flags can break meta.permissions_or_attributes, while a change to meta.permissions_or_attributes can't break flags.
- Position
- Below the diagonal: meta.permissions_or_attributes uses a module listed above it, which is the healthy direction.
37→34 meta.permissions_or_attributes uses color✕
- Connections
- 1 pair of types, where a type in meta.permissions_or_attributes uses a type in color.
- The types involved
lsd.meta.permissions_or_attributes.PermissionsOrAttributes→lsd.color.Colors
- Direction
- meta.permissions_or_attributes uses color, so a change to color can break meta.permissions_or_attributes, while a change to meta.permissions_or_attributes can't break color.
- Position
- Below the diagonal: meta.permissions_or_attributes uses a module listed above it, which is the healthy direction.
38→12 meta uses flags.permission✕
- Connections
- 1 pair of types, where a type in meta uses a type in flags.permission.
- The types involved
lsd.meta.Meta→lsd.flags.permission.PermissionFlag
- Direction
- meta uses flags.permission, so a change to flags.permission can break meta, while a change to meta can't break flags.permission.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
38→17 meta uses meta.inode✕
- Connections
- 1 pair of types, where a type in meta uses a type in meta.inode.
- The types involved
lsd.meta.Meta→lsd.meta.inode.INode
- Direction
- meta uses meta.inode, so a change to meta.inode can break meta, while a change to meta can't break meta.inode.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
38→18 meta uses meta.links✕
- Connections
- 1 pair of types, where a type in meta uses a type in meta.links.
- The types involved
lsd.meta.Meta→lsd.meta.links.Links
- Direction
- meta uses meta.links, so a change to meta.links can break meta, while a change to meta can't break meta.links.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
38→20 meta uses meta.git_file_status✕
- Connections
- 1 pair of types, where a type in meta uses a type in meta.git_file_status.
- The types involved
lsd.meta.Meta→lsd.meta.git_file_status.GitFileStatus
- Direction
- meta uses meta.git_file_status, so a change to meta.git_file_status can break meta, while a change to meta can't break meta.git_file_status.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
38→21 meta uses flags✕
- Connections
- 1 pair of types, where a type in meta uses a type in flags.
- The types involved
lsd.meta.Meta→lsd.flags.Flags
- Direction
- meta uses flags, so a change to flags can break meta, while a change to meta can't break flags.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
38→22 meta uses git✕
- Connections
- 1 pair of types, where a type in meta uses a type in git.
- The types involved
lsd.meta.Meta→lsd.git.GitCache
- Direction
- meta uses git, so a change to git can break meta, while a change to meta can't break git.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
38→26 meta uses meta.date✕
- Connections
- 1 pair of types, where a type in meta uses a type in meta.date.
- The types involved
lsd.meta.Meta→lsd.meta.date.Date
- Direction
- meta uses meta.date, so a change to meta.date can break meta, while a change to meta can't break meta.date.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
38→28 meta uses meta.size✕
- Connections
- 1 pair of types, where a type in meta uses a type in meta.size.
- The types involved
lsd.meta.Meta→lsd.meta.size.Size
- Direction
- meta uses meta.size, so a change to meta.size can break meta, while a change to meta can't break meta.size.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
38→30 meta uses meta.filetype✕
- Connections
- 1 pair of types, where a type in meta uses a type in meta.filetype.
- The types involved
lsd.meta.Meta→lsd.meta.filetype.FileType
- Direction
- meta uses meta.filetype, so a change to meta.filetype can break meta, while a change to meta can't break meta.filetype.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
38→32 meta uses meta.indicator✕
- Connections
- 1 pair of types, where a type in meta uses a type in meta.indicator.
- The types involved
lsd.meta.Meta→lsd.meta.indicator.Indicator
- Direction
- meta uses meta.indicator, so a change to meta.indicator can break meta, while a change to meta can't break meta.indicator.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
38→35 meta uses meta.name✕
- Connections
- 1 pair of types, where a type in meta uses a type in meta.name.
- The types involved
lsd.meta.Meta→lsd.meta.name.Name
- Direction
- meta uses meta.name, so a change to meta.name can break meta, while a change to meta can't break meta.name.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
38→36 meta uses meta.owner✕
- Connections
- 1 pair of types, where a type in meta uses a type in meta.owner.
- The types involved
lsd.meta.Meta→lsd.meta.owner.Owner
- Direction
- meta uses meta.owner, so a change to meta.owner can break meta, while a change to meta can't break meta.owner.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
38→37 meta uses meta.permissions_or_attributes✕
- Connections
- 1 pair of types, where a type in meta uses a type in meta.permissions_or_attributes.
- The types involved
lsd.meta.Meta→lsd.meta.permissions_or_attributes.PermissionsOrAttributes
- Direction
- meta uses meta.permissions_or_attributes, so a change to meta.permissions_or_attributes can break meta, while a change to meta can't break meta.permissions_or_attributes.
- Position
- Below the diagonal: meta uses a module listed above it, which is the healthy direction.
39→16 core uses git_theme✕
- Connections
- 1 pair of types, where a type in core uses a type in git_theme.
- The types involved
lsd.core.Core→lsd.git_theme.GitTheme
- Direction
- core uses git_theme, so a change to git_theme can break core, while a change to core can't break git_theme.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
39→21 core uses flags✕
- Connections
- 1 pair of types, where a type in core uses a type in flags.
- The types involved
lsd.core.Core→lsd.flags.Flags
- Direction
- core uses flags, so a change to flags can break core, while a change to core can't break flags.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
39→29 core uses config_file✕
- Connections
- 1 pair of types, where a type in core uses a type in config_file.
- The types involved
lsd.core.Core→lsd.config_file.Icons
- Direction
- core uses config_file, so a change to config_file can break core, while a change to core can't break config_file.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
39→34 core uses color✕
- Connections
- 1 pair of types, where a type in core uses a type in color.
- The types involved
lsd.core.Core→lsd.color.Colors
- Direction
- core uses color, so a change to color can break core, while a change to core can't break color.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
39→38 core uses meta✕
- Connections
- 1 pair of types, where a type in core uses a type in meta.
- The types involved
lsd.core.Core→lsd.meta.Meta
- Direction
- core uses meta, so a change to meta can break core, while a change to core can't break meta.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
40→16 display uses git_theme✕
- Connections
- 1 pair of types, where a type in display uses a type in git_theme.
- The types involved
lsd.display.display$module→lsd.git_theme.GitTheme
- Direction
- display uses git_theme, so a change to git_theme can break display, while a change to display can't break git_theme.
- Position
- Below the diagonal: display uses a module listed above it, which is the healthy direction.
40→21 display uses flags✕
- Connections
- 1 pair of types, where a type in display uses a type in flags.
- The types involved
lsd.display.display$module→lsd.flags.Flags
- Direction
- display uses flags, so a change to flags can break display, while a change to display can't break flags.
- Position
- Below the diagonal: display uses a module listed above it, which is the healthy direction.
40→29 display uses config_file✕
- Connections
- 1 pair of types, where a type in display uses a type in config_file.
- The types involved
lsd.display.display$module→lsd.config_file.Icons
- Direction
- display uses config_file, so a change to config_file can break display, while a change to display can't break config_file.
- Position
- Below the diagonal: display uses a module listed above it, which is the healthy direction.
40→34 display uses color✕
- Connections
- 1 pair of types, where a type in display uses a type in color.
- The types involved
lsd.display.display$module→lsd.color.Colors
- Direction
- display uses color, so a change to color can break display, while a change to display can't break color.
- Position
- Below the diagonal: display uses a module listed above it, which is the healthy direction.
40→35 display uses meta.name✕
- Connections
- 1 pair of types, where a type in display uses a type in meta.name.
- The types involved
lsd.display.display$module→lsd.meta.name.DisplayOption
- Direction
- display uses meta.name, so a change to meta.name can break display, while a change to display can't break meta.name.
- Position
- Below the diagonal: display uses a module listed above it, which is the healthy direction.
40→38 display uses meta✕
- Connections
- 1 pair of types, where a type in display uses a type in meta.
- The types involved
lsd.display.display$module→lsd.meta.Meta
- Direction
- display uses meta, so a change to meta can break display, while a change to display can't break meta.
- Position
- Below the diagonal: display 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 16 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 13 | Medium |
Roadmap
Begin by resolving the missing architectural decision records and addressing the twenty-seven orphaned files to ensure knowledge freshness and design traceability. Next, implement a diagnostic logging trail with verbose flags to capture error paths, enabling users to provide actionable bug reports. Finally, enable automated dependency review tools to strengthen security and performance monitoring.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +8.1 pts | Low | ADR Quality |
| 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. | +7.4 pts | Medium | Observability |
| 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.2 pts | Medium | Architecture documentation |
| Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with size.rs (2), blocks.rs, sorting.rs. | +5.2 pts | Medium | Knowledge Freshness |
| Enable Dependabot/Renovate or a dependency-review gate. | +3.3 pts | Medium | Security & performance tooling |
| 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. | +2.3 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.3 pts | Medium | Release Hygiene |
| 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. | +1.3 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| src/color.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/core.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/meta/windows_utils.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/display.rs | 7.1 | Mixed | Cyclomatic Complexity: lsd::display::get_output (cyclomatic 29) |
| src/app.rs | 7.2 | Mixed | Cyclomatic Complexity: lsd::app::validate_time_format (cyclomatic 21) |
| src/meta/mod.rs | 7.4 | Mixed | Cyclomatic Complexity: Meta::recurse_into (cyclomatic 22) |
| src/theme/color.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/meta/date.rs | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| src/flags/layout.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/meta/name.rs | 8.5 | Near-clean | Cognitive Complexity: Name::escape (cognitive 17) |
| src/meta/owner.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (12 lines × 2) |
| src/flags/color.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 45 of 45 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 45 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 77 of 101 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`cargo tarpaulin`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rs), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs 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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
5 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was lsd::display::get_output at 29. A further 1 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 Elem::get_color at 48 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with lsd::display::get_output (cyclomatic 29), lsd::color::to_content_style (cyclomatic 27), Meta::recurse_into (cyclomatic 22). — 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 5 together lifts Cyclomatic Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
9 function(s) exceeded the cognitive complexity threshold of 15; the worst was lsd::display::get_output at 43.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with lsd::display::get_output (cognitive 43). — Refactoring it lifts Cognitive Complexity from 7.6 to about 8.2/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 TooManyFields finding(s) in God Classes — start with app.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
4 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with owner.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with windows_utils.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with color.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 31 classes have LCOM4 above 3.
D9 · Test Distribution
447 test methods: 402 unit, 45 integration, 0 BDD, 0 e2e. The Rust suite contributes 447 `#[test]` function(s) across 43 file(s) declaring at least one; its unit/integration split is Cargo's own — 1 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 43 test files): measured (0 flaky).
D12 · Dependency Hygiene
9 outdated, 0 yanked direct Cargo dependencies. 21 of 29 direct crates were graded against crates.io (0 not published there, 8 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 201 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/meta/windows_utils.rs. Counted over 39 of the 52 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
6 deducted task-comment markers across 11735 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 5 TodoComment finding(s) in Explicit Debt — start with color.rs (2), core.rs, windows_utils.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with date.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 1 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
16 finding(s): 0 critical, 16 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 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
6 finding(s): 0 critical, 0 high, 6 medium, 0 low.
What to do
- Resolve the 3 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Medium advisory (unmaintained) 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
29 of 39 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/display.rs. Counted over 39 of the 52 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 27 Orphaned file finding(s) in Knowledge Freshness — start with size.rs (2), blocks.rs, sorting.rs. — One of this dimension's main actionable groups (27 recommendation-level).
- Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with display.rs, name.rs. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Concentrated knowledge decay 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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
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
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
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 95% | Exemplary | Solid. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 56% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 43% | Weak — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 73% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 — ~767 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 — Naming consistency is measured on C# only; Rust not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (14 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 52 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.
- 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
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 16 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 35 finding(s)
- TodoComment src/color.rs:207
- TodoComment src/core.rs:59
- TodoComment src/theme/color.rs:444
- TodoComment src/meta/windows_utils.rs:281
- TodoComment src/flags/layout.rs:32
- lsd::display::get_output (cyclomatic 29) src/display.rs:325
- lsd::color::to_content_style (cyclomatic 27) src/color.rs:394
- lsd::app::validate_time_format (cyclomatic 21) src/app.rs:215
- lsd::display::inner_display_grid (cyclomatic 18) src/display.rs:82
- lsd::display::get_output (cognitive 43) src/display.rs:325
- lsd::display::inner_display_grid (cognitive 28) src/display.rs:82
- lsd::app::validate_time_format (cognitive 24) src/app.rs:215
- lsd::display::inner_display_tree (cognitive 21) src/display.rs:232
- REDACTED
- REDACTED
- REDACTED
- Meta::recurse_into (cognitive 27) src/meta/mod.rs:63
- Meta::calculate_total_size (cognitive 20) src/meta/mod.rs:192
- REDACTED
- REDACTED
- Meta::recurse_into (cyclomatic 22) src/meta/mod.rs:63
- FixmeComment src/meta/date.rs:19
- Colors::new (cognitive 22) src/color.rs:195
- Core::fetch (cognitive 18) src/core.rs:105
- Name::escape (cognitive 17) src/meta/name.rs:81
- TooManyFields: Cli src/app.rs:7
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2) src/meta/owner.rs:71
- Duplicated block (11 lines × 2) src/meta/windows_utils.rs:71
- Duplicated block (7 lines × 2) src/flags/color.rs:119
- Duplicated block (5 lines × 2) src/app.rs:222
- Coverage collected but not gated
- No structured logging
Minor — 41 finding(s)
- Orphaned file src/flags/blocks.rs:1
- Orphaned file src/flags/sorting.rs:1
- Orphaned file src/sort.rs:1
- Orphaned file src/config_file.rs:1
- Orphaned file src/meta/permissions.rs:1
- Orphaned file src/meta/date.rs:1
- Orphaned file src/meta/filetype.rs:1
- Orphaned file src/flags/icons.rs:1
- Orphaned file src/app.rs:1
- Orphaned file src/meta/size.rs:1
- Orphaned file src/flags/color.rs:1
- Orphaned file src/core.rs:1
- Orphaned file src/flags/recursion.rs:1
- Orphaned file src/flags/permission.rs:1
- Orphaned file src/flags/ignore_globs.rs:1
- Orphaned file src/flags.rs:1
- Orphaned file src/flags/hyperlink.rs:1
- Orphaned file src/flags/size.rs:1
- Orphaned file src/meta/access_control.rs:1
- Orphaned file src/flags/display.rs:1
- Orphaned file src/meta/symlink.rs:1
- Orphaned file src/meta/windows_attributes.rs:1
- Orphaned file src/flags/layout.rs:1
- Orphaned file src/flags/truncate_owner.rs:1
- Orphaned file src/main.rs:1
- Most significant orphaned file src/display.rs:1
- Most significant orphaned file src/meta/name.rs:1
- Off-boarding risk: anonymized user #1
- No ADRs found
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No release approval gate
- No changelog
Minor — 9 finding(s)
- Outdated: chrono
- Outdated: jiff
- Outdated: once_cell
- Outdated: serde
- Outdated: sys-locale
- Outdated: thiserror
- Outdated: unicode-width
- Outdated: url
- Outdated: xattr
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-dad8e9ba5b944ec0892d2d1edd184d54/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-dad8e9ba5b944ec0892d2d1edd184d54/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 16 | 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 . | 6 | 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 |