Executive summary
AngelMunoz/Navs falls short of our standard for production, held back most by its Maturity lens, the way the project is documented and understood. It scores 67 out of 100 and is rated Adequate, and 14 of its 18 critical findings are security problems in the build pipeline and in the packages it uses.
Maturity, at 60, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing each deprecated dependency, worth about 3 points. Recording design decisions would lift Maturity itself, worth about 6 points. Raising Maturity to 70 would lift the score to about 70.
Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One known security hole in a package the code depends on can be used by attackers, and one secret can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting the secret to its own step would close these risks. The four sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 4,001 lines, about €7,700 to rebuild.
If Maturity rose from 60 to 70, the lowest score rated Strong, the score would rise from 67 to about 70.
New since the last survey: 4 findings
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/Navs.Avalonia/Library.fs
- Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) src/UrlTemplates.CSharp/RouteMatcher.cs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/UrlTemplates.CSharp/RouteMatcher.cs
- Code Duplication · Edited copy of a member (23 corresponding lines) samples/GooSample/About.fs
Fixed since the last survey: 2 findings
- Code Duplication · Duplicated block (25–26 lines × 2) src/Navs/Types.fs
- Code Duplication · Duplicated block (11 lines × 2) src/Navs/Types.fs
Rebuild cost: about €7,700 · Estimate
| Cost to rebuild | €2,500 to €13,000, for 42 to 135 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 67. 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: 4,001 lines of product code |
| Comment lines | The estimate prices 3,944 lines. Comment lines count towards the size of 4,001 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Navs.CSharp | 2 UrlTemplates.CSharp | 3 UrlTemplates.Parser.Common | 4 UrlTemplates.Parser.Report | 5 UrlTemplates.UrlParser | 6 UrlTemplates.UrlTemplate | 7 UrlTemplates.RouteMatcher | 8 UrlTemplates.UrlParser.UrlParser | 9 UrlTemplates.UrlTemplate.UrlTemplateModule | 10 Navs | 11 UrlTemplates.RouteMatcher.RouteMatcher | 12 UrlTemplates.RouteMatcher.UrlMatchModule | 13 Navs.Avalonia | 14 Navs.FuncUI | 15 Navs.FuncUI.DSL | 16 Navs.Goo | 17 Navs.RouteModule | 18 Navs.Router | 19 Navs.Terminal.Gui |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Navs.CSharp | |||||||||||||||||||
| 2 UrlTemplates.CSharp | |||||||||||||||||||
| 3 UrlTemplates.Parser.Common | |||||||||||||||||||
| 4 UrlTemplates.Parser.Report | |||||||||||||||||||
| 5 UrlTemplates.UrlParser | |||||||||||||||||||
| 6 UrlTemplates.UrlTemplate | |||||||||||||||||||
| 7 UrlTemplates.RouteMatcher | 2 | ||||||||||||||||||
| 8 UrlTemplates.UrlParser.UrlParser | 1 | ||||||||||||||||||
| 9 UrlTemplates.UrlTemplate.UrlTemplateModule | 1 | ||||||||||||||||||
| 10 Navs | 1 | 1 | |||||||||||||||||
| 11 UrlTemplates.RouteMatcher.RouteMatcher | 1 | 1 | 3 | ||||||||||||||||
| 12 UrlTemplates.RouteMatcher.UrlMatchModule | 1 | ||||||||||||||||||
| 13 Navs.Avalonia | 6 | ||||||||||||||||||
| 14 Navs.FuncUI | 6 | ||||||||||||||||||
| 15 Navs.FuncUI.DSL | 1 | ||||||||||||||||||
| 16 Navs.Goo | 3 | ||||||||||||||||||
| 17 Navs.RouteModule | 3 | ||||||||||||||||||
| 18 Navs.Router | 5 | ||||||||||||||||||
| 19 Navs.Terminal.Gui | 6 |
7→6 UrlTemplates.RouteMatcher uses UrlTemplates.UrlTemplate✕
- Connections
- 2 pairs of types, where a type in UrlTemplates.RouteMatcher uses a type in UrlTemplates.UrlTemplate.
- The types involved
UrlTemplates.RouteMatcher.MatchingError→UrlTemplates.UrlTemplate.TypedParamUrlTemplates.RouteMatcher.QueryParamError→UrlTemplates.UrlTemplate.TypedParam
- Direction
- UrlTemplates.RouteMatcher uses UrlTemplates.UrlTemplate, so a change to UrlTemplates.UrlTemplate can break UrlTemplates.RouteMatcher, while a change to UrlTemplates.RouteMatcher can't break UrlTemplates.UrlTemplate.
- Position
- Below the diagonal: UrlTemplates.RouteMatcher uses a module listed above it, which is the healthy direction.
8→5 UrlTemplates.UrlParser.UrlParser uses UrlTemplates.UrlParser✕
- Connections
- 1 pair of types, where a type in UrlTemplates.UrlParser.UrlParser uses a type in UrlTemplates.UrlParser.
- The types involved
UrlTemplates.UrlParser.UrlParser.UrlParser→UrlTemplates.UrlParser.UrlInfo
- Direction
- UrlTemplates.UrlParser.UrlParser uses UrlTemplates.UrlParser, so a change to UrlTemplates.UrlParser can break UrlTemplates.UrlParser.UrlParser, while a change to UrlTemplates.UrlParser.UrlParser can't break UrlTemplates.UrlParser.
- Position
- Below the diagonal: UrlTemplates.UrlParser.UrlParser uses a module listed above it, which is the healthy direction.
9→6 UrlTemplates.UrlTemplate.UrlTemplateModule uses UrlTemplates.UrlTemplate✕
- Connections
- 1 pair of types, where a type in UrlTemplates.UrlTemplate.UrlTemplateModule uses a type in UrlTemplates.UrlTemplate.
- The types involved
UrlTemplates.UrlTemplate.UrlTemplateModule.UrlTemplateModule→UrlTemplates.UrlTemplate.UrlTemplate
- Direction
- UrlTemplates.UrlTemplate.UrlTemplateModule uses UrlTemplates.UrlTemplate, so a change to UrlTemplates.UrlTemplate can break UrlTemplates.UrlTemplate.UrlTemplateModule, while a change to UrlTemplates.UrlTemplate.UrlTemplateModule can't break UrlTemplates.UrlTemplate.
- Position
- Below the diagonal: UrlTemplates.UrlTemplate.UrlTemplateModule uses a module listed above it, which is the healthy direction.
10→5 Navs uses UrlTemplates.UrlParser✕
- Connections
- 1 pair of types, where a type in Navs uses a type in UrlTemplates.UrlParser.
- The types involved
Navs.RouteContext→UrlTemplates.UrlParser.UrlInfo
- Direction
- Navs uses UrlTemplates.UrlParser, so a change to UrlTemplates.UrlParser can break Navs, while a change to Navs can't break UrlTemplates.UrlParser.
- Position
- Below the diagonal: Navs uses a module listed above it, which is the healthy direction.
10→7 Navs uses UrlTemplates.RouteMatcher✕
- Connections
- 1 pair of types, where a type in Navs uses a type in UrlTemplates.RouteMatcher.
- The types involved
Navs.RouteContext→UrlTemplates.RouteMatcher.UrlMatch
- Direction
- Navs uses UrlTemplates.RouteMatcher, so a change to UrlTemplates.RouteMatcher can break Navs, while a change to Navs can't break UrlTemplates.RouteMatcher.
- Position
- Below the diagonal: Navs uses a module listed above it, which is the healthy direction.
11→5 UrlTemplates.RouteMatcher.RouteMatcher uses UrlTemplates.UrlParser✕
- Connections
- 1 pair of types, where a type in UrlTemplates.RouteMatcher.RouteMatcher uses a type in UrlTemplates.UrlParser.
- The types involved
UrlTemplates.RouteMatcher.RouteMatcher.RouteMatcher→UrlTemplates.UrlParser.UrlInfo
- Direction
- UrlTemplates.RouteMatcher.RouteMatcher uses UrlTemplates.UrlParser, so a change to UrlTemplates.UrlParser can break UrlTemplates.RouteMatcher.RouteMatcher, while a change to UrlTemplates.RouteMatcher.RouteMatcher can't break UrlTemplates.UrlParser.
- Position
- Below the diagonal: UrlTemplates.RouteMatcher.RouteMatcher uses a module listed above it, which is the healthy direction.
11→6 UrlTemplates.RouteMatcher.RouteMatcher uses UrlTemplates.UrlTemplate✕
- Connections
- 1 pair of types, where a type in UrlTemplates.RouteMatcher.RouteMatcher uses a type in UrlTemplates.UrlTemplate.
- The types involved
UrlTemplates.RouteMatcher.RouteMatcher.RouteMatcher→UrlTemplates.UrlTemplate.UrlTemplate
- Direction
- UrlTemplates.RouteMatcher.RouteMatcher uses UrlTemplates.UrlTemplate, so a change to UrlTemplates.UrlTemplate can break UrlTemplates.RouteMatcher.RouteMatcher, while a change to UrlTemplates.RouteMatcher.RouteMatcher can't break UrlTemplates.UrlTemplate.
- Position
- Below the diagonal: UrlTemplates.RouteMatcher.RouteMatcher uses a module listed above it, which is the healthy direction.
11→7 UrlTemplates.RouteMatcher.RouteMatcher uses UrlTemplates.RouteMatcher✕
- Connections
- 3 pairs of types, where a type in UrlTemplates.RouteMatcher.RouteMatcher uses a type in UrlTemplates.RouteMatcher.
- The types involved
UrlTemplates.RouteMatcher.RouteMatcher.RouteMatcher→UrlTemplates.RouteMatcher.MatchingErrorUrlTemplates.RouteMatcher.RouteMatcher.RouteMatcher→UrlTemplates.RouteMatcher.StringMatchErrorUrlTemplates.RouteMatcher.RouteMatcher.RouteMatcher→UrlTemplates.RouteMatcher.UrlMatch
- Direction
- UrlTemplates.RouteMatcher.RouteMatcher uses UrlTemplates.RouteMatcher, so a change to UrlTemplates.RouteMatcher can break UrlTemplates.RouteMatcher.RouteMatcher, while a change to UrlTemplates.RouteMatcher.RouteMatcher can't break UrlTemplates.RouteMatcher.
- Position
- Below the diagonal: UrlTemplates.RouteMatcher.RouteMatcher uses a module listed above it, which is the healthy direction.
12→7 UrlTemplates.RouteMatcher.UrlMatchModule uses UrlTemplates.RouteMatcher✕
- Connections
- 1 pair of types, where a type in UrlTemplates.RouteMatcher.UrlMatchModule uses a type in UrlTemplates.RouteMatcher.
- The types involved
UrlTemplates.RouteMatcher.UrlMatchModule.UrlMatchModule→UrlTemplates.RouteMatcher.UrlMatch
- Direction
- UrlTemplates.RouteMatcher.UrlMatchModule uses UrlTemplates.RouteMatcher, so a change to UrlTemplates.RouteMatcher can break UrlTemplates.RouteMatcher.UrlMatchModule, while a change to UrlTemplates.RouteMatcher.UrlMatchModule can't break UrlTemplates.RouteMatcher.
- Position
- Below the diagonal: UrlTemplates.RouteMatcher.UrlMatchModule uses a module listed above it, which is the healthy direction.
13→10 Navs.Avalonia uses Navs✕
- Connections
- 6 pairs of types, where a type in Navs.Avalonia uses a type in Navs.
- The types involved
Navs.Avalonia.AvaloniaRouter→Navs.IHistoryNavs.Avalonia.AvaloniaRouter→Navs.IRouteLinksNavs.Avalonia.AvaloniaRouter→Navs.IRouter`1Navs.Avalonia.AvaloniaRouter→Navs.RouteDefinition`1Navs.Avalonia.AvaloniaRouter→Navs.RouterSnapshot`1Navs.Avalonia.RouterOutlet→Navs.IRouter`1
- Direction
- Navs.Avalonia uses Navs, so a change to Navs can break Navs.Avalonia, while a change to Navs.Avalonia can't break Navs.
- Position
- Below the diagonal: Navs.Avalonia uses a module listed above it, which is the healthy direction.
14→10 Navs.FuncUI uses Navs✕
- Connections
- 6 pairs of types, where a type in Navs.FuncUI uses a type in Navs.
- The types involved
Navs.FuncUI.FuncUIRouter→Navs.IHistoryNavs.FuncUI.FuncUIRouter→Navs.IRouteLinksNavs.FuncUI.FuncUIRouter→Navs.IRouter`1Navs.FuncUI.FuncUIRouter→Navs.RouteDefinition`1Navs.FuncUI.FuncUIRouter→Navs.RouterSnapshot`1Navs.FuncUI.IComponentContextExtensions→Navs.IRouter`1
- Direction
- Navs.FuncUI uses Navs, so a change to Navs can break Navs.FuncUI, while a change to Navs.FuncUI can't break Navs.
- Position
- Below the diagonal: Navs.FuncUI uses a module listed above it, which is the healthy direction.
15→10 Navs.FuncUI.DSL uses Navs✕
- Connections
- 1 pair of types, where a type in Navs.FuncUI.DSL uses a type in Navs.
- The types involved
Navs.FuncUI.DSL.RouterOutlet→Navs.IRouter`1
- Direction
- Navs.FuncUI.DSL uses Navs, so a change to Navs can break Navs.FuncUI.DSL, while a change to Navs.FuncUI.DSL can't break Navs.
- Position
- Below the diagonal: Navs.FuncUI.DSL uses a module listed above it, which is the healthy direction.
16→10 Navs.Goo uses Navs✕
- Connections
- 3 pairs of types, where a type in Navs.Goo uses a type in Navs.
- The types involved
Navs.Goo.GooRouter→Navs.IRouter`1Navs.Goo.GooRouter→Navs.RouteDefinition`1Navs.Goo.RouterOutlet→Navs.IRouter`1
- Direction
- Navs.Goo uses Navs, so a change to Navs can break Navs.Goo, while a change to Navs.Goo can't break Navs.
- Position
- Below the diagonal: Navs.Goo uses a module listed above it, which is the healthy direction.
17→10 Navs.RouteModule uses Navs✕
- Connections
- 3 pairs of types, where a type in Navs.RouteModule uses a type in Navs.
- The types involved
Navs.RouteModule.RouteModule→Navs.CachePolicyNavs.RouteModule.RouteModule→Navs.NavigationTargetNavs.RouteModule.RouteModule→Navs.RouteDefinition`1
- Direction
- Navs.RouteModule uses Navs, so a change to Navs can break Navs.RouteModule, while a change to Navs.RouteModule can't break Navs.
- Position
- Below the diagonal: Navs.RouteModule uses a module listed above it, which is the healthy direction.
18→10 Navs.Router uses Navs✕
- Connections
- 5 pairs of types, where a type in Navs.Router uses a type in Navs.
- The types involved
Navs.Router.InMemoryHistory→Navs.IHistoryStoreNavs.Router.Router→Navs.IRouter`1Navs.Router.Router→Navs.RouteDefinition`1Navs.Router.Router→Navs.RouteTableErrorNavs.Router.Router→Navs.RouterConfig`1
- Direction
- Navs.Router uses Navs, so a change to Navs can break Navs.Router, while a change to Navs.Router can't break Navs.
- Position
- Below the diagonal: Navs.Router uses a module listed above it, which is the healthy direction.
19→10 Navs.Terminal.Gui uses Navs✕
- Connections
- 6 pairs of types, where a type in Navs.Terminal.Gui uses a type in Navs.
- The types involved
Navs.Terminal.Gui.RouterOutlet→Navs.IRouter`1Navs.Terminal.Gui.TerminalGuiRouter→Navs.IHistoryNavs.Terminal.Gui.TerminalGuiRouter→Navs.IRouteLinksNavs.Terminal.Gui.TerminalGuiRouter→Navs.IRouter`1Navs.Terminal.Gui.TerminalGuiRouter→Navs.RouteDefinition`1Navs.Terminal.Gui.TerminalGuiRouter→Navs.RouterSnapshot`1
- Direction
- Navs.Terminal.Gui uses Navs, so a change to Navs can break Navs.Terminal.Gui, while a change to Navs.Terminal.Gui can't break Navs.
- Position
- Below the diagonal: Navs.Terminal.Gui uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 15 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | Medium |
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Add a build/run (quick start) section to the root README — the first thing a newcomer needs; Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props. | +3.3 pts | Low | Dependency Hygiene |
| 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. | +5.6 pts | Medium | Architecture documentation |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +3.3 pts | Medium | Documentation (README) |
| Resolve the 4 NoWarnInCsproj finding(s) in Explicit Debt — start with Navs.CSharp.csproj, Navs.CSharp.Tests.csproj, UrlTemplates.CSharp.csproj. | +1.4 pts | Low | Explicit Debt |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.5 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.4 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +0.4 pts | Low | Dependency Vulnerabilities |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +0.3 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/Navs.Avalonia/Library.fs | 7.4 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| src/Navs.CSharp/Navs.CSharp.csproj | 7.6 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/Navs.CSharp.Tests/Navs.CSharp.Tests.csproj | 7.6 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/UrlTemplates.CSharp/UrlTemplates.CSharp.csproj | 7.6 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/UrlTemplates.CSharp.Tests/UrlTemplates.CSharp.Tests.csproj | 7.6 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/UrlTemplates.CSharp/RouteMatcher.cs | 7.8 | Mixed | Code Duplication: Edited copies of one member (3 members, 17+ corresponding lines) |
| src/Navs.CSharp/TypedParameters.cs | 7.8 | Mixed | Code Duplication: Duplicated block (15 lines × 2) |
| samples/NxuiDeclarative/Program.fs | 7.8 | Mixed | Code Duplication: Duplicated block (36 lines × 2) |
| src/UrlTemplates/UrlTemplate.fs | 8.5 | Near-clean | Cyclomatic Complexity: UrlTemplateModule.toUrl (cyclomatic 16) |
| src/Navs/Router.fs | 8.5 | Near-clean | God Classes: FileTooLong: Navs/Router.fs |
| samples/GooSample/About.fs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (23 corresponding lines) |
| src/Directory.Packages.props | 8.5 | Near-clean | Dependency Hygiene: Deprecated: xunit |
| REDACTED | 9.0 | Near-clean | IaC & Container Security: Low IaC: 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
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 41 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 41 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 40 of 66 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 27 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 10 test source file(s) (.fs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D16 Bus Factor — 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. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 197 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/Navs.Adapters.Tests/Navs.Adapters.Tests.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 4 deducted marker(s) and the 1.4/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (3,096 lines, 77% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 0.329 chown: cannot access '/home/vscode/.dotnet': No such file or directory ------ REDACTED:8 -------------------- 6 | ENV PATH=$PATH:$DOTNET_ROOT:$DOTNET_ROOT/tools 7 | 8 | >>> RUN chown -R vscode:vscode $DOTNET_ROOT 9 | -------------------- ERROR: failed to solve: process "/bin/sh -c chown -R vscode:vscode $DOTNET_ROOT" did not complete successfully: exit code: 1; runtime evidence skipped.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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 REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was UrlTemplateModule.toUrl at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with UrlTemplateModule.toUrl (cyclomatic 16). — Refactoring it lifts Cyclomatic Complexity from 9.9 to about 10.0/10.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with Router.fs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
6 duplicated block group(s) detected. 8.6 % of the production lines (344 of 4,001) are in a reported copy. A further 6 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 3 of the 12 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with Library.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copies of one member (3 members, 17+ corresponding lines) finding(s) in Code Duplication — start with RouteMatcher.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (16 corresponding lines) finding(s) in Code Duplication — start with RouteMatcher.cs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
7 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 4 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 81.8%.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 27 tests. Measured on the C# suite only — at least 10 test source file(s) (.fs) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 · Dependency Hygiene
17 outdated, 0 vulnerable, 1 deprecated packages.
What to do
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 200 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 23 direct `PackageReference`(s), and 182 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
4 deducted debt markers + unmeasured dead symbols across 905 LoC in the .NET projects (1.4/KLoC) → score 7.2. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (77% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 4 NoWarnInCsproj finding(s) in Explicit Debt — start with Navs.CSharp.csproj, Navs.CSharp.Tests.csproj, UrlTemplates.CSharp.csproj. — One of this dimension's main actionable groups (4 issue-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 9 document(s) read across 3 unit(s).
D26 · Project Cohesion
0 of 5 projects flagged as possibly oversized/incoherent.
D27 · Navigability
91 % of calls cross a namespace and 7 % go through an interface, but 38 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
15 finding(s): 0 critical, 13 high, 2 medium, 0 low. 12 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 12 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (12 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 0 high, 0 medium, 2 low.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 13 of the 20 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. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 21 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:10
- `src/Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/Directory.Packages.props:7
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
X5 · Nullable reference types
- ~1.6 `!` suppressions per 1k syntax nodes — 7 suppression(s) across the 4302 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81% | Strong | Solid. |
| Architecture | 98% | Exemplary | Solid. |
| Maturity | 60% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 62% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 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 — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — AX6 reached only 23% of this repository's production lines — fsharp (3,096 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 0.329 chown: cannot access '/home/vscode/.dotnet': No such file or directory ------ REDACTED:8 -------------------- 6 | ENV PATH=$PATH:$DOTNET_ROOT:$DOTNET_ROOT/tools 7 | 8 | >>> RUN chown -R vscode:vscode $DOTNET_ROOT 9 | -------------------- ERROR: failed to solve: process "/bin/sh -c chown -R vscode:vscode $DOTNET_ROOT" did not complete successfully: exit code: 1; runtime evidence skipped 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 the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, 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 the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (860 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (4,001 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 12 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- 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
- IC1 Incompleteness & stubs — IC1 reached only 23% of this repository's production lines — fsharp (3,096 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- M4 Documentation accuracy — Not applicable: the 9 current-state document(s) make no claim of a kind M4 checks.
- 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'.
- P2 Observability — This repository's F# source (6 module(s), 10 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage data present for 19 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — X1 reached only 23% of this repository's production lines — fsharp (3,096 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X12 Unreachable branch — X12 reached only 23% of this repository's production lines — fsharp (3,096 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — X18 reached only 23% of this repository's production lines — fsharp (3,096 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — X2 reached only 23% of this repository's production lines — fsharp (3,096 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 18 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj src/Navs.CSharp/Navs.CSharp.csproj:11
- NoWarnInCsproj src/Navs.CSharp.Tests/Navs.CSharp.Tests.csproj:7
- NoWarnInCsproj src/UrlTemplates.CSharp/UrlTemplates.CSharp.csproj:11
- NoWarnInCsproj src/UrlTemplates.CSharp.Tests/UrlTemplates.CSharp.Tests.csproj:7
- REDACTED
- REDACTED
Serious — 18 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- UrlTemplateModule.toUrl (cyclomatic 16) src/UrlTemplates/UrlTemplate.fs:160
- Deprecated: xunit src/Directory.Packages.props:26
- FileTooLong: Navs/Router.fs src/Navs/Router.fs
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/Navs.Avalonia/Library.fs:1
- Edited copies of one member (3 members, 17+ corresponding lines) src/UrlTemplates.CSharp/RouteMatcher.cs:31
- Edited copy of a member (16 corresponding lines) src/UrlTemplates.CSharp/RouteMatcher.cs:8
- Duplicated block (18–19 lines × 4) src/Navs.Avalonia/Library.fs:16
- Duplicated block (15 lines × 2) src/Navs.CSharp/TypedParameters.cs:22
- Duplicated block (12 lines × 4) src/Navs.Avalonia/Library.fs:37
- Duplicated block (12 lines × 2) src/Navs.CSharp/TypedParameters.cs:7
- Edited copy of a member (23 corresponding lines) samples/GooSample/About.fs:1
- Duplicated block (36 lines × 2) samples/NxuiDeclarative/Program.fs:35
- Duplicated block (14–16 lines × 2) samples/NxuiDeclarative/Program.fs:84
Minor — 13 finding(s)
- REDACTED
- REDACTED
- Scattered collaborators
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:10
- No dependency-update automation src/Directory.Packages.props:7
- Duplicated predicate src/Navs.CSharp/TypedParameters.cs:10
- Null-forgiving operator (`!`) suppressions override nullable warnings
Minor — 17 finding(s)
- Outdated: Avalonia.Headless
- Outdated: Expecto
- Outdated: FSharp.Core
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: YoloDev.Expecto.TestSdk
- Outdated: Avalonia
- Outdated: Ionide.KeepAChangelog.Tasks
- Outdated: Microsoft.Extensions.Logging
- Outdated: xunit.runner.visualstudio
- Outdated: Avalonia.FuncUI
- Outdated: Goo
- Outdated: Terminal.Gui
- Outdated: FsCheck
- Outdated: Avalonia.Desktop
- Outdated: Avalonia.Themes.Fluent
- Outdated: Goo.Widgets
- Outdated: Microsoft.Extensions.Logging.Console
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e45bc9813baf420786bfeb7e4f5fe4df/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e45bc9813baf420786bfeb7e4f5fe4df/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 15 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Navs.slnx package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-59216ad57a5a4a0c981901531e3302c8 | 0 | artifacts/raw/osv-scanner.json |