Executive summary
reaptor/elmish-land falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 63 out of 100 and is rated Adequate, and all seven of its critical findings are security problems in the build pipeline.
Production Readiness, at 52, is the weakest lens and counts most in the score. The best first step is updating the outdated dependencies, worth about 9 points. Adding tests for untested code comes next, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 71.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 4,058 lines, about €8,400 to rebuild.
If Production Readiness rose from 52 to 70, the lowest score rated Strong, the score would rise from 63 to about 71.
New since the last survey: 18 findings
- Code Duplication · Near-duplicate member pair (103 shared lines) src/Commands/AddLayout.fs
- Code Coverage · Low coverage: src/Program.fs src/Program.fs
- Code Coverage · Low coverage: src/Commands/Upgrade.fs src/Commands/Upgrade.fs
- Code Coverage · Low coverage: src/Commands/AddLayout.fs src/Commands/AddLayout.fs
- Code Coverage · Low coverage: src/Commands/AddPage.fs src/Commands/AddPage.fs
- Code Coverage · Low coverage: src/Commands/Server.fs src/Commands/Server.fs
- Code Coverage · Low coverage: src/Commands/Build.fs src/Commands/Build.fs
- Code Coverage · Low coverage: src/Commands/Restore.fs src/Commands/Restore.fs
- Code Coverage · Low coverage: src/Commands/Init.fs src/Commands/Init.fs
- Code Coverage · Low coverage: src/FableOutput.fs src/FableOutput.fs
- Code Coverage · Low coverage: src/Generate.fs src/Generate.fs
- Code Coverage · Low coverage: src/Resources.fs src/Resources.fs
- Code Coverage · Low coverage: src/FsProj.fs src/FsProj.fs
- Code Coverage · Low coverage: src/Settings.fs src/Settings.fs
- Code Coverage · Low coverage: src/PackageVersions.fs src/PackageVersions.fs
- Code Coverage · Low coverage: src/Base.fs src/Base.fs
- Code Coverage · No test project references backwards-compability-with-1-0-4 integration-tests/backwards-compability-with-1-0-4/backwards-compability-with-1-0-4.fsproj
- Code Coverage · No test project references using-commands-from-shared-module-does-not-work-27 integration-tests/using-commands-from-shared-module-does-not-work-27/using-commands-from-shared-module-does-not-work-27.fsproj
Fixed since the last survey: 4 findings
- Code Duplication · Near-duplicate member pair (103 shared lines) src/Commands/AddLayout.fs
- Code Duplication · Duplicated block (10 lines × 2) src/Commands/Upgrade.fs
- Code Duplication · Duplicated block (6 lines × 2) src/Commands/AddLayout.fs
- Churn × Complexity Hotspots · Hotspot: src/Program.fs src/Program.fs
Rebuild cost: about €8,400 · Estimate
| Cost to rebuild | €2,800 to €14,000, for 47 to 148 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 63. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 4,058 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 ElmishLand.AppError | 2 ElmishLand.Base.Result | 3 ElmishLand.Base.String | 4 ElmishLand.FableOutput | 5 ElmishLand.Log | 6 docs.src | 7 docs.src.components | 8 docs.src.components.PreviewComponents | 9 ElmishLand.Base | 10 ElmishLand.Effect | 11 ElmishLand.Effect.Http | 12 ElmishLand.AddPage | 13 ElmishLand.Base.AbsoluteProjectDirModule | 14 ElmishLand.Base.DotnetSdkVersionModule | 15 ElmishLand.Base.FileNameModule | 16 ElmishLand.Base.FilePathModule | 17 ElmishLand.Build | 18 ElmishLand.DotNetCli | 19 ElmishLand.FsProj | 20 ElmishLand.Generate | 21 ElmishLand.PackageVersions | 22 ElmishLand.Process | 23 ElmishLand.Program | 24 ElmishLand.Restore | 25 ElmishLand.Server | 26 ElmishLand.Settings | 27 ElmishLand.Upgrade | 28 ElmishLand.Settings.LayoutNameModule | 29 ElmishLand.Settings.RenderMethodModule | 30 ElmishLand.Settings.RouteModeModule | 31 ElmishLand.Settings.RouteParametersModule | 32 ElmishLand.TemplateEngine | 33 ElmishLand.AddLayout | 34 ElmishLand.Init | 35 ElmishLand.Resources |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ElmishLand.AppError | |||||||||||||||||||||||||||||||||||
| 2 ElmishLand.Base.Result | |||||||||||||||||||||||||||||||||||
| 3 ElmishLand.Base.String | |||||||||||||||||||||||||||||||||||
| 4 ElmishLand.FableOutput | |||||||||||||||||||||||||||||||||||
| 5 ElmishLand.Log | |||||||||||||||||||||||||||||||||||
| 6 docs.src | |||||||||||||||||||||||||||||||||||
| 7 docs.src.components | |||||||||||||||||||||||||||||||||||
| 8 docs.src.components.PreviewComponents | |||||||||||||||||||||||||||||||||||
| 9 ElmishLand.Base | 1 | ||||||||||||||||||||||||||||||||||
| 10 ElmishLand.Effect | 1 | ||||||||||||||||||||||||||||||||||
| 11 ElmishLand.Effect.Http | 1 | ||||||||||||||||||||||||||||||||||
| 12 ElmishLand.AddPage | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||
| 13 ElmishLand.Base.AbsoluteProjectDirModule | 2 | ||||||||||||||||||||||||||||||||||
| 14 ElmishLand.Base.DotnetSdkVersionModule | 1 | ||||||||||||||||||||||||||||||||||
| 15 ElmishLand.Base.FileNameModule | 2 | ||||||||||||||||||||||||||||||||||
| 16 ElmishLand.Base.FilePathModule | 1 | ||||||||||||||||||||||||||||||||||
| 17 ElmishLand.Build | 1 | 3 | |||||||||||||||||||||||||||||||||
| 18 ElmishLand.DotNetCli | 1 | 2 | |||||||||||||||||||||||||||||||||
| 19 ElmishLand.FsProj | 1 | 3 | |||||||||||||||||||||||||||||||||
| 20 ElmishLand.Generate | 1 | 3 | |||||||||||||||||||||||||||||||||
| 21 ElmishLand.PackageVersions | 1 | 1 | |||||||||||||||||||||||||||||||||
| 22 ElmishLand.Process | 1 | 1 | |||||||||||||||||||||||||||||||||
| 23 ElmishLand.Program | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||
| 24 ElmishLand.Restore | 1 | 3 | |||||||||||||||||||||||||||||||||
| 25 ElmishLand.Server | 1 | 3 | |||||||||||||||||||||||||||||||||
| 26 ElmishLand.Settings | 1 | 1 | |||||||||||||||||||||||||||||||||
| 27 ElmishLand.Upgrade | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 28 ElmishLand.Settings.LayoutNameModule | 1 | ||||||||||||||||||||||||||||||||||
| 29 ElmishLand.Settings.RenderMethodModule | 1 | ||||||||||||||||||||||||||||||||||
| 30 ElmishLand.Settings.RouteModeModule | 1 | ||||||||||||||||||||||||||||||||||
| 31 ElmishLand.Settings.RouteParametersModule | 1 | ||||||||||||||||||||||||||||||||||
| 32 ElmishLand.TemplateEngine | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 33 ElmishLand.AddLayout | 1 | 5 | 1 | 1 | |||||||||||||||||||||||||||||||
| 34 ElmishLand.Init | 1 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||
| 35 ElmishLand.Resources | 1 | 1 | 9 |
9→1 ElmishLand.Base uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.Base uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.Base.FsProjPath→ElmishLand.AppError.AppError
- Direction
- ElmishLand.Base uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.Base, while a change to ElmishLand.Base can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.Base uses a module listed above it, which is the healthy direction.
10→1 ElmishLand.Effect uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.Effect uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.Effect.IHttp→ElmishLand.AppError.AppError
- Direction
- ElmishLand.Effect uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.Effect, while a change to ElmishLand.Effect can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.Effect uses a module listed above it, which is the healthy direction.
11→1 ElmishLand.Effect.Http uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.Effect.Http uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.Effect.Http.Http→ElmishLand.AppError.AppError
- Direction
- ElmishLand.Effect.Http uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.Effect.Http, while a change to ElmishLand.Effect.Http can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.Effect.Http uses a module listed above it, which is the healthy direction.
12→1 ElmishLand.AddPage uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.AddPage uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.AddPage.AddPage→ElmishLand.AppError.AppError
- Direction
- ElmishLand.AddPage uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.AddPage, while a change to ElmishLand.AddPage can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.AddPage uses a module listed above it, which is the healthy direction.
12→9 ElmishLand.AddPage uses ElmishLand.Base✕
- Connections
- 4 pairs of types, where a type in ElmishLand.AddPage uses a type in ElmishLand.Base.
- The types involved
ElmishLand.AddPage.AddPage→ElmishLand.Base.AbsoluteProjectDirElmishLand.AddPage.AddPage→ElmishLand.Base.FilePathElmishLand.AddPage.AddPage→ElmishLand.Base.FsProjPathElmishLand.AddPage.AddPage→ElmishLand.Base.UserPromptBehaviour
- Direction
- ElmishLand.AddPage uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.AddPage, while a change to ElmishLand.AddPage can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.AddPage uses a module listed above it, which is the healthy direction.
12→10 ElmishLand.AddPage uses ElmishLand.Effect✕
- Connections
- 1 pair of types, where a type in ElmishLand.AddPage uses a type in ElmishLand.Effect.
- The types involved
ElmishLand.AddPage.AddPage→ElmishLand.Effect.ILog
- Direction
- ElmishLand.AddPage uses ElmishLand.Effect, so a change to ElmishLand.Effect can break ElmishLand.AddPage, while a change to ElmishLand.AddPage can't break ElmishLand.Effect.
- Position
- Below the diagonal: ElmishLand.AddPage uses a module listed above it, which is the healthy direction.
13→9 ElmishLand.Base.AbsoluteProjectDirModule uses ElmishLand.Base✕
- Connections
- 2 pairs of types, where a type in ElmishLand.Base.AbsoluteProjectDirModule uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Base.AbsoluteProjectDirModule.AbsoluteProjectDirModule→ElmishLand.Base.AbsoluteProjectDirElmishLand.Base.AbsoluteProjectDirModule.AbsoluteProjectDirModule→ElmishLand.Base.FilePath
- Direction
- ElmishLand.Base.AbsoluteProjectDirModule uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Base.AbsoluteProjectDirModule, while a change to ElmishLand.Base.AbsoluteProjectDirModule can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Base.AbsoluteProjectDirModule uses a module listed above it, which is the healthy direction.
14→9 ElmishLand.Base.DotnetSdkVersionModule uses ElmishLand.Base✕
- Connections
- 1 pair of types, where a type in ElmishLand.Base.DotnetSdkVersionModule uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Base.DotnetSdkVersionModule.DotnetSdkVersionModule→ElmishLand.Base.DotnetSdkVersion
- Direction
- ElmishLand.Base.DotnetSdkVersionModule uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Base.DotnetSdkVersionModule, while a change to ElmishLand.Base.DotnetSdkVersionModule can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Base.DotnetSdkVersionModule uses a module listed above it, which is the healthy direction.
15→9 ElmishLand.Base.FileNameModule uses ElmishLand.Base✕
- Connections
- 2 pairs of types, where a type in ElmishLand.Base.FileNameModule uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Base.FileNameModule.FileNameModule→ElmishLand.Base.FileNameElmishLand.Base.FileNameModule.FileNameModule→ElmishLand.Base.FilePath
- Direction
- ElmishLand.Base.FileNameModule uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Base.FileNameModule, while a change to ElmishLand.Base.FileNameModule can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Base.FileNameModule uses a module listed above it, which is the healthy direction.
16→9 ElmishLand.Base.FilePathModule uses ElmishLand.Base✕
- Connections
- 1 pair of types, where a type in ElmishLand.Base.FilePathModule uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Base.FilePathModule.FilePathModule→ElmishLand.Base.FilePath
- Direction
- ElmishLand.Base.FilePathModule uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Base.FilePathModule, while a change to ElmishLand.Base.FilePathModule can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Base.FilePathModule uses a module listed above it, which is the healthy direction.
17→1 ElmishLand.Build uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.Build uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.Build.Build→ElmishLand.AppError.AppError
- Direction
- ElmishLand.Build uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.Build, while a change to ElmishLand.Build can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.Build uses a module listed above it, which is the healthy direction.
17→9 ElmishLand.Build uses ElmishLand.Base✕
- Connections
- 3 pairs of types, where a type in ElmishLand.Build uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Build.Build→ElmishLand.Base.AbsoluteProjectDirElmishLand.Build.Build→ElmishLand.Base.FilePathElmishLand.Build.Build→ElmishLand.Base.UserPromptBehaviour
- Direction
- ElmishLand.Build uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Build, while a change to ElmishLand.Build can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Build uses a module listed above it, which is the healthy direction.
18→1 ElmishLand.DotNetCli uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.DotNetCli uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.DotNetCli.DotNetCli→ElmishLand.AppError.AppError
- Direction
- ElmishLand.DotNetCli uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.DotNetCli, while a change to ElmishLand.DotNetCli can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.DotNetCli uses a module listed above it, which is the healthy direction.
18→9 ElmishLand.DotNetCli uses ElmishLand.Base✕
- Connections
- 2 pairs of types, where a type in ElmishLand.DotNetCli uses a type in ElmishLand.Base.
- The types involved
ElmishLand.DotNetCli.DotNetCli→ElmishLand.Base.DotnetSdkVersionElmishLand.DotNetCli.DotNetCli→ElmishLand.Base.FilePath
- Direction
- ElmishLand.DotNetCli uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.DotNetCli, while a change to ElmishLand.DotNetCli can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.DotNetCli uses a module listed above it, which is the healthy direction.
19→1 ElmishLand.FsProj uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.FsProj uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.FsProj.FsProj→ElmishLand.AppError.AppError
- Direction
- ElmishLand.FsProj uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.FsProj, while a change to ElmishLand.FsProj can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.FsProj uses a module listed above it, which is the healthy direction.
19→9 ElmishLand.FsProj uses ElmishLand.Base✕
- Connections
- 3 pairs of types, where a type in ElmishLand.FsProj uses a type in ElmishLand.Base.
- The types involved
ElmishLand.FsProj.FsProj→ElmishLand.Base.AbsoluteProjectDirElmishLand.FsProj.FsProj→ElmishLand.Base.FsProjPathElmishLand.FsProj.FsProj→ElmishLand.Base.UserPromptBehaviour
- Direction
- ElmishLand.FsProj uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.FsProj, while a change to ElmishLand.FsProj can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.FsProj uses a module listed above it, which is the healthy direction.
20→1 ElmishLand.Generate uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.Generate uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.Generate.Generate→ElmishLand.AppError.AppError
- Direction
- ElmishLand.Generate uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.Generate, while a change to ElmishLand.Generate can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.Generate uses a module listed above it, which is the healthy direction.
20→9 ElmishLand.Generate uses ElmishLand.Base✕
- Connections
- 3 pairs of types, where a type in ElmishLand.Generate uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Generate.Generate→ElmishLand.Base.AbsoluteProjectDirElmishLand.Generate.Generate→ElmishLand.Base.DotnetSdkVersionElmishLand.Generate.Generate→ElmishLand.Base.FilePath
- Direction
- ElmishLand.Generate uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Generate, while a change to ElmishLand.Generate can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Generate uses a module listed above it, which is the healthy direction.
21→1 ElmishLand.PackageVersions uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.PackageVersions uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.PackageVersions.PackageVersions→ElmishLand.AppError.AppError
- Direction
- ElmishLand.PackageVersions uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.PackageVersions, while a change to ElmishLand.PackageVersions can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.PackageVersions uses a module listed above it, which is the healthy direction.
21→10 ElmishLand.PackageVersions uses ElmishLand.Effect✕
- Connections
- 1 pair of types, where a type in ElmishLand.PackageVersions uses a type in ElmishLand.Effect.
- The types involved
ElmishLand.PackageVersions.PackageVersions→ElmishLand.Effect.IEffectEnv
- Direction
- ElmishLand.PackageVersions uses ElmishLand.Effect, so a change to ElmishLand.Effect can break ElmishLand.PackageVersions, while a change to ElmishLand.PackageVersions can't break ElmishLand.Effect.
- Position
- Below the diagonal: ElmishLand.PackageVersions uses a module listed above it, which is the healthy direction.
22→1 ElmishLand.Process uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.Process uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.Process.Process→ElmishLand.AppError.AppError
- Direction
- ElmishLand.Process uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.Process, while a change to ElmishLand.Process can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.Process uses a module listed above it, which is the healthy direction.
22→9 ElmishLand.Process uses ElmishLand.Base✕
- Connections
- 1 pair of types, where a type in ElmishLand.Process uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Process.Process→ElmishLand.Base.FilePath
- Direction
- ElmishLand.Process uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Process, while a change to ElmishLand.Process can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Process uses a module listed above it, which is the healthy direction.
23→1 ElmishLand.Program uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.Program uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.Program.Program→ElmishLand.AppError.AppError
- Direction
- ElmishLand.Program uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.Program, while a change to ElmishLand.Program can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.Program uses a module listed above it, which is the healthy direction.
23→9 ElmishLand.Program uses ElmishLand.Base✕
- Connections
- 1 pair of types, where a type in ElmishLand.Program uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Program.Program→ElmishLand.Base.UserPromptBehaviour
- Direction
- ElmishLand.Program uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Program, while a change to ElmishLand.Program can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Program uses a module listed above it, which is the healthy direction.
23→10 ElmishLand.Program uses ElmishLand.Effect✕
- Connections
- 3 pairs of types, where a type in ElmishLand.Program uses a type in ElmishLand.Effect.
- The types involved
ElmishLand.Program.ConsoleLogger→ElmishLand.Effect.ILogElmishLand.Program.Program→ElmishLand.Effect.IEffectEnvElmishLand.Program.Program→ElmishLand.Effect.ILog
- Direction
- ElmishLand.Program uses ElmishLand.Effect, so a change to ElmishLand.Effect can break ElmishLand.Program, while a change to ElmishLand.Program can't break ElmishLand.Effect.
- Position
- Below the diagonal: ElmishLand.Program uses a module listed above it, which is the healthy direction.
24→1 ElmishLand.Restore uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.Restore uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.Restore.Restore→ElmishLand.AppError.AppError
- Direction
- ElmishLand.Restore uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.Restore, while a change to ElmishLand.Restore can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.Restore uses a module listed above it, which is the healthy direction.
24→9 ElmishLand.Restore uses ElmishLand.Base✕
- Connections
- 3 pairs of types, where a type in ElmishLand.Restore uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Restore.Restore→ElmishLand.Base.AbsoluteProjectDirElmishLand.Restore.Restore→ElmishLand.Base.FilePathElmishLand.Restore.Restore→ElmishLand.Base.UserPromptBehaviour
- Direction
- ElmishLand.Restore uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Restore, while a change to ElmishLand.Restore can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Restore uses a module listed above it, which is the healthy direction.
25→1 ElmishLand.Server uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.Server uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.Server.Server→ElmishLand.AppError.AppError
- Direction
- ElmishLand.Server uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.Server, while a change to ElmishLand.Server can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.Server uses a module listed above it, which is the healthy direction.
25→9 ElmishLand.Server uses ElmishLand.Base✕
- Connections
- 3 pairs of types, where a type in ElmishLand.Server uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Server.Server→ElmishLand.Base.AbsoluteProjectDirElmishLand.Server.Server→ElmishLand.Base.FilePathElmishLand.Server.Server→ElmishLand.Base.UserPromptBehaviour
- Direction
- ElmishLand.Server uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Server, while a change to ElmishLand.Server can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Server uses a module listed above it, which is the healthy direction.
26→1 ElmishLand.Settings uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.Settings uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.Settings.Settings→ElmishLand.AppError.AppError
- Direction
- ElmishLand.Settings uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.Settings, while a change to ElmishLand.Settings can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.Settings uses a module listed above it, which is the healthy direction.
26→9 ElmishLand.Settings uses ElmishLand.Base✕
- Connections
- 1 pair of types, where a type in ElmishLand.Settings uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Settings.Settings→ElmishLand.Base.AbsoluteProjectDir
- Direction
- ElmishLand.Settings uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Settings, while a change to ElmishLand.Settings can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Settings uses a module listed above it, which is the healthy direction.
27→1 ElmishLand.Upgrade uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.Upgrade uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.Upgrade.Upgrade→ElmishLand.AppError.AppError
- Direction
- ElmishLand.Upgrade uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.Upgrade, while a change to ElmishLand.Upgrade can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.Upgrade uses a module listed above it, which is the healthy direction.
27→9 ElmishLand.Upgrade uses ElmishLand.Base✕
- Connections
- 2 pairs of types, where a type in ElmishLand.Upgrade uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Upgrade.Upgrade→ElmishLand.Base.AbsoluteProjectDirElmishLand.Upgrade.Upgrade→ElmishLand.Base.FilePath
- Direction
- ElmishLand.Upgrade uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Upgrade, while a change to ElmishLand.Upgrade can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Upgrade uses a module listed above it, which is the healthy direction.
27→10 ElmishLand.Upgrade uses ElmishLand.Effect✕
- Connections
- 1 pair of types, where a type in ElmishLand.Upgrade uses a type in ElmishLand.Effect.
- The types involved
ElmishLand.Upgrade.Upgrade→ElmishLand.Effect.IEffectEnv
- Direction
- ElmishLand.Upgrade uses ElmishLand.Effect, so a change to ElmishLand.Effect can break ElmishLand.Upgrade, while a change to ElmishLand.Upgrade can't break ElmishLand.Effect.
- Position
- Below the diagonal: ElmishLand.Upgrade uses a module listed above it, which is the healthy direction.
28→26 ElmishLand.Settings.LayoutNameModule uses ElmishLand.Settings✕
- Connections
- 1 pair of types, where a type in ElmishLand.Settings.LayoutNameModule uses a type in ElmishLand.Settings.
- The types involved
ElmishLand.Settings.LayoutNameModule.LayoutNameModule→ElmishLand.Settings.LayoutName
- Direction
- ElmishLand.Settings.LayoutNameModule uses ElmishLand.Settings, so a change to ElmishLand.Settings can break ElmishLand.Settings.LayoutNameModule, while a change to ElmishLand.Settings.LayoutNameModule can't break ElmishLand.Settings.
- Position
- Below the diagonal: ElmishLand.Settings.LayoutNameModule uses a module listed above it, which is the healthy direction.
29→26 ElmishLand.Settings.RenderMethodModule uses ElmishLand.Settings✕
- Connections
- 1 pair of types, where a type in ElmishLand.Settings.RenderMethodModule uses a type in ElmishLand.Settings.
- The types involved
ElmishLand.Settings.RenderMethodModule.RenderMethodModule→ElmishLand.Settings.RenderMethod
- Direction
- ElmishLand.Settings.RenderMethodModule uses ElmishLand.Settings, so a change to ElmishLand.Settings can break ElmishLand.Settings.RenderMethodModule, while a change to ElmishLand.Settings.RenderMethodModule can't break ElmishLand.Settings.
- Position
- Below the diagonal: ElmishLand.Settings.RenderMethodModule uses a module listed above it, which is the healthy direction.
30→26 ElmishLand.Settings.RouteModeModule uses ElmishLand.Settings✕
- Connections
- 1 pair of types, where a type in ElmishLand.Settings.RouteModeModule uses a type in ElmishLand.Settings.
- The types involved
ElmishLand.Settings.RouteModeModule.RouteModeModule→ElmishLand.Settings.RouteMode
- Direction
- ElmishLand.Settings.RouteModeModule uses ElmishLand.Settings, so a change to ElmishLand.Settings can break ElmishLand.Settings.RouteModeModule, while a change to ElmishLand.Settings.RouteModeModule can't break ElmishLand.Settings.
- Position
- Below the diagonal: ElmishLand.Settings.RouteModeModule uses a module listed above it, which is the healthy direction.
31→26 ElmishLand.Settings.RouteParametersModule uses ElmishLand.Settings✕
- Connections
- 1 pair of types, where a type in ElmishLand.Settings.RouteParametersModule uses a type in ElmishLand.Settings.
- The types involved
ElmishLand.Settings.RouteParametersModule.RouteParametersModule→ElmishLand.Settings.RouteParameters
- Direction
- ElmishLand.Settings.RouteParametersModule uses ElmishLand.Settings, so a change to ElmishLand.Settings can break ElmishLand.Settings.RouteParametersModule, while a change to ElmishLand.Settings.RouteParametersModule can't break ElmishLand.Settings.
- Position
- Below the diagonal: ElmishLand.Settings.RouteParametersModule uses a module listed above it, which is the healthy direction.
32→1 ElmishLand.TemplateEngine uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.TemplateEngine uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.TemplateEngine.TemplateEngine→ElmishLand.AppError.AppError
- Direction
- ElmishLand.TemplateEngine uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.TemplateEngine, while a change to ElmishLand.TemplateEngine can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.TemplateEngine uses a module listed above it, which is the healthy direction.
32→9 ElmishLand.TemplateEngine uses ElmishLand.Base✕
- Connections
- 3 pairs of types, where a type in ElmishLand.TemplateEngine uses a type in ElmishLand.Base.
- The types involved
ElmishLand.TemplateEngine.TemplateEngine→ElmishLand.Base.AbsoluteProjectDirElmishLand.TemplateEngine.TemplateEngine→ElmishLand.Base.FilePathElmishLand.TemplateEngine.TemplateEngine→ElmishLand.Base.ProjectName
- Direction
- ElmishLand.TemplateEngine uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.TemplateEngine, while a change to ElmishLand.TemplateEngine can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.TemplateEngine uses a module listed above it, which is the healthy direction.
32→26 ElmishLand.TemplateEngine uses ElmishLand.Settings✕
- Connections
- 1 pair of types, where a type in ElmishLand.TemplateEngine uses a type in ElmishLand.Settings.
- The types involved
ElmishLand.TemplateEngine.TemplateEngine→ElmishLand.Settings.RouteParameters
- Direction
- ElmishLand.TemplateEngine uses ElmishLand.Settings, so a change to ElmishLand.Settings can break ElmishLand.TemplateEngine, while a change to ElmishLand.TemplateEngine can't break ElmishLand.Settings.
- Position
- Below the diagonal: ElmishLand.TemplateEngine uses a module listed above it, which is the healthy direction.
33→1 ElmishLand.AddLayout uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.AddLayout uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.AddLayout.AddLayout→ElmishLand.AppError.AppError
- Direction
- ElmishLand.AddLayout uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.AddLayout, while a change to ElmishLand.AddLayout can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.AddLayout uses a module listed above it, which is the healthy direction.
33→9 ElmishLand.AddLayout uses ElmishLand.Base✕
- Connections
- 5 pairs of types, where a type in ElmishLand.AddLayout uses a type in ElmishLand.Base.
- The types involved
ElmishLand.AddLayout.AddLayout→ElmishLand.Base.AbsoluteProjectDirElmishLand.AddLayout.AddLayout→ElmishLand.Base.FilePathElmishLand.AddLayout.AddLayout→ElmishLand.Base.FsProjPathElmishLand.AddLayout.AddLayout→ElmishLand.Base.UserPromptBehaviourElmishLand.AddLayout.PageUpdate→ElmishLand.Base.FilePath
- Direction
- ElmishLand.AddLayout uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.AddLayout, while a change to ElmishLand.AddLayout can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.AddLayout uses a module listed above it, which is the healthy direction.
33→10 ElmishLand.AddLayout uses ElmishLand.Effect✕
- Connections
- 1 pair of types, where a type in ElmishLand.AddLayout uses a type in ElmishLand.Effect.
- The types involved
ElmishLand.AddLayout.AddLayout→ElmishLand.Effect.ILog
- Direction
- ElmishLand.AddLayout uses ElmishLand.Effect, so a change to ElmishLand.Effect can break ElmishLand.AddLayout, while a change to ElmishLand.AddLayout can't break ElmishLand.Effect.
- Position
- Below the diagonal: ElmishLand.AddLayout uses a module listed above it, which is the healthy direction.
33→32 ElmishLand.AddLayout uses ElmishLand.TemplateEngine✕
- Connections
- 1 pair of types, where a type in ElmishLand.AddLayout uses a type in ElmishLand.TemplateEngine.
- The types involved
ElmishLand.AddLayout.AddLayout→ElmishLand.TemplateEngine.TemplateData
- Direction
- ElmishLand.AddLayout uses ElmishLand.TemplateEngine, so a change to ElmishLand.TemplateEngine can break ElmishLand.AddLayout, while a change to ElmishLand.AddLayout can't break ElmishLand.TemplateEngine.
- Position
- Below the diagonal: ElmishLand.AddLayout uses a module listed above it, which is the healthy direction.
34→1 ElmishLand.Init uses ElmishLand.AppError✕
- Connections
- 1 pair of types, where a type in ElmishLand.Init uses a type in ElmishLand.AppError.
- The types involved
ElmishLand.Init.Init→ElmishLand.AppError.AppError
- Direction
- ElmishLand.Init uses ElmishLand.AppError, so a change to ElmishLand.AppError can break ElmishLand.Init, while a change to ElmishLand.Init can't break ElmishLand.AppError.
- Position
- Below the diagonal: ElmishLand.Init uses a module listed above it, which is the healthy direction.
34→9 ElmishLand.Init uses ElmishLand.Base✕
- Connections
- 4 pairs of types, where a type in ElmishLand.Init uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Init.Init→ElmishLand.Base.AbsoluteProjectDirElmishLand.Init.Init→ElmishLand.Base.DotnetSdkVersionElmishLand.Init.Init→ElmishLand.Base.FilePathElmishLand.Init.Init→ElmishLand.Base.UserPromptBehaviour
- Direction
- ElmishLand.Init uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Init, while a change to ElmishLand.Init can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Init uses a module listed above it, which is the healthy direction.
34→10 ElmishLand.Init uses ElmishLand.Effect✕
- Connections
- 1 pair of types, where a type in ElmishLand.Init uses a type in ElmishLand.Effect.
- The types involved
ElmishLand.Init.Init→ElmishLand.Effect.IEffectEnv
- Direction
- ElmishLand.Init uses ElmishLand.Effect, so a change to ElmishLand.Effect can break ElmishLand.Init, while a change to ElmishLand.Init can't break ElmishLand.Effect.
- Position
- Below the diagonal: ElmishLand.Init uses a module listed above it, which is the healthy direction.
34→32 ElmishLand.Init uses ElmishLand.TemplateEngine✕
- Connections
- 1 pair of types, where a type in ElmishLand.Init uses a type in ElmishLand.TemplateEngine.
- The types involved
ElmishLand.Init.Init→ElmishLand.TemplateEngine.TemplateData
- Direction
- ElmishLand.Init uses ElmishLand.TemplateEngine, so a change to ElmishLand.TemplateEngine can break ElmishLand.Init, while a change to ElmishLand.Init can't break ElmishLand.TemplateEngine.
- Position
- Below the diagonal: ElmishLand.Init uses a module listed above it, which is the healthy direction.
35→9 ElmishLand.Resources uses ElmishLand.Base✕
- Connections
- 1 pair of types, where a type in ElmishLand.Resources uses a type in ElmishLand.Base.
- The types involved
ElmishLand.Resources.Resources→ElmishLand.Base.FilePath
- Direction
- ElmishLand.Resources uses ElmishLand.Base, so a change to ElmishLand.Base can break ElmishLand.Resources, while a change to ElmishLand.Resources can't break ElmishLand.Base.
- Position
- Below the diagonal: ElmishLand.Resources uses a module listed above it, which is the healthy direction.
35→10 ElmishLand.Resources uses ElmishLand.Effect✕
- Connections
- 1 pair of types, where a type in ElmishLand.Resources uses a type in ElmishLand.Effect.
- The types involved
ElmishLand.Resources.Resources→ElmishLand.Effect.ILog
- Direction
- ElmishLand.Resources uses ElmishLand.Effect, so a change to ElmishLand.Effect can break ElmishLand.Resources, while a change to ElmishLand.Resources can't break ElmishLand.Effect.
- Position
- Below the diagonal: ElmishLand.Resources uses a module listed above it, which is the healthy direction.
35→32 ElmishLand.Resources uses ElmishLand.TemplateEngine✕
- Connections
- 9 pairs of types, where a type in ElmishLand.Resources uses a type in ElmishLand.TemplateEngine.
- The types involved
ElmishLand.Resources.AddLayout_template→ElmishLand.TemplateEngine.LayoutElmishLand.Resources.AddPage_template→ElmishLand.TemplateEngine.RouteElmishLand.Resources.App_template→ElmishLand.TemplateEngine.TemplateDataElmishLand.Resources.Command_fs_template→ElmishLand.TemplateEngine.TemplateDataElmishLand.Resources.Layout_fs_template→ElmishLand.TemplateEngine.TemplateDataElmishLand.Resources.Page_fs_template→ElmishLand.TemplateEngine.TemplateDataElmishLand.Resources.Resources→ElmishLand.TemplateEngine.TemplateDataElmishLand.Resources.Routes_template→ElmishLand.TemplateEngine.TemplateDataElmishLand.Resources.Shared_template→ElmishLand.TemplateEngine.TemplateData
- Direction
- ElmishLand.Resources uses ElmishLand.TemplateEngine, so a change to ElmishLand.TemplateEngine can break ElmishLand.Resources, while a change to ElmishLand.Resources can't break ElmishLand.TemplateEngine.
- Position
- Below the diagonal: ElmishLand.Resources 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 | 9 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Top priorities: Resolve the 96 Outdated (npm) finding(s) in Dependency Hygiene; Resolve the 15 Low coverage finding(s) in Code Coverage — start with Program.fs, Upgrade.fs, AddLayout.fs; Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 96 Outdated (npm) finding(s) in Dependency Hygiene. | +8.6 pts | Medium | Dependency Hygiene |
| Resolve the 15 Low coverage finding(s) in Code Coverage — start with Program.fs, Upgrade.fs, AddLayout.fs. | +6.6 pts | Medium | Code Coverage |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with elmish-land.fsproj. | +3.3 pts | Low | ADR Quality |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +3.4 pts | Medium | Deployment & Rollback |
| 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. | +2.6 pts | Medium | Architecture documentation |
| Add a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) so orchestrators and load balancers can probe liveness/readiness. | +1.4 pts | Medium | Observability |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.2 pts | Medium | Documentation (README) |
| Resolve the 1 No test project references backwards-compability-with-1-0-4 finding(s) in Code Coverage — start with backwards-compability-with-1-0-4.fsproj. | +0.4 pts | Low | Code Coverage |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/Commands/AddLayout.fs | 5.5 | Mixed | Cyclomatic Complexity: AddLayout.addCompileIncludeToProject (cyclomatic 20) |
| src/FableOutput.fs | 5.5 | Mixed | Cyclomatic Complexity: FableOutput.detectLayoutMismatch (cyclomatic 37) |
| src/FsProj.fs | 5.6 | Mixed | Cyclomatic Complexity: FsProj.previewAddCompileIncludeSnippet (cyclomatic 41) |
| src/Commands/AddPage.fs | 5.9 | Mixed | Cyclomatic Complexity: AddPage.addCompileIncludeToProject (cyclomatic 25) |
| src/Commands/Server.fs | 6.3 | Mixed | Cyclomatic Complexity: Server.fableWatch (cyclomatic 18) |
| src/Commands/Upgrade.fs | 6.3 | Mixed | Code Duplication: Duplicated block (16 lines × 2) |
| src/Commands/Build.fs | 7.0 | Mixed | Cognitive Complexity: Build.build (cognitive 36) |
| src/Base.fs | 7.0 | Mixed | Code Duplication: Duplicated block (9 lines × 2) |
| src/TemplateEngine.fs | 7.8 | Mixed | Cyclomatic Complexity: TemplateEngine.fileToRoute (cyclomatic 26) |
| src/Process.fs | 8.5 | Near-clean | Cognitive Complexity: Process.runProcessInternal (cognitive 16) |
| integration-tests/backwards-compability-with-1-0-4/src/Pages/Layout.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (24 lines × 2) |
| integration-tests/backwards-compability-with-1-0-4/src/Pages/Page.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (20 lines × 2) |
| src/Program.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Program.fs |
| src/Commands/Restore.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Commands/Restore.fs |
| src/Commands/Init.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Commands/Init.fs |
| src/Generate.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Generate.fs |
| src/Resources.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Resources.fs |
| src/Settings.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Settings.fs |
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 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 40 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, 68 of 751 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
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D15 Churn × Complexity Hotspots — 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 hotspot's complexity is meant to be the worst body its churn actually touched. For src/TemplateEngine.fs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- 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 (8 contributor(s) across 327 commit(s) sampled, automation and bot accounts excluded). One of them holds 82% of the history; the other 7 hold 2.6% 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.
- D21 Naming Consistency — evaluation did not complete — Naming Consistency not included (check did not complete) — excluded from the score.
- D22 Internal API 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- 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.
- D27 Navigability — evaluation did not complete — Navigability not included (check did not complete) — excluded from the score.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FsProj.previewAddCompileIncludeSnippet at 41. 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 Program.handleAppResult at 16 — 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/Program.fs (Program.handleAppResult at 16). 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.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with FsProj.previewAddCompileIncludeSnippet (cyclomatic 41), FableOutput.detectLayoutMismatch (cyclomatic 37), TemplateEngine.fileToRoute (cyclomatic 26). — 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 7 together lifts Cyclomatic Complexity from 7.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
14 method(s) exceeded the cognitive complexity threshold of 15; the worst was FsProj.previewAddCompileIncludeSnippet at 88.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with FsProj.previewAddCompileIncludeSnippet (cognitive 88), FableOutput.detectLayoutMismatch (cognitive 87). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 3.3 to about 4.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
13 duplicated block group(s) detected. 7.4 % of the production lines (302 of 4,058) are in a reported copy. One further row reports members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 14 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Base.fs, FsProj.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Near-duplicate member pair (103 shared lines) finding(s) in Code Duplication — start with AddLayout.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (30–31 lines × 2) finding(s) in Code Duplication — start with AddLayout.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
4 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 1 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 32.6% — 15 file(s) below 50%.
What to do
- Resolve the 15 Low coverage finding(s) in Code Coverage — start with Program.fs, Upgrade.fs, AddLayout.fs. — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 1 No test project references backwards-compability-with-1-0-4 finding(s) in Code Coverage — start with backwards-compability-with-1-0-4.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references using-commands-from-shared-module-does-not-wo… finding(s) in Code Coverage — start with using-commands-from-shared-module-does-not-work-27.fsproj. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 · Dependency Hygiene
8 outdated, 0 vulnerable, 1 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 669 outdated of 1070 package(s) across 3 lockfile(s).
What to do
- Resolve the 96 Outdated (npm) finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (96 recommendation-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 115 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 9 direct `PackageReference`(s), and 106 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: src/TemplateEngine.fs (4×26=104)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with TemplateEngine.fs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 25 document(s) read across 4 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 elmish-land.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 2 build units (MSBuild, npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
9 finding(s): 0 critical, 7 high, 2 medium, 0 low. 7 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
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 7 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 (7 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 16 of the 29 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 4 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
AX8 · Test isolation
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.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- Add a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) so orchestrators and load balancers can probe liveness/readiness.
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 2 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
- `Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Directory.Packages.props:7
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70% | Checked 4 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 67% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 52% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 73% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 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 — Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~3343 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D21 Naming Consistency — Naming Consistency not included (check did not complete)
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ 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
- D27 Navigability — Navigability not included (check did not complete)
- 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
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 38 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 20 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not 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 — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- 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 — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 7 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 58 finding(s)
- Low coverage: src/Program.fs src/Program.fs:1
- Low coverage: src/Commands/Upgrade.fs src/Commands/Upgrade.fs:1
- Low coverage: src/Commands/AddLayout.fs src/Commands/AddLayout.fs:1
- Low coverage: src/Commands/AddPage.fs src/Commands/AddPage.fs:1
- Low coverage: src/Commands/Server.fs src/Commands/Server.fs:1
- Low coverage: src/Commands/Build.fs src/Commands/Build.fs:1
- Low coverage: src/Commands/Restore.fs src/Commands/Restore.fs:1
- Low coverage: src/Commands/Init.fs src/Commands/Init.fs:1
- Low coverage: src/FableOutput.fs src/FableOutput.fs:1
- Low coverage: src/Generate.fs src/Generate.fs:1
- Low coverage: src/Resources.fs src/Resources.fs:1
- Low coverage: src/FsProj.fs src/FsProj.fs:1
- Low coverage: src/Settings.fs src/Settings.fs:1
- Low coverage: src/PackageVersions.fs src/PackageVersions.fs:1
- Low coverage: src/Base.fs src/Base.fs:1
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) src/Base.fs:208
- Duplicated block (9 lines × 2) src/FsProj.fs:228
- FsProj.previewAddCompileIncludeSnippet (cyclomatic 41) src/FsProj.fs:311
- FableOutput.detectLayoutMismatch (cyclomatic 37) src/FableOutput.fs:30
- TemplateEngine.fileToRoute (cyclomatic 26) src/TemplateEngine.fs:286
- AddPage.addCompileIncludeToProject (cyclomatic 25) src/Commands/AddPage.fs:43
- AddLayout.addCompileIncludeToProject (cyclomatic 20) src/Commands/AddLayout.fs:159
- Server.fableWatch (cyclomatic 18) src/Commands/Server.fs:16
- FableOutput.promptForAutoFix (cyclomatic 16) src/FableOutput.fs:376
- Deprecated: xunit Directory.Packages.props:14
- Hotspot: src/TemplateEngine.fs src/TemplateEngine.fs:286
- FsProj.previewAddCompileIncludeSnippet (cognitive 88) src/FsProj.fs:311
- FableOutput.detectLayoutMismatch (cognitive 87) src/FableOutput.fs:30
- FableOutput.promptForAutoFix (cognitive 52) src/FableOutput.fs:376
- AddPage.addCompileIncludeToProject (cognitive 51) src/Commands/AddPage.fs:43
- TemplateEngine.fileToRoute (cognitive 49) src/TemplateEngine.fs:286
- FsProj.previewPageFilesReordering (cognitive 45) src/FsProj.fs:91
- AddLayout.addCompileIncludeToProject (cognitive 43) src/Commands/AddLayout.fs:159
- Build.build (cognitive 36) src/Commands/Build.fs:54
- FsProj.ensurePageFilesLast (cognitive 25) src/FsProj.fs:12
- Server.fableWatch (cognitive 21) src/Commands/Server.fs:16
- FableOutput.findPagesWithWrongLayout (cognitive 21) src/FableOutput.fs:334
- FableOutput.fixLayoutReference (cognitive 19) src/FableOutput.fs:269
- FableOutput.processOutput (cognitive 18) src/FableOutput.fs:175
- Process.runProcessInternal (cognitive 16) src/Process.fs:34
- REDACTED
- REDACTED
- Near-duplicate member pair (103 shared lines) src/Commands/AddLayout.fs:1
- Duplicated block (30–31 lines × 2) src/Commands/AddLayout.fs:269
- Duplicated block (22–23 lines × 2) src/Commands/AddLayout.fs:165
- Duplicated block (17 lines × 2) src/Commands/AddLayout.fs:192
- Duplicated block (12–13 lines × 2) src/Commands/AddLayout.fs:127
- Duplicated block (11–12 lines × 2) src/Commands/AddLayout.fs:154
- Duplicated block (11 lines × 2) src/Commands/AddLayout.fs:211
- Duplicated block (16 lines × 2) src/Commands/Upgrade.fs:114
- Duplicated block (8–9 lines × 2) src/Commands/AddPage.fs:156
- Duplicated block (7 lines × 2) src/Commands/Upgrade.fs:258
- Duplicated block (24 lines × 2) integration-tests/backwards-compability-with-1-0-4/src/Pages/Layout.fs:1
- Duplicated block (20 lines × 2) integration-tests/backwards-compability-with-1-0-4/src/Pages/Page.fs:1
- No test project references backwards-compability-with-1-0-4 integration-tests/backwards-compability-with-1-0-4/backwards-compability-with-1-0-4.fsproj
- No test project references using-commands-from-shared-module-does-not-work-27 integration-tests/using-commands-from-shared-module-does-not-work-27/using-commands-from-shared-module-does-not-work-27.fsproj
Minor — 105 finding(s)
- Outdated (npm): @jsonjoy.com/base64
- Outdated (npm): @jsonjoy.com/buffers
- Outdated (npm): @jsonjoy.com/codegen
- Outdated (npm): @jsonjoy.com/json-pack
- Outdated (npm): @jsonjoy.com/json-pointer
- Outdated (npm): @jsonjoy.com/util
- Outdated (npm): @pnpm/config.env-replace
- Outdated (npm): @pnpm/network.ca-file
- Outdated (npm): @sindresorhus/is
- Outdated (npm): @types/eslint-scope
- Outdated (npm): @types/mime
- Outdated (npm): @types/node
- Outdated (npm): balanced-match
- Outdated (npm): brace-expansion
- Outdated (npm): cacheable-request
- Outdated (npm): camelcase
- Outdated (npm): chokidar
- Outdated (npm): clean-stack
- Outdated (npm): commander
- Outdated (npm): content-disposition
- Outdated (npm): copy-webpack-plugin
- Outdated (npm): css-minimizer-webpack-plugin
- Outdated (npm): cssnano
- Outdated (npm): cssnano-preset-advanced
- Outdated (npm): cssnano-preset-default
- No ADRs found src/elmish-land.fsproj:5
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:6
- No dependency-update automation Directory.Packages.props:7
- Duplicated predicate src/Commands/AddLayout.fs:116
Minor — 581 finding(s)
- Outdated (npm): @algolia/abtesting
- Outdated (npm): @algolia/autocomplete-core
- Outdated (npm): @algolia/autocomplete-js
- Outdated (npm): @algolia/autocomplete-plugin-algolia-insights
- Outdated (npm): @algolia/autocomplete-preset-algolia
- Outdated (npm): @algolia/autocomplete-shared
- Outdated (npm): @algolia/autocomplete-theme-classic
- Outdated (npm): @algolia/client-abtesting
- Outdated (npm): @algolia/client-analytics
- Outdated (npm): @algolia/client-common
- Outdated (npm): @algolia/client-insights
- Outdated (npm): @algolia/client-personalization
- Outdated (npm): @algolia/client-query-suggestions
- Outdated (npm): @algolia/client-search
- Outdated (npm): @algolia/ingestion
- Outdated (npm): @algolia/logger-console
- Outdated (npm): @algolia/monitoring
- Outdated (npm): @algolia/recommend
- Outdated (npm): @algolia/requester-browser-xhr
- Outdated (npm): @algolia/requester-fetch
- Outdated (npm): @algolia/requester-node-http
- Outdated (npm): @babel/code-frame
- Outdated (npm): @babel/compat-data
- Outdated (npm): @babel/core
- Outdated (npm): @babel/generator
- Outdated: Handlebars.Net
- Outdated: Orsak
- Outdated: FSharp.Compiler.Service
- Outdated: Ionide.ProjInfo
- Outdated: Ionide.ProjInfo.FCS
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: xunit
- Outdated: xunit.runner.visualstudio
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-3b3b67a20bfa4a16b3ae40dde2f78231/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-3b3b67a20bfa4a16b3ae40dde2f78231/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 . | 9 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list elmish-land.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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |