Executive summary
AngelMunoz/Migrondi falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 64 out of 100 and is rated Adequate, and all 12 of its critical findings are security problems in the build pipeline.
Code Health, at 60, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step for the work it takes is recording design decisions, worth about 3 points. Turning on missing-value checks would lift Code Health itself, worth about 4 points.
Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two pipeline steps run downloads nobody checks, and one secret can leak from the build pipeline. Pinning each tool to an exact version, checking each download against a checksum and limiting the secret to its own step would close these risks.
The product code is 10,832 lines, about €17,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 54 findings
- Cyclomatic Complexity · VirtualFs.getVirtualFs (cyclomatic 25) src/Migrondi.UI/Logic/VirtualFs.fs
- Cyclomatic Complexity · ProjectDetails.create (cyclomatic 18) src/Migrondi.UI/Views/ProjectDetails.fs
- Cognitive Complexity · ProjectDetails.highlightText (cognitive 29) src/Migrondi.UI/Views/ProjectDetails.fs
- Cognitive Complexity · ProjectDetails.migrationPane (cognitive 16) src/Migrondi.UI/Views/ProjectDetails.fs
- God Classes · FileTooLong: Views/ProjectDetails.fs src/Migrondi.UI/Views/ProjectDetails.fs
- God Classes · FileTooLong: Migrondi.Mcp/Server.fs src/Migrondi.Mcp/Server.fs
- God Classes · FileTooLong: Migrondi/Handlers.fs src/Migrondi/Handlers.fs
- God Classes · FileTooLong: Migrondi.Mcp/SingleProject.fs src/Migrondi.Mcp/SingleProject.fs
- Code Duplication · Edited copy of a member (5 corresponding lines) .agents/skills/fsharp-signature-files/scripts/breaks/HiddenRecordConstruction/Lib.fs
- Code Duplication · Duplicated block (21 lines × 2) src/Migrondi.UI/Logic/VirtualFs.fs
- Code Duplication · Duplicated block (20 lines × 2) src/Migrondi.UI/Logic/Database.fs
- Code Duplication · Duplicated block (18 lines × 2) src/Migrondi.UI/Logic/Database.fs
- Code Duplication · Duplicated block (15 lines × 2) src/Migrondi.Mcp/Server.fs
- Code Duplication · Duplicated block (15 lines × 2) src/Migrondi.UI/Views/Common.fs
- Code Duplication · Duplicated block (12–14 lines × 2) src/Migrondi.Mcp/Tools.fs
- Code Duplication · Duplicated block (13 lines × 2) src/Migrondi.Mcp/ProjectBinding.fs
- Code Duplication · Duplicated block (10 lines × 2) src/Migrondi.UI/Logic/Services.fs
- Code Duplication · Duplicated block (6 lines × 2) src/Migrondi/Handlers.fs
- Code Duplication · Duplicated block (13 lines × 2) src/Migrondi.UI/Views/NewProject.fs
- Code Duplication · Duplicated block (8 lines × 2) src/Migrondi.UI/Views/Shell.fs
- Cohesion (LCOM4) · Low cohesion: ProjectCollection (LCOM4 5) src/Migrondi.UI/Logic/Services.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Program.fs src/Migrondi.UI/Program.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Views/Shell.fs src/Migrondi.UI/Views/Shell.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Views/NewProject.fs src/Migrondi.UI/Views/NewProject.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Views/ProjectDetails.fs src/Migrondi.UI/Views/ProjectDetails.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Views/Landing.fs src/Migrondi.UI/Views/Landing.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Views/ProjectSettings.fs src/Migrondi.UI/Views/ProjectSettings.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Views/Common.fs src/Migrondi.UI/Views/Common.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Feedback.fs src/Migrondi.UI/Feedback.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Host.fs src/Migrondi.UI/Host.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Types.fs src/Migrondi.UI/Types.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Mcp/Server.fs src/Migrondi.UI/Mcp/Server.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Logic/Migrations.fs src/Migrondi.UI/Logic/Migrations.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Logic/OsOperations.fs src/Migrondi.UI/Logic/OsOperations.fs
- Code Coverage · Low coverage: src/Migrondi.UI/Logic/Services.fs src/Migrondi.UI/Logic/Services.fs
- Code Coverage · Low coverage: src/Migrondi.Mcp/Server.fs src/Migrondi.Mcp/Server.fs
- Code Coverage · Low coverage: src/Migrondi.Mcp/Results.fs src/Migrondi.Mcp/Results.fs
- Code Coverage · Low coverage: src/Migrondi/Commands.fs src/Migrondi/Commands.fs
- Code Coverage · Low coverage: src/Migrondi/Handlers.fs src/Migrondi/Handlers.fs
- Code Coverage · No test project references Break .agents/skills/fsharp-signature-files/scripts/breaks/HiddenHelper/Break.fsproj
- Code Coverage · No test project references Break .agents/skills/fsharp-signature-files/scripts/breaks/HiddenRecordConstruction/Break.fsproj
- Code Coverage · No test project references Break .agents/skills/fsharp-signature-files/scripts/breaks/HiddenUnionCase/Break.fsproj
- Code Coverage · No test project references Break .agents/skills/fsharp-signature-files/scripts/breaks/InterfaceNotListed/Break.fsproj
- Code Coverage · No test project references Break .agents/skills/fsharp-signature-files/scripts/breaks/MissingQualifiedAccess/Break.fsproj
- Code Coverage · No test project references Break .agents/skills/fsharp-signature-files/scripts/breaks/PrivateRepresentation/Break.fsproj
- Code Coverage · No test project references Domain .agents/skills/fsharp-native-aot/scripts/Domain/Domain.fsproj
- Code Coverage · No test project references Shape .agents/skills/fsharp-module-shape/scripts/Shape/Shape.fsproj
- Code Coverage · No test project references StateMachine .agents/skills/fsharp-async-composition/scripts/StateMachine/StateMachine.fsproj
- Code Coverage · No test project references DomainJson .agents/skills/fsharp-native-aot/scripts/DomainJson/DomainJson.csproj
- Code Coverage · No test project references Generate .agents/skills/fsharp-signature-files/scripts/Generate/Generate.fsproj
- Code Coverage · No test project references Probe .agents/skills/fsharp-native-aot/scripts/Probe/Probe.fsproj
- Code Coverage · No test project references WarnGate .agents/skills/fsharp-native-aot/scripts/WarnGate/WarnGate.fsproj
- Churn × Complexity Hotspots · Hotspot: src/Migrondi/Handlers.fs src/Migrondi/Handlers.fs
- Churn × Complexity Hotspots · Hotspot: src/Migrondi.UI/Logic/VirtualFs.fs src/Migrondi.UI/Logic/VirtualFs.fs
Fixed since the last survey: 30 findings
- Cyclomatic Complexity · VirtualFs.getVirtualFs (cyclomatic 25) src/MigrondiUI/VirtualFs.fs
- God Classes · FileTooLong: Mcp/Server.fs src/MigrondiUI/Mcp/Server.fs
- Code Duplication · Near-duplicate member pair (145 shared lines) src/MigrondiUI/Views/LocalProjectDetails.fs
- Code Duplication · Duplicated block (126–127 lines × 2) src/Migrondi.Core/Database.fs
- Code Duplication · Duplicated block (52–53 lines × 2) src/MigrondiUI/Views/LocalProjectDetails.fs
- Code Duplication · Duplicated block (35–36 lines × 2) src/MigrondiUI/Views/LocalProjectDetails.fs
- Code Duplication · Duplicated block (29–31 lines × 2) src/Migrondi.Core/Migrondi.fs
- Code Duplication · Duplicated block (26–27 lines × 2) src/MigrondiUI/Views/LocalProjectDetails.fs
- Code Duplication · Duplicated block (21 lines × 2) src/MigrondiUI/VirtualFs.fs
- Code Duplication · Duplicated block (20 lines × 2) src/MigrondiUI/Database.fs
- Code Duplication · Duplicated block (18 lines × 2) src/MigrondiUI/Database.fs
- Code Duplication · Duplicated block (15 lines × 2) src/MigrondiUI/Mcp/Server.fs
- Code Duplication · Duplicated block (13–15 lines × 2) src/MigrondiUI/Mcp/Tools.fs
- Code Duplication · Duplicated block (14–15 lines × 2) src/MigrondiUI/Views/LocalProjectDetails.fs
- Code Duplication · Duplicated block (11–12 lines × 2) src/MigrondiUI/Components/TextEditor.fs
- Code Duplication · Duplicated block (11 lines × 2) src/MigrondiUI/Components/Fields.fs
- Code Duplication · Duplicated block (10 lines × 2) src/MigrondiUI/Services.fs
- Code Duplication · Duplicated block (8 lines × 2) src/MigrondiUI/Views/VirtualProjectDetails.fs
- Code Duplication · Duplicated block (6–7 lines × 2) src/MigrondiUI/Views/LocalProjectDetails.fs
- Code Duplication · Duplicated block (11 lines × 2) src/MigrondiUI/Views/LocalProjectDetails.fs
- Code Duplication · Duplicated block (7 lines × 2) src/MigrondiUI/Components/VirtualProjectForm.fs
- Dependency Hygiene · Deprecated: MSTest src/Directory.Packages.props
- Dependency Hygiene · Deprecated: MSTest.TestAdapter
- Dependency Hygiene · Deprecated: MSTest.TestFramework
- License Compliance · Banned license: MySql.Data src/Directory.Packages.props
- Churn × Complexity Hotspots · Hotspot: src/MigrondiUI/VirtualFs.fs src/MigrondiUI/VirtualFs.fs
- Dependency Vulnerabilities · High CVE: System.Security.Cryptography.Pkcs 8.0.1 src/Migrondi.Core/Migrondi.Core.fsproj
- Dependency Vulnerabilities · High CVE: System.Security.Cryptography.Pkcs 9.0.13 src/Migrondi.Core/Migrondi.Core.fsproj
- Dependency Vulnerabilities · Medium CVE: Microsoft.Build.Tasks.Git 10.0.300 Directory.Build.props
- Documentation (README) · README may be stale
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,500 to €28,000, for 92 to 290 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 64. 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: 10,832 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 Domain | 2 Migrondi.UI.Database | 3 Migrondi.UI.Logic | 4 Migrondi.UI.Mcp | 5 Migrondi.UI.Views.Common | 6 Shop.Ordering | 7 DomainJsonConverters | 8 Migrondi.Core.Serialization | 9 Migrondi.UI.Host | 10 Migrondi.UI.Types | 11 Migrondi.Core.FileSystem | 12 Migrondi.UI.Feedback | 13 Migrondi.UI.Views.NewProject | 14 Migrondi.UI.Views.ProjectDetails | 15 Migrondi.Core | 16 Migrondi.Core.Database | 17 Migrondi.Core.Database.MigrationsImpl | 18 Migrondi.Core.MigrondiserviceImpl | 19 Migrondi.Env.Configuration | 20 Migrondi.Handlers.Init | 21 Migrondi.Handlers.Migrations | 22 Migrondi.Inputs.ListArgs | 23 MigrondiUI | 24 Migrondi.Env | 25 Migrondi.Mcp.McpResults | 26 MigrondiUI.Services | 27 Migrondi.Commands.ArgumentMapper | 28 Migrondi.Commands.Commands | 29 Migrondi.Mcp | 30 Migrondi.Handlers.Mcp | 31 Migrondi.Mcp.HttpServer | 32 Migrondi.Mcp.McpTools | 33 Migrondi.Mcp.ProjectBindingModule | 34 Migrondi.Mcp.ProjectInit | 35 Migrondi.Mcp.ServerBuilder | 36 Migrondi.Mcp.ServerBuilder.ReadTools | 37 Migrondi.Mcp.ServerBuilder.WriteTools | 38 Migrondi.Mcp.SingleProjectServer | 39 Migrondi.Mcp.SingleProjectTools | 40 Migrondi.Handlers.Mcp.Transport |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Domain | ||||||||||||||||||||||||||||||||||||||||
| 2 Migrondi.UI.Database | ||||||||||||||||||||||||||||||||||||||||
| 3 Migrondi.UI.Logic | ||||||||||||||||||||||||||||||||||||||||
| 4 Migrondi.UI.Mcp | ||||||||||||||||||||||||||||||||||||||||
| 5 Migrondi.UI.Views.Common | ||||||||||||||||||||||||||||||||||||||||
| 6 Shop.Ordering | ||||||||||||||||||||||||||||||||||||||||
| 7 DomainJsonConverters | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 Migrondi.Core.Serialization | 6 | |||||||||||||||||||||||||||||||||||||||
| 9 Migrondi.UI.Host | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Migrondi.UI.Types | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Migrondi.Core.FileSystem | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 Migrondi.UI.Feedback | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 Migrondi.UI.Views.NewProject | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 14 Migrondi.UI.Views.ProjectDetails | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 15 Migrondi.Core | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Migrondi.Core.Database | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 Migrondi.Core.Database.MigrationsImpl | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Migrondi.Core.MigrondiserviceImpl | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Migrondi.Env.Configuration | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 Migrondi.Handlers.Init | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 Migrondi.Handlers.Migrations | 4 | |||||||||||||||||||||||||||||||||||||||
| 22 Migrondi.Inputs.ListArgs | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 MigrondiUI | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 Migrondi.Env | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 Migrondi.Mcp.McpResults | 9 | 5 | ||||||||||||||||||||||||||||||||||||||
| 26 MigrondiUI.Services | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 Migrondi.Commands.ArgumentMapper | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 Migrondi.Commands.Commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 Migrondi.Mcp | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 Migrondi.Handlers.Mcp | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 Migrondi.Mcp.HttpServer | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 Migrondi.Mcp.McpTools | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Migrondi.Mcp.ProjectBindingModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 34 Migrondi.Mcp.ProjectInit | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 Migrondi.Mcp.ServerBuilder | 4 | |||||||||||||||||||||||||||||||||||||||
| 36 Migrondi.Mcp.ServerBuilder.ReadTools | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 Migrondi.Mcp.ServerBuilder.WriteTools | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 Migrondi.Mcp.SingleProjectServer | 2 | |||||||||||||||||||||||||||||||||||||||
| 39 Migrondi.Mcp.SingleProjectTools | 5 | |||||||||||||||||||||||||||||||||||||||
| 40 Migrondi.Handlers.Mcp.Transport | 1 | 1 |
7→1 DomainJsonConverters uses Domain✕
- Connections
- 1 pair of types, where a type in DomainJsonConverters uses a type in Domain.
- The types involved
DomainJsonConverters.ShapeConverter→Domain.Shape
- Direction
- DomainJsonConverters uses Domain, so a change to Domain can break DomainJsonConverters, while a change to DomainJsonConverters can't break Domain.
- Position
- Below the diagonal: DomainJsonConverters uses a module listed above it, which is the healthy direction.
8→15 Migrondi.Core.Serialization uses Migrondi.Core part of a loop✕
- Connections
- 6 pairs of types, where a type in Migrondi.Core.Serialization uses a type in Migrondi.Core.
- The types involved
Migrondi.Core.Serialization.IMiConfigurationSerializer→Migrondi.Core.MigrondiConfigMigrondi.Core.Serialization.IMiMigrationSerializer→Migrondi.Core.MigrationMigrondi.Core.Serialization.IMiMigrationSerializer→Migrondi.Core.MigrationRecordMigrondi.Core.Serialization.MiSerializer→Migrondi.Core.MigrationMigrondi.Core.Serialization.MiSerializer→Migrondi.Core.MigrationRecordMigrondi.Core.Serialization.MiSerializer→Migrondi.Core.MigrondiConfig
- Direction
- Migrondi.Core.Serialization uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Core.Serialization, while a change to Migrondi.Core.Serialization can't break Migrondi.Core.
- 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.
9→3 Migrondi.UI.Host uses Migrondi.UI.Logic✕
- Connections
- 1 pair of types, where a type in Migrondi.UI.Host uses a type in Migrondi.UI.Logic.
- The types involved
Migrondi.UI.Host.FilePicker→Migrondi.UI.Logic.IFilePicker
- Direction
- Migrondi.UI.Host uses Migrondi.UI.Logic, so a change to Migrondi.UI.Logic can break Migrondi.UI.Host, while a change to Migrondi.UI.Host can't break Migrondi.UI.Logic.
- Position
- Below the diagonal: Migrondi.UI.Host uses a module listed above it, which is the healthy direction.
10→3 Migrondi.UI.Types uses Migrondi.UI.Logic✕
- Connections
- 1 pair of types, where a type in Migrondi.UI.Types uses a type in Migrondi.UI.Logic.
- The types involved
Migrondi.UI.Types.IProvideFilePicker→Migrondi.UI.Logic.IFilePicker
- Direction
- Migrondi.UI.Types uses Migrondi.UI.Logic, so a change to Migrondi.UI.Logic can break Migrondi.UI.Types, while a change to Migrondi.UI.Types can't break Migrondi.UI.Logic.
- Position
- Below the diagonal: Migrondi.UI.Types uses a module listed above it, which is the healthy direction.
11→8 Migrondi.Core.FileSystem uses Migrondi.Core.Serialization✕
- Connections
- 2 pairs of types, where a type in Migrondi.Core.FileSystem uses a type in Migrondi.Core.Serialization.
- The types involved
Migrondi.Core.FileSystem.MiFileSystem→Migrondi.Core.Serialization.IMiConfigurationSerializerMigrondi.Core.FileSystem.MiFileSystem→Migrondi.Core.Serialization.IMiMigrationSerializer
- Direction
- Migrondi.Core.FileSystem uses Migrondi.Core.Serialization, so a change to Migrondi.Core.Serialization can break Migrondi.Core.FileSystem, while a change to Migrondi.Core.FileSystem can't break Migrondi.Core.Serialization.
- Position
- Below the diagonal: Migrondi.Core.FileSystem uses a module listed above it, which is the healthy direction.
11→15 Migrondi.Core.FileSystem uses Migrondi.Core part of a loop✕
- Connections
- 2 pairs of types, where a type in Migrondi.Core.FileSystem uses a type in Migrondi.Core.
- The types involved
Migrondi.Core.FileSystem.IMiFileSystem→Migrondi.Core.MigrationMigrondi.Core.FileSystem.IMiFileSystem→Migrondi.Core.MigrondiConfig
- Direction
- Migrondi.Core.FileSystem uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Core.FileSystem, while a change to Migrondi.Core.FileSystem can't break Migrondi.Core.
- 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.
12→10 Migrondi.UI.Feedback uses Migrondi.UI.Types✕
- Connections
- 2 pairs of types, where a type in Migrondi.UI.Feedback uses a type in Migrondi.UI.Types.
- The types involved
Migrondi.UI.Feedback.Feedback→Migrondi.UI.Types.IPostUIMigrondi.UI.Feedback.FeedbackCell→Migrondi.UI.Types.IFeedback
- Direction
- Migrondi.UI.Feedback uses Migrondi.UI.Types, so a change to Migrondi.UI.Types can break Migrondi.UI.Feedback, while a change to Migrondi.UI.Feedback can't break Migrondi.UI.Types.
- Position
- Below the diagonal: Migrondi.UI.Feedback uses a module listed above it, which is the healthy direction.
13→3 Migrondi.UI.Views.NewProject uses Migrondi.UI.Logic✕
- Connections
- 1 pair of types, where a type in Migrondi.UI.Views.NewProject uses a type in Migrondi.UI.Logic.
- The types involved
Migrondi.UI.Views.NewProject.Operations→Migrondi.UI.Logic.IFilePicker
- Direction
- Migrondi.UI.Views.NewProject uses Migrondi.UI.Logic, so a change to Migrondi.UI.Logic can break Migrondi.UI.Views.NewProject, while a change to Migrondi.UI.Views.NewProject can't break Migrondi.UI.Logic.
- Position
- Below the diagonal: Migrondi.UI.Views.NewProject uses a module listed above it, which is the healthy direction.
13→5 Migrondi.UI.Views.NewProject uses Migrondi.UI.Views.Common✕
- Connections
- 1 pair of types, where a type in Migrondi.UI.Views.NewProject uses a type in Migrondi.UI.Views.Common.
- The types involved
Migrondi.UI.Views.NewProject.NewProject→Migrondi.UI.Views.Common.Palette
- Direction
- Migrondi.UI.Views.NewProject uses Migrondi.UI.Views.Common, so a change to Migrondi.UI.Views.Common can break Migrondi.UI.Views.NewProject, while a change to Migrondi.UI.Views.NewProject can't break Migrondi.UI.Views.Common.
- Position
- Below the diagonal: Migrondi.UI.Views.NewProject uses a module listed above it, which is the healthy direction.
13→10 Migrondi.UI.Views.NewProject uses Migrondi.UI.Types✕
- Connections
- 2 pairs of types, where a type in Migrondi.UI.Views.NewProject uses a type in Migrondi.UI.Types.
- The types involved
Migrondi.UI.Views.NewProject.Operations→Migrondi.UI.Types.IFeedbackMigrondi.UI.Views.NewProject.Operations→Migrondi.UI.Types.IPostUI
- Direction
- Migrondi.UI.Views.NewProject uses Migrondi.UI.Types, so a change to Migrondi.UI.Types can break Migrondi.UI.Views.NewProject, while a change to Migrondi.UI.Views.NewProject can't break Migrondi.UI.Types.
- Position
- Below the diagonal: Migrondi.UI.Views.NewProject uses a module listed above it, which is the healthy direction.
14→5 Migrondi.UI.Views.ProjectDetails uses Migrondi.UI.Views.Common✕
- Connections
- 2 pairs of types, where a type in Migrondi.UI.Views.ProjectDetails uses a type in Migrondi.UI.Views.Common.
- The types involved
Migrondi.UI.Views.ProjectDetails.MigrationSpans→Migrondi.UI.Views.Common.PaletteMigrondi.UI.Views.ProjectDetails.ProjectDetails→Migrondi.UI.Views.Common.Palette
- Direction
- Migrondi.UI.Views.ProjectDetails uses Migrondi.UI.Views.Common, so a change to Migrondi.UI.Views.Common can break Migrondi.UI.Views.ProjectDetails, while a change to Migrondi.UI.Views.ProjectDetails can't break Migrondi.UI.Views.Common.
- Position
- Below the diagonal: Migrondi.UI.Views.ProjectDetails uses a module listed above it, which is the healthy direction.
14→10 Migrondi.UI.Views.ProjectDetails uses Migrondi.UI.Types✕
- Connections
- 3 pairs of types, where a type in Migrondi.UI.Views.ProjectDetails uses a type in Migrondi.UI.Types.
- The types involved
Migrondi.UI.Views.ProjectDetails.Operations→Migrondi.UI.Types.IFeedbackMigrondi.UI.Views.ProjectDetails.Operations→Migrondi.UI.Types.IPostUIMigrondi.UI.Views.ProjectDetails.Operations→Migrondi.UI.Types.ThemeStore
- Direction
- Migrondi.UI.Views.ProjectDetails uses Migrondi.UI.Types, so a change to Migrondi.UI.Types can break Migrondi.UI.Views.ProjectDetails, while a change to Migrondi.UI.Views.ProjectDetails can't break Migrondi.UI.Types.
- Position
- Below the diagonal: Migrondi.UI.Views.ProjectDetails uses a module listed above it, which is the healthy direction.
15→11 Migrondi.Core uses Migrondi.Core.FileSystem✕
- Connections
- 1 pair of types, where a type in Migrondi.Core uses a type in Migrondi.Core.FileSystem.
- The types involved
Migrondi.Core.Migrondi→Migrondi.Core.FileSystem.IMiMigrationSource
- Direction
- Migrondi.Core uses Migrondi.Core.FileSystem, so a change to Migrondi.Core.FileSystem can break Migrondi.Core, while a change to Migrondi.Core can't break Migrondi.Core.FileSystem.
- Position
- Below the diagonal: Migrondi.Core uses a module listed above it, which is the healthy direction.
16→15 Migrondi.Core.Database uses Migrondi.Core✕
- Connections
- 3 pairs of types, where a type in Migrondi.Core.Database uses a type in Migrondi.Core.
- The types involved
Migrondi.Core.Database.IMiDatabaseHandler→Migrondi.Core.MigrationMigrondi.Core.Database.IMiDatabaseHandler→Migrondi.Core.MigrationRecordMigrondi.Core.Database.MiDatabaseHandler→Migrondi.Core.MigrondiConfig
- Direction
- Migrondi.Core.Database uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Core.Database, while a change to Migrondi.Core.Database can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Core.Database uses a module listed above it, which is the healthy direction.
17→15 Migrondi.Core.Database.MigrationsImpl uses Migrondi.Core✕
- Connections
- 1 pair of types, where a type in Migrondi.Core.Database.MigrationsImpl uses a type in Migrondi.Core.
- The types involved
Migrondi.Core.Database.MigrationsImpl.MigrationsImpl→Migrondi.Core.MigrondiDriver
- Direction
- Migrondi.Core.Database.MigrationsImpl uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Core.Database.MigrationsImpl, while a change to Migrondi.Core.Database.MigrationsImpl can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Core.Database.MigrationsImpl uses a module listed above it, which is the healthy direction.
18→15 Migrondi.Core.MigrondiserviceImpl uses Migrondi.Core✕
- Connections
- 1 pair of types, where a type in Migrondi.Core.MigrondiserviceImpl uses a type in Migrondi.Core.
- The types involved
Migrondi.Core.MigrondiserviceImpl.MigrondiserviceImpl→Migrondi.Core.MigrondiConfig
- Direction
- Migrondi.Core.MigrondiserviceImpl uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Core.MigrondiserviceImpl, while a change to Migrondi.Core.MigrondiserviceImpl can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Core.MigrondiserviceImpl uses a module listed above it, which is the healthy direction.
19→8 Migrondi.Env.Configuration uses Migrondi.Core.Serialization✕
- Connections
- 1 pair of types, where a type in Migrondi.Env.Configuration uses a type in Migrondi.Core.Serialization.
- The types involved
Migrondi.Env.Configuration.Configuration→Migrondi.Core.Serialization.IMiConfigurationSerializer
- Direction
- Migrondi.Env.Configuration uses Migrondi.Core.Serialization, so a change to Migrondi.Core.Serialization can break Migrondi.Env.Configuration, while a change to Migrondi.Env.Configuration can't break Migrondi.Core.Serialization.
- Position
- Below the diagonal: Migrondi.Env.Configuration uses a module listed above it, which is the healthy direction.
19→15 Migrondi.Env.Configuration uses Migrondi.Core✕
- Connections
- 1 pair of types, where a type in Migrondi.Env.Configuration uses a type in Migrondi.Core.
- The types involved
Migrondi.Env.Configuration.Configuration→Migrondi.Core.MigrondiConfig
- Direction
- Migrondi.Env.Configuration uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Env.Configuration, while a change to Migrondi.Env.Configuration can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Env.Configuration uses a module listed above it, which is the healthy direction.
20→8 Migrondi.Handlers.Init uses Migrondi.Core.Serialization✕
- Connections
- 1 pair of types, where a type in Migrondi.Handlers.Init uses a type in Migrondi.Core.Serialization.
- The types involved
Migrondi.Handlers.Init.Init→Migrondi.Core.Serialization.IMiConfigurationSerializer
- Direction
- Migrondi.Handlers.Init uses Migrondi.Core.Serialization, so a change to Migrondi.Core.Serialization can break Migrondi.Handlers.Init, while a change to Migrondi.Handlers.Init can't break Migrondi.Core.Serialization.
- Position
- Below the diagonal: Migrondi.Handlers.Init uses a module listed above it, which is the healthy direction.
20→11 Migrondi.Handlers.Init uses Migrondi.Core.FileSystem✕
- Connections
- 1 pair of types, where a type in Migrondi.Handlers.Init uses a type in Migrondi.Core.FileSystem.
- The types involved
Migrondi.Handlers.Init.Init→Migrondi.Core.FileSystem.IMiFileSystem
- Direction
- Migrondi.Handlers.Init uses Migrondi.Core.FileSystem, so a change to Migrondi.Core.FileSystem can break Migrondi.Handlers.Init, while a change to Migrondi.Handlers.Init can't break Migrondi.Core.FileSystem.
- Position
- Below the diagonal: Migrondi.Handlers.Init uses a module listed above it, which is the healthy direction.
20→15 Migrondi.Handlers.Init uses Migrondi.Core✕
- Connections
- 1 pair of types, where a type in Migrondi.Handlers.Init uses a type in Migrondi.Core.
- The types involved
Migrondi.Handlers.Init.Init→Migrondi.Core.MigrondiConfig
- Direction
- Migrondi.Handlers.Init uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Handlers.Init, while a change to Migrondi.Handlers.Init can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Handlers.Init uses a module listed above it, which is the healthy direction.
21→15 Migrondi.Handlers.Migrations uses Migrondi.Core✕
- Connections
- 4 pairs of types, where a type in Migrondi.Handlers.Migrations uses a type in Migrondi.Core.
- The types involved
Migrondi.Handlers.Migrations.ListFilters→Migrondi.Core.MigrationTypeMigrondi.Handlers.Migrations.Migrations→Migrondi.Core.IMigrondiMigrondi.Handlers.Migrations.Migrations→Migrondi.Core.MigrationMigrondi.Handlers.Migrations.Migrations→Migrondi.Core.MigrationStatus
- Direction
- Migrondi.Handlers.Migrations uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Handlers.Migrations, while a change to Migrondi.Handlers.Migrations can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Handlers.Migrations uses a module listed above it, which is the healthy direction.
22→15 Migrondi.Inputs.ListArgs uses Migrondi.Core✕
- Connections
- 1 pair of types, where a type in Migrondi.Inputs.ListArgs uses a type in Migrondi.Core.
- The types involved
Migrondi.Inputs.ListArgs.ListArgs→Migrondi.Core.MigrationType
- Direction
- Migrondi.Inputs.ListArgs uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Inputs.ListArgs, while a change to Migrondi.Inputs.ListArgs can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Inputs.ListArgs uses a module listed above it, which is the healthy direction.
23→15 MigrondiUI uses Migrondi.Core✕
- Connections
- 2 pairs of types, where a type in MigrondiUI uses a type in Migrondi.Core.
- The types involved
MigrondiUI.LocalProject→Migrondi.Core.MigrondiConfigMigrondiUI.VirtualProject→Migrondi.Core.MigrondiDriver
- Direction
- MigrondiUI uses Migrondi.Core, so a change to Migrondi.Core can break MigrondiUI, while a change to MigrondiUI can't break Migrondi.Core.
- Position
- Below the diagonal: MigrondiUI uses a module listed above it, which is the healthy direction.
24→8 Migrondi.Env uses Migrondi.Core.Serialization✕
- Connections
- 2 pairs of types, where a type in Migrondi.Env uses a type in Migrondi.Core.Serialization.
- The types involved
Migrondi.Env.AppEnv→Migrondi.Core.Serialization.IMiConfigurationSerializerMigrondi.Env.AppEnv→Migrondi.Core.Serialization.IMiMigrationSerializer
- Direction
- Migrondi.Env uses Migrondi.Core.Serialization, so a change to Migrondi.Core.Serialization can break Migrondi.Env, while a change to Migrondi.Env can't break Migrondi.Core.Serialization.
- Position
- Below the diagonal: Migrondi.Env uses a module listed above it, which is the healthy direction.
24→11 Migrondi.Env uses Migrondi.Core.FileSystem✕
- Connections
- 1 pair of types, where a type in Migrondi.Env uses a type in Migrondi.Core.FileSystem.
- The types involved
Migrondi.Env.AppEnv→Migrondi.Core.FileSystem.IMiFileSystem
- Direction
- Migrondi.Env uses Migrondi.Core.FileSystem, so a change to Migrondi.Core.FileSystem can break Migrondi.Env, while a change to Migrondi.Env can't break Migrondi.Core.FileSystem.
- Position
- Below the diagonal: Migrondi.Env uses a module listed above it, which is the healthy direction.
24→15 Migrondi.Env uses Migrondi.Core✕
- Connections
- 2 pairs of types, where a type in Migrondi.Env uses a type in Migrondi.Core.
- The types involved
Migrondi.Env.AppEnv→Migrondi.Core.IMigrondiMigrondi.Env.AppEnv→Migrondi.Core.MigrondiConfig
- Direction
- Migrondi.Env uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Env, while a change to Migrondi.Env can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Env uses a module listed above it, which is the healthy direction.
24→16 Migrondi.Env uses Migrondi.Core.Database✕
- Connections
- 1 pair of types, where a type in Migrondi.Env uses a type in Migrondi.Core.Database.
- The types involved
Migrondi.Env.AppEnv→Migrondi.Core.Database.IMiDatabaseHandler
- Direction
- Migrondi.Env uses Migrondi.Core.Database, so a change to Migrondi.Core.Database can break Migrondi.Env, while a change to Migrondi.Env can't break Migrondi.Core.Database.
- Position
- Below the diagonal: Migrondi.Env uses a module listed above it, which is the healthy direction.
25→15 Migrondi.Mcp.McpResults uses Migrondi.Core✕
- Connections
- 9 pairs of types, where a type in Migrondi.Mcp.McpResults uses a type in Migrondi.Core.
- The types involved
Migrondi.Mcp.McpResults.AppliedMigration→Migrondi.Core.MigrationMigrondi.Mcp.McpResults.AppliedMigration→Migrondi.Core.MigrationRecordMigrondi.Mcp.McpResults.DryRunResult→Migrondi.Core.MigrationMigrondi.Mcp.McpResults.ListMigrationsResult→Migrondi.Core.MigrationStatusMigrondi.Mcp.McpResults.MigrationPreview→Migrondi.Core.MigrationMigrondi.Mcp.McpResults.MigrationStatusOutput→Migrondi.Core.MigrationStatusMigrondi.Mcp.McpResults.MigrationsResult→Migrondi.Core.MigrationMigrondi.Mcp.McpResults.MigrationsResult→Migrondi.Core.MigrationRecordMigrondi.Mcp.McpResults.ProjectConfigOutput→Migrondi.Core.MigrondiConfig
- Direction
- Migrondi.Mcp.McpResults uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Mcp.McpResults, while a change to Migrondi.Mcp.McpResults can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Mcp.McpResults uses a module listed above it, which is the healthy direction.
25→23 Migrondi.Mcp.McpResults uses MigrondiUI✕
- Connections
- 5 pairs of types, where a type in Migrondi.Mcp.McpResults uses a type in MigrondiUI.
- The types involved
Migrondi.Mcp.McpResults.LocalProjectDetail→MigrondiUI.LocalProjectMigrondi.Mcp.McpResults.LocalProjectSummary→MigrondiUI.LocalProjectMigrondi.Mcp.McpResults.MigrationDetail→MigrondiUI.VirtualMigrationMigrondi.Mcp.McpResults.VirtualProjectDetail→MigrondiUI.VirtualProjectMigrondi.Mcp.McpResults.VirtualProjectSummary→MigrondiUI.VirtualProject
- Direction
- Migrondi.Mcp.McpResults uses MigrondiUI, so a change to MigrondiUI can break Migrondi.Mcp.McpResults, while a change to Migrondi.Mcp.McpResults can't break MigrondiUI.
- Position
- Below the diagonal: Migrondi.Mcp.McpResults uses a module listed above it, which is the healthy direction.
26→15 MigrondiUI.Services uses Migrondi.Core✕
- Connections
- 2 pairs of types, where a type in MigrondiUI.Services uses a type in Migrondi.Core.
- The types involved
MigrondiUI.Services.IMigrationOperations→Migrondi.Core.IMigrondiMigrondiUI.Services.IMigrationOperations→Migrondi.Core.Migration
- Direction
- MigrondiUI.Services uses Migrondi.Core, so a change to Migrondi.Core can break MigrondiUI.Services, while a change to MigrondiUI.Services can't break Migrondi.Core.
- Position
- Below the diagonal: MigrondiUI.Services uses a module listed above it, which is the healthy direction.
26→23 MigrondiUI.Services uses MigrondiUI✕
- Connections
- 2 pairs of types, where a type in MigrondiUI.Services uses a type in MigrondiUI.
- The types involved
MigrondiUI.Services.IMigrationOperationsFactory→MigrondiUI.ProjectMigrondiUI.Services.IProjectCollection→MigrondiUI.VirtualProject
- Direction
- MigrondiUI.Services uses MigrondiUI, so a change to MigrondiUI can break MigrondiUI.Services, while a change to MigrondiUI.Services can't break MigrondiUI.
- Position
- Below the diagonal: MigrondiUI.Services uses a module listed above it, which is the healthy direction.
27→15 Migrondi.Commands.ArgumentMapper uses Migrondi.Core✕
- Connections
- 1 pair of types, where a type in Migrondi.Commands.ArgumentMapper uses a type in Migrondi.Core.
- The types involved
Migrondi.Commands.ArgumentMapper.ArgumentMapper→Migrondi.Core.MigrationType
- Direction
- Migrondi.Commands.ArgumentMapper uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Commands.ArgumentMapper, while a change to Migrondi.Commands.ArgumentMapper can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Commands.ArgumentMapper uses a module listed above it, which is the healthy direction.
27→24 Migrondi.Commands.ArgumentMapper uses Migrondi.Env✕
- Connections
- 1 pair of types, where a type in Migrondi.Commands.ArgumentMapper uses a type in Migrondi.Env.
- The types involved
Migrondi.Commands.ArgumentMapper.ArgumentMapper→Migrondi.Env.AppEnv
- Direction
- Migrondi.Commands.ArgumentMapper uses Migrondi.Env, so a change to Migrondi.Env can break Migrondi.Commands.ArgumentMapper, while a change to Migrondi.Commands.ArgumentMapper can't break Migrondi.Env.
- Position
- Below the diagonal: Migrondi.Commands.ArgumentMapper uses a module listed above it, which is the healthy direction.
28→24 Migrondi.Commands.Commands uses Migrondi.Env✕
- Connections
- 1 pair of types, where a type in Migrondi.Commands.Commands uses a type in Migrondi.Env.
- The types involved
Migrondi.Commands.Commands.Commands→Migrondi.Env.AppEnv
- Direction
- Migrondi.Commands.Commands uses Migrondi.Env, so a change to Migrondi.Env can break Migrondi.Commands.Commands, while a change to Migrondi.Commands.Commands can't break Migrondi.Env.
- Position
- Below the diagonal: Migrondi.Commands.Commands uses a module listed above it, which is the healthy direction.
29→15 Migrondi.Mcp uses Migrondi.Core✕
- Connections
- 1 pair of types, where a type in Migrondi.Mcp uses a type in Migrondi.Core.
- The types involved
Migrondi.Mcp.ProjectBinding→Migrondi.Core.MigrondiConfig
- Direction
- Migrondi.Mcp uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Mcp, while a change to Migrondi.Mcp can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Mcp uses a module listed above it, which is the healthy direction.
29→26 Migrondi.Mcp uses MigrondiUI.Services✕
- Connections
- 2 pairs of types, where a type in Migrondi.Mcp uses a type in MigrondiUI.Services.
- The types involved
Migrondi.Mcp.McpEnvironment→MigrondiUI.Services.IMigrationOperationsFactoryMigrondi.Mcp.McpEnvironment→MigrondiUI.Services.IProjectCollection
- Direction
- Migrondi.Mcp uses MigrondiUI.Services, so a change to MigrondiUI.Services can break Migrondi.Mcp, while a change to Migrondi.Mcp can't break MigrondiUI.Services.
- Position
- Below the diagonal: Migrondi.Mcp uses a module listed above it, which is the healthy direction.
30→29 Migrondi.Handlers.Mcp uses Migrondi.Mcp✕
- Connections
- 1 pair of types, where a type in Migrondi.Handlers.Mcp uses a type in Migrondi.Mcp.
- The types involved
Migrondi.Handlers.Mcp.McpArgs→Migrondi.Mcp.McpMode
- Direction
- Migrondi.Handlers.Mcp uses Migrondi.Mcp, so a change to Migrondi.Mcp can break Migrondi.Handlers.Mcp, while a change to Migrondi.Handlers.Mcp can't break Migrondi.Mcp.
- Position
- Below the diagonal: Migrondi.Handlers.Mcp uses a module listed above it, which is the healthy direction.
31→29 Migrondi.Mcp.HttpServer uses Migrondi.Mcp✕
- Connections
- 1 pair of types, where a type in Migrondi.Mcp.HttpServer uses a type in Migrondi.Mcp.
- The types involved
Migrondi.Mcp.HttpServer.HttpServer→Migrondi.Mcp.IMcpHttpServer
- Direction
- Migrondi.Mcp.HttpServer uses Migrondi.Mcp, so a change to Migrondi.Mcp can break Migrondi.Mcp.HttpServer, while a change to Migrondi.Mcp.HttpServer can't break Migrondi.Mcp.
- Position
- Below the diagonal: Migrondi.Mcp.HttpServer uses a module listed above it, which is the healthy direction.
32→15 Migrondi.Mcp.McpTools uses Migrondi.Core✕
- Connections
- 1 pair of types, where a type in Migrondi.Mcp.McpTools uses a type in Migrondi.Core.
- The types involved
Migrondi.Mcp.McpTools.McpTools→Migrondi.Core.MigrondiDriver
- Direction
- Migrondi.Mcp.McpTools uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Mcp.McpTools, while a change to Migrondi.Mcp.McpTools can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Mcp.McpTools uses a module listed above it, which is the healthy direction.
32→29 Migrondi.Mcp.McpTools uses Migrondi.Mcp✕
- Connections
- 1 pair of types, where a type in Migrondi.Mcp.McpTools uses a type in Migrondi.Mcp.
- The types involved
Migrondi.Mcp.McpTools.McpTools→Migrondi.Mcp.McpEnvironment
- Direction
- Migrondi.Mcp.McpTools uses Migrondi.Mcp, so a change to Migrondi.Mcp can break Migrondi.Mcp.McpTools, while a change to Migrondi.Mcp.McpTools can't break Migrondi.Mcp.
- Position
- Below the diagonal: Migrondi.Mcp.McpTools uses a module listed above it, which is the healthy direction.
33→29 Migrondi.Mcp.ProjectBindingModule uses Migrondi.Mcp✕
- Connections
- 3 pairs of types, where a type in Migrondi.Mcp.ProjectBindingModule uses a type in Migrondi.Mcp.
- The types involved
Migrondi.Mcp.ProjectBindingModule.ProjectBindingModule→Migrondi.Mcp.ProjectBindingMigrondi.Mcp.ProjectBindingModule.ProjectBindingModule→Migrondi.Mcp.ProjectResolveArgsMigrondi.Mcp.ProjectBindingModule.ProjectBindingModule→Migrondi.Mcp.ProjectResolveError
- Direction
- Migrondi.Mcp.ProjectBindingModule uses Migrondi.Mcp, so a change to Migrondi.Mcp can break Migrondi.Mcp.ProjectBindingModule, while a change to Migrondi.Mcp.ProjectBindingModule can't break Migrondi.Mcp.
- Position
- Below the diagonal: Migrondi.Mcp.ProjectBindingModule uses a module listed above it, which is the healthy direction.
34→15 Migrondi.Mcp.ProjectInit uses Migrondi.Core✕
- Connections
- 1 pair of types, where a type in Migrondi.Mcp.ProjectInit uses a type in Migrondi.Core.
- The types involved
Migrondi.Mcp.ProjectInit.ProjectInit→Migrondi.Core.MigrondiConfig
- Direction
- Migrondi.Mcp.ProjectInit uses Migrondi.Core, so a change to Migrondi.Core can break Migrondi.Mcp.ProjectInit, while a change to Migrondi.Mcp.ProjectInit can't break Migrondi.Core.
- Position
- Below the diagonal: Migrondi.Mcp.ProjectInit uses a module listed above it, which is the healthy direction.
34→29 Migrondi.Mcp.ProjectInit uses Migrondi.Mcp✕
- Connections
- 1 pair of types, where a type in Migrondi.Mcp.ProjectInit uses a type in Migrondi.Mcp.
- The types involved
Migrondi.Mcp.ProjectInit.ProjectInit→Migrondi.Mcp.ProjectOverrides
- Direction
- Migrondi.Mcp.ProjectInit uses Migrondi.Mcp, so a change to Migrondi.Mcp can break Migrondi.Mcp.ProjectInit, while a change to Migrondi.Mcp.ProjectInit can't break Migrondi.Mcp.
- Position
- Below the diagonal: Migrondi.Mcp.ProjectInit uses a module listed above it, which is the healthy direction.
35→29 Migrondi.Mcp.ServerBuilder uses Migrondi.Mcp✕
- Connections
- 4 pairs of types, where a type in Migrondi.Mcp.ServerBuilder uses a type in Migrondi.Mcp.
- The types involved
Migrondi.Mcp.ServerBuilder.ServerBuilder→Migrondi.Mcp.McpEnvironmentMigrondi.Mcp.ServerBuilder.ServerBuilder→Migrondi.Mcp.McpModeMigrondi.Mcp.ServerBuilder.ServerBuilder→Migrondi.Mcp.McpOptionsMigrondi.Mcp.ServerBuilder.ServerBuilder→Migrondi.Mcp.ToolSpec
- Direction
- Migrondi.Mcp.ServerBuilder uses Migrondi.Mcp, so a change to Migrondi.Mcp can break Migrondi.Mcp.ServerBuilder, while a change to Migrondi.Mcp.ServerBuilder can't break Migrondi.Mcp.
- Position
- Below the diagonal: Migrondi.Mcp.ServerBuilder uses a module listed above it, which is the healthy direction.
36→29 Migrondi.Mcp.ServerBuilder.ReadTools uses Migrondi.Mcp✕
- Connections
- 1 pair of types, where a type in Migrondi.Mcp.ServerBuilder.ReadTools uses a type in Migrondi.Mcp.
- The types involved
Migrondi.Mcp.ServerBuilder.ReadTools.ReadTools→Migrondi.Mcp.McpEnvironment
- Direction
- Migrondi.Mcp.ServerBuilder.ReadTools uses Migrondi.Mcp, so a change to Migrondi.Mcp can break Migrondi.Mcp.ServerBuilder.ReadTools, while a change to Migrondi.Mcp.ServerBuilder.ReadTools can't break Migrondi.Mcp.
- Position
- Below the diagonal: Migrondi.Mcp.ServerBuilder.ReadTools uses a module listed above it, which is the healthy direction.
37→29 Migrondi.Mcp.ServerBuilder.WriteTools uses Migrondi.Mcp✕
- Connections
- 1 pair of types, where a type in Migrondi.Mcp.ServerBuilder.WriteTools uses a type in Migrondi.Mcp.
- The types involved
Migrondi.Mcp.ServerBuilder.WriteTools.WriteTools→Migrondi.Mcp.McpEnvironment
- Direction
- Migrondi.Mcp.ServerBuilder.WriteTools uses Migrondi.Mcp, so a change to Migrondi.Mcp can break Migrondi.Mcp.ServerBuilder.WriteTools, while a change to Migrondi.Mcp.ServerBuilder.WriteTools can't break Migrondi.Mcp.
- Position
- Below the diagonal: Migrondi.Mcp.ServerBuilder.WriteTools uses a module listed above it, which is the healthy direction.
38→29 Migrondi.Mcp.SingleProjectServer uses Migrondi.Mcp✕
- Connections
- 2 pairs of types, where a type in Migrondi.Mcp.SingleProjectServer uses a type in Migrondi.Mcp.
- The types involved
Migrondi.Mcp.SingleProjectServer.ServeArgs→Migrondi.Mcp.McpModeMigrondi.Mcp.SingleProjectServer.SingleProjectServer→Migrondi.Mcp.ToolContext
- Direction
- Migrondi.Mcp.SingleProjectServer uses Migrondi.Mcp, so a change to Migrondi.Mcp can break Migrondi.Mcp.SingleProjectServer, while a change to Migrondi.Mcp.SingleProjectServer can't break Migrondi.Mcp.
- Position
- Below the diagonal: Migrondi.Mcp.SingleProjectServer uses a module listed above it, which is the healthy direction.
39→29 Migrondi.Mcp.SingleProjectTools uses Migrondi.Mcp✕
- Connections
- 5 pairs of types, where a type in Migrondi.Mcp.SingleProjectTools uses a type in Migrondi.Mcp.
- The types involved
Migrondi.Mcp.SingleProjectTools.SingleProjectTools→Migrondi.Mcp.CreateArgsMigrondi.Mcp.SingleProjectTools.SingleProjectTools→Migrondi.Mcp.InitProjectArgsMigrondi.Mcp.SingleProjectTools.SingleProjectTools→Migrondi.Mcp.ProjectCallMigrondi.Mcp.SingleProjectTools.SingleProjectTools→Migrondi.Mcp.ToolContextMigrondi.Mcp.SingleProjectTools.SingleProjectTools→Migrondi.Mcp.UpdateConfigArgs
- Direction
- Migrondi.Mcp.SingleProjectTools uses Migrondi.Mcp, so a change to Migrondi.Mcp can break Migrondi.Mcp.SingleProjectTools, while a change to Migrondi.Mcp.SingleProjectTools can't break Migrondi.Mcp.
- Position
- Below the diagonal: Migrondi.Mcp.SingleProjectTools uses a module listed above it, which is the healthy direction.
40→29 Migrondi.Handlers.Mcp.Transport uses Migrondi.Mcp✕
- Connections
- 1 pair of types, where a type in Migrondi.Handlers.Mcp.Transport uses a type in Migrondi.Mcp.
- The types involved
Migrondi.Handlers.Mcp.Transport.Transport→Migrondi.Mcp.McpMode
- Direction
- Migrondi.Handlers.Mcp.Transport uses Migrondi.Mcp, so a change to Migrondi.Mcp can break Migrondi.Handlers.Mcp.Transport, while a change to Migrondi.Handlers.Mcp.Transport can't break Migrondi.Mcp.
- Position
- Below the diagonal: Migrondi.Handlers.Mcp.Transport uses a module listed above it, which is the healthy direction.
40→30 Migrondi.Handlers.Mcp.Transport uses Migrondi.Handlers.Mcp✕
- Connections
- 1 pair of types, where a type in Migrondi.Handlers.Mcp.Transport uses a type in Migrondi.Handlers.Mcp.
- The types involved
Migrondi.Handlers.Mcp.Transport.Transport→Migrondi.Handlers.Mcp.McpTransportError
- Direction
- Migrondi.Handlers.Mcp.Transport uses Migrondi.Handlers.Mcp, so a change to Migrondi.Handlers.Mcp can break Migrondi.Handlers.Mcp.Transport, while a change to Migrondi.Handlers.Mcp.Transport can't break Migrondi.Handlers.Mcp.
- Position
- Below the diagonal: Migrondi.Handlers.Mcp.Transport uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 13 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | Medium |
Roadmap
Top priorities: Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Migrondi.fsproj; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Migrondi.fsproj. | +3.2 pts | Low | ADR Quality |
| Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`. | +3.5 pts | Medium | Nullable reference types |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.4 pts | Medium | Architecture documentation |
| Resolve the 6 FileTooLong finding(s) in God Classes — start with ProjectDetails.fs, Server.fs, Handlers.fs. | +1.4 pts | High | God Classes |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.1 pts | Medium | Documentation (README) |
| Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with ProjectDetails.highlightText (cognitive 29), Migrations.listMigrations (cognitive 25), ProjectDetails.migrationPane (cognitive 16). | +0.9 pts | High | Cognitive Complexity |
| Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with VirtualFs.getVirtualFs (cyclomatic 25), Migrations.listMigrations (cyclomatic 18), ProjectDetails.create (cyclomatic 18). | +0.8 pts | High | Cyclomatic Complexity |
| Resolve the 18 Low coverage finding(s) in Code Coverage — start with Server.fs (2), Program.fs, Shell.fs. | +0.4 pts | Medium | Code Coverage |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Migrondi.UI/Logic/Services.fs | 5.5 | Mixed | Code Duplication: Duplicated block (10 lines × 2) |
| src/Migrondi/Handlers.fs | 5.6 | Mixed | Cyclomatic Complexity: Migrations.listMigrations (cyclomatic 18) |
| src/Migrondi.UI/Views/ProjectDetails.fs | 5.7 | Mixed | Cyclomatic Complexity: ProjectDetails.create (cyclomatic 18) |
| src/Migrondi.Mcp/Server.fs | 6.3 | Mixed | God Classes: FileTooLong: Migrondi.Mcp/Server.fs |
| src/Migrondi.UI/Views/Common.fs | 7.0 | Mixed | Code Duplication: Duplicated block (15 lines × 2) |
| src/Migrondi.UI/Views/NewProject.fs | 7.0 | Mixed | Code Duplication: Duplicated block (13 lines × 2) |
| src/Migrondi.UI/Views/Shell.fs | 7.0 | Mixed | Code Duplication: Duplicated block (8 lines × 2) |
| src/Migrondi.Core/Database.fs | 7.0 | Mixed | God Classes: FileTooLong: Migrondi.Core/Database.fs |
| src/Migrondi.Core/Migrondi.fs | 7.1 | Mixed | God Classes: FileTooLong: Migrondi.Core/Migrondi.fs |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Migrondi.Core/Serialization.fs | 7.4 | Mixed | Code Duplication: Duplicated block (16–17 lines × 2) |
| src/Migrondi.UI/Logic/VirtualFs.fs | 7.8 | Mixed | Cyclomatic Complexity: VirtualFs.getVirtualFs (cyclomatic 25) |
| src/Migrondi.UI/Logic/Database.fs | 7.8 | Mixed | Code Duplication: Duplicated block (20 lines × 2) |
| src/Migrondi.Mcp/SingleProject.fs | 8.5 | Near-clean | God Classes: FileTooLong: Migrondi.Mcp/SingleProject.fs |
| .agents/skills/fsharp-signature-files/scripts/breaks/HiddenRecordConstruction/Lib.fs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (5 corresponding lines) |
| src/Migrondi.Mcp/Tools.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (12–14 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 40 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 90 of 115 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/Migrondi.UI/Logic/VirtualFs.fs, src/Migrondi/Handlers.fs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 326 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 2 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/Migrondi.Core/Migrondi.Core.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (10,832 lines, 100% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — 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.
- D26 Project Cohesion — 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. `DomainJson` (18 LoC, 296 public types across 92 namespaces) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was VirtualFs.getVirtualFs at 25.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with VirtualFs.getVirtualFs (cyclomatic 25), Migrations.listMigrations (cyclomatic 18), ProjectDetails.create (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was ProjectDetails.highlightText at 29.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with ProjectDetails.highlightText (cognitive 29), Migrations.listMigrations (cognitive 25), ProjectDetails.migrationPane (cognitive 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
6 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 6 FileTooLong finding(s) in God Classes — start with ProjectDetails.fs, Server.fs, Handlers.fs. — One of this dimension's main actionable groups (6 warning-level).
D4 · Code Duplication
26 duplicated block group(s) detected. 6.3 % of the production lines (679 of 10,832) are in a reported copy. One further row reports members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with Migrondi.fs, Server.fs, Common.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with Database.fs, ProjectBinding.fs, NewProject.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (27 lines × 2) finding(s) in Code Duplication — start with Migrondi.fs (2). — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
1 of 5 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with Services.fs. — One of this dimension's main actionable groups (1 warning-level).
D8 · Code Coverage
Line coverage 47.3% — 18 file(s) below 50%.
What to do
- Resolve the 18 Low coverage finding(s) in Code Coverage — start with Server.fs (2), Program.fs, Shell.fs. — One of this dimension's main actionable groups (18 warning-level).
- Resolve the 6 No test project references Break finding(s) in Code Coverage — start with Break.fsproj (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 No test project references Domain finding(s) in Code Coverage — start with Domain.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
14 outdated, 0 vulnerable, 0 deprecated packages.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 88 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 31 direct `PackageReference`(s), and 87 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
Top hotspots: src/Migrondi/Handlers.fs (5×18=90); src/Migrondi.UI/Logic/VirtualFs.fs (2×25=50)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with Handlers.fs, VirtualFs.fs. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
0 deducted debt markers + unmeasured dead symbols across 18 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (100% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 8 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Migrondi.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
98 % of calls cross a namespace and 9 % go through an interface, but 39 % 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)
13 finding(s): 0 critical, 12 high, 1 medium, 0 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 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 9 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 (9 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 30 of the 40 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 29 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 3 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:11
- `src/Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/Directory.Packages.props:7
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
P8 · Schema migrations
PF3 · Async & latency hygiene
X5 · Nullable reference types
- 0/1 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 60% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 95% | Exemplary | Solid. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 64% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 64% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~6113 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (2160 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed F# surface was not measured.
- D23 Boundary Type-Coupling — small single-context codebase (10,832 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one project reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 46 value object(s); 16 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 — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
- M4 Documentation accuracy — Not applicable: the 8 current-state document(s) make no claim of a kind M4 checks. 10 claim(s) of kinds M4 does not check were not checked (environment variable 10); 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'.
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P9 Domain vs controller coverage — coverage data present for 37 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no async method does work a token could cancel
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — X23 reached only 0% of this repository's production lines — fsharp (10,832 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 12 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 77 finding(s)
- Low coverage: src/Migrondi.UI/Program.fs src/Migrondi.UI/Program.fs:1
- Low coverage: src/Migrondi.UI/Views/Shell.fs src/Migrondi.UI/Views/Shell.fs:1
- Low coverage: src/Migrondi.UI/Views/NewProject.fs src/Migrondi.UI/Views/NewProject.fs:1
- Low coverage: src/Migrondi.UI/Views/ProjectDetails.fs src/Migrondi.UI/Views/ProjectDetails.fs:1
- Low coverage: src/Migrondi.UI/Views/Landing.fs src/Migrondi.UI/Views/Landing.fs:1
- Low coverage: src/Migrondi.UI/Views/ProjectSettings.fs src/Migrondi.UI/Views/ProjectSettings.fs:1
- Low coverage: src/Migrondi.UI/Views/Common.fs src/Migrondi.UI/Views/Common.fs:1
- Low coverage: src/Migrondi.UI/Feedback.fs src/Migrondi.UI/Feedback.fs:1
- Low coverage: src/Migrondi.UI/Host.fs src/Migrondi.UI/Host.fs:1
- Low coverage: src/Migrondi.UI/Types.fs src/Migrondi.UI/Types.fs:1
- Low coverage: src/Migrondi.UI/Mcp/Server.fs src/Migrondi.UI/Mcp/Server.fs:1
- Low coverage: src/Migrondi.UI/Logic/Migrations.fs src/Migrondi.UI/Logic/Migrations.fs:1
- Low coverage: src/Migrondi.UI/Logic/OsOperations.fs src/Migrondi.UI/Logic/OsOperations.fs:1
- Low coverage: src/Migrondi.UI/Logic/Services.fs src/Migrondi.UI/Logic/Services.fs:1
- Low coverage: src/Migrondi.Mcp/Server.fs src/Migrondi.Mcp/Server.fs:1
- Low coverage: src/Migrondi.Mcp/Results.fs src/Migrondi.Mcp/Results.fs:1
- Low coverage: src/Migrondi/Commands.fs src/Migrondi/Commands.fs:1
- Low coverage: src/Migrondi/Handlers.fs src/Migrondi/Handlers.fs:1
- FileTooLong: Views/ProjectDetails.fs src/Migrondi.UI/Views/ProjectDetails.fs
- FileTooLong: Migrondi.Mcp/Server.fs src/Migrondi.Mcp/Server.fs
- FileTooLong: Migrondi/Handlers.fs src/Migrondi/Handlers.fs
- FileTooLong: Migrondi.Core/Database.fs src/Migrondi.Core/Database.fs
- FileTooLong: Migrondi.Core/Migrondi.fs src/Migrondi.Core/Migrondi.fs
- FileTooLong: Migrondi.Mcp/SingleProject.fs src/Migrondi.Mcp/SingleProject.fs
- No test project references Break .agents/skills/fsharp-signature-files/scripts/breaks/HiddenHelper/Break.fsproj
- No test project references Break .agents/skills/fsharp-signature-files/scripts/breaks/HiddenRecordConstruction/Break.fsproj
- No test project references Break .agents/skills/fsharp-signature-files/scripts/breaks/HiddenUnionCase/Break.fsproj
- No test project references Break .agents/skills/fsharp-signature-files/scripts/breaks/InterfaceNotListed/Break.fsproj
- No test project references Break .agents/skills/fsharp-signature-files/scripts/breaks/MissingQualifiedAccess/Break.fsproj
- No test project references Break .agents/skills/fsharp-signature-files/scripts/breaks/PrivateRepresentation/Break.fsproj
- Duplicated block (15 lines × 2) src/Migrondi.Core/Migrondi.fs:253
- Duplicated block (15 lines × 2) src/Migrondi.Mcp/Server.fs:216
- Duplicated block (15 lines × 2) src/Migrondi.UI/Views/Common.fs:31
- Duplicated block (13 lines × 2) src/Migrondi.Core/Database.fs:915
- Duplicated block (13 lines × 2) src/Migrondi.Mcp/ProjectBinding.fs:96
- Duplicated block (13 lines × 2) src/Migrondi.UI/Views/NewProject.fs:202
- Hotspot: src/Migrondi/Handlers.fs src/Migrondi/Handlers.fs:608
- Hotspot: src/Migrondi.UI/Logic/VirtualFs.fs src/Migrondi.UI/Logic/VirtualFs.fs:55
- Duplicated block (27 lines × 2) src/Migrondi.Core/Migrondi.fs:170
- Duplicated block (27 lines × 2) src/Migrondi.Core/Migrondi.fs:211
- Duplicated block (12–13 lines × 2) src/Migrondi.Core/Database.fs:308
- Duplicated block (12–13 lines × 2) src/Migrondi.Core/Migrondi.fs:127
- Duplicated block (10 lines × 2) src/Migrondi.UI/Logic/Services.fs:308
- Duplicated block (10 lines × 2) src/Migrondi.Core/Serialization.fs:245
- VirtualFs.getVirtualFs (cyclomatic 25) src/Migrondi.UI/Logic/VirtualFs.fs:55
- Migrations.listMigrations (cyclomatic 18) src/Migrondi/Handlers.fs:608
- ProjectDetails.create (cyclomatic 18) src/Migrondi.UI/Views/ProjectDetails.fs:963
- ProjectDetails.highlightText (cognitive 29) src/Migrondi.UI/Views/ProjectDetails.fs:404
- Migrations.listMigrations (cognitive 25) src/Migrondi/Handlers.fs:608
- ProjectDetails.migrationPane (cognitive 16) src/Migrondi.UI/Views/ProjectDetails.fs:785
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (5 corresponding lines) .agents/skills/fsharp-signature-files/scripts/breaks/HiddenRecordConstruction/Lib.fs:1
- Duplicated block (31 lines × 2) src/Migrondi.Core/Database.fs:416
- Duplicated block (21 lines × 2) src/Migrondi.UI/Logic/VirtualFs.fs:104
- Duplicated block (20 lines × 2) src/Migrondi.UI/Logic/Database.fs:189
- Duplicated block (18 lines × 2) src/Migrondi.UI/Logic/Database.fs:314
- Duplicated block (17 lines × 2) src/Migrondi.Core/Migrondi.fs:421
- Duplicated block (16–17 lines × 2) src/Migrondi.Core/Serialization.fs:198
- Duplicated block (14 lines × 4) src/Migrondi.Core/Database.fs:422
- Duplicated block (12–14 lines × 2) src/Migrondi.Mcp/Tools.fs:66
- Duplicated block (12 lines × 2) src/Migrondi.Core/Serialization.fs:181
- Duplicated block (11 lines × 2) src/Migrondi.Core/Database.fs:315
- Duplicated block (7–8 lines × 4) src/Migrondi.Core/Database.fs:314
- Duplicated block (6 lines × 2) src/Migrondi/Handlers.fs:576
- Duplicated block (16 lines × 2) src/Migrondi/Handlers.fs:319
- Duplicated block (8 lines × 2) src/Migrondi.UI/Views/Shell.fs:104
- Low cohesion: ProjectCollection (LCOM4 5) src/Migrondi.UI/Logic/Services.fs:21
- No test project references Domain .agents/skills/fsharp-native-aot/scripts/Domain/Domain.fsproj
- No test project references Shape .agents/skills/fsharp-module-shape/scripts/Shape/Shape.fsproj
- No test project references StateMachine .agents/skills/fsharp-async-composition/scripts/StateMachine/StateMachine.fsproj
- No test project references DomainJson .agents/skills/fsharp-native-aot/scripts/DomainJson/DomainJson.csproj
- No test project references Generate .agents/skills/fsharp-signature-files/scripts/Generate/Generate.fsproj
- No test project references Probe .agents/skills/fsharp-native-aot/scripts/Probe/Probe.fsproj
- No test project references WarnGate .agents/skills/fsharp-native-aot/scripts/WarnGate/WarnGate.fsproj
Minor — 12 finding(s)
- No ADRs found src/Migrondi/Migrondi.fsproj:3
- Scattered collaborators
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:11
- No dependency-update automation src/Directory.Packages.props:7
- Nullable reference types not enabled everywhere
Minor — 14 finding(s)
- Outdated: Microsoft.Data.SqlClient
- Outdated: Microsoft.Data.Sqlite
- Outdated: Microsoft.Extensions.Logging
- Outdated: Microsoft.Extensions.Logging.Console
- Outdated: Microsoft.SourceLink.GitHub
- Outdated: System.Security.Cryptography.Pkcs
- Outdated: Microsoft.Testing.Extensions.TrxReport
- Outdated: MSTest
- Outdated: MSTest.TestAdapter
- Outdated: MSTest.TestFramework
- Outdated: xunit.runner.visualstudio
- Outdated: xunit.v3.mtp-v2
- Outdated: Goo
- Outdated: Goo.Widgets
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-ac7a067e47b2453c9322962636bcfc78/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-ac7a067e47b2453c9322962636bcfc78/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 . | 13 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Migrondi.slnx package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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-b8aed2dd319243e9a9d63ffac1419885 | 0 | artifacts/raw/osv-scanner.json |