Executive summary
o2sh/onefetch falls short of our standard for production because we found no logging, tracing or health checks in the code. It scores 69 out of 100 and is rated Adequate, and all 17 of its critical findings are security problems.
Production Readiness, at 67, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step for the work it takes is recording design decisions, worth about 1 point. Adopting a logging library would lift Production Readiness itself, worth about 2 points.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two known security holes in the packages the code depends on can be used by attackers, and two pipeline steps install packages that can change without warning. Pinning each tool to an exact version, updating the vulnerable packages and pinning what the pipeline installs would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once.
The product code is 5,563 lines, about €7,600 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 22 findings
- Cohesion (LCOM4) · Low cohesion: Tokens (LCOM4 4) src/render/ascii.rs
- Churn × Complexity Hotspots · Hotspot: src/data/fields/mod.rs src/data/fields/mod.rs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 11 findings
- Cohesion (LCOM4) · Low cohesion: Tokens (LCOM4 4) src/render/logo.rs
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED .github/workflows/msrv-badge.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/msrv-badge.yml
- Static Analysis (SAST) · High: npm-missing-minimum-release-age site/.npmrc
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €7,600 · Estimate
| Cost to rebuild | €2,500 to €13,000, for 42 to 133 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 | ×1.0 at a score of 69. 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: 5,563 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 data.fields | 2 data.git.bots | 3 data.git.metrics | 4 data.manifest | 5 data.title | 6 render.format | 7 render.image | 8 render.style | 9 data.git.traversal | 10 render | 11 render.ascii | 12 render.image.iterm | 13 cli | 14 render.colors | 15 render.fields | 16 data | 17 data.fields.activity | 18 data.fields.authors | 19 data.fields.churn | 20 data.fields.commits | 21 data.fields.contributors | 22 data.fields.created | 23 data.fields.dependencies | 24 data.fields.description | 25 data.fields.head | 26 data.fields.languages | 27 data.fields.last_change | 28 data.fields.license | 29 data.fields.lines_of_code | 30 data.fields.pending | 31 data.fields.project | 32 data.fields.size | 33 data.fields.url | 34 data.fields.version | 35 options | 36 data.builder | 37 data.loc | 38 render.fields.languages | 39 render.info | 40 render.printer |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 data.fields | ||||||||||||||||||||||||||||||||||||||||
| 2 data.git.bots | ||||||||||||||||||||||||||||||||||||||||
| 3 data.git.metrics | ||||||||||||||||||||||||||||||||||||||||
| 4 data.manifest | ||||||||||||||||||||||||||||||||||||||||
| 5 data.title | ||||||||||||||||||||||||||||||||||||||||
| 6 render.format | ||||||||||||||||||||||||||||||||||||||||
| 7 render.image | ||||||||||||||||||||||||||||||||||||||||
| 8 render.style | ||||||||||||||||||||||||||||||||||||||||
| 9 data.git.traversal | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 render | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 11 render.ascii | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 render.image.iterm | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 cli | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 14 render.colors | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 render.fields | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 data | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 17 data.fields.activity | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 data.fields.authors | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 data.fields.churn | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 data.fields.commits | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 data.fields.contributors | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 data.fields.created | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 data.fields.dependencies | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 data.fields.description | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 data.fields.head | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 data.fields.languages | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 data.fields.last_change | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 data.fields.license | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 data.fields.lines_of_code | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 data.fields.pending | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 data.fields.project | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 data.fields.size | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 data.fields.url | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 data.fields.version | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 options | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 data.builder | 2 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 37 data.loc | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 render.fields.languages | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 render.info | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 render.printer | 2 | 2 | 1 | 2 | 1 |
9→2 data.git.traversal uses data.git.bots✕
- Connections
- 1 pair of types, where a type in data.git.traversal uses a type in data.git.bots.
- The types involved
onefetch.data.git.traversal.traversal$module→onefetch.data.git.bots.BotRegex
- Direction
- data.git.traversal uses data.git.bots, so a change to data.git.bots can break data.git.traversal, while a change to data.git.traversal can't break data.git.bots.
- Position
- Below the diagonal: data.git.traversal uses a module listed above it, which is the healthy direction.
10→6 render uses render.format✕
- Connections
- 1 pair of types, where a type in render uses a type in render.format.
- The types involved
onefetch.render.RenderOptions→onefetch.render.format.NumberSeparator
- Direction
- render uses render.format, so a change to render.format can break render, while a change to render can't break render.format.
- Position
- Below the diagonal: render uses a module listed above it, which is the healthy direction.
10→7 render uses render.image✕
- Connections
- 1 pair of types, where a type in render uses a type in render.image.
- The types involved
onefetch.render.RenderOptions→onefetch.render.image.ImageProtocol
- Direction
- render uses render.image, so a change to render.image can break render, while a change to render can't break render.image.
- Position
- Below the diagonal: render uses a module listed above it, which is the healthy direction.
10→13 render uses cli part of a loop✕
- Connections
- 1 pair of types, where a type in render uses a type in cli.
- The types involved
onefetch.render.RenderOptions→onefetch.cli.Cli
- Direction
- render uses cli, so a change to cli can break render, while a change to render can't break cli.
- 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→8 render.ascii uses render.style✕
- Connections
- 2 pairs of types, where a type in render.ascii uses a type in render.style.
- The types involved
onefetch.render.ascii.AsciiArt→onefetch.render.style.Lineonefetch.render.ascii.Tokens→onefetch.render.style.Line
- Direction
- render.ascii uses render.style, so a change to render.style can break render.ascii, while a change to render.ascii can't break render.style.
- Position
- Below the diagonal: render.ascii uses a module listed above it, which is the healthy direction.
12→7 render.image.iterm uses render.image✕
- Connections
- 1 pair of types, where a type in render.image.iterm uses a type in render.image.
- The types involved
onefetch.render.image.iterm.ITermBackend→onefetch.render.image.ImageBackend
- Direction
- render.image.iterm uses render.image, so a change to render.image can break render.image.iterm, while a change to render.image.iterm can't break render.image.
- Position
- Below the diagonal: render.image.iterm uses a module listed above it, which is the healthy direction.
13→1 cli uses data.fields✕
- Connections
- 1 pair of types, where a type in cli uses a type in data.fields.
- The types involved
onefetch.cli.InfoArgs→onefetch.data.fields.FieldKind
- Direction
- cli uses data.fields, so a change to data.fields can break cli, while a change to cli can't break data.fields.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
13→2 cli uses data.git.bots✕
- Connections
- 1 pair of types, where a type in cli uses a type in data.git.bots.
- The types involved
onefetch.cli.InfoArgs→onefetch.data.git.bots.BotRegex
- Direction
- cli uses data.git.bots, so a change to data.git.bots can break cli, while a change to cli can't break data.git.bots.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
13→6 cli uses render.format✕
- Connections
- 1 pair of types, where a type in cli uses a type in render.format.
- The types involved
onefetch.cli.TextFormattingArgs→onefetch.render.format.NumberSeparator
- Direction
- cli uses render.format, so a change to render.format can break cli, while a change to cli can't break render.format.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
13→7 cli uses render.image✕
- Connections
- 1 pair of types, where a type in cli uses a type in render.image.
- The types involved
onefetch.cli.ImageArgs→onefetch.render.image.ImageProtocol
- Direction
- cli uses render.image, so a change to render.image can break cli, while a change to cli can't break render.image.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
13→10 cli uses render✕
- Connections
- 1 pair of types, where a type in cli uses a type in render.
- The types involved
onefetch.cli.DeveloperArgs→onefetch.render.SerializationFormat
- Direction
- cli uses render, so a change to render can break cli, while a change to cli can't break render.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
14→8 render.colors uses render.style✕
- Connections
- 2 pairs of types, where a type in render.colors uses a type in render.style.
- The types involved
onefetch.render.colors.Colors→onefetch.render.style.LanguageEntryonefetch.render.colors.Colors→onefetch.render.style.Style
- Direction
- render.colors uses render.style, so a change to render.style can break render.colors, while a change to render.colors can't break render.style.
- Position
- Below the diagonal: render.colors uses a module listed above it, which is the healthy direction.
14→10 render.colors uses render✕
- Connections
- 1 pair of types, where a type in render.colors uses a type in render.
- The types involved
onefetch.render.colors.Colors→onefetch.render.RenderOptions
- Direction
- render.colors uses render, so a change to render can break render.colors, while a change to render.colors can't break render.
- Position
- Below the diagonal: render.colors uses a module listed above it, which is the healthy direction.
15→1 render.fields uses data.fields✕
- Connections
- 1 pair of types, where a type in render.fields uses a type in data.fields.
- The types involved
onefetch.render.fields.fields$module→onefetch.data.fields.Field
- Direction
- render.fields uses data.fields, so a change to data.fields can break render.fields, while a change to render.fields can't break data.fields.
- Position
- Below the diagonal: render.fields uses a module listed above it, which is the healthy direction.
15→8 render.fields uses render.style✕
- Connections
- 1 pair of types, where a type in render.fields uses a type in render.style.
- The types involved
onefetch.render.fields.FieldView→onefetch.render.style.Line
- Direction
- render.fields uses render.style, so a change to render.style can break render.fields, while a change to render.fields can't break render.style.
- Position
- Below the diagonal: render.fields uses a module listed above it, which is the healthy direction.
15→10 render.fields uses render✕
- Connections
- 1 pair of types, where a type in render.fields uses a type in render.
- The types involved
onefetch.render.fields.FieldView→onefetch.render.RenderOptions
- Direction
- render.fields uses render, so a change to render can break render.fields, while a change to render.fields can't break render.
- Position
- Below the diagonal: render.fields uses a module listed above it, which is the healthy direction.
16→1 data uses data.fields✕
- Connections
- 2 pairs of types, where a type in data uses a type in data.fields.
- The types involved
onefetch.data.Info→onefetch.data.fields.Fieldonefetch.data.InfoOptions→onefetch.data.fields.FieldKind
- Direction
- data uses data.fields, so a change to data.fields can break data, while a change to data can't break data.fields.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
16→2 data uses data.git.bots✕
- Connections
- 1 pair of types, where a type in data uses a type in data.git.bots.
- The types involved
onefetch.data.InfoOptions→onefetch.data.git.bots.BotRegex
- Direction
- data uses data.git.bots, so a change to data.git.bots can break data, while a change to data can't break data.git.bots.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
16→5 data uses data.title✕
- Connections
- 1 pair of types, where a type in data uses a type in data.title.
- The types involved
onefetch.data.Info→onefetch.data.title.Title
- Direction
- data uses data.title, so a change to data.title can break data, while a change to data can't break data.title.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
16→13 data uses cli✕
- Connections
- 1 pair of types, where a type in data uses a type in cli.
- The types involved
onefetch.data.InfoOptions→onefetch.cli.Cli
- Direction
- data uses cli, so a change to cli can break data, while a change to data can't break cli.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
17→8 data.fields.activity uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.activity uses a type in render.style.
- The types involved
onefetch.data.fields.activity.Activity→onefetch.render.style.Line
- Direction
- data.fields.activity uses render.style, so a change to render.style can break data.fields.activity, while a change to data.fields.activity can't break render.style.
- Position
- Below the diagonal: data.fields.activity uses a module listed above it, which is the healthy direction.
17→10 data.fields.activity uses render✕
- Connections
- 1 pair of types, where a type in data.fields.activity uses a type in render.
- The types involved
onefetch.data.fields.activity.Activity→onefetch.render.RenderOptions
- Direction
- data.fields.activity uses render, so a change to render can break data.fields.activity, while a change to data.fields.activity can't break render.
- Position
- Below the diagonal: data.fields.activity uses a module listed above it, which is the healthy direction.
17→15 data.fields.activity uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.activity uses a type in render.fields.
- The types involved
onefetch.data.fields.activity.Activity→onefetch.render.fields.FieldView
- Direction
- data.fields.activity uses render.fields, so a change to render.fields can break data.fields.activity, while a change to data.fields.activity can't break render.fields.
- Position
- Below the diagonal: data.fields.activity uses a module listed above it, which is the healthy direction.
18→8 data.fields.authors uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.authors uses a type in render.style.
- The types involved
onefetch.data.fields.authors.Authors→onefetch.render.style.Line
- Direction
- data.fields.authors uses render.style, so a change to render.style can break data.fields.authors, while a change to data.fields.authors can't break render.style.
- Position
- Below the diagonal: data.fields.authors uses a module listed above it, which is the healthy direction.
18→10 data.fields.authors uses render✕
- Connections
- 1 pair of types, where a type in data.fields.authors uses a type in render.
- The types involved
onefetch.data.fields.authors.Authors→onefetch.render.RenderOptions
- Direction
- data.fields.authors uses render, so a change to render can break data.fields.authors, while a change to data.fields.authors can't break render.
- Position
- Below the diagonal: data.fields.authors uses a module listed above it, which is the healthy direction.
18→15 data.fields.authors uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.authors uses a type in render.fields.
- The types involved
onefetch.data.fields.authors.Authors→onefetch.render.fields.FieldView
- Direction
- data.fields.authors uses render.fields, so a change to render.fields can break data.fields.authors, while a change to data.fields.authors can't break render.fields.
- Position
- Below the diagonal: data.fields.authors uses a module listed above it, which is the healthy direction.
19→8 data.fields.churn uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.churn uses a type in render.style.
- The types involved
onefetch.data.fields.churn.Churn→onefetch.render.style.Line
- Direction
- data.fields.churn uses render.style, so a change to render.style can break data.fields.churn, while a change to data.fields.churn can't break render.style.
- Position
- Below the diagonal: data.fields.churn uses a module listed above it, which is the healthy direction.
19→10 data.fields.churn uses render✕
- Connections
- 1 pair of types, where a type in data.fields.churn uses a type in render.
- The types involved
onefetch.data.fields.churn.Churn→onefetch.render.RenderOptions
- Direction
- data.fields.churn uses render, so a change to render can break data.fields.churn, while a change to data.fields.churn can't break render.
- Position
- Below the diagonal: data.fields.churn uses a module listed above it, which is the healthy direction.
19→15 data.fields.churn uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.churn uses a type in render.fields.
- The types involved
onefetch.data.fields.churn.Churn→onefetch.render.fields.FieldView
- Direction
- data.fields.churn uses render.fields, so a change to render.fields can break data.fields.churn, while a change to data.fields.churn can't break render.fields.
- Position
- Below the diagonal: data.fields.churn uses a module listed above it, which is the healthy direction.
20→3 data.fields.commits uses data.git.metrics✕
- Connections
- 1 pair of types, where a type in data.fields.commits uses a type in data.git.metrics.
- The types involved
onefetch.data.fields.commits.Commits→onefetch.data.git.metrics.GitMetrics
- Direction
- data.fields.commits uses data.git.metrics, so a change to data.git.metrics can break data.fields.commits, while a change to data.fields.commits can't break data.git.metrics.
- Position
- Below the diagonal: data.fields.commits uses a module listed above it, which is the healthy direction.
20→8 data.fields.commits uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.commits uses a type in render.style.
- The types involved
onefetch.data.fields.commits.Commits→onefetch.render.style.Line
- Direction
- data.fields.commits uses render.style, so a change to render.style can break data.fields.commits, while a change to data.fields.commits can't break render.style.
- Position
- Below the diagonal: data.fields.commits uses a module listed above it, which is the healthy direction.
20→10 data.fields.commits uses render✕
- Connections
- 1 pair of types, where a type in data.fields.commits uses a type in render.
- The types involved
onefetch.data.fields.commits.Commits→onefetch.render.RenderOptions
- Direction
- data.fields.commits uses render, so a change to render can break data.fields.commits, while a change to data.fields.commits can't break render.
- Position
- Below the diagonal: data.fields.commits uses a module listed above it, which is the healthy direction.
20→15 data.fields.commits uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.commits uses a type in render.fields.
- The types involved
onefetch.data.fields.commits.Commits→onefetch.render.fields.FieldView
- Direction
- data.fields.commits uses render.fields, so a change to render.fields can break data.fields.commits, while a change to data.fields.commits can't break render.fields.
- Position
- Below the diagonal: data.fields.commits uses a module listed above it, which is the healthy direction.
21→8 data.fields.contributors uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.contributors uses a type in render.style.
- The types involved
onefetch.data.fields.contributors.Contributors→onefetch.render.style.Line
- Direction
- data.fields.contributors uses render.style, so a change to render.style can break data.fields.contributors, while a change to data.fields.contributors can't break render.style.
- Position
- Below the diagonal: data.fields.contributors uses a module listed above it, which is the healthy direction.
21→10 data.fields.contributors uses render✕
- Connections
- 1 pair of types, where a type in data.fields.contributors uses a type in render.
- The types involved
onefetch.data.fields.contributors.Contributors→onefetch.render.RenderOptions
- Direction
- data.fields.contributors uses render, so a change to render can break data.fields.contributors, while a change to data.fields.contributors can't break render.
- Position
- Below the diagonal: data.fields.contributors uses a module listed above it, which is the healthy direction.
21→15 data.fields.contributors uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.contributors uses a type in render.fields.
- The types involved
onefetch.data.fields.contributors.Contributors→onefetch.render.fields.FieldView
- Direction
- data.fields.contributors uses render.fields, so a change to render.fields can break data.fields.contributors, while a change to data.fields.contributors can't break render.fields.
- Position
- Below the diagonal: data.fields.contributors uses a module listed above it, which is the healthy direction.
22→3 data.fields.created uses data.git.metrics✕
- Connections
- 1 pair of types, where a type in data.fields.created uses a type in data.git.metrics.
- The types involved
onefetch.data.fields.created.Created→onefetch.data.git.metrics.GitMetrics
- Direction
- data.fields.created uses data.git.metrics, so a change to data.git.metrics can break data.fields.created, while a change to data.fields.created can't break data.git.metrics.
- Position
- Below the diagonal: data.fields.created uses a module listed above it, which is the healthy direction.
22→8 data.fields.created uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.created uses a type in render.style.
- The types involved
onefetch.data.fields.created.Created→onefetch.render.style.Line
- Direction
- data.fields.created uses render.style, so a change to render.style can break data.fields.created, while a change to data.fields.created can't break render.style.
- Position
- Below the diagonal: data.fields.created uses a module listed above it, which is the healthy direction.
22→10 data.fields.created uses render✕
- Connections
- 1 pair of types, where a type in data.fields.created uses a type in render.
- The types involved
onefetch.data.fields.created.Created→onefetch.render.RenderOptions
- Direction
- data.fields.created uses render, so a change to render can break data.fields.created, while a change to data.fields.created can't break render.
- Position
- Below the diagonal: data.fields.created uses a module listed above it, which is the healthy direction.
22→15 data.fields.created uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.created uses a type in render.fields.
- The types involved
onefetch.data.fields.created.Created→onefetch.render.fields.FieldView
- Direction
- data.fields.created uses render.fields, so a change to render.fields can break data.fields.created, while a change to data.fields.created can't break render.fields.
- Position
- Below the diagonal: data.fields.created uses a module listed above it, which is the healthy direction.
23→4 data.fields.dependencies uses data.manifest✕
- Connections
- 1 pair of types, where a type in data.fields.dependencies uses a type in data.manifest.
- The types involved
onefetch.data.fields.dependencies.Dependencies→onefetch.data.manifest.Manifest
- Direction
- data.fields.dependencies uses data.manifest, so a change to data.manifest can break data.fields.dependencies, while a change to data.fields.dependencies can't break data.manifest.
- Position
- Below the diagonal: data.fields.dependencies uses a module listed above it, which is the healthy direction.
23→8 data.fields.dependencies uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.dependencies uses a type in render.style.
- The types involved
onefetch.data.fields.dependencies.Dependencies→onefetch.render.style.Line
- Direction
- data.fields.dependencies uses render.style, so a change to render.style can break data.fields.dependencies, while a change to data.fields.dependencies can't break render.style.
- Position
- Below the diagonal: data.fields.dependencies uses a module listed above it, which is the healthy direction.
23→10 data.fields.dependencies uses render✕
- Connections
- 1 pair of types, where a type in data.fields.dependencies uses a type in render.
- The types involved
onefetch.data.fields.dependencies.Dependencies→onefetch.render.RenderOptions
- Direction
- data.fields.dependencies uses render, so a change to render can break data.fields.dependencies, while a change to data.fields.dependencies can't break render.
- Position
- Below the diagonal: data.fields.dependencies uses a module listed above it, which is the healthy direction.
23→15 data.fields.dependencies uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.dependencies uses a type in render.fields.
- The types involved
onefetch.data.fields.dependencies.Dependencies→onefetch.render.fields.FieldView
- Direction
- data.fields.dependencies uses render.fields, so a change to render.fields can break data.fields.dependencies, while a change to data.fields.dependencies can't break render.fields.
- Position
- Below the diagonal: data.fields.dependencies uses a module listed above it, which is the healthy direction.
24→4 data.fields.description uses data.manifest✕
- Connections
- 1 pair of types, where a type in data.fields.description uses a type in data.manifest.
- The types involved
onefetch.data.fields.description.Description→onefetch.data.manifest.Manifest
- Direction
- data.fields.description uses data.manifest, so a change to data.manifest can break data.fields.description, while a change to data.fields.description can't break data.manifest.
- Position
- Below the diagonal: data.fields.description uses a module listed above it, which is the healthy direction.
24→8 data.fields.description uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.description uses a type in render.style.
- The types involved
onefetch.data.fields.description.Description→onefetch.render.style.Line
- Direction
- data.fields.description uses render.style, so a change to render.style can break data.fields.description, while a change to data.fields.description can't break render.style.
- Position
- Below the diagonal: data.fields.description uses a module listed above it, which is the healthy direction.
24→10 data.fields.description uses render✕
- Connections
- 1 pair of types, where a type in data.fields.description uses a type in render.
- The types involved
onefetch.data.fields.description.Description→onefetch.render.RenderOptions
- Direction
- data.fields.description uses render, so a change to render can break data.fields.description, while a change to data.fields.description can't break render.
- Position
- Below the diagonal: data.fields.description uses a module listed above it, which is the healthy direction.
24→15 data.fields.description uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.description uses a type in render.fields.
- The types involved
onefetch.data.fields.description.Description→onefetch.render.fields.FieldView
- Direction
- data.fields.description uses render.fields, so a change to render.fields can break data.fields.description, while a change to data.fields.description can't break render.fields.
- Position
- Below the diagonal: data.fields.description uses a module listed above it, which is the healthy direction.
25→8 data.fields.head uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.head uses a type in render.style.
- The types involved
onefetch.data.fields.head.Head→onefetch.render.style.Line
- Direction
- data.fields.head uses render.style, so a change to render.style can break data.fields.head, while a change to data.fields.head can't break render.style.
- Position
- Below the diagonal: data.fields.head uses a module listed above it, which is the healthy direction.
25→10 data.fields.head uses render✕
- Connections
- 1 pair of types, where a type in data.fields.head uses a type in render.
- The types involved
onefetch.data.fields.head.Head→onefetch.render.RenderOptions
- Direction
- data.fields.head uses render, so a change to render can break data.fields.head, while a change to data.fields.head can't break render.
- Position
- Below the diagonal: data.fields.head uses a module listed above it, which is the healthy direction.
25→15 data.fields.head uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.head uses a type in render.fields.
- The types involved
onefetch.data.fields.head.Head→onefetch.render.fields.FieldView
- Direction
- data.fields.head uses render.fields, so a change to render.fields can break data.fields.head, while a change to data.fields.head can't break render.fields.
- Position
- Below the diagonal: data.fields.head uses a module listed above it, which is the healthy direction.
26→8 data.fields.languages uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.languages uses a type in render.style.
- The types involved
onefetch.data.fields.languages.Languages→onefetch.render.style.Line
- Direction
- data.fields.languages uses render.style, so a change to render.style can break data.fields.languages, while a change to data.fields.languages can't break render.style.
- Position
- Below the diagonal: data.fields.languages uses a module listed above it, which is the healthy direction.
26→10 data.fields.languages uses render✕
- Connections
- 1 pair of types, where a type in data.fields.languages uses a type in render.
- The types involved
onefetch.data.fields.languages.Languages→onefetch.render.RenderOptions
- Direction
- data.fields.languages uses render, so a change to render can break data.fields.languages, while a change to data.fields.languages can't break render.
- Position
- Below the diagonal: data.fields.languages uses a module listed above it, which is the healthy direction.
26→15 data.fields.languages uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.languages uses a type in render.fields.
- The types involved
onefetch.data.fields.languages.Languages→onefetch.render.fields.FieldView
- Direction
- data.fields.languages uses render.fields, so a change to render.fields can break data.fields.languages, while a change to data.fields.languages can't break render.fields.
- Position
- Below the diagonal: data.fields.languages uses a module listed above it, which is the healthy direction.
27→3 data.fields.last_change uses data.git.metrics✕
- Connections
- 1 pair of types, where a type in data.fields.last_change uses a type in data.git.metrics.
- The types involved
onefetch.data.fields.last_change.LastChange→onefetch.data.git.metrics.GitMetrics
- Direction
- data.fields.last_change uses data.git.metrics, so a change to data.git.metrics can break data.fields.last_change, while a change to data.fields.last_change can't break data.git.metrics.
- Position
- Below the diagonal: data.fields.last_change uses a module listed above it, which is the healthy direction.
27→8 data.fields.last_change uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.last_change uses a type in render.style.
- The types involved
onefetch.data.fields.last_change.LastChange→onefetch.render.style.Line
- Direction
- data.fields.last_change uses render.style, so a change to render.style can break data.fields.last_change, while a change to data.fields.last_change can't break render.style.
- Position
- Below the diagonal: data.fields.last_change uses a module listed above it, which is the healthy direction.
27→10 data.fields.last_change uses render✕
- Connections
- 1 pair of types, where a type in data.fields.last_change uses a type in render.
- The types involved
onefetch.data.fields.last_change.LastChange→onefetch.render.RenderOptions
- Direction
- data.fields.last_change uses render, so a change to render can break data.fields.last_change, while a change to data.fields.last_change can't break render.
- Position
- Below the diagonal: data.fields.last_change uses a module listed above it, which is the healthy direction.
27→15 data.fields.last_change uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.last_change uses a type in render.fields.
- The types involved
onefetch.data.fields.last_change.LastChange→onefetch.render.fields.FieldView
- Direction
- data.fields.last_change uses render.fields, so a change to render.fields can break data.fields.last_change, while a change to data.fields.last_change can't break render.fields.
- Position
- Below the diagonal: data.fields.last_change uses a module listed above it, which is the healthy direction.
28→4 data.fields.license uses data.manifest✕
- Connections
- 2 pairs of types, where a type in data.fields.license uses a type in data.manifest.
- The types involved
onefetch.data.fields.license.Detector→onefetch.data.manifest.Manifestonefetch.data.fields.license.License→onefetch.data.manifest.Manifest
- Direction
- data.fields.license uses data.manifest, so a change to data.manifest can break data.fields.license, while a change to data.fields.license can't break data.manifest.
- Position
- Below the diagonal: data.fields.license uses a module listed above it, which is the healthy direction.
28→8 data.fields.license uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.license uses a type in render.style.
- The types involved
onefetch.data.fields.license.License→onefetch.render.style.Line
- Direction
- data.fields.license uses render.style, so a change to render.style can break data.fields.license, while a change to data.fields.license can't break render.style.
- Position
- Below the diagonal: data.fields.license uses a module listed above it, which is the healthy direction.
28→10 data.fields.license uses render✕
- Connections
- 1 pair of types, where a type in data.fields.license uses a type in render.
- The types involved
onefetch.data.fields.license.License→onefetch.render.RenderOptions
- Direction
- data.fields.license uses render, so a change to render can break data.fields.license, while a change to data.fields.license can't break render.
- Position
- Below the diagonal: data.fields.license uses a module listed above it, which is the healthy direction.
28→15 data.fields.license uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.license uses a type in render.fields.
- The types involved
onefetch.data.fields.license.License→onefetch.render.fields.FieldView
- Direction
- data.fields.license uses render.fields, so a change to render.fields can break data.fields.license, while a change to data.fields.license can't break render.fields.
- Position
- Below the diagonal: data.fields.license uses a module listed above it, which is the healthy direction.
29→8 data.fields.lines_of_code uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.lines_of_code uses a type in render.style.
- The types involved
onefetch.data.fields.lines_of_code.LinesOfCode→onefetch.render.style.Line
- Direction
- data.fields.lines_of_code uses render.style, so a change to render.style can break data.fields.lines_of_code, while a change to data.fields.lines_of_code can't break render.style.
- Position
- Below the diagonal: data.fields.lines_of_code uses a module listed above it, which is the healthy direction.
29→10 data.fields.lines_of_code uses render✕
- Connections
- 1 pair of types, where a type in data.fields.lines_of_code uses a type in render.
- The types involved
onefetch.data.fields.lines_of_code.LinesOfCode→onefetch.render.RenderOptions
- Direction
- data.fields.lines_of_code uses render, so a change to render can break data.fields.lines_of_code, while a change to data.fields.lines_of_code can't break render.
- Position
- Below the diagonal: data.fields.lines_of_code uses a module listed above it, which is the healthy direction.
29→15 data.fields.lines_of_code uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.lines_of_code uses a type in render.fields.
- The types involved
onefetch.data.fields.lines_of_code.LinesOfCode→onefetch.render.fields.FieldView
- Direction
- data.fields.lines_of_code uses render.fields, so a change to render.fields can break data.fields.lines_of_code, while a change to data.fields.lines_of_code can't break render.fields.
- Position
- Below the diagonal: data.fields.lines_of_code uses a module listed above it, which is the healthy direction.
30→8 data.fields.pending uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.pending uses a type in render.style.
- The types involved
onefetch.data.fields.pending.Pending→onefetch.render.style.Line
- Direction
- data.fields.pending uses render.style, so a change to render.style can break data.fields.pending, while a change to data.fields.pending can't break render.style.
- Position
- Below the diagonal: data.fields.pending uses a module listed above it, which is the healthy direction.
30→10 data.fields.pending uses render✕
- Connections
- 1 pair of types, where a type in data.fields.pending uses a type in render.
- The types involved
onefetch.data.fields.pending.Pending→onefetch.render.RenderOptions
- Direction
- data.fields.pending uses render, so a change to render can break data.fields.pending, while a change to data.fields.pending can't break render.
- Position
- Below the diagonal: data.fields.pending uses a module listed above it, which is the healthy direction.
30→15 data.fields.pending uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.pending uses a type in render.fields.
- The types involved
onefetch.data.fields.pending.Pending→onefetch.render.fields.FieldView
- Direction
- data.fields.pending uses render.fields, so a change to render.fields can break data.fields.pending, while a change to data.fields.pending can't break render.fields.
- Position
- Below the diagonal: data.fields.pending uses a module listed above it, which is the healthy direction.
31→4 data.fields.project uses data.manifest✕
- Connections
- 2 pairs of types, where a type in data.fields.project uses a type in data.manifest.
- The types involved
onefetch.data.fields.project.Project→onefetch.data.manifest.Manifestonefetch.data.fields.project.project$module→onefetch.data.manifest.Manifest
- Direction
- data.fields.project uses data.manifest, so a change to data.manifest can break data.fields.project, while a change to data.fields.project can't break data.manifest.
- Position
- Below the diagonal: data.fields.project uses a module listed above it, which is the healthy direction.
31→8 data.fields.project uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.project uses a type in render.style.
- The types involved
onefetch.data.fields.project.Project→onefetch.render.style.Line
- Direction
- data.fields.project uses render.style, so a change to render.style can break data.fields.project, while a change to data.fields.project can't break render.style.
- Position
- Below the diagonal: data.fields.project uses a module listed above it, which is the healthy direction.
31→10 data.fields.project uses render✕
- Connections
- 1 pair of types, where a type in data.fields.project uses a type in render.
- The types involved
onefetch.data.fields.project.Project→onefetch.render.RenderOptions
- Direction
- data.fields.project uses render, so a change to render can break data.fields.project, while a change to data.fields.project can't break render.
- Position
- Below the diagonal: data.fields.project uses a module listed above it, which is the healthy direction.
31→15 data.fields.project uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.project uses a type in render.fields.
- The types involved
onefetch.data.fields.project.Project→onefetch.render.fields.FieldView
- Direction
- data.fields.project uses render.fields, so a change to render.fields can break data.fields.project, while a change to data.fields.project can't break render.fields.
- Position
- Below the diagonal: data.fields.project uses a module listed above it, which is the healthy direction.
32→8 data.fields.size uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.size uses a type in render.style.
- The types involved
onefetch.data.fields.size.Size→onefetch.render.style.Line
- Direction
- data.fields.size uses render.style, so a change to render.style can break data.fields.size, while a change to data.fields.size can't break render.style.
- Position
- Below the diagonal: data.fields.size uses a module listed above it, which is the healthy direction.
32→10 data.fields.size uses render✕
- Connections
- 1 pair of types, where a type in data.fields.size uses a type in render.
- The types involved
onefetch.data.fields.size.Size→onefetch.render.RenderOptions
- Direction
- data.fields.size uses render, so a change to render can break data.fields.size, while a change to data.fields.size can't break render.
- Position
- Below the diagonal: data.fields.size uses a module listed above it, which is the healthy direction.
32→15 data.fields.size uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.size uses a type in render.fields.
- The types involved
onefetch.data.fields.size.Size→onefetch.render.fields.FieldView
- Direction
- data.fields.size uses render.fields, so a change to render.fields can break data.fields.size, while a change to data.fields.size can't break render.fields.
- Position
- Below the diagonal: data.fields.size uses a module listed above it, which is the healthy direction.
33→8 data.fields.url uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.url uses a type in render.style.
- The types involved
onefetch.data.fields.url.Url→onefetch.render.style.Line
- Direction
- data.fields.url uses render.style, so a change to render.style can break data.fields.url, while a change to data.fields.url can't break render.style.
- Position
- Below the diagonal: data.fields.url uses a module listed above it, which is the healthy direction.
33→10 data.fields.url uses render✕
- Connections
- 1 pair of types, where a type in data.fields.url uses a type in render.
- The types involved
onefetch.data.fields.url.Url→onefetch.render.RenderOptions
- Direction
- data.fields.url uses render, so a change to render can break data.fields.url, while a change to data.fields.url can't break render.
- Position
- Below the diagonal: data.fields.url uses a module listed above it, which is the healthy direction.
33→15 data.fields.url uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.url uses a type in render.fields.
- The types involved
onefetch.data.fields.url.Url→onefetch.render.fields.FieldView
- Direction
- data.fields.url uses render.fields, so a change to render.fields can break data.fields.url, while a change to data.fields.url can't break render.fields.
- Position
- Below the diagonal: data.fields.url uses a module listed above it, which is the healthy direction.
34→4 data.fields.version uses data.manifest✕
- Connections
- 2 pairs of types, where a type in data.fields.version uses a type in data.manifest.
- The types involved
onefetch.data.fields.version.Version→onefetch.data.manifest.Manifestonefetch.data.fields.version.version$module→onefetch.data.manifest.Manifest
- Direction
- data.fields.version uses data.manifest, so a change to data.manifest can break data.fields.version, while a change to data.fields.version can't break data.manifest.
- Position
- Below the diagonal: data.fields.version uses a module listed above it, which is the healthy direction.
34→8 data.fields.version uses render.style✕
- Connections
- 1 pair of types, where a type in data.fields.version uses a type in render.style.
- The types involved
onefetch.data.fields.version.Version→onefetch.render.style.Line
- Direction
- data.fields.version uses render.style, so a change to render.style can break data.fields.version, while a change to data.fields.version can't break render.style.
- Position
- Below the diagonal: data.fields.version uses a module listed above it, which is the healthy direction.
34→10 data.fields.version uses render✕
- Connections
- 1 pair of types, where a type in data.fields.version uses a type in render.
- The types involved
onefetch.data.fields.version.Version→onefetch.render.RenderOptions
- Direction
- data.fields.version uses render, so a change to render can break data.fields.version, while a change to data.fields.version can't break render.
- Position
- Below the diagonal: data.fields.version uses a module listed above it, which is the healthy direction.
34→15 data.fields.version uses render.fields✕
- Connections
- 1 pair of types, where a type in data.fields.version uses a type in render.fields.
- The types involved
onefetch.data.fields.version.Version→onefetch.render.fields.FieldView
- Direction
- data.fields.version uses render.fields, so a change to render.fields can break data.fields.version, while a change to data.fields.version can't break render.fields.
- Position
- Below the diagonal: data.fields.version uses a module listed above it, which is the healthy direction.
35→13 options uses cli✕
- Connections
- 1 pair of types, where a type in options uses a type in cli.
- The types involved
onefetch.options.options$module→onefetch.cli.When
- Direction
- options uses cli, so a change to cli can break options, while a change to options can't break cli.
- Position
- Below the diagonal: options uses a module listed above it, which is the healthy direction.
36→1 data.builder uses data.fields✕
- Connections
- 2 pairs of types, where a type in data.builder uses a type in data.fields.
- The types involved
onefetch.data.builder.InfoBuilder→onefetch.data.fields.Fieldonefetch.data.builder.InfoBuilder→onefetch.data.fields.FieldKind
- Direction
- data.builder uses data.fields, so a change to data.fields can break data.builder, while a change to data.builder can't break data.fields.
- Position
- Below the diagonal: data.builder uses a module listed above it, which is the healthy direction.
36→3 data.builder uses data.git.metrics✕
- Connections
- 1 pair of types, where a type in data.builder uses a type in data.git.metrics.
- The types involved
onefetch.data.builder.InfoBuilder→onefetch.data.git.metrics.GitMetrics
- Direction
- data.builder uses data.git.metrics, so a change to data.git.metrics can break data.builder, while a change to data.builder can't break data.git.metrics.
- Position
- Below the diagonal: data.builder uses a module listed above it, which is the healthy direction.
36→4 data.builder uses data.manifest✕
- Connections
- 1 pair of types, where a type in data.builder uses a type in data.manifest.
- The types involved
onefetch.data.builder.InfoBuilder→onefetch.data.manifest.Manifest
- Direction
- data.builder uses data.manifest, so a change to data.manifest can break data.builder, while a change to data.builder can't break data.manifest.
- Position
- Below the diagonal: data.builder uses a module listed above it, which is the healthy direction.
36→5 data.builder uses data.title✕
- Connections
- 1 pair of types, where a type in data.builder uses a type in data.title.
- The types involved
onefetch.data.builder.InfoBuilder→onefetch.data.title.Title
- Direction
- data.builder uses data.title, so a change to data.title can break data.builder, while a change to data.builder can't break data.title.
- Position
- Below the diagonal: data.builder uses a module listed above it, which is the healthy direction.
36→16 data.builder uses data✕
- Connections
- 2 pairs of types, where a type in data.builder uses a type in data.
- The types involved
onefetch.data.builder.InfoBuilder→onefetch.data.Infoonefetch.data.builder.InfoBuilder→onefetch.data.InfoOptions
- Direction
- data.builder uses data, so a change to data can break data.builder, while a change to data.builder can't break data.
- Position
- Below the diagonal: data.builder uses a module listed above it, which is the healthy direction.
37→26 data.loc uses data.fields.languages✕
- Connections
- 1 pair of types, where a type in data.loc uses a type in data.fields.languages.
- The types involved
onefetch.data.loc.loc$module→onefetch.data.fields.languages.Languages
- Direction
- data.loc uses data.fields.languages, so a change to data.fields.languages can break data.loc, while a change to data.loc can't break data.fields.languages.
- Position
- Below the diagonal: data.loc uses a module listed above it, which is the healthy direction.
38→8 render.fields.languages uses render.style✕
- Connections
- 2 pairs of types, where a type in render.fields.languages uses a type in render.style.
- The types involved
onefetch.render.fields.languages.LanguageDisplayData→onefetch.render.style.LanguageEntryonefetch.render.fields.languages.languages$module→onefetch.render.style.Line
- Direction
- render.fields.languages uses render.style, so a change to render.style can break render.fields.languages, while a change to render.fields.languages can't break render.style.
- Position
- Below the diagonal: render.fields.languages uses a module listed above it, which is the healthy direction.
38→10 render.fields.languages uses render✕
- Connections
- 1 pair of types, where a type in render.fields.languages uses a type in render.
- The types involved
onefetch.render.fields.languages.languages$module→onefetch.render.RenderOptions
- Direction
- render.fields.languages uses render, so a change to render can break render.fields.languages, while a change to render.fields.languages can't break render.
- Position
- Below the diagonal: render.fields.languages uses a module listed above it, which is the healthy direction.
38→26 render.fields.languages uses data.fields.languages✕
- Connections
- 1 pair of types, where a type in render.fields.languages uses a type in data.fields.languages.
- The types involved
onefetch.render.fields.languages.languages$module→onefetch.data.fields.languages.Languages
- Direction
- render.fields.languages uses data.fields.languages, so a change to data.fields.languages can break render.fields.languages, while a change to render.fields.languages can't break data.fields.languages.
- Position
- Below the diagonal: render.fields.languages uses a module listed above it, which is the healthy direction.
39→5 render.info uses data.title✕
- Connections
- 1 pair of types, where a type in render.info uses a type in data.title.
- The types involved
onefetch.render.info.info$module→onefetch.data.title.Title
- Direction
- render.info uses data.title, so a change to data.title can break render.info, while a change to render.info can't break data.title.
- Position
- Below the diagonal: render.info uses a module listed above it, which is the healthy direction.
39→8 render.info uses render.style✕
- Connections
- 1 pair of types, where a type in render.info uses a type in render.style.
- The types involved
onefetch.render.info.info$module→onefetch.render.style.Line
- Direction
- render.info uses render.style, so a change to render.style can break render.info, while a change to render.info can't break render.style.
- Position
- Below the diagonal: render.info uses a module listed above it, which is the healthy direction.
39→10 render.info uses render✕
- Connections
- 1 pair of types, where a type in render.info uses a type in render.
- The types involved
onefetch.render.info.info$module→onefetch.render.RenderOptions
- Direction
- render.info uses render, so a change to render can break render.info, while a change to render.info can't break render.
- Position
- Below the diagonal: render.info uses a module listed above it, which is the healthy direction.
39→16 render.info uses data✕
- Connections
- 1 pair of types, where a type in render.info uses a type in data.
- The types involved
onefetch.render.info.info$module→onefetch.data.Info
- Direction
- render.info uses data, so a change to data can break render.info, while a change to render.info can't break data.
- Position
- Below the diagonal: render.info uses a module listed above it, which is the healthy direction.
40→8 render.printer uses render.style✕
- Connections
- 2 pairs of types, where a type in render.printer uses a type in render.style.
- The types involved
onefetch.render.printer.printer$module→onefetch.render.style.Lineonefetch.render.printer.printer$module→onefetch.render.style.Segment
- Direction
- render.printer uses render.style, so a change to render.style can break render.printer, while a change to render.printer can't break render.style.
- Position
- Below the diagonal: render.printer uses a module listed above it, which is the healthy direction.
40→10 render.printer uses render✕
- Connections
- 2 pairs of types, where a type in render.printer uses a type in render.
- The types involved
onefetch.render.printer.Printer→onefetch.render.RenderOptionsonefetch.render.printer.PrinterKind→onefetch.render.RenderOptions
- Direction
- render.printer uses render, so a change to render can break render.printer, while a change to render.printer can't break render.
- Position
- Below the diagonal: render.printer uses a module listed above it, which is the healthy direction.
40→11 render.printer uses render.ascii✕
- Connections
- 1 pair of types, where a type in render.printer uses a type in render.ascii.
- The types involved
onefetch.render.printer.printer$module→onefetch.render.ascii.AsciiArt
- Direction
- render.printer uses render.ascii, so a change to render.ascii can break render.printer, while a change to render.printer can't break render.ascii.
- Position
- Below the diagonal: render.printer uses a module listed above it, which is the healthy direction.
40→14 render.printer uses render.colors✕
- Connections
- 2 pairs of types, where a type in render.printer uses a type in render.colors.
- The types involved
onefetch.render.printer.Printer→onefetch.render.colors.Colorsonefetch.render.printer.printer$module→onefetch.render.colors.Colors
- Direction
- render.printer uses render.colors, so a change to render.colors can break render.printer, while a change to render.printer can't break render.colors.
- Position
- Below the diagonal: render.printer uses a module listed above it, which is the healthy direction.
40→16 render.printer uses data✕
- Connections
- 1 pair of types, where a type in render.printer uses a type in data.
- The types involved
onefetch.render.printer.Printer→onefetch.data.Info
- Direction
- render.printer uses data, so a change to data can break render.printer, while a change to render.printer can't break data.
- Position
- Below the diagonal: render.printer uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 32 | High / Critical |
| A05:2025 — Injection | 15 | High / Critical |
Roadmap
First, implement structured observability by adopting tracing with JSON output and logging at key points in your binaries to address the current lack of metrics and health checks. Next, resolve the absence of Architecture Decision Records by documenting significant design choices in a dedicated folder, ensuring each entry captures the date, context, decision, and consequences. Finally, mitigate off-boarding risks by clarifying bus factor dependencies and update the README to include a clear section on how to run the test suite.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.4 pts | Low | ADR Quality |
| Adopt `tracing` with `tracing-subscriber` (JSON output) and log at meaningful points in the binaries you run. | +2.4 pts | Medium | Observability |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.9 pts | Low | Bus Factor |
| 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. | +1.3 pts | Medium | Architecture documentation |
| 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. | +0.6 pts | Medium | Documentation (README) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +0.3 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +0.3 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.3 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/render/image/sixel.rs | 7.8 | Mixed | Cognitive Complexity: SixelBackend::add_image (cognitive 17) |
| src/render/image/iterm.rs | 7.8 | Mixed | Code Duplication: Duplicated block (11 lines × 2) |
| src/data/mod.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/render/image/kitty.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (12 lines × 2) |
| src/render/ascii.rs | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Tokens (LCOM4 4) |
| REDACTED | 9.3 | Near-clean | Dependency Vulnerabilities: Low CVE: REDACTED |
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. 66 of 66 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 — 66 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, 54 of 67 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D14 License Compliance — 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. This repository declares REDACTED, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AXR1 Runtime accessibility — 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. Render strategy: boot via DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- 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 this repository's Rust is most of its product and 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 this repository's Rust is most of its product and 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.
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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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
0 function(s) exceeded the cyclomatic complexity threshold of 15. A further 3 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Field::serialize at 18 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/data/fields/mod.rs (Field::serialize at 18), src/render/fields/mod.rs (onefetch::render::fields::view at 18), src/render/colors.rs (onefetch::render::colors::num_to_color at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
D2 · Cognitive Complexity
2 function(s) exceeded the cognitive complexity threshold of 15; the worst was SixelBackend::add_image at 17.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with SixelBackend::add_image (cognitive 17), SixelBackend::supported (cognitive 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- 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
0 god class(es) detected.
D4 · Code Duplication
3 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with kitty.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 iterm.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (10 lines × 3) finding(s) in Code Duplication — start with iterm.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)
1 of 20 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ascii.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
131 test methods: 119 unit, 12 integration, 0 BDD, 0 e2e. The Rust suite contributes 131 `#[test]` function(s) across 41 file(s) declaring at least one; its unit/integration split is Cargo's own — 2 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, 41 test files): measured (0 flaky).
D12 · Dependency Hygiene
2 outdated, 0 yanked direct Cargo dependencies. 27 of 31 direct crates were graded against crates.io (0 not published there, 4 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 388 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares REDACTED, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: src/data/fields/mod.rs (3×18=54)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/render/ascii.rs. Counted over 24 of the 68 production source files in this repository: 43 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
1 deducted task-comment markers across 5563 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with mod.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. 10 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)
15 finding(s): 0 critical, 15 high, 0 medium, 0 low. 10 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. semgrep hit a parse error in 1 file(s) — `languages.yaml` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
23 finding(s): 0 critical, 2 high, 19 medium, 2 low.
What to do
- Resolve the 10 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 5 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 25 of the 68 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- 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).
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
AC2 · Forms & labels
AC3 · Page structure
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — site/src/routes/+page.svelte:89
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 3 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Accessibility linting is already configured — assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- `npm run check:prettier` invokes prettier in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — REDACTED:41
What to do
- Add `--check` to the prettier step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 67 Rust production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (Rust: the log and tracing crates (info!/warn!/error!, #[instrument]), slog, env_logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt `tracing` with `tracing-subscriber` (JSON output) and log at meaningful points in the binaries you run.
- Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF1 · Benchmark discipline
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `vercel.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — site/vercel.json:1
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
- Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 73% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 86% | Strong | Strongest area. |
| Maturity | 69% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 67% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 72% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 73% | Strong | Solid. |
| Performance | 80% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 53 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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 — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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 — ~297 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, TypeScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rb, .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 (3 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Ruby, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Ruby and Rust were read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter; 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.
- 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 Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 35 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- SixelBackend::add_image (cognitive 17) src/render/image/sixel.rs:68
- SixelBackend::supported (cognitive 16) src/render/image/sixel.rs:19
- REDACTED
- REDACTED
- Heading level jumps from h1 to h3 site/src/routes/+page.svelte:89
- Hotspot: src/data/fields/mod.rs src/data/fields/mod.rs:89
- TodoComment src/data/mod.rs:57
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2) src/render/image/kitty.rs:17
- Duplicated block (11 lines × 2) src/render/image/iterm.rs:25
- Duplicated block (10 lines × 3) src/render/image/iterm.rs:47
- Low cohesion: Tokens (LCOM4 4) src/render/ascii.rs:127
- CI formatting step cannot fail REDACTED:41
- No structured logging
Minor — 13 finding(s)
- REDACTED
- REDACTED
- Accessibility enforcement below the top rung
- Off-boarding risk: anonymized user #1
- No ADRs found
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No security response headers detected site/vercel.json:1
- Ruby's type checker does not check nil everywhere
- Silent fallback default on Err src/data/title.rs:32
Minor — 2 finding(s)
- Outdated: rustix
- Outdated: serde_json
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-744328b05bfc4329af810e7cd7109961/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-744328b05bfc4329af810e7cd7109961/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 --exclude site . | 15 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 23 | artifacts/raw/trivy-fs.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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |