Executive summary
AngelMunoz/Perla is rated At risk because critical security findings are open. It scores 48 out of 100, which the At risk rating leaves unchanged.
Code Health, at 41, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 4 points. Removing the copied code would lift Code Health itself, also worth about 4. Raising Code Health to 70 would lift the score to about 53.
Eight settings leave the servers or containers unsafe. Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two pipeline steps run downloads nobody checks. Correcting the unsafe settings, pinning each tool to an exact version and checking each download against a checksum would close these risks. Updating the vulnerable packages would fix the package with a known security hole. The page that doesn't say its language needs its language set.
The product code is 13,511 lines, about €18,000 to rebuild.
If Code Health rose from 41 to 70, the lowest score rated Strong, the score would rise from 48 to about 53.
Rebuild cost: about €18,000 · Estimate
| Cost to rebuild | €6,100 to €31,000, for 102 to 323 hours of work, about 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.7 at a score of 48. 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: 13,511 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 Fable.Mocha | 2 Fable.QUnit | 3 Logger | 4 Plugins | 5 PkgManager.RequestHandler | 6 Plugins.Registry | 7 RequestHandler | 8 Extensibility | 9 PkgManager | 10 Types | 11 VirtualFs | 12 Build.Build | 13 Configuration | 14 Fable | 15 Handlers | 16 Json | 17 Json.PerlaConfig | 18 Testing.Print.LiveDashboard | 19 Commands | 20 Configuration.ConfigExtraction | 21 Configuration.ConfigExtraction.FromFields | 22 Database | 23 FileSystem | 24 Esbuild | 25 Scaffolding | 26 SuaveService.PerlaHandlers | 27 SuaveService.SpaFallback | 28 Warmup.Recover | 29 Build | 30 Perla | 31 Handlers.Handlers | 32 ImportMaps | 33 Patterns | 34 SuaveService | 35 SuaveService.TestingHandlers | 36 Testing | 37 Warmup.Check | 38 Testing.Print | 39 Testing.Testing | 40 Testing.TestingServiceModule |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Fable.Mocha | ||||||||||||||||||||||||||||||||||||||||
| 2 Fable.QUnit | ||||||||||||||||||||||||||||||||||||||||
| 3 Logger | ||||||||||||||||||||||||||||||||||||||||
| 4 Plugins | ||||||||||||||||||||||||||||||||||||||||
| 5 PkgManager.RequestHandler | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 Plugins.Registry | 3 | |||||||||||||||||||||||||||||||||||||||
| 7 RequestHandler | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 Extensibility | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 PkgManager | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Types | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 VirtualFs | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Build.Build | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 Configuration | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 Fable | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 Handlers | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 Json | 1 | 8 | ||||||||||||||||||||||||||||||||||||||
| 17 Json.PerlaConfig | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 Testing.Print.LiveDashboard | 3 | |||||||||||||||||||||||||||||||||||||||
| 19 Commands | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 Configuration.ConfigExtraction | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 Configuration.ConfigExtraction.FromFields | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 Database | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 FileSystem | 1 | 1 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 24 Esbuild | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 Scaffolding | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 SuaveService.PerlaHandlers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 SuaveService.SpaFallback | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 Warmup.Recover | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 Build | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 30 Perla | 2 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||
| 31 Handlers.Handlers | 9 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 ImportMaps | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 Patterns | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||
| 34 SuaveService | 3 | 3 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 35 SuaveService.TestingHandlers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 Testing | 1 | 8 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 Warmup.Check | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 Testing.Print | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 Testing.Testing | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 Testing.TestingServiceModule | 1 | 3 |
5→9 PkgManager.RequestHandler uses PkgManager part of a loop✕
- Connections
- 2 pairs of types, where a type in PkgManager.RequestHandler uses a type in PkgManager.
- The types involved
Perla.PkgManager.RequestHandler.JspmService→Perla.PkgManager.DownloadResponsePerla.PkgManager.RequestHandler.JspmService→Perla.PkgManager.GeneratorResponseKind
- Direction
- PkgManager.RequestHandler uses PkgManager, so a change to PkgManager can break PkgManager.RequestHandler, while a change to PkgManager.RequestHandler can't break PkgManager.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→4 Plugins.Registry uses Plugins✕
- Connections
- 3 pairs of types, where a type in Plugins.Registry uses a type in Plugins.
- The types involved
Perla.Plugins.Registry.PluginManager→Perla.Plugins.FileTransformPerla.Plugins.Registry.PluginManager→Perla.Plugins.PluginInfoPerla.Plugins.Registry.PluginManager→Perla.Plugins.RunnablePlugin
- Direction
- Plugins.Registry uses Plugins, so a change to Plugins can break Plugins.Registry, while a change to Plugins.Registry can't break Plugins.
- Position
- Below the diagonal: Plugins.Registry uses a module listed above it, which is the healthy direction.
7→30 RequestHandler uses Perla part of a loop✕
- Connections
- 2 pairs of types, where a type in RequestHandler uses a type in Perla.
- The types involved
Perla.RequestHandler.RequestHandlerArgs→Perla.PerlaDirectoriesPerla.RequestHandler.RequestHandlerArgs→Perla.PlatformOps
- Direction
- RequestHandler uses Perla, so a change to Perla can break RequestHandler, while a change to RequestHandler can't break Perla.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→4 Extensibility uses Plugins✕
- Connections
- 3 pairs of types, where a type in Extensibility uses a type in Plugins.
- The types involved
Perla.Extensibility.ExtensibilityService→Perla.Plugins.FileTransformPerla.Extensibility.ExtensibilityService→Perla.Plugins.PluginInfoPerla.Extensibility.ExtensibilityService→Perla.Plugins.RunnablePlugin
- Direction
- Extensibility uses Plugins, so a change to Plugins can break Extensibility, while a change to Extensibility can't break Plugins.
- Position
- Below the diagonal: Extensibility uses a module listed above it, which is the healthy direction.
8→6 Extensibility uses Plugins.Registry✕
- Connections
- 1 pair of types, where a type in Extensibility uses a type in Plugins.Registry.
- The types involved
Perla.Extensibility.ExtensibilityService→Perla.Plugins.Registry.PluginLoadError
- Direction
- Extensibility uses Plugins.Registry, so a change to Plugins.Registry can break Extensibility, while a change to Extensibility can't break Plugins.Registry.
- Position
- Below the diagonal: Extensibility uses a module listed above it, which is the healthy direction.
9→5 PkgManager uses PkgManager.RequestHandler✕
- Connections
- 1 pair of types, where a type in PkgManager uses a type in PkgManager.RequestHandler.
- The types involved
Perla.PkgManager.PkgManagerServiceArgs→Perla.PkgManager.RequestHandler.JspmService
- Direction
- PkgManager uses PkgManager.RequestHandler, so a change to PkgManager.RequestHandler can break PkgManager, while a change to PkgManager can't break PkgManager.RequestHandler.
- Position
- Below the diagonal: PkgManager uses a module listed above it, which is the healthy direction.
10→9 Types uses PkgManager✕
- Connections
- 1 pair of types, where a type in Types uses a type in PkgManager.
- The types involved
Perla.Types.PerlaConfig→Perla.PkgManager.DownloadProvider
- Direction
- Types uses PkgManager, so a change to PkgManager can break Types, while a change to Types can't break PkgManager.
- Position
- Below the diagonal: Types uses a module listed above it, which is the healthy direction.
11→8 VirtualFs uses Extensibility✕
- Connections
- 1 pair of types, where a type in VirtualFs uses a type in Extensibility.
- The types involved
Perla.VirtualFs.VirtualFileSystemArgs→Perla.Extensibility.ExtensibilityService
- Direction
- VirtualFs uses Extensibility, so a change to Extensibility can break VirtualFs, while a change to VirtualFs can't break Extensibility.
- Position
- Below the diagonal: VirtualFs uses a module listed above it, which is the healthy direction.
12→9 Build.Build uses PkgManager✕
- Connections
- 1 pair of types, where a type in Build.Build uses a type in PkgManager.
- The types involved
Perla.Build.Build.Build→Perla.PkgManager.ImportMap
- Direction
- Build.Build uses PkgManager, so a change to PkgManager can break Build.Build, while a change to Build.Build can't break PkgManager.
- Position
- Below the diagonal: Build.Build uses a module listed above it, which is the healthy direction.
12→10 Build.Build uses Types✕
- Connections
- 1 pair of types, where a type in Build.Build uses a type in Types.
- The types involved
Perla.Build.Build.Build→Perla.Types.PerlaConfig
- Direction
- Build.Build uses Types, so a change to Types can break Build.Build, while a change to Build.Build can't break Types.
- Position
- Below the diagonal: Build.Build uses a module listed above it, which is the healthy direction.
13→10 Configuration uses Types✕
- Connections
- 3 pairs of types, where a type in Configuration uses a type in Types.
- The types involved
Perla.Configuration.ConfigurationManager→Perla.Types.PerlaConfigPerla.Configuration.TestingField→Perla.Types.BrowserPerla.Configuration.TestingField→Perla.Types.BrowserMode
- Direction
- Configuration uses Types, so a change to Types can break Configuration, while a change to Configuration can't break Types.
- Position
- Below the diagonal: Configuration uses a module listed above it, which is the healthy direction.
14→10 Fable uses Types✕
- Connections
- 1 pair of types, where a type in Fable uses a type in Types.
- The types involved
Perla.Fable.FableService→Perla.Types.FableConfig
- Direction
- Fable uses Types, so a change to Types can break Fable, while a change to Fable can't break Types.
- Position
- Below the diagonal: Fable uses a module listed above it, which is the healthy direction.
14→30 Fable uses Perla part of a loop✕
- Connections
- 1 pair of types, where a type in Fable uses a type in Perla.
- The types involved
Perla.Fable.FableArgs→Perla.PlatformOps
- Direction
- Fable uses Perla, so a change to Perla can break Fable, while a change to Fable can't break Perla.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→9 Handlers uses PkgManager✕
- Connections
- 1 pair of types, where a type in Handlers uses a type in PkgManager.
- The types involved
Perla.Handlers.InstallOptions→Perla.PkgManager.DownloadProvider
- Direction
- Handlers uses PkgManager, so a change to PkgManager can break Handlers, while a change to Handlers can't break PkgManager.
- Position
- Below the diagonal: Handlers uses a module listed above it, which is the healthy direction.
15→10 Handlers uses Types✕
- Connections
- 2 pairs of types, where a type in Handlers uses a type in Types.
- The types involved
Perla.Handlers.TestingOptions→Perla.Types.BrowserPerla.Handlers.TestingOptions→Perla.Types.BrowserMode
- Direction
- Handlers uses Types, so a change to Types can break Handlers, while a change to Handlers can't break Types.
- Position
- Below the diagonal: Handlers uses a module listed above it, which is the healthy direction.
16→9 Json uses PkgManager✕
- Connections
- 1 pair of types, where a type in Json uses a type in PkgManager.
- The types involved
Perla.Json.DecodedPerlaConfig→Perla.PkgManager.DownloadProvider
- Direction
- Json uses PkgManager, so a change to PkgManager can break Json, while a change to Json can't break PkgManager.
- Position
- Below the diagonal: Json uses a module listed above it, which is the healthy direction.
16→10 Json uses Types✕
- Connections
- 8 pairs of types, where a type in Json uses a type in Types.
- The types involved
Perla.Json.DecodedPerlaConfig→Perla.Types.PkgDependencyPerla.Json.DecodedTesting→Perla.Types.BrowserPerla.Json.DecodedTesting→Perla.Types.BrowserModePerla.Json.DecodedTesting→Perla.Types.TestFrameworkPerla.Json.PerlaConfigSection→Perla.Types.BuildConfigPerla.Json.PerlaConfigSection→Perla.Types.DevServerConfigPerla.Json.PerlaConfigSection→Perla.Types.FableConfigPerla.Json.PerlaConfigSection→Perla.Types.PkgDependency
- Direction
- Json uses Types, so a change to Types can break Json, while a change to Json can't break Types.
- Position
- Below the diagonal: Json uses a module listed above it, which is the healthy direction.
17→9 Json.PerlaConfig uses PkgManager✕
- Connections
- 1 pair of types, where a type in Json.PerlaConfig uses a type in PkgManager.
- The types involved
Perla.Json.PerlaConfig.PerlaWritableField→Perla.PkgManager.DownloadProvider
- Direction
- Json.PerlaConfig uses PkgManager, so a change to PkgManager can break Json.PerlaConfig, while a change to Json.PerlaConfig can't break PkgManager.
- Position
- Below the diagonal: Json.PerlaConfig uses a module listed above it, which is the healthy direction.
17→10 Json.PerlaConfig uses Types✕
- Connections
- 2 pairs of types, where a type in Json.PerlaConfig uses a type in Types.
- The types involved
Perla.Json.PerlaConfig.PerlaConfig→Perla.Types.PerlaConfigPerla.Json.PerlaConfig.PerlaWritableField→Perla.Types.PkgDependency
- Direction
- Json.PerlaConfig uses Types, so a change to Types can break Json.PerlaConfig, while a change to Json.PerlaConfig can't break Types.
- Position
- Below the diagonal: Json.PerlaConfig uses a module listed above it, which is the healthy direction.
18→10 Testing.Print.LiveDashboard uses Types✕
- Connections
- 3 pairs of types, where a type in Testing.Print.LiveDashboard uses a type in Types.
- The types involved
Perla.Testing.Print.LiveDashboard.LiveDashboard→Perla.Types.TestEventPerla.Testing.Print.LiveDashboard.TestResult→Perla.Types.TestPerla.Testing.Print.LiveDashboard.TestRunState→Perla.Types.TestStats
- Direction
- Testing.Print.LiveDashboard uses Types, so a change to Types can break Testing.Print.LiveDashboard, while a change to Testing.Print.LiveDashboard can't break Types.
- Position
- Below the diagonal: Testing.Print.LiveDashboard uses a module listed above it, which is the healthy direction.
19→9 Commands uses PkgManager✕
- Connections
- 1 pair of types, where a type in Commands uses a type in PkgManager.
- The types involved
Perla.Commands.PerlaOptions→Perla.PkgManager.DownloadProvider
- Direction
- Commands uses PkgManager, so a change to PkgManager can break Commands, while a change to Commands can't break PkgManager.
- Position
- Below the diagonal: Commands uses a module listed above it, which is the healthy direction.
19→10 Commands uses Types✕
- Connections
- 1 pair of types, where a type in Commands uses a type in Types.
- The types involved
Perla.Commands.PerlaOptions→Perla.Types.Browser
- Direction
- Commands uses Types, so a change to Types can break Commands, while a change to Commands can't break Types.
- Position
- Below the diagonal: Commands uses a module listed above it, which is the healthy direction.
19→15 Commands uses Handlers✕
- Connections
- 1 pair of types, where a type in Commands uses a type in Handlers.
- The types involved
Perla.Commands.PerlaOptions→Perla.Handlers.ListFormat
- Direction
- Commands uses Handlers, so a change to Handlers can break Commands, while a change to Commands can't break Handlers.
- Position
- Below the diagonal: Commands uses a module listed above it, which is the healthy direction.
20→10 Configuration.ConfigExtraction uses Types✕
- Connections
- 1 pair of types, where a type in Configuration.ConfigExtraction uses a type in Types.
- The types involved
Perla.Configuration.ConfigExtraction.ConfigExtraction→Perla.Types.PerlaConfig
- Direction
- Configuration.ConfigExtraction uses Types, so a change to Types can break Configuration.ConfigExtraction, while a change to Configuration.ConfigExtraction can't break Types.
- Position
- Below the diagonal: Configuration.ConfigExtraction uses a module listed above it, which is the healthy direction.
20→13 Configuration.ConfigExtraction uses Configuration✕
- Connections
- 2 pairs of types, where a type in Configuration.ConfigExtraction uses a type in Configuration.
- The types involved
Perla.Configuration.ConfigExtraction.ConfigExtraction→Perla.Configuration.DevServerFieldPerla.Configuration.ConfigExtraction.ConfigExtraction→Perla.Configuration.TestingField
- Direction
- Configuration.ConfigExtraction uses Configuration, so a change to Configuration can break Configuration.ConfigExtraction, while a change to Configuration.ConfigExtraction can't break Configuration.
- Position
- Below the diagonal: Configuration.ConfigExtraction uses a module listed above it, which is the healthy direction.
21→10 Configuration.ConfigExtraction.FromFields uses Types✕
- Connections
- 2 pairs of types, where a type in Configuration.ConfigExtraction.FromFields uses a type in Types.
- The types involved
Perla.Configuration.ConfigExtraction.FromFields.FromFields→Perla.Types.DevServerConfigPerla.Configuration.ConfigExtraction.FromFields.FromFields→Perla.Types.TestConfig
- Direction
- Configuration.ConfigExtraction.FromFields uses Types, so a change to Types can break Configuration.ConfigExtraction.FromFields, while a change to Configuration.ConfigExtraction.FromFields can't break Types.
- Position
- Below the diagonal: Configuration.ConfigExtraction.FromFields uses a module listed above it, which is the healthy direction.
21→13 Configuration.ConfigExtraction.FromFields uses Configuration✕
- Connections
- 2 pairs of types, where a type in Configuration.ConfigExtraction.FromFields uses a type in Configuration.
- The types involved
Perla.Configuration.ConfigExtraction.FromFields.FromFields→Perla.Configuration.DevServerFieldPerla.Configuration.ConfigExtraction.FromFields.FromFields→Perla.Configuration.TestingField
- Direction
- Configuration.ConfigExtraction.FromFields uses Configuration, so a change to Configuration can break Configuration.ConfigExtraction.FromFields, while a change to Configuration.ConfigExtraction.FromFields can't break Configuration.
- Position
- Below the diagonal: Configuration.ConfigExtraction.FromFields uses a module listed above it, which is the healthy direction.
22→16 Database uses Json✕
- Connections
- 1 pair of types, where a type in Database uses a type in Json.
- The types involved
Perla.Database.TemplateRepository→Perla.Json.DecodedTemplateConfiguration
- Direction
- Database uses Json, so a change to Json can break Database, while a change to Database can't break Json.
- Position
- Below the diagonal: Database uses a module listed above it, which is the healthy direction.
22→30 Database uses Perla part of a loop✕
- Connections
- 1 pair of types, where a type in Database uses a type in Perla.
- The types involved
Perla.Database.PerlaDatabaseArgs→Perla.PerlaDirectories
- Direction
- Database uses Perla, so a change to Perla can break Database, while a change to Database can't break Perla.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→7 FileSystem uses RequestHandler✕
- Connections
- 1 pair of types, where a type in FileSystem uses a type in RequestHandler.
- The types involved
Perla.FileSystem.PerlaFsManagerArgs→Perla.RequestHandler.RequestHandler
- Direction
- FileSystem uses RequestHandler, so a change to RequestHandler can break FileSystem, while a change to FileSystem can't break RequestHandler.
- Position
- Below the diagonal: FileSystem uses a module listed above it, which is the healthy direction.
23→9 FileSystem uses PkgManager✕
- Connections
- 1 pair of types, where a type in FileSystem uses a type in PkgManager.
- The types involved
Perla.FileSystem.PerlaFsManager→Perla.PkgManager.ImportMap
- Direction
- FileSystem uses PkgManager, so a change to PkgManager can break FileSystem, while a change to FileSystem can't break PkgManager.
- Position
- Below the diagonal: FileSystem uses a module listed above it, which is the healthy direction.
23→10 FileSystem uses Types✕
- Connections
- 2 pairs of types, where a type in FileSystem uses a type in Types.
- The types involved
Perla.FileSystem.PerlaFsManager→Perla.Types.BuildConfigPerla.FileSystem.PerlaFsManager→Perla.Types.PerlaConfig
- Direction
- FileSystem uses Types, so a change to Types can break FileSystem, while a change to FileSystem can't break Types.
- Position
- Below the diagonal: FileSystem uses a module listed above it, which is the healthy direction.
23→17 FileSystem uses Json.PerlaConfig✕
- Connections
- 1 pair of types, where a type in FileSystem uses a type in Json.PerlaConfig.
- The types involved
Perla.FileSystem.PerlaFsManager→Perla.Json.PerlaConfig.PerlaWritableField
- Direction
- FileSystem uses Json.PerlaConfig, so a change to Json.PerlaConfig can break FileSystem, while a change to FileSystem can't break Json.PerlaConfig.
- Position
- Below the diagonal: FileSystem uses a module listed above it, which is the healthy direction.
23→30 FileSystem uses Perla part of a loop✕
- Connections
- 2 pairs of types, where a type in FileSystem uses a type in Perla.
- The types involved
Perla.FileSystem.PerlaFsManagerArgs→Perla.PerlaDirectoriesPerla.FileSystem.PerlaFsManagerArgs→Perla.PlatformOps
- Direction
- FileSystem uses Perla, so a change to Perla can break FileSystem, while a change to FileSystem can't break Perla.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→4 Esbuild uses Plugins✕
- Connections
- 1 pair of types, where a type in Esbuild uses a type in Plugins.
- The types involved
Perla.Esbuild.EsbuildService→Perla.Plugins.PluginInfo
- Direction
- Esbuild uses Plugins, so a change to Plugins can break Esbuild, while a change to Esbuild can't break Plugins.
- Position
- Below the diagonal: Esbuild uses a module listed above it, which is the healthy direction.
24→10 Esbuild uses Types✕
- Connections
- 1 pair of types, where a type in Esbuild uses a type in Types.
- The types involved
Perla.Esbuild.EsbuildService→Perla.Types.EsbuildConfig
- Direction
- Esbuild uses Types, so a change to Types can break Esbuild, while a change to Esbuild can't break Types.
- Position
- Below the diagonal: Esbuild uses a module listed above it, which is the healthy direction.
24→23 Esbuild uses FileSystem✕
- Connections
- 1 pair of types, where a type in Esbuild uses a type in FileSystem.
- The types involved
Perla.Esbuild.EsbuildServiceArgs→Perla.FileSystem.PerlaFsManager
- Direction
- Esbuild uses FileSystem, so a change to FileSystem can break Esbuild, while a change to Esbuild can't break FileSystem.
- Position
- Below the diagonal: Esbuild uses a module listed above it, which is the healthy direction.
24→30 Esbuild uses Perla part of a loop✕
- Connections
- 1 pair of types, where a type in Esbuild uses a type in Perla.
- The types involved
Perla.Esbuild.EsbuildServiceArgs→Perla.PlatformOps
- Direction
- Esbuild uses Perla, so a change to Perla can break Esbuild, while a change to Esbuild can't break Perla.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→22 Scaffolding uses Database✕
- Connections
- 7 pairs of types, where a type in Scaffolding uses a type in Database.
- The types involved
Perla.Scaffolding.TemplateScriptKind→Perla.Database.PerlaTemplateRepositoryPerla.Scaffolding.TemplateScriptKind→Perla.Database.TemplateItemPerla.Scaffolding.TemplateService→Perla.Database.PerlaTemplateRepositoryPerla.Scaffolding.TemplateService→Perla.Database.QuickAccessSearchPerla.Scaffolding.TemplateService→Perla.Database.TemplateItemPerla.Scaffolding.TemplateService→Perla.Database.TemplateSearchKindPerla.Scaffolding.TemplateServiceArgs→Perla.Database.PerlaDatabase
- Direction
- Scaffolding uses Database, so a change to Database can break Scaffolding, while a change to Scaffolding can't break Database.
- Position
- Below the diagonal: Scaffolding uses a module listed above it, which is the healthy direction.
25→23 Scaffolding uses FileSystem✕
- Connections
- 1 pair of types, where a type in Scaffolding uses a type in FileSystem.
- The types involved
Perla.Scaffolding.TemplateServiceArgs→Perla.FileSystem.PerlaFsManager
- Direction
- Scaffolding uses FileSystem, so a change to FileSystem can break Scaffolding, while a change to Scaffolding can't break FileSystem.
- Position
- Below the diagonal: Scaffolding uses a module listed above it, which is the healthy direction.
26→10 SuaveService.PerlaHandlers uses Types✕
- Connections
- 1 pair of types, where a type in SuaveService.PerlaHandlers uses a type in Types.
- The types involved
Perla.SuaveService.PerlaHandlers.PerlaHandlers→Perla.Types.PerlaConfig
- Direction
- SuaveService.PerlaHandlers uses Types, so a change to Types can break SuaveService.PerlaHandlers, while a change to SuaveService.PerlaHandlers can't break Types.
- Position
- Below the diagonal: SuaveService.PerlaHandlers uses a module listed above it, which is the healthy direction.
26→23 SuaveService.PerlaHandlers uses FileSystem✕
- Connections
- 1 pair of types, where a type in SuaveService.PerlaHandlers uses a type in FileSystem.
- The types involved
Perla.SuaveService.PerlaHandlers.PerlaHandlers→Perla.FileSystem.PerlaFsManager
- Direction
- SuaveService.PerlaHandlers uses FileSystem, so a change to FileSystem can break SuaveService.PerlaHandlers, while a change to SuaveService.PerlaHandlers can't break FileSystem.
- Position
- Below the diagonal: SuaveService.PerlaHandlers uses a module listed above it, which is the healthy direction.
27→10 SuaveService.SpaFallback uses Types✕
- Connections
- 1 pair of types, where a type in SuaveService.SpaFallback uses a type in Types.
- The types involved
Perla.SuaveService.SpaFallback.SpaFallback→Perla.Types.PerlaConfig
- Direction
- SuaveService.SpaFallback uses Types, so a change to Types can break SuaveService.SpaFallback, while a change to SuaveService.SpaFallback can't break Types.
- Position
- Below the diagonal: SuaveService.SpaFallback uses a module listed above it, which is the healthy direction.
27→23 SuaveService.SpaFallback uses FileSystem✕
- Connections
- 1 pair of types, where a type in SuaveService.SpaFallback uses a type in FileSystem.
- The types involved
Perla.SuaveService.SpaFallback.SpaFallback→Perla.FileSystem.PerlaFsManager
- Direction
- SuaveService.SpaFallback uses FileSystem, so a change to FileSystem can break SuaveService.SpaFallback, while a change to SuaveService.SpaFallback can't break FileSystem.
- Position
- Below the diagonal: SuaveService.SpaFallback uses a module listed above it, which is the healthy direction.
28→10 Warmup.Recover uses Types✕
- Connections
- 1 pair of types, where a type in Warmup.Recover uses a type in Types.
- The types involved
Perla.Warmup.Recover.RecoverArgs→Perla.Types.PerlaConfig
- Direction
- Warmup.Recover uses Types, so a change to Types can break Warmup.Recover, while a change to Warmup.Recover can't break Types.
- Position
- Below the diagonal: Warmup.Recover uses a module listed above it, which is the healthy direction.
28→22 Warmup.Recover uses Database✕
- Connections
- 1 pair of types, where a type in Warmup.Recover uses a type in Database.
- The types involved
Perla.Warmup.Recover.RecoverArgs→Perla.Database.PerlaDatabase
- Direction
- Warmup.Recover uses Database, so a change to Database can break Warmup.Recover, while a change to Warmup.Recover can't break Database.
- Position
- Below the diagonal: Warmup.Recover uses a module listed above it, which is the healthy direction.
28→23 Warmup.Recover uses FileSystem✕
- Connections
- 1 pair of types, where a type in Warmup.Recover uses a type in FileSystem.
- The types involved
Perla.Warmup.Recover.RecoverArgs→Perla.FileSystem.PerlaFsManager
- Direction
- Warmup.Recover uses FileSystem, so a change to FileSystem can break Warmup.Recover, while a change to Warmup.Recover can't break FileSystem.
- Position
- Below the diagonal: Warmup.Recover uses a module listed above it, which is the healthy direction.
29→8 Build uses Extensibility✕
- Connections
- 1 pair of types, where a type in Build uses a type in Extensibility.
- The types involved
Perla.Build.BuildServiceArgs→Perla.Extensibility.ExtensibilityService
- Direction
- Build uses Extensibility, so a change to Extensibility can break Build, while a change to Build can't break Extensibility.
- Position
- Below the diagonal: Build uses a module listed above it, which is the healthy direction.
29→9 Build uses PkgManager✕
- Connections
- 1 pair of types, where a type in Build uses a type in PkgManager.
- The types involved
Perla.Build.BuildService→Perla.PkgManager.ImportMap
- Direction
- Build uses PkgManager, so a change to PkgManager can break Build, while a change to Build can't break PkgManager.
- Position
- Below the diagonal: Build uses a module listed above it, which is the healthy direction.
29→10 Build uses Types✕
- Connections
- 1 pair of types, where a type in Build uses a type in Types.
- The types involved
Perla.Build.BuildService→Perla.Types.PerlaConfig
- Direction
- Build uses Types, so a change to Types can break Build, while a change to Build can't break Types.
- Position
- Below the diagonal: Build uses a module listed above it, which is the healthy direction.
29→11 Build uses VirtualFs✕
- Connections
- 1 pair of types, where a type in Build uses a type in VirtualFs.
- The types involved
Perla.Build.BuildServiceArgs→Perla.VirtualFs.VirtualFileSystem
- Direction
- Build uses VirtualFs, so a change to VirtualFs can break Build, while a change to Build can't break VirtualFs.
- Position
- Below the diagonal: Build uses a module listed above it, which is the healthy direction.
29→14 Build uses Fable✕
- Connections
- 1 pair of types, where a type in Build uses a type in Fable.
- The types involved
Perla.Build.BuildServiceArgs→Perla.Fable.FableService
- Direction
- Build uses Fable, so a change to Fable can break Build, while a change to Build can't break Fable.
- Position
- Below the diagonal: Build uses a module listed above it, which is the healthy direction.
29→23 Build uses FileSystem✕
- Connections
- 1 pair of types, where a type in Build uses a type in FileSystem.
- The types involved
Perla.Build.BuildServiceArgs→Perla.FileSystem.PerlaFsManager
- Direction
- Build uses FileSystem, so a change to FileSystem can break Build, while a change to Build can't break FileSystem.
- Position
- Below the diagonal: Build uses a module listed above it, which is the healthy direction.
29→24 Build uses Esbuild✕
- Connections
- 1 pair of types, where a type in Build uses a type in Esbuild.
- The types involved
Perla.Build.BuildServiceArgs→Perla.Esbuild.EsbuildService
- Direction
- Build uses Esbuild, so a change to Esbuild can break Build, while a change to Build can't break Esbuild.
- Position
- Below the diagonal: Build uses a module listed above it, which is the healthy direction.
29→30 Build uses Perla part of a loop✕
- Connections
- 1 pair of types, where a type in Build uses a type in Perla.
- The types involved
Perla.Build.BuildServiceArgs→Perla.PerlaDirectories
- Direction
- Build uses Perla, so a change to Perla can break Build, while a change to Build can't break Perla.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→7 Perla uses RequestHandler✕
- Connections
- 2 pairs of types, where a type in Perla uses a type in RequestHandler.
- The types involved
Perla.AppContainerArgs→Perla.RequestHandler.RequestHandlerPerla.HasRequestHandler→Perla.RequestHandler.RequestHandler
- Direction
- Perla uses RequestHandler, so a change to RequestHandler can break Perla, while a change to Perla can't break RequestHandler.
- Position
- Below the diagonal: Perla uses a module listed above it, which is the healthy direction.
30→8 Perla uses Extensibility✕
- Connections
- 1 pair of types, where a type in Perla uses a type in Extensibility.
- The types involved
Perla.HasExtensibilityService→Perla.Extensibility.ExtensibilityService
- Direction
- Perla uses Extensibility, so a change to Extensibility can break Perla, while a change to Perla can't break Extensibility.
- Position
- Below the diagonal: Perla uses a module listed above it, which is the healthy direction.
30→9 Perla uses PkgManager✕
- Connections
- 2 pairs of types, where a type in Perla uses a type in PkgManager.
- The types involved
Perla.HasPkgManager→Perla.PkgManager.PkgManagerPerla.ImportMapResolution→Perla.PkgManager.ImportMap
- Direction
- Perla uses PkgManager, so a change to PkgManager can break Perla, while a change to Perla can't break PkgManager.
- Position
- Below the diagonal: Perla uses a module listed above it, which is the healthy direction.
30→10 Perla uses Types✕
- Connections
- 1 pair of types, where a type in Perla uses a type in Types.
- The types involved
Perla.PlatformOps→Perla.Types.EsbuildConfig
- Direction
- Perla uses Types, so a change to Types can break Perla, while a change to Perla can't break Types.
- Position
- Below the diagonal: Perla uses a module listed above it, which is the healthy direction.
30→11 Perla uses VirtualFs✕
- Connections
- 1 pair of types, where a type in Perla uses a type in VirtualFs.
- The types involved
Perla.HasVirtualFileSystem→Perla.VirtualFs.VirtualFileSystem
- Direction
- Perla uses VirtualFs, so a change to VirtualFs can break Perla, while a change to Perla can't break VirtualFs.
- Position
- Below the diagonal: Perla uses a module listed above it, which is the healthy direction.
30→13 Perla uses Configuration✕
- Connections
- 1 pair of types, where a type in Perla uses a type in Configuration.
- The types involved
Perla.HasConfiguration→Perla.Configuration.ConfigurationManager
- Direction
- Perla uses Configuration, so a change to Configuration can break Perla, while a change to Perla can't break Configuration.
- Position
- Below the diagonal: Perla uses a module listed above it, which is the healthy direction.
30→14 Perla uses Fable✕
- Connections
- 1 pair of types, where a type in Perla uses a type in Fable.
- The types involved
Perla.HasFableService→Perla.Fable.FableService
- Direction
- Perla uses Fable, so a change to Fable can break Perla, while a change to Perla can't break Fable.
- Position
- Below the diagonal: Perla uses a module listed above it, which is the healthy direction.
30→22 Perla uses Database✕
- Connections
- 1 pair of types, where a type in Perla uses a type in Database.
- The types involved
Perla.HasDatabase→Perla.Database.PerlaDatabase
- Direction
- Perla uses Database, so a change to Database can break Perla, while a change to Perla can't break Database.
- Position
- Below the diagonal: Perla uses a module listed above it, which is the healthy direction.
30→23 Perla uses FileSystem✕
- Connections
- 2 pairs of types, where a type in Perla uses a type in FileSystem.
- The types involved
Perla.AppContainerArgs→Perla.FileSystem.PerlaFsManagerPerla.HasFsManager→Perla.FileSystem.PerlaFsManager
- Direction
- Perla uses FileSystem, so a change to FileSystem can break Perla, while a change to Perla can't break FileSystem.
- Position
- Below the diagonal: Perla uses a module listed above it, which is the healthy direction.
30→24 Perla uses Esbuild✕
- Connections
- 1 pair of types, where a type in Perla uses a type in Esbuild.
- The types involved
Perla.HasEsbuildService→Perla.Esbuild.EsbuildService
- Direction
- Perla uses Esbuild, so a change to Esbuild can break Perla, while a change to Perla can't break Esbuild.
- Position
- Below the diagonal: Perla uses a module listed above it, which is the healthy direction.
30→25 Perla uses Scaffolding✕
- Connections
- 1 pair of types, where a type in Perla uses a type in Scaffolding.
- The types involved
Perla.HasTemplateService→Perla.Scaffolding.TemplateService
- Direction
- Perla uses Scaffolding, so a change to Scaffolding can break Perla, while a change to Perla can't break Scaffolding.
- Position
- Below the diagonal: Perla uses a module listed above it, which is the healthy direction.
30→29 Perla uses Build✕
- Connections
- 1 pair of types, where a type in Perla uses a type in Build.
- The types involved
Perla.HasBuildService→Perla.Build.BuildService
- Direction
- Perla uses Build, so a change to Build can break Perla, while a change to Perla can't break Build.
- Position
- Below the diagonal: Perla uses a module listed above it, which is the healthy direction.
31→15 Handlers.Handlers uses Handlers✕
- Connections
- 9 pairs of types, where a type in Handlers.Handlers uses a type in Handlers.
- The types involved
Perla.Handlers.Handlers.Handlers→Perla.Handlers.BuildOptionsPerla.Handlers.Handlers.Handlers→Perla.Handlers.DependencyOptionsPerla.Handlers.Handlers.Handlers→Perla.Handlers.DescribeOptionsPerla.Handlers.Handlers.Handlers→Perla.Handlers.InstallOptionsPerla.Handlers.Handlers.Handlers→Perla.Handlers.ListPackagesOptionsPerla.Handlers.Handlers.Handlers→Perla.Handlers.ProjectOptionsPerla.Handlers.Handlers.Handlers→Perla.Handlers.ServeOptionsPerla.Handlers.Handlers.Handlers→Perla.Handlers.TemplateRepositoryOptionsPerla.Handlers.Handlers.Handlers→Perla.Handlers.TestingOptions
- Direction
- Handlers.Handlers uses Handlers, so a change to Handlers can break Handlers.Handlers, while a change to Handlers.Handlers can't break Handlers.
- Position
- Below the diagonal: Handlers.Handlers uses a module listed above it, which is the healthy direction.
31→30 Handlers.Handlers uses Perla✕
- Connections
- 1 pair of types, where a type in Handlers.Handlers uses a type in Perla.
- The types involved
Perla.Handlers.Handlers.Handlers→Perla.AppContainer
- Direction
- Handlers.Handlers uses Perla, so a change to Perla can break Handlers.Handlers, while a change to Handlers.Handlers can't break Perla.
- Position
- Below the diagonal: Handlers.Handlers uses a module listed above it, which is the healthy direction.
32→9 ImportMaps uses PkgManager✕
- Connections
- 1 pair of types, where a type in ImportMaps uses a type in PkgManager.
- The types involved
Perla.ImportMaps.ImportMaps→Perla.PkgManager.ImportMap
- Direction
- ImportMaps uses PkgManager, so a change to PkgManager can break ImportMaps, while a change to ImportMaps can't break PkgManager.
- Position
- Below the diagonal: ImportMaps uses a module listed above it, which is the healthy direction.
32→10 ImportMaps uses Types✕
- Connections
- 1 pair of types, where a type in ImportMaps uses a type in Types.
- The types involved
Perla.ImportMaps.ImportMaps→Perla.Types.PerlaConfig
- Direction
- ImportMaps uses Types, so a change to Types can break ImportMaps, while a change to ImportMaps can't break Types.
- Position
- Below the diagonal: ImportMaps uses a module listed above it, which is the healthy direction.
32→30 ImportMaps uses Perla✕
- Connections
- 1 pair of types, where a type in ImportMaps uses a type in Perla.
- The types involved
Perla.ImportMaps.ImportMaps→Perla.ImportMapResolution
- Direction
- ImportMaps uses Perla, so a change to Perla can break ImportMaps, while a change to ImportMaps can't break Perla.
- Position
- Below the diagonal: ImportMaps uses a module listed above it, which is the healthy direction.
33→7 Patterns uses RequestHandler✕
- Connections
- 1 pair of types, where a type in Patterns uses a type in RequestHandler.
- The types involved
Perla.Patterns.Patterns→Perla.RequestHandler.RequestHandler
- Direction
- Patterns uses RequestHandler, so a change to RequestHandler can break Patterns, while a change to Patterns can't break RequestHandler.
- Position
- Below the diagonal: Patterns uses a module listed above it, which is the healthy direction.
33→8 Patterns uses Extensibility✕
- Connections
- 1 pair of types, where a type in Patterns uses a type in Extensibility.
- The types involved
Perla.Patterns.Patterns→Perla.Extensibility.ExtensibilityService
- Direction
- Patterns uses Extensibility, so a change to Extensibility can break Patterns, while a change to Patterns can't break Extensibility.
- Position
- Below the diagonal: Patterns uses a module listed above it, which is the healthy direction.
33→9 Patterns uses PkgManager✕
- Connections
- 1 pair of types, where a type in Patterns uses a type in PkgManager.
- The types involved
Perla.Patterns.Patterns→Perla.PkgManager.PkgManager
- Direction
- Patterns uses PkgManager, so a change to PkgManager can break Patterns, while a change to Patterns can't break PkgManager.
- Position
- Below the diagonal: Patterns uses a module listed above it, which is the healthy direction.
33→11 Patterns uses VirtualFs✕
- Connections
- 1 pair of types, where a type in Patterns uses a type in VirtualFs.
- The types involved
Perla.Patterns.Patterns→Perla.VirtualFs.VirtualFileSystem
- Direction
- Patterns uses VirtualFs, so a change to VirtualFs can break Patterns, while a change to Patterns can't break VirtualFs.
- Position
- Below the diagonal: Patterns uses a module listed above it, which is the healthy direction.
33→13 Patterns uses Configuration✕
- Connections
- 1 pair of types, where a type in Patterns uses a type in Configuration.
- The types involved
Perla.Patterns.Patterns→Perla.Configuration.ConfigurationManager
- Direction
- Patterns uses Configuration, so a change to Configuration can break Patterns, while a change to Patterns can't break Configuration.
- Position
- Below the diagonal: Patterns uses a module listed above it, which is the healthy direction.
33→14 Patterns uses Fable✕
- Connections
- 1 pair of types, where a type in Patterns uses a type in Fable.
- The types involved
Perla.Patterns.Patterns→Perla.Fable.FableService
- Direction
- Patterns uses Fable, so a change to Fable can break Patterns, while a change to Patterns can't break Fable.
- Position
- Below the diagonal: Patterns uses a module listed above it, which is the healthy direction.
33→22 Patterns uses Database✕
- Connections
- 1 pair of types, where a type in Patterns uses a type in Database.
- The types involved
Perla.Patterns.Patterns→Perla.Database.PerlaDatabase
- Direction
- Patterns uses Database, so a change to Database can break Patterns, while a change to Patterns can't break Database.
- Position
- Below the diagonal: Patterns uses a module listed above it, which is the healthy direction.
33→23 Patterns uses FileSystem✕
- Connections
- 1 pair of types, where a type in Patterns uses a type in FileSystem.
- The types involved
Perla.Patterns.Patterns→Perla.FileSystem.PerlaFsManager
- Direction
- Patterns uses FileSystem, so a change to FileSystem can break Patterns, while a change to Patterns can't break FileSystem.
- Position
- Below the diagonal: Patterns uses a module listed above it, which is the healthy direction.
33→24 Patterns uses Esbuild✕
- Connections
- 1 pair of types, where a type in Patterns uses a type in Esbuild.
- The types involved
Perla.Patterns.Patterns→Perla.Esbuild.EsbuildService
- Direction
- Patterns uses Esbuild, so a change to Esbuild can break Patterns, while a change to Patterns can't break Esbuild.
- Position
- Below the diagonal: Patterns uses a module listed above it, which is the healthy direction.
33→25 Patterns uses Scaffolding✕
- Connections
- 1 pair of types, where a type in Patterns uses a type in Scaffolding.
- The types involved
Perla.Patterns.Patterns→Perla.Scaffolding.TemplateService
- Direction
- Patterns uses Scaffolding, so a change to Scaffolding can break Patterns, while a change to Patterns can't break Scaffolding.
- Position
- Below the diagonal: Patterns uses a module listed above it, which is the healthy direction.
33→30 Patterns uses Perla✕
- Connections
- 2 pairs of types, where a type in Patterns uses a type in Perla.
- The types involved
Perla.Patterns.Patterns→Perla.PerlaDirectoriesPerla.Patterns.Patterns→Perla.PlatformOps
- Direction
- Patterns uses Perla, so a change to Perla can break Patterns, while a change to Patterns can't break Perla.
- Position
- Below the diagonal: Patterns uses a module listed above it, which is the healthy direction.
34→10 SuaveService uses Types✕
- Connections
- 3 pairs of types, where a type in SuaveService uses a type in Types.
- The types involved
Perla.SuaveService.SuaveContext→Perla.Types.PerlaConfigPerla.SuaveService.SuaveServerContext→Perla.Types.PerlaConfigPerla.SuaveService.SuaveTestingContext→Perla.Types.PerlaConfig
- Direction
- SuaveService uses Types, so a change to Types can break SuaveService, while a change to SuaveService can't break Types.
- Position
- Below the diagonal: SuaveService uses a module listed above it, which is the healthy direction.
34→11 SuaveService uses VirtualFs✕
- Connections
- 3 pairs of types, where a type in SuaveService uses a type in VirtualFs.
- The types involved
Perla.SuaveService.SuaveContext→Perla.VirtualFs.VirtualFileSystemPerla.SuaveService.SuaveServerContext→Perla.VirtualFs.VirtualFileSystemPerla.SuaveService.SuaveTestingContext→Perla.VirtualFs.VirtualFileSystem
- Direction
- SuaveService uses VirtualFs, so a change to VirtualFs can break SuaveService, while a change to SuaveService can't break VirtualFs.
- Position
- Below the diagonal: SuaveService uses a module listed above it, which is the healthy direction.
34→23 SuaveService uses FileSystem✕
- Connections
- 3 pairs of types, where a type in SuaveService uses a type in FileSystem.
- The types involved
Perla.SuaveService.SuaveContext→Perla.FileSystem.PerlaFsManagerPerla.SuaveService.SuaveServerContext→Perla.FileSystem.PerlaFsManagerPerla.SuaveService.SuaveTestingContext→Perla.FileSystem.PerlaFsManager
- Direction
- SuaveService uses FileSystem, so a change to FileSystem can break SuaveService, while a change to SuaveService can't break FileSystem.
- Position
- Below the diagonal: SuaveService uses a module listed above it, which is the healthy direction.
34→30 SuaveService uses Perla✕
- Connections
- 2 pairs of types, where a type in SuaveService uses a type in Perla.
- The types involved
Perla.SuaveService.SuaveServerContext→Perla.PerlaDirectoriesPerla.SuaveService.SuaveTestingContext→Perla.PerlaDirectories
- Direction
- SuaveService uses Perla, so a change to Perla can break SuaveService, while a change to SuaveService can't break Perla.
- Position
- Below the diagonal: SuaveService uses a module listed above it, which is the healthy direction.
35→10 SuaveService.TestingHandlers uses Types✕
- Connections
- 1 pair of types, where a type in SuaveService.TestingHandlers uses a type in Types.
- The types involved
Perla.SuaveService.TestingHandlers.TestingHandlers→Perla.Types.TestConfig
- Direction
- SuaveService.TestingHandlers uses Types, so a change to Types can break SuaveService.TestingHandlers, while a change to SuaveService.TestingHandlers can't break Types.
- Position
- Below the diagonal: SuaveService.TestingHandlers uses a module listed above it, which is the healthy direction.
35→30 SuaveService.TestingHandlers uses Perla✕
- Connections
- 1 pair of types, where a type in SuaveService.TestingHandlers uses a type in Perla.
- The types involved
Perla.SuaveService.TestingHandlers.TestingHandlers→Perla.PerlaDirectories
- Direction
- SuaveService.TestingHandlers uses Perla, so a change to Perla can break SuaveService.TestingHandlers, while a change to SuaveService.TestingHandlers can't break Perla.
- Position
- Below the diagonal: SuaveService.TestingHandlers uses a module listed above it, which is the healthy direction.
36→7 Testing uses RequestHandler✕
- Connections
- 1 pair of types, where a type in Testing uses a type in RequestHandler.
- The types involved
Perla.Testing.TestingServiceArgs→Perla.RequestHandler.RequestHandler
- Direction
- Testing uses RequestHandler, so a change to RequestHandler can break Testing, while a change to Testing can't break RequestHandler.
- Position
- Below the diagonal: Testing uses a module listed above it, which is the healthy direction.
36→10 Testing uses Types✕
- Connections
- 8 pairs of types, where a type in Testing uses a type in Types.
- The types involved
Perla.Testing.ReportResult→Perla.Types.BrowserPerla.Testing.ReportResult→Perla.Types.SuitePerla.Testing.ReportResult→Perla.Types.TestStatsPerla.Testing.ReportedError→Perla.Types.TestPerla.Testing.RunTestOption→Perla.Types.BrowserPerla.Testing.RunTestOption→Perla.Types.BrowserModePerla.Testing.TestingService→Perla.Types.TestEventPerla.Testing.TestingServiceArgs→Perla.Types.PerlaConfig
- Direction
- Testing uses Types, so a change to Types can break Testing, while a change to Testing can't break Types.
- Position
- Below the diagonal: Testing uses a module listed above it, which is the healthy direction.
36→11 Testing uses VirtualFs✕
- Connections
- 1 pair of types, where a type in Testing uses a type in VirtualFs.
- The types involved
Perla.Testing.TestingServiceArgs→Perla.VirtualFs.VirtualFileSystem
- Direction
- Testing uses VirtualFs, so a change to VirtualFs can break Testing, while a change to Testing can't break VirtualFs.
- Position
- Below the diagonal: Testing uses a module listed above it, which is the healthy direction.
36→23 Testing uses FileSystem✕
- Connections
- 1 pair of types, where a type in Testing uses a type in FileSystem.
- The types involved
Perla.Testing.TestingServiceArgs→Perla.FileSystem.PerlaFsManager
- Direction
- Testing uses FileSystem, so a change to FileSystem can break Testing, while a change to Testing can't break FileSystem.
- Position
- Below the diagonal: Testing uses a module listed above it, which is the healthy direction.
36→30 Testing uses Perla✕
- Connections
- 1 pair of types, where a type in Testing uses a type in Perla.
- The types involved
Perla.Testing.TestingServiceArgs→Perla.PerlaDirectories
- Direction
- Testing uses Perla, so a change to Perla can break Testing, while a change to Testing can't break Perla.
- Position
- Below the diagonal: Testing uses a module listed above it, which is the healthy direction.
37→10 Warmup.Check uses Types✕
- Connections
- 1 pair of types, where a type in Warmup.Check uses a type in Types.
- The types involved
Perla.Warmup.Check.Check→Perla.Types.PerlaConfig
- Direction
- Warmup.Check uses Types, so a change to Types can break Warmup.Check, while a change to Warmup.Check can't break Types.
- Position
- Below the diagonal: Warmup.Check uses a module listed above it, which is the healthy direction.
37→14 Warmup.Check uses Fable✕
- Connections
- 1 pair of types, where a type in Warmup.Check uses a type in Fable.
- The types involved
Perla.Warmup.Check.Check→Perla.Fable.FableService
- Direction
- Warmup.Check uses Fable, so a change to Fable can break Warmup.Check, while a change to Warmup.Check can't break Fable.
- Position
- Below the diagonal: Warmup.Check uses a module listed above it, which is the healthy direction.
37→22 Warmup.Check uses Database✕
- Connections
- 1 pair of types, where a type in Warmup.Check uses a type in Database.
- The types involved
Perla.Warmup.Check.Check→Perla.Database.PerlaDatabase
- Direction
- Warmup.Check uses Database, so a change to Database can break Warmup.Check, while a change to Warmup.Check can't break Database.
- Position
- Below the diagonal: Warmup.Check uses a module listed above it, which is the healthy direction.
37→30 Warmup.Check uses Perla✕
- Connections
- 1 pair of types, where a type in Warmup.Check uses a type in Perla.
- The types involved
Perla.Warmup.Check.Check→Perla.PerlaDirectories
- Direction
- Warmup.Check uses Perla, so a change to Perla can break Warmup.Check, while a change to Warmup.Check can't break Perla.
- Position
- Below the diagonal: Warmup.Check uses a module listed above it, which is the healthy direction.
38→10 Testing.Print uses Types✕
- Connections
- 3 pairs of types, where a type in Testing.Print uses a type in Types.
- The types involved
Perla.Testing.Print.Print→Perla.Types.SuitePerla.Testing.Print.Print→Perla.Types.TestPerla.Testing.Print.Print→Perla.Types.TestStats
- Direction
- Testing.Print uses Types, so a change to Types can break Testing.Print, while a change to Testing.Print can't break Types.
- Position
- Below the diagonal: Testing.Print uses a module listed above it, which is the healthy direction.
38→36 Testing.Print uses Testing✕
- Connections
- 2 pairs of types, where a type in Testing.Print uses a type in Testing.
- The types involved
Perla.Testing.Print.Print→Perla.Testing.ReportResultPerla.Testing.Print.Print→Perla.Testing.ReportedError
- Direction
- Testing.Print uses Testing, so a change to Testing can break Testing.Print, while a change to Testing.Print can't break Testing.
- Position
- Below the diagonal: Testing.Print uses a module listed above it, which is the healthy direction.
39→10 Testing.Testing uses Types✕
- Connections
- 2 pairs of types, where a type in Testing.Testing uses a type in Types.
- The types involved
Perla.Testing.Testing.Testing→Perla.Types.BrowserPerla.Testing.Testing.Testing→Perla.Types.TestEvent
- Direction
- Testing.Testing uses Types, so a change to Types can break Testing.Testing, while a change to Testing.Testing can't break Types.
- Position
- Below the diagonal: Testing.Testing uses a module listed above it, which is the healthy direction.
39→36 Testing.Testing uses Testing✕
- Connections
- 1 pair of types, where a type in Testing.Testing uses a type in Testing.
- The types involved
Perla.Testing.Testing.Testing→Perla.Testing.ReportResult
- Direction
- Testing.Testing uses Testing, so a change to Testing can break Testing.Testing, while a change to Testing.Testing can't break Testing.
- Position
- Below the diagonal: Testing.Testing uses a module listed above it, which is the healthy direction.
40→7 Testing.TestingServiceModule uses RequestHandler✕
- Connections
- 1 pair of types, where a type in Testing.TestingServiceModule uses a type in RequestHandler.
- The types involved
Perla.Testing.TestingServiceModule.TestingServiceModule→Perla.RequestHandler.RequestHandler
- Direction
- Testing.TestingServiceModule uses RequestHandler, so a change to RequestHandler can break Testing.TestingServiceModule, while a change to Testing.TestingServiceModule can't break RequestHandler.
- Position
- Below the diagonal: Testing.TestingServiceModule uses a module listed above it, which is the healthy direction.
40→36 Testing.TestingServiceModule uses Testing✕
- Connections
- 3 pairs of types, where a type in Testing.TestingServiceModule uses a type in Testing.
- The types involved
Perla.Testing.TestingServiceModule.TestingServiceModule→Perla.Testing.RunTestOptionPerla.Testing.TestingServiceModule.TestingServiceModule→Perla.Testing.TestingServicePerla.Testing.TestingServiceModule.TestingServiceModule→Perla.Testing.TestingServiceArgs
- Direction
- Testing.TestingServiceModule uses Testing, so a change to Testing can break Testing.TestingServiceModule, while a change to Testing.TestingServiceModule can't break Testing.
- Position
- Below the diagonal: Testing.TestingServiceModule uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 11 | High / Critical |
| A05:2025 — Injection | 10 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 2 | High / Critical |
Roadmap
Top priorities: Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract; Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Perla.fsproj.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Perla.fsproj. | +3.9 pts | Low | ADR Quality |
| Resolve the 1 `FindOne should return repository when searching by ID` spells `ID`… finding(s) in Naming Consistency — start with Database.Tests.fs. | +3.4 pts | Low | Naming Consistency |
| Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract. | +4.2 pts | Medium | Code Duplication |
| Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value. | +4.2 pts | Medium | Dead Code |
| Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with Library.fs (5), Types.fs (2), RequestHandler.fs (2). | +3.7 pts | Medium | Knowledge Freshness |
| Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. | +1.8 pts | Low | Dependency Hygiene |
| Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with REDACTED. | +1.8 pts | Low | Dependency Hygiene |
| Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. | +1.8 pts | Low | Dependency Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.1 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/Perla/Handlers.fs | 5.5 | Mixed | Cyclomatic Complexity: Handlers.runTemplate (cyclomatic 23) |
| src/Perla/SuaveService.fs | 5.5 | Mixed | God Classes: FileTooLong: Perla/SuaveService.fs |
| src/Perla/Testing.fs | 5.6 | Mixed | Cyclomatic Complexity: TestingServiceModule.Create (cyclomatic 20) |
| src/Perla/Commands.fs | 5.9 | Mixed | Cognitive Complexity: Commands.Test (cognitive 19) |
| src/Perla/Configuration.fs | 5.9 | Mixed | Code Duplication: Duplicated block (17–20 lines × 2) |
| src/Perla.Logger/Library.fs | 5.9 | Mixed | Code Duplication: Duplicated block (15–18 lines × 2) |
| src/Perla/PlatformOps.fs | 6.3 | Mixed | Cyclomatic Complexity: PlatformOpsModule.Create (cyclomatic 20) |
| src/Perla/Build.fs | 6.3 | Mixed | Cognitive Complexity: Build.getMissingLocalDependencies (cognitive 28) |
| src/Perla.PkgManager/RequestHandler.fs | 6.3 | Mixed | Code Duplication: Duplicated block (18 lines × 2) |
| src/Perla/Library.fs | 6.3 | Mixed | Code Duplication: Duplicated block (11 lines × 2) |
| src/Perla.PkgManager/Types.fs | 7.0 | Mixed | Cyclomatic Complexity: GeneratorOptionModule.toDict (cyclomatic 29) |
| src/Perla/Orchestration.fs | 7.0 | Mixed | Cognitive Complexity: Check.Setup (cognitive 23) |
| src/Perla/Directories.fs | 7.0 | Mixed | Code Duplication: Duplicated block (6 lines × 2) |
| src/Perla.Fable.Mocha/Library.fs | 7.0 | Mixed | Code Duplication: Duplicated block (8–10 lines × 2) |
| src/Perla.PkgManager/PkgManager.fs | 7.1 | Mixed | Cyclomatic Complexity: PkgManagerModule.cleanupRemovedPackages (cyclomatic 16) |
| src/Perla/Json.fs | 7.1 | Mixed | Cyclomatic Complexity: PerlaConfig.UpdateFileFields (cyclomatic 25) |
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 51 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 51 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, 181 of 215 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- 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 (7 contributor(s) across 912 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 6 hold 0.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — 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.
- D32 Data Compliance (PII/GDPR) — 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. `docs/src/router.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — 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 reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in src/Perla/Orchestration.fs, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM gitpod/workspace-full:2023-11-04-12-07-48 2 | 3 | RUN sudo apt-get update && sudo apt-get install apt-transport-https -------------------- ERROR: failed to solve: failed to register layer: write /home/gitpod/.rustup/toolchains/1.73.0-x86_64-unknown-linux-gnu/share/doc/rust/html/core/ops/trait.BitAnd.html: no space left on device; runtime evidence skipped.
- 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.
- 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.
- 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was GeneratorOptionModule.toDict at 29. A further 2 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 SpectreSink.Serilog.Core.ILogEventSink.Emit at 22 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Perla.Logger/Library.fs (SpectreSink.Serilog.Core.ILogEventSink.Emit at 22), src/Perla/SuaveService.fs (MimeTypes.tryGetContentType at 20). 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 13 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with GeneratorOptionModule.toDict (cyclomatic 29), PerlaConfig.UpdateFileFields (cyclomatic 25), Handlers.runTemplate (cyclomatic 23). — 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 13 together lifts Cyclomatic Complexity from 8.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
20 method(s) exceeded the cognitive complexity threshold of 15; the worst was PkgManagerModule.cleanupRemovedPackages at 43.
What to do
- Bring the 20 bodies over 15 down to 15 or less in Cognitive Complexity — start with PkgManagerModule.cleanupRemovedPackages (cognitive 43), Handlers.runTesting (cognitive 43), Handlers.runRestore (cognitive 36). — 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 20 together lifts Cognitive Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
7 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 7 FileTooLong finding(s) in God Classes — start with SuaveService.fs, Handlers.fs, Testing.fs. — One of this dimension's main actionable groups (7 warning-level).
D4 · Code Duplication
39 duplicated block group(s) detected. 6.6 % of the production lines (888 of 13,511) are in a reported copy.
What to do
- Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Library.fs (3), Json.fs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Library.fs (2), Configuration.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Database.fs, Handlers.fs, Json.fs. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
15 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 29.8% — 18 file(s) below 50%.
What to do
- Resolve the 18 Low coverage finding(s) in Code Coverage — start with RequestHandler.fs (2), Library.fs (2), Types.fs. — One of this dimension's main actionable groups (18 warning-level).
- Resolve the 1 No test project references Perla.Fable.Mocha finding(s) in Code Coverage — start with Perla.Fable.Mocha.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references Perla.Fable.QUnit finding(s) in Code Coverage — start with Perla.Fable.QUnit.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
28 outdated, 2 vulnerable, 1 deprecated, 1 prerelease packages.
What to do
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 30 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 38 direct `PackageReference`(s), and 16 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
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 Perla.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
1 naming inconsistencies among 15 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `FindOne should return repository when searching by ID` spells `ID`… finding(s) in Naming Consistency — start with Database.Tests.fs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 8 build units (MSBuild) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
96 % of calls cross a namespace and 6 % go through an interface, but 40 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
10 finding(s): 0 critical, 9 high, 1 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. semgrep hit a parse error in 1 file(s) — `docs/src/router.ts` (lines 5–7) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-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
2 finding(s): 1 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
11 finding(s): 3 critical, 5 high, 1 medium, 2 low.
What to do
- Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 3 Critical IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
30 of 32 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Perla/SuaveService.fs. Counted over 32 of the 36 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with Library.fs (5), Types.fs (2), RequestHandler.fs (2). — One of this dimension's main actionable groups (27 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with SuaveService.fs, Handlers.fs, Testing.fs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 31 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — docs/src/Components/Index.tsx:130
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — src/Perla/offline-templates/fable-feliz/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
- `blockquote` sets color: rgb(110, 85, 47) on background-color: rgb(219, 205, 182) — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/src/index.css:46
- `blockquote` sets color: rgb(219, 205, 182) on background-color: rgb(110, 85, 47) — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/src/index.css:95
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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
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:16
- `REDACTED` 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`. — REDACTED: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
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- src/Perla/livereload.js:5 · src/Perla/testing-helpers.js:91 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/Perla/livereload.js:5
- src/Perla/qunit-runner.js:68 · src/Perla/qunit-runner.js:89 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/Perla/qunit-runner.js:68
- src/Perla/testing-helpers.js:36 · src/Perla/testing-helpers.js:65 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/Perla/testing-helpers.js:36
- src/Perla/mocha-runner.js:115 · src/Perla/qunit-runner.js:144 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/Perla/mocha-runner.js:115
- src/Perla/offline-templates/basic/src/main.js:1 · src/Perla/offline-templates/blocal/src/main.js:1 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/Perla/offline-templates/basic/src/main.js:1
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×5) — src/Perla/qunit-runner.js:1, src/Perla/mocha-runner.js:1, src/Perla/testing-helpers.js:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R7 · Dead Code
- Unreachable from the 3 application, 0 tooling and 3 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
- no import path from any entry point (3 application, 0 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×5) — src/Perla/qunit-runner.js, src/Perla/mocha-runner.js, src/Perla/testing-helpers.js, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R9 · Circular Imports
S1 · Web-Security Posture
- `https://ga.jspm.io/npm:es-module-shims@2.6.1/dist/es-module-shims.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 5 such include(s) across the repository's markup. — src/Perla/offline-templates/basic/index.html:9
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X23 · Unguarded diagnostic materialisation
X28 · Index access outside its own emptiness guard
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 41% | Weak — gated by R10, R7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 51% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 42% | Weak — gated by R4, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 81% | Strong | Solid. |
| Accessibility | 66% | Adequate | Acceptable, with room to improve. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 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 — 70 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — 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
- 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. Its F# is compiled by Fable to JavaScript, which runs on one event loop, so no two requests write a shared object at the same instant. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM gitpod/workspace-full:2023-11-04-12-07-48 2 | 3 | RUN sudo apt-get update && sudo apt-get install apt-transport-https -------------------- ERROR: failed to solve: failed to register layer: write /home/gitpod/.rustup/toolchains/1.73.0-x86_64-unknown-linux-gnu/share/doc/rust/html/core/ops/trait.BitAnd.html: no space left on device; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — 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 — ~6649 lines of test source are present (.fs, .js) 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.
- D19 Documentation Quality — D19 withholds "Documentation: empty section": 2 candidate(s) were measured and not published.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed F# surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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): 43 value object(s); 6 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
- M4 Documentation accuracy — Not applicable: the 39 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (cd 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not 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 30 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
- R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
- 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.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- 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 — 19 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang src/Perla/offline-templates/fable-feliz/index.html:2
- REDACTED
- REDACTED
- REDACTED
Serious — 124 finding(s)
- Low coverage: src/Perla.PkgManager/Types.fs src/Perla.PkgManager/Types.fs:1
- Low coverage: src/Perla.PkgManager/RequestHandler.fs src/Perla.PkgManager/RequestHandler.fs:1
- Low coverage: src/Perla.Logger/Library.fs src/Perla.Logger/Library.fs:1
- Low coverage: src/Perla/SuaveService.fs src/Perla/SuaveService.fs:1
- Low coverage: src/Perla/Testing.fs src/Perla/Testing.fs:1
- Low coverage: src/Perla/Commands.fs src/Perla/Commands.fs:1
- Low coverage: src/Perla/Program.fs src/Perla/Program.fs:1
- Low coverage: src/Perla/Handlers.fs src/Perla/Handlers.fs:1
- Low coverage: src/Perla/Orchestration.fs src/Perla/Orchestration.fs:1
- Low coverage: src/Perla/Configuration.fs src/Perla/Configuration.fs:1
- Low coverage: src/Perla/Library.fs src/Perla/Library.fs:1
- Low coverage: src/Perla/Scaffolding.fs src/Perla/Scaffolding.fs:1
- Low coverage: src/Perla/Build.fs src/Perla/Build.fs:1
- Low coverage: src/Perla/Fable.fs src/Perla/Fable.fs:1
- Low coverage: src/Perla/Esbuild.fs src/Perla/Esbuild.fs:1
- Low coverage: src/Perla/RequestHandler.fs src/Perla/RequestHandler.fs:1
- Low coverage: src/Perla/Directories.fs src/Perla/Directories.fs:1
- Low coverage: src/Perla/PlatformOps.fs src/Perla/PlatformOps.fs:1
- FileTooLong: Perla/SuaveService.fs src/Perla/SuaveService.fs
- FileTooLong: Perla/Handlers.fs src/Perla/Handlers.fs
- FileTooLong: Perla/Testing.fs src/Perla/Testing.fs
- FileTooLong: Perla/Commands.fs src/Perla/Commands.fs
- FileTooLong: Perla/Json.fs src/Perla/Json.fs
- FileTooLong: Perla/VirtualFileSystem.fs src/Perla/VirtualFileSystem.fs
- FileTooLong: Perla.PkgManager/PkgManager.fs src/Perla.PkgManager/PkgManager.fs
- No test reaches this file src/Perla/qunit-runner.js:1
- No test reaches this file src/Perla/mocha-runner.js:1
- No test reaches this file src/Perla/testing-helpers.js:1
- No test reaches this file src/Perla/livereload.js:1
- No test reaches this file src/Perla/worker.js:1
- Duplicated block (7 lines × 2) src/Perla.Fable.Mocha/Library.fs:58
- Duplicated block (7 lines × 2) src/Perla.Fable.Mocha/Library.fs:67
- Duplicated block (7 lines × 2) src/Perla.Fable.Mocha/Library.fs:76
- Duplicated block (7 lines × 2) src/Perla/Json.fs:246
- Duplicated block (9 lines × 2) src/Perla/Configuration.fs:54
- Duplicated block (9 lines × 2) src/Perla/Library.fs:201
- Duplicated block (9 lines × 2) src/Perla.Fable.Mocha/Library.fs:180
- Duplicated block (8 lines × 2) src/Perla/Database.fs:353
- Duplicated block (8 lines × 2) src/Perla/Handlers.fs:255
- Duplicated block (8 lines × 2) src/Perla/Json.fs:309
- Low contrast colour pair in CSS (4.4:1) docs/src/index.css:46
- Low contrast colour pair in CSS (4.4:1) docs/src/index.css:95
- Duplicated block (18 lines × 2) src/Perla.PkgManager/RequestHandler.fs:85
- Duplicated block (18 lines × 2) src/Perla/SuaveService.fs:1510
- Duplicated block (14 lines × 2) src/Perla/SuaveService.fs:1436
- Duplicated block (14 lines × 2) src/Perla.PkgManager/PkgManager.fs:158
- Duplicated block (6 lines × 2) src/Perla.Fable.Mocha/Library.fs:50
- Duplicated block (6 lines × 2) src/Perla/Directories.fs:23
- Heading level jumps from h1 to h3 docs/src/Components/Index.tsx:130
- GeneratorOptionModule.toDict (cyclomatic 29) src/Perla.PkgManager/Types.fs:212
- PerlaConfig.UpdateFileFields (cyclomatic 25) src/Perla/Json.fs:807
- Handlers.runTemplate (cyclomatic 23) src/Perla/Handlers.fs:331
- Handlers.runTesting (cyclomatic 22) src/Perla/Handlers.fs:839
- FileSystem.GetManager (cyclomatic 22) src/Perla/FileSystem.fs:122
- Handlers.runRestore (cyclomatic 20) src/Perla/Handlers.fs:1369
- TestingServiceModule.Create (cyclomatic 20) src/Perla/Testing.fs:892
- PlatformOpsModule.Create (cyclomatic 20) src/Perla/PlatformOps.fs:208
- VirtualFs.Create (cyclomatic 18) src/Perla/VirtualFileSystem.fs:712
- PluginManagerModule.Create (cyclomatic 17) src/Perla.Plugins/Registry.fs:82
- Handlers.runRemovePackage (cyclomatic 17) src/Perla/Handlers.fs:1187
- PkgManagerModule.cleanupRemovedPackages (cyclomatic 16) src/Perla.PkgManager/PkgManager.fs:476
- ProviderOps.extractFilePath (cyclomatic 16) src/Perla.PkgManager/Provider.fs:61
- Deprecated: xunit REDACTED:40
- Prerelease dependency: Suave
- PkgManagerModule.cleanupRemovedPackages (cognitive 43) src/Perla.PkgManager/PkgManager.fs:476
- Handlers.runTesting (cognitive 43) src/Perla/Handlers.fs:839
- Handlers.runRestore (cognitive 36) src/Perla/Handlers.fs:1369
- Handlers.runTemplate (cognitive 35) src/Perla/Handlers.fs:331
- Handlers.runRemovePackage (cognitive 30) src/Perla/Handlers.fs:1187
- Build.getMissingLocalDependencies (cognitive 28) src/Perla/Build.fs:233
- TestingServiceModule.Create (cognitive 25) src/Perla/Testing.fs:892
- FileSystem.GetManager (cognitive 25) src/Perla/FileSystem.fs:122
- VirtualFs.Create (cognitive 24) src/Perla/VirtualFileSystem.fs:712
- PlatformOpsModule.Create (cognitive 24) src/Perla/PlatformOps.fs:208
- Check.Setup (cognitive 23) src/Perla/Orchestration.fs:40
- ProviderOps.extractFilePath (cognitive 22) src/Perla.PkgManager/Provider.fs:61
- PkgManagerModule.goOffline (cognitive 21) src/Perla.PkgManager/PkgManager.fs:607
- ProviderOps.extractPkgAndVersion (cognitive 20) src/Perla.PkgManager/Provider.fs:155
- Commands.Test (cognitive 19) src/Perla/Commands.fs:827
- PluginManagerModule.Create (cognitive 17) src/Perla.Plugins/Registry.fs:82
- Handlers.runAddPackage (cognitive 17) src/Perla/Handlers.fs:1040
- BuildServiceModule.Create (cognitive 17) src/Perla/Build.fs:311
- PerlaConfig.UpdateFileFields (cognitive 17) src/Perla/Json.fs:807
- Print.BrowserReport (cognitive 16) src/Perla/Testing.fs:215
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (35 lines × 2) src/Perla/Handlers.fs:736
- Duplicated block (33–34 lines × 5) src/Perla/Commands.fs:378
- Duplicated block (27 lines × 2) src/Perla/SuaveService.fs:1641
- Duplicated block (26 lines × 2) src/Perla/Handlers.fs:778
- Duplicated block (22 lines × 2) src/Perla.PkgManager/PkgManager.fs:389
- Duplicated block (21 lines × 2) src/Perla/Testing.fs:918
- Duplicated block (17–20 lines × 2) src/Perla/Configuration.fs:33
- Duplicated block (15–18 lines × 2) src/Perla.Logger/Library.fs:148
- Duplicated block (13–16 lines × 2) src/Perla/SuaveService.fs:351
- Duplicated block (13–15 lines × 3) src/Perla.PkgManager/RequestHandler.fs:63
- Duplicated block (10–13 lines × 2) src/Perla/SuaveService.fs:1000
- Duplicated block (9–12 lines × 2) src/Perla/Configuration.fs:68
- Duplicated block (10–12 lines × 2) src/Perla/VirtualFileSystem.fs:635
- Duplicated block (11 lines × 2) src/Perla/Library.fs:144
- Duplicated block (10–11 lines × 2) src/Perla/SuaveService.fs:1405
- Duplicated block (9–10 lines × 3) src/Perla.Logger/Library.fs:116
- Duplicated block (8–10 lines × 2) src/Perla.Fable.Mocha/Library.fs:122
- Duplicated block (9–10 lines × 2) src/Perla/SuaveService.fs:1422
- Duplicated block (8–9 lines × 2) src/Perla.Fable.QUnit/Library.fs:430
- Duplicated block (8 lines × 3) src/Perla/Database.fs:293
- Duplicated block (5 lines × 2) src/Perla.Logger/Library.fs:130
- Duplicated block (9 lines × 3) src/Perla.Fable.Mocha/Library.fs:37
- Duplicated block (5 lines × 5) src/Perla.Fable.Mocha/Library.fs:28
- No test project references Perla.Fable.Mocha src/Perla.Fable.Mocha/Perla.Fable.Mocha.fsproj
- No test project references Perla.Fable.QUnit src/Perla.Fable.QUnit/Perla.Fable.QUnit.fsproj
- Duplicated block (33 lines × 2 locations) src/Perla/livereload.js:5
- Duplicated block (16 lines × 2 locations) src/Perla/qunit-runner.js:68
- Duplicated block (14 lines × 2 locations) src/Perla/testing-helpers.js:36
- Duplicated block (12 lines × 2 locations) src/Perla/mocha-runner.js:115
- Duplicated block with local edits (9 matched lines × 2 locations) src/Perla/offline-templates/basic/src/main.js:1
- Dead file (~164 LoC) src/Perla/qunit-runner.js
- Dead file (~133 LoC) src/Perla/mocha-runner.js
- Dead file (~126 LoC) src/Perla/testing-helpers.js
- Dead file (~95 LoC) src/Perla/livereload.js
- Dead file (~69 LoC) src/Perla/worker.js
- Third-party script without Subresource Integrity src/Perla/offline-templates/basic/index.html:9
Minor — 45 finding(s)
- Orphaned file src/Perla/Json.fs:1
- Orphaned file src/Perla/VirtualFileSystem.fs:1
- Orphaned file src/Perla.PkgManager/PkgManager.fs:1
- Orphaned file src/Perla/FileSystem.fs:1
- Orphaned file src/Perla/Database.fs:1
- Orphaned file src/Perla/Build.fs:1
- Orphaned file src/Perla.Fable.Mocha/Library.fs:1
- Orphaned file src/Perla/Orchestration.fs:1
- Orphaned file src/Perla/PlatformOps.fs:1
- Orphaned file src/Perla.Fable.QUnit/Library.fs:1
- Orphaned file src/Perla.Logger/Library.fs:1
- Orphaned file src/Perla.PkgManager/Types.fs:1
- Orphaned file src/Perla/Library.fs:1
- Orphaned file src/Perla/Types.fs:1
- Orphaned file src/Perla.PkgManager/Provider.fs:1
- Orphaned file src/Perla.Plugins/Library.fs:1
- Orphaned file src/Perla.Plugins/Registry.fs:1
- Orphaned file src/Perla/Esbuild.fs:1
- Orphaned file src/Perla/Scaffolding.fs:1
- Orphaned file src/Perla/ImportMaps.fs:1
- Orphaned file src/Perla/Directories.fs:1
- Orphaned file src/Perla/Configuration.fs:1
- Orphaned file src/Perla/Extensibility.fs:1
- Orphaned file src/Perla.PkgManager/RequestHandler.fs:1
- Orphaned file src/Perla/Extensions.fs:1
- Most significant orphaned file src/Perla/SuaveService.fs:1
- Most significant orphaned file src/Perla/Handlers.fs:1
- Most significant orphaned file src/Perla/Testing.fs:1
- REDACTED
- REDACTED
- Outdated: coverlet.collector REDACTED:9
- No ADRs found src/Perla/Perla.fsproj:4
- `FindOne should return repository when searching by ID` spells `ID` where 14 names in the project spell it `Id` tests/Perla.Tests/Database.Tests.fs:271
- Projects may be oversized for their cohesion
- Scattered collaborators
- Concentrated knowledge decay
- REDACTED
- No ADRs
- No SAST REDACTED:16
- No dependency-update automation REDACTED:7
- No changelog
- Duplicated predicate src/Perla/livereload.js:25
- Silent fallback default in catch src/Perla/worker.js:12
Minor — 27 finding(s)
- Outdated: Fable.Core
- Outdated: Fable.Package.SDK
- Outdated: FSharp.Core
- Outdated: Microsoft.Extensions.Logging
- Outdated: Serilog
- Outdated: Serilog.Extensions.Logging
- Outdated: Spectre.Console
- Outdated: FsHttp
- Outdated: FsToolkit.ErrorHandling
- Outdated: IcedTasks
- Outdated: JDeck
- Outdated: FSharp.Compiler.Service
- Outdated: FSharp.Control.AsyncSeq
- Outdated: AngleSharp
- Outdated: CliWrap
- Outdated: Fake.IO.FileSystem
- Outdated: FSharp.Control.TaskSeq
- Outdated: FSharp.Data.Adaptive
- Outdated: FSharp.SystemCommandLine
- Outdated: FsToolkit.ErrorHandling.IcedTasks
- Outdated: Microsoft.Playwright
- Outdated: Scriban
- Outdated: Suave
- Outdated: System.IO.Pipelines
- Outdated: Microsoft.NET.Test.Sdk
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-e60d28c446274df18693072adce5fe19/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-e60d28c446274df18693072adce5fe19/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 . | 10 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Perla.slnx package --vulnerable --include-transitive --format json | 2 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 11 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `docs/src/router.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-947e7e2bb0924a8b893b61792128b144 | 0 | artifacts/raw/osv-scanner.json |