Executive summary
vbfox/FoxSharp falls short of our standard for production because its Explicit debt dimensions are rated Critical, and it has sets of compiler warnings switched off in projects. It scores 56 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Code Health, at 43, is the weakest lens and counts most in the score. The best first step is fixing the silenced warnings, worth about 13 points. Recording design decisions comes next, worth about 5 points. Raising Code Health to 70 would lift the score to about 65.
Four known security holes in the packages the code depends on can be used by attackers. One automatic update takes new releases before a bad one can be spotted. Updating the vulnerable packages and setting a waiting period for automatic updates would close both risks. The check for vulnerable packages switched off needs switching back on. The five sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 2,135 lines, about €4,000 to rebuild.
If Code Health rose from 43 to 70, the lowest score rated Strong, the score would rise from 56 to about 65.
New since the last survey: 2 findings
- Incompleteness & stubs · Unfinished branch — throws a "not implemented" exception src/BlackFox.CommandLine.TestParsers/MonoUnix.cs
- Incompleteness & stubs · Unfinished branch — throws a "not implemented" exception src/BlackFox.CommandLine.TestParsers/MonoUnix.cs
Fixed since the last survey: 2 findings
- Dependency Hygiene · Vulnerable: System.Security.Cryptography.Pkcs
- Dependency Hygiene · Vulnerable: Microsoft.NETCore.App
Rebuild cost: about €4,000 · Estimate
| Cost to rebuild | €1,300 to €6,800, for 22 to 71 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. 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: 2,135 lines of product code |
| Comment lines | The estimate prices 2,099 lines. Comment lines count towards the size of 2,135 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 BlackFox | 2 BlackFox.CachedFSharpReflection | 3 BlackFox.CommandLine.EnvironmentDetection | 4 BlackFox.CommandLine.MonoUnixCommandLine | 5 BlackFox.CommandLine.MsvcrCommandLine | 6 BlackFox.Fake.BuildTask | 7 BlackFox.JavaPropertiesFile | 8 BlackFox.MasterOfFoo.Build.Program | 9 BlackFox.PathEnvironmentUtils | 10 BlackFox.VsWhere | 11 BlackFox.VsWhereCmd | 12 BlackFox.CachedFSharpReflection.DictCache | 13 BlackFox.CommandLine | 14 BlackFox.JavaPropertiesFile.JavaPropertiesFile | 15 BlackFox.JavaPropertiesFile.Parser | 16 BlackFox.MasterOfFoo.Build.Tasks | 17 BlackFox.VsWhere.VsInstances | 18 BlackFox.VsWhere.VsInstances.Legacy | 19 BlackFox.CommandLine.CmdLineModule |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 BlackFox | |||||||||||||||||||
| 2 BlackFox.CachedFSharpReflection | |||||||||||||||||||
| 3 BlackFox.CommandLine.EnvironmentDetection | |||||||||||||||||||
| 4 BlackFox.CommandLine.MonoUnixCommandLine | |||||||||||||||||||
| 5 BlackFox.CommandLine.MsvcrCommandLine | |||||||||||||||||||
| 6 BlackFox.Fake.BuildTask | |||||||||||||||||||
| 7 BlackFox.JavaPropertiesFile | |||||||||||||||||||
| 8 BlackFox.MasterOfFoo.Build.Program | |||||||||||||||||||
| 9 BlackFox.PathEnvironmentUtils | |||||||||||||||||||
| 10 BlackFox.VsWhere | |||||||||||||||||||
| 11 BlackFox.VsWhereCmd | |||||||||||||||||||
| 12 BlackFox.CachedFSharpReflection.DictCache | 1 | ||||||||||||||||||
| 13 BlackFox.CommandLine | 1 | 1 | |||||||||||||||||
| 14 BlackFox.JavaPropertiesFile.JavaPropertiesFile | 1 | ||||||||||||||||||
| 15 BlackFox.JavaPropertiesFile.Parser | 1 | ||||||||||||||||||
| 16 BlackFox.MasterOfFoo.Build.Tasks | 1 | ||||||||||||||||||
| 17 BlackFox.VsWhere.VsInstances | 10 | ||||||||||||||||||
| 18 BlackFox.VsWhere.VsInstances.Legacy | 1 | ||||||||||||||||||
| 19 BlackFox.CommandLine.CmdLineModule | 1 | 1 |
12→2 BlackFox.CachedFSharpReflection.DictCache uses BlackFox.CachedFSharpReflection✕
- Connections
- 1 pair of types, where a type in BlackFox.CachedFSharpReflection.DictCache uses a type in BlackFox.CachedFSharpReflection.
- The types involved
BlackFox.CachedFSharpReflection.DictCache.DictCache→BlackFox.CachedFSharpReflection.DictCache`3
- Direction
- BlackFox.CachedFSharpReflection.DictCache uses BlackFox.CachedFSharpReflection, so a change to BlackFox.CachedFSharpReflection can break BlackFox.CachedFSharpReflection.DictCache, while a change to BlackFox.CachedFSharpReflection.DictCache can't break BlackFox.CachedFSharpReflection.
- Position
- Below the diagonal: BlackFox.CachedFSharpReflection.DictCache uses a module listed above it, which is the healthy direction.
13→4 BlackFox.CommandLine uses BlackFox.CommandLine.MonoUnixCommandLine✕
- Connections
- 1 pair of types, where a type in BlackFox.CommandLine uses a type in BlackFox.CommandLine.MonoUnixCommandLine.
- The types involved
BlackFox.CommandLine.CmdLine→BlackFox.CommandLine.MonoUnixCommandLine.EscapeSettings
- Direction
- BlackFox.CommandLine uses BlackFox.CommandLine.MonoUnixCommandLine, so a change to BlackFox.CommandLine.MonoUnixCommandLine can break BlackFox.CommandLine, while a change to BlackFox.CommandLine can't break BlackFox.CommandLine.MonoUnixCommandLine.
- Position
- Below the diagonal: BlackFox.CommandLine uses a module listed above it, which is the healthy direction.
13→5 BlackFox.CommandLine uses BlackFox.CommandLine.MsvcrCommandLine✕
- Connections
- 1 pair of types, where a type in BlackFox.CommandLine uses a type in BlackFox.CommandLine.MsvcrCommandLine.
- The types involved
BlackFox.CommandLine.CmdLine→BlackFox.CommandLine.MsvcrCommandLine.EscapeSettings
- Direction
- BlackFox.CommandLine uses BlackFox.CommandLine.MsvcrCommandLine, so a change to BlackFox.CommandLine.MsvcrCommandLine can break BlackFox.CommandLine, while a change to BlackFox.CommandLine can't break BlackFox.CommandLine.MsvcrCommandLine.
- Position
- Below the diagonal: BlackFox.CommandLine uses a module listed above it, which is the healthy direction.
14→7 BlackFox.JavaPropertiesFile.JavaPropertiesFile uses BlackFox.JavaPropertiesFile✕
- Connections
- 1 pair of types, where a type in BlackFox.JavaPropertiesFile.JavaPropertiesFile uses a type in BlackFox.JavaPropertiesFile.
- The types involved
BlackFox.JavaPropertiesFile.JavaPropertiesFile.JavaPropertiesFile→BlackFox.JavaPropertiesFile.Entry
- Direction
- BlackFox.JavaPropertiesFile.JavaPropertiesFile uses BlackFox.JavaPropertiesFile, so a change to BlackFox.JavaPropertiesFile can break BlackFox.JavaPropertiesFile.JavaPropertiesFile, while a change to BlackFox.JavaPropertiesFile.JavaPropertiesFile can't break BlackFox.JavaPropertiesFile.
- Position
- Below the diagonal: BlackFox.JavaPropertiesFile.JavaPropertiesFile uses a module listed above it, which is the healthy direction.
15→7 BlackFox.JavaPropertiesFile.Parser uses BlackFox.JavaPropertiesFile✕
- Connections
- 1 pair of types, where a type in BlackFox.JavaPropertiesFile.Parser uses a type in BlackFox.JavaPropertiesFile.
- The types involved
BlackFox.JavaPropertiesFile.Parser.Parser→BlackFox.JavaPropertiesFile.Entry
- Direction
- BlackFox.JavaPropertiesFile.Parser uses BlackFox.JavaPropertiesFile, so a change to BlackFox.JavaPropertiesFile can break BlackFox.JavaPropertiesFile.Parser, while a change to BlackFox.JavaPropertiesFile.Parser can't break BlackFox.JavaPropertiesFile.
- Position
- Below the diagonal: BlackFox.JavaPropertiesFile.Parser uses a module listed above it, which is the healthy direction.
16→6 BlackFox.MasterOfFoo.Build.Tasks uses BlackFox.Fake.BuildTask✕
- Connections
- 1 pair of types, where a type in BlackFox.MasterOfFoo.Build.Tasks uses a type in BlackFox.Fake.BuildTask.
- The types involved
BlackFox.MasterOfFoo.Build.Tasks.Tasks→BlackFox.Fake.BuildTask.TaskInfo
- Direction
- BlackFox.MasterOfFoo.Build.Tasks uses BlackFox.Fake.BuildTask, so a change to BlackFox.Fake.BuildTask can break BlackFox.MasterOfFoo.Build.Tasks, while a change to BlackFox.MasterOfFoo.Build.Tasks can't break BlackFox.Fake.BuildTask.
- Position
- Below the diagonal: BlackFox.MasterOfFoo.Build.Tasks uses a module listed above it, which is the healthy direction.
17→10 BlackFox.VsWhere.VsInstances uses BlackFox.VsWhere✕
- Connections
- 10 pairs of types, where a type in BlackFox.VsWhere.VsInstances uses a type in BlackFox.VsWhere.
- The types involved
BlackFox.VsWhere.VsInstances.VsInstances→BlackFox.VsWhere.ISetupConfigurationBlackFox.VsWhere.VsInstances.VsInstances→BlackFox.VsWhere.ISetupErrorInfoBlackFox.VsWhere.VsInstances.VsInstances→BlackFox.VsWhere.ISetupErrorStateBlackFox.VsWhere.VsInstances.VsInstances→BlackFox.VsWhere.ISetupInstanceBlackFox.VsWhere.VsInstances.VsInstances→BlackFox.VsWhere.ISetupPackageReferenceBlackFox.VsWhere.VsInstances.VsInstances→BlackFox.VsWhere.ISetupPropertyStoreBlackFox.VsWhere.VsInstances.VsInstances→BlackFox.VsWhere.VsSetupErrorInfoBlackFox.VsWhere.VsInstances.VsInstances→BlackFox.VsWhere.VsSetupErrorStateBlackFox.VsWhere.VsInstances.VsInstances→BlackFox.VsWhere.VsSetupInstanceBlackFox.VsWhere.VsInstances.VsInstances→BlackFox.VsWhere.VsSetupPackage
- Direction
- BlackFox.VsWhere.VsInstances uses BlackFox.VsWhere, so a change to BlackFox.VsWhere can break BlackFox.VsWhere.VsInstances, while a change to BlackFox.VsWhere.VsInstances can't break BlackFox.VsWhere.
- Position
- Below the diagonal: BlackFox.VsWhere.VsInstances uses a module listed above it, which is the healthy direction.
18→10 BlackFox.VsWhere.VsInstances.Legacy uses BlackFox.VsWhere✕
- Connections
- 1 pair of types, where a type in BlackFox.VsWhere.VsInstances.Legacy uses a type in BlackFox.VsWhere.
- The types involved
BlackFox.VsWhere.VsInstances.Legacy.Legacy→BlackFox.VsWhere.VsSetupInstance
- Direction
- BlackFox.VsWhere.VsInstances.Legacy uses BlackFox.VsWhere, so a change to BlackFox.VsWhere can break BlackFox.VsWhere.VsInstances.Legacy, while a change to BlackFox.VsWhere.VsInstances.Legacy can't break BlackFox.VsWhere.
- Position
- Below the diagonal: BlackFox.VsWhere.VsInstances.Legacy uses a module listed above it, which is the healthy direction.
19→5 BlackFox.CommandLine.CmdLineModule uses BlackFox.CommandLine.MsvcrCommandLine✕
- Connections
- 1 pair of types, where a type in BlackFox.CommandLine.CmdLineModule uses a type in BlackFox.CommandLine.MsvcrCommandLine.
- The types involved
BlackFox.CommandLine.CmdLineModule.CmdLineModule→BlackFox.CommandLine.MsvcrCommandLine.EscapeSettings
- Direction
- BlackFox.CommandLine.CmdLineModule uses BlackFox.CommandLine.MsvcrCommandLine, so a change to BlackFox.CommandLine.MsvcrCommandLine can break BlackFox.CommandLine.CmdLineModule, while a change to BlackFox.CommandLine.CmdLineModule can't break BlackFox.CommandLine.MsvcrCommandLine.
- Position
- Below the diagonal: BlackFox.CommandLine.CmdLineModule uses a module listed above it, which is the healthy direction.
19→13 BlackFox.CommandLine.CmdLineModule uses BlackFox.CommandLine✕
- Connections
- 1 pair of types, where a type in BlackFox.CommandLine.CmdLineModule uses a type in BlackFox.CommandLine.
- The types involved
BlackFox.CommandLine.CmdLineModule.CmdLineModule→BlackFox.CommandLine.CmdLine
- Direction
- BlackFox.CommandLine.CmdLineModule uses BlackFox.CommandLine, so a change to BlackFox.CommandLine can break BlackFox.CommandLine.CmdLineModule, while a change to BlackFox.CommandLine.CmdLineModule can't break BlackFox.CommandLine.
- Position
- Below the diagonal: BlackFox.CommandLine.CmdLineModule uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 4 | High / Critical |
| A05:2025 — Injection | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 5 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (5); Resolve the 1 No ADRs found finding(s) in ADR Quality — start with BlackFox.FoxSharp.Build.fsproj; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 5 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (5). | +12.9 pts | Low | Explicit Debt |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with BlackFox.FoxSharp.Build.fsproj. | +5.3 pts | Low | ADR Quality |
| Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with REDACTED, Directory.Build.props. | +2.4 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. | +4.4 pts | Medium | Architecture documentation |
| Resolve the 1 Deprecated finding(s) in Dependency Hygiene. | +1.2 pts | Low | Dependency Hygiene |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.5 pts | Medium | Release Hygiene |
| Expand the README with getting-started, architecture overview and a project map. | +1.3 pts | Medium | Documentation (README) |
| Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with MonoUnixCommandLine.parse (cognitive 72), MsvcrCommandLine.parse (cognitive 49), MonoUnix.split_cmdline (cognitive 40). | +1.7 pts | High | Cognitive Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/Directory.Build.props | 4.9 | Mixed | Explicit Debt: NoWarnInCsproj — 6 warning codes suppressed in one element |
| REDACTED | 5.3 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/BlackFox.CommandLine/MonoUnixCommandLine.fs | 7.2 | Mixed | Cyclomatic Complexity: MonoUnixCommandLine.parse (cyclomatic 24) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/BlackFox.CommandLine.TestParsers/MonoUnix.cs | 7.8 | Mixed | Cyclomatic Complexity: MonoUnix.split_cmdline (cyclomatic 23) |
| src/BlackFox.JavaPropertiesFile/Parser.fs | 7.8 | Mixed | Cyclomatic Complexity: Parser.readKey (cyclomatic 19) |
| src/BlackFox.CommandLine/MsvcrCommandLine.fs | 7.8 | Mixed | Cognitive Complexity: MsvcrCommandLine.parse (cognitive 49) |
| src/BlackFox.VsWhere/ComTypes.fs | 7.8 | Mixed | Code Duplication: Duplicated block (12 lines × 2) |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| src/BlackFox.CommandLine.TestParsers/DotnetCoreUnix.cs | 8.5 | Near-clean | Cognitive Complexity: DotnetCoreUnix.GetNextArgument (cognitive 26) |
| src/BlackFox.VsWhere/VsInstances.fs | 8.5 | Near-clean | Cognitive Complexity: Legacy.getAll (cognitive 21) |
| src/BlackFox.Fake.BuildTask/BuildTask.fs | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: TaskBuilder (LCOM4 4) |
| src/BlackFox.FoxSharp.Build/BlackFox.FoxSharp.Build.fsproj | 9.5 | Near-clean | ADR Quality: No ADRs found |
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 33 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 33 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, 31 of 83 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — 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. Coverage NOT MEASURED: this repository's test suite BUILT and its tests PASSED in this run — so neither the build nor our analyzer environment is in question — but the run produced no coverage data, and it captured no message saying why. The usual cause is that the test projects wire up no coverage collector (`--collect:"XPlat Code Coverage"` needs a `coverlet.collector` PackageReference); on a very large suite the instrumented run can also exceed its per-target budget before writing anything. Add a `coverlet.collector` PackageReference, or commit the Cobertura/OpenCover/lcov report your CI already produces, and real coverage is measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D11 Test Reliability — 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. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- 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-maintainer repository — bus factor is not applicable (4 contributor(s) across 164 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 3 hold 0.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and 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 'REDACTED' 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 6 deducted marker(s) and the 4.5/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (1,758 lines, 89% 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- 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.
- 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.
- 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.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X28 Index access outside its own emptiness guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X30 Support guard that admits what it rejects — 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.
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MonoUnixCommandLine.parse at 24.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with MonoUnixCommandLine.parse (cyclomatic 24), MonoUnix.split_cmdline (cyclomatic 23), Parser.readKey (cyclomatic 19). — 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 3 together lifts Cyclomatic Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was MonoUnixCommandLine.parse at 72.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with MonoUnixCommandLine.parse (cognitive 72), MsvcrCommandLine.parse (cognitive 49), MonoUnix.split_cmdline (cognitive 40). — 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 3 together lifts Cognitive Complexity from 6.9 to about 8.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
4 duplicated block group(s) detected. 3.7 % of the production lines (78 of 2,135) are in a reported copy.
What to do
- Resolve the 1 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with MonoUnixCommandLine.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Parser.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with ComTypes.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
1 of 1 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with BuildTask.fs. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
47 outdated, 2 vulnerable, 1 deprecated packages.
What to do
- Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with REDACTED, Directory.Build.props. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene. — 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 178 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 3 direct `PackageReference`(s), and 170 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
6 deducted debt markers + unmeasured dead symbols across 225 LoC in the .NET projects (4.5/KLoC) → score 1.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (89% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 5 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (5). — One of this dimension's main actionable groups (5 issue-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with BlackFox.FoxSharp.Build.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
90 % of calls cross a namespace and 5 % go through an interface, but 99 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 4 high, 0 medium, 0 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
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.
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 10 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)
- The root README is 69 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — Readme.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P3 · Security & performance tooling
- `NoWarn` silences NU1901, NU1902, NU1903, NU1904 — NuGet's vulnerability-audit warnings for low, moderate, high and critical advisories. Suppressed advisories are still shipped; they are only invisible in the build log. Remove these codes from NoWarn and address or explicitly accept each advisory instead. — src/Directory.Build.props:17
- 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 1 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:6
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `nuget`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
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.
- Dependabot is configured but does not watch `nuget` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 43% | Weak — gated by D17 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 92% | Adequate — gated by D6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 59% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 60% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 95% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 79 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 — no public interfaces
- 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in 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.
- D10 Test Quality — ~940 lines of test source are present (.fs) 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.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D16 Bus Factor — single-maintainer 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.
- D19 Documentation Quality — D19 withholds "XML-doc coverage": 1 candidate(s) (0 of them low-coverage Warnings on library projects) were measured and not published.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (2,135 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
- D26 Project Cohesion — This repository is one project, `BlackFox.CommandLine.TestParsers` (225 LoC, 45 public types across 23 namespaces), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — the suite ran but produced no coverage data
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (15 value object(s))
- 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 11% of this repository's production lines — fsharp (1,910 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), 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 not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- 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.
- PF3 Async & latency hygiene — 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.
- 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.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 11% of this repository's production lines — fsharp (1,910 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 — X16 reached only 11% of this repository's production lines — fsharp (1,910 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — no async method does work a token could cancel
- 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 — X28 reached only 11% of this repository's production lines — fsharp (1,910 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X30 reached only 11% of this repository's production lines — fsharp (1,910 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- X5 Nullable reference types — no NRT-eligible projects
- 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 — 11 finding(s)
- NoWarnInCsproj — 6 warning codes suppressed in one element src/Directory.Build.props:17
- NoWarnInCsproj — known-vulnerability alert suppressed src/Directory.Build.props:17
- NoWarnInCsproj — known-vulnerability alert suppressed src/Directory.Build.props:17
- NoWarnInCsproj — known-vulnerability alert suppressed src/Directory.Build.props:17
- NoWarnInCsproj — known-vulnerability alert suppressed src/Directory.Build.props:17
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NuGet vulnerability audit suppressed via NoWarn src/Directory.Build.props:17
Serious — 18 finding(s)
- MonoUnixCommandLine.parse (cyclomatic 24) src/BlackFox.CommandLine/MonoUnixCommandLine.fs:70
- MonoUnix.split_cmdline (cyclomatic 23) src/BlackFox.CommandLine.TestParsers/MonoUnix.cs:35
- Parser.readKey (cyclomatic 19) src/BlackFox.JavaPropertiesFile/Parser.fs:65
- Deprecated: Microsoft.NETCore.App
- MonoUnixCommandLine.parse (cognitive 72) src/BlackFox.CommandLine/MonoUnixCommandLine.fs:70
- MsvcrCommandLine.parse (cognitive 49) src/BlackFox.CommandLine/MsvcrCommandLine.fs:134
- MonoUnix.split_cmdline (cognitive 40) src/BlackFox.CommandLine.TestParsers/MonoUnix.cs:35
- DotnetCoreUnix.GetNextArgument (cognitive 26) src/BlackFox.CommandLine.TestParsers/DotnetCoreUnix.cs:42
- MsvcrCommandLine.escapeArgumentToBuilder (cognitive 26) src/BlackFox.CommandLine/MsvcrCommandLine.fs:65
- Legacy.getAll (cognitive 21) src/BlackFox.VsWhere/VsInstances.fs:166
- MonoUnixCommandLine.escapeArgumentToBuilder (cognitive 19) src/BlackFox.CommandLine/MonoUnixCommandLine.fs:22
- REDACTED
- Duplicated block (14 lines × 2) src/BlackFox.CommandLine/MonoUnixCommandLine.fs:52
- Duplicated block (9 lines × 2) src/BlackFox.JavaPropertiesFile/Parser.fs:78
- Duplicated block (12 lines × 2) src/BlackFox.VsWhere/ComTypes.fs:35
- Duplicated block (7 lines × 2) src/BlackFox.VsWhere/ComTypes.fs:12
- Low cohesion: TaskBuilder (LCOM4 4) src/BlackFox.Fake.BuildTask/BuildTask.fs:51
- NuGet dependencies are not locked
Minor — 9 finding(s)
- Outdated: FSharp.Core REDACTED:12
- Outdated: Microsoft.SourceLink.GitHub src/Directory.Build.props:27
- No ADRs found src/BlackFox.FoxSharp.Build/BlackFox.FoxSharp.Build.fsproj:4
- Thin README Readme.md:1
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:6
- Dependabot does not watch nuget REDACTED:2
- No changelog
Minor — 45 finding(s)
- Outdated: Fake.Core.Target
- Outdated: Fake.Api.GitHub
- Outdated: Fake.BuildServer.GitHubActions
- Outdated: Fake.Core.CommandLineParsing
- Outdated: Fake.Core.Context
- Outdated: Fake.Core.Environment
- Outdated: Fake.Core.FakeVar
- Outdated: Fake.Core.Process
- Outdated: Fake.Core.ReleaseNotes
- Outdated: Fake.Core.SemVer
- Outdated: Fake.Core.String
- Outdated: Fake.Core.Tasks
- Outdated: Fake.Core.Trace
- Outdated: Fake.Core.UserInput
- Outdated: Fake.Core.Xml
- Outdated: Fake.DotNet.AssemblyInfoFile
- Outdated: Fake.DotNet.Cli
- Outdated: Fake.DotNet.MSBuild
- Outdated: Fake.DotNet.NuGet
- Outdated: Fake.DotNet.Paket
- Outdated: Fake.DotNet.Testing.Expecto
- Outdated: Fake.IO.FileSystem
- Outdated: Fake.IO.Zip
- Outdated: Fake.Net.Http
- Outdated: Fake.Testing.Common
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-77438e71983d4748b2d8e71546a91d23/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-77438e71983d4748b2d8e71546a91d23/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 1 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list FoxSharp.sln package --vulnerable --include-transitive --format json | 4 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d3abcf79ec4f4ac5a79c75713deaeea0 | 0 | artifacts/raw/osv-scanner.json |