Executive summary
Neftedollar/FsMcp meets our standard for production, though we found no automated security scanning of the code, its secrets or its dependencies. It scores 74 out of 100 and is rated Strong, and it has no critical findings.
Production Readiness, at 56, is the weakest lens and counts most in the score. The best first step is updating the outdated dependencies, worth about 12 points. Adding a release approval would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 80.
Most of the 16 serious findings are in Code Health.
The product code is 4,919 lines, about €17,000 to rebuild.
If Production Readiness rose from 56 to 70, the lowest score rated Strong, the score would rise from 74 to about 80.
Fixed since the last survey: 9 findings
- Cyclomatic Complexity · verify-npm-audit.validateAudit (cyclomatic 50) scripts/verify-npm-audit.mjs
- Cyclomatic Complexity · verify-release.verify_package (cyclomatic 25) scripts/verify-release.py
- Cognitive Complexity · verify-npm-audit.validateAudit (cognitive 74) scripts/verify-npm-audit.mjs
- Cognitive Complexity · verify-nuget-audit.vulnerabilities (cognitive 30) scripts/verify-nuget-audit.py
- Cognitive Complexity · verify-release.verify_package (cognitive 24) scripts/verify-release.py
- Cognitive Complexity · verify-npm-audit.validateDependencyPolicy (cognitive 16) scripts/verify-npm-audit.mjs
- God Classes · FunctionTooLong: verify-npm-audit.runNegativeSelfTests scripts/verify-npm-audit.mjs
- God Classes · FileTooLong: scripts/verify-npm-audit.mjs scripts/verify-npm-audit.mjs
- Code Duplication · Duplicated block (11 lines × 2) src/FsMcp.Server/TypedHandlers.fs
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,600 to €28,000, for 94 to 297 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.1 at a score of 74. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 4,919 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Core.Validation | 2 Core | 3 Client | 4 Core.ContentModule | 5 Core.Interop | 6 Core.ResultExtensions | 7 Core.Serialization | 8 Core.Validation.MimeTypeModule | 9 Core.Validation.PromptNameModule | 10 Core.Validation.ResourceUriModule | 11 Core.Validation.ServerNameModule | 12 Core.Validation.ServerVersionModule | 13 Core.Validation.ToolNameModule | 14 Core.ValidationErrorModule | 15 Sampling | 16 Server | 17 Server.Notifications | 18 Testing | 19 Testing.McpArbitraries | 20 Client.ClientTransportModule | 21 Client.EnterpriseAuthorizationEndpoint | 22 Client.EnterpriseAuthorizationValidation | 23 Client.EnterpriseIdentityProviderModule | 24 Client.EnterpriseManagedAuthorizationEndpointPolicy | 25 Client.EnterpriseManagedAuthorizationFailureModule | 26 Client.EnterpriseManagedAuthorizationModule | 27 Client.EnterpriseManagedAuthorizationOptionsModule | 28 Client.EnterprisePlaintextEndpointAllowanceModule | 29 Client.EnterpriseRequestReplay | 30 Client.McpClientAsync | 31 Client.McpClientModule | 32 Sampling.SamplingTool | 33 Server.DynamicServer | 34 Server.Notifications.ContextualTool | 35 Server.ResourceSubscriptions | 36 Server.Server | 37 Server.ServerConfigModule | 38 Server.ValidationMiddleware | 39 TaskApi.ClientPipeline | 40 Testing.TestServer |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Core.Validation | ||||||||||||||||||||||||||||||||||||||||
| 2 Core | 10 | |||||||||||||||||||||||||||||||||||||||
| 3 Client | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 Core.ContentModule | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 5 Core.Interop | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 Core.ResultExtensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 Core.Serialization | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 Core.Validation.MimeTypeModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 Core.Validation.PromptNameModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 Core.Validation.ResourceUriModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 Core.Validation.ServerNameModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 Core.Validation.ServerVersionModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 Core.Validation.ToolNameModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 Core.ValidationErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Sampling | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 Server | 5 | 11 | ||||||||||||||||||||||||||||||||||||||
| 17 Server.Notifications | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Testing | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Testing.McpArbitraries | 8 | 7 | ||||||||||||||||||||||||||||||||||||||
| 20 Client.ClientTransportModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 Client.EnterpriseAuthorizationEndpoint | 3 | |||||||||||||||||||||||||||||||||||||||
| 22 Client.EnterpriseAuthorizationValidation | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Client.EnterpriseIdentityProviderModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 Client.EnterpriseManagedAuthorizationEndpointPolicy | 3 | |||||||||||||||||||||||||||||||||||||||
| 25 Client.EnterpriseManagedAuthorizationFailureModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Client.EnterpriseManagedAuthorizationModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 Client.EnterpriseManagedAuthorizationOptionsModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 28 Client.EnterprisePlaintextEndpointAllowanceModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 Client.EnterpriseRequestReplay | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 Client.McpClientAsync | 3 | 4 | 7 | |||||||||||||||||||||||||||||||||||||
| 31 Client.McpClientModule | 3 | 5 | 8 | |||||||||||||||||||||||||||||||||||||
| 32 Sampling.SamplingTool | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 33 Server.DynamicServer | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 34 Server.Notifications.ContextualTool | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 Server.ResourceSubscriptions | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 36 Server.Server | 1 | 8 | 3 | |||||||||||||||||||||||||||||||||||||
| 37 Server.ServerConfigModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 Server.ValidationMiddleware | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 39 TaskApi.ClientPipeline | 4 | 7 | ||||||||||||||||||||||||||||||||||||||
| 40 Testing.TestServer | 4 | 1 | 3 |
2→1 Core uses Core.Validation✕
- Connections
- 10 pairs of types, where a type in Core uses a type in Core.Validation.
- The types involved
FsMcp.Core.Content→FsMcp.Core.Validation.MimeTypeFsMcp.Core.McpError→FsMcp.Core.Validation.PromptNameFsMcp.Core.McpError→FsMcp.Core.Validation.ResourceUriFsMcp.Core.McpError→FsMcp.Core.Validation.ToolNameFsMcp.Core.PromptDefinition→FsMcp.Core.Validation.PromptNameFsMcp.Core.ResourceContents→FsMcp.Core.Validation.MimeTypeFsMcp.Core.ResourceContents→FsMcp.Core.Validation.ResourceUriFsMcp.Core.ResourceDefinition→FsMcp.Core.Validation.MimeTypeFsMcp.Core.ResourceDefinition→FsMcp.Core.Validation.ResourceUriFsMcp.Core.ToolDefinition→FsMcp.Core.Validation.ToolName
- Direction
- Core uses Core.Validation, so a change to Core.Validation can break Core, while a change to Core can't break Core.Validation.
- Position
- Below the diagonal: Core uses a module listed above it, which is the healthy direction.
3→2 Client uses Core✕
- Connections
- 1 pair of types, where a type in Client uses a type in Core.
- The types involved
FsMcp.Client.PromptDetails→FsMcp.Core.PromptArgument
- Direction
- Client uses Core, so a change to Core can break Client, while a change to Client can't break Core.
- Position
- Below the diagonal: Client uses a module listed above it, which is the healthy direction.
4→1 Core.ContentModule uses Core.Validation✕
- Connections
- 1 pair of types, where a type in Core.ContentModule uses a type in Core.Validation.
- The types involved
FsMcp.Core.ContentModule.ContentModule→FsMcp.Core.Validation.MimeType
- Direction
- Core.ContentModule uses Core.Validation, so a change to Core.Validation can break Core.ContentModule, while a change to Core.ContentModule can't break Core.Validation.
- Position
- Below the diagonal: Core.ContentModule uses a module listed above it, which is the healthy direction.
4→2 Core.ContentModule uses Core✕
- Connections
- 2 pairs of types, where a type in Core.ContentModule uses a type in Core.
- The types involved
FsMcp.Core.ContentModule.ContentModule→FsMcp.Core.ContentFsMcp.Core.ContentModule.ContentModule→FsMcp.Core.ResourceContents
- Direction
- Core.ContentModule uses Core, so a change to Core can break Core.ContentModule, while a change to Core.ContentModule can't break Core.
- Position
- Below the diagonal: Core.ContentModule uses a module listed above it, which is the healthy direction.
5→2 Core.Interop uses Core✕
- Connections
- 2 pairs of types, where a type in Core.Interop uses a type in Core.
- The types involved
FsMcp.Core.Interop.Interop→FsMcp.Core.ContentFsMcp.Core.Interop.Interop→FsMcp.Core.McpRole
- Direction
- Core.Interop uses Core, so a change to Core can break Core.Interop, while a change to Core.Interop can't break Core.
- Position
- Below the diagonal: Core.Interop uses a module listed above it, which is the healthy direction.
6→2 Core.ResultExtensions uses Core✕
- Connections
- 1 pair of types, where a type in Core.ResultExtensions uses a type in Core.
- The types involved
FsMcp.Core.ResultExtensions.ResultExtensions→FsMcp.Core.ValidationError
- Direction
- Core.ResultExtensions uses Core, so a change to Core can break Core.ResultExtensions, while a change to Core.ResultExtensions can't break Core.
- Position
- Below the diagonal: Core.ResultExtensions uses a module listed above it, which is the healthy direction.
7→2 Core.Serialization uses Core✕
- Connections
- 2 pairs of types, where a type in Core.Serialization uses a type in Core.
- The types involved
FsMcp.Core.Serialization.ContentConverter→FsMcp.Core.ContentFsMcp.Core.Serialization.ResourceContentsConverter→FsMcp.Core.ResourceContents
- Direction
- Core.Serialization uses Core, so a change to Core can break Core.Serialization, while a change to Core.Serialization can't break Core.
- Position
- Below the diagonal: Core.Serialization uses a module listed above it, which is the healthy direction.
8→1 Core.Validation.MimeTypeModule uses Core.Validation✕
- Connections
- 1 pair of types, where a type in Core.Validation.MimeTypeModule uses a type in Core.Validation.
- The types involved
FsMcp.Core.Validation.MimeTypeModule.MimeTypeModule→FsMcp.Core.Validation.MimeType
- Direction
- Core.Validation.MimeTypeModule uses Core.Validation, so a change to Core.Validation can break Core.Validation.MimeTypeModule, while a change to Core.Validation.MimeTypeModule can't break Core.Validation.
- Position
- Below the diagonal: Core.Validation.MimeTypeModule uses a module listed above it, which is the healthy direction.
8→2 Core.Validation.MimeTypeModule uses Core✕
- Connections
- 1 pair of types, where a type in Core.Validation.MimeTypeModule uses a type in Core.
- The types involved
FsMcp.Core.Validation.MimeTypeModule.MimeTypeModule→FsMcp.Core.ValidationError
- Direction
- Core.Validation.MimeTypeModule uses Core, so a change to Core can break Core.Validation.MimeTypeModule, while a change to Core.Validation.MimeTypeModule can't break Core.
- Position
- Below the diagonal: Core.Validation.MimeTypeModule uses a module listed above it, which is the healthy direction.
9→1 Core.Validation.PromptNameModule uses Core.Validation✕
- Connections
- 1 pair of types, where a type in Core.Validation.PromptNameModule uses a type in Core.Validation.
- The types involved
FsMcp.Core.Validation.PromptNameModule.PromptNameModule→FsMcp.Core.Validation.PromptName
- Direction
- Core.Validation.PromptNameModule uses Core.Validation, so a change to Core.Validation can break Core.Validation.PromptNameModule, while a change to Core.Validation.PromptNameModule can't break Core.Validation.
- Position
- Below the diagonal: Core.Validation.PromptNameModule uses a module listed above it, which is the healthy direction.
9→2 Core.Validation.PromptNameModule uses Core✕
- Connections
- 1 pair of types, where a type in Core.Validation.PromptNameModule uses a type in Core.
- The types involved
FsMcp.Core.Validation.PromptNameModule.PromptNameModule→FsMcp.Core.ValidationError
- Direction
- Core.Validation.PromptNameModule uses Core, so a change to Core can break Core.Validation.PromptNameModule, while a change to Core.Validation.PromptNameModule can't break Core.
- Position
- Below the diagonal: Core.Validation.PromptNameModule uses a module listed above it, which is the healthy direction.
10→1 Core.Validation.ResourceUriModule uses Core.Validation✕
- Connections
- 1 pair of types, where a type in Core.Validation.ResourceUriModule uses a type in Core.Validation.
- The types involved
FsMcp.Core.Validation.ResourceUriModule.ResourceUriModule→FsMcp.Core.Validation.ResourceUri
- Direction
- Core.Validation.ResourceUriModule uses Core.Validation, so a change to Core.Validation can break Core.Validation.ResourceUriModule, while a change to Core.Validation.ResourceUriModule can't break Core.Validation.
- Position
- Below the diagonal: Core.Validation.ResourceUriModule uses a module listed above it, which is the healthy direction.
10→2 Core.Validation.ResourceUriModule uses Core✕
- Connections
- 1 pair of types, where a type in Core.Validation.ResourceUriModule uses a type in Core.
- The types involved
FsMcp.Core.Validation.ResourceUriModule.ResourceUriModule→FsMcp.Core.ValidationError
- Direction
- Core.Validation.ResourceUriModule uses Core, so a change to Core can break Core.Validation.ResourceUriModule, while a change to Core.Validation.ResourceUriModule can't break Core.
- Position
- Below the diagonal: Core.Validation.ResourceUriModule uses a module listed above it, which is the healthy direction.
11→1 Core.Validation.ServerNameModule uses Core.Validation✕
- Connections
- 1 pair of types, where a type in Core.Validation.ServerNameModule uses a type in Core.Validation.
- The types involved
FsMcp.Core.Validation.ServerNameModule.ServerNameModule→FsMcp.Core.Validation.ServerName
- Direction
- Core.Validation.ServerNameModule uses Core.Validation, so a change to Core.Validation can break Core.Validation.ServerNameModule, while a change to Core.Validation.ServerNameModule can't break Core.Validation.
- Position
- Below the diagonal: Core.Validation.ServerNameModule uses a module listed above it, which is the healthy direction.
11→2 Core.Validation.ServerNameModule uses Core✕
- Connections
- 1 pair of types, where a type in Core.Validation.ServerNameModule uses a type in Core.
- The types involved
FsMcp.Core.Validation.ServerNameModule.ServerNameModule→FsMcp.Core.ValidationError
- Direction
- Core.Validation.ServerNameModule uses Core, so a change to Core can break Core.Validation.ServerNameModule, while a change to Core.Validation.ServerNameModule can't break Core.
- Position
- Below the diagonal: Core.Validation.ServerNameModule uses a module listed above it, which is the healthy direction.
12→1 Core.Validation.ServerVersionModule uses Core.Validation✕
- Connections
- 1 pair of types, where a type in Core.Validation.ServerVersionModule uses a type in Core.Validation.
- The types involved
FsMcp.Core.Validation.ServerVersionModule.ServerVersionModule→FsMcp.Core.Validation.ServerVersion
- Direction
- Core.Validation.ServerVersionModule uses Core.Validation, so a change to Core.Validation can break Core.Validation.ServerVersionModule, while a change to Core.Validation.ServerVersionModule can't break Core.Validation.
- Position
- Below the diagonal: Core.Validation.ServerVersionModule uses a module listed above it, which is the healthy direction.
12→2 Core.Validation.ServerVersionModule uses Core✕
- Connections
- 1 pair of types, where a type in Core.Validation.ServerVersionModule uses a type in Core.
- The types involved
FsMcp.Core.Validation.ServerVersionModule.ServerVersionModule→FsMcp.Core.ValidationError
- Direction
- Core.Validation.ServerVersionModule uses Core, so a change to Core can break Core.Validation.ServerVersionModule, while a change to Core.Validation.ServerVersionModule can't break Core.
- Position
- Below the diagonal: Core.Validation.ServerVersionModule uses a module listed above it, which is the healthy direction.
13→1 Core.Validation.ToolNameModule uses Core.Validation✕
- Connections
- 1 pair of types, where a type in Core.Validation.ToolNameModule uses a type in Core.Validation.
- The types involved
FsMcp.Core.Validation.ToolNameModule.ToolNameModule→FsMcp.Core.Validation.ToolName
- Direction
- Core.Validation.ToolNameModule uses Core.Validation, so a change to Core.Validation can break Core.Validation.ToolNameModule, while a change to Core.Validation.ToolNameModule can't break Core.Validation.
- Position
- Below the diagonal: Core.Validation.ToolNameModule uses a module listed above it, which is the healthy direction.
13→2 Core.Validation.ToolNameModule uses Core✕
- Connections
- 1 pair of types, where a type in Core.Validation.ToolNameModule uses a type in Core.
- The types involved
FsMcp.Core.Validation.ToolNameModule.ToolNameModule→FsMcp.Core.ValidationError
- Direction
- Core.Validation.ToolNameModule uses Core, so a change to Core can break Core.Validation.ToolNameModule, while a change to Core.Validation.ToolNameModule can't break Core.
- Position
- Below the diagonal: Core.Validation.ToolNameModule uses a module listed above it, which is the healthy direction.
14→2 Core.ValidationErrorModule uses Core✕
- Connections
- 1 pair of types, where a type in Core.ValidationErrorModule uses a type in Core.
- The types involved
FsMcp.Core.ValidationErrorModule.ValidationErrorModule→FsMcp.Core.ValidationError
- Direction
- Core.ValidationErrorModule uses Core, so a change to Core can break Core.ValidationErrorModule, while a change to Core.ValidationErrorModule can't break Core.
- Position
- Below the diagonal: Core.ValidationErrorModule uses a module listed above it, which is the healthy direction.
15→2 Sampling uses Core✕
- Connections
- 2 pairs of types, where a type in Sampling uses a type in Core.
- The types involved
FsMcp.Sampling.SamplingRequest→FsMcp.Core.McpMessageFsMcp.Sampling.SamplingResult→FsMcp.Core.McpMessage
- Direction
- Sampling uses Core, so a change to Core can break Sampling, while a change to Sampling can't break Core.
- Position
- Below the diagonal: Sampling uses a module listed above it, which is the healthy direction.
16→1 Server uses Core.Validation✕
- Connections
- 5 pairs of types, where a type in Server uses a type in Core.Validation.
- The types involved
FsMcp.Server.ServerBuilderState→FsMcp.Core.Validation.ServerNameFsMcp.Server.ServerBuilderState→FsMcp.Core.Validation.ServerVersionFsMcp.Server.ServerConfig→FsMcp.Core.Validation.ServerNameFsMcp.Server.ServerConfig→FsMcp.Core.Validation.ServerVersionFsMcp.Server.SubscriptionEntry→FsMcp.Core.Validation.ResourceUri
- Direction
- Server uses Core.Validation, so a change to Core.Validation can break Server, while a change to Server can't break Core.Validation.
- Position
- Below the diagonal: Server uses a module listed above it, which is the healthy direction.
16→2 Server uses Core✕
- Connections
- 11 pairs of types, where a type in Server uses a type in Core.
- The types involved
FsMcp.Server.McpResponse→FsMcp.Core.McpErrorFsMcp.Server.McpServerBuilder→FsMcp.Core.PromptDefinitionFsMcp.Server.McpServerBuilder→FsMcp.Core.ResourceDefinitionFsMcp.Server.McpServerBuilder→FsMcp.Core.ToolDefinitionFsMcp.Server.ServerBuilderState→FsMcp.Core.PromptDefinitionFsMcp.Server.ServerBuilderState→FsMcp.Core.ResourceDefinitionFsMcp.Server.ServerBuilderState→FsMcp.Core.ToolDefinitionFsMcp.Server.ServerConfig→FsMcp.Core.PromptDefinitionFsMcp.Server.ServerConfig→FsMcp.Core.ResourceDefinitionFsMcp.Server.ServerConfig→FsMcp.Core.ToolDefinitionFsMcp.Server.ToolCEBuilder→FsMcp.Core.ToolDefinition
- Direction
- Server uses Core, so a change to Core can break Server, while a change to Server can't break Core.
- Position
- Below the diagonal: Server uses a module listed above it, which is the healthy direction.
17→2 Server.Notifications uses Core✕
- Connections
- 1 pair of types, where a type in Server.Notifications uses a type in Core.
- The types involved
FsMcp.Server.Notifications.ContextualToolHandle→FsMcp.Core.ToolDefinition
- Direction
- Server.Notifications uses Core, so a change to Core can break Server.Notifications, while a change to Server.Notifications can't break Core.
- Position
- Below the diagonal: Server.Notifications uses a module listed above it, which is the healthy direction.
18→2 Testing uses Core✕
- Connections
- 1 pair of types, where a type in Testing uses a type in Core.
- The types involved
FsMcp.Testing.PromptInfo→FsMcp.Core.PromptArgument
- Direction
- Testing uses Core, so a change to Core can break Testing, while a change to Testing can't break Core.
- Position
- Below the diagonal: Testing uses a module listed above it, which is the healthy direction.
19→1 Testing.McpArbitraries uses Core.Validation✕
- Connections
- 8 pairs of types, where a type in Testing.McpArbitraries uses a type in Core.Validation.
- The types involved
FsMcp.Testing.McpArbitraries.McpArbitraries→FsMcp.Core.Validation.MimeTypeFsMcp.Testing.McpArbitraries.McpArbitraries→FsMcp.Core.Validation.PromptNameFsMcp.Testing.McpArbitraries.McpArbitraries→FsMcp.Core.Validation.ResourceUriFsMcp.Testing.McpArbitraries.McpArbitraries→FsMcp.Core.Validation.ToolNameFsMcp.Testing.McpArbitraries.McpArbitraryProvider→FsMcp.Core.Validation.MimeTypeFsMcp.Testing.McpArbitraries.McpArbitraryProvider→FsMcp.Core.Validation.PromptNameFsMcp.Testing.McpArbitraries.McpArbitraryProvider→FsMcp.Core.Validation.ResourceUriFsMcp.Testing.McpArbitraries.McpArbitraryProvider→FsMcp.Core.Validation.ToolName
- Direction
- Testing.McpArbitraries uses Core.Validation, so a change to Core.Validation can break Testing.McpArbitraries, while a change to Testing.McpArbitraries can't break Core.Validation.
- Position
- Below the diagonal: Testing.McpArbitraries uses a module listed above it, which is the healthy direction.
19→2 Testing.McpArbitraries uses Core✕
- Connections
- 7 pairs of types, where a type in Testing.McpArbitraries uses a type in Core.
- The types involved
FsMcp.Testing.McpArbitraries.McpArbitraries→FsMcp.Core.ContentFsMcp.Testing.McpArbitraries.McpArbitraries→FsMcp.Core.McpMessageFsMcp.Testing.McpArbitraries.McpArbitraries→FsMcp.Core.McpRoleFsMcp.Testing.McpArbitraries.McpArbitraries→FsMcp.Core.ResourceContentsFsMcp.Testing.McpArbitraries.McpArbitraryProvider→FsMcp.Core.ContentFsMcp.Testing.McpArbitraries.McpArbitraryProvider→FsMcp.Core.McpMessageFsMcp.Testing.McpArbitraries.McpArbitraryProvider→FsMcp.Core.ResourceContents
- Direction
- Testing.McpArbitraries uses Core, so a change to Core can break Testing.McpArbitraries, while a change to Testing.McpArbitraries can't break Core.
- Position
- Below the diagonal: Testing.McpArbitraries uses a module listed above it, which is the healthy direction.
20→3 Client.ClientTransportModule uses Client✕
- Connections
- 1 pair of types, where a type in Client.ClientTransportModule uses a type in Client.
- The types involved
FsMcp.Client.ClientTransportModule.ClientTransportModule→FsMcp.Client.ClientTransport
- Direction
- Client.ClientTransportModule uses Client, so a change to Client can break Client.ClientTransportModule, while a change to Client.ClientTransportModule can't break Client.
- Position
- Below the diagonal: Client.ClientTransportModule uses a module listed above it, which is the healthy direction.
21→3 Client.EnterpriseAuthorizationEndpoint uses Client✕
- Connections
- 3 pairs of types, where a type in Client.EnterpriseAuthorizationEndpoint uses a type in Client.
- The types involved
FsMcp.Client.EnterpriseAuthorizationEndpoint.EnterpriseAuthorizationEndpoint→FsMcp.Client.EnterpriseManagedAuthorizationConfigurationErrorFsMcp.Client.EnterpriseAuthorizationEndpoint.EnterpriseAuthorizationEndpoint→FsMcp.Client.EnterprisePlaintextEndpointAllowanceFsMcp.Client.EnterpriseAuthorizationEndpoint.EnterpriseAuthorizationEndpoint→FsMcp.Client.EnterpriseTokenRequestPolicy
- Direction
- Client.EnterpriseAuthorizationEndpoint uses Client, so a change to Client can break Client.EnterpriseAuthorizationEndpoint, while a change to Client.EnterpriseAuthorizationEndpoint can't break Client.
- Position
- Below the diagonal: Client.EnterpriseAuthorizationEndpoint uses a module listed above it, which is the healthy direction.
22→3 Client.EnterpriseAuthorizationValidation uses Client✕
- Connections
- 1 pair of types, where a type in Client.EnterpriseAuthorizationValidation uses a type in Client.
- The types involved
FsMcp.Client.EnterpriseAuthorizationValidation.EnterpriseAuthorizationValidation→FsMcp.Client.EnterpriseManagedAuthorizationConfigurationError
- Direction
- Client.EnterpriseAuthorizationValidation uses Client, so a change to Client can break Client.EnterpriseAuthorizationValidation, while a change to Client.EnterpriseAuthorizationValidation can't break Client.
- Position
- Below the diagonal: Client.EnterpriseAuthorizationValidation uses a module listed above it, which is the healthy direction.
23→3 Client.EnterpriseIdentityProviderModule uses Client✕
- Connections
- 2 pairs of types, where a type in Client.EnterpriseIdentityProviderModule uses a type in Client.
- The types involved
FsMcp.Client.EnterpriseIdentityProviderModule.EnterpriseIdentityProviderModule→FsMcp.Client.EnterpriseIdentityProviderFsMcp.Client.EnterpriseIdentityProviderModule.EnterpriseIdentityProviderModule→FsMcp.Client.EnterpriseManagedAuthorizationConfigurationError
- Direction
- Client.EnterpriseIdentityProviderModule uses Client, so a change to Client can break Client.EnterpriseIdentityProviderModule, while a change to Client.EnterpriseIdentityProviderModule can't break Client.
- Position
- Below the diagonal: Client.EnterpriseIdentityProviderModule uses a module listed above it, which is the healthy direction.
24→3 Client.EnterpriseManagedAuthorizationEndpointPolicy uses Client✕
- Connections
- 3 pairs of types, where a type in Client.EnterpriseManagedAuthorizationEndpointPolicy uses a type in Client.
- The types involved
FsMcp.Client.EnterpriseManagedAuthorizationEndpointPolicy.EnterpriseManagedAuthorizationEndpointPolicy→FsMcp.Client.EnterpriseManagedAuthorizationSettingsFsMcp.Client.EnterpriseManagedAuthorizationEndpointPolicy.EnterpriseManagedAuthorizationEndpointPolicy→FsMcp.Client.EnterprisePlaintextEndpointAllowanceFsMcp.Client.EnterpriseManagedAuthorizationEndpointPolicy.EnterpriseManagedAuthorizationEndpointPolicy→FsMcp.Client.EnterpriseTokenRequestPolicy
- Direction
- Client.EnterpriseManagedAuthorizationEndpointPolicy uses Client, so a change to Client can break Client.EnterpriseManagedAuthorizationEndpointPolicy, while a change to Client.EnterpriseManagedAuthorizationEndpointPolicy can't break Client.
- Position
- Below the diagonal: Client.EnterpriseManagedAuthorizationEndpointPolicy uses a module listed above it, which is the healthy direction.
25→3 Client.EnterpriseManagedAuthorizationFailureModule uses Client✕
- Connections
- 1 pair of types, where a type in Client.EnterpriseManagedAuthorizationFailureModule uses a type in Client.
- The types involved
FsMcp.Client.EnterpriseManagedAuthorizationFailureModule.EnterpriseManagedAuthorizationFailureModule→FsMcp.Client.EnterpriseManagedAuthorizationFailure
- Direction
- Client.EnterpriseManagedAuthorizationFailureModule uses Client, so a change to Client can break Client.EnterpriseManagedAuthorizationFailureModule, while a change to Client.EnterpriseManagedAuthorizationFailureModule can't break Client.
- Position
- Below the diagonal: Client.EnterpriseManagedAuthorizationFailureModule uses a module listed above it, which is the healthy direction.
26→3 Client.EnterpriseManagedAuthorizationModule uses Client✕
- Connections
- 2 pairs of types, where a type in Client.EnterpriseManagedAuthorizationModule uses a type in Client.
- The types involved
FsMcp.Client.EnterpriseManagedAuthorizationModule.EnterpriseManagedAuthorizationModule→FsMcp.Client.EnterpriseManagedAuthorizationFsMcp.Client.EnterpriseManagedAuthorizationModule.EnterpriseManagedAuthorizationModule→FsMcp.Client.EnterpriseManagedAuthorizationOptions
- Direction
- Client.EnterpriseManagedAuthorizationModule uses Client, so a change to Client can break Client.EnterpriseManagedAuthorizationModule, while a change to Client.EnterpriseManagedAuthorizationModule can't break Client.
- Position
- Below the diagonal: Client.EnterpriseManagedAuthorizationModule uses a module listed above it, which is the healthy direction.
27→3 Client.EnterpriseManagedAuthorizationOptionsModule uses Client✕
- Connections
- 3 pairs of types, where a type in Client.EnterpriseManagedAuthorizationOptionsModule uses a type in Client.
- The types involved
FsMcp.Client.EnterpriseManagedAuthorizationOptionsModule.EnterpriseManagedAuthorizationOptionsModule→FsMcp.Client.EnterpriseIdentityProviderFsMcp.Client.EnterpriseManagedAuthorizationOptionsModule.EnterpriseManagedAuthorizationOptionsModule→FsMcp.Client.EnterpriseManagedAuthorizationConfigurationErrorFsMcp.Client.EnterpriseManagedAuthorizationOptionsModule.EnterpriseManagedAuthorizationOptionsModule→FsMcp.Client.EnterpriseManagedAuthorizationOptions
- Direction
- Client.EnterpriseManagedAuthorizationOptionsModule uses Client, so a change to Client can break Client.EnterpriseManagedAuthorizationOptionsModule, while a change to Client.EnterpriseManagedAuthorizationOptionsModule can't break Client.
- Position
- Below the diagonal: Client.EnterpriseManagedAuthorizationOptionsModule uses a module listed above it, which is the healthy direction.
28→3 Client.EnterprisePlaintextEndpointAllowanceModule uses Client✕
- Connections
- 1 pair of types, where a type in Client.EnterprisePlaintextEndpointAllowanceModule uses a type in Client.
- The types involved
FsMcp.Client.EnterprisePlaintextEndpointAllowanceModule.EnterprisePlaintextEndpointAllowanceModule→FsMcp.Client.EnterprisePlaintextEndpointAllowance
- Direction
- Client.EnterprisePlaintextEndpointAllowanceModule uses Client, so a change to Client can break Client.EnterprisePlaintextEndpointAllowanceModule, while a change to Client.EnterprisePlaintextEndpointAllowanceModule can't break Client.
- Position
- Below the diagonal: Client.EnterprisePlaintextEndpointAllowanceModule uses a module listed above it, which is the healthy direction.
29→3 Client.EnterpriseRequestReplay uses Client✕
- Connections
- 1 pair of types, where a type in Client.EnterpriseRequestReplay uses a type in Client.
- The types involved
FsMcp.Client.EnterpriseRequestReplay.EnterpriseRequestReplay→FsMcp.Client.ReplayableRequestBody
- Direction
- Client.EnterpriseRequestReplay uses Client, so a change to Client can break Client.EnterpriseRequestReplay, while a change to Client.EnterpriseRequestReplay can't break Client.
- Position
- Below the diagonal: Client.EnterpriseRequestReplay uses a module listed above it, which is the healthy direction.
30→1 Client.McpClientAsync uses Core.Validation✕
- Connections
- 3 pairs of types, where a type in Client.McpClientAsync uses a type in Core.Validation.
- The types involved
FsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Core.Validation.PromptNameFsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Core.Validation.ResourceUriFsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Core.Validation.ToolName
- Direction
- Client.McpClientAsync uses Core.Validation, so a change to Core.Validation can break Client.McpClientAsync, while a change to Client.McpClientAsync can't break Core.Validation.
- Position
- Below the diagonal: Client.McpClientAsync uses a module listed above it, which is the healthy direction.
30→2 Client.McpClientAsync uses Core✕
- Connections
- 4 pairs of types, where a type in Client.McpClientAsync uses a type in Core.
- The types involved
FsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Core.ContentFsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Core.McpErrorFsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Core.McpMessageFsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Core.ResourceContents
- Direction
- Client.McpClientAsync uses Core, so a change to Core can break Client.McpClientAsync, while a change to Client.McpClientAsync can't break Core.
- Position
- Below the diagonal: Client.McpClientAsync uses a module listed above it, which is the healthy direction.
30→3 Client.McpClientAsync uses Client✕
- Connections
- 7 pairs of types, where a type in Client.McpClientAsync uses a type in Client.
- The types involved
FsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Client.ClientConfigFsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Client.EnterpriseManagedAuthorizationFsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Client.McpClientFsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Client.PromptDetailsFsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Client.PromptInfoFsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Client.ResourceInfoFsMcp.Client.McpClientAsync.McpClientAsync→FsMcp.Client.ToolInfo
- Direction
- Client.McpClientAsync uses Client, so a change to Client can break Client.McpClientAsync, while a change to Client.McpClientAsync can't break Client.
- Position
- Below the diagonal: Client.McpClientAsync uses a module listed above it, which is the healthy direction.
31→1 Client.McpClientModule uses Core.Validation✕
- Connections
- 3 pairs of types, where a type in Client.McpClientModule uses a type in Core.Validation.
- The types involved
FsMcp.Client.McpClientModule.McpClientModule→FsMcp.Core.Validation.PromptNameFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Core.Validation.ResourceUriFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Core.Validation.ToolName
- Direction
- Client.McpClientModule uses Core.Validation, so a change to Core.Validation can break Client.McpClientModule, while a change to Client.McpClientModule can't break Core.Validation.
- Position
- Below the diagonal: Client.McpClientModule uses a module listed above it, which is the healthy direction.
31→2 Client.McpClientModule uses Core✕
- Connections
- 5 pairs of types, where a type in Client.McpClientModule uses a type in Core.
- The types involved
FsMcp.Client.McpClientModule.McpClientModule→FsMcp.Core.ContentFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Core.McpErrorFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Core.McpMessageFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Core.McpRoleFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Core.ResourceContents
- Direction
- Client.McpClientModule uses Core, so a change to Core can break Client.McpClientModule, while a change to Client.McpClientModule can't break Core.
- Position
- Below the diagonal: Client.McpClientModule uses a module listed above it, which is the healthy direction.
31→3 Client.McpClientModule uses Client✕
- Connections
- 8 pairs of types, where a type in Client.McpClientModule uses a type in Client.
- The types involved
FsMcp.Client.McpClientModule.McpClientModule→FsMcp.Client.ClientConfigFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Client.ClientTransportFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Client.EnterpriseManagedAuthorizationFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Client.McpClientFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Client.PromptDetailsFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Client.PromptInfoFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Client.ResourceInfoFsMcp.Client.McpClientModule.McpClientModule→FsMcp.Client.ToolInfo
- Direction
- Client.McpClientModule uses Client, so a change to Client can break Client.McpClientModule, while a change to Client.McpClientModule can't break Client.
- Position
- Below the diagonal: Client.McpClientModule uses a module listed above it, which is the healthy direction.
32→2 Sampling.SamplingTool uses Core✕
- Connections
- 2 pairs of types, where a type in Sampling.SamplingTool uses a type in Core.
- The types involved
FsMcp.Sampling.SamplingTool.SamplingTool→FsMcp.Core.ToolDefinitionFsMcp.Sampling.SamplingTool.SamplingTool→FsMcp.Core.ValidationError
- Direction
- Sampling.SamplingTool uses Core, so a change to Core can break Sampling.SamplingTool, while a change to Sampling.SamplingTool can't break Core.
- Position
- Below the diagonal: Sampling.SamplingTool uses a module listed above it, which is the healthy direction.
32→15 Sampling.SamplingTool uses Sampling✕
- Connections
- 4 pairs of types, where a type in Sampling.SamplingTool uses a type in Sampling.
- The types involved
FsMcp.Sampling.SamplingTool.SamplingTool→FsMcp.Sampling.SamplingContextFsMcp.Sampling.SamplingTool.SamplingTool→FsMcp.Sampling.SamplingErrorFsMcp.Sampling.SamplingTool.SamplingTool→FsMcp.Sampling.SamplingRequestFsMcp.Sampling.SamplingTool.SamplingTool→FsMcp.Sampling.SamplingResult
- Direction
- Sampling.SamplingTool uses Sampling, so a change to Sampling can break Sampling.SamplingTool, while a change to Sampling.SamplingTool can't break Sampling.
- Position
- Below the diagonal: Sampling.SamplingTool uses a module listed above it, which is the healthy direction.
33→1 Server.DynamicServer uses Core.Validation✕
- Connections
- 1 pair of types, where a type in Server.DynamicServer uses a type in Core.Validation.
- The types involved
FsMcp.Server.DynamicServer.DynamicServer→FsMcp.Core.Validation.ToolName
- Direction
- Server.DynamicServer uses Core.Validation, so a change to Core.Validation can break Server.DynamicServer, while a change to Server.DynamicServer can't break Core.Validation.
- Position
- Below the diagonal: Server.DynamicServer uses a module listed above it, which is the healthy direction.
33→2 Server.DynamicServer uses Core✕
- Connections
- 1 pair of types, where a type in Server.DynamicServer uses a type in Core.
- The types involved
FsMcp.Server.DynamicServer.DynamicServer→FsMcp.Core.ToolDefinition
- Direction
- Server.DynamicServer uses Core, so a change to Core can break Server.DynamicServer, while a change to Server.DynamicServer can't break Core.
- Position
- Below the diagonal: Server.DynamicServer uses a module listed above it, which is the healthy direction.
33→16 Server.DynamicServer uses Server✕
- Connections
- 2 pairs of types, where a type in Server.DynamicServer uses a type in Server.
- The types involved
FsMcp.Server.DynamicServer.DynamicServer→FsMcp.Server.DynamicServerConfigFsMcp.Server.DynamicServer.DynamicServer→FsMcp.Server.ServerConfig
- Direction
- Server.DynamicServer uses Server, so a change to Server can break Server.DynamicServer, while a change to Server.DynamicServer can't break Server.
- Position
- Below the diagonal: Server.DynamicServer uses a module listed above it, which is the healthy direction.
34→2 Server.Notifications.ContextualTool uses Core✕
- Connections
- 3 pairs of types, where a type in Server.Notifications.ContextualTool uses a type in Core.
- The types involved
FsMcp.Server.Notifications.ContextualTool.ContextualTool→FsMcp.Core.ContentFsMcp.Server.Notifications.ContextualTool.ContextualTool→FsMcp.Core.McpErrorFsMcp.Server.Notifications.ContextualTool.ContextualTool→FsMcp.Core.ValidationError
- Direction
- Server.Notifications.ContextualTool uses Core, so a change to Core can break Server.Notifications.ContextualTool, while a change to Server.Notifications.ContextualTool can't break Core.
- Position
- Below the diagonal: Server.Notifications.ContextualTool uses a module listed above it, which is the healthy direction.
34→17 Server.Notifications.ContextualTool uses Server.Notifications✕
- Connections
- 2 pairs of types, where a type in Server.Notifications.ContextualTool uses a type in Server.Notifications.
- The types involved
FsMcp.Server.Notifications.ContextualTool.ContextualTool→FsMcp.Server.Notifications.ContextualToolHandleFsMcp.Server.Notifications.ContextualTool.ContextualTool→FsMcp.Server.Notifications.HandlerContext
- Direction
- Server.Notifications.ContextualTool uses Server.Notifications, so a change to Server.Notifications can break Server.Notifications.ContextualTool, while a change to Server.Notifications.ContextualTool can't break Server.Notifications.
- Position
- Below the diagonal: Server.Notifications.ContextualTool uses a module listed above it, which is the healthy direction.
35→1 Server.ResourceSubscriptions uses Core.Validation✕
- Connections
- 1 pair of types, where a type in Server.ResourceSubscriptions uses a type in Core.Validation.
- The types involved
FsMcp.Server.ResourceSubscriptions.ResourceSubscriptions→FsMcp.Core.Validation.ResourceUri
- Direction
- Server.ResourceSubscriptions uses Core.Validation, so a change to Core.Validation can break Server.ResourceSubscriptions, while a change to Server.ResourceSubscriptions can't break Core.Validation.
- Position
- Below the diagonal: Server.ResourceSubscriptions uses a module listed above it, which is the healthy direction.
35→16 Server.ResourceSubscriptions uses Server✕
- Connections
- 3 pairs of types, where a type in Server.ResourceSubscriptions uses a type in Server.
- The types involved
FsMcp.Server.ResourceSubscriptions.ResourceSubscriptions→FsMcp.Server.ResourceSubscriptionRegistryFsMcp.Server.ResourceSubscriptions.ResourceSubscriptions→FsMcp.Server.SubscriptionErrorFsMcp.Server.ResourceSubscriptions.ResourceSubscriptions→FsMcp.Server.SubscriptionId
- Direction
- Server.ResourceSubscriptions uses Server, so a change to Server can break Server.ResourceSubscriptions, while a change to Server.ResourceSubscriptions can't break Server.
- Position
- Below the diagonal: Server.ResourceSubscriptions uses a module listed above it, which is the healthy direction.
36→1 Server.Server uses Core.Validation✕
- Connections
- 1 pair of types, where a type in Server.Server uses a type in Core.Validation.
- The types involved
FsMcp.Server.Server.Server→FsMcp.Core.Validation.ResourceUri
- Direction
- Server.Server uses Core.Validation, so a change to Core.Validation can break Server.Server, while a change to Server.Server can't break Core.Validation.
- Position
- Below the diagonal: Server.Server uses a module listed above it, which is the healthy direction.
36→2 Server.Server uses Core✕
- Connections
- 8 pairs of types, where a type in Server.Server uses a type in Core.
- The types involved
FsMcp.Server.Server.PromptAIFunction→FsMcp.Core.PromptDefinitionFsMcp.Server.Server.ResourceAIFunction→FsMcp.Core.ResourceDefinitionFsMcp.Server.Server.Server→FsMcp.Core.McpErrorFsMcp.Server.Server.Server→FsMcp.Core.PromptDefinitionFsMcp.Server.Server.Server→FsMcp.Core.ResourceDefinitionFsMcp.Server.Server.Server→FsMcp.Core.ToolDefinitionFsMcp.Server.Server.Server→FsMcp.Core.ValidationErrorFsMcp.Server.Server.ToolAIFunction→FsMcp.Core.ToolDefinition
- Direction
- Server.Server uses Core, so a change to Core can break Server.Server, while a change to Server.Server can't break Core.
- Position
- Below the diagonal: Server.Server uses a module listed above it, which is the healthy direction.
36→16 Server.Server uses Server✕
- Connections
- 3 pairs of types, where a type in Server.Server uses a type in Server.
- The types involved
FsMcp.Server.Server.Server→FsMcp.Server.ResourceSubscriptionRegistryFsMcp.Server.Server.Server→FsMcp.Server.ServerConfigFsMcp.Server.Server.Server→FsMcp.Server.ServerRegistration
- Direction
- Server.Server uses Server, so a change to Server can break Server.Server, while a change to Server.Server can't break Server.
- Position
- Below the diagonal: Server.Server uses a module listed above it, which is the healthy direction.
37→2 Server.ServerConfigModule uses Core✕
- Connections
- 1 pair of types, where a type in Server.ServerConfigModule uses a type in Core.
- The types involved
FsMcp.Server.ServerConfigModule.ServerConfigModule→FsMcp.Core.ValidationError
- Direction
- Server.ServerConfigModule uses Core, so a change to Core can break Server.ServerConfigModule, while a change to Server.ServerConfigModule can't break Core.
- Position
- Below the diagonal: Server.ServerConfigModule uses a module listed above it, which is the healthy direction.
37→16 Server.ServerConfigModule uses Server✕
- Connections
- 1 pair of types, where a type in Server.ServerConfigModule uses a type in Server.
- The types involved
FsMcp.Server.ServerConfigModule.ServerConfigModule→FsMcp.Server.ServerConfig
- Direction
- Server.ServerConfigModule uses Server, so a change to Server can break Server.ServerConfigModule, while a change to Server.ServerConfigModule can't break Server.
- Position
- Below the diagonal: Server.ServerConfigModule uses a module listed above it, which is the healthy direction.
38→2 Server.ValidationMiddleware uses Core✕
- Connections
- 1 pair of types, where a type in Server.ValidationMiddleware uses a type in Core.
- The types involved
FsMcp.Server.ValidationMiddleware.ValidationMiddleware→FsMcp.Core.ToolDefinition
- Direction
- Server.ValidationMiddleware uses Core, so a change to Core can break Server.ValidationMiddleware, while a change to Server.ValidationMiddleware can't break Core.
- Position
- Below the diagonal: Server.ValidationMiddleware uses a module listed above it, which is the healthy direction.
38→16 Server.ValidationMiddleware uses Server✕
- Connections
- 3 pairs of types, where a type in Server.ValidationMiddleware uses a type in Server.
- The types involved
FsMcp.Server.ValidationMiddleware.ValidationMiddleware→FsMcp.Server.McpContextFsMcp.Server.ValidationMiddleware.ValidationMiddleware→FsMcp.Server.McpResponseFsMcp.Server.ValidationMiddleware.ValidationMiddleware→FsMcp.Server.ServerConfig
- Direction
- Server.ValidationMiddleware uses Server, so a change to Server can break Server.ValidationMiddleware, while a change to Server.ValidationMiddleware can't break Server.
- Position
- Below the diagonal: Server.ValidationMiddleware uses a module listed above it, which is the healthy direction.
39→2 TaskApi.ClientPipeline uses Core✕
- Connections
- 4 pairs of types, where a type in TaskApi.ClientPipeline uses a type in Core.
- The types involved
FsMcp.TaskApi.ClientPipeline.ClientPipeline→FsMcp.Core.ContentFsMcp.TaskApi.ClientPipeline.ClientPipeline→FsMcp.Core.McpErrorFsMcp.TaskApi.ClientPipeline.ClientPipeline→FsMcp.Core.McpMessageFsMcp.TaskApi.ClientPipeline.ClientPipeline→FsMcp.Core.ResourceContents
- Direction
- TaskApi.ClientPipeline uses Core, so a change to Core can break TaskApi.ClientPipeline, while a change to TaskApi.ClientPipeline can't break Core.
- Position
- Below the diagonal: TaskApi.ClientPipeline uses a module listed above it, which is the healthy direction.
39→3 TaskApi.ClientPipeline uses Client✕
- Connections
- 7 pairs of types, where a type in TaskApi.ClientPipeline uses a type in Client.
- The types involved
FsMcp.TaskApi.ClientPipeline.ClientPipeline→FsMcp.Client.ClientConfigFsMcp.TaskApi.ClientPipeline.ClientPipeline→FsMcp.Client.EnterpriseManagedAuthorizationFsMcp.TaskApi.ClientPipeline.ClientPipeline→FsMcp.Client.McpClientFsMcp.TaskApi.ClientPipeline.ClientPipeline→FsMcp.Client.PromptDetailsFsMcp.TaskApi.ClientPipeline.ClientPipeline→FsMcp.Client.PromptInfoFsMcp.TaskApi.ClientPipeline.ClientPipeline→FsMcp.Client.ResourceInfoFsMcp.TaskApi.ClientPipeline.ClientPipeline→FsMcp.Client.ToolInfo
- Direction
- TaskApi.ClientPipeline uses Client, so a change to Client can break TaskApi.ClientPipeline, while a change to TaskApi.ClientPipeline can't break Client.
- Position
- Below the diagonal: TaskApi.ClientPipeline uses a module listed above it, which is the healthy direction.
40→2 Testing.TestServer uses Core✕
- Connections
- 4 pairs of types, where a type in Testing.TestServer uses a type in Core.
- The types involved
FsMcp.Testing.TestServer.TestServer→FsMcp.Core.ContentFsMcp.Testing.TestServer.TestServer→FsMcp.Core.McpErrorFsMcp.Testing.TestServer.TestServer→FsMcp.Core.McpMessageFsMcp.Testing.TestServer.TestServer→FsMcp.Core.ResourceContents
- Direction
- Testing.TestServer uses Core, so a change to Core can break Testing.TestServer, while a change to Testing.TestServer can't break Core.
- Position
- Below the diagonal: Testing.TestServer uses a module listed above it, which is the healthy direction.
40→16 Testing.TestServer uses Server✕
- Connections
- 1 pair of types, where a type in Testing.TestServer uses a type in Server.
- The types involved
FsMcp.Testing.TestServer.TestServer→FsMcp.Server.ServerConfig
- Direction
- Testing.TestServer uses Server, so a change to Server can break Testing.TestServer, while a change to Testing.TestServer can't break Server.
- Position
- Below the diagonal: Testing.TestServer uses a module listed above it, which is the healthy direction.
40→18 Testing.TestServer uses Testing✕
- Connections
- 3 pairs of types, where a type in Testing.TestServer uses a type in Testing.
- The types involved
FsMcp.Testing.TestServer.TestServer→FsMcp.Testing.PromptInfoFsMcp.Testing.TestServer.TestServer→FsMcp.Testing.ResourceInfoFsMcp.Testing.TestServer.TestServer→FsMcp.Testing.ToolInfo
- Direction
- Testing.TestServer uses Testing, so a change to Testing can break Testing.TestServer, while a change to Testing.TestServer can't break Testing.
- Position
- Below the diagonal: Testing.TestServer uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
Roadmap
Top priorities: Resolve the 86 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json; Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it; Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with packages.lock.json (7).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 86 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json. | +11.6 pts | Medium | Dependency Hygiene |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +4.0 pts | Medium | Deployment & Rollback |
| Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with packages.lock.json (7). | +0.9 pts | Low | Dependency Hygiene |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 TooManyFunctions finding(s) in God Classes — start with McpClient.fs. | +0.3 pts | Low | God Classes |
| Resolve the 1 Scattered collaborators finding(s) in Navigability. | +0.2 pts | Low | Navigability |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/FsMcp.Core/Interop.fs | 6.3 | Mixed | Cyclomatic Complexity: Interop.fromSdkContentBlock (cyclomatic 16) |
| src/FsMcp.Client/McpClient.fs | 7.2 | Mixed | Cyclomatic Complexity: McpClientModule.convertContentBlock (cyclomatic 17) |
| src/FsMcp.Server/TypedHandlers.fs | 7.8 | Mixed | Cognitive Complexity: SchemaGen.generateSchema (cognitive 27) |
| src/FsMcp.Client/EnterpriseManagedAuthorization.fs | 7.8 | Mixed | Cognitive Complexity: EnterpriseTokenExchangeSecurityHandler.SendAsync (cognitive 17) |
| src/FsMcp.Server/Subscriptions.fs | 8.5 | Near-clean | Cognitive Complexity: ResourceSubscriptions.subscribe (cognitive 17) |
| src/FsMcp.Server/Streaming.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (17–18 lines × 3) |
| src/FsMcp.Server/Transport.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| src/FsMcp.Server/DynamicServer.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/FsMcp.Server/DynamicServer.fs |
| website/package.json | 9.5 | Near-clean | Dependency Hygiene: Outdated (npm): uuid |
| tests/FsMcp.Client.Tests/packages.lock.json | 9.5 | Near-clean | Dependency Hygiene: Deprecated: Microsoft.Testing.Platform.MSBuild |
| tests/FsMcp.Core.Tests/packages.lock.json | 9.5 | Near-clean | Dependency Hygiene: Deprecated: Microsoft.Testing.Platform.MSBuild |
| tests/FsMcp.Sampling.Tests/packages.lock.json | 9.5 | Near-clean | Dependency Hygiene: Deprecated: Microsoft.Testing.Platform.MSBuild |
| tests/FsMcp.Server.Http.Tests/packages.lock.json | 9.5 | Near-clean | Dependency Hygiene: Deprecated: Microsoft.Testing.Platform.MSBuild |
| tests/FsMcp.Server.Tests/packages.lock.json | 9.5 | Near-clean | Dependency Hygiene: Deprecated: Microsoft.Testing.Platform.MSBuild |
| tests/FsMcp.TaskApi.Tests/packages.lock.json | 9.5 | Near-clean | Dependency Hygiene: Deprecated: Microsoft.Testing.Platform.MSBuild |
| tests/FsMcp.Testing.Tests/packages.lock.json | 9.5 | Near-clean | Dependency Hygiene: Deprecated: Microsoft.Testing.Platform.MSBuild |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 42 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 42 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 25 of 670 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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-contributor repository — bus factor is not applicable (1 contributor(s) across 59 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D22 Internal API Consistency — 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. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `website/docusaurus.config.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Microsoft.Extensions.DependencyInjection registered from F#, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was McpClientModule.convertContentBlock at 17.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with McpClientModule.convertContentBlock (cyclomatic 17), Interop.fromSdkContentBlock (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
6 method(s) exceeded the cognitive complexity threshold of 15; the worst was McpClientModule.convertContentBlock at 36.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cognitive Complexity — start with McpClientModule.convertContentBlock (cognitive 36), Interop.fromSdkContentBlock (cognitive 35), SchemaGen.generateSchema (cognitive 27). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with EnterpriseManagedAuthorization.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyFunctions finding(s) in God Classes — start with McpClient.fs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
3 duplicated block group(s) detected. 2.0 % of the production lines (98 of 4,919) are in a reported copy.
What to do
- Resolve the 1 Duplicated block (17–18 lines × 3) finding(s) in Code Duplication — start with Streaming.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Transport.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with TypedHandlers.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
17 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 5 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Cycles found: 0.
D8 · Code Coverage
Line coverage 81.3% — 2 file(s) below 50%.
What to do
- Resolve the 2 Low coverage finding(s) in Code Coverage — start with DynamicServer.fs, Interop.fs. — One of this dimension's main actionable groups (2 warning-level).
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); other: measured (0 flaky).
D12 · Dependency Hygiene
14 outdated, 0 vulnerable, 0 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 626 outdated of 1099 package(s) across 1 lockfile(s).
What to do
- Resolve the 86 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (86 recommendation-level).
- Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with packages.lock.json (7). — One of this dimension's main actionable groups (7 recommendation-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 190 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 14 direct `PackageReference`(s), and 147 further package(s) were reached beyond them by closing the graph over the committed `packages.lock.json` and nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 22 document(s) read across 2 unit(s).
D20 · ADR Quality
0 of 1 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.
D26 · Project Cohesion
0 of 8 build units (MSBuild, checkout, npm) flagged as possibly oversized/incoherent.
D27 · Navigability
91 % of calls cross a namespace and 2 % go through an interface, but 38 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 3 file(s) — `.specify/scripts/bash/common.sh`, `.specify/scripts/bash/create-new-feature.sh`, `website/docusaurus.config.ts` (line 40, line 173) — 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. Separately, one or more rules could not re-parse an embedded snippet in 2 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.
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 24 of the 30 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 17 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- Add a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/ci.yml:6
- `Directory.Build.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Directory.Build.props:39
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X20 · Mistyped argument guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 90% | Checked 4 of 11 | Solid. |
| Architecture | 95% | Exemplary | Solid. |
| Maturity | 93% | Exemplary | Solid. |
| Readiness | 56% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 85% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 70 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~6741 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1738 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs, .py source were not judged.
- 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.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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 — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 57 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 28 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- 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 — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Serious — 16 finding(s)
- Low coverage: src/FsMcp.Server/DynamicServer.fs src/FsMcp.Server/DynamicServer.fs:1
- Low coverage: src/FsMcp.Core/Interop.fs src/FsMcp.Core/Interop.fs:1
- McpClientModule.convertContentBlock (cyclomatic 17) src/FsMcp.Client/McpClient.fs:279
- Interop.fromSdkContentBlock (cyclomatic 16) src/FsMcp.Core/Interop.fs:37
- McpClientModule.convertContentBlock (cognitive 36) src/FsMcp.Client/McpClient.fs:279
- Interop.fromSdkContentBlock (cognitive 35) src/FsMcp.Core/Interop.fs:37
- SchemaGen.generateSchema (cognitive 27) src/FsMcp.Server/TypedHandlers.fs:46
- ResourceSubscriptions.subscribe (cognitive 17) src/FsMcp.Server/Subscriptions.fs:73
- McpClientModule.convertResourceContent (cognitive 17) src/FsMcp.Client/McpClient.fs:429
- EnterpriseTokenExchangeSecurityHandler.SendAsync (cognitive 17) src/FsMcp.Client/EnterpriseManagedAuthorization.fs:596
- FileTooLong: FsMcp.Client/EnterpriseManagedAuthorization.fs src/FsMcp.Client/EnterpriseManagedAuthorization.fs
- TooManyFunctions: McpClientModule src/FsMcp.Client/McpClient.fs:113
- Duplicated block (17–18 lines × 3) src/FsMcp.Server/Streaming.fs:67
- Duplicated block (9 lines × 2) src/FsMcp.Server/Transport.fs:172
- Duplicated block (18 lines × 2) src/FsMcp.Server/TypedHandlers.fs:211
- Coverage collected but not gated
Minor — 100 finding(s)
- Outdated (npm): @pnpm/config.env-replace
- Outdated (npm): @pnpm/network.ca-file
- Outdated (npm): @sindresorhus/is
- Outdated (npm): @types/mime
- Outdated (npm): balanced-match
- Outdated (npm): brace-expansion
- Outdated (npm): cacheable-request
- Outdated (npm): camelcase
- Outdated (npm): chokidar
- Outdated (npm): clean-stack
- Outdated (npm): commander
- Outdated (npm): content-disposition
- Outdated (npm): copy-webpack-plugin
- Outdated (npm): css-minimizer-webpack-plugin
- Outdated (npm): cssnano
- Outdated (npm): cssnano-preset-advanced
- Outdated (npm): cssnano-preset-default
- Outdated (npm): cssnano-utils
- Outdated (npm): debounce
- Outdated (npm): decompress-response
- Outdated (npm): dot-prop
- Outdated (npm): eslint-scope
- Outdated (npm): execa
- Outdated (npm): get-stream
- Outdated (npm): globby
- Deprecated: Microsoft.Testing.Platform.MSBuild tests/FsMcp.Client.Tests/packages.lock.json:404
- Deprecated: Microsoft.Testing.Platform.MSBuild tests/FsMcp.Core.Tests/packages.lock.json:189
- Deprecated: Microsoft.Testing.Platform.MSBuild tests/FsMcp.Sampling.Tests/packages.lock.json:385
- Deprecated: Microsoft.Testing.Platform.MSBuild tests/FsMcp.Server.Http.Tests/packages.lock.json:156
- Deprecated: Microsoft.Testing.Platform.MSBuild tests/FsMcp.Server.Tests/packages.lock.json:405
- Deprecated: Microsoft.Testing.Platform.MSBuild tests/FsMcp.TaskApi.Tests/packages.lock.json:186
- Deprecated: Microsoft.Testing.Platform.MSBuild tests/FsMcp.Testing.Tests/packages.lock.json:404
- Scattered collaborators
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No SAST .github/workflows/ci.yml:6
- No dependency-update automation Directory.Build.props:39
Minor — 554 finding(s)
- Outdated (npm): @11ty/gray-matter
- Outdated (npm): @algolia/abtesting
- Outdated (npm): @algolia/autocomplete-core
- Outdated (npm): @algolia/autocomplete-plugin-algolia-insights
- Outdated (npm): @algolia/autocomplete-shared
- Outdated (npm): @algolia/client-abtesting
- Outdated (npm): @algolia/client-analytics
- Outdated (npm): @algolia/client-common
- Outdated (npm): @algolia/client-insights
- Outdated (npm): @algolia/client-personalization
- Outdated (npm): @algolia/client-query-suggestions
- Outdated (npm): @algolia/client-search
- Outdated (npm): @algolia/ingestion
- Outdated (npm): @algolia/monitoring
- Outdated (npm): @algolia/recommend
- Outdated (npm): @algolia/requester-browser-xhr
- Outdated (npm): @algolia/requester-fetch
- Outdated (npm): @algolia/requester-node-http
- Outdated (npm): @babel/code-frame
- Outdated (npm): @babel/compat-data
- Outdated (npm): @babel/core
- Outdated (npm): @babel/generator
- Outdated (npm): @babel/helper-annotate-as-pure
- Outdated (npm): @babel/helper-compilation-targets
- Outdated (npm): @babel/helper-create-class-features-plugin
- Outdated: FSharp.Core
- Outdated: Ionide.Analyzers
- Outdated: ModelContextProtocol
- Outdated: Microsoft.Extensions.Logging.Abstractions
- Outdated: ModelContextProtocol.AspNetCore
- Outdated: Microsoft.Extensions.Hosting
- Outdated: Microsoft.Extensions.Logging.Console
- Outdated: Expecto
- Outdated: Expecto.FsCheck
- Outdated: FsCheck
- Outdated: coverlet.collector
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: YoloDev.Expecto.TestSdk
- Outdated: Microsoft.AspNetCore.TestHost
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e76309fccfce4ffc954b4241d468a196/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e76309fccfce4ffc954b4241d468a196/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list FsMcp.slnx package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `website/docusaurus.config.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |