Executive summary
finos/morphir-dotnet falls short of our standard for production, held back most by its Performance lens, the way the code guards its speed and its use of resources. It scores 62 out of 100 and is rated Adequate, and 134 of its 150 critical findings are security problems in the build pipeline and in its code.
Performance, at 60, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is removing the blocking calls, worth about 2 points. Separating the feature slices comes next, worth about 1 point.
111 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Ten pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline, and six pipeline steps run downloads nobody checks. Pinning each tool to an exact version, passing outside input through environment variables and checking each download against a checksum would close these risks. Fixing the weaknesses the scanner points to would fix the six security weaknesses in the code, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed. The six errors that are caught and ignored need handling or logging instead of being ignored.
The product code is 126,587 lines, about €490,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 235 findings
- Code Duplication · Edited copy of a member (56 corresponding lines) src/Morphir.Tooling/Scenarios/ManagementScenario.cs
- Code Duplication · Edited copies of one member (3 members, 54+ corresponding lines) src/Morphir.Tooling/Features/Management/DistHandlers.cs
- Code Duplication · Edited copy of a member (24 corresponding lines) spikes/extension-model/jsonrpc/CurlyRpcProbe/Program.cs
- Code Duplication · Edited copies of one member (4 members, 43+ corresponding lines) src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs
- Code Duplication · Edited copy of a member (44 corresponding lines) src/Morphir.Tooling/Features/Management/DistHandlers.cs
- Code Duplication · Edited copies of one member (3 members, 41+ corresponding lines) src/Morphir.Tooling/Features/Management/DistHandlers.cs
- Code Duplication · Edited copy of a member (20 corresponding lines) src/Morphir.Tooling/Features/Generate/MepGenerationBackend.cs
- Code Duplication · Edited copies of one member (3 members, 34+ corresponding lines) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs
- Code Duplication · Edited copy of a member (23 corresponding lines) src/Morphir.Tooling/Configuration/OsPaths.cs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/Morphir.Configuration.IO/Json5Reader.cs
- Code Duplication · Edited copy of a member (38 corresponding lines) src/Morphir.Tooling/Infrastructure/JsonSchema/SchemaValidator.cs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/Morphir.Configuration.IO/ProjectMigrationService.cs
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) src/Morphir.Tooling/Features/Management/DistCommands.cs
- Code Duplication · Edited copy of a member (15 corresponding lines) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs
- Code Duplication · Edited copy of a member (16 corresponding lines) src/Morphir.Extensions.Wasm/GuestOutput.cs
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) src/Morphir.Tooling/MorphirCliExtensions.cs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/Morphir.Configuration.IO/ConfigurationEditService.cs
- Code Duplication · Edited copy of a member (9 corresponding lines) src/Morphir.Configuration.IO/ProjectMigrationService.cs
- Code Duplication · Edited copy of a member (12 corresponding lines) src/Morphir.Extensions.Wasm/WasiSandbox.cs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/Morphir.Extensions.Wasm/WasiSandbox.cs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs
- Code Duplication · Edited copy of a member (6 corresponding lines) src/Morphir.Extensions.Wasm/ExtismHostFunctions.cs
- Code Duplication · Edited copy of a member (12 corresponding lines) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs
- Code Duplication · Edited copy of a member (2 corresponding lines) src/Morphir.Tooling/Features/Generate/CSharpGenerationBackend.cs
- Code Duplication · Edited copy of a member (2 corresponding lines) src/Morphir.Configuration.IO/ProjectMigrationService.cs
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) src/Morphir.Tooling/Features/Configuration/ConfigurationEditingCommand.cs
- Code Duplication · Edited copies of one member (3 members, 2+ corresponding lines) src/Morphir.Configuration.IO/ProjectLoading.cs
- Code Duplication · Edited copy of a member (4 corresponding lines) build/Helpers/ReleaseProfiles.cs
- Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) src/Morphir.Extensions.Wasm/GuestFailure.cs
- Code Duplication · Duplicated block (11 lines × 3) src/Morphir.Tooling/Features/Configuration/ConfigurationEditingHost.cs
- Code Duplication · Duplicated block (7 lines × 2) src/Morphir.Extensions.Wasm/WasiSandbox.cs
- Code Duplication · Duplicated block (9 lines × 5) src/Morphir.Tooling/Scenarios/ManagementScenario.cs
- Code Duplication · Duplicated block (8–9 lines × 3) src/Morphir.Configuration.IO/ConfigurationEditService.cs
- Code Duplication · Duplicated block (9 lines × 2) src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs
- Code Duplication · Duplicated block (7 lines × 2) src/Morphir.Configuration.IO/ConfigurationTransaction.cs
- Code Duplication · Duplicated block (8 lines × 2) src/Morphir.Tooling/Scenarios/ManagementScenario.cs
- Code Duplication · Duplicated block (6 lines × 2) build/Helpers/PackagedContents.cs
- Code Duplication · Duplicated block (7 lines × 2) src/Morphir.Tooling/Features/Generate/MepGenerationBackend.cs
- Code Duplication · Duplicated block (6 lines × 2) src/Morphir.Myriad.Build/GenerateMorphirModules.cs
- Code Duplication · Duplicated block (5 lines × 2) src/Morphir.Tooling/Scenarios/ManagementScenario.cs
- Code Duplication · Duplicated block (14 lines × 2) src/Morphir.Managed/Program.cs
- Code Duplication · Duplicated block (5 lines × 2) spikes/extension-model/jsonrpc/CurlyRpcProbe/Program.cs
- Code Duplication · Duplicated block (5 lines × 2) src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs
- Code Duplication · Duplicated block (5 lines × 2) src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs
- Coupling · Unstable project Morphir.Myriad.Build src/Morphir.Myriad.Build/Morphir.Myriad.Build.csproj
- Coupling · Unstable project Morphir.Myriad.SystemTextJson.Build src/Morphir.Myriad.SystemTextJson.Build/Morphir.Myriad.SystemTextJson.Build.csproj
- Coupling · Off the main sequence: Morphir.Myriad.Hosting src/Morphir.Myriad.Hosting/Morphir.Myriad.Hosting.csproj
- Coupling · Off the main sequence: Morphir.Configuration.IO(net11.0) src/Morphir.Configuration.IO/Morphir.Configuration.IO.csproj
- Cohesion (LCOM4) · Low cohesion: Build (LCOM4 8) build/Build.cs
- Code Coverage · No test project references FSharpSyntaxLowering spikes/FSharpSyntaxLowering/FSharpSyntaxLowering.fsproj
- Code Coverage · No test project references TufProbe spikes/tuf-client/TufProbe/TufProbe.csproj
- Code Coverage · No test project references BaselineProbe spikes/extension-model/jsonrpc/BaselineProbe/BaselineProbe.csproj
- Code Coverage · No test project references BaselineProbe spikes/extension-model/wasm-runtime/BaselineProbe/BaselineProbe.csproj
- Code Coverage · No test project references CurlyRpcProbe spikes/extension-model/jsonrpc/CurlyRpcProbe/CurlyRpcProbe.csproj
- Code Coverage · No test project references ExtismProbe spikes/extension-model/wasm-runtime/ExtismProbe/ExtismProbe.csproj
- Code Coverage · No test project references FSharpMatchJoin spikes/FSharpMatchJoin/FSharpMatchJoin.fsproj
- Code Coverage · No test project references MorphirGuestProbe spikes/extension-model/dotnet-guest-toolchains/csharp-naot-llvm/MorphirGuestProbe.csproj
- Code Coverage · No test project references MorphirGuestProbeFs spikes/extension-model/dotnet-guest-toolchains/fsharp-naot-llvm/MorphirGuestProbeFs.fsproj
- Code Coverage · No test project references NuGetProbe spikes/nuget-extension-source/NuGetProbe/NuGetProbe.fsproj
- Code Coverage · No test project references PlatformProbe spikes/extension-model/tool-platform-packages/PlatformProbe/PlatformProbe.csproj
- Code Coverage · No test project references RoslynAotProbe spikes/extension-model/roslyn-aot/RoslynAotProbe.csproj
- Code Coverage · No test project references StreamJsonRpcProbe spikes/extension-model/jsonrpc/StreamJsonRpcProbe/StreamJsonRpcProbe.csproj
- Code Coverage · No test project references TrapRepro spikes/wasm-win-x64-trap/TrapRepro.csproj
- Code Coverage · No test project references WacsProbe spikes/extension-model/wasm-runtime/WacsProbe/WacsProbe.csproj
- Code Coverage · No test project references WasmtimeProbe spikes/extension-model/wasm-runtime/WasmtimeProbe/WasmtimeProbe.csproj
- Test Quality · Fixed-sleep synchronisation: SeparateNativeProcessesUseTheSameCoordinator tests/Morphir.Configuration.IO.Tests/ConfigurationTransactionTests.cs
- Test Quality · Fixed-sleep synchronisation: Timeout_KillsAGrandchildThatOutlivedItsParent tests/Morphir.TestSupport.Tests/ChildProcessTests.cs
- Test Quality · Fixed-sleep synchronisation: TimeoutStartsAfterTheGateIsHeld tests/Morphir.TestSupport.Tests/ChildProcessTests.cs
- Test Quality · Fixed-sleep synchronisation: DeadlineStopsADescendantThatOutlivedItsParent tests/Morphir.Tooling.Tests/Infrastructure/BoundedProcessTests.cs
- Explicit Debt · EmptyCatchBlock src/Morphir.Configuration.IO/ConfigurationTransaction.cs
- Explicit Debt · EmptyCatchBlock src/Morphir.Configuration.IO/ConfigurationTransaction.cs
- Explicit Debt · EmptyCatchBlock src/Morphir.Configuration.IO/ConfigurationTransaction.cs
- Explicit Debt · EmptyCatchBlock src/Morphir.Tooling/Features/Generate/GenerationPublisher.cs
- Explicit Debt · EmptyCatchBlock src/Morphir.Tooling/Features/Generate/GenerationPublisher.cs
- Explicit Debt · EmptyCatchBlock src/Morphir.Tooling/Features/TaskRecords/TaskInstaller.cs
- Explicit Debt · NoWarnInCsproj spikes/wasm-win-x64-trap/TrapRepro.csproj
- Explicit Debt · NoWarnInCsproj spikes/wasm-win-x64-trap/TrapRepro.csproj
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
Fixed since the last survey: 81 findings
- Cyclomatic Complexity · TypeCodec.decodeWithOptions (cyclomatic 38) src/Morphir.Models/Json/Codecs/TypeCodec.fs
- Cyclomatic Complexity · TypeValidator.inferValueType (cyclomatic 30) src/Morphir.IR.Pipeline.Plugins/TypeValidator.fs
- Cyclomatic Complexity · LiteralCodec.readFromWithOptions (cyclomatic 30) src/Morphir.Models/Json/Codecs/LiteralCodec.fs
- Cyclomatic Complexity · Value.toString (cyclomatic 24) src/Morphir.Models/IR/Classic/Value.fs
- Cognitive Complexity · LiteralCodec.readFromWithOptions (cognitive 95) src/Morphir.Models/Json/Codecs/LiteralCodec.fs
- Cognitive Complexity · TypeCodec.decodeWithOptions (cognitive 63) src/Morphir.Models/Json/Codecs/TypeCodec.fs
- Cognitive Complexity · NameModule.toMorphirWords (cognitive 59) src/Morphir.Models/IR/Name.fs
- Cognitive Complexity · SemanticVersionModule.parse (cognitive 45) src/Morphir.Models/IR/Versioning.fs
- Cognitive Complexity · FQNameCodec.readFromWithOptions (cognitive 42) src/Morphir.Models/Json/Codecs/FQNameCodec.fs
- Cognitive Complexity · TypeValidator.inferValueType (cognitive 32) src/Morphir.IR.Pipeline.Plugins/TypeValidator.fs
- Cognitive Complexity · IrToolingScenario.FormatVerifyOutput (cognitive 24) src/Morphir.Tooling/Scenarios/IrToolingScenario.cs
- Cognitive Complexity · DistHandlers.HandleList (cognitive 23) src/Morphir.Tooling/Features/Management/DistHandlers.cs
- Cognitive Complexity · SemanticVersionModule.isValidIdentifier (cognitive 20) src/Morphir.Models/IR/Versioning.fs
- Cognitive Complexity · ClassicTypeJsonConverter.ReadReference (cognitive 17) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs
- Cognitive Complexity · ClassicTypeJsonConverter.ReadExtensibleRecord (cognitive 17) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs
- Cognitive Complexity · NameCodec.readFromWithOptions (cognitive 17) src/Morphir.Models/Json/Codecs/NameCodec.fs
- Cognitive Complexity · ConfigResolver.ResolveConfigAsync (cognitive 16) src/Morphir.Tooling/Configuration/ConfigResolver.cs
- Cognitive Complexity · TomlParser.ParseCachePaths (cognitive 16) src/Morphir.Tooling/Configuration/TomlParser.cs
- Cognitive Complexity · SchemaValidator.ExtractExpectedValue (cognitive 16) src/Morphir.Tooling/Infrastructure/JsonSchema/SchemaValidator.cs
- Cognitive Complexity · PathCodec.readFromWithOptions (cognitive 16) src/Morphir.Models/Json/Codecs/PathCodec.fs
- God Classes · TooManyFunctions: List src/Morphir.SDK/List.fs
- God Classes · TooManyFunctions: String src/Morphir.SDK/String.fs
- God Classes · TooManyMethods: PatternBuilder src/Morphir.Models/IR/Classic/DSL/Patterns.fs
- God Classes · TooManyMethods: ValueBuilder src/Morphir.Models/IR/Classic/DSL/Values.fs
- God Classes · TooManyMethods: PatternBuilder`1 src/Morphir.Models/IR/Classic/DSL/Patterns.fs
- God Classes · TooManyMethods: PatternBuilderWithAttrs`1 src/Morphir.Models/IR/Classic/DSL/Patterns.fs
- God Classes · TooManyMethods: TypeBuilder src/Morphir.Models/IR/Classic/DSL/Types.fs
- God Classes · TooManyMethods: ValueBuilder`2 src/Morphir.Models/IR/Classic/DSL/Values.fs
- God Classes · TooManyMethods: ValueBuilderWithAttrs`2 src/Morphir.Models/IR/Classic/DSL/Values.fs
- Code Duplication · Near-duplicate member pair (28 shared lines) src/Morphir.Tooling/Scenarios/ManagementScenario.cs
- Code Duplication · Duplicated block (209 lines × 2) src/Morphir.Models/IR/Classic/DSL/Values.fs
- Code Duplication · Duplicated block (126 lines × 2) src/Morphir.Models/IR/Classic/DSL/Patterns.fs
- Code Duplication · Duplicated block (11–113 lines × 3) src/Morphir.Models/IR/Classic/DSL/Types.fs
- Code Duplication · Duplicated block (44 lines × 2) src/Morphir.Models/IR/Classic/DSL/Patterns.fs
- Code Duplication · Duplicated block (36 lines × 3) src/Morphir.Models/IR/Classic/DSL/Patterns.fs
- Code Duplication · Duplicated block (24 lines × 3) src/Morphir.Models/IR/Classic/DSL/Types.fs
- Code Duplication · Duplicated block (21–23 lines × 2) src/Morphir.Tooling/MorphirCliExtensions.cs
- Code Duplication · Duplicated block (23 lines × 2) src/Morphir.Models/IR/Classic/DSL/Patterns.fs
- Code Duplication · Duplicated block (21 lines × 3) src/Morphir.Models/IR/Classic/DSL/Patterns.fs
- Code Duplication · Duplicated block (17 lines × 2) src/Morphir.Models/IR/Classic/Type.fs
- Code Duplication · Duplicated block (15 lines × 2) src/Morphir.Models/Json/Encode.fs
- Code Duplication · Duplicated block (10 lines × 2) src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs
- Code Duplication · Duplicated block (13 lines × 3) src/Morphir.Models/IR/FQName.fs
- Code Duplication · Duplicated block (12–13 lines × 2) build/Helpers/PathHelper.cs
- Code Duplication · Duplicated block (13 lines × 2) src/Morphir.Tooling/Configuration/TomlParser.cs
- Code Duplication · Duplicated block (9 lines × 2) src/Morphir.Tooling/Scenarios/ManagementScenario.cs
- Code Duplication · Duplicated block (10 lines × 2) src/Morphir.Models/IR/Classic/DSL/Modules.fs
- Code Duplication · Duplicated block (10 lines × 2) src/Morphir.Models/IR/Classic/DSL/Modules.fs
- Code Duplication · Duplicated block (9 lines × 5) src/Morphir.Tooling/Scenarios/ManagementScenario.cs
- Code Duplication · Duplicated block (9 lines × 2) src/Morphir.Models/IR/Classic/DSL/Modules.fs
- Code Duplication · Duplicated block (8 lines × 2) src/Morphir.Tooling/Scenarios/ManagementScenario.cs
- Code Duplication · Duplicated block (7–8 lines × 2) src/Morphir.Models/IR/Classic/Value.fs
- Code Duplication · Duplicated block (6–7 lines × 3) src/Morphir.Models/IR/Classic/Value.fs
- Code Duplication · Duplicated block (7 lines × 2) src/Morphir.Models/Json/Codecs/TypeCodec.fs
- Code Duplication · Duplicated block (6 lines × 2) src/Morphir.IR.Pipeline.Plugins/Optimizer.fs
- Code Duplication · Duplicated block (6 lines × 2) src/Morphir.Models/IR/Classic/DSL/Patterns.fs
- Code Duplication · Duplicated block (13 lines × 3) src/Morphir.Models/Json/Codecs/FQNameCodec.fs
- Code Duplication · Duplicated block (5 lines × 2) src/Morphir.IR.Pipeline.Plugins/PrettyPrinter.fs
- Code Duplication · Duplicated block (5 lines × 2) src/Morphir.IR.Pipeline.Plugins/PrettyPrinter.fs
- Code Duplication · Duplicated block (8 lines × 2) src/Morphir.IR.Pipeline/PipelineBuilder.fs
- Code Coverage · No test project references Morphir.Tool src/Morphir.Tool/Morphir.Tool.csproj
- Static Analysis (SAST) · High: dependabot-missing-cooldown .github/dependabot.yml
- Static Analysis (SAST) · High: watchdog-untrusted-context-laundered-through-step-output REDACTED
- Static Analysis (SAST) · High: watchdog-untrusted-context-laundered-across-jobs REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: watchdog-untrusted-context-laundered-across-jobs REDACTED
- Static Analysis (SAST) · High: watchdog-untrusted-context-laundered-across-jobs REDACTED
- Static Analysis (SAST) · High: gha-curl-pipe-shell REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-go-toolchain-in-workflow REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-node-runtime-in-workflow REDACTED
- Dependency Vulnerabilities · High CVE: System.Security.Cryptography.Pkcs 9.0.6 build/packages.lock.json
- Dependency Vulnerabilities · High CVE: System.Security.Cryptography.Xml 9.0.0 build/packages.lock.json
- Dependency Vulnerabilities · Medium CVE: AngleSharp 1.2.0 tests/Morphir.Live.Tests/packages.lock.json
- Knowledge Freshness · Orphaned knowledge src/Morphir.Tooling/Scenarios/ManagementScenario.cs
- Observability · No structured logging
- Outbound HTTP resilience · Outbound HTTP without resilience
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €490,000 · Estimate
| Cost to rebuild | €160,000 to €810,000, for 2,662 to 8,540 hours of work, about 3.3 person-years for 1 to 7 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 62. 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 | Large: 126,587 lines of product code |
| Comment lines | The estimate prices 120,003 lines. Comment lines count towards the size of 126,587 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 .github.install-scripts | 2 Morphir.Build.Helpers | 3 Morphir.Configuration.IO | 4 Morphir.Extensions.Wasm | 5 Morphir.Internals | 6 Morphir.Myriad.Build | 7 Morphir.Myriad.Hosting | 8 Morphir.Myriad.SystemTextJson | 9 Morphir.Myriad.SystemTextJson.Build | 10 Morphir.SDK.CSharp | 11 Morphir.Tooling | 12 Morphir.Tooling.Configuration | 13 Morphir.Tooling.Features.Management | 14 Morphir.Tooling.Features.Mck | 15 MorphirGuestProbe | 16 Spike | 17 TufProbe | 18 (global) | 19 Morphir.Configuration.Microsoft | 20 Morphir.IR.Codecs | 21 Morphir.Managed | 22 Morphir.Tool | 23 Morphir.Tooling.Features.TaskRecords | 24 Morphir.Tooling.Infrastructure | 25 Morphir.Tooling.Infrastructure.JsonSchema | 26 Morphir.Tooling.Managed | 27 Morphir.IR | 28 Morphir.Tooling.Features.Configuration | 29 Morphir.Tooling.Features.Extensions | 30 Morphir.Tooling.Features.VerifyIR | 31 Morphir | 32 Morphir.Classic.IR | 33 Morphir.Tooling.Features.Generate | 34 Morphir.Tooling.Features.ProjectMigration | 35 Morphir.Tooling.Scenarios | 36 Morphir.Classic.IR.Codecs | 37 Morphir.Tooling.Features.Compile.Sources | 38 Morphir.Tooling.Features.Validate | 39 Morphir.Tooling.Features.WorkspaceMigration | 40 Morphir.Tooling.Features.Compile |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 .github.install-scripts | ||||||||||||||||||||||||||||||||||||||||
| 2 Morphir.Build.Helpers | ||||||||||||||||||||||||||||||||||||||||
| 3 Morphir.Configuration.IO | ||||||||||||||||||||||||||||||||||||||||
| 4 Morphir.Extensions.Wasm | ||||||||||||||||||||||||||||||||||||||||
| 5 Morphir.Internals | ||||||||||||||||||||||||||||||||||||||||
| 6 Morphir.Myriad.Build | ||||||||||||||||||||||||||||||||||||||||
| 7 Morphir.Myriad.Hosting | ||||||||||||||||||||||||||||||||||||||||
| 8 Morphir.Myriad.SystemTextJson | ||||||||||||||||||||||||||||||||||||||||
| 9 Morphir.Myriad.SystemTextJson.Build | ||||||||||||||||||||||||||||||||||||||||
| 10 Morphir.SDK.CSharp | ||||||||||||||||||||||||||||||||||||||||
| 11 Morphir.Tooling | ||||||||||||||||||||||||||||||||||||||||
| 12 Morphir.Tooling.Configuration | ||||||||||||||||||||||||||||||||||||||||
| 13 Morphir.Tooling.Features.Management | ||||||||||||||||||||||||||||||||||||||||
| 14 Morphir.Tooling.Features.Mck | ||||||||||||||||||||||||||||||||||||||||
| 15 MorphirGuestProbe | ||||||||||||||||||||||||||||||||||||||||
| 16 Spike | ||||||||||||||||||||||||||||||||||||||||
| 17 TufProbe | ||||||||||||||||||||||||||||||||||||||||
| 18 (global) | 14 | 25 | 6 | |||||||||||||||||||||||||||||||||||||
| 19 Morphir.Configuration.Microsoft | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 Morphir.IR.Codecs | 19 | |||||||||||||||||||||||||||||||||||||||
| 21 Morphir.Managed | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 Morphir.Tool | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 Morphir.Tooling.Features.TaskRecords | 7 | |||||||||||||||||||||||||||||||||||||||
| 24 Morphir.Tooling.Infrastructure | 1 | 12 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 Morphir.Tooling.Infrastructure.JsonSchema | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 Morphir.Tooling.Managed | 3 | |||||||||||||||||||||||||||||||||||||||
| 27 Morphir.IR | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Morphir.Tooling.Features.Configuration | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 Morphir.Tooling.Features.Extensions | 15 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 Morphir.Tooling.Features.VerifyIR | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 Morphir | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 32 Morphir.Classic.IR | 8 | |||||||||||||||||||||||||||||||||||||||
| 33 Morphir.Tooling.Features.Generate | 1 | 2 | 1 | 3 | 6 | |||||||||||||||||||||||||||||||||||
| 34 Morphir.Tooling.Features.ProjectMigration | 1 | 3 | 12 | |||||||||||||||||||||||||||||||||||||
| 35 Morphir.Tooling.Scenarios | 16 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 Morphir.Classic.IR.Codecs | 8 | 3 | 10 | |||||||||||||||||||||||||||||||||||||
| 37 Morphir.Tooling.Features.Compile.Sources | 4 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 38 Morphir.Tooling.Features.Validate | 1 | 2 | 6 | |||||||||||||||||||||||||||||||||||||
| 39 Morphir.Tooling.Features.WorkspaceMigration | 1 | 3 | 8 | 10 | ||||||||||||||||||||||||||||||||||||
| 40 Morphir.Tooling.Features.Compile | 1 | 8 | 3 | 18 | 2 |
18→2 (global) uses Morphir.Build.Helpers✕
- Connections
- 14 pairs of types, where a type in (global) uses a type in Morphir.Build.Helpers.
- The types involved
Build→Morphir.Build.Helpers.CheckCommandBuild→Morphir.Build.Helpers.CheckOutcomeBuild→Morphir.Build.Helpers.CiEvidenceBuild→Morphir.Build.Helpers.CiTriggerBuild→Morphir.Build.Helpers.DeclaredNativeLibraryBuild→Morphir.Build.Helpers.LinkedPackageBuild→Morphir.Build.Helpers.PackOriginBuild→Morphir.Build.Helpers.ReleaseArtifactBuild→Morphir.Build.Helpers.RepositoryTargetFrameworksBuild→Morphir.Build.Helpers.TargetPlatformBuild→Morphir.Build.Helpers.TestRunBuild→Morphir.Build.Helpers.TestScopeBuild→Morphir.Build.Helpers.TestSuiteSuiteResult→Morphir.Build.Helpers.TestSuite
- Direction
- (global) uses Morphir.Build.Helpers, so a change to Morphir.Build.Helpers can break (global), while a change to (global) can't break Morphir.Build.Helpers.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
18→16 (global) uses Spike✕
- Connections
- 25 pairs of types, where a type in (global) uses a type in Spike.
- The types involved
ExtismDirectGuest→Spike.ExchangeExtismDirectGuest→Spike.IBytesGuestExtismDirectGuest→Spike.LimitsExtismRuntime→Spike.ExchangeExtismRuntime→Spike.IBytesGuestExtismRuntime→Spike.IGuestRuntimeExtismRuntime→Spike.LimitsExtismSdkGuest→Spike.ExchangeExtismSdkGuest→Spike.IBytesGuestExtismSdkGuest→Spike.LimitsNoRuntime→Spike.IBytesGuestNoRuntime→Spike.IGuestRuntimeNoRuntime→Spike.LimitsWacsGuest→Spike.ExchangeWacsGuest→Spike.IBytesGuestWacsGuest→Spike.LimitsWacsRuntime→Spike.IBytesGuestWacsRuntime→Spike.IGuestRuntimeWacsRuntime→Spike.LimitsWasmtimeGuest→Spike.ExchangeWasmtimeGuest→Spike.IBytesGuestWasmtimeGuest→Spike.LimitsWasmtimeRuntime→Spike.IBytesGuestWasmtimeRuntime→Spike.IGuestRuntimeWasmtimeRuntime→Spike.Limits
- Direction
- (global) uses Spike, so a change to Spike can break (global), while a change to (global) can't break Spike.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
18→17 (global) uses TufProbe✕
- Connections
- 6 pairs of types, where a type in (global) uses a type in TufProbe.
- The types involved
Cases→TufProbe.FixtureRepositoryCases→TufProbe.KeyFixtures→TufProbe.FixtureRepositorySignedFixture→TufProbe.FixtureRepositorySignedFixture→TufProbe.KeyV1Fixture→TufProbe.FixtureRepository
- Direction
- (global) uses TufProbe, so a change to TufProbe can break (global), while a change to (global) can't break TufProbe.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
19→3 Morphir.Configuration.Microsoft uses Morphir.Configuration.IO✕
- Connections
- 2 pairs of types, where a type in Morphir.Configuration.Microsoft uses a type in Morphir.Configuration.IO.
- The types involved
Morphir.Configuration.Microsoft.MorphirConfigurationExtensions→Morphir.Configuration.IO.IProjectTreeMorphir.Configuration.Microsoft.MorphirConfigurationExtensions→Morphir.Configuration.IO.ProjectLoadOptions
- Direction
- Morphir.Configuration.Microsoft uses Morphir.Configuration.IO, so a change to Morphir.Configuration.IO can break Morphir.Configuration.Microsoft, while a change to Morphir.Configuration.Microsoft can't break Morphir.Configuration.IO.
- Position
- Below the diagonal: Morphir.Configuration.Microsoft uses a module listed above it, which is the healthy direction.
20→27 Morphir.IR.Codecs uses Morphir.IR part of a loop✕
- Connections
- 19 pairs of types, where a type in Morphir.IR.Codecs uses a type in Morphir.IR.
- The types involved
Morphir.IR.Codecs.DocumentJsonConverter→Morphir.IR.ArrayMorphir.IR.Codecs.DocumentJsonConverter→Morphir.IR.BytesMorphir.IR.Codecs.DocumentJsonConverter→Morphir.IR.DocumentMorphir.IR.Codecs.DocumentJsonConverter→Morphir.IR.ObjectMorphir.IR.Codecs.DocumentJsonConverter→Morphir.IR.UriMorphir.IR.Codecs.DocumentJsonConverter→Morphir.IR.UuidMorphir.IR.Codecs.FqNameJsonConverter→Morphir.IR.FqNameMorphir.IR.Codecs.FqNameJsonConverter→Morphir.IR.ModulePathMorphir.IR.Codecs.FqNameJsonConverter→Morphir.IR.NameMorphir.IR.Codecs.FqNameJsonConverter→Morphir.IR.PackageNameMorphir.IR.Codecs.ModulePathJsonConverter→Morphir.IR.ModulePathMorphir.IR.Codecs.ModulePathJsonConverter→Morphir.IR.NameMorphir.IR.Codecs.MorphirJsonOptions→Morphir.IR.MorphirFormatVersionMorphir.IR.Codecs.NameConverter→Morphir.IR.NameMorphir.IR.Codecs.PackageNameJsonConverter→Morphir.IR.NameMorphir.IR.Codecs.PackageNameJsonConverter→Morphir.IR.PackageNameMorphir.IR.Codecs.PathJsonConverter→Morphir.IR.NameMorphir.IR.Codecs.PathJsonConverter→Morphir.IR.PathMorphir.IR.Codecs.TypeJsonConverter→Morphir.IR.Type
- Direction
- Morphir.IR.Codecs uses Morphir.IR, so a change to Morphir.IR can break Morphir.IR.Codecs, while a change to Morphir.IR.Codecs can't break Morphir.IR.
- 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.
21→11 Morphir.Managed uses Morphir.Tooling✕
- Connections
- 2 pairs of types, where a type in Morphir.Managed uses a type in Morphir.Tooling.
- The types involved
Morphir.Managed.Program→Morphir.Tooling.MorphirCliAppMorphir.Managed.Program→Morphir.Tooling.MorphirCliBuilder
- Direction
- Morphir.Managed uses Morphir.Tooling, so a change to Morphir.Tooling can break Morphir.Managed, while a change to Morphir.Managed can't break Morphir.Tooling.
- Position
- Below the diagonal: Morphir.Managed uses a module listed above it, which is the healthy direction.
22→11 Morphir.Tool uses Morphir.Tooling✕
- Connections
- 2 pairs of types, where a type in Morphir.Tool uses a type in Morphir.Tooling.
- The types involved
Morphir.Tool.Program→Morphir.Tooling.MorphirCliAppMorphir.Tool.Program→Morphir.Tooling.MorphirCliBuilder
- Direction
- Morphir.Tool uses Morphir.Tooling, so a change to Morphir.Tooling can break Morphir.Tool, while a change to Morphir.Tool can't break Morphir.Tooling.
- Position
- Below the diagonal: Morphir.Tool uses a module listed above it, which is the healthy direction.
23→33 Morphir.Tooling.Features.TaskRecords uses Morphir.Tooling.Features.Generate part of a loop✕
- Connections
- 7 pairs of types, where a type in Morphir.Tooling.Features.TaskRecords uses a type in Morphir.Tooling.Features.Generate.
- The types involved
Morphir.Tooling.Features.TaskRecords.CompileTaskRun→Morphir.Tooling.Features.Generate.OutcomeMorphir.Tooling.Features.TaskRecords.CompileTaskStore→Morphir.Tooling.Features.Generate.OutcomeMorphir.Tooling.Features.TaskRecords.MemberPath→Morphir.Tooling.Features.Generate.OutcomeMorphir.Tooling.Features.TaskRecords.OutRoot→Morphir.Tooling.Features.Generate.OutcomeMorphir.Tooling.Features.TaskRecords.TaskFailures→Morphir.Tooling.Features.Generate.GenerationFailureKindMorphir.Tooling.Features.TaskRecords.TaskFailures→Morphir.Tooling.Features.Generate.OutcomeMorphir.Tooling.Features.TaskRecords.TaskInstaller→Morphir.Tooling.Features.Generate.Outcome
- Direction
- Morphir.Tooling.Features.TaskRecords uses Morphir.Tooling.Features.Generate, so a change to Morphir.Tooling.Features.Generate can break Morphir.Tooling.Features.TaskRecords, while a change to Morphir.Tooling.Features.TaskRecords can't break Morphir.Tooling.Features.Generate.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→29 Morphir.Tooling.Infrastructure uses Morphir.Tooling.Features.Extensions part of a loop✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Infrastructure uses a type in Morphir.Tooling.Features.Extensions.
- The types involved
Morphir.Tooling.Infrastructure.InstalledExtensionConnector→Morphir.Tooling.Features.Extensions.IWasmModuleLoader
- Direction
- Morphir.Tooling.Infrastructure uses Morphir.Tooling.Features.Extensions, so a change to Morphir.Tooling.Features.Extensions can break Morphir.Tooling.Infrastructure, while a change to Morphir.Tooling.Infrastructure can't break Morphir.Tooling.Features.Extensions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→33 Morphir.Tooling.Infrastructure uses Morphir.Tooling.Features.Generate part of a loop✕
- Connections
- 12 pairs of types, where a type in Morphir.Tooling.Infrastructure uses a type in Morphir.Tooling.Features.Generate.
- The types involved
Morphir.Tooling.Infrastructure.BoundedCapture→Morphir.Tooling.Features.Generate.RetainedEntryMorphir.Tooling.Infrastructure.InstalledExtensionConnector→Morphir.Tooling.Features.Generate.BackendExtensionRequestMorphir.Tooling.Infrastructure.InstalledExtensionConnector→Morphir.Tooling.Features.Generate.IExternalGenerationBackendMorphir.Tooling.Infrastructure.InstalledExtensionConnector→Morphir.Tooling.Features.Generate.OutcomeMorphir.Tooling.Infrastructure.OwnedBackend→Morphir.Tooling.Features.Generate.BackendDescriptorMorphir.Tooling.Infrastructure.OwnedBackend→Morphir.Tooling.Features.Generate.BackendGenerationRequestMorphir.Tooling.Infrastructure.OwnedBackend→Morphir.Tooling.Features.Generate.BackendOptionsMorphir.Tooling.Infrastructure.OwnedBackend→Morphir.Tooling.Features.Generate.GenerationArtifactsMorphir.Tooling.Infrastructure.OwnedBackend→Morphir.Tooling.Features.Generate.IExternalGenerationBackendMorphir.Tooling.Infrastructure.OwnedBackend→Morphir.Tooling.Features.Generate.MepGenerationBackendMorphir.Tooling.Infrastructure.OwnedBackend→Morphir.Tooling.Features.Generate.OutcomeMorphir.Tooling.Infrastructure.OwnedBackend→Morphir.Tooling.Features.Generate.ValidatedBackendOptions
- Direction
- Morphir.Tooling.Infrastructure uses Morphir.Tooling.Features.Generate, so a change to Morphir.Tooling.Features.Generate can break Morphir.Tooling.Infrastructure, while a change to Morphir.Tooling.Infrastructure can't break Morphir.Tooling.Features.Generate.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→40 Morphir.Tooling.Infrastructure uses Morphir.Tooling.Features.Compile part of a loop✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Infrastructure uses a type in Morphir.Tooling.Features.Compile.
- The types involved
Morphir.Tooling.Infrastructure.InstalledExtensionConnector→Morphir.Tooling.Features.Compile.FrontendExtensionRequest
- Direction
- Morphir.Tooling.Infrastructure uses Morphir.Tooling.Features.Compile, so a change to Morphir.Tooling.Features.Compile can break Morphir.Tooling.Infrastructure, while a change to Morphir.Tooling.Infrastructure can't break Morphir.Tooling.Features.Compile.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→30 Morphir.Tooling.Infrastructure.JsonSchema uses Morphir.Tooling.Features.VerifyIR part of a loop✕
- Connections
- 2 pairs of types, where a type in Morphir.Tooling.Infrastructure.JsonSchema uses a type in Morphir.Tooling.Features.VerifyIR.
- The types involved
Morphir.Tooling.Infrastructure.JsonSchema.SchemaValidationResult→Morphir.Tooling.Features.VerifyIR.ValidationErrorMorphir.Tooling.Infrastructure.JsonSchema.SchemaValidator→Morphir.Tooling.Features.VerifyIR.ValidationError
- Direction
- Morphir.Tooling.Infrastructure.JsonSchema uses Morphir.Tooling.Features.VerifyIR, so a change to Morphir.Tooling.Features.VerifyIR can break Morphir.Tooling.Infrastructure.JsonSchema, while a change to Morphir.Tooling.Infrastructure.JsonSchema can't break Morphir.Tooling.Features.VerifyIR.
- 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.
26→11 Morphir.Tooling.Managed uses Morphir.Tooling✕
- Connections
- 3 pairs of types, where a type in Morphir.Tooling.Managed uses a type in Morphir.Tooling.
- The types involved
Morphir.Tooling.Managed.FSharpFrontendScenario→Morphir.Tooling.IMorphirCliScenarioMorphir.Tooling.Managed.FSharpFrontendScenario→Morphir.Tooling.MorphirCliBuilderMorphir.Tooling.Managed.ManagedComposition→Morphir.Tooling.MorphirCliBuilder
- Direction
- Morphir.Tooling.Managed uses Morphir.Tooling, so a change to Morphir.Tooling can break Morphir.Tooling.Managed, while a change to Morphir.Tooling.Managed can't break Morphir.Tooling.
- Position
- Below the diagonal: Morphir.Tooling.Managed uses a module listed above it, which is the healthy direction.
27→20 Morphir.IR uses Morphir.IR.Codecs✕
- Connections
- 1 pair of types, where a type in Morphir.IR uses a type in Morphir.IR.Codecs.
- The types involved
Morphir.IR.MorphirJson→Morphir.IR.Codecs.MorphirJsonOptions
- Direction
- Morphir.IR uses Morphir.IR.Codecs, so a change to Morphir.IR.Codecs can break Morphir.IR, while a change to Morphir.IR can't break Morphir.IR.Codecs.
- Position
- Below the diagonal: Morphir.IR uses a module listed above it, which is the healthy direction.
28→11 Morphir.Tooling.Features.Configuration uses Morphir.Tooling✕
- Connections
- 4 pairs of types, where a type in Morphir.Tooling.Features.Configuration uses a type in Morphir.Tooling.
- The types involved
Morphir.Tooling.Features.Configuration.ConfigurationCommand→Morphir.Tooling.IMorphirParseErrorHandlerMorphir.Tooling.Features.Configuration.ConfigurationCommandProvider→Morphir.Tooling.ICommandProviderMorphir.Tooling.Features.Configuration.ConfigurationCommandProvider→Morphir.Tooling.IMorphirHostInitializationErrorHandlerMorphir.Tooling.Features.Configuration.ConfigurationEditingCommand→Morphir.Tooling.IMorphirParseErrorHandler
- Direction
- Morphir.Tooling.Features.Configuration uses Morphir.Tooling, so a change to Morphir.Tooling can break Morphir.Tooling.Features.Configuration, while a change to Morphir.Tooling.Features.Configuration can't break Morphir.Tooling.
- Position
- Below the diagonal: Morphir.Tooling.Features.Configuration uses a module listed above it, which is the healthy direction.
28→24 Morphir.Tooling.Features.Configuration uses Morphir.Tooling.Infrastructure✕
- Connections
- 2 pairs of types, where a type in Morphir.Tooling.Features.Configuration uses a type in Morphir.Tooling.Infrastructure.
- The types involved
Morphir.Tooling.Features.Configuration.ConfigurationContainment→Morphir.Tooling.Infrastructure.ContainmentMorphir.Tooling.Features.Configuration.ConfigurationContainment→Morphir.Tooling.Infrastructure.ContainmentSource
- Direction
- Morphir.Tooling.Features.Configuration uses Morphir.Tooling.Infrastructure, so a change to Morphir.Tooling.Infrastructure can break Morphir.Tooling.Features.Configuration, while a change to Morphir.Tooling.Features.Configuration can't break Morphir.Tooling.Infrastructure.
- Position
- Below the diagonal: Morphir.Tooling.Features.Configuration uses a module listed above it, which is the healthy direction.
29→4 Morphir.Tooling.Features.Extensions uses Morphir.Extensions.Wasm✕
- Connections
- 15 pairs of types, where a type in Morphir.Tooling.Features.Extensions uses a type in Morphir.Extensions.Wasm.
- The types involved
Morphir.Tooling.Features.Extensions.DigestMismatch→Morphir.Extensions.Wasm.ModuleDigestMorphir.Tooling.Features.Extensions.ExtensionWorker→Morphir.Extensions.Wasm.WasmChannelMorphir.Tooling.Features.Extensions.LoadedWasmModule→Morphir.Extensions.Wasm.ExtismModuleMorphir.Tooling.Features.Extensions.LoadedWasmModule→Morphir.Extensions.Wasm.ModuleDigestMorphir.Tooling.Features.Extensions.LoadedWasmModule→Morphir.Extensions.Wasm.WasmAbiMorphir.Tooling.Features.Extensions.NotAModule→Morphir.Extensions.Wasm.ModuleDigestMorphir.Tooling.Features.Extensions.OutputChannel→Morphir.Extensions.Wasm.WasmChannelMorphir.Tooling.Features.Extensions.Refused→Morphir.Extensions.Wasm.ModuleDigestMorphir.Tooling.Features.Extensions.Refused→Morphir.Extensions.Wasm.WasmRefusalMorphir.Tooling.Features.Extensions.WasmModuleSource→Morphir.Extensions.Wasm.ModuleDigestMorphir.Tooling.Features.Extensions.WasmModuleSource→Morphir.Extensions.Wasm.WasmAbiMorphir.Tooling.Features.Extensions.WorkerOptions→Morphir.Extensions.Wasm.SessionLimitsMorphir.Tooling.Features.Extensions.WorkerOptions→Morphir.Extensions.Wasm.WasmAbiMorphir.Tooling.Features.Extensions.WorkerReport→Morphir.Extensions.Wasm.GuestOutputDrainMorphir.Tooling.Features.Extensions.WorkerReport→Morphir.Extensions.Wasm.WasmAbi
- Direction
- Morphir.Tooling.Features.Extensions uses Morphir.Extensions.Wasm, so a change to Morphir.Extensions.Wasm can break Morphir.Tooling.Features.Extensions, while a change to Morphir.Tooling.Features.Extensions can't break Morphir.Extensions.Wasm.
- Position
- Below the diagonal: Morphir.Tooling.Features.Extensions uses a module listed above it, which is the healthy direction.
29→24 Morphir.Tooling.Features.Extensions uses Morphir.Tooling.Infrastructure✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Features.Extensions uses a type in Morphir.Tooling.Infrastructure.
- The types involved
Morphir.Tooling.Features.Extensions.ExtensionListCommand→Morphir.Tooling.Infrastructure.TerminalProfile
- Direction
- Morphir.Tooling.Features.Extensions uses Morphir.Tooling.Infrastructure, so a change to Morphir.Tooling.Infrastructure can break Morphir.Tooling.Features.Extensions, while a change to Morphir.Tooling.Features.Extensions can't break Morphir.Tooling.Infrastructure.
- Position
- Below the diagonal: Morphir.Tooling.Features.Extensions uses a module listed above it, which is the healthy direction.
29→33 Morphir.Tooling.Features.Extensions uses Morphir.Tooling.Features.Generate part of a loop✕
- Connections
- 2 pairs of types, where a type in Morphir.Tooling.Features.Extensions uses a type in Morphir.Tooling.Features.Generate.
- The types involved
Morphir.Tooling.Features.Extensions.BackendExtensionSource→Morphir.Tooling.Features.Generate.BackendDescriptorMorphir.Tooling.Features.Extensions.BackendExtensionSource→Morphir.Tooling.Features.Generate.IGenerationBackend
- Direction
- Morphir.Tooling.Features.Extensions uses Morphir.Tooling.Features.Generate, so a change to Morphir.Tooling.Features.Generate can break Morphir.Tooling.Features.Extensions, while a change to Morphir.Tooling.Features.Extensions can't break Morphir.Tooling.Features.Generate.
- 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.
29→40 Morphir.Tooling.Features.Extensions uses Morphir.Tooling.Features.Compile part of a loop✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Features.Extensions uses a type in Morphir.Tooling.Features.Compile.
- The types involved
Morphir.Tooling.Features.Extensions.ConfiguredWasmModule→Morphir.Tooling.Features.Compile.ConfigurationView
- Direction
- Morphir.Tooling.Features.Extensions uses Morphir.Tooling.Features.Compile, so a change to Morphir.Tooling.Features.Compile can break Morphir.Tooling.Features.Extensions, while a change to Morphir.Tooling.Features.Extensions can't break Morphir.Tooling.Features.Compile.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→25 Morphir.Tooling.Features.VerifyIR uses Morphir.Tooling.Infrastructure.JsonSchema✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Features.VerifyIR uses a type in Morphir.Tooling.Infrastructure.JsonSchema.
- The types involved
Morphir.Tooling.Features.VerifyIR.VerifyIRHandler→Morphir.Tooling.Infrastructure.JsonSchema.SchemaValidator
- Direction
- Morphir.Tooling.Features.VerifyIR uses Morphir.Tooling.Infrastructure.JsonSchema, so a change to Morphir.Tooling.Infrastructure.JsonSchema can break Morphir.Tooling.Features.VerifyIR, while a change to Morphir.Tooling.Features.VerifyIR can't break Morphir.Tooling.Infrastructure.JsonSchema.
- Position
- Below the diagonal: Morphir.Tooling.Features.VerifyIR uses a module listed above it, which is the healthy direction.
31→11 Morphir uses Morphir.Tooling✕
- Connections
- 2 pairs of types, where a type in Morphir uses a type in Morphir.Tooling.
- The types involved
Morphir.Program→Morphir.Tooling.MorphirCliAppMorphir.Program→Morphir.Tooling.MorphirCliBuilder
- Direction
- Morphir uses Morphir.Tooling, so a change to Morphir.Tooling can break Morphir, while a change to Morphir can't break Morphir.Tooling.
- Position
- Below the diagonal: Morphir uses a module listed above it, which is the healthy direction.
31→30 Morphir uses Morphir.Tooling.Features.VerifyIR✕
- Connections
- 2 pairs of types, where a type in Morphir uses a type in Morphir.Tooling.Features.VerifyIR.
- The types involved
Morphir.MorphirJsonContext→Morphir.Tooling.Features.VerifyIR.ValidationErrorMorphir.MorphirJsonContext→Morphir.Tooling.Features.VerifyIR.VerifyIRResult
- Direction
- Morphir uses Morphir.Tooling.Features.VerifyIR, so a change to Morphir.Tooling.Features.VerifyIR can break Morphir, while a change to Morphir can't break Morphir.Tooling.Features.VerifyIR.
- Position
- Below the diagonal: Morphir uses a module listed above it, which is the healthy direction.
32→27 Morphir.Classic.IR uses Morphir.IR✕
- Connections
- 8 pairs of types, where a type in Morphir.Classic.IR uses a type in Morphir.IR.
- The types involved
Morphir.Classic.IR.Constructor→Morphir.IR.FqNameMorphir.Classic.IR.ExtensibleRecord→Morphir.IR.NameMorphir.Classic.IR.Field→Morphir.IR.FieldMorphir.Classic.IR.Field→Morphir.IR.NameMorphir.Classic.IR.Reference→Morphir.IR.FqNameMorphir.Classic.IR.Value→Morphir.IR.FqNameMorphir.Classic.IR.Value→Morphir.IR.NameMorphir.Classic.IR.Variable→Morphir.IR.Name
- Direction
- Morphir.Classic.IR uses Morphir.IR, so a change to Morphir.IR can break Morphir.Classic.IR, while a change to Morphir.Classic.IR can't break Morphir.IR.
- Position
- Below the diagonal: Morphir.Classic.IR uses a module listed above it, which is the healthy direction.
33→11 Morphir.Tooling.Features.Generate uses Morphir.Tooling✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Features.Generate uses a type in Morphir.Tooling.
- The types involved
Morphir.Tooling.Features.Generate.GenerateCommand→Morphir.Tooling.IMorphirParseErrorHandler
- Direction
- Morphir.Tooling.Features.Generate uses Morphir.Tooling, so a change to Morphir.Tooling can break Morphir.Tooling.Features.Generate, while a change to Morphir.Tooling.Features.Generate can't break Morphir.Tooling.
- Position
- Below the diagonal: Morphir.Tooling.Features.Generate uses a module listed above it, which is the healthy direction.
33→23 Morphir.Tooling.Features.Generate uses Morphir.Tooling.Features.TaskRecords✕
- Connections
- 2 pairs of types, where a type in Morphir.Tooling.Features.Generate uses a type in Morphir.Tooling.Features.TaskRecords.
- The types involved
Morphir.Tooling.Features.Generate.RecordGenerationSettingsResolver→Morphir.Tooling.Features.TaskRecords.TaskStoreOptionsMorphir.Tooling.Features.Generate.RecordLease→Morphir.Tooling.Features.TaskRecords.CompileTaskOutput
- Direction
- Morphir.Tooling.Features.Generate uses Morphir.Tooling.Features.TaskRecords, so a change to Morphir.Tooling.Features.TaskRecords can break Morphir.Tooling.Features.Generate, while a change to Morphir.Tooling.Features.Generate can't break Morphir.Tooling.Features.TaskRecords.
- Position
- Below the diagonal: Morphir.Tooling.Features.Generate uses a module listed above it, which is the healthy direction.
33→24 Morphir.Tooling.Features.Generate uses Morphir.Tooling.Infrastructure✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Features.Generate uses a type in Morphir.Tooling.Infrastructure.
- The types involved
Morphir.Tooling.Features.Generate.BoundedModelCapture→Morphir.Tooling.Infrastructure.CaptureFailure
- Direction
- Morphir.Tooling.Features.Generate uses Morphir.Tooling.Infrastructure, so a change to Morphir.Tooling.Infrastructure can break Morphir.Tooling.Features.Generate, while a change to Morphir.Tooling.Features.Generate can't break Morphir.Tooling.Infrastructure.
- Position
- Below the diagonal: Morphir.Tooling.Features.Generate uses a module listed above it, which is the healthy direction.
33→29 Morphir.Tooling.Features.Generate uses Morphir.Tooling.Features.Extensions✕
- Connections
- 3 pairs of types, where a type in Morphir.Tooling.Features.Generate uses a type in Morphir.Tooling.Features.Extensions.
- The types involved
Morphir.Tooling.Features.Generate.BackendExtensionRequest→Morphir.Tooling.Features.Extensions.WasmModuleSourceMorphir.Tooling.Features.Generate.GenerationSettings→Morphir.Tooling.Features.Extensions.WasmModuleSourceMorphir.Tooling.Features.Generate.MepBackendExtensionConnector→Morphir.Tooling.Features.Extensions.IWasmModuleLoader
- Direction
- Morphir.Tooling.Features.Generate uses Morphir.Tooling.Features.Extensions, so a change to Morphir.Tooling.Features.Extensions can break Morphir.Tooling.Features.Generate, while a change to Morphir.Tooling.Features.Generate can't break Morphir.Tooling.Features.Extensions.
- Position
- Below the diagonal: Morphir.Tooling.Features.Generate uses a module listed above it, which is the healthy direction.
33→40 Morphir.Tooling.Features.Generate uses Morphir.Tooling.Features.Compile part of a loop✕
- Connections
- 6 pairs of types, where a type in Morphir.Tooling.Features.Generate uses a type in Morphir.Tooling.Features.Compile.
- The types involved
Morphir.Tooling.Features.Generate.BackendExtensionRequest→Morphir.Tooling.Features.Compile.SettingMorphir.Tooling.Features.Generate.GenerateHandler→Morphir.Tooling.Features.Compile.SettingMorphir.Tooling.Features.Generate.GenerationSettings→Morphir.Tooling.Features.Compile.SettingMorphir.Tooling.Features.Generate.RecordGenerationSettingsResolver→Morphir.Tooling.Features.Compile.CompileContextMorphir.Tooling.Features.Generate.RecordGenerationSettingsResolver→Morphir.Tooling.Features.Compile.ICompileConfigurationLoaderMorphir.Tooling.Features.Generate.RecordGenerationSettingsResolver→Morphir.Tooling.Features.Compile.LoadedCompileConfiguration
- Direction
- Morphir.Tooling.Features.Generate uses Morphir.Tooling.Features.Compile, so a change to Morphir.Tooling.Features.Compile can break Morphir.Tooling.Features.Generate, while a change to Morphir.Tooling.Features.Generate can't break Morphir.Tooling.Features.Compile.
- 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.
34→3 Morphir.Tooling.Features.ProjectMigration uses Morphir.Configuration.IO✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Features.ProjectMigration uses a type in Morphir.Configuration.IO.
- The types involved
Morphir.Tooling.Features.ProjectMigration.ProjectMigrationReport→Morphir.Configuration.IO.ProjectMigrationPreview
- Direction
- Morphir.Tooling.Features.ProjectMigration uses Morphir.Configuration.IO, so a change to Morphir.Configuration.IO can break Morphir.Tooling.Features.ProjectMigration, while a change to Morphir.Tooling.Features.ProjectMigration can't break Morphir.Configuration.IO.
- Position
- Below the diagonal: Morphir.Tooling.Features.ProjectMigration uses a module listed above it, which is the healthy direction.
34→11 Morphir.Tooling.Features.ProjectMigration uses Morphir.Tooling✕
- Connections
- 3 pairs of types, where a type in Morphir.Tooling.Features.ProjectMigration uses a type in Morphir.Tooling.
- The types involved
Morphir.Tooling.Features.ProjectMigration.ProjectCommandProvider→Morphir.Tooling.ICommandProviderMorphir.Tooling.Features.ProjectMigration.ProjectCommandProvider→Morphir.Tooling.IMorphirHostInitializationErrorHandlerMorphir.Tooling.Features.ProjectMigration.ProjectMigrationCommand→Morphir.Tooling.IMorphirParseErrorHandler
- Direction
- Morphir.Tooling.Features.ProjectMigration uses Morphir.Tooling, so a change to Morphir.Tooling can break Morphir.Tooling.Features.ProjectMigration, while a change to Morphir.Tooling.Features.ProjectMigration can't break Morphir.Tooling.
- Position
- Below the diagonal: Morphir.Tooling.Features.ProjectMigration uses a module listed above it, which is the healthy direction.
34→28 Morphir.Tooling.Features.ProjectMigration uses Morphir.Tooling.Features.Configuration✕
- Connections
- 12 pairs of types, where a type in Morphir.Tooling.Features.ProjectMigration uses a type in Morphir.Tooling.Features.Configuration.
- The types involved
Morphir.Tooling.Features.ProjectMigration.MigrationConflictDto→Morphir.Tooling.Features.Configuration.ConfigurationSourceDtoMorphir.Tooling.Features.ProjectMigration.MigrationOriginChangeDto→Morphir.Tooling.Features.Configuration.ConfigurationOriginDtoMorphir.Tooling.Features.ProjectMigration.ProjectMigrationJsonContext→Morphir.Tooling.Features.Configuration.ConfigurationDiagnosticDtoMorphir.Tooling.Features.ProjectMigration.ProjectMigrationJsonContext→Morphir.Tooling.Features.Configuration.ConfigurationEditArtifactDtoMorphir.Tooling.Features.ProjectMigration.ProjectMigrationJsonContext→Morphir.Tooling.Features.Configuration.ConfigurationOriginDtoMorphir.Tooling.Features.ProjectMigration.ProjectMigrationJsonContext→Morphir.Tooling.Features.Configuration.ConfigurationSourceDtoMorphir.Tooling.Features.ProjectMigration.ProjectMigrationJsonContext→Morphir.Tooling.Features.Configuration.ConfigurationValueTypeDtoMorphir.Tooling.Features.ProjectMigration.ProjectMigrationReport→Morphir.Tooling.Features.Configuration.ConfigurationDiagnosticDtoMorphir.Tooling.Features.ProjectMigration.ProjectMigrationReport→Morphir.Tooling.Features.Configuration.ConfigurationEditArtifactDtoMorphir.Tooling.Features.ProjectMigration.ProjectMigrationReport→Morphir.Tooling.Features.Configuration.ConfigurationOriginDtoMorphir.Tooling.Features.ProjectMigration.ProjectMigrationReport→Morphir.Tooling.Features.Configuration.ConfigurationSourceDtoMorphir.Tooling.Features.ProjectMigration.ProjectMigrationReport→Morphir.Tooling.Features.Configuration.ConfigurationValueTypeDto
- Direction
- Morphir.Tooling.Features.ProjectMigration uses Morphir.Tooling.Features.Configuration, so a change to Morphir.Tooling.Features.Configuration can break Morphir.Tooling.Features.ProjectMigration, while a change to Morphir.Tooling.Features.ProjectMigration can't break Morphir.Tooling.Features.Configuration.
- Position
- Below the diagonal: Morphir.Tooling.Features.ProjectMigration uses a module listed above it, which is the healthy direction.
35→11 Morphir.Tooling.Scenarios uses Morphir.Tooling✕
- Connections
- 16 pairs of types, where a type in Morphir.Tooling.Scenarios uses a type in Morphir.Tooling.
- The types involved
Morphir.Tooling.Scenarios.CompilationScenario→Morphir.Tooling.IMorphirCliScenarioMorphir.Tooling.Scenarios.CompilationScenario→Morphir.Tooling.MorphirCliBuilderMorphir.Tooling.Scenarios.ConfigurationScenario→Morphir.Tooling.IMorphirCliScenarioMorphir.Tooling.Scenarios.ConfigurationScenario→Morphir.Tooling.MorphirCliBuilderMorphir.Tooling.Scenarios.GenerationScenario→Morphir.Tooling.IMorphirCliScenarioMorphir.Tooling.Scenarios.GenerationScenario→Morphir.Tooling.MorphirCliBuilderMorphir.Tooling.Scenarios.IrToolingScenario→Morphir.Tooling.IMorphirCliScenarioMorphir.Tooling.Scenarios.IrToolingScenario→Morphir.Tooling.MorphirCliBuilderMorphir.Tooling.Scenarios.ManagementScenario→Morphir.Tooling.IMorphirCliScenarioMorphir.Tooling.Scenarios.ManagementScenario→Morphir.Tooling.MorphirCliBuilderMorphir.Tooling.Scenarios.ProjectScenario→Morphir.Tooling.IMorphirCliScenarioMorphir.Tooling.Scenarios.ProjectScenario→Morphir.Tooling.MorphirCliBuilderMorphir.Tooling.Scenarios.ValidationScenario→Morphir.Tooling.IMorphirCliScenarioMorphir.Tooling.Scenarios.ValidationScenario→Morphir.Tooling.MorphirCliBuilderMorphir.Tooling.Scenarios.WorkspaceScenario→Morphir.Tooling.IMorphirCliScenarioMorphir.Tooling.Scenarios.WorkspaceScenario→Morphir.Tooling.MorphirCliBuilder
- Direction
- Morphir.Tooling.Scenarios uses Morphir.Tooling, so a change to Morphir.Tooling can break Morphir.Tooling.Scenarios, while a change to Morphir.Tooling.Scenarios can't break Morphir.Tooling.
- Position
- Below the diagonal: Morphir.Tooling.Scenarios uses a module listed above it, which is the healthy direction.
35→13 Morphir.Tooling.Scenarios uses Morphir.Tooling.Features.Management✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Scenarios uses a type in Morphir.Tooling.Features.Management.
- The types involved
Morphir.Tooling.Scenarios.ManagementScenario→Morphir.Tooling.Features.Management.ExtensionLocalOutcome
- Direction
- Morphir.Tooling.Scenarios uses Morphir.Tooling.Features.Management, so a change to Morphir.Tooling.Features.Management can break Morphir.Tooling.Scenarios, while a change to Morphir.Tooling.Scenarios can't break Morphir.Tooling.Features.Management.
- Position
- Below the diagonal: Morphir.Tooling.Scenarios uses a module listed above it, which is the healthy direction.
35→30 Morphir.Tooling.Scenarios uses Morphir.Tooling.Features.VerifyIR✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Scenarios uses a type in Morphir.Tooling.Features.VerifyIR.
- The types involved
Morphir.Tooling.Scenarios.IrToolingScenario→Morphir.Tooling.Features.VerifyIR.VerifyIRResult
- Direction
- Morphir.Tooling.Scenarios uses Morphir.Tooling.Features.VerifyIR, so a change to Morphir.Tooling.Features.VerifyIR can break Morphir.Tooling.Scenarios, while a change to Morphir.Tooling.Scenarios can't break Morphir.Tooling.Features.VerifyIR.
- Position
- Below the diagonal: Morphir.Tooling.Scenarios uses a module listed above it, which is the healthy direction.
36→20 Morphir.Classic.IR.Codecs uses Morphir.IR.Codecs✕
- Connections
- 8 pairs of types, where a type in Morphir.Classic.IR.Codecs uses a type in Morphir.IR.Codecs.
- The types involved
Morphir.Classic.IR.Codecs.ClassicTypeJsonConverter→Morphir.IR.Codecs.ConverterReferencesMorphir.Classic.IR.Codecs.ClassicTypeJsonConverter→Morphir.IR.Codecs.MorphirJsonOptionsMorphir.Classic.IR.Codecs.ClassicTypeJsonConverterFactory→Morphir.IR.Codecs.ConverterReferencesMorphir.Classic.IR.Codecs.ClassicTypeJsonConverterFactory→Morphir.IR.Codecs.MorphirJsonOptionsMorphir.Classic.IR.Codecs.FieldJsonConverter→Morphir.IR.Codecs.ConverterReferencesMorphir.Classic.IR.Codecs.FieldJsonConverter→Morphir.IR.Codecs.MorphirJsonOptionsMorphir.Classic.IR.Codecs.FieldJsonConverterFactory→Morphir.IR.Codecs.ConverterReferencesMorphir.Classic.IR.Codecs.FieldJsonConverterFactory→Morphir.IR.Codecs.MorphirJsonOptions
- Direction
- Morphir.Classic.IR.Codecs uses Morphir.IR.Codecs, so a change to Morphir.IR.Codecs can break Morphir.Classic.IR.Codecs, while a change to Morphir.Classic.IR.Codecs can't break Morphir.IR.Codecs.
- Position
- Below the diagonal: Morphir.Classic.IR.Codecs uses a module listed above it, which is the healthy direction.
36→27 Morphir.Classic.IR.Codecs uses Morphir.IR✕
- Connections
- 3 pairs of types, where a type in Morphir.Classic.IR.Codecs uses a type in Morphir.IR.
- The types involved
Morphir.Classic.IR.Codecs.ClassicTypeJsonConverter→Morphir.IR.FqNameMorphir.Classic.IR.Codecs.ClassicTypeJsonConverter→Morphir.IR.NameMorphir.Classic.IR.Codecs.FieldJsonConverter→Morphir.IR.Name
- Direction
- Morphir.Classic.IR.Codecs uses Morphir.IR, so a change to Morphir.IR can break Morphir.Classic.IR.Codecs, while a change to Morphir.Classic.IR.Codecs can't break Morphir.IR.
- Position
- Below the diagonal: Morphir.Classic.IR.Codecs uses a module listed above it, which is the healthy direction.
36→32 Morphir.Classic.IR.Codecs uses Morphir.Classic.IR✕
- Connections
- 10 pairs of types, where a type in Morphir.Classic.IR.Codecs uses a type in Morphir.Classic.IR.
- The types involved
Morphir.Classic.IR.Codecs.ClassicTypeJsonConverter→Morphir.Classic.IR.ExtensibleRecordMorphir.Classic.IR.Codecs.ClassicTypeJsonConverter→Morphir.Classic.IR.FunctionMorphir.Classic.IR.Codecs.ClassicTypeJsonConverter→Morphir.Classic.IR.RecordMorphir.Classic.IR.Codecs.ClassicTypeJsonConverter→Morphir.Classic.IR.ReferenceMorphir.Classic.IR.Codecs.ClassicTypeJsonConverter→Morphir.Classic.IR.TupleMorphir.Classic.IR.Codecs.ClassicTypeJsonConverter→Morphir.Classic.IR.TypeMorphir.Classic.IR.Codecs.ClassicTypeJsonConverter→Morphir.Classic.IR.UnitMorphir.Classic.IR.Codecs.ClassicTypeJsonConverter→Morphir.Classic.IR.VariableMorphir.Classic.IR.Codecs.FieldJsonConverter→Morphir.Classic.IR.FieldMorphir.Classic.IR.Codecs.FieldJsonConverter→Morphir.Classic.IR.Type
- Direction
- Morphir.Classic.IR.Codecs uses Morphir.Classic.IR, so a change to Morphir.Classic.IR can break Morphir.Classic.IR.Codecs, while a change to Morphir.Classic.IR.Codecs can't break Morphir.Classic.IR.
- Position
- Below the diagonal: Morphir.Classic.IR.Codecs uses a module listed above it, which is the healthy direction.
37→24 Morphir.Tooling.Features.Compile.Sources uses Morphir.Tooling.Infrastructure✕
- Connections
- 4 pairs of types, where a type in Morphir.Tooling.Features.Compile.Sources uses a type in Morphir.Tooling.Infrastructure.
- The types involved
Morphir.Tooling.Features.Compile.Sources.MsBuildProjectFileProvider→Morphir.Tooling.Infrastructure.ExitedMorphir.Tooling.Features.Compile.Sources.MsBuildProjectFileProvider→Morphir.Tooling.Infrastructure.ProcessLimitsMorphir.Tooling.Features.Compile.Sources.MsBuildProjectFileProvider→Morphir.Tooling.Infrastructure.ProcessRunMorphir.Tooling.Features.Compile.Sources.SourceCapture→Morphir.Tooling.Infrastructure.CaptureFailureKind
- Direction
- Morphir.Tooling.Features.Compile.Sources uses Morphir.Tooling.Infrastructure, so a change to Morphir.Tooling.Infrastructure can break Morphir.Tooling.Features.Compile.Sources, while a change to Morphir.Tooling.Features.Compile.Sources can't break Morphir.Tooling.Infrastructure.
- Position
- Below the diagonal: Morphir.Tooling.Features.Compile.Sources uses a module listed above it, which is the healthy direction.
37→33 Morphir.Tooling.Features.Compile.Sources uses Morphir.Tooling.Features.Generate✕
- Connections
- 2 pairs of types, where a type in Morphir.Tooling.Features.Compile.Sources uses a type in Morphir.Tooling.Features.Generate.
- The types involved
Morphir.Tooling.Features.Compile.Sources.CapturedDocument→Morphir.Tooling.Features.Generate.RetainedEntryMorphir.Tooling.Features.Compile.Sources.SourceCapture→Morphir.Tooling.Features.Generate.RetainedEntry
- Direction
- Morphir.Tooling.Features.Compile.Sources uses Morphir.Tooling.Features.Generate, so a change to Morphir.Tooling.Features.Generate can break Morphir.Tooling.Features.Compile.Sources, while a change to Morphir.Tooling.Features.Compile.Sources can't break Morphir.Tooling.Features.Generate.
- Position
- Below the diagonal: Morphir.Tooling.Features.Compile.Sources uses a module listed above it, which is the healthy direction.
37→40 Morphir.Tooling.Features.Compile.Sources uses Morphir.Tooling.Features.Compile part of a loop✕
- Connections
- 2 pairs of types, where a type in Morphir.Tooling.Features.Compile.Sources uses a type in Morphir.Tooling.Features.Compile.
- The types involved
Morphir.Tooling.Features.Compile.Sources.ISourceCapture→Morphir.Tooling.Features.Compile.SelectedSourcesMorphir.Tooling.Features.Compile.Sources.SourceCapture→Morphir.Tooling.Features.Compile.SelectedSources
- Direction
- Morphir.Tooling.Features.Compile.Sources uses Morphir.Tooling.Features.Compile, so a change to Morphir.Tooling.Features.Compile can break Morphir.Tooling.Features.Compile.Sources, while a change to Morphir.Tooling.Features.Compile.Sources can't break Morphir.Tooling.Features.Compile.
- 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.
38→11 Morphir.Tooling.Features.Validate uses Morphir.Tooling✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Features.Validate uses a type in Morphir.Tooling.
- The types involved
Morphir.Tooling.Features.Validate.ValidateCommand→Morphir.Tooling.IMorphirParseErrorHandler
- Direction
- Morphir.Tooling.Features.Validate uses Morphir.Tooling, so a change to Morphir.Tooling can break Morphir.Tooling.Features.Validate, while a change to Morphir.Tooling.Features.Validate can't break Morphir.Tooling.
- Position
- Below the diagonal: Morphir.Tooling.Features.Validate uses a module listed above it, which is the healthy direction.
38→24 Morphir.Tooling.Features.Validate uses Morphir.Tooling.Infrastructure✕
- Connections
- 2 pairs of types, where a type in Morphir.Tooling.Features.Validate uses a type in Morphir.Tooling.Infrastructure.
- The types involved
Morphir.Tooling.Features.Validate.ValidateCommand→Morphir.Tooling.Infrastructure.TerminalProfileMorphir.Tooling.Features.Validate.ValidationReport→Morphir.Tooling.Infrastructure.TerminalProfile
- Direction
- Morphir.Tooling.Features.Validate uses Morphir.Tooling.Infrastructure, so a change to Morphir.Tooling.Infrastructure can break Morphir.Tooling.Features.Validate, while a change to Morphir.Tooling.Features.Validate can't break Morphir.Tooling.Infrastructure.
- Position
- Below the diagonal: Morphir.Tooling.Features.Validate uses a module listed above it, which is the healthy direction.
38→33 Morphir.Tooling.Features.Validate uses Morphir.Tooling.Features.Generate✕
- Connections
- 6 pairs of types, where a type in Morphir.Tooling.Features.Validate uses a type in Morphir.Tooling.Features.Generate.
- The types involved
Morphir.Tooling.Features.Validate.IAnalyzerConfiguration→Morphir.Tooling.Features.Generate.OutcomeMorphir.Tooling.Features.Validate.LayeredAnalyzerConfiguration→Morphir.Tooling.Features.Generate.OutcomeMorphir.Tooling.Features.Validate.ModelValidation→Morphir.Tooling.Features.Generate.IModelLoaderMorphir.Tooling.Features.Validate.ModelValidation→Morphir.Tooling.Features.Generate.InvocationContextMorphir.Tooling.Features.Validate.ValidationReport→Morphir.Tooling.Features.Generate.GenerationDiagnosticMorphir.Tooling.Features.Validate.ValidationReport→Morphir.Tooling.Features.Generate.GenerationFailure
- Direction
- Morphir.Tooling.Features.Validate uses Morphir.Tooling.Features.Generate, so a change to Morphir.Tooling.Features.Generate can break Morphir.Tooling.Features.Validate, while a change to Morphir.Tooling.Features.Validate can't break Morphir.Tooling.Features.Generate.
- Position
- Below the diagonal: Morphir.Tooling.Features.Validate uses a module listed above it, which is the healthy direction.
39→3 Morphir.Tooling.Features.WorkspaceMigration uses Morphir.Configuration.IO✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Features.WorkspaceMigration uses a type in Morphir.Configuration.IO.
- The types involved
Morphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationReport→Morphir.Configuration.IO.WorkspaceMigrationPreview
- Direction
- Morphir.Tooling.Features.WorkspaceMigration uses Morphir.Configuration.IO, so a change to Morphir.Configuration.IO can break Morphir.Tooling.Features.WorkspaceMigration, while a change to Morphir.Tooling.Features.WorkspaceMigration can't break Morphir.Configuration.IO.
- Position
- Below the diagonal: Morphir.Tooling.Features.WorkspaceMigration uses a module listed above it, which is the healthy direction.
39→11 Morphir.Tooling.Features.WorkspaceMigration uses Morphir.Tooling✕
- Connections
- 3 pairs of types, where a type in Morphir.Tooling.Features.WorkspaceMigration uses a type in Morphir.Tooling.
- The types involved
Morphir.Tooling.Features.WorkspaceMigration.WorkspaceCommandProvider→Morphir.Tooling.ICommandProviderMorphir.Tooling.Features.WorkspaceMigration.WorkspaceCommandProvider→Morphir.Tooling.IMorphirHostInitializationErrorHandlerMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationCommand→Morphir.Tooling.IMorphirParseErrorHandler
- Direction
- Morphir.Tooling.Features.WorkspaceMigration uses Morphir.Tooling, so a change to Morphir.Tooling can break Morphir.Tooling.Features.WorkspaceMigration, while a change to Morphir.Tooling.Features.WorkspaceMigration can't break Morphir.Tooling.
- Position
- Below the diagonal: Morphir.Tooling.Features.WorkspaceMigration uses a module listed above it, which is the healthy direction.
39→28 Morphir.Tooling.Features.WorkspaceMigration uses Morphir.Tooling.Features.Configuration✕
- Connections
- 8 pairs of types, where a type in Morphir.Tooling.Features.WorkspaceMigration uses a type in Morphir.Tooling.Features.Configuration.
- The types involved
Morphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.Configuration.ConfigurationDiagnosticDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.Configuration.ConfigurationEditArtifactDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.Configuration.ConfigurationOriginDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.Configuration.ConfigurationSourceDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.Configuration.ConfigurationValueTypeDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationReport→Morphir.Tooling.Features.Configuration.ConfigurationDiagnosticDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationReport→Morphir.Tooling.Features.Configuration.ConfigurationEditArtifactDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationReport→Morphir.Tooling.Features.Configuration.ConfigurationValueTypeDto
- Direction
- Morphir.Tooling.Features.WorkspaceMigration uses Morphir.Tooling.Features.Configuration, so a change to Morphir.Tooling.Features.Configuration can break Morphir.Tooling.Features.WorkspaceMigration, while a change to Morphir.Tooling.Features.WorkspaceMigration can't break Morphir.Tooling.Features.Configuration.
- Position
- Below the diagonal: Morphir.Tooling.Features.WorkspaceMigration uses a module listed above it, which is the healthy direction.
39→34 Morphir.Tooling.Features.WorkspaceMigration uses Morphir.Tooling.Features.ProjectMigration✕
- Connections
- 10 pairs of types, where a type in Morphir.Tooling.Features.WorkspaceMigration uses a type in Morphir.Tooling.Features.ProjectMigration.
- The types involved
Morphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.ProjectMigration.MigrationConflictDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.ProjectMigration.MigrationDifferenceDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.ProjectMigration.MigrationEditDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.ProjectMigration.MigrationFieldDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.ProjectMigration.MigrationOriginChangeDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.ProjectMigration.MigrationVerificationDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.ProjectMigration.MigrationWorkspaceDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationJsonContext→Morphir.Tooling.Features.ProjectMigration.ProjectMigrationReportMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationReport→Morphir.Tooling.Features.ProjectMigration.MigrationEditDtoMorphir.Tooling.Features.WorkspaceMigration.WorkspaceMigrationReport→Morphir.Tooling.Features.ProjectMigration.ProjectMigrationReport
- Direction
- Morphir.Tooling.Features.WorkspaceMigration uses Morphir.Tooling.Features.ProjectMigration, so a change to Morphir.Tooling.Features.ProjectMigration can break Morphir.Tooling.Features.WorkspaceMigration, while a change to Morphir.Tooling.Features.WorkspaceMigration can't break Morphir.Tooling.Features.ProjectMigration.
- Position
- Below the diagonal: Morphir.Tooling.Features.WorkspaceMigration uses a module listed above it, which is the healthy direction.
40→11 Morphir.Tooling.Features.Compile uses Morphir.Tooling✕
- Connections
- 1 pair of types, where a type in Morphir.Tooling.Features.Compile uses a type in Morphir.Tooling.
- The types involved
Morphir.Tooling.Features.Compile.CompileCommand→Morphir.Tooling.IMorphirParseErrorHandler
- Direction
- Morphir.Tooling.Features.Compile uses Morphir.Tooling, so a change to Morphir.Tooling can break Morphir.Tooling.Features.Compile, while a change to Morphir.Tooling.Features.Compile can't break Morphir.Tooling.
- Position
- Below the diagonal: Morphir.Tooling.Features.Compile uses a module listed above it, which is the healthy direction.
40→23 Morphir.Tooling.Features.Compile uses Morphir.Tooling.Features.TaskRecords✕
- Connections
- 8 pairs of types, where a type in Morphir.Tooling.Features.Compile uses a type in Morphir.Tooling.Features.TaskRecords.
- The types involved
Morphir.Tooling.Features.Compile.CompileSettings→Morphir.Tooling.Features.TaskRecords.MemberPathMorphir.Tooling.Features.Compile.CompileSettings→Morphir.Tooling.Features.TaskRecords.OutRootMorphir.Tooling.Features.Compile.CompileTaskPlace→Morphir.Tooling.Features.TaskRecords.CompileTaskStoreMorphir.Tooling.Features.Compile.CompileTaskPlace→Morphir.Tooling.Features.TaskRecords.MemberPathMorphir.Tooling.Features.Compile.CompileTaskPlace→Morphir.Tooling.Features.TaskRecords.OutRootMorphir.Tooling.Features.Compile.CompileTaskPlace→Morphir.Tooling.Features.TaskRecords.TaskStoreOptionsMorphir.Tooling.Features.Compile.Publication→Morphir.Tooling.Features.TaskRecords.CompileTaskRunMorphir.Tooling.Features.Compile.TaskRecordCompilePublisher→Morphir.Tooling.Features.TaskRecords.TaskStoreOptions
- Direction
- Morphir.Tooling.Features.Compile uses Morphir.Tooling.Features.TaskRecords, so a change to Morphir.Tooling.Features.TaskRecords can break Morphir.Tooling.Features.Compile, while a change to Morphir.Tooling.Features.Compile can't break Morphir.Tooling.Features.TaskRecords.
- Position
- Below the diagonal: Morphir.Tooling.Features.Compile uses a module listed above it, which is the healthy direction.
40→29 Morphir.Tooling.Features.Compile uses Morphir.Tooling.Features.Extensions✕
- Connections
- 3 pairs of types, where a type in Morphir.Tooling.Features.Compile uses a type in Morphir.Tooling.Features.Extensions.
- The types involved
Morphir.Tooling.Features.Compile.CompileSettings→Morphir.Tooling.Features.Extensions.WasmModuleSourceMorphir.Tooling.Features.Compile.FrontendExtensionRequest→Morphir.Tooling.Features.Extensions.WasmModuleSourceMorphir.Tooling.Features.Compile.MepFrontendExtensionConnector→Morphir.Tooling.Features.Extensions.IWasmModuleLoader
- Direction
- Morphir.Tooling.Features.Compile uses Morphir.Tooling.Features.Extensions, so a change to Morphir.Tooling.Features.Extensions can break Morphir.Tooling.Features.Compile, while a change to Morphir.Tooling.Features.Compile can't break Morphir.Tooling.Features.Extensions.
- Position
- Below the diagonal: Morphir.Tooling.Features.Compile uses a module listed above it, which is the healthy direction.
40→33 Morphir.Tooling.Features.Compile uses Morphir.Tooling.Features.Generate✕
- Connections
- 18 pairs of types, where a type in Morphir.Tooling.Features.Compile uses a type in Morphir.Tooling.Features.Generate.
- The types involved
Morphir.Tooling.Features.Compile.CompileGeneration→Morphir.Tooling.Features.Generate.GenerationSuccessMorphir.Tooling.Features.Compile.CompileGenerationStages→Morphir.Tooling.Features.Generate.GenerationDiagnosticMorphir.Tooling.Features.Compile.CompileGenerationStages→Morphir.Tooling.Features.Generate.GenerationFailureKindMorphir.Tooling.Features.Compile.CompileGenerationStages→Morphir.Tooling.Features.Generate.GenerationSuccessMorphir.Tooling.Features.Compile.CompileGenerationStages→Morphir.Tooling.Features.Generate.IGenerationBackendResolverMorphir.Tooling.Features.Compile.CompileGenerationStages→Morphir.Tooling.Features.Generate.IGenerationPublisherMorphir.Tooling.Features.Compile.CompileGenerationStages→Morphir.Tooling.Features.Generate.ModelReadLimitsMorphir.Tooling.Features.Compile.CompileGenerationStages→Morphir.Tooling.Features.Generate.OutcomeMorphir.Tooling.Features.Compile.CompileTarget→Morphir.Tooling.Features.Generate.BackendOptionsMorphir.Tooling.Features.Compile.CompileTarget→Morphir.Tooling.Features.Generate.RequestedTargetMorphir.Tooling.Features.Compile.CompileTaskLocator→Morphir.Tooling.Features.Generate.OutcomeMorphir.Tooling.Features.Compile.StagedPublisher→Morphir.Tooling.Features.Generate.GenerationArtifactsMorphir.Tooling.Features.Compile.StagedPublisher→Morphir.Tooling.Features.Generate.GenerationPublicationMorphir.Tooling.Features.Compile.StagedPublisher→Morphir.Tooling.Features.Generate.IGenerationPublisherMorphir.Tooling.Features.Compile.StagedPublisher→Morphir.Tooling.Features.Generate.ModelInputMorphir.Tooling.Features.Compile.StagedPublisher→Morphir.Tooling.Features.Generate.OutcomeMorphir.Tooling.Features.Compile.StagedPublisher→Morphir.Tooling.Features.Generate.PublicationPolicyMorphir.Tooling.Features.Compile.TaskDiagnostics→Morphir.Tooling.Features.Generate.GenerationFailure
- Direction
- Morphir.Tooling.Features.Compile uses Morphir.Tooling.Features.Generate, so a change to Morphir.Tooling.Features.Generate can break Morphir.Tooling.Features.Compile, while a change to Morphir.Tooling.Features.Compile can't break Morphir.Tooling.Features.Generate.
- Position
- Below the diagonal: Morphir.Tooling.Features.Compile uses a module listed above it, which is the healthy direction.
40→37 Morphir.Tooling.Features.Compile uses Morphir.Tooling.Features.Compile.Sources✕
- Connections
- 2 pairs of types, where a type in Morphir.Tooling.Features.Compile uses a type in Morphir.Tooling.Features.Compile.Sources.
- The types involved
Morphir.Tooling.Features.Compile.CompileRunner→Morphir.Tooling.Features.Compile.Sources.CapturedSourcesMorphir.Tooling.Features.Compile.CompileRunner→Morphir.Tooling.Features.Compile.Sources.ISourceCapture
- Direction
- Morphir.Tooling.Features.Compile uses Morphir.Tooling.Features.Compile.Sources, so a change to Morphir.Tooling.Features.Compile.Sources can break Morphir.Tooling.Features.Compile, while a change to Morphir.Tooling.Features.Compile can't break Morphir.Tooling.Features.Compile.Sources.
- Position
- Below the diagonal: Morphir.Tooling.Features.Compile uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 136 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | Medium |
| A02:2025 — Security Misconfiguration | 2 | Medium |
Roadmap
Top priorities: Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult(); Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices; Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult(). | +2.4 pts | Medium | Async & latency hygiene |
| Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices. | +1.3 pts | Medium | Slice cohesion |
| Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging. | +1.2 pts | Medium | Outbound HTTP resilience |
| Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness. | +1.0 pts | Medium | Observability |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +0.9 pts | Medium | Keyboard semantics |
| A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does. | +0.6 pts | Medium | Stateful singletons |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). | +0.2 pts | Low | Static Analysis (SAST) |
| Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ClassicTypeJsonConverterFactory.cs, TypeJsonConverter.cs. | +0.2 pts | Low | Explicit Debt |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/Morphir.Configuration.IO/ConfigurationTransaction.cs | 4.3 | Mixed | Explicit Debt: EmptyCatchBlock |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs | 4.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| spikes/wasm-win-x64-trap/TrapRepro.csproj | 4.9 | Mixed | Explicit Debt: NoWarnInCsproj |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
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 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 52 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, 370 of 379 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — 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. Most of this repository's production source (.fs, .rs) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — 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. Most of this repository's production source (.fs, .rs) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D4 Code Duplication — 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 28 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .fs (89,373 lines, 72% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
- D10 Test 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. The 2,354 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 339 test source file(s) (.fs, .ps1) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (go.mod/go.sum), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (424296 line(s) across the 90-day window), but no complexity could be computed for .fs, .rs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (8 contributor(s) across 1031 commit(s) sampled, automation and bot accounts excluded). One of them holds 93% of the history; the other 7 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: solution references project 'src\Morphir.Live\Morphir.Live.fsproj' but the on-disk path is 'src/Morphir.Live/Morphir.Live.fsproj' (separator/casing mismatch); on a case-sensitive file system MSBuildWorkspace would load 0 of these projects. Loading a corrected copy of the solution.
- 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 13 deducted marker(s) and the 0.4/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (89,373 lines, 72% 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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.
- 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D23 Boundary Type-Coupling — 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. Large codebase (33,862 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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 — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — 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 the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D30 Dependency Vulnerabilities — 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. Osv-scanner exited 127 with no findings — dependency CVEs were not measured. 2 of 3 declared ecosystem(s) (npm,nuget) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `scripts/wasm-engine-linux-floor/ManagedSha256.cs`, `spikes/extension-model/jsonrpc/BaselineProbe/Program.cs`, `spikes/extension-model/jsonrpc/CurlyRpcProbe/Program.cs`, `spikes/extension-model/jsonrpc/RawWire.cs`, `spikes/extension-model/jsonrpc/StreamJsonRpcProbe/Program.cs`, … (+56 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D43 Malicious Dependencies — 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. Osv-scanner exited 127 with no findings — dependency CVEs were not measured. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- AX7 Slice cohesion — 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. 94 further occurrence(s) are not listed individually; the score already reflects all 134.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X28 Index access outside its own emptiness guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- Production source was not modelled — run is Degraded — No code model read .c, .fs, so the complexity, duplication and architecture dimensions were scored over a minority of this repository rather than its product, and dimensions that abstained did so for want of a model rather than for want of findings. The grade is NOT representative of this repository; diagnostics.md records the exact cause. The F# sidecar did not produce a code model, so the F# code model degraded to null; the engine recorded no reason.
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
- 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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- 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.
- D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D4 · Code Duplication
28 duplicated block group(s) detected. 4.6 % of the production lines (1,542 of 33,862) are in a reported copy. A further 54 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .fs (72% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
What to do
- Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ConfigurationCommand.cs (2), ManagementScenario.cs, Program.cs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with WasiSandbox.cs, ConfigurationTransaction.cs, MepGenerationBackend.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with ConfigurationCommand.cs, ExtensionHandlers.cs, ToolHandlers.cs. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
58 projects, 0 dependency cycle(s), 2 unstable depended-on project(s).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling — start with Morphir.Myriad.Hosting.csproj, Morphir.Configuration.IO.csproj. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Unstable project Morphir.Myriad.Build finding(s) in Coupling — start with Morphir.Myriad.Build.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Unstable project Morphir.Myriad.SystemTextJson.Build finding(s) in Coupling — start with Morphir.Myriad.SystemTextJson.Build.csproj. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 89 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with Build.cs. — One of this dimension's main actionable groups (1 warning-level).
D7 · Architectural Integrity
All 1 mechanizable ADR(s) are enforced: 1 by analyzers, 0 by tests. Cycles found: 0.
D8 · Code Coverage
Line coverage 86.2%.
What to do
- Resolve the 2 No test project references BaselineProbe finding(s) in Code Coverage — start with BaselineProbe.csproj (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 No test project references FSharpSyntaxLowering finding(s) in Code Coverage — start with FSharpSyntaxLowering.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references TufProbe finding(s) in Code Coverage — start with TufProbe.csproj. — One of this dimension's main actionable groups (1 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, 4 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2354 tests. Measured on the C# suite only — at least 339 test source file(s) (.fs, .ps1) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 4 Fixed-sleep synchronisation finding(s) in Test Quality — start with ChildProcessTests.cs (2), ConfigurationTransactionTests.cs, BoundedProcessTests.cs. — One of this dimension's main actionable groups (4 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 48 packages use a banned license. ★ DEPTH: every package graded here is one this repository's MSBuild projects declare as a direct `PackageReference` (79 declared), and nothing beyond them was reached — this is the DECLARATION-SITE set, NOT the transitive closure. .NET has no lockfile a checkout is guaranteed to carry and this pass grades an unrestored tree, so a banned licence that only a direct dependency's OWN dependencies pull in is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Go module (go.mod/go.sum) and package.json, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D17 · Explicit Debt
13 deducted debt markers + unmeasured dead symbols across 33862 LoC in the .NET projects (0.4/KLoC) → score 9.3. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (72% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with ConfigurationTransaction.cs (3), GenerationPublisher.cs (2), TaskInstaller.cs. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 5 NoWarnInCsproj finding(s) in Explicit Debt — start with _build.csproj (2), TrapRepro.csproj (2), Morphir.Tooling.csproj. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ClassicTypeJsonConverterFactory.cs, TypeJsonConverter.cs. — One of this dimension's main actionable groups (2 issue-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 216 document(s) read across 32 unit(s).
D20 · ADR Quality
1 of 3 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What to do
- Resolve the 1 ADR has no Decision section finding(s) in ADR Quality — start with 0001-morphir-dotnet-default-cli-and-conformance-oracle.md. — One of this dimension's main actionable groups (1 recommendation-level).
D22 · Internal API Consistency
0 API inconsistencies among 22 exposed members measured against a convention their peers follow.
D24 · Comment Value
8 of 796 judged comments only repeat the code they sit on (1.0 %). 11 comment(s) in another language or script were not judged.
What to do
- Resolve the 8 redundant comment finding(s) in Comment Value — start with BlackBoxRulesTests.cs (2), TypeMorphirJsonEncodingTests.cs (2), BackendExtensionSource.cs. — One of this dimension's main actionable groups (8 recommendation-level).
D26 · Project Cohesion
1 of 52 projects flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
136 finding(s): 0 critical, 134 high, 2 medium, 0 low. 111 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 66 file(s) — `openspec/changes/archive/2026-11-13-consolidate-black-box-tests/evidence/library-reach.cs` (line 12), `scripts/measure-compile-aot.sh` (line 37), `scripts/wasm-engine-linux-floor/ManagedSha256.cs` (lines 10–15), `spikes/extension-model/jsonrpc/BaselineProbe/Program.cs` (lines 22–24), `spikes/extension-model/jsonrpc/CurlyRpcProbe/Program.cs` (lines 81–86), … (+61 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 41 of those file(s) — `spikes/extension-model/jsonrpc/RawWire.cs`, `spikes/extension-model/roslyn-aot/Program.cs`, `spikes/extension-model/wasm-runtime/shared/Probe.cs`, `spikes/tuf-client/TufProbe/Repositories.cs`, `src/Morphir.Configuration.IO/ConfigurationEditService.cs`, … (+36 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 13 of those file(s) — `spikes/extension-model/jsonrpc/RawWire.cs`, `spikes/extension-model/roslyn-aot/Program.cs`, `spikes/extension-model/wasm-runtime/shared/Probe.cs`, `src/Morphir.Configuration.IO/ConfigurationEditService.cs`, `src/Morphir.Configuration.IO/ProjectMigrationService.cs`, … (+8 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 15 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 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 111 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 (111 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 2 ecosystem(s) that were scanned (npm,nuget). Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,nuget), and the findings above are real and complete for them. osv was not scanned (osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured), so this is not the whole dependency surface and the result is reported at reduced confidence.
D31 · IaC & Container Security
2 finding(s): 0 critical, 0 high, 0 medium, 2 low.
D34 · Knowledge Freshness
12 of 400 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Morphir.Tooling/Features/Management/DistHandlers.cs. Counted over 400 of the 527 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
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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 known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured), so this is not the whole dependency surface and the result is reported at reduced confidence.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 109 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
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
- A <tr> may hold only <td>/<th> cells. Text or a value written between the cells is moved out of the table by the browser, so it is read detached from its row. Wrap it in a <td>. — openspec/changes/archive/2026-11-09-add-mep-core/design.html:239
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. — src/Morphir.Live/wwwroot/index.html:34
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AX10 · Code composition
AX2 · Stateful singletons
- `ConsoleOutputHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_originalStdout, _isRedirected; e.g. `_originalStdout` at line 21). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Morphir.Tooling/Infrastructure/ConsoleOutputHelper.cs:7
What to do
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- The namespaces Morphir.Tooling.Features.VerifyIR ↔ Morphir.Tooling.Infrastructure.JsonSchema depend on each other. The lightest dependency in the cycle is Morphir.Tooling.Features.VerifyIR → Morphir.Tooling.Infrastructure.JsonSchema (Morphir.Tooling.Features.VerifyIR.VerifyIRHandler → Morphir.Tooling.Infrastructure.JsonSchema.SchemaValidator, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Morphir.Tooling/Features/VerifyIR/VerifyIR.cs:41
- The namespaces Morphir.IR ↔ Morphir.IR.Codecs depend on each other. The lightest dependency in the cycle is Morphir.IR → Morphir.IR.Codecs (Morphir.IR.MorphirJson → Morphir.IR.Codecs.MorphirJsonOptions, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Morphir.Core/IR/MorphirJson.cs:3
- The namespaces Morphir.Tooling.Features.Compile ↔ Morphir.Tooling.Features.Compile.Sources ↔ Morphir.Tooling.Features.Extensions ↔ Morphir.Tooling.Features.Generate ↔ Morphir.Tooling.Features.TaskRecords ↔ Morphir.Tooling.Infrastructure depend on each other. The lightest dependency in the cycle is Morphir.Tooling.Features.Extensions → Morphir.Tooling.Features.Compile (Morphir.Tooling.Features.Extensions.ConfiguredWasmModule → Morphir.Tooling.Features.Compile.ConfigurationView, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Morphir.Tooling/Features/Extensions/ConfiguredWasmModule.cs:5
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX5 · Architecture & structure
AX7 · Slice cohesion
- `CompileCommand` (slice 'Compile') depends on `RequestedTarget` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileCommand.cs:106
- `CompileCommand` (slice 'Compile') depends on `GenerateCommand` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileCommand.cs:111
- `CompileSettings` (slice 'Compile') depends on `WasmModuleSource` from slice 'Extensions'. — src/Morphir.Tooling/Features/Compile/CompileContracts.cs:210
- `CompileSettings` (slice 'Compile') depends on `OutRoot` from slice 'TaskRecords'. — src/Morphir.Tooling/Features/Compile/CompileContracts.cs:226
- `CompileSettings` (slice 'Compile') depends on `MemberPath` from slice 'TaskRecords'. — src/Morphir.Tooling/Features/Compile/CompileContracts.cs:228
- `CompileTarget` (slice 'Compile') depends on `RequestedTarget` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:19
- `CompileTarget` (slice 'Compile') depends on `BackendOptions` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:19
- `CompileTarget` (slice 'Compile') depends on `BackendOptionText` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:49
- `CompileTarget` (slice 'Compile') depends on `Outcome.Failure` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:50
- `CompileGeneration` (slice 'Compile') depends on `GenerationSuccess` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:71
- `CompileGenerationStages` (slice 'Compile') depends on `IGenerationBackendResolver` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:80
- `CompileGenerationStages` (slice 'Compile') depends on `IGenerationPublisher` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:80
- `CompileGenerationStages` (slice 'Compile') depends on `ModelReadLimits` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:84
- `CompileGenerationStages` (slice 'Compile') depends on `ModelInput` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:94
- `CompileGenerationStages` (slice 'Compile') depends on `InputFormat` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:94
- `CompileGenerationStages` (slice 'Compile') depends on `GenerationSettings` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:95
- `CompileGenerationStages` (slice 'Compile') depends on `PublicationPolicy` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:95
- `CompileGenerationStages` (slice 'Compile') depends on `Outcome` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:99
- `CompileGenerationStages` (slice 'Compile') depends on `GenerationSuccess` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:99
- `CompileGenerationStages` (slice 'Compile') depends on `GenerationFailure` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:101
- `CompileGenerationStages` (slice 'Compile') depends on `GenerationFailureKind` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:101
- `CompileGenerationStages` (slice 'Compile') depends on `RetainedInput.File` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:105
- `CompileGenerationStages` (slice 'Compile') depends on `RetainedEntry` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:105
- `CompileGenerationStages` (slice 'Compile') depends on `GenerationModelLoader` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:106
- `CompileGenerationStages` (slice 'Compile') depends on `LoadedModel` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:109
- `CompileGenerationStages` (slice 'Compile') depends on `GenerationStages` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:109
- `CompileGenerationStages` (slice 'Compile') depends on `GenerationDiagnostic` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:145
- `CompileGenerationStages` (slice 'Compile') depends on `GenerationArtifacts` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:237
- `CompileGenerationStages` (slice 'Compile') depends on `GenerationPublication` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:241
- `TaskRecordCompilePublisher` (slice 'Compile') depends on `TaskStoreOptions` from slice 'TaskRecords'. — src/Morphir.Tooling/Features/Compile/CompilePublisher.cs:42
- `TaskRecordCompilePublisher` (slice 'Compile') depends on `CompileTaskRun` from slice 'TaskRecords'. — src/Morphir.Tooling/Features/Compile/CompilePublisher.cs:57
- `TaskRecordCompilePublisher` (slice 'Compile') depends on `Outcome.Success` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompilePublisher.cs:57
- `TaskRecordCompilePublisher` (slice 'Compile') depends on `IrDescriptor` from slice 'TaskRecords'. — src/Morphir.Tooling/Features/Compile/CompilePublisher.cs:79
- `TaskRecordCompilePublisher` (slice 'Compile') depends on `RecordPath` from slice 'TaskRecords'. — src/Morphir.Tooling/Features/Compile/CompilePublisher.cs:79
- `TaskRecordCompilePublisher` (slice 'Compile') depends on `IrLayout` from slice 'TaskRecords'. — src/Morphir.Tooling/Features/Compile/CompilePublisher.cs:79
- `TaskRecordCompilePublisher` (slice 'Compile') depends on `IrStorageFormat` from slice 'TaskRecords'. — src/Morphir.Tooling/Features/Compile/CompilePublisher.cs:79
- `TaskRecordCompilePublisher` (slice 'Compile') depends on `CompileProduct` from slice 'TaskRecords'. — src/Morphir.Tooling/Features/Compile/CompilePublisher.cs:80
- `TaskRecordCompilePublisher` (slice 'Compile') depends on `TaskRecord` from slice 'TaskRecords'. — src/Morphir.Tooling/Features/Compile/CompilePublisher.cs:80
- `TaskRecordCompilePublisher` (slice 'Compile') depends on `InstallReport` from slice 'TaskRecords'. — src/Morphir.Tooling/Features/Compile/CompilePublisher.cs:86
- `TaskDiagnostics` (slice 'Compile') depends on `GenerationFailure` from slice 'Generate'. — src/Morphir.Tooling/Features/Compile/CompilePublisher.cs:104
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
AX8 · Test isolation
AX9 · CQS / query purity
ED5 · Idempotency
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/Morphir.Core/IR/Codecs/TypeJsonConverter.cs:10, src/Morphir.Core/IR/Codecs/TypeJsonConverter.cs:15
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
M1 · Documentation (README)
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
- CONTRIBUTING.md links to `dco/dco_template.md`, but `dco/dco_template.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:114
- README.md names .NET 8, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:149
- tests/Morphir.Configuration.IO.Smoke/README.md names FSharp.Core 11, but the manifest declares `FSharp.Core` 10.1.403. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tests/Morphir.Configuration.IO.Smoke/README.md:69
- docs/content/contributing/design/prds/introduce-fsharp-sdk-package.md names AltCover 8, but the manifest declares `altcover` 9.0.145. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/content/contributing/design/prds/introduce-fsharp-sdk-package.md:204
- docs/content/contributing/design/spikes/extension-model/dotnet-guest-toolchains.md names Wasmtime 49, but the manifest declares `Wasmtime` 50.0.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/content/contributing/design/spikes/extension-model/dotnet-guest-toolchains.md:30
What to do
- Reconcile the README with reality: CONTRIBUTING.md links to `dco/dco_template.md`, but `dco/dco_template.md` does not exist; README.md names .NET 8, but the projects target .NET 10, 11; tests/Morphir.Configuration.IO.Smoke/README.md names FSharp.Core 11, but the manifest declares `FSharp.Core` 10.1.403; docs/content/contributing/design/prds/introduce-fsharp-sdk-package.md names AltCover 8, but the manifest declares `altcover` 9.0.145; docs/content/contributing/design/spikes/extension-model/dotnet-guest-toolchains.md names Wasmtime 49, but the manifest declares `Wasmtime` 50.0.1.
P1 · CI/CD gates
P10 · Library API & versioning
P11 · BDD / executable specs
P2 · Observability
What to do
- Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 21 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:15
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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out. — build/Build.CI.cs:217
What to do
- Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
PF3 · Async & latency hygiene
- 9 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×8) — build/Build.CI.cs:237, build/Build.CI.cs:239, build/Build.CI.cs:246, …
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
X5 · Nullable reference types
- ~1.4 `!` suppressions per 1k syntax nodes — 241 suppression(s) across the 177804 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 87% | Checked 3 of 9 | Solid. |
| Architecture | 63% | Adequate — gated by AX7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 92% | Exemplary | Strongest area. |
| Readiness | 61% | Adequate — gated by P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 65% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 68% | Adequate — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Largest drag on the score — prioritise here. |
Unscored — 4 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 13 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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 — 62 check(s) not relevant to this codebase
- AX1 Captive dependencies — AX1 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- AX6 Interface segregation — AX6 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — 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.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .fs, .rs exposed no member bodies
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D12 Dependency Hygiene — Dependency hygiene not measured
- D15 Churn × Complexity Hotspots — complexity unreadable for .fs, .rs — churn × complexity hotspots could not be measured
- 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 .c, .fs, .py, .rs, 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.
- D2 Cognitive Complexity — cognitive complexity not measured — .fs, .rs exposed no member bodies
- D21 Naming Consistency — D21 withholds its affix on another kind of member (`Is` on a non-bool, `Async` on a non-awaitable) rows: 1 candidate(s) found and not reported.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .c, .fs, .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D3 God Classes — Most of this repository's production source (.fs, .rs) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 61 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (114 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — IC1 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage data present for 229 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
- 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 — X1 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X12 Unreachable branch — X12 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — X13 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — X18 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X19 Unrestored process-global state — X19 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X2 Cancellation propagation — X2 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X21 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — X25 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X27 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — X28 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X29 Per-element action decided by a fixed element — X29 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X3 Exception handling — X3 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — X30 reached only 27% of this repository's production lines — fsharp (91,741 lines), rust (335 lines), python (252 lines), c (24 lines), javascript (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's C# was read, and every log call in it goes through a logger that takes one finished message — its own wrapper, log4net, Console or Debug — so an interpolated message there loses nothing the API could have kept. Calls through Microsoft.Extensions.Logging, Serilog, NLog or ZLogger, or any logger with a message-template overload, would be judged.
- 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 — 150 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- EmptyCatchBlock src/Morphir.Configuration.IO/ConfigurationTransaction.cs:217
- EmptyCatchBlock src/Morphir.Configuration.IO/ConfigurationTransaction.cs:601
- EmptyCatchBlock src/Morphir.Configuration.IO/ConfigurationTransaction.cs:603
- EmptyCatchBlock src/Morphir.Tooling/Features/Generate/GenerationPublisher.cs:71
- EmptyCatchBlock src/Morphir.Tooling/Features/Generate/GenerationPublisher.cs:72
- EmptyCatchBlock src/Morphir.Tooling/Features/TaskRecords/TaskInstaller.cs:200
- NoWarnInCsproj build/_build.csproj:8
- NoWarnInCsproj build/_build.csproj:8
- NoWarnInCsproj spikes/wasm-win-x64-trap/TrapRepro.csproj:24
- NoWarnInCsproj spikes/wasm-win-x64-trap/TrapRepro.csproj:24
- NoWarnInCsproj src/Morphir.Tooling/Morphir.Tooling.csproj:8
- Namespace dependency cycle src/Morphir.Tooling/Features/VerifyIR/VerifyIR.cs:41
- Namespace dependency cycle src/Morphir.Core/IR/MorphirJson.cs:3
- Namespace dependency cycle src/Morphir.Tooling/Features/Extensions/ConfiguredWasmModule.cs:5
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:50
- WriteOnlyPrivateField src/Morphir.Core/IR/Codecs/TypeJsonConverter.cs:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 147 finding(s)
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileCommand.cs:106
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileCommand.cs:111
- Cross-slice coupling: Compile → Extensions src/Morphir.Tooling/Features/Compile/CompileContracts.cs:210
- Cross-slice coupling: Compile → TaskRecords src/Morphir.Tooling/Features/Compile/CompileContracts.cs:226
- Cross-slice coupling: Compile → TaskRecords src/Morphir.Tooling/Features/Compile/CompileContracts.cs:228
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:19
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:19
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:49
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:50
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:71
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:80
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:80
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:84
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:94
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:94
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:95
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:95
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:99
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:99
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:101
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:101
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:105
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:105
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:106
- Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:109
- Sync-over-async blocking
- Sync-over-async blocking build/Build.CI.cs:237
- Sync-over-async blocking build/Build.CI.cs:239
- Sync-over-async blocking build/Build.CI.cs:246
- Sync-over-async blocking build/Build.WindowsToolchain.cs:28
- Sync-over-async blocking src/Morphir.Myriad.Hosting/MyriadHost.cs:81
- Sync-over-async blocking src/Morphir.Tooling/Features/Compile/CompileCommand.cs:146
- Sync-over-async blocking src/Morphir.Tooling/Features/Extensions/ExtensionWorkerProcess.cs:61
- Sync-over-async blocking src/Morphir.Tooling/MorphirCli.cs:308
- Fixed-sleep synchronisation: SeparateNativeProcessesUseTheSameCoordinator tests/Morphir.Configuration.IO.Tests/ConfigurationTransactionTests.cs:141
- Fixed-sleep synchronisation: Timeout_KillsAGrandchildThatOutlivedItsParent tests/Morphir.TestSupport.Tests/ChildProcessTests.cs:44
- Fixed-sleep synchronisation: TimeoutStartsAfterTheGateIsHeld tests/Morphir.TestSupport.Tests/ChildProcessTests.cs:93
- Fixed-sleep synchronisation: DeadlineStopsADescendantThatOutlivedItsParent tests/Morphir.Tooling.Tests/Infrastructure/BoundedProcessTests.cs:46
- Duplicated block (5 lines × 2) src/Morphir.Tooling/Scenarios/ManagementScenario.cs:189
- Duplicated block (5 lines × 2) spikes/extension-model/jsonrpc/CurlyRpcProbe/Program.cs:65
- Duplicated block (5 lines × 2) src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:95
- Duplicated block (5 lines × 2) src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:116
- Duplicated block (7 lines × 2) src/Morphir.Extensions.Wasm/WasiSandbox.cs:281
- Duplicated block (7 lines × 2) src/Morphir.Configuration.IO/ConfigurationTransaction.cs:489
- Duplicated block (7 lines × 2) src/Morphir.Tooling/Features/Generate/MepGenerationBackend.cs:129
- Duplicated block (9 lines × 2) src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:40
- Duplicated block (9 lines × 2) src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:155
- Duplicated block (9 lines × 2) src/Morphir.Tooling/Features/Management/ToolHandlers.cs:122
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (14 corresponding lines) src/Morphir.Configuration.IO/Json5Reader.cs:101
- Edited copy of a member (14 corresponding lines) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:414
- Edited copy of a member (16 corresponding lines) src/Morphir.Configuration.IO/ProjectMigrationService.cs:274
- Edited copy of a member (16 corresponding lines) src/Morphir.Extensions.Wasm/GuestOutput.cs:174
- Edited copies of one member (3 members, 15+ corresponding lines) src/Morphir.Tooling/Features/Management/DistCommands.cs:95
- Edited copies of one member (3 members, 15+ corresponding lines) src/Morphir.Tooling/MorphirCliExtensions.cs:83
- Edited copy of a member (9 corresponding lines) src/Morphir.Configuration.IO/ConfigurationEditService.cs:211
- Edited copy of a member (9 corresponding lines) src/Morphir.Configuration.IO/ProjectMigrationService.cs:296
- Edited copy of a member (12 corresponding lines) src/Morphir.Extensions.Wasm/WasiSandbox.cs:202
- Edited copy of a member (12 corresponding lines) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:35
- Edited copy of a member (2 corresponding lines) src/Morphir.Tooling/Features/Generate/CSharpGenerationBackend.cs:49
- Edited copy of a member (2 corresponding lines) src/Morphir.Configuration.IO/ProjectMigrationService.cs:263
- Duplicated block (12 lines × 2) src/Morphir.Tooling/Features/Management/ExtensionCommands.cs:122
- Duplicated block (12 lines × 2) src/Morphir.Tooling/Features/Management/ToolCommands.cs:127
- Duplicated block (8 lines × 2) src/Morphir.Tooling/Scenarios/ManagementScenario.cs:67
- Duplicated block (8 lines × 2) src/Morphir.Tooling/Scenarios/ManagementScenario.cs:80
- Duplicated block (6 lines × 2) build/Helpers/PackagedContents.cs:79
- Duplicated block (6 lines × 2) src/Morphir.Myriad.Build/GenerateMorphirModules.cs:19
- Off the main sequence: Morphir.Myriad.Hosting src/Morphir.Myriad.Hosting/Morphir.Myriad.Hosting.csproj:1
- Off the main sequence: Morphir.Configuration.IO(net11.0) src/Morphir.Configuration.IO/Morphir.Configuration.IO.csproj:1
- No test project references BaselineProbe spikes/extension-model/jsonrpc/BaselineProbe/BaselineProbe.csproj
- No test project references BaselineProbe spikes/extension-model/wasm-runtime/BaselineProbe/BaselineProbe.csproj
- Unfinished stub — throws NotImplementedException src/Morphir.Core/IR/Codecs/TypeJsonConverter.cs:10
- Unfinished stub — throws NotImplementedException src/Morphir.Core/IR/Codecs/TypeJsonConverter.cs:15
- Text directly inside a table row openspec/changes/archive/2026-11-09-add-mep-core/design.html:239
- Anchor without href src/Morphir.Live/wwwroot/index.html:34
- Process-global static state: ConsoleOutputHelper src/Morphir.Tooling/Infrastructure/ConsoleOutputHelper.cs:7
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (56 corresponding lines) src/Morphir.Tooling/Scenarios/ManagementScenario.cs:54
- Edited copies of one member (3 members, 54+ corresponding lines) src/Morphir.Tooling/Features/Management/DistHandlers.cs:91
- Edited copy of a member (24 corresponding lines) spikes/extension-model/jsonrpc/CurlyRpcProbe/Program.cs:37
- Edited copies of one member (4 members, 43+ corresponding lines) src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:153
- Edited copy of a member (44 corresponding lines) src/Morphir.Tooling/Features/Management/DistHandlers.cs:163
- Edited copies of one member (3 members, 41+ corresponding lines) src/Morphir.Tooling/Features/Management/DistHandlers.cs:276
- Edited copy of a member (20 corresponding lines) src/Morphir.Tooling/Features/Generate/MepGenerationBackend.cs:124
- Edited copies of one member (3 members, 34+ corresponding lines) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:152
- Edited copy of a member (23 corresponding lines) src/Morphir.Tooling/Configuration/OsPaths.cs:17
- Edited copy of a member (38 corresponding lines) src/Morphir.Tooling/Infrastructure/JsonSchema/SchemaValidator.cs:120
- Edited copy of a member (15 corresponding lines) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:448
- Edited copy of a member (10 corresponding lines) src/Morphir.Extensions.Wasm/WasiSandbox.cs:232
- Edited copy of a member (6 corresponding lines) src/Morphir.Extensions.Wasm/ExtismHostFunctions.cs:96
- Edited copies of one member (3 members, 7+ corresponding lines) src/Morphir.Tooling/Features/Configuration/ConfigurationEditingCommand.cs:34
- Edited copies of one member (3 members, 2+ corresponding lines) src/Morphir.Configuration.IO/ProjectLoading.cs:149
- Edited copy of a member (4 corresponding lines) build/Helpers/ReleaseProfiles.cs:152
- Edited copies of one member (3 members, 6+ corresponding lines) src/Morphir.Extensions.Wasm/GuestFailure.cs:208
- Duplicated block (26 lines × 2) build/ChangelogHelper.cs:23
- Duplicated block (21–22 lines × 2) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:168
- Duplicated block (16 lines × 2) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:208
- Duplicated block (18 lines × 2) src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:103
- Duplicated block (11–16 lines × 3) src/Morphir.Tooling/Features/Management/DistHandlers.cs:100
- Duplicated block (15–16 lines × 2) src/Morphir.Tooling/Infrastructure/JsonSchema/SchemaValidator.cs:128
- Duplicated block (14 lines × 3) src/Morphir.Tooling/Features/Management/DistCommands.cs:96
- Duplicated block (11 lines × 3) src/Morphir.Tooling/Features/Configuration/ConfigurationEditingHost.cs:50
- Duplicated block (10 lines × 2) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:453
- Duplicated block (9 lines × 5) src/Morphir.Tooling/Scenarios/ManagementScenario.cs:68
- Duplicated block (8–9 lines × 3) src/Morphir.Configuration.IO/ConfigurationEditService.cs:211
- Duplicated block (14 lines × 2) src/Morphir.Managed/Program.cs:21
- Unstable project Morphir.Myriad.Build src/Morphir.Myriad.Build/Morphir.Myriad.Build.csproj:1
- Unstable project Morphir.Myriad.SystemTextJson.Build src/Morphir.Myriad.SystemTextJson.Build/Morphir.Myriad.SystemTextJson.Build.csproj:1
- Low cohesion: Build (LCOM4 8) build/Build.cs:21
- No test project references FSharpSyntaxLowering spikes/FSharpSyntaxLowering/FSharpSyntaxLowering.fsproj
- No test project references TufProbe spikes/tuf-client/TufProbe/TufProbe.csproj
- No test project references CurlyRpcProbe spikes/extension-model/jsonrpc/CurlyRpcProbe/CurlyRpcProbe.csproj
- No test project references ExtismProbe spikes/extension-model/wasm-runtime/ExtismProbe/ExtismProbe.csproj
- No test project references FSharpMatchJoin spikes/FSharpMatchJoin/FSharpMatchJoin.fsproj
- No test project references MorphirGuestProbe spikes/extension-model/dotnet-guest-toolchains/csharp-naot-llvm/MorphirGuestProbe.csproj
- No test project references MorphirGuestProbeFs spikes/extension-model/dotnet-guest-toolchains/fsharp-naot-llvm/MorphirGuestProbeFs.fsproj
- No test project references NuGetProbe spikes/nuget-extension-source/NuGetProbe/NuGetProbe.fsproj
- No test project references PlatformProbe spikes/extension-model/tool-platform-packages/PlatformProbe/PlatformProbe.csproj
- No test project references RoslynAotProbe spikes/extension-model/roslyn-aot/RoslynAotProbe.csproj
- No test project references StreamJsonRpcProbe spikes/extension-model/jsonrpc/StreamJsonRpcProbe/StreamJsonRpcProbe.csproj
- No test project references TrapRepro spikes/wasm-win-x64-trap/TrapRepro.csproj
- No test project references WacsProbe spikes/extension-model/wasm-runtime/WacsProbe/WacsProbe.csproj
- No test project references WasmtimeProbe spikes/extension-model/wasm-runtime/WasmtimeProbe/WasmtimeProbe.csproj
- Outbound HTTP without resilience build/Build.CI.cs:217
Minor — 74 finding(s)
- Duplicated predicate build/Build.MorphirProbe.cs:66
- Duplicated predicate src/Morphir.Tooling/Features/Generate/CSharpGenerationBackend.cs:54
- Duplicated predicate build/Build.MorphirProbe.cs:208
- Duplicated predicate src/Morphir.Configuration.IO/ConfigurationEditService.cs:173
- Duplicated predicate src/Morphir.Configuration.IO/ProjectMigrationService.cs:135
- Duplicated predicate src/Morphir.Ion/Ir/TreeStems.fs:37
- Duplicated predicate src/Morphir.Ion/Ir/TreeStems.fs:31
- Duplicated predicate src/Morphir.Ion/IonReader.fs:210
- Duplicated predicate src/Morphir.Models/Json/Codecs/NameCodec.fs:64
- Duplicated predicate src/Morphir.Extensions/Text.fs:46
- Duplicated predicate src/Morphir.Models/Json/Codecs/FQNameCodec.fs:64
- Duplicated predicate src/Morphir.Models/Json/V4/V4JsonValues.fs:134
- Duplicated predicate src/Morphir.Extensions.Installation/Archives.fs:1262
- Duplicated predicate src/Morphir.Conformance/GuestKit/Kit.fs:107
- Duplicated predicate src/Morphir.Toolchain.IO/WindowsProcess.fs:585
- Duplicated predicate src/Morphir.Frontend.FSharp/Lowering.fs:75
- Duplicated predicate src/Morphir.Ion/Ir/V4IonTypes.fs:27
- Duplicated predicate src/Morphir.Myriad.Build/GenerateMorphirModules.cs:71
- Duplicated predicate src/Morphir.Tooling/Features/Management/DistCommands.cs:107
- Duplicated predicate src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:176
- Duplicated predicate src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:88
- Duplicated predicate src/Morphir.Tooling/Features/Compile/CompileReport.cs:157
- Duplicated predicate src/Morphir.Configuration.IO/ConfigurationEditService.cs:180
- Duplicated predicate src/Morphir.Configuration.IO/ConfigurationEditService.cs:107
- Duplicated predicate src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:80
- Orphaned file src/Morphir.Tooling/Features/Management/DistHandlers.cs:1
- Orphaned file src/Morphir.Live/Pages/TryMorphir.fs:1
- Orphaned file src/Morphir.Tooling/Features/Management/ToolHandlers.cs:1
- Orphaned file src/Morphir.Tooling/Features/Management/ArtifactPathResolver.cs:1
- Orphaned file src/Morphir.SDK.FSharp/String.fs:1
- Orphaned file src/Morphir.SDK.FSharp/List.fs:1
- Orphaned file src/Morphir.Tooling/Features/Management/ToolCommands.cs:1
- Orphaned file src/Morphir.Tooling/Features/Management/DistCommands.cs:1
- Orphaned file src/Morphir.SDK.FSharp/Dict.fs:1
- Orphaned file src/Morphir.Tooling/Configuration/OsPaths.cs:1
- Orphaned file src/Morphir.SDK.FSharp/Result.fs:1
- Orphaned file src/Morphir.Tooling/Features/Management/Manifest.cs:1
- Silent fallback default in catch build/Helpers/PathHelper.cs:192
- Silent fallback default in catch build/Helpers/PublishedLayout.cs:89
- Silent fallback default in catch build/Helpers/PublishedLayout.cs:104
- Silent fallback default in catch src/Morphir.Configuration.IO/ConfigurationTransaction.cs:447
- Silent fallback default in catch src/Morphir.Configuration.IO/ConfigurationTransaction.cs:472
- Silent fallback default in catch src/Morphir.Configuration.IO/FileSystemProjectTree.cs:55
- Silent fallback default in catch src/Morphir.Tooling/Features/VerifyIR/VersionDetector.cs:39
- Silent fallback default in catch spikes/extension-model/dotnet-guest-toolchains/csharp-naot-llvm/Guest.cs:71
- Silent fallback default in catch spikes/wasm-win-x64-trap/Program.cs:116
- redundant comment src/Morphir.Tooling/Features/Extensions/BackendExtensionSource.cs:22
- redundant comment src/Morphir.Tooling/Features/VerifyIR/VersionDetector.cs:21
- redundant comment tests/Morphir.Build.Tests/Helpers/BlackBoxRulesTests.cs:98
- redundant comment tests/Morphir.Build.Tests/Helpers/BlackBoxRulesTests.cs:166
- redundant comment tests/Morphir.Build.Tests/Helpers/PackageValidatorTests.cs:49
- redundant comment tests/Morphir.Core.Tests/Classic/IR/TypeMorphirJsonEncodingTests.cs:336
- redundant comment tests/Morphir.Core.Tests/Classic/IR/TypeMorphirJsonEncodingTests.cs:368
- redundant comment tests/Morphir.TestSupport.Tests/Drivers/TestEligibilityTests.cs:168
- README/code drift CONTRIBUTING.md:114
- README/code drift README.md:149
- README/code drift tests/Morphir.Configuration.IO.Smoke/README.md:69
- README/code drift docs/content/contributing/design/prds/introduce-fsharp-sdk-package.md:204
- README/code drift docs/content/contributing/design/spikes/extension-model/dotnet-guest-toolchains.md:30
- REDACTED
- REDACTED
- Silent fallback default on unknown code src/Morphir.Configuration.IO/ProjectLoading.cs:158
- Silent fallback default on unknown code src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:204
- Silent fallback default on parse failure src/Morphir.Tooling/Features/Compile/CompileCommand.cs:190
- Silent fallback default on parse failure spikes/extension-model/jsonrpc/RawWire.cs:106
- ADR has no Decision section docs/adr/0001-morphir-dotnet-default-cli-and-conformance-oracle.md:6
- Projects may be oversized for their cohesion src/Morphir.Tooling/Morphir.Tooling.csproj:1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- Sleep-based test synchronization
- No SAST REDACTED:15
- Null-forgiving operator (`!`) suppressions override nullable warnings
- Hand-rolled JSON/XML parsing via regex build/Build.MorphirProbe.cs:366
Minor — 8 finding(s)
- doc comments repeat the names tests/Morphir.Build.Tests/Helpers/PathHelperTests.cs:7
- doc comments repeat the names src/Morphir.Core/IR/Path.cs:29
- doc comments repeat the names src/Morphir.Extensions.Wasm/WasmChannelFailure.cs:83
- doc comments repeat the names tests/Morphir.Extensions.Wasm.Tests/CraftedCorpus.cs:305
- doc comments repeat the names src/Morphir.Myriad.SystemTextJson.Build/GenerateJsonContexts.cs:24
- doc comments repeat the names tests/Morphir.TestSupport/Drivers/ExtensionDriver.cs:9
- doc comments repeat the names src/Morphir.Tooling/Features/Compile/CompileContracts.cs:181
- doc comments repeat the names tests/Morphir.Tooling.Tests/Features/Compile/CompileWorkspace.cs:16
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-696aed05f3aa4ed4a5ef158148e58d23/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-696aed05f3aa4ed4a5ef158148e58d23/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 .agents .claude .codex .config .cursor .cursorrules .devcontainer .editorconfig .fallout .gemini .git-blame-ignore-revs .gitattributes .github .gitignore .grok .husky .idea .nuke .opencode .prototools .vscode .windsurf AGENTS.md CHANGELOG.md CLAUDE.md CODE_OF_CONDUCT.md CONTRIBUTING.md Directory.Build.props Directory.Build.targets Directory.Packages.props LICENSE LICENSE.md LICENSE.spdx MAINTAINERS.md Morphir.slnx NOTICE NOTICE.txt NUKE_MIGRATION.md NuGet.config README.md build build.cmd REDACTED REDACTED conformance docs dotnet.config examples global.json integrations justfile mise.toml openspec renovate.json scratch scripts spikes src tests | 136 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Morphir.slnx package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D30 · Dependency Vulnerabilities | 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-853ac0d10d5c44b29f688c62cfd8dc27 | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 61 file(s) — `scripts/wasm-engine-linux-floor/ManagedSha256.cs`, `spikes/extension-model/jsonrpc/BaselineProbe/Program.cs`, `spikes/extension-model/jsonrpc/CurlyRpcProbe/Program.cs`, `spikes/extension-model/jsonrpc/RawWire.cs`, `spikes/extension-model/jsonrpc/StreamJsonRpcProbe/Program.cs`, … (+56 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-853ac0d10d5c44b29f688c62cfd8dc27 | 0 | artifacts/raw/osv-scanner.json |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |