Public report of finos/morphir-dotnet, published 15 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard. This copy doesn't carry the survey's signed record. How a survey is checked →

finos/morphir-dotnet

Measured 15 November 2026, 12:17 UTC, at code version 50c11ee

Test reliability is not measured: No test run produced results.

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 62out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 8 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A large codebase: 126,587 lines of product code in 58 projects, tests not counted · Estimated rebuild effort: about 3.3 person-years · Weakest lens: Performance, 60

Findings by how serious they are

150 critical 147 serious 82 minor

24 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 12:17 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

52of 52 dimensions measured by tools.
370of 379 findings point to an exact file and line, so you can open each one in the code. The other 9 concern the repository as a whole, such as missing documentation.
52dimensions across 7 lenses, read from 126,587 lines of product code in 58 projects.
Chapters

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.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Performance 60 · counts for 46%Production Readiness 61 · counts for 25%Architecture 63 · counts for 14%Security and Compliance 65 · counts for 8%Accessibility 68 · counts for 4%Code Health 87 · counts for 2%Maturity 92 · counts for 1%

The weakest lenses score close to each other, so improving any of them moves the score.

Code composition: what the lines of code are
Business logic 9%Supporting code 7%Tests 84%
New since the last survey: 235 findings

These 235 critical or serious findings weren't in the previous survey, on 31 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • 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

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 81 findings

These 81 critical or serious findings were in the previous survey, on 31 October 2026, and are gone from this one.

  • 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 problemStandard, 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.
SizeLarge: 126,587 lines of product code
Comment linesThe estimate prices 120,003 lines. Comment lines count towards the size of 126,587 lines but aren't priced as work.
What it is notNot 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.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Raises the score by about 2 points · Medium effort · Async & latency hygiene
2
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
Raises the score by about 1 point · Medium effort · Slice cohesion
3
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.
Raises the score by about 1 point · Medium effort · Outbound HTTP resilience

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €490,000 to build again, about 3.3 person-years of work. Its weakest lens is Performance, at 60 (Adequate). Performance is about whether the code is written and measured with speed in mind. Because the weakest lens counts most in the score, work on Performance also moves the score most.
Based on: the rebuild estimate · the Performance grade · how much each lens counts
What to do: Start with the Performance actions in Top priorities.
If you do one thing first · First action
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult(). Of all the actions in this report, it raises the score most for the work it takes: about 2 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — bounded-context dependency graph

Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.

arch BaselineProbe (spikes/extension-model/jsonrpc/BaselineProbe) BaselineProbe (spikes/extension-model/jsonrpc/BaselineProbe) BaselineProbe (spikes/extension-model/wasm-runtime/BaselineProbe) BaselineProbe (spikes/extension-model/wasm-runtime/BaselineProbe) CurlyRpcProbe CurlyRpcProbe ExtismProbe ExtismProbe Morphir Morphir ctx:Tooling Tooling Tooling Morphir->ctx:Tooling Managed Managed Managed->ctx:Tooling ctx:Tooling.Managed Tooling.Managed Managed Managed->ctx:Tooling.Managed Tool Tool Tool->ctx:Tooling Tool->ctx:Tooling.Managed PlatformProbe PlatformProbe RoslynAotProbe RoslynAotProbe SampleTool SampleTool StreamJsonRpcProbe StreamJsonRpcProbe ToolPortable ToolPortable ToolRid ToolRid TrapRepro TrapRepro TufProbe TufProbe WacsProbe WacsProbe WasmtimeProbe WasmtimeProbe _build _build ctx:Compilation.Mep Compilation.Mep Mep _build->ctx:Compilation.Mep ctx:Extensions.Installation Extensions.Installation Installation _build->ctx:Extensions.Installation ctx:Analyzers Analyzers Analyzers ctx:Extensions Extensions Extensions ctx:Analyzers->ctx:Extensions ctx:IR.Pipeline.Plugins IR.Pipeline.Plugins Plugins ctx:Analyzers->ctx:IR.Pipeline.Plugins ctx:CodeGeneration.FSharp CodeGeneration.FSharp FSharp ctx:IR.Pipeline IR.Pipeline Pipeline ctx:CodeGeneration.FSharp->ctx:IR.Pipeline ctx:CodeGeneration.FSharp->ctx:IR.Pipeline.Plugins ctx:Models Models Models ctx:CodeGeneration.FSharp->ctx:Models ctx:Compilation Compilation Compilation ctx:Compilation->ctx:Models ctx:Compilation.Mep->ctx:Compilation ctx:Mep Mep Mep ctx:Compilation.Mep->ctx:Mep ctx:Toolchain.IO Toolchain.IO IO ctx:Compilation.Mep->ctx:Toolchain.IO ctx:Extensions->ctx:Compilation ctx:Extensions->ctx:Mep ctx:Extensions->ctx:Models ctx:Extensions.Installation->ctx:Extensions ctx:Extensions.Installation->ctx:Mep ctx:Frontend.FSharp Frontend.FSharp FSharp ctx:Frontend.FSharp->ctx:Compilation ctx:IR.Pipeline.Plugins->ctx:IR.Pipeline ctx:IR.Pipeline.Plugins->ctx:Models ctx:Tooling->ctx:Analyzers ctx:Tooling->ctx:CodeGeneration.FSharp ctx:Tooling->ctx:Compilation ctx:Tooling->ctx:Compilation.Mep ctx:Tooling->ctx:Extensions ctx:Tooling->ctx:Extensions.Installation ctx:Tooling->ctx:IR.Pipeline ctx:Tooling->ctx:Models ctx:Tooling->ctx:Toolchain.IO ctx:Tooling.Managed->ctx:Frontend.FSharp ctx:Tooling.Managed->ctx:Tooling __more__ +26 more contexts

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

46 modules, with 53 dependencies between them. 3 loops run through 10 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 6 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 .github.install-scripts2 Morphir.Build.Helpers3 Morphir.Configuration.IO4 Morphir.Extensions.Wasm5 Morphir.Internals6 Morphir.Myriad.Build7 Morphir.Myriad.Hosting8 Morphir.Myriad.SystemTextJson9 Morphir.Myriad.SystemTextJson.Build10 Morphir.SDK.CSharp11 Morphir.Tooling12 Morphir.Tooling.Configuration13 Morphir.Tooling.Features.Management14 Morphir.Tooling.Features.Mck15 MorphirGuestProbe16 Spike17 TufProbe18 (global)19 Morphir.Configuration.Microsoft20 Morphir.IR.Codecs21 Morphir.Managed22 Morphir.Tool23 Morphir.Tooling.Features.TaskRecords24 Morphir.Tooling.Infrastructure25 Morphir.Tooling.Infrastructure.JsonSchema26 Morphir.Tooling.Managed27 Morphir.IR28 Morphir.Tooling.Features.Configuration29 Morphir.Tooling.Features.Extensions30 Morphir.Tooling.Features.VerifyIR31 Morphir32 Morphir.Classic.IR33 Morphir.Tooling.Features.Generate34 Morphir.Tooling.Features.ProjectMigration35 Morphir.Tooling.Scenarios36 Morphir.Classic.IR.Codecs37 Morphir.Tooling.Features.Compile.Sources38 Morphir.Tooling.Features.Validate39 Morphir.Tooling.Features.WorkspaceMigration40 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)14256
19 Morphir.Configuration.Microsoft2
20 Morphir.IR.Codecs19
21 Morphir.Managed2
22 Morphir.Tool2
23 Morphir.Tooling.Features.TaskRecords7
24 Morphir.Tooling.Infrastructure1121
25 Morphir.Tooling.Infrastructure.JsonSchema2
26 Morphir.Tooling.Managed3
27 Morphir.IR1
28 Morphir.Tooling.Features.Configuration42
29 Morphir.Tooling.Features.Extensions15121
30 Morphir.Tooling.Features.VerifyIR1
31 Morphir22
32 Morphir.Classic.IR8
33 Morphir.Tooling.Features.Generate12136
34 Morphir.Tooling.Features.ProjectMigration1312
35 Morphir.Tooling.Scenarios1611
36 Morphir.Classic.IR.Codecs8310
37 Morphir.Tooling.Features.Compile.Sources422
38 Morphir.Tooling.Features.Validate126
39 Morphir.Tooling.Features.WorkspaceMigration13810
40 Morphir.Tooling.Features.Compile183182
Uses a module listed above itPart of a loopThe module itself
1 .github.install-scripts2 Morphir.Build.Helpers3 Morphir.Configuration.IO4 Morphir.Extensions.Wasm5 Morphir.Internals6 Morphir.Myriad.Build7 Morphir.Myriad.Hosting8 Morphir.Myriad.SystemTextJson9 Morphir.Myriad.SystemTextJson.Build10 Morphir.SDK.CSharp11 Morphir.Tooling12 Morphir.Tooling.Configuration13 Morphir.Tooling.Features.Management14 Morphir.Tooling.Features.Mck15 MorphirGuestProbe16 Spike17 TufProbe18 (global)19 Morphir.Configuration.Microsoft20 Morphir.IR.Codecs21 Morphir.Managed22 Morphir.Tool23 Morphir.Tooling.Features.TaskRecords24 Morphir.Tooling.Infrastructure25 Morphir.Tooling.Infrastructure.JsonSchema26 Morphir.Tooling.Managed27 Morphir.IR28 Morphir.Tooling.Features.Configuration29 Morphir.Tooling.Features.Extensions30 Morphir.Tooling.Features.VerifyIR31 Morphir32 Morphir.Classic.IR33 Morphir.Tooling.Features.Generate34 Morphir.Tooling.Features.ProjectMigration35 Morphir.Tooling.Scenarios36 Morphir.Classic.IR.Codecs37 Morphir.Tooling.Features.Compile.Sources38 Morphir.Tooling.Features.Validate39 Morphir.Tooling.Features.WorkspaceMigration40 Morphir.Tooling.Features.Compile.github.install-scripts1Morphir.Build.Helpers2Morphir.Configuration.IO3Morphir.Extensions.Wasm4Morphir.Internals5Morphir.Myriad.Build6Morphir.Myriad.Hosting7Morphir.Myriad.SystemTextJson8Morphir.Myriad.SystemTextJson.Build9Morphir.SDK.CSharp10Morphir.Tooling11Morphir.Tooling.Configuration12Morphir.Tooling.Features.Management13Morphir.Tooling.Features.Mck14MorphirGuestProbe15Spike16TufProbe17(global)18Morphir.Configuration.Microsoft19Morphir.IR.Codecs20Morphir.Managed21Morphir.Tool22Morphir.Tooling.Features.TaskRecords23Morphir.Tooling.Infrastructure24Morphir.Tooling.Infrastructure.JsonSchema25Morphir.Tooling.Managed26Morphir.IR27Morphir.Tooling.Features.Configuration28Morphir.Tooling.Features.Extensions29Morphir.Tooling.Features.VerifyIR30Morphir31Morphir.Classic.IR32Morphir.Tooling.Features.Generate33Morphir.Tooling.Features.ProjectMigration34Morphir.Tooling.Scenarios35Morphir.Classic.IR.Codecs36Morphir.Tooling.Features.Compile.Sources37Morphir.Tooling.Features.Validate38Morphir.Tooling.Features.WorkspaceMigration39Morphir.Tooling.Features.Compile40142562192271121231421512112281213613121611831042212613810183182+6 more modules (most-connected shown)

At a glance — Code Health · 87% · Checked 3 of 9 ·

At a glance — Architecture · 63% · Adequate · gated by AX7 ·

At a glance — Maturity · 92% · Exemplary ·

At a glance — Readiness · 61% · Adequate · gated by P3, P7 ·

At a glance — Security · 65% · Adequate · gated by D29, D36 ·

At a glance — Accessibility · 68% · Adequate · gated by AC4 ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection136High / Critical
A03:2025 — Software Supply Chain Failures10Medium
A02:2025 — Security Misconfiguration2Medium

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.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().+2.4 ptsMediumAsync & latency hygiene
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.+1.3 ptsMediumSlice 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 ptsMediumOutbound HTTP resilience
Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.+1.0 ptsMediumObservability
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+0.9 ptsMediumKeyboard 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 ptsMediumStateful singletons
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3).+0.2 ptsLowStatic Analysis (SAST)
Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ClassicTypeJsonConverterFactory.cs, TypeJsonConverter.cs.+0.2 ptsLowExplicit Debt

File quality

Per-file score 0–10 — a quality signature. Of 94 files carrying findings, judged against the Production bar: 5% slop · 44% mixed · 51% near-clean.

FileScoreBandWorst signal
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
src/Morphir.Configuration.IO/ConfigurationTransaction.cs4.3MixedExplicit Debt: EmptyCatchBlock
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs4.6MixedExplicit Debt: WriteOnlyPrivateField
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
spikes/wasm-win-x64-trap/TrapRepro.csproj4.9MixedExplicit Debt: NoWarnInCsproj
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 150

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.

Serious — 147

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.

Minor — 82

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 24

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.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 52 dimensions across the health lenses
D4D5D6D7D8D10D13D14D17D19D20D22D24D26D28D29D30D31D34D35D36D43D44AC1AC2AC3AC4AC5AC6AX10AX2AX3AX5AX7AX8AX9ED5GD1M1M2M3M4P1P10P11P2P3P4P6P7PF3X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. 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. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1df24-3f6f-7caf-8a96-3e770925f86d.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • 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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

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

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • 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 Duplication8.2 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.2 / 10 · rule-coverage 100% · ceiling Verified

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.

Duplicated block (5 lines × 2) · ×4src/Morphir.Tooling/Scenarios/ManagementScenario.cs:189
Duplicated block (7 lines × 2) · ×3src/Morphir.Extensions.Wasm/WasiSandbox.cs:281
Duplicated block (9 lines × 2) · ×3src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:40
Edited copy of a member (14 corresponding lines) · ×2src/Morphir.Configuration.IO/Json5Reader.cs:101
Edited copy of a member (16 corresponding lines) · ×2src/Morphir.Configuration.IO/ProjectMigrationService.cs:274

+ 36 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. 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).
  3. 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).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling9.4 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Prevented

58 projects, 0 dependency cycle(s), 2 unstable depended-on project(s).

Off the main sequence: Morphir.Myriad.Hosting · ×2src/Morphir.Myriad.Hosting/Morphir.Myriad.Hosting.csproj:1
Unstable project Morphir.Myriad.Buildsrc/Morphir.Myriad.Build/Morphir.Myriad.Build.csproj:1
Unstable project Morphir.Myriad.SystemTextJson.Buildsrc/Morphir.Myriad.SystemTextJson.Build/Morphir.Myriad.SystemTextJson.Build.csproj:1

What to do

  1. 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).
  2. 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).
  3. 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).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

1 of 89 classes have LCOM4 above 3.

Low cohesion: Build (LCOM4 8)build/Build.cs:21

What to do

  1. 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).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D7 · Architectural Integrity10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

All 1 mechanizable ADR(s) are enforced: 1 by analyzers, 0 by tests. Cycles found: 0.

✓ On the Gold path — maintain.

Detailed fixes: d7_recommendation.md.

D8 · Code Coverage10.0 / 10Stronggated by 16 serious findings✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

Line coverage 86.2%.

No test project references BaselineProbe · ×2spikes/extension-model/jsonrpc/BaselineProbe/BaselineProbe.csproj
No test project references FSharpSyntaxLoweringspikes/FSharpSyntaxLowering/FSharpSyntaxLowering.fsproj
No test project references TufProbespikes/tuf-client/TufProbe/TufProbe.csproj
No test project references CurlyRpcProbespikes/extension-model/jsonrpc/CurlyRpcProbe/CurlyRpcProbe.csproj
No test project references ExtismProbespikes/extension-model/wasm-runtime/ExtismProbe/ExtismProbe.csproj

+ 10 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. 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).
  3. 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).

Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.

D10 · Test Quality10.0 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

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.

Fixed-sleep synchronisation: SeparateNativeProcessesUseTheSameCoordinator · ×4tests/Morphir.Configuration.IO.Tests/ConfigurationTransactionTests.cs:141

What to do

  1. 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).

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D17 · Explicit Debt9.3 / 10Adequategated by 13 critical findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.3 / 10 · rule-coverage 100% · ceiling Prevented

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).

EmptyCatchBlock · ×6src/Morphir.Configuration.IO/ConfigurationTransaction.cs:217
NoWarnInCsproj · ×5build/_build.csproj:8
WriteOnlyPrivateField · ×2src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:50

What to do

  1. 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).
  2. 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).
  3. 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).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

2 of 2 documentation facets pass in full. 216 document(s) read across 32 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality6.7 / 10Adequate✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 6.7 / 10 · rule-coverage 100% · ceiling Documented

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.

ADR has no Decision sectiondocs/adr/0001-morphir-dotnet-default-cli-and-conformance-oracle.md:6detected by adr-integrity

What to do

  1. 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).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D22 · Internal API Consistency10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the internal API surface is consistent and coherent.

Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 API inconsistencies among 22 exposed members measured against a convention their peers follow.

✓ On the Gold path — maintain.

Detailed fixes: d22_recommendation.md.

D24 · Comment Value9.0 8.9 / 10Strong✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 99% · ceiling Documented

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.

redundant comment · ×8src/Morphir.Tooling/Features/Extensions/BackendExtensionSource.cs:22
doc comments repeat the names · ×8tests/Morphir.Build.Tests/Helpers/PathHelperTests.cs:7

What to do

  1. 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).

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion9.6 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Documented

1 of 52 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionsrc/Morphir.Tooling/Morphir.Tooling.csproj:1

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.2 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 0.2 / 10 · rule-coverage 100% · ceiling Documented

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.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 5 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. 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).
  3. 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).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D31 · IaC & Container Security9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

2 finding(s): 0 critical, 0 high, 0 medium, 2 low.

REDACTED

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness9.7 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Documented

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.

Orphaned file · ×12src/Morphir.Tooling/Features/Management/DistHandlers.cs:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 3 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. 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).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC3 · Page structure8.0 / 10Strong✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • 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 semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • 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 correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AX10 · Code composition7.8 / 10Strong✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX2 · Stateful singletons6.6 / 10Adequate✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `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 cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

  • 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 & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX7 · Slice cohesion1.0 / 10Critical✓ Tool-verified

Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.

Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.

  • `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 isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

ED5 · Idempotency10.0 / 10Exemplary○ Nothing flagged

Other · Readiness — Whether retry-prone mutations (command handlers and message or event consumers) are idempotent, so an at-least-once redelivery or a client retry does not apply the effect twice.

Method: Roslyn (any mutation, ungated): each persistent write of a command handler or message/event consumer is idempotent when a guard is visible (an exists/dedup read that gates an exit, upsert, idempotency-key/inbox used in a condition or store call, versioned or fixed-value write, dedup envelope or pipeline), at risk only on positive double-apply evidence (a fresh-identity insert, an accumulation on a loaded and saved object, a growing member list, an unkeyed POST/SMTP send/Stripe charge), and otherwise not classified. Deterministic, no model; not scored when more than half are not classified. Advisory.

Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. Every mutation is classified exhaustively and deterministically: guarded, at risk on positive evidence, or not classified; the score is over the classified ones and is withheld when they are fewer than half.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • 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)8.7 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

M2 · Architecture documentation10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy8.6 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

  • 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 gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P11 · BDD / executable specs10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether behaviour is captured as executable Gherkin specifications (a plus for shared understanding) — only assessed when a BDD framework is present.

Method: Filesystem scan: BDD framework presence (SpecFlow, Gherkin files) when a project references a BDD tool. Exhaustive, deterministic.

P2 · Observability5.5 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

What to do

  • Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • 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 & Rollback10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `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 hygiene6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • 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 types8.9 / 10Strong✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • ~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

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health87%Checked 3 of 9Solid.
Architecture63%Adequate — gated by AX7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity92%ExemplaryStrongest area.
Readiness61%Adequate — gated by P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security65%Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility68%Adequate — gated by AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60%AdequateLargest drag on the score — prioritise here.
Unscored — 4 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • 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

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • 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

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • 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)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 150 finding(s)
D29 · Static Analysis (SAST) · 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
  • + 86 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · EmptyCatchBlock · ×6
  • EmptyCatchBlock src/Morphir.Configuration.IO/ConfigurationTransaction.cs:217 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Morphir.Configuration.IO/ConfigurationTransaction.cs:601 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Morphir.Configuration.IO/ConfigurationTransaction.cs:603 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Morphir.Tooling/Features/Generate/GenerationPublisher.cs:71 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Morphir.Tooling/Features/Generate/GenerationPublisher.cs:72 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Morphir.Tooling/Features/TaskRecords/TaskInstaller.cs:200 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D17 · Explicit Debt · NoWarnInCsproj · ×5
  • NoWarnInCsproj build/_build.csproj:8 — CS0649 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj build/_build.csproj:8 — CS0169 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj spikes/wasm-win-x64-trap/TrapRepro.csproj:24 — IL2104 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj spikes/wasm-win-x64-trap/TrapRepro.csproj:24 — IL3053 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/Morphir.Tooling/Morphir.Tooling.csproj:8 — NU1608 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
AX3 · Project dependency cycles · Namespace dependency cycle · ×3
  • Namespace dependency cycle src/Morphir.Tooling/Features/VerifyIR/VerifyIR.cs:41 — 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.
  • Namespace dependency cycle src/Morphir.Core/IR/MorphirJson.cs:3 — 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.
  • Namespace dependency cycle src/Morphir.Tooling/Features/Extensions/ConfiguredWasmModule.cs:5 — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · WriteOnlyPrivateField · ×2
  • WriteOnlyPrivateField src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:50 — private MorphirJsonOptions _morphirJsonOptions — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Morphir.Core/IR/Codecs/TypeJsonConverter.cs:8 — private MorphirJsonOptions _morphirJsonOptions — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 147 finding(s)
AX7 · Slice cohesion · Cross-slice coupling · ×40
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileCommand.cs:106 — `CompileCommand` (slice 'Compile') depends on `RequestedTarget` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileCommand.cs:111 — `CompileCommand` (slice 'Compile') depends on `GenerateCommand` from slice 'Generate'.
  • Cross-slice coupling: Compile → Extensions src/Morphir.Tooling/Features/Compile/CompileContracts.cs:210 — `CompileSettings` (slice 'Compile') depends on `WasmModuleSource` from slice 'Extensions'.
  • Cross-slice coupling: Compile → TaskRecords src/Morphir.Tooling/Features/Compile/CompileContracts.cs:226 — `CompileSettings` (slice 'Compile') depends on `OutRoot` from slice 'TaskRecords'.
  • Cross-slice coupling: Compile → TaskRecords src/Morphir.Tooling/Features/Compile/CompileContracts.cs:228 — `CompileSettings` (slice 'Compile') depends on `MemberPath` from slice 'TaskRecords'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:19 — `CompileTarget` (slice 'Compile') depends on `RequestedTarget` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:19 — `CompileTarget` (slice 'Compile') depends on `BackendOptions` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:49 — `CompileTarget` (slice 'Compile') depends on `BackendOptionText` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:50 — `CompileTarget` (slice 'Compile') depends on `Outcome.Failure` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:71 — `CompileGeneration` (slice 'Compile') depends on `GenerationSuccess` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:80 — `CompileGenerationStages` (slice 'Compile') depends on `IGenerationBackendResolver` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:80 — `CompileGenerationStages` (slice 'Compile') depends on `IGenerationPublisher` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:84 — `CompileGenerationStages` (slice 'Compile') depends on `ModelReadLimits` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:94 — `CompileGenerationStages` (slice 'Compile') depends on `ModelInput` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:94 — `CompileGenerationStages` (slice 'Compile') depends on `InputFormat` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:95 — `CompileGenerationStages` (slice 'Compile') depends on `GenerationSettings` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:95 — `CompileGenerationStages` (slice 'Compile') depends on `PublicationPolicy` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:99 — `CompileGenerationStages` (slice 'Compile') depends on `Outcome` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:99 — `CompileGenerationStages` (slice 'Compile') depends on `GenerationSuccess` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:101 — `CompileGenerationStages` (slice 'Compile') depends on `GenerationFailure` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:101 — `CompileGenerationStages` (slice 'Compile') depends on `GenerationFailureKind` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:105 — `CompileGenerationStages` (slice 'Compile') depends on `RetainedInput.File` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:105 — `CompileGenerationStages` (slice 'Compile') depends on `RetainedEntry` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:106 — `CompileGenerationStages` (slice 'Compile') depends on `GenerationModelLoader` from slice 'Generate'.
  • Cross-slice coupling: Compile → Generate src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:109 — `CompileGenerationStages` (slice 'Compile') depends on `LoadedModel` from slice 'Generate'.
  • + 15 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×9
  • Sync-over-async blocking — 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).
  • Sync-over-async blocking build/Build.CI.cs:237 — `.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).
  • Sync-over-async blocking build/Build.CI.cs:239 — `.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).
  • Sync-over-async blocking build/Build.CI.cs:246 — `.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).
  • Sync-over-async blocking build/Build.WindowsToolchain.cs:28 — `.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).
  • Sync-over-async blocking src/Morphir.Myriad.Hosting/MyriadHost.cs:81 — `.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).
  • Sync-over-async blocking src/Morphir.Tooling/Features/Compile/CompileCommand.cs:146 — `.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).
  • Sync-over-async blocking src/Morphir.Tooling/Features/Extensions/ExtensionWorkerProcess.cs:61 — `.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).
  • Sync-over-async blocking src/Morphir.Tooling/MorphirCli.cs:308 — `.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).
D10 · Test Quality · Fixed-sleep synchronisation · ×4
  • Fixed-sleep synchronisation: SeparateNativeProcessesUseTheSameCoordinator tests/Morphir.Configuration.IO.Tests/ConfigurationTransactionTests.cs:141 — This test starts a spawned process and then orders itself against it with `Thread.Sleep(200)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: Timeout_KillsAGrandchildThatOutlivedItsParent tests/Morphir.TestSupport.Tests/ChildProcessTests.cs:44 — This test starts a spawned process and then orders itself against it with `Task.Delay(TimeSpan.FromSeconds(5))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: TimeoutStartsAfterTheGateIsHeld tests/Morphir.TestSupport.Tests/ChildProcessTests.cs:93 — This test starts a spawned process and then orders itself against it with `Task.Delay(200)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: DeadlineStopsADescendantThatOutlivedItsParent tests/Morphir.Tooling.Tests/Infrastructure/BoundedProcessTests.cs:46 — This test starts a spawned process and then orders itself against it with `Task.Delay(TimeSpan.FromSeconds(5))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4
  • Duplicated block (5 lines × 2) src/Morphir.Tooling/Scenarios/ManagementScenario.cs:189 — src/Morphir.Tooling/Scenarios/ManagementScenario.cs:189-194 | src/Morphir.Tooling/Scenarios/ManagementScenario.cs:211-215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Morphir.Tooling/Scenarios/ManagementScenario.cs:189` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 2) spikes/extension-model/jsonrpc/CurlyRpcProbe/Program.cs:65 — spikes/extension-model/jsonrpc/CurlyRpcProbe/Program.cs:65-69 | spikes/extension-model/jsonrpc/StreamJsonRpcProbe/Program.cs:72-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:95 — src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:95-99 | src/Morphir.Tooling/Features/Configuration/ConfigurationEditingCommand.cs:72-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:116 — src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:116-120 | src/Morphir.Tooling/Features/Configuration/ConfigurationEditingCommand.cs:91-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:116` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) src/Morphir.Extensions.Wasm/WasiSandbox.cs:281 — src/Morphir.Extensions.Wasm/WasiSandbox.cs:281-287 | src/Morphir.Extensions.Wasm/WasiSandbox.cs:306-312 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Morphir.Configuration.IO/ConfigurationTransaction.cs:489 — src/Morphir.Configuration.IO/ConfigurationTransaction.cs:489-495 | src/Morphir.Configuration.IO/ConfigurationTransaction.cs:524-530 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Morphir.Configuration.IO/ConfigurationTransaction.cs:489` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) src/Morphir.Tooling/Features/Generate/MepGenerationBackend.cs:129 — src/Morphir.Tooling/Features/Generate/MepGenerationBackend.cs:129-138 | src/Morphir.Tooling/Features/Generate/MepGenerationBackend.cs:155-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Morphir.Tooling/Features/Generate/MepGenerationBackend.cs:129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×3
  • Duplicated block (9 lines × 2) src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:40 — src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:40-48 | src/Morphir.Tooling/Features/Configuration/ConfigurationEditingCommand.cs:19-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (9 lines × 2) src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:155 — src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:155-163 | src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:204-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:155` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) src/Morphir.Tooling/Features/Management/ToolHandlers.cs:122 — src/Morphir.Tooling/Features/Management/ToolHandlers.cs:122-130 | src/Morphir.Tooling/Features/Management/ToolHandlers.cs:171-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Morphir.Tooling/Features/Management/ToolHandlers.cs:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×2
  • Edited copy of a member (14 corresponding lines) src/Morphir.Configuration.IO/Json5Reader.cs:101 — src/Morphir.Configuration.IO/Json5Reader.cs:101-121 | src/Morphir.Configuration.IO/Json5Reader.cs:124-137 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:414 — src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:414-427 | src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:430-445 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×2
  • Edited copy of a member (16 corresponding lines) src/Morphir.Configuration.IO/ProjectMigrationService.cs:274 — src/Morphir.Configuration.IO/ProjectMigrationService.cs:274-289 | src/Morphir.Configuration.IO/WorkspaceMigrationService.cs:433-452 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) src/Morphir.Extensions.Wasm/GuestOutput.cs:174 — src/Morphir.Extensions.Wasm/GuestOutput.cs:174-196 | src/Morphir.Tooling/Features/Extensions/WorkerReport.cs:172-187 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 15+ corresponding lines) src/Morphir.Tooling/Features/Management/DistCommands.cs:95 — src/Morphir.Tooling/Features/Management/DistCommands.cs:95-109 | src/Morphir.Tooling/Features/Management/ExtensionCommands.cs:97-115 | src/Morphir.Tooling/Features/Management/ToolCommands.cs:102-120 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) src/Morphir.Tooling/MorphirCliExtensions.cs:83 — src/Morphir.Tooling/MorphirCliExtensions.cs:83-97 | src/Morphir.Tooling/Program.cs:20-48 | src/Morphir.Tooling/Scenarios/IrToolingScenario.cs:176-192 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×2
  • Edited copy of a member (9 corresponding lines) src/Morphir.Configuration.IO/ConfigurationEditService.cs:211 — src/Morphir.Configuration.IO/ConfigurationEditService.cs:211-220 | src/Morphir.Configuration.IO/WorkspaceMigrationService.cs:515-523 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/Morphir.Configuration.IO/ProjectMigrationService.cs:296 — src/Morphir.Configuration.IO/ProjectMigrationService.cs:296-305 | src/Morphir.Configuration.IO/WorkspaceMigrationService.cs:515-523 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×2
  • Edited copy of a member (12 corresponding lines) src/Morphir.Extensions.Wasm/WasiSandbox.cs:202 — src/Morphir.Extensions.Wasm/WasiSandbox.cs:202-214 | src/Morphir.Extensions.Wasm/WasiSandbox.cs:259-270 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:35 — src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:35-46 | src/Morphir.Core/Classic/IR/Codecs/FieldJsonConverterFactory.cs:68-79 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (2 corresponding lines) · ×2
  • Edited copy of a member (2 corresponding lines) src/Morphir.Tooling/Features/Generate/CSharpGenerationBackend.cs:49 — src/Morphir.Tooling/Features/Generate/CSharpGenerationBackend.cs:49-51 | src/Morphir.Tooling/Features/Generate/FSharpGenerationBackend.cs:43-44 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) src/Morphir.Configuration.IO/ProjectMigrationService.cs:263 — src/Morphir.Configuration.IO/ProjectMigrationService.cs:263-264 | src/Morphir.Configuration.IO/WorkspaceMigrationService.cs:397-398 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) src/Morphir.Tooling/Features/Management/ExtensionCommands.cs:122 — src/Morphir.Tooling/Features/Management/ExtensionCommands.cs:122-133 | src/Morphir.Tooling/Features/Management/ExtensionCommands.cs:140-151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) src/Morphir.Tooling/Features/Management/ToolCommands.cs:127 — src/Morphir.Tooling/Features/Management/ToolCommands.cs:127-138 | src/Morphir.Tooling/Features/Management/ToolCommands.cs:145-156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2
  • Duplicated block (8 lines × 2) src/Morphir.Tooling/Scenarios/ManagementScenario.cs:67 — src/Morphir.Tooling/Scenarios/ManagementScenario.cs:67-74 | src/Morphir.Tooling/Scenarios/ManagementScenario.cs:126-133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Morphir.Tooling/Scenarios/ManagementScenario.cs:135` calls `Add` and `src/Morphir.Tooling/Scenarios/ManagementScenario.cs:76` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) src/Morphir.Tooling/Scenarios/ManagementScenario.cs:80 — src/Morphir.Tooling/Scenarios/ManagementScenario.cs:80-87 | src/Morphir.Tooling/Scenarios/ManagementScenario.cs:91-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) build/Helpers/PackagedContents.cs:79 — build/Helpers/PackagedContents.cs:79-84 | build/Helpers/PackagedEngine.cs:136-141 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `build/Helpers/PackagedContents.cs:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) src/Morphir.Myriad.Build/GenerateMorphirModules.cs:19 — src/Morphir.Myriad.Build/GenerateMorphirModules.cs:19-24 | src/Morphir.Myriad.SystemTextJson.Build/GenerateJsonContexts.cs:28-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: Morphir.Myriad.Hosting src/Morphir.Myriad.Hosting/Morphir.Myriad.Hosting.csproj:1 — Morphir.Myriad.Hosting: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: Morphir.Configuration.IO(net11.0) src/Morphir.Configuration.IO/Morphir.Configuration.IO.csproj:1 — Morphir.Configuration.IO(net11.0): abstractness 0.04, instability 0.00, distance 0.96 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
D8 · Code Coverage · No test project references BaselineProbe · ×2
  • No test project references BaselineProbe spikes/extension-model/jsonrpc/BaselineProbe/BaselineProbe.csproj — No test project in this repository references BaselineProbe (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
  • No test project references BaselineProbe spikes/extension-model/wasm-runtime/BaselineProbe/BaselineProbe.csproj — No test project in this repository references BaselineProbe (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
GD1 · Unfinished & placeholder code · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException src/Morphir.Core/IR/Codecs/TypeJsonConverter.cs:10 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Morphir.Core/IR/Codecs/TypeJsonConverter.cs:15 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
AC3 · Page structure · Text directly inside a table row · ×1
  • Text directly inside a table row openspec/changes/archive/2026-11-09-add-mep-core/design.html:239 — 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>.
AC4 · Keyboard semantics · Anchor without href · ×1
  • Anchor without href src/Morphir.Live/wwwroot/index.html:34 — 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.
AX2 · Stateful singletons · Process-global static state · ×1
  • Process-global static state: ConsoleOutputHelper src/Morphir.Tooling/Infrastructure/ConsoleOutputHelper.cs:7 — `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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (56 corresponding lines) · ×1
  • Edited copy of a member (56 corresponding lines) src/Morphir.Tooling/Scenarios/ManagementScenario.cs:54 — src/Morphir.Tooling/Scenarios/ManagementScenario.cs:54-109 | src/Morphir.Tooling/Scenarios/ManagementScenario.cs:112-175 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 54+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 54+ corresponding lines) src/Morphir.Tooling/Features/Management/DistHandlers.cs:91 — src/Morphir.Tooling/Features/Management/DistHandlers.cs:91-153 | src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:93-146 | src/Morphir.Tooling/Features/Management/ToolHandlers.cs:60-113 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 54 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) spikes/extension-model/jsonrpc/CurlyRpcProbe/Program.cs:37 — spikes/extension-model/jsonrpc/CurlyRpcProbe/Program.cs:37-60 | spikes/extension-model/jsonrpc/StreamJsonRpcProbe/Program.cs:43-67 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 43+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 43+ corresponding lines) src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:153 — src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:153-195 | src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:202-251 | src/Morphir.Tooling/Features/Management/ToolHandlers.cs:120-162 | src/Morphir.Tooling/Features/Management/ToolHandlers.cs:169-218 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×1
  • Edited copy of a member (44 corresponding lines) src/Morphir.Tooling/Features/Management/DistHandlers.cs:163 — src/Morphir.Tooling/Features/Management/DistHandlers.cs:163-206 | src/Morphir.Tooling/Features/Management/DistHandlers.cs:216-266 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 41+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 41+ corresponding lines) src/Morphir.Tooling/Features/Management/DistHandlers.cs:276 — src/Morphir.Tooling/Features/Management/DistHandlers.cs:276-316 | src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:258-298 | src/Morphir.Tooling/Features/Management/ToolHandlers.cs:225-265 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 41 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) src/Morphir.Tooling/Features/Generate/MepGenerationBackend.cs:124 — src/Morphir.Tooling/Features/Generate/MepGenerationBackend.cs:124-146 | src/Morphir.Tooling/Features/Generate/MepGenerationBackend.cs:150-169 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 34+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 34+ corresponding lines) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:152 — src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:152-193 | src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:196-229 | src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:232-274 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) src/Morphir.Tooling/Configuration/OsPaths.cs:17 — src/Morphir.Tooling/Configuration/OsPaths.cs:17-39 | src/Morphir.Tooling/Configuration/OsPaths.cs:48-70 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (38 corresponding lines) · ×1
  • Edited copy of a member (38 corresponding lines) src/Morphir.Tooling/Infrastructure/JsonSchema/SchemaValidator.cs:120 — src/Morphir.Tooling/Infrastructure/JsonSchema/SchemaValidator.cs:120-163 | src/Morphir.Tooling/Infrastructure/JsonSchema/SchemaValidator.cs:166-203 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:448 — src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:448-462 | src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:465-481 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) src/Morphir.Extensions.Wasm/WasiSandbox.cs:232 — src/Morphir.Extensions.Wasm/WasiSandbox.cs:232-241 | src/Morphir.Extensions.Wasm/WasiSandbox.cs:246-255 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) src/Morphir.Extensions.Wasm/ExtismHostFunctions.cs:96 — src/Morphir.Extensions.Wasm/ExtismHostFunctions.cs:96-107 | src/Morphir.Extensions.Wasm/ExtismHostFunctions.cs:244-249 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) src/Morphir.Tooling/Features/Configuration/ConfigurationEditingCommand.cs:34 — src/Morphir.Tooling/Features/Configuration/ConfigurationEditingCommand.cs:34-41 | src/Morphir.Tooling/Features/ProjectMigration/ProjectMigrationCommand.cs:39-45 | src/Morphir.Tooling/Features/WorkspaceMigration/WorkspaceMigrationCommand.cs:40-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 2+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 2+ corresponding lines) src/Morphir.Configuration.IO/ProjectLoading.cs:149 — src/Morphir.Configuration.IO/ProjectLoading.cs:149-151 | src/Morphir.Configuration.IO/ProjectMigrationService.cs:260-261 | src/Morphir.Configuration.IO/WorkspaceMigrationService.cs:344-345 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 2 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) build/Helpers/ReleaseProfiles.cs:152 — build/Helpers/ReleaseProfiles.cs:152-155 | src/Morphir.Extensions.Wasm/WasmAbi.cs:40-43 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 6+ corresponding lines) src/Morphir.Extensions.Wasm/GuestFailure.cs:208 — src/Morphir.Extensions.Wasm/GuestFailure.cs:208-213 | src/Morphir.Extensions.Wasm/WasmChannelFailure.cs:205-210 | src/Morphir.Tooling/Features/Extensions/WasmModuleLoader.cs:170-175 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) build/ChangelogHelper.cs:23 — build/ChangelogHelper.cs:23-48 | build/ChangelogHelper.cs:66-91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (21–22 lines × 2) · ×1
  • Duplicated block (21–22 lines × 2) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:168 — src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:168-188 | src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:365-386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:168` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:208 — src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:208-223 | src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:253-268 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:208` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:103 — src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:103-120 | src/Morphir.Tooling/Features/Management/ToolHandlers.cs:70-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (11–16 lines × 3) · ×1
  • Duplicated block (11–16 lines × 3) src/Morphir.Tooling/Features/Management/DistHandlers.cs:100 — src/Morphir.Tooling/Features/Management/DistHandlers.cs:100-115 | src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:101-111 | src/Morphir.Tooling/Features/Management/ToolHandlers.cs:68-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Morphir.Tooling/Features/Management/DistHandlers.cs:117` calls `LogInformation` and `src/Morphir.Tooling/Features/Management/ExtensionHandlers.cs:113` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) src/Morphir.Tooling/Infrastructure/JsonSchema/SchemaValidator.cs:128 — src/Morphir.Tooling/Infrastructure/JsonSchema/SchemaValidator.cs:128-143 | src/Morphir.Tooling/Infrastructure/JsonSchema/SchemaValidator.cs:174-188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Morphir.Tooling/Infrastructure/JsonSchema/SchemaValidator.cs:128` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) src/Morphir.Tooling/Features/Management/DistCommands.cs:96 — src/Morphir.Tooling/Features/Management/DistCommands.cs:96-109 | src/Morphir.Tooling/Features/Management/ExtensionCommands.cs:102-115 | src/Morphir.Tooling/Features/Management/ToolCommands.cs:107-120 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Morphir.Tooling/Features/Management/ExtensionCommands.cs:102` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) src/Morphir.Tooling/Features/Configuration/ConfigurationEditingHost.cs:50 — src/Morphir.Tooling/Features/Configuration/ConfigurationEditingHost.cs:50-60 | src/Morphir.Tooling/Features/ProjectMigration/ProjectMigrationHost.cs:28-38 | src/Morphir.Tooling/Features/WorkspaceMigration/WorkspaceMigrationHost.cs:34-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:453 — src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:453-462 | src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:472-481 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:453` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:469` calls `Write` and `src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:450` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×1
  • Duplicated block (9 lines × 5) src/Morphir.Tooling/Scenarios/ManagementScenario.cs:68 — src/Morphir.Tooling/Scenarios/ManagementScenario.cs:68-76 | src/Morphir.Tooling/Scenarios/ManagementScenario.cs:141-149 | src/Morphir.Tooling/Scenarios/ManagementScenario.cs:154-162 | src/Morphir.Tooling/Scenarios/ManagementScenario.cs:240-248 | src/Morphir.Tooling/Scenarios/ManagementScenario.cs:253-261 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (8–9 lines × 3) · ×1
  • Duplicated block (8–9 lines × 3) src/Morphir.Configuration.IO/ConfigurationEditService.cs:211 — src/Morphir.Configuration.IO/ConfigurationEditService.cs:211-219 | src/Morphir.Configuration.IO/ProjectMigrationService.cs:296-304 | src/Morphir.Configuration.IO/WorkspaceMigrationService.cs:515-522 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Morphir.Configuration.IO/ConfigurationEditService.cs:211` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) src/Morphir.Managed/Program.cs:21 — src/Morphir.Managed/Program.cs:21-34 | src/Morphir.Tool/Program.cs:20-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D5 · Coupling · Unstable project Morphir.Myriad.Build · ×1
  • Unstable project Morphir.Myriad.Build src/Morphir.Myriad.Build/Morphir.Myriad.Build.csproj:1 — Morphir.Myriad.Build has instability 1.00 with 0 dependents.
D5 · Coupling · Unstable project Morphir.Myriad.SystemTextJson.Build · ×1
  • Unstable project Morphir.Myriad.SystemTextJson.Build src/Morphir.Myriad.SystemTextJson.Build/Morphir.Myriad.SystemTextJson.Build.csproj:1 — Morphir.Myriad.SystemTextJson.Build has instability 1.00 with 0 dependents.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: Build (LCOM4 8) build/Build.cs:21 — Build's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D8 · Code Coverage · No test project references FSharpSyntaxLowering · ×1
  • No test project references FSharpSyntaxLowering spikes/FSharpSyntaxLowering/FSharpSyntaxLowering.fsproj — No test project in this repository references FSharpSyntaxLowering (3 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references TufProbe · ×1
  • No test project references TufProbe spikes/tuf-client/TufProbe/TufProbe.csproj — No test project in this repository references TufProbe (3 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references CurlyRpcProbe · ×1
  • No test project references CurlyRpcProbe spikes/extension-model/jsonrpc/CurlyRpcProbe/CurlyRpcProbe.csproj — No test project in this repository references CurlyRpcProbe (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references ExtismProbe · ×1
  • No test project references ExtismProbe spikes/extension-model/wasm-runtime/ExtismProbe/ExtismProbe.csproj — No test project in this repository references ExtismProbe (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references FSharpMatchJoin · ×1
  • No test project references FSharpMatchJoin spikes/FSharpMatchJoin/FSharpMatchJoin.fsproj — No test project in this repository references FSharpMatchJoin (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references MorphirGuestProbe · ×1
  • No test project references MorphirGuestProbe spikes/extension-model/dotnet-guest-toolchains/csharp-naot-llvm/MorphirGuestProbe.csproj — No test project in this repository references MorphirGuestProbe (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references MorphirGuestProbeFs · ×1
  • No test project references MorphirGuestProbeFs spikes/extension-model/dotnet-guest-toolchains/fsharp-naot-llvm/MorphirGuestProbeFs.fsproj — No test project in this repository references MorphirGuestProbeFs (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references NuGetProbe · ×1
  • No test project references NuGetProbe spikes/nuget-extension-source/NuGetProbe/NuGetProbe.fsproj — No test project in this repository references NuGetProbe (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references PlatformProbe · ×1
  • No test project references PlatformProbe spikes/extension-model/tool-platform-packages/PlatformProbe/PlatformProbe.csproj — No test project in this repository references PlatformProbe (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references RoslynAotProbe · ×1
  • No test project references RoslynAotProbe spikes/extension-model/roslyn-aot/RoslynAotProbe.csproj — No test project in this repository references RoslynAotProbe (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references StreamJsonRpcProbe · ×1
  • No test project references StreamJsonRpcProbe spikes/extension-model/jsonrpc/StreamJsonRpcProbe/StreamJsonRpcProbe.csproj — No test project in this repository references StreamJsonRpcProbe (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references TrapRepro · ×1
  • No test project references TrapRepro spikes/wasm-win-x64-trap/TrapRepro.csproj — No test project in this repository references TrapRepro (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references WacsProbe · ×1
  • No test project references WacsProbe spikes/extension-model/wasm-runtime/WacsProbe/WacsProbe.csproj — No test project in this repository references WacsProbe (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references WasmtimeProbe · ×1
  • No test project references WasmtimeProbe spikes/extension-model/wasm-runtime/WasmtimeProbe/WasmtimeProbe.csproj — No test project in this repository references WasmtimeProbe (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 86.2% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience build/Build.CI.cs:217 — `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.
Minor — 74 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate build/Build.MorphirProbe.cs:66 — `!TargetPlatform.TryParse(Rid, out var platform) || platform is null` appears character-identically in 3 files — build/Build.MorphirProbe.cs, build/Build.Morphirup.cs, build/Build.ReleaseProfiles.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Tooling/Features/Generate/CSharpGenerationBackend.cs:54 — `!request.Target.Equals(Descriptor.Target) || request.Options is not Options options` appears character-identically in 2 files — src/Morphir.Tooling/Features/Generate/CSharpGenerationBackend.cs, src/Morphir.Tooling/Features/Generate/FSharpGenerationBackend.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate build/Build.MorphirProbe.cs:208 — `char.IsLetterOrDigit(c) || c is '-' or '.'` appears character-identically in 2 files — build/Build.MorphirProbe.cs, build/Build.NativeCheck.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Configuration.IO/ConfigurationEditService.cs:173 — `entry is ProjectEntry.File && before.Kind == ConfigurationObservationKind.File` appears character-identically in 2 files — src/Morphir.Configuration.IO/ConfigurationEditService.cs, src/Morphir.Configuration.IO/ProjectMigrationService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Configuration.IO/ProjectMigrationService.cs:135 — `f.RawPath.Any() && f.Disposition == "normalized"` appears character-identically in 2 files — src/Morphir.Configuration.IO/ProjectMigrationService.cs, src/Morphir.Configuration.IO/WorkspaceMigrationService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Ion/Ir/TreeStems.fs:37 — `(c >= '0' && c <= '9') || (c >= 'a' && c <= 'f')` appears character-identically in 2 files — src/Morphir.Ion/Ir/TreeStems.fs, src/Morphir.Toolchain/TufMetadata.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Ion/Ir/TreeStems.fs:31 — `(c >= 'a' && c <= 'z') || (c >= '0' && c <= '9')` appears character-identically in 3 files — src/Morphir.Ion/Ir/TreeStems.fs, src/Morphir.Models/Json/V4/V4JsonValues.fs, src/Morphir.Models/Json/V4/V4JsonWriter.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Ion/IonReader.fs:210 — `bytes.Length >= 4 && bytes.Span.Slice(0, 4).SequenceEqual(ReadOnlySpan<byte> binaryMarker)` appears character-identically in 3 files — src/Morphir.Ion/IonReader.fs, src/Morphir.Ion/Ir/IonSources.fs, src/Morphir.Ion/ModelDocument.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Models/Json/Codecs/NameCodec.fs:64 — `error.IsNone && reader.Read() && reader.TokenType <> JsonTokenType.EndArray` appears character-identically in 2 files — src/Morphir.Models/Json/Codecs/NameCodec.fs, src/Morphir.Models/Json/Codecs/PathCodec.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Extensions/Text.fs:46 — `first.StartsWith("com", StringComparison.Ordinal) || first.StartsWith("lpt", StringComparison.Ordinal)` appears character-identically in 2 files — src/Morphir.Extensions/Text.fs, src/Morphir.Toolchain/Primitives.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Models/Json/Codecs/FQNameCodec.fs:64 — `if not (reader.Read()) || reader.TokenType <> JsonTokenType.EndArray` appears character-identically in 2 files — src/Morphir.Models/Json/Codecs/FQNameCodec.fs, src/Morphir.Models/Json/Codecs/LiteralCodec.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Models/Json/V4/V4JsonValues.fs:134 — `input.Length > 0 && input[0] >= 'a' && input[0] <= 'z' && input.Split('-')` appears character-identically in 2 files — src/Morphir.Models/Json/V4/V4JsonValues.fs, src/Morphir.Models/Json/V4/V4JsonWriter.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Extensions.Installation/Archives.fs:1262 — `not directory && entry.EntryType <> TarEntryType.RegularFile && entry.EntryType <> TarEntryType.V7RegularFile` appears character-identically in 2 files — src/Morphir.Extensions.Installation/Archives.fs, src/Morphirup/LocalInstallation.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Conformance/GuestKit/Kit.fs:107 — `segment <> "" && segment <> "." && segment <> ".."` appears character-identically in 2 files — src/Morphir.Conformance/GuestKit/Kit.fs, src/Morphir.IR.Pipeline/FileTree.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Toolchain.IO/WindowsProcess.fs:585 — `start.UseShellExecute || not start.RedirectStandardOutput || not start.RedirectStandardError` appears character-identically in 2 files — src/Morphir.Toolchain.IO/WindowsProcess.fs, src/Morphirup/LocalProcess.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Frontend.FSharp/Lowering.fs:75 — `typ.IsTupleType && not typ.IsStructTupleType` appears character-identically in 2 files — src/Morphir.Frontend.FSharp/Lowering.fs, src/Morphir.Frontend.FSharp/SdkMapping.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Ion/Ir/V4IonTypes.fs:27 — `value.Coefficient.Sign < 0 || (value.Coefficient.IsZero && value.IsNegativeZero)` appears character-identically in 2 files — src/Morphir.Ion/Ir/V4IonTypes.fs, src/Morphir.Ion/IrProjection.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Myriad.Build/GenerateMorphirModules.cs:71 — `message.Severity.IsError || message.Severity.IsFatal` appears character-identically in 2 files — src/Morphir.Myriad.Build/GenerateMorphirModules.cs, src/Morphir.Tooling/Features/Generate/FSharpGenerationBackend.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Tooling/Features/Management/DistCommands.cs:107 — `platform == null || Infrastructure.RuntimeIdentifier.IsValidRid(platform)` appears character-identically in 3 files — src/Morphir.Tooling/Features/Management/DistCommands.cs, src/Morphir.Tooling/Features/Management/ExtensionCommands.cs, src/Morphir.Tooling/Features/Management/ToolCommands.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:176 — `reader.Read() && reader.TokenType != JsonTokenType.EndArray` appears character-identically in 3 files — src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs, src/Morphir.Core/IR/Codecs/DocumentJsonConverter.cs, src/Morphir.Core/IR/Codecs/PathJsonConverter.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs:88 — `reader.Read() && reader.TokenType == JsonTokenType.String` appears character-identically in 2 files — src/Morphir.Core/Classic/IR/Codecs/ClassicTypeJsonConverterFactory.cs, src/Morphir.Core/IR/Codecs/NameConverter.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Tooling/Features/Compile/CompileReport.cs:157 — `relative.StartsWith("..", StringComparison.Ordinal) || Path.IsPathRooted(relative)` appears character-identically in 2 files — src/Morphir.Tooling/Features/Compile/CompileReport.cs, src/Morphir.Tooling/Features/Compile/SourceSelector.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Configuration.IO/ConfigurationEditService.cs:180 — `storage.Observe(path) != before || evidence.TryGetValue(path, out var prior) && prior != before` appears character-identically in 2 files — src/Morphir.Configuration.IO/ConfigurationEditService.cs, src/Morphir.Configuration.IO/ProjectMigrationService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Configuration.IO/ConfigurationEditService.cs:107 — `targetEntry.IsLink || targetEntry.IsDirectory || targetEntry.IsFailure` appears character-identically in 2 files — src/Morphir.Configuration.IO/ConfigurationEditService.cs, src/Morphir.Configuration.IO/ProjectMigrationService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs:80 — `value is not null && string.IsNullOrWhiteSpace(value)` appears character-identically in 3 files — src/Morphir.Tooling/Features/Configuration/ConfigurationCommand.cs, src/Morphir.Tooling/Features/Configuration/ConfigurationEditingCommand.cs, src/Morphir.Tooling/Features/ProjectMigration/ProjectMigrationCommand.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D34 · Knowledge Freshness · Orphaned file · ×12
  • Orphaned file src/Morphir.Tooling/Features/Management/DistHandlers.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Morphir.Live/Pages/TryMorphir.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Morphir.Tooling/Features/Management/ToolHandlers.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Morphir.Tooling/Features/Management/ArtifactPathResolver.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Morphir.SDK.FSharp/String.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Morphir.SDK.FSharp/List.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Morphir.Tooling/Features/Management/ToolCommands.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Morphir.Tooling/Features/Management/DistCommands.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Morphir.SDK.FSharp/Dict.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Morphir.Tooling/Configuration/OsPaths.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Morphir.SDK.FSharp/Result.fs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Morphir.Tooling/Features/Management/Manifest.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
X7 · Silent fallback defaults · Silent fallback default in catch · ×9
  • Silent fallback default in catch build/Helpers/PathHelper.cs:192 — `TryParseVersionFromFilename` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch build/Helpers/PublishedLayout.cs:89 — `ReferencesSharedFramework` swallows `JsonException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch build/Helpers/PublishedLayout.cs:104 — `IsManagedAssembly` swallows `BadImageFormatException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/Morphir.Configuration.IO/ConfigurationTransaction.cs:447 — `TryCleanup` swallows `Exception` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/Morphir.Configuration.IO/ConfigurationTransaction.cs:472 — `Retained` swallows `Exception` into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/Morphir.Configuration.IO/FileSystemProjectTree.cs:55 — `Observe` swallows `FileNotFoundException` into `return ProjectEntry.Missing;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/Morphir.Tooling/Features/VerifyIR/VersionDetector.cs:39 — `DetectVersion` swallows `JsonException` into `return "3";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch spikes/extension-model/dotnet-guest-toolchains/csharp-naot-llvm/Guest.cs:71 — `Handle` swallows every exception into `return -1;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch spikes/wasm-win-x64-trap/Program.cs:116 — `Print` swallows `EntryPointNotFoundException` and sets `available = "unknown (no IsUserCetAvailableInEnvironment)";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
D24 · Comment Value · redundant comment · ×8
  • redundant comment src/Morphir.Tooling/Features/Extensions/BackendExtensionSource.cs:22 — "Each capability has at least one version and a descriptor has at least one capability." repeats the code it sits on: 3 of its 3 words (capability, version, descriptor) are already in `var versions = descriptor.Capabilities.SelectMany(capability => capability.Versions).ToArray();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Morphir.Tooling/Features/VerifyIR/VersionDetector.cs:21 — "Try to get the formatVersion field" repeats the code it sits on: 4 of its 5 words (try, get, format, version) are already in `if (root.TryGetProperty("formatVersion", out var formatVersionElement))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/Morphir.Build.Tests/Helpers/BlackBoxRulesTests.cs:98 — "Framework tests have one group." repeats the code it sits on: 3 of its 3 words (framework, tests, group) are already in `private const string FrameworkSource = """`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/Morphir.Build.Tests/Helpers/BlackBoxRulesTests.cs:166 — "No assembly from src/ is visible." repeats the code it sits on: 4 of its 4 words (no, assembly, src, visible) are already in `[Test]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/Morphir.Build.Tests/Helpers/PackageValidatorTests.cs:49 — "Arrange - Test with Morphir.Core package" repeats the code it sits on: 4 of its 5 words (test, morphir, core, package) are already in `var package = TestFixture.FindLatestPackage("Morphir.Core.*.nupkg");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/Morphir.Core.Tests/Classic/IR/TypeMorphirJsonEncodingTests.cs:336 — "ExtensibleRecord with variable "r" and field name: String" repeats the code it sits on: 5 of its 6 words (extensible, record, variable, name, string) are already in `var variableName = Name.FromString("r");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/Morphir.Core.Tests/Classic/IR/TypeMorphirJsonEncodingTests.cs:368 — "Function type: Unit -> Unit" repeats the code it sits on: 3 of its 3 words (function, type, unit) are already in `var paramType = Type.Unit(Unit.Default);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/Morphir.TestSupport.Tests/Drivers/TestEligibilityTests.cs:168 — "The lane and the host both fail: the reason is the lane." repeats the code it sits on: 4 of its 4 words (lane, host, fail, reason) are already in `var laneAndHost = Skipped(TestEligibility.Decide(Needs("lane", "packages", "host-managed"), Run(TestLane.None, NativeAot …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
M4 · Documentation accuracy · README/code drift · ×5
  • README/code drift CONTRIBUTING.md:114 — 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.
  • README/code drift README.md:149 — 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/code drift tests/Morphir.Configuration.IO.Smoke/README.md:69 — 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.
  • README/code drift docs/content/contributing/design/prds/introduce-fsharp-sdk-package.md:204 — 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.
  • README/code drift docs/content/contributing/design/spikes/extension-model/dotnet-guest-toolchains.md:30 — 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.
D31 · IaC & Container Security · Low IaC · ×2
  • REDACTED
  • REDACTED
X7 · Silent fallback defaults · Silent fallback default on unknown code · ×2
  • Silent fallback default on unknown code src/Morphir.Configuration.IO/ProjectLoading.cs:158 — `FormatOf` maps every unrecognised code to `DocumentFormat.Memory`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
  • Silent fallback default on unknown code src/Morphir.Tooling/Features/Compile/CompileGeneration.cs:204 — `Convert` maps every unrecognised code to `Severity.Error`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×2
  • Silent fallback default on parse failure src/Morphir.Tooling/Features/Compile/CompileCommand.cs:190 — `Summary` falls back to `""` when `report.Generation is { Backend: { } backend } generation && report.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure spikes/extension-model/jsonrpc/RawWire.cs:106 — `RunAll` falls back to `"(none)"` when `root.TryGetProperty("id", out var id)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
D20 · ADR Quality · ADR has no Decision section · ×1
  • ADR has no Decision section docs/adr/0001-morphir-dotnet-default-cli-and-conformance-oracle.md:6 — docs/adr/0001-morphir-dotnet-default-cli-and-conformance-oracle.md has no Decision section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion src/Morphir.Tooling/Morphir.Tooling.csproj:1 — `Morphir.Tooling(net11.0)` overshoots its size bounds (13212 LoC, 369 public types across 17 namespaces). 1 of 52 project(s) overshoot their size bounds, lowering Project Cohesion to 9.6/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 12 of 400 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 400 of the 527 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/Morphir.Tooling/Features/Management/DistHandlers.cs, src/Morphir.Live/Pages/TryMorphir.fs, src/Morphir.Tooling/Features/Management/ToolHandlers.cs, src/Morphir.Tooling/Features/Management/ArtifactPathResolver.cs, src/Morphir.SDK.FSharp/String.fs, src/Morphir.SDK.FSharp/List.fs, src/Morphir.Tooling/Features/Management/ToolCommands.cs, src/Morphir.Tooling/Features/Management/DistCommands.cs (and 4 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
P12 · CI test-gate honesty · Sleep-based test synchronization · ×1
  • Sleep-based test synchronization — 14 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:15 — 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.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions override nullable warnings · ×1
  • Null-forgiving operator (`!`) suppressions override nullable warnings — ~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.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×1
  • Hand-rolled JSON/XML parsing via regex build/Build.MorphirProbe.cs:366 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Minor — 8 finding(s)
D24 · Comment Value · doc comments repeat the names · ×8
  • doc comments repeat the names tests/Morphir.Build.Tests/Helpers/PathHelperTests.cs:7 — 0 of 1 documented parameters and 1 of 44 summaries in `Morphir.Build.Tests` only repeat the member or parameter name (e.g. "Tests for PathHelper helper class" for `PathHelperTests`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Morphir.Core/IR/Path.cs:29 — 1 of 54 documented parameters and 0 of 88 summaries in `Morphir.Core(net11.0)` only repeat the member or parameter name (e.g. "the path" for `path`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Morphir.Extensions.Wasm/WasmChannelFailure.cs:83 — 5 of 87 documented parameters and 0 of 309 summaries in `Morphir.Extensions.Wasm(net11.0)` only repeat the member or parameter name (e.g. "What returned." for `ReturnCode`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names tests/Morphir.Extensions.Wasm.Tests/CraftedCorpus.cs:305 — 0 of 14 documented parameters and 2 of 103 summaries in `Morphir.Extensions.Wasm.Tests` only repeat the member or parameter name (e.g. "The of the frame ." for `FrameMethod`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Morphir.Myriad.SystemTextJson.Build/GenerateJsonContexts.cs:24 — 0 of 0 documented parameters and 2 of 13 summaries in `Morphir.Myriad.SystemTextJson.Build` only repeat the member or parameter name (e.g. "The project directory." for `ProjectDirectory`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names tests/Morphir.TestSupport/Drivers/ExtensionDriver.cs:9 — 0 of 43 documented parameters and 14 of 728 summaries in `Morphir.TestSupport` only repeat the member or parameter name (e.g. "The options of ." for `ExtensionListOptions`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Morphir.Tooling/Features/Compile/CompileContracts.cs:181 — 2 of 132 documented parameters and 20 of 903 summaries in `Morphir.Tooling(net11.0)` only repeat the member or parameter name (e.g. "One project file, from or ." for `ProjectFile`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names tests/Morphir.Tooling.Tests/Features/Compile/CompileWorkspace.cs:16 — 0 of 6 documented parameters and 2 of 190 summaries in `Morphir.Tooling.Tests` only repeat the member or parameter name (e.g. "A path under ." for `PathOf`). Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw 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 .0artifacts/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 .0artifacts/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 tests136artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list Morphir.slnx package --vulnerable --include-transitive --format json0artifacts/raw/dotnet-vulnerable.json
D30 · Dependency Vulnerabilitiesosv-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-853ac0d10d5c44b29f688c62cfd8dc270artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .2artifacts/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 Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciesosv-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-853ac0d10d5c44b29f688c62cfd8dc270artifacts/raw/osv-scanner.json
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1df24-3f6f-7caf-8a96-3e770925f86d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md