Executive summary
aardvark-platform/aardvark.docs falls short of our standard for production because the project has no automated tests and we found no logging, tracing or health checks in the code. It scores 45 out of 100 and is rated Weak, and two of its four critical findings are security problems in the build pipeline.
Production Readiness, at 22, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 9 points. Adding automated tests would lift Production Readiness itself, worth about 20 points. Raising Production Readiness to 70 would lift the score to about 61.
Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. The project has no automated tests, so a change can break it without warning. Adding automated tests and pinning each tool to an exact version would close both risks. The set of compiler warnings switched off in a project needs turning back on in the build file.
The product code is 3,055 lines, about €2,300 to rebuild.
If Production Readiness rose from 22 to 70, the lowest score rated Strong, the score would rise from 45 to about 61.
Fixed since the last survey: 1 finding
- Code Duplication · Duplicated block (6 lines × 2) src/Sky/Shaders.fs
Rebuild cost: about €2,300 · Estimate
| Cost to rebuild | €760 to €3,800, for 13 to 40 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, 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.7 at a score of 45. 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: 3,055 lines of product code |
| Comment lines | The estimate prices 3,038 lines. Comment lines count towards the size of 3,055 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 Aardvark.Docs.SierpinksiTetrahedron | 2 Aardvark.Docs.Utils.Geometry | 3 Aardvark.Docs.Utils.ThickLine | 4 Constellations | 5 HelloWorldCSharp | 6 Program | 7 SSAO | 8 SSAO.PointShader | 9 SSAO.SSAO.Semantic | 10 Sky.App.Markers | 11 Sky.App.RenderPass | 12 Sky.App.SgExtensions | 13 Sky.GuiExtensions | 14 Sky.GuiExtensions.Incremental | 15 Sky.GuiExtensions.Incremental.Html | 16 Sky.Hip | 17 Sky.Model | 18 SSAO.App | 19 SSAO.SSAO | 20 SSAO.SSAO.Shader | 21 SSAO.Utilities | 22 Sky | 23 Sky.App.Moon | 24 Sky.App.Planets | 25 Sky.App.Sky | 26 Sky.App.Stars | 27 Sky.App.Sun | 28 Sky.Model.GeoInfoModule | 29 Sky.Model.ModelModule | 30 Sky.Shaders | 31 Sky.App | 32 Sky.GeoApp |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Aardvark.Docs.SierpinksiTetrahedron | ||||||||||||||||||||||||||||||||
| 2 Aardvark.Docs.Utils.Geometry | ||||||||||||||||||||||||||||||||
| 3 Aardvark.Docs.Utils.ThickLine | ||||||||||||||||||||||||||||||||
| 4 Constellations | ||||||||||||||||||||||||||||||||
| 5 HelloWorldCSharp | ||||||||||||||||||||||||||||||||
| 6 Program | ||||||||||||||||||||||||||||||||
| 7 SSAO | ||||||||||||||||||||||||||||||||
| 8 SSAO.PointShader | ||||||||||||||||||||||||||||||||
| 9 SSAO.SSAO.Semantic | ||||||||||||||||||||||||||||||||
| 10 Sky.App.Markers | ||||||||||||||||||||||||||||||||
| 11 Sky.App.RenderPass | ||||||||||||||||||||||||||||||||
| 12 Sky.App.SgExtensions | ||||||||||||||||||||||||||||||||
| 13 Sky.GuiExtensions | ||||||||||||||||||||||||||||||||
| 14 Sky.GuiExtensions.Incremental | ||||||||||||||||||||||||||||||||
| 15 Sky.GuiExtensions.Incremental.Html | ||||||||||||||||||||||||||||||||
| 16 Sky.Hip | ||||||||||||||||||||||||||||||||
| 17 Sky.Model | ||||||||||||||||||||||||||||||||
| 18 SSAO.App | 3 | |||||||||||||||||||||||||||||||
| 19 SSAO.SSAO | 1 | |||||||||||||||||||||||||||||||
| 20 SSAO.SSAO.Shader | 1 | |||||||||||||||||||||||||||||||
| 21 SSAO.Utilities | 1 | |||||||||||||||||||||||||||||||
| 22 Sky | 2 | |||||||||||||||||||||||||||||||
| 23 Sky.App.Moon | 1 | |||||||||||||||||||||||||||||||
| 24 Sky.App.Planets | 1 | |||||||||||||||||||||||||||||||
| 25 Sky.App.Sky | 2 | |||||||||||||||||||||||||||||||
| 26 Sky.App.Stars | 2 | |||||||||||||||||||||||||||||||
| 27 Sky.App.Sun | 1 | |||||||||||||||||||||||||||||||
| 28 Sky.Model.GeoInfoModule | 1 | |||||||||||||||||||||||||||||||
| 29 Sky.Model.ModelModule | 1 | |||||||||||||||||||||||||||||||
| 30 Sky.Shaders | 1 | |||||||||||||||||||||||||||||||
| 31 Sky.App | 2 | 1 | ||||||||||||||||||||||||||||||
| 32 Sky.GeoApp | 2 | 1 |
18→7 SSAO.App uses SSAO✕
- Connections
- 3 pairs of types, where a type in SSAO.App uses a type in SSAO.
- The types involved
SSAO.App.App→SSAO.AdaptiveModelSSAO.App.App→SSAO.ModelSSAO.App.Message→SSAO.SSAOVisualization
- Direction
- SSAO.App uses SSAO, so a change to SSAO can break SSAO.App, while a change to SSAO.App can't break SSAO.
- Position
- Below the diagonal: SSAO.App uses a module listed above it, which is the healthy direction.
19→7 SSAO.SSAO uses SSAO✕
- Connections
- 1 pair of types, where a type in SSAO.SSAO uses a type in SSAO.
- The types involved
SSAO.SSAO.SSAO→SSAO.SSAOConfig
- Direction
- SSAO.SSAO uses SSAO, so a change to SSAO can break SSAO.SSAO, while a change to SSAO.SSAO can't break SSAO.
- Position
- Below the diagonal: SSAO.SSAO uses a module listed above it, which is the healthy direction.
20→7 SSAO.SSAO.Shader uses SSAO✕
- Connections
- 1 pair of types, where a type in SSAO.SSAO.Shader uses a type in SSAO.
- The types involved
SSAO.SSAO.Shader.Shader→SSAO.SSAOVisualization
- Direction
- SSAO.SSAO.Shader uses SSAO, so a change to SSAO can break SSAO.SSAO.Shader, while a change to SSAO.SSAO.Shader can't break SSAO.
- Position
- Below the diagonal: SSAO.SSAO.Shader uses a module listed above it, which is the healthy direction.
21→7 SSAO.Utilities uses SSAO✕
- Connections
- 1 pair of types, where a type in SSAO.Utilities uses a type in SSAO.
- The types involved
SSAO.Utilities.Utilities→SSAO.SSAOConfig
- Direction
- SSAO.Utilities uses SSAO, so a change to SSAO can break SSAO.Utilities, while a change to SSAO.Utilities can't break SSAO.
- Position
- Below the diagonal: SSAO.Utilities uses a module listed above it, which is the healthy direction.
22→17 Sky uses Sky.Model✕
- Connections
- 2 pairs of types, where a type in Sky uses a type in Sky.Model.
- The types involved
Sky.Message→Sky.Model.ExposureModeSky.Message→Sky.Model.SkyType
- Direction
- Sky uses Sky.Model, so a change to Sky.Model can break Sky, while a change to Sky can't break Sky.Model.
- Position
- Below the diagonal: Sky uses a module listed above it, which is the healthy direction.
23→17 Sky.App.Moon uses Sky.Model✕
- Connections
- 1 pair of types, where a type in Sky.App.Moon uses a type in Sky.Model.
- The types involved
Sky.App.Moon.Moon→Sky.Model.AdaptiveGeoInfo
- Direction
- Sky.App.Moon uses Sky.Model, so a change to Sky.Model can break Sky.App.Moon, while a change to Sky.App.Moon can't break Sky.Model.
- Position
- Below the diagonal: Sky.App.Moon uses a module listed above it, which is the healthy direction.
24→17 Sky.App.Planets uses Sky.Model✕
- Connections
- 1 pair of types, where a type in Sky.App.Planets uses a type in Sky.Model.
- The types involved
Sky.App.Planets.Planets→Sky.Model.AdaptiveGeoInfo
- Direction
- Sky.App.Planets uses Sky.Model, so a change to Sky.Model can break Sky.App.Planets, while a change to Sky.App.Planets can't break Sky.Model.
- Position
- Below the diagonal: Sky.App.Planets uses a module listed above it, which is the healthy direction.
25→17 Sky.App.Sky uses Sky.Model✕
- Connections
- 2 pairs of types, where a type in Sky.App.Sky uses a type in Sky.Model.
- The types involved
Sky.App.Sky.Sky→Sky.Model.AdaptiveGeoInfoSky.App.Sky.Sky→Sky.Model.AdaptiveSkyParams
- Direction
- Sky.App.Sky uses Sky.Model, so a change to Sky.Model can break Sky.App.Sky, while a change to Sky.App.Sky can't break Sky.Model.
- Position
- Below the diagonal: Sky.App.Sky uses a module listed above it, which is the healthy direction.
26→17 Sky.App.Stars uses Sky.Model✕
- Connections
- 2 pairs of types, where a type in Sky.App.Stars uses a type in Sky.Model.
- The types involved
Sky.App.Stars.Stars→Sky.Model.AdaptiveGeoInfoSky.App.Stars.Stars→Sky.Model.AdaptiveStarParams
- Direction
- Sky.App.Stars uses Sky.Model, so a change to Sky.Model can break Sky.App.Stars, while a change to Sky.App.Stars can't break Sky.Model.
- Position
- Below the diagonal: Sky.App.Stars uses a module listed above it, which is the healthy direction.
27→17 Sky.App.Sun uses Sky.Model✕
- Connections
- 1 pair of types, where a type in Sky.App.Sun uses a type in Sky.Model.
- The types involved
Sky.App.Sun.Sun→Sky.Model.AdaptiveGeoInfo
- Direction
- Sky.App.Sun uses Sky.Model, so a change to Sky.Model can break Sky.App.Sun, while a change to Sky.App.Sun can't break Sky.Model.
- Position
- Below the diagonal: Sky.App.Sun uses a module listed above it, which is the healthy direction.
28→17 Sky.Model.GeoInfoModule uses Sky.Model✕
- Connections
- 1 pair of types, where a type in Sky.Model.GeoInfoModule uses a type in Sky.Model.
- The types involved
Sky.Model.GeoInfoModule.GeoInfoModule→Sky.Model.GeoInfo
- Direction
- Sky.Model.GeoInfoModule uses Sky.Model, so a change to Sky.Model can break Sky.Model.GeoInfoModule, while a change to Sky.Model.GeoInfoModule can't break Sky.Model.
- Position
- Below the diagonal: Sky.Model.GeoInfoModule uses a module listed above it, which is the healthy direction.
29→17 Sky.Model.ModelModule uses Sky.Model✕
- Connections
- 1 pair of types, where a type in Sky.Model.ModelModule uses a type in Sky.Model.
- The types involved
Sky.Model.ModelModule.ModelModule→Sky.Model.Model
- Direction
- Sky.Model.ModelModule uses Sky.Model, so a change to Sky.Model can break Sky.Model.ModelModule, while a change to Sky.Model.ModelModule can't break Sky.Model.
- Position
- Below the diagonal: Sky.Model.ModelModule uses a module listed above it, which is the healthy direction.
30→17 Sky.Shaders uses Sky.Model✕
- Connections
- 1 pair of types, where a type in Sky.Shaders uses a type in Sky.Model.
- The types involved
Sky.Shaders.Shaders→Sky.Model.ExposureMode
- Direction
- Sky.Shaders uses Sky.Model, so a change to Sky.Model can break Sky.Shaders, while a change to Sky.Shaders can't break Sky.Model.
- Position
- Below the diagonal: Sky.Shaders uses a module listed above it, which is the healthy direction.
31→17 Sky.App uses Sky.Model✕
- Connections
- 2 pairs of types, where a type in Sky.App uses a type in Sky.Model.
- The types involved
Sky.App.App→Sky.Model.AdaptiveModelSky.App.App→Sky.Model.Model
- Direction
- Sky.App uses Sky.Model, so a change to Sky.Model can break Sky.App, while a change to Sky.App can't break Sky.Model.
- Position
- Below the diagonal: Sky.App uses a module listed above it, which is the healthy direction.
31→22 Sky.App uses Sky✕
- Connections
- 1 pair of types, where a type in Sky.App uses a type in Sky.
- The types involved
Sky.App.App→Sky.Message
- Direction
- Sky.App uses Sky, so a change to Sky can break Sky.App, while a change to Sky.App can't break Sky.
- Position
- Below the diagonal: Sky.App uses a module listed above it, which is the healthy direction.
32→17 Sky.GeoApp uses Sky.Model✕
- Connections
- 2 pairs of types, where a type in Sky.GeoApp uses a type in Sky.Model.
- The types involved
Sky.GeoApp.GeoApp→Sky.Model.AdaptiveGeoInfoSky.GeoApp.GeoApp→Sky.Model.GeoInfo
- Direction
- Sky.GeoApp uses Sky.Model, so a change to Sky.Model can break Sky.GeoApp, while a change to Sky.GeoApp can't break Sky.Model.
- Position
- Below the diagonal: Sky.GeoApp uses a module listed above it, which is the healthy direction.
32→22 Sky.GeoApp uses Sky✕
- Connections
- 1 pair of types, where a type in Sky.GeoApp uses a type in Sky.
- The types involved
Sky.GeoApp.GeoApp→Sky.GeoAction
- Direction
- Sky.GeoApp uses Sky, so a change to Sky can break Sky.GeoApp, while a change to Sky.GeoApp can't break Sky.
- Position
- Below the diagonal: Sky.GeoApp 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 | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with HelloWorldCSharp.csproj; Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with HelloWorldCSharp.csproj. | +8.7 pts | Low | ADR Quality |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +20.3 pts | High | Code Coverage |
| Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with App.fs, Hip.fs, Geometry.fs. | +4.3 pts | Low | Knowledge Freshness |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +8.2 pts | Medium | Observability |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.0 pts | Medium | Architecture documentation |
| Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.targets. | +2.8 pts | Low | Explicit Debt |
| Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`. | +4.6 pts | Medium | Nullable reference types |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.1 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/SierpinskiTetrahedron/FoldingTetrahedron.fs | 7.4 | Mixed | Code Duplication: Duplicated block (8–9 lines × 2) |
| Directory.Build.targets | 7.6 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/Sky/App.fs | 7.8 | Mixed | God Classes: FileTooLong: Sky/App.fs |
| src/SSAO/SSAO.fs | 7.8 | Mixed | Code Duplication: Duplicated block (11 lines × 2) |
| src/Sky/Shaders.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (11–12 lines × 2) |
| src/AdaptiveWorld/Program.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| src/HelloWorldCSharp/HelloWorldCSharp.csproj | 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, 23 of 31 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
- D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D14 License Compliance — 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. Not scored — this repository's projects are MSBuild/NuGet projects, whose package licenses are exactly what this dimension reads, but no license could be resolved for them (the .NET license collector did not run, or restore failed). A gap in the analysis run, NOT a finding that the repository's licenses are compliant.
- 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/Utils/Utils.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 1 deducted marker(s) and the 0.5/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (2,987 lines, 98% 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.
- 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.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- 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.
- 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.
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.
- 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- 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.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being App.update at 21 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Sky/App.fs (App.update at 21). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
D2 · Cognitive Complexity
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 App.fs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
8 duplicated block group(s) detected. 2.9 % of the production lines (89 of 3,055) are in a reported copy.
What to do
- Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Program.fs, SSAO.fs, App.fs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with SSAO.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8–9 lines × 2) finding(s) in Code Duplication — start with FoldingTetrahedron.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)
0 of 2 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Sky/App.fs. Counted over 8 of the 22 production source files in this repository: 11 are under the ~2,400-byte size floor this dimension measures over, and the remaining 3 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
1 deducted debt markers + unmeasured dead symbols across 68 LoC in the .NET projects (0.5/KLoC) → score 9.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (98% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.targets. — One of this dimension's main actionable groups (1 issue-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with HelloWorldCSharp.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
97 % of calls cross a namespace and 1 % go through an interface, but 100 % 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)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. 2 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.
What to do
- No action in Static Analysis (SAST) — all 2 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 (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
7 of 11 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/SSAO/App.fs. Counted over 11 of the 22 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with App.fs, Hip.fs, Geometry.fs. — One of this dimension's main actionable groups (7 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- 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:7
- `paket.dependencies` 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`. — paket.dependencies:5
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.
PF3 · Async & latency hygiene
X5 · Nullable reference types
- 0/1 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
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 | 61% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 46% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 22% | Critical — gated by D8, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 1 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.
Not evidenced — 3 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
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 78 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
- AX8 Test isolation — no test/production split to check
- 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 — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D14 License Compliance — Package licences not resolved for an MSBuild/NuGet repository
- 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.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (407 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 (3,055 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, `HelloWorldCSharp` (68 LoC, 0 public types across 0 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (14 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 2% of this repository's production lines — fsharp (2,987 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 2 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (command argument 3); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — 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.
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 2% of this repository's production lines — fsharp (2,987 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 — 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 — 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 — 4 finding(s)
- REDACTED
- REDACTED
- NoWarnInCsproj Directory.Build.targets:4
- No automated tests
Serious — 11 finding(s)
- Duplicated block (5 lines × 2) src/AdaptiveWorld/Program.fs:23
- Duplicated block (5 lines × 2) src/SSAO/SSAO.fs:326
- Duplicated block (5 lines × 2) src/Sky/App.fs:22
- Duplicated block (5 lines × 2) src/SierpinskiTetrahedron/FoldingTetrahedron.fs:18
- FileTooLong: Sky/App.fs src/Sky/App.fs
- REDACTED
- Duplicated block (11 lines × 2) src/SSAO/SSAO.fs:336
- Duplicated block (8–9 lines × 2) src/SierpinskiTetrahedron/FoldingTetrahedron.fs:65
- Duplicated block (7 lines × 2) src/SierpinskiTetrahedron/FoldingTetrahedron.fs:28
- Duplicated block (11–12 lines × 2) src/Sky/Shaders.fs:113
- No structured logging
Minor — 16 finding(s)
- Orphaned file src/SSAO/App.fs:1
- Orphaned file src/Sky/Hip.fs:1
- Orphaned file src/Utils/Geometry.fs:1
- Orphaned file src/Gravity/Program.fs:1
- Orphaned file src/SierpinskiTetrahedron/FoldingTetrahedron.fs:1
- Orphaned file src/HelloWorldCSharp/Program.cs:1
- Orphaned file src/Sky/Constellations.fs:1
- Off-boarding risk: anonymized user #1
- No ADRs found src/HelloWorldCSharp/HelloWorldCSharp.csproj:4
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:7
- No dependency-update automation paket.dependencies:5
- Nullable reference types not enabled everywhere
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-27a3a6caf56a489db747a37379ac7adf/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-27a3a6caf56a489db747a37379ac7adf/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 . | 2 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/Aardvark.Docs.sln package --vulnerable --include-transitive --format json | 0 | 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 | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |