Executive summary
ThreeMammals/Ocelot is rated At risk because critical security findings are open. Its score is held back in part because it has unsafe settings in infrastructure or container files. It scores 45 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 36, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the two exposed passwords or keys and switching the old ones off, worth about 4 points. Restoring certificate checks would lift Security and Compliance itself, worth about 7 points. Raising Security and Compliance to 70 would lift the score to about 53.
Eighteen settings leave the servers or containers unsafe. Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and four secrets can leak from the build pipeline. Correcting the unsafe settings, pinning each tool to an exact version and limiting each secret to its own step would close these risks. Loading the key from a secret store instead of the code would fix the encryption key written into the code, and the two passwords or keys in the code and the two passwords or keys in the code's history need replacing, with the old ones switched off. The 15 data fields that are written but never read need removing.
The product code is 18,919 lines, about €56,000 to rebuild.
If Security and Compliance rose from 36 to 70, the lowest score rated Strong, the score would rise from 45 to about 53.
New since the last survey: 40 findings
- Code Duplication · Edited copy of a member (41 corresponding lines) src/Configuration/Repository/FileConfigurationPoller.cs
- Code Duplication · Edited copy of a member (35 corresponding lines) src/Infrastructure/DesignPatterns/Retry.cs
- Code Duplication · Edited copy of a member (28 corresponding lines) src/Configuration/Creator/CacheOptionsCreator.cs
- Code Duplication · Edited copy of a member (28 corresponding lines) src/Configuration/Creator/LoadBalancerOptionsCreator.cs
- Code Duplication · Edited copy of a member (10 corresponding lines) src/DependencyInjection/ConfigurationBuilderExtensions.cs
- Code Duplication · Edited copy of a member (24 corresponding lines) src/Configuration/Creator/AuthenticationOptionsCreator.cs
- Code Duplication · Edited copy of a member (22 corresponding lines) src/Headers/AddHeadersToRequest.cs
- Code Duplication · Edited copy of a member (22 corresponding lines) src/Headers/Middleware/ClaimsToHeadersMiddleware.cs
- Code Duplication · Edited copy of a member (21 corresponding lines) src/Headers/AddHeadersToRequest.cs
- Code Duplication · Edited copy of a member (22 corresponding lines) src/Configuration/Repository/DiskFileConfigurationRepository.cs
- Code Duplication · Edited copy of a member (9 corresponding lines) testing/Ocelot.cs
- Code Duplication · Edited copy of a member (13 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (17 corresponding lines) testing/AcceptanceSteps.cs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/Configuration/File/FileSecurityOptions.cs
- Code Duplication · Edited copy of a member (6 corresponding lines) src/LoadBalancer/Balancers/LeastConnection.cs
- Code Duplication · Edited copy of a member (7 corresponding lines) src/Configuration/File/FileMetadataOptions.cs
- Code Duplication · Edited copy of a member (4 corresponding lines) src/Configuration/Creator/DynamicRoutesCreator.cs
- Code Duplication · Edited copy of a member (4 corresponding lines) src/Logging/OcelotLogger.cs
- Code Duplication · Duplicated block (7 lines × 2) samples/Kubernetes/DownstreamService/Program.cs
- Cohesion (LCOM4) · Low cohesion: WebSocketsSteps (LCOM4 4) REDACTED
- Test Quality · No assertions: ShouldProxyWebsocketInputToDownstreamServiceAndUseLoadBalancer acceptance/WebSockets/WebSocketsFactoryTests.cs
- Test Quality · Fixed-sleep synchronisation: StopAsync_Should_prevent_new_timer_callbacks_after_change unit/Configuration/Repository/FileConfigurationPollerTests.cs
- Test Quality · Fixed-sleep synchronisation: StopAsync_Should_prevent_new_callbacks_and_complete unit/Configuration/Repository/FileConfigurationPollerTests.cs
- Test Quality · Fixed-sleep synchronisation: StopAsync_Should_prevent_use_of_disposed_timer_from_callbacks unit/Configuration/Repository/FileConfigurationPollerTests.cs
- Test Quality · Fixed-sleep synchronisation: Multiple_Start_Stop_Cycles_Should_work_correctly unit/Configuration/Repository/FileConfigurationPollerTests.cs
- Test Quality · Fixed-sleep synchronisation: StopAsync_Should_log_warning_when_timer_disposal_exceeds_timeout unit/Configuration/Repository/FileConfigurationPollerTests.cs
- Explicit Debt · TodoComment acceptance/Aggregation/AggregateTests.cs
- Explicit Debt · TodoComment acceptance/Aggregation/AggregateTests.cs
- Explicit Debt · TodoComment acceptance/QualityOfService/QualityOfServiceTests.cs
- Explicit Debt · TodoComment src/Multiplexer/MultiplexingMiddleware.cs
- Explicit Debt · TodoComment src/Multiplexer/SimpleJsonResponseAggregator.cs
- Explicit Debt · TodoComment src/Multiplexer/SimpleJsonResponseAggregator.cs
- Explicit Debt · TodoComment REDACTED
- Static Analysis (SAST) · REDACTED
- Stateful singletons · Stateful shared instance: RateLimitRule src/Configuration/RateLimitRule.cs
- Stateful singletons · Process-global static state: DownstreamRoute src/Configuration/DownstreamRoute.cs
- Stateful singletons · Process-global static state: ConfigurationBuilderExtensions src/DependencyInjection/ConfigurationBuilderExtensions.cs
- Stateful singletons · Process-global static state: Ocelot testing/Ocelot.cs
- Test isolation · Production project references a test package: Ocelot.Testing → Moq testing/Ocelot.Testing.csproj
- Test isolation · Production project references a test package: Ocelot.Testing → Shouldly testing/Ocelot.Testing.csproj
Fixed since the last survey: 165 findings
- Secret Scanning · Leaked secret: high-entropy-secret samples/Kubernetes/ApiGateway/ocelot.json
- Explicit Debt · CommentedOutCode acceptance/Properties/BddfyConfig.cs
- Explicit Debt · CommentedOutCode acceptance/RateLimiting/ClientHeaderRateLimitingTests.cs
- Explicit Debt · CommentedOutCode acceptance/RateLimiting/ClientHeaderRateLimitingTests.cs
- Explicit Debt · CommentedOutCode acceptance/Authentication/AuthenticationTests.cs
- Explicit Debt · CommentedOutCode acceptance/Authentication/AuthenticationTests.cs
- Explicit Debt · CommentedOutCode acceptance/Properties/BddfyConfig.cs
- Explicit Debt · TodoComment acceptance/QualityOfService/QualityOfServiceTests.cs
- Explicit Debt · TodoComment acceptance/QualityOfService/QualityOfServiceTests.cs
- Explicit Debt · CommentedOutCode acceptance/Request/StreamContentTests.cs
- Explicit Debt · TodoComment src/DependencyInjection/OcelotBuilder.cs
- Explicit Debt · Dead code: AndIf acceptance/IFluentStepBuilderExtensions.cs
- Explicit Debt · Dead code: AndIfNot acceptance/IFluentStepBuilderExtensions.cs
- Secrets (history) · Secret: generic-api-key docs/features/kubernetes.rst
- Secrets (history) · Secret: generic-api-key samples/Kubernetes/ApiGateway/ocelot.json
- Secrets (history) · Secret: generic-api-key samples/OcelotKube/ApiGateway/ocelot.json
- Secrets (history) · Secret: generic-api-key samples/OelotKube/ApiGateway/ocelot.json
- Cancellation propagation · Async method without CancellationToken: WhenIGetUrlOnTheApiGatewayWithCookie testing/AcceptanceSteps.cs
- Cancellation propagation · Async method without CancellationToken: WhenIGetUrlOnTheApiGatewayWithCookie testing/AcceptanceSteps.cs
- Cancellation propagation · Async method without CancellationToken: ReleasePortAsync testing/ServiceHandler.cs
- Cancellation propagation · Async method without CancellationToken: GivenThereIsAServiceRunningOnAsync testing/ServiceHandler.cs
- Cancellation propagation · Async method without CancellationToken: WatchWhenIGetUrlOnTheApiGateway testing/Steps/TimeoutSteps.cs
- Cancellation propagation · Async method without CancellationToken: StartOcelotWithWebSockets REDACTED
- Cancellation propagation · Async method drops its CancellationToken: StopAsync src/Configuration/Repository/FileConfigurationPoller.cs
- Incompleteness & stubs · Skipped test marks a known-real bug acceptance/Aggregation/AggregateTests.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Configuration/Repository/FileConfigurationPoller.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Configuration/Repository/FileConfigurationPoller.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Configuration/Repository/FileConfigurationPoller.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Configuration/Repository/ServiceDiscoveryFileConfigurationPollerOptions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Configuration/Validator/FileAuthenticationOptionsValidator.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Configuration/Validator/FileConfigurationFluentValidator.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/DownstreamPathManipulation/Middleware/ClaimsToDownstreamPathMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/DownstreamRouteFinder/DownstreamRouteFinderMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/DownstreamUrlCreator/DownstreamUrlCreatorMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Errors/ExceptionHandlerMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Headers/Middleware/ClaimsToHeadersMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Headers/Middleware/HttpHeadersTransformationMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/DesignPatterns/Retry.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/DesignPatterns/Retry.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/DesignPatterns/Retry.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/DesignPatterns/Retry.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Infrastructure/InMemoryBus.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/LoadBalancer/Balancers/LeastConnection.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/LoadBalancer/Balancers/NoLoadBalancer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/LoadBalancer/Balancers/NoLoadBalancer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/LoadBalancer/Balancers/RoundRobin.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/LoadBalancer/Creators/NoLoadBalancerCreator.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/LoadBalancer/LoadBalancingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/LoadBalancer/LoadBalancingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Middleware/ConfigurationMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Middleware/OcelotMiddlewareExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Middleware/OcelotMiddlewareExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Middleware/OcelotMiddlewareExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Middleware/OcelotMiddlewareExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Middleware/OcelotMiddlewareExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Middleware/OcelotMiddlewareExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Middleware/OcelotMiddlewareExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Middleware/OcelotMiddlewareExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/MultiplexingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/SimpleJsonResponseAggregator.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/SimpleJsonResponseAggregator.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/SimpleJsonResponseAggregator.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Multiplexer/UserDefinedResponseAggregator.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/QualityOfService/CircuitBreakerDelegatingHandler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/QualityOfService/CircuitBreakerDelegatingHandler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/QualityOfService/CircuitBreakerDelegatingHandler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/QualityOfService/CircuitBreakerDelegatingHandler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/QueryStrings/ClaimsToQueryStringMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Request/Mapper/StreamHttpContent.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Request/Mapper/StreamHttpContent.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Request/Mapper/StreamHttpContent.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Request/Mapper/StreamHttpContent.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Request/Middleware/DownstreamRequestInitialiserMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Requester/MessageInvokerHttpRequester.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Requester/Middleware/HttpRequesterMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Requester/Middleware/HttpRequesterMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Requester/TimeoutDelegatingHandler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/RequestId/Middleware/RequestIdMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Responder/HttpContextResponder.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Responder/HttpContextResponder.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Responder/HttpContextResponder.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Responder/HttpContextResponder.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Responder/HttpContextResponder.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Responder/Middleware/ResponderMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Responder/Middleware/ResponderMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Responder/Middleware/ResponderMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Responder/Middleware/ResponderMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Security/SecurityMiddleware.cs
Rebuild cost: about €56,000 · Estimate
| Cost to rebuild | €19,000 to €93,000, for 310 to 981 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 45. 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: 18,919 lines of product code |
| Comment lines | The estimate prices 16,584 lines. Comment lines count towards the size of 18,919 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Values | 2 Configuration.File | 3 Responses | 4 ServiceDiscovery.Providers | 5 DownstreamRouteFinder.UrlMatcher | 6 Infrastructure.RequestData | 7 Logging | 8 Configuration.Repository | 9 Request.Middleware | 10 Middleware | 11 Errors | 12 RequestId.Middleware | 13 Configuration.Parser | 14 Infrastructure | 15 Infrastructure.Claims | 16 ServiceDiscovery | 17 Authorization | 18 Configuration.Validator | 19 Configuration.Creator | 20 Configuration | 21 Cache | 22 Claims | 23 DependencyInjection | 24 DownstreamRouteFinder.Finder | 25 DownstreamUrlCreator | 26 Headers | 27 LoadBalancer.Interfaces | 28 Multiplexer | 29 PathManipulation | 30 QualityOfService | 31 QueryStrings | 32 RateLimiting | 33 Security | 34 Administration | 35 LoadBalancer | 36 LoadBalancer.Creators | 37 Requester | 38 Responder | 39 LoadBalancer.Balancers | 40 Requester.Middleware |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Values | ||||||||||||||||||||||||||||||||||||||||
| 2 Configuration.File | 2 | |||||||||||||||||||||||||||||||||||||||
| 3 Responses | 2 | |||||||||||||||||||||||||||||||||||||||
| 4 ServiceDiscovery.Providers | 3 | |||||||||||||||||||||||||||||||||||||||
| 5 DownstreamRouteFinder.UrlMatcher | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 6 Infrastructure.RequestData | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 7 Logging | 4 | |||||||||||||||||||||||||||||||||||||||
| 8 Configuration.Repository | 6 | 2 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 9 Request.Middleware | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 Middleware | 1 | 1 | 2 | 1 | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||
| 11 Errors | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 12 RequestId.Middleware | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 13 Configuration.Parser | 2 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 14 Infrastructure | 3 | 1 | 3 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 15 Infrastructure.Claims | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 ServiceDiscovery | 2 | 3 | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||||
| 17 Authorization | 1 | 4 | 2 | 1 | 1 | 4 | 2 | |||||||||||||||||||||||||||||||||
| 18 Configuration.Validator | 8 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 Configuration.Creator | 4 | 102 | 2 | 5 | 1 | 1 | 1 | 40 | 1 | 1 | ||||||||||||||||||||||||||||||
| 20 Configuration | 5 | 8 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 Cache | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 22 Claims | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 DependencyInjection | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 24 DownstreamRouteFinder.Finder | 3 | 2 | 2 | 1 | 2 | 9 | ||||||||||||||||||||||||||||||||||
| 25 DownstreamUrlCreator | 3 | 3 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 26 Headers | 8 | 4 | 2 | 4 | 3 | 1 | 4 | 6 | ||||||||||||||||||||||||||||||||
| 27 LoadBalancer.Interfaces | 1 | 4 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 28 Multiplexer | 1 | 2 | 1 | 1 | 3 | 1 | 9 | |||||||||||||||||||||||||||||||||
| 29 PathManipulation | 2 | 2 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 30 QualityOfService | 6 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 31 QueryStrings | 2 | 1 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 32 RateLimiting | 1 | 2 | 1 | 6 | ||||||||||||||||||||||||||||||||||||
| 33 Security | 2 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 34 Administration | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 35 LoadBalancer | 3 | 2 | 1 | 1 | 1 | 4 | 7 | |||||||||||||||||||||||||||||||||
| 36 LoadBalancer.Creators | 5 | 5 | 5 | 10 | ||||||||||||||||||||||||||||||||||||
| 37 Requester | 2 | 7 | 6 | 5 | 1 | |||||||||||||||||||||||||||||||||||
| 38 Responder | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 LoadBalancer.Balancers | 7 | 4 | 1 | 4 | 5 | |||||||||||||||||||||||||||||||||||
| 40 Requester.Middleware | 1 | 1 | 1 | 1 |
2→20 Configuration.File uses Configuration part of a loop✕
- Connections
- 2 pairs of types, where a type in Configuration.File uses a type in Configuration.
- The types involved
Ocelot.Configuration.File.FileGlobalQoSOptions→Ocelot.Configuration.QoSOptionsOcelot.Configuration.File.FileQoSOptions→Ocelot.Configuration.QoSOptions
- Direction
- Configuration.File uses Configuration, so a change to Configuration can break Configuration.File, while a change to Configuration.File can't break Configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→11 Responses uses Errors part of a loop✕
- Connections
- 2 pairs of types, where a type in Responses uses a type in Errors.
- The types involved
Ocelot.Responses.ErrorResponse→Ocelot.Errors.ErrorOcelot.Responses.Response→Ocelot.Errors.Error
- Direction
- Responses uses Errors, so a change to Errors can break Responses, while a change to Responses can't break Errors.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→1 ServiceDiscovery.Providers uses Values✕
- Connections
- 3 pairs of types, where a type in ServiceDiscovery.Providers uses a type in Values.
- The types involved
Ocelot.ServiceDiscovery.Providers.ConfigurationServiceProvider→Ocelot.Values.ServiceOcelot.ServiceDiscovery.Providers.IServiceDiscoveryProvider→Ocelot.Values.ServiceOcelot.ServiceDiscovery.Providers.ServiceFabricServiceDiscoveryProvider→Ocelot.Values.Service
- Direction
- ServiceDiscovery.Providers uses Values, so a change to Values can break ServiceDiscovery.Providers, while a change to ServiceDiscovery.Providers can't break Values.
- Position
- Below the diagonal: ServiceDiscovery.Providers uses a module listed above it, which is the healthy direction.
5→1 DownstreamRouteFinder.UrlMatcher uses Values✕
- Connections
- 2 pairs of types, where a type in DownstreamRouteFinder.UrlMatcher uses a type in Values.
- The types involved
Ocelot.DownstreamRouteFinder.UrlMatcher.IUrlPathToUrlTemplateMatcher→Ocelot.Values.UpstreamPathTemplateOcelot.DownstreamRouteFinder.UrlMatcher.RegExUrlMatcher→Ocelot.Values.UpstreamPathTemplate
- Direction
- DownstreamRouteFinder.UrlMatcher uses Values, so a change to Values can break DownstreamRouteFinder.UrlMatcher, while a change to DownstreamRouteFinder.UrlMatcher can't break Values.
- Position
- Below the diagonal: DownstreamRouteFinder.UrlMatcher uses a module listed above it, which is the healthy direction.
5→3 DownstreamRouteFinder.UrlMatcher uses Responses✕
- Connections
- 2 pairs of types, where a type in DownstreamRouteFinder.UrlMatcher uses a type in Responses.
- The types involved
Ocelot.DownstreamRouteFinder.UrlMatcher.IPlaceholderNameAndValueFinder→Ocelot.Responses.ResponseOcelot.DownstreamRouteFinder.UrlMatcher.UrlPathPlaceholderNameAndValueFinder→Ocelot.Responses.Response
- Direction
- DownstreamRouteFinder.UrlMatcher uses Responses, so a change to Responses can break DownstreamRouteFinder.UrlMatcher, while a change to DownstreamRouteFinder.UrlMatcher can't break Responses.
- Position
- Below the diagonal: DownstreamRouteFinder.UrlMatcher uses a module listed above it, which is the healthy direction.
6→3 Infrastructure.RequestData uses Responses✕
- Connections
- 2 pairs of types, where a type in Infrastructure.RequestData uses a type in Responses.
- The types involved
Ocelot.Infrastructure.RequestData.HttpDataRepository→Ocelot.Responses.ResponseOcelot.Infrastructure.RequestData.IRequestScopedDataRepository→Ocelot.Responses.Response
- Direction
- Infrastructure.RequestData uses Responses, so a change to Responses can break Infrastructure.RequestData, while a change to Infrastructure.RequestData can't break Responses.
- Position
- Below the diagonal: Infrastructure.RequestData uses a module listed above it, which is the healthy direction.
6→11 Infrastructure.RequestData uses Errors part of a loop✕
- Connections
- 2 pairs of types, where a type in Infrastructure.RequestData uses a type in Errors.
- The types involved
Ocelot.Infrastructure.RequestData.CannotAddDataError→Ocelot.Errors.ErrorOcelot.Infrastructure.RequestData.CannotFindDataError→Ocelot.Errors.Error
- Direction
- Infrastructure.RequestData uses Errors, so a change to Errors can break Infrastructure.RequestData, while a change to Infrastructure.RequestData can't break Errors.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→6 Logging uses Infrastructure.RequestData✕
- Connections
- 4 pairs of types, where a type in Logging uses a type in Infrastructure.RequestData.
- The types involved
Ocelot.Logging.OcelotHttpTracingHandler→Ocelot.Infrastructure.RequestData.IRequestScopedDataRepositoryOcelot.Logging.OcelotLogger→Ocelot.Infrastructure.RequestData.IRequestScopedDataRepositoryOcelot.Logging.OcelotLoggerFactory→Ocelot.Infrastructure.RequestData.IRequestScopedDataRepositoryOcelot.Logging.TracingHandlerFactory→Ocelot.Infrastructure.RequestData.IRequestScopedDataRepository
- Direction
- Logging uses Infrastructure.RequestData, so a change to Infrastructure.RequestData can break Logging, while a change to Logging can't break Infrastructure.RequestData.
- Position
- Below the diagonal: Logging uses a module listed above it, which is the healthy direction.
8→2 Configuration.Repository uses Configuration.File✕
- Connections
- 6 pairs of types, where a type in Configuration.Repository uses a type in Configuration.File.
- The types involved
Ocelot.Configuration.Repository.DiskFileConfigurationRepository→Ocelot.Configuration.File.FileConfigurationOcelot.Configuration.Repository.FileAndInternalConfigurationSetter→Ocelot.Configuration.File.FileConfigurationOcelot.Configuration.Repository.FileConfigurationPoller→Ocelot.Configuration.File.FileConfigurationOcelot.Configuration.Repository.IFileConfigurationRepository→Ocelot.Configuration.File.FileConfigurationOcelot.Configuration.Repository.IFileConfigurationSetter→Ocelot.Configuration.File.FileConfigurationOcelot.Configuration.Repository.ServiceDiscoveryFileConfigurationPollerOptions→Ocelot.Configuration.File.FileConfiguration
- Direction
- Configuration.Repository uses Configuration.File, so a change to Configuration.File can break Configuration.Repository, while a change to Configuration.Repository can't break Configuration.File.
- Position
- Below the diagonal: Configuration.Repository uses a module listed above it, which is the healthy direction.
8→7 Configuration.Repository uses Logging✕
- Connections
- 2 pairs of types, where a type in Configuration.Repository uses a type in Logging.
- The types involved
Ocelot.Configuration.Repository.FileConfigurationPoller→Ocelot.Logging.IOcelotLoggerOcelot.Configuration.Repository.FileConfigurationPoller→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- Configuration.Repository uses Logging, so a change to Logging can break Configuration.Repository, while a change to Configuration.Repository can't break Logging.
- Position
- Below the diagonal: Configuration.Repository uses a module listed above it, which is the healthy direction.
8→11 Configuration.Repository uses Errors part of a loop✕
- Connections
- 1 pair of types, where a type in Configuration.Repository uses a type in Errors.
- The types involved
Ocelot.Configuration.Repository.ConfigurationRepositoryException→Ocelot.Errors.Error
- Direction
- Configuration.Repository uses Errors, so a change to Errors can break Configuration.Repository, while a change to Configuration.Repository can't break Errors.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→19 Configuration.Repository uses Configuration.Creator part of a loop✕
- Connections
- 2 pairs of types, where a type in Configuration.Repository uses a type in Configuration.Creator.
- The types involved
Ocelot.Configuration.Repository.FileAndInternalConfigurationSetter→Ocelot.Configuration.Creator.IInternalConfigurationCreatorOcelot.Configuration.Repository.FileConfigurationPoller→Ocelot.Configuration.Creator.IInternalConfigurationCreator
- Direction
- Configuration.Repository uses Configuration.Creator, so a change to Configuration.Creator can break Configuration.Repository, while a change to Configuration.Repository can't break Configuration.Creator.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→20 Configuration.Repository uses Configuration part of a loop✕
- Connections
- 2 pairs of types, where a type in Configuration.Repository uses a type in Configuration.
- The types involved
Ocelot.Configuration.Repository.IInternalConfigurationRepository→Ocelot.Configuration.IInternalConfigurationOcelot.Configuration.Repository.InMemoryInternalConfigurationRepository→Ocelot.Configuration.IInternalConfiguration
- Direction
- Configuration.Repository uses Configuration, so a change to Configuration can break Configuration.Repository, while a change to Configuration.Repository can't break Configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→7 Request.Middleware uses Logging✕
- Connections
- 1 pair of types, where a type in Request.Middleware uses a type in Logging.
- The types involved
Ocelot.Request.Middleware.DownstreamRequestInitialiserMiddleware→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- Request.Middleware uses Logging, so a change to Logging can break Request.Middleware, while a change to Request.Middleware can't break Logging.
- Position
- Below the diagonal: Request.Middleware uses a module listed above it, which is the healthy direction.
9→10 Request.Middleware uses Middleware part of a loop✕
- Connections
- 1 pair of types, where a type in Request.Middleware uses a type in Middleware.
- The types involved
Ocelot.Request.Middleware.DownstreamRequestInitialiserMiddleware→Ocelot.Middleware.OcelotMiddleware
- Direction
- Request.Middleware uses Middleware, so a change to Middleware can break Request.Middleware, while a change to Request.Middleware can't break Middleware.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→3 Middleware uses Responses✕
- Connections
- 1 pair of types, where a type in Middleware uses a type in Responses.
- The types involved
Ocelot.Middleware.OcelotMiddlewareExtensions→Ocelot.Responses.Response
- Direction
- Middleware uses Responses, so a change to Responses can break Middleware, while a change to Middleware can't break Responses.
- Position
- Below the diagonal: Middleware uses a module listed above it, which is the healthy direction.
10→5 Middleware uses DownstreamRouteFinder.UrlMatcher✕
- Connections
- 1 pair of types, where a type in Middleware uses a type in DownstreamRouteFinder.UrlMatcher.
- The types involved
Ocelot.Middleware.HttpItemsExtensions→Ocelot.DownstreamRouteFinder.UrlMatcher.PlaceholderNameAndValue
- Direction
- Middleware uses DownstreamRouteFinder.UrlMatcher, so a change to DownstreamRouteFinder.UrlMatcher can break Middleware, while a change to Middleware can't break DownstreamRouteFinder.UrlMatcher.
- Position
- Below the diagonal: Middleware uses a module listed above it, which is the healthy direction.
10→7 Middleware uses Logging✕
- Connections
- 2 pairs of types, where a type in Middleware uses a type in Logging.
- The types involved
Ocelot.Middleware.ConfigurationMiddleware→Ocelot.Logging.IOcelotLoggerFactoryOcelot.Middleware.OcelotMiddleware→Ocelot.Logging.IOcelotLogger
- Direction
- Middleware uses Logging, so a change to Logging can break Middleware, while a change to Middleware can't break Logging.
- Position
- Below the diagonal: Middleware uses a module listed above it, which is the healthy direction.
10→8 Middleware uses Configuration.Repository✕
- Connections
- 1 pair of types, where a type in Middleware uses a type in Configuration.Repository.
- The types involved
Ocelot.Middleware.ConfigurationMiddleware→Ocelot.Configuration.Repository.IInternalConfigurationRepository
- Direction
- Middleware uses Configuration.Repository, so a change to Configuration.Repository can break Middleware, while a change to Middleware can't break Configuration.Repository.
- Position
- Below the diagonal: Middleware uses a module listed above it, which is the healthy direction.
10→9 Middleware uses Request.Middleware✕
- Connections
- 1 pair of types, where a type in Middleware uses a type in Request.Middleware.
- The types involved
Ocelot.Middleware.HttpItemsExtensions→Ocelot.Request.Middleware.DownstreamRequest
- Direction
- Middleware uses Request.Middleware, so a change to Request.Middleware can break Middleware, while a change to Middleware can't break Request.Middleware.
- Position
- Below the diagonal: Middleware uses a module listed above it, which is the healthy direction.
10→11 Middleware uses Errors part of a loop✕
- Connections
- 2 pairs of types, where a type in Middleware uses a type in Errors.
- The types involved
Ocelot.Middleware.HttpItemsExtensions→Ocelot.Errors.ErrorOcelot.Middleware.UnauthenticatedError→Ocelot.Errors.Error
- Direction
- Middleware uses Errors, so a change to Errors can break Middleware, while a change to Middleware can't break Errors.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→20 Middleware uses Configuration part of a loop✕
- Connections
- 4 pairs of types, where a type in Middleware uses a type in Configuration.
- The types involved
Ocelot.Middleware.HttpItemsExtensions→Ocelot.Configuration.DownstreamRouteOcelot.Middleware.HttpItemsExtensions→Ocelot.Configuration.IInternalConfigurationOcelot.Middleware.HttpItemsExtensions→Ocelot.Configuration.RouteOcelot.Middleware.OcelotMiddlewareExtensions→Ocelot.Configuration.IInternalConfiguration
- Direction
- Middleware uses Configuration, so a change to Configuration can break Middleware, while a change to Middleware can't break Configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→6 Errors uses Infrastructure.RequestData✕
- Connections
- 1 pair of types, where a type in Errors uses a type in Infrastructure.RequestData.
- The types involved
Ocelot.Errors.ExceptionHandlerMiddleware→Ocelot.Infrastructure.RequestData.IRequestScopedDataRepository
- Direction
- Errors uses Infrastructure.RequestData, so a change to Infrastructure.RequestData can break Errors, while a change to Errors can't break Infrastructure.RequestData.
- Position
- Below the diagonal: Errors uses a module listed above it, which is the healthy direction.
11→7 Errors uses Logging✕
- Connections
- 1 pair of types, where a type in Errors uses a type in Logging.
- The types involved
Ocelot.Errors.ExceptionHandlerMiddleware→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- Errors uses Logging, so a change to Logging can break Errors, while a change to Errors can't break Logging.
- Position
- Below the diagonal: Errors uses a module listed above it, which is the healthy direction.
11→10 Errors uses Middleware✕
- Connections
- 1 pair of types, where a type in Errors uses a type in Middleware.
- The types involved
Ocelot.Errors.ExceptionHandlerMiddleware→Ocelot.Middleware.OcelotMiddleware
- Direction
- Errors uses Middleware, so a change to Middleware can break Errors, while a change to Errors can't break Middleware.
- Position
- Below the diagonal: Errors uses a module listed above it, which is the healthy direction.
11→20 Errors uses Configuration part of a loop✕
- Connections
- 1 pair of types, where a type in Errors uses a type in Configuration.
- The types involved
Ocelot.Errors.ExceptionHandlerMiddleware→Ocelot.Configuration.IInternalConfiguration
- Direction
- Errors uses Configuration, so a change to Configuration can break Errors, while a change to Errors can't break Configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→6 RequestId.Middleware uses Infrastructure.RequestData✕
- Connections
- 1 pair of types, where a type in RequestId.Middleware uses a type in Infrastructure.RequestData.
- The types involved
Ocelot.RequestId.Middleware.RequestIdMiddleware→Ocelot.Infrastructure.RequestData.IRequestScopedDataRepository
- Direction
- RequestId.Middleware uses Infrastructure.RequestData, so a change to Infrastructure.RequestData can break RequestId.Middleware, while a change to RequestId.Middleware can't break Infrastructure.RequestData.
- Position
- Below the diagonal: RequestId.Middleware uses a module listed above it, which is the healthy direction.
12→7 RequestId.Middleware uses Logging✕
- Connections
- 1 pair of types, where a type in RequestId.Middleware uses a type in Logging.
- The types involved
Ocelot.RequestId.Middleware.RequestIdMiddleware→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- RequestId.Middleware uses Logging, so a change to Logging can break RequestId.Middleware, while a change to RequestId.Middleware can't break Logging.
- Position
- Below the diagonal: RequestId.Middleware uses a module listed above it, which is the healthy direction.
12→9 RequestId.Middleware uses Request.Middleware✕
- Connections
- 1 pair of types, where a type in RequestId.Middleware uses a type in Request.Middleware.
- The types involved
Ocelot.RequestId.Middleware.RequestIdMiddleware→Ocelot.Request.Middleware.DownstreamRequest
- Direction
- RequestId.Middleware uses Request.Middleware, so a change to Request.Middleware can break RequestId.Middleware, while a change to RequestId.Middleware can't break Request.Middleware.
- Position
- Below the diagonal: RequestId.Middleware uses a module listed above it, which is the healthy direction.
12→10 RequestId.Middleware uses Middleware✕
- Connections
- 1 pair of types, where a type in RequestId.Middleware uses a type in Middleware.
- The types involved
Ocelot.RequestId.Middleware.RequestIdMiddleware→Ocelot.Middleware.OcelotMiddleware
- Direction
- RequestId.Middleware uses Middleware, so a change to Middleware can break RequestId.Middleware, while a change to RequestId.Middleware can't break Middleware.
- Position
- Below the diagonal: RequestId.Middleware uses a module listed above it, which is the healthy direction.
13→3 Configuration.Parser uses Responses✕
- Connections
- 2 pairs of types, where a type in Configuration.Parser uses a type in Responses.
- The types involved
Ocelot.Configuration.Parser.ClaimToThingConfigurationParser→Ocelot.Responses.ResponseOcelot.Configuration.Parser.IClaimToThingConfigurationParser→Ocelot.Responses.Response
- Direction
- Configuration.Parser uses Responses, so a change to Responses can break Configuration.Parser, while a change to Configuration.Parser can't break Responses.
- Position
- Below the diagonal: Configuration.Parser uses a module listed above it, which is the healthy direction.
13→11 Configuration.Parser uses Errors✕
- Connections
- 3 pairs of types, where a type in Configuration.Parser uses a type in Errors.
- The types involved
Ocelot.Configuration.Parser.InstructionNotForClaimsError→Ocelot.Errors.ErrorOcelot.Configuration.Parser.NoInstructionsError→Ocelot.Errors.ErrorOcelot.Configuration.Parser.ParsingConfigurationHeaderError→Ocelot.Errors.Error
- Direction
- Configuration.Parser uses Errors, so a change to Errors can break Configuration.Parser, while a change to Configuration.Parser can't break Errors.
- Position
- Below the diagonal: Configuration.Parser uses a module listed above it, which is the healthy direction.
13→20 Configuration.Parser uses Configuration part of a loop✕
- Connections
- 2 pairs of types, where a type in Configuration.Parser uses a type in Configuration.
- The types involved
Ocelot.Configuration.Parser.ClaimToThingConfigurationParser→Ocelot.Configuration.ClaimToThingOcelot.Configuration.Parser.IClaimToThingConfigurationParser→Ocelot.Configuration.ClaimToThing
- Direction
- Configuration.Parser uses Configuration, so a change to Configuration can break Configuration.Parser, while a change to Configuration.Parser can't break Configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→3 Infrastructure uses Responses✕
- Connections
- 3 pairs of types, where a type in Infrastructure uses a type in Responses.
- The types involved
Ocelot.Infrastructure.ConfigAwarePlaceholders→Ocelot.Responses.ResponseOcelot.Infrastructure.IPlaceholders→Ocelot.Responses.ResponseOcelot.Infrastructure.Placeholders→Ocelot.Responses.Response
- Direction
- Infrastructure uses Responses, so a change to Responses can break Infrastructure, while a change to Infrastructure can't break Responses.
- Position
- Below the diagonal: Infrastructure uses a module listed above it, which is the healthy direction.
14→6 Infrastructure uses Infrastructure.RequestData✕
- Connections
- 1 pair of types, where a type in Infrastructure uses a type in Infrastructure.RequestData.
- The types involved
Ocelot.Infrastructure.Placeholders→Ocelot.Infrastructure.RequestData.IRequestScopedDataRepository
- Direction
- Infrastructure uses Infrastructure.RequestData, so a change to Infrastructure.RequestData can break Infrastructure, while a change to Infrastructure can't break Infrastructure.RequestData.
- Position
- Below the diagonal: Infrastructure uses a module listed above it, which is the healthy direction.
14→9 Infrastructure uses Request.Middleware✕
- Connections
- 3 pairs of types, where a type in Infrastructure uses a type in Request.Middleware.
- The types involved
Ocelot.Infrastructure.ConfigAwarePlaceholders→Ocelot.Request.Middleware.DownstreamRequestOcelot.Infrastructure.IPlaceholders→Ocelot.Request.Middleware.DownstreamRequestOcelot.Infrastructure.Placeholders→Ocelot.Request.Middleware.DownstreamRequest
- Direction
- Infrastructure uses Request.Middleware, so a change to Request.Middleware can break Infrastructure, while a change to Infrastructure can't break Request.Middleware.
- Position
- Below the diagonal: Infrastructure uses a module listed above it, which is the healthy direction.
14→10 Infrastructure uses Middleware✕
- Connections
- 1 pair of types, where a type in Infrastructure uses a type in Middleware.
- The types involved
Ocelot.Infrastructure.Placeholders→Ocelot.Middleware.IBaseUrlFinder
- Direction
- Infrastructure uses Middleware, so a change to Middleware can break Infrastructure, while a change to Infrastructure can't break Middleware.
- Position
- Below the diagonal: Infrastructure uses a module listed above it, which is the healthy direction.
14→11 Infrastructure uses Errors✕
- Connections
- 3 pairs of types, where a type in Infrastructure uses a type in Errors.
- The types involved
Ocelot.Infrastructure.CannotAddPlaceholderError→Ocelot.Errors.ErrorOcelot.Infrastructure.CannotRemovePlaceholderError→Ocelot.Errors.ErrorOcelot.Infrastructure.CouldNotFindPlaceholderError→Ocelot.Errors.Error
- Direction
- Infrastructure uses Errors, so a change to Errors can break Infrastructure, while a change to Infrastructure can't break Errors.
- Position
- Below the diagonal: Infrastructure uses a module listed above it, which is the healthy direction.
15→3 Infrastructure.Claims uses Responses✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Claims uses a type in Responses.
- The types involved
Ocelot.Infrastructure.Claims.ClaimsParser→Ocelot.Responses.ResponseOcelot.Infrastructure.Claims.IClaimsParser→Ocelot.Responses.Response
- Direction
- Infrastructure.Claims uses Responses, so a change to Responses can break Infrastructure.Claims, while a change to Infrastructure.Claims can't break Responses.
- Position
- Below the diagonal: Infrastructure.Claims uses a module listed above it, which is the healthy direction.
15→11 Infrastructure.Claims uses Errors✕
- Connections
- 1 pair of types, where a type in Infrastructure.Claims uses a type in Errors.
- The types involved
Ocelot.Infrastructure.Claims.CannotFindClaimError→Ocelot.Errors.Error
- Direction
- Infrastructure.Claims uses Errors, so a change to Errors can break Infrastructure.Claims, while a change to Infrastructure.Claims can't break Errors.
- Position
- Below the diagonal: Infrastructure.Claims uses a module listed above it, which is the healthy direction.
16→3 ServiceDiscovery uses Responses✕
- Connections
- 2 pairs of types, where a type in ServiceDiscovery uses a type in Responses.
- The types involved
Ocelot.ServiceDiscovery.IServiceDiscoveryProviderFactory→Ocelot.Responses.ResponseOcelot.ServiceDiscovery.ServiceDiscoveryProviderFactory→Ocelot.Responses.Response
- Direction
- ServiceDiscovery uses Responses, so a change to Responses can break ServiceDiscovery, while a change to ServiceDiscovery can't break Responses.
- Position
- Below the diagonal: ServiceDiscovery uses a module listed above it, which is the healthy direction.
16→4 ServiceDiscovery uses ServiceDiscovery.Providers✕
- Connections
- 3 pairs of types, where a type in ServiceDiscovery uses a type in ServiceDiscovery.Providers.
- The types involved
Ocelot.ServiceDiscovery.IServiceDiscoveryProviderFactory→Ocelot.ServiceDiscovery.Providers.IServiceDiscoveryProviderOcelot.ServiceDiscovery.ServiceDiscoveryFinderDelegate→Ocelot.ServiceDiscovery.Providers.IServiceDiscoveryProviderOcelot.ServiceDiscovery.ServiceDiscoveryProviderFactory→Ocelot.ServiceDiscovery.Providers.IServiceDiscoveryProvider
- Direction
- ServiceDiscovery uses ServiceDiscovery.Providers, so a change to ServiceDiscovery.Providers can break ServiceDiscovery, while a change to ServiceDiscovery can't break ServiceDiscovery.Providers.
- Position
- Below the diagonal: ServiceDiscovery uses a module listed above it, which is the healthy direction.
16→7 ServiceDiscovery uses Logging✕
- Connections
- 2 pairs of types, where a type in ServiceDiscovery uses a type in Logging.
- The types involved
Ocelot.ServiceDiscovery.ServiceDiscoveryProviderFactory→Ocelot.Logging.IOcelotLoggerOcelot.ServiceDiscovery.ServiceDiscoveryProviderFactory→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- ServiceDiscovery uses Logging, so a change to Logging can break ServiceDiscovery, while a change to ServiceDiscovery can't break Logging.
- Position
- Below the diagonal: ServiceDiscovery uses a module listed above it, which is the healthy direction.
16→11 ServiceDiscovery uses Errors✕
- Connections
- 1 pair of types, where a type in ServiceDiscovery uses a type in Errors.
- The types involved
Ocelot.ServiceDiscovery.UnableToFindServiceDiscoveryProviderError→Ocelot.Errors.Error
- Direction
- ServiceDiscovery uses Errors, so a change to Errors can break ServiceDiscovery, while a change to ServiceDiscovery can't break Errors.
- Position
- Below the diagonal: ServiceDiscovery uses a module listed above it, which is the healthy direction.
16→20 ServiceDiscovery uses Configuration part of a loop✕
- Connections
- 6 pairs of types, where a type in ServiceDiscovery uses a type in Configuration.
- The types involved
Ocelot.ServiceDiscovery.IServiceDiscoveryProviderFactory→Ocelot.Configuration.DownstreamRouteOcelot.ServiceDiscovery.IServiceDiscoveryProviderFactory→Ocelot.Configuration.ServiceProviderConfigurationOcelot.ServiceDiscovery.ServiceDiscoveryFinderDelegate→Ocelot.Configuration.DownstreamRouteOcelot.ServiceDiscovery.ServiceDiscoveryFinderDelegate→Ocelot.Configuration.ServiceProviderConfigurationOcelot.ServiceDiscovery.ServiceDiscoveryProviderFactory→Ocelot.Configuration.DownstreamRouteOcelot.ServiceDiscovery.ServiceDiscoveryProviderFactory→Ocelot.Configuration.ServiceProviderConfiguration
- Direction
- ServiceDiscovery uses Configuration, so a change to Configuration can break ServiceDiscovery, while a change to ServiceDiscovery can't break Configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→2 Authorization uses Configuration.File✕
- Connections
- 1 pair of types, where a type in Authorization uses a type in Configuration.File.
- The types involved
Ocelot.Authorization.RouteClaimsRequirementPostConfigureOptions→Ocelot.Configuration.File.FileConfiguration
- Direction
- Authorization uses Configuration.File, so a change to Configuration.File can break Authorization, while a change to Authorization can't break Configuration.File.
- Position
- Below the diagonal: Authorization uses a module listed above it, which is the healthy direction.
17→3 Authorization uses Responses✕
- Connections
- 4 pairs of types, where a type in Authorization uses a type in Responses.
- The types involved
Ocelot.Authorization.ClaimsAuthorizer→Ocelot.Responses.ResponseOcelot.Authorization.IClaimsAuthorizer→Ocelot.Responses.ResponseOcelot.Authorization.IScopesAuthorizer→Ocelot.Responses.ResponseOcelot.Authorization.ScopesAuthorizer→Ocelot.Responses.Response
- Direction
- Authorization uses Responses, so a change to Responses can break Authorization, while a change to Authorization can't break Responses.
- Position
- Below the diagonal: Authorization uses a module listed above it, which is the healthy direction.
17→5 Authorization uses DownstreamRouteFinder.UrlMatcher✕
- Connections
- 2 pairs of types, where a type in Authorization uses a type in DownstreamRouteFinder.UrlMatcher.
- The types involved
Ocelot.Authorization.ClaimsAuthorizer→Ocelot.DownstreamRouteFinder.UrlMatcher.PlaceholderNameAndValueOcelot.Authorization.IClaimsAuthorizer→Ocelot.DownstreamRouteFinder.UrlMatcher.PlaceholderNameAndValue
- Direction
- Authorization uses DownstreamRouteFinder.UrlMatcher, so a change to DownstreamRouteFinder.UrlMatcher can break Authorization, while a change to Authorization can't break DownstreamRouteFinder.UrlMatcher.
- Position
- Below the diagonal: Authorization uses a module listed above it, which is the healthy direction.
17→7 Authorization uses Logging✕
- Connections
- 1 pair of types, where a type in Authorization uses a type in Logging.
- The types involved
Ocelot.Authorization.AuthorizationMiddleware→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- Authorization uses Logging, so a change to Logging can break Authorization, while a change to Authorization can't break Logging.
- Position
- Below the diagonal: Authorization uses a module listed above it, which is the healthy direction.
17→10 Authorization uses Middleware✕
- Connections
- 1 pair of types, where a type in Authorization uses a type in Middleware.
- The types involved
Ocelot.Authorization.AuthorizationMiddleware→Ocelot.Middleware.OcelotMiddleware
- Direction
- Authorization uses Middleware, so a change to Middleware can break Authorization, while a change to Authorization can't break Middleware.
- Position
- Below the diagonal: Authorization uses a module listed above it, which is the healthy direction.
17→11 Authorization uses Errors✕
- Connections
- 4 pairs of types, where a type in Authorization uses a type in Errors.
- The types involved
Ocelot.Authorization.ClaimValueNotAuthorizedError→Ocelot.Errors.ErrorOcelot.Authorization.ScopeNotAuthorizedError→Ocelot.Errors.ErrorOcelot.Authorization.UnauthorizedError→Ocelot.Errors.ErrorOcelot.Authorization.UserDoesNotHaveClaimError→Ocelot.Errors.Error
- Direction
- Authorization uses Errors, so a change to Errors can break Authorization, while a change to Authorization can't break Errors.
- Position
- Below the diagonal: Authorization uses a module listed above it, which is the healthy direction.
17→15 Authorization uses Infrastructure.Claims✕
- Connections
- 2 pairs of types, where a type in Authorization uses a type in Infrastructure.Claims.
- The types involved
Ocelot.Authorization.ClaimsAuthorizer→Ocelot.Infrastructure.Claims.IClaimsParserOcelot.Authorization.ScopesAuthorizer→Ocelot.Infrastructure.Claims.IClaimsParser
- Direction
- Authorization uses Infrastructure.Claims, so a change to Infrastructure.Claims can break Authorization, while a change to Authorization can't break Infrastructure.Claims.
- Position
- Below the diagonal: Authorization uses a module listed above it, which is the healthy direction.
18→2 Configuration.Validator uses Configuration.File✕
- Connections
- 8 pairs of types, where a type in Configuration.Validator uses a type in Configuration.File.
- The types involved
Ocelot.Configuration.Validator.FileAuthenticationOptionsValidator→Ocelot.Configuration.File.FileAuthenticationOptionsOcelot.Configuration.Validator.FileConfigurationFluentValidator→Ocelot.Configuration.File.FileAggregateRouteOcelot.Configuration.Validator.FileConfigurationFluentValidator→Ocelot.Configuration.File.FileConfigurationOcelot.Configuration.Validator.FileConfigurationFluentValidator→Ocelot.Configuration.File.FileRouteOcelot.Configuration.Validator.FileConfigurationFluentValidator→Ocelot.Configuration.File.FileServiceDiscoveryProviderOcelot.Configuration.Validator.FileQoSOptionsFluentValidator→Ocelot.Configuration.File.FileQoSOptionsOcelot.Configuration.Validator.IConfigurationValidator→Ocelot.Configuration.File.FileConfigurationOcelot.Configuration.Validator.RouteFluentValidator→Ocelot.Configuration.File.FileRateLimitByHeaderRule
- Direction
- Configuration.Validator uses Configuration.File, so a change to Configuration.File can break Configuration.Validator, while a change to Configuration.Validator can't break Configuration.File.
- Position
- Below the diagonal: Configuration.Validator uses a module listed above it, which is the healthy direction.
18→3 Configuration.Validator uses Responses✕
- Connections
- 2 pairs of types, where a type in Configuration.Validator uses a type in Responses.
- The types involved
Ocelot.Configuration.Validator.FileConfigurationFluentValidator→Ocelot.Responses.ResponseOcelot.Configuration.Validator.IConfigurationValidator→Ocelot.Responses.Response
- Direction
- Configuration.Validator uses Responses, so a change to Responses can break Configuration.Validator, while a change to Configuration.Validator can't break Responses.
- Position
- Below the diagonal: Configuration.Validator uses a module listed above it, which is the healthy direction.
18→11 Configuration.Validator uses Errors✕
- Connections
- 2 pairs of types, where a type in Configuration.Validator uses a type in Errors.
- The types involved
Ocelot.Configuration.Validator.ConfigurationValidationResult→Ocelot.Errors.ErrorOcelot.Configuration.Validator.FileValidationFailedError→Ocelot.Errors.Error
- Direction
- Configuration.Validator uses Errors, so a change to Errors can break Configuration.Validator, while a change to Configuration.Validator can't break Errors.
- Position
- Below the diagonal: Configuration.Validator uses a module listed above it, which is the healthy direction.
18→16 Configuration.Validator uses ServiceDiscovery✕
- Connections
- 1 pair of types, where a type in Configuration.Validator uses a type in ServiceDiscovery.
- The types involved
Ocelot.Configuration.Validator.FileConfigurationFluentValidator→Ocelot.ServiceDiscovery.ServiceDiscoveryFinderDelegate
- Direction
- Configuration.Validator uses ServiceDiscovery, so a change to ServiceDiscovery can break Configuration.Validator, while a change to Configuration.Validator can't break ServiceDiscovery.
- Position
- Below the diagonal: Configuration.Validator uses a module listed above it, which is the healthy direction.
19→1 Configuration.Creator uses Values✕
- Connections
- 4 pairs of types, where a type in Configuration.Creator uses a type in Values.
- The types involved
Ocelot.Configuration.Creator.IUpstreamHeaderTemplatePatternCreator→Ocelot.Values.UpstreamHeaderTemplateOcelot.Configuration.Creator.IUpstreamTemplatePatternCreator→Ocelot.Values.UpstreamPathTemplateOcelot.Configuration.Creator.UpstreamHeaderTemplatePatternCreator→Ocelot.Values.UpstreamHeaderTemplateOcelot.Configuration.Creator.UpstreamTemplatePatternCreator→Ocelot.Values.UpstreamPathTemplate
- Direction
- Configuration.Creator uses Values, so a change to Values can break Configuration.Creator, while a change to Configuration.Creator can't break Values.
- Position
- Below the diagonal: Configuration.Creator uses a module listed above it, which is the healthy direction.
19→2 Configuration.Creator uses Configuration.File✕
- Connections
- 102 pairs of types, where a type in Configuration.Creator uses a type in Configuration.File. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Ocelot.Configuration.Creator.AggregatesCreator→Ocelot.Configuration.File.FileAggregateRouteOcelot.Configuration.Creator.AggregatesCreator→Ocelot.Configuration.File.FileConfigurationOcelot.Configuration.Creator.AggregatesCreator→Ocelot.Configuration.File.FileGlobalConfigurationOcelot.Configuration.Creator.AuthenticationOptionsCreator→Ocelot.Configuration.File.FileAuthenticationOptionsOcelot.Configuration.Creator.AuthenticationOptionsCreator→Ocelot.Configuration.File.FileDynamicRouteOcelot.Configuration.Creator.AuthenticationOptionsCreator→Ocelot.Configuration.File.FileGlobalAuthenticationOptionsOcelot.Configuration.Creator.AuthenticationOptionsCreator→Ocelot.Configuration.File.FileGlobalConfigurationOcelot.Configuration.Creator.AuthenticationOptionsCreator→Ocelot.Configuration.File.FileRouteOcelot.Configuration.Creator.AuthenticationOptionsCreator→Ocelot.Configuration.File.IRouteGroupingOcelot.Configuration.Creator.CacheOptionsCreator→Ocelot.Configuration.File.FileCacheOptionsOcelot.Configuration.Creator.CacheOptionsCreator→Ocelot.Configuration.File.FileDynamicRouteOcelot.Configuration.Creator.CacheOptionsCreator→Ocelot.Configuration.File.FileGlobalCacheOptionsOcelot.Configuration.Creator.CacheOptionsCreator→Ocelot.Configuration.File.FileGlobalConfigurationOcelot.Configuration.Creator.CacheOptionsCreator→Ocelot.Configuration.File.FileRouteOcelot.Configuration.Creator.CacheOptionsCreator→Ocelot.Configuration.File.IRouteGroupingOcelot.Configuration.Creator.ConfigurationCreator→Ocelot.Configuration.File.FileConfigurationOcelot.Configuration.Creator.DefaultMetadataCreator→Ocelot.Configuration.File.FileGlobalConfigurationOcelot.Configuration.Creator.DownstreamAddressesCreator→Ocelot.Configuration.File.FileRouteOcelot.Configuration.Creator.DynamicRoutesCreator→Ocelot.Configuration.File.FileConfigurationOcelot.Configuration.Creator.DynamicRoutesCreator→Ocelot.Configuration.File.FileDynamicRouteOcelot.Configuration.Creator.DynamicRoutesCreator→Ocelot.Configuration.File.FileGlobalConfigurationOcelot.Configuration.Creator.FileInternalConfigurationCreator→Ocelot.Configuration.File.FileConfigurationOcelot.Configuration.Creator.HeaderFindAndReplaceCreator→Ocelot.Configuration.File.FileGlobalConfigurationOcelot.Configuration.Creator.HeaderFindAndReplaceCreator→Ocelot.Configuration.File.FileRouteOcelot.Configuration.Creator.HttpHandlerOptionsCreator→Ocelot.Configuration.File.FileDynamicRoute
- Direction
- Configuration.Creator uses Configuration.File, so a change to Configuration.File can break Configuration.Creator, while a change to Configuration.Creator can't break Configuration.File.
- Position
- Below the diagonal: Configuration.Creator uses a module listed above it, which is the healthy direction.
19→3 Configuration.Creator uses Responses✕
- Connections
- 2 pairs of types, where a type in Configuration.Creator uses a type in Responses.
- The types involved
Ocelot.Configuration.Creator.FileInternalConfigurationCreator→Ocelot.Responses.ResponseOcelot.Configuration.Creator.IInternalConfigurationCreator→Ocelot.Responses.Response
- Direction
- Configuration.Creator uses Responses, so a change to Responses can break Configuration.Creator, while a change to Configuration.Creator can't break Responses.
- Position
- Below the diagonal: Configuration.Creator uses a module listed above it, which is the healthy direction.
19→7 Configuration.Creator uses Logging✕
- Connections
- 5 pairs of types, where a type in Configuration.Creator uses a type in Logging.
- The types involved
Ocelot.Configuration.Creator.ClaimsToThingCreator→Ocelot.Logging.IOcelotLoggerOcelot.Configuration.Creator.ClaimsToThingCreator→Ocelot.Logging.IOcelotLoggerFactoryOcelot.Configuration.Creator.HeaderFindAndReplaceCreator→Ocelot.Logging.IOcelotLoggerOcelot.Configuration.Creator.HeaderFindAndReplaceCreator→Ocelot.Logging.IOcelotLoggerFactoryOcelot.Configuration.Creator.HttpHandlerOptionsCreator→Ocelot.Logging.IOcelotTracer
- Direction
- Configuration.Creator uses Logging, so a change to Logging can break Configuration.Creator, while a change to Configuration.Creator can't break Logging.
- Position
- Below the diagonal: Configuration.Creator uses a module listed above it, which is the healthy direction.
19→13 Configuration.Creator uses Configuration.Parser✕
- Connections
- 1 pair of types, where a type in Configuration.Creator uses a type in Configuration.Parser.
- The types involved
Ocelot.Configuration.Creator.ClaimsToThingCreator→Ocelot.Configuration.Parser.IClaimToThingConfigurationParser
- Direction
- Configuration.Creator uses Configuration.Parser, so a change to Configuration.Parser can break Configuration.Creator, while a change to Configuration.Creator can't break Configuration.Parser.
- Position
- Below the diagonal: Configuration.Creator uses a module listed above it, which is the healthy direction.
19→14 Configuration.Creator uses Infrastructure✕
- Connections
- 1 pair of types, where a type in Configuration.Creator uses a type in Infrastructure.
- The types involved
Ocelot.Configuration.Creator.HeaderFindAndReplaceCreator→Ocelot.Infrastructure.IPlaceholders
- Direction
- Configuration.Creator uses Infrastructure, so a change to Infrastructure can break Configuration.Creator, while a change to Configuration.Creator can't break Infrastructure.
- Position
- Below the diagonal: Configuration.Creator uses a module listed above it, which is the healthy direction.
19→18 Configuration.Creator uses Configuration.Validator✕
- Connections
- 1 pair of types, where a type in Configuration.Creator uses a type in Configuration.Validator.
- The types involved
Ocelot.Configuration.Creator.FileInternalConfigurationCreator→Ocelot.Configuration.Validator.IConfigurationValidator
- Direction
- Configuration.Creator uses Configuration.Validator, so a change to Configuration.Validator can break Configuration.Creator, while a change to Configuration.Creator can't break Configuration.Validator.
- Position
- Below the diagonal: Configuration.Creator uses a module listed above it, which is the healthy direction.
19→20 Configuration.Creator uses Configuration part of a loop✕
- Connections
- 40 pairs of types, where a type in Configuration.Creator uses a type in Configuration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Ocelot.Configuration.Creator.AggregatesCreator→Ocelot.Configuration.DownstreamRouteOcelot.Configuration.Creator.AggregatesCreator→Ocelot.Configuration.RouteOcelot.Configuration.Creator.AuthenticationOptionsCreator→Ocelot.Configuration.AuthenticationOptionsOcelot.Configuration.Creator.CacheOptionsCreator→Ocelot.Configuration.CacheOptionsOcelot.Configuration.Creator.ClaimsToThingCreator→Ocelot.Configuration.ClaimToThingOcelot.Configuration.Creator.ConfigurationCreator→Ocelot.Configuration.InternalConfigurationOcelot.Configuration.Creator.ConfigurationCreator→Ocelot.Configuration.RouteOcelot.Configuration.Creator.DefaultMetadataCreator→Ocelot.Configuration.MetadataOptionsOcelot.Configuration.Creator.DownstreamAddressesCreator→Ocelot.Configuration.DownstreamHostAndPortOcelot.Configuration.Creator.DynamicRoutesCreator→Ocelot.Configuration.RouteOcelot.Configuration.Creator.FileInternalConfigurationCreator→Ocelot.Configuration.IInternalConfigurationOcelot.Configuration.Creator.HeaderFindAndReplaceCreator→Ocelot.Configuration.HeaderFindAndReplaceOcelot.Configuration.Creator.HeaderTransformations→Ocelot.Configuration.HeaderFindAndReplaceOcelot.Configuration.Creator.HttpHandlerOptionsCreator→Ocelot.Configuration.HttpHandlerOptionsOcelot.Configuration.Creator.IAggregatesCreator→Ocelot.Configuration.RouteOcelot.Configuration.Creator.IAuthenticationOptionsCreator→Ocelot.Configuration.AuthenticationOptionsOcelot.Configuration.Creator.ICacheOptionsCreator→Ocelot.Configuration.CacheOptionsOcelot.Configuration.Creator.IClaimsToThingCreator→Ocelot.Configuration.ClaimToThingOcelot.Configuration.Creator.IConfigurationCreator→Ocelot.Configuration.InternalConfigurationOcelot.Configuration.Creator.IConfigurationCreator→Ocelot.Configuration.RouteOcelot.Configuration.Creator.IDownstreamAddressesCreator→Ocelot.Configuration.DownstreamHostAndPortOcelot.Configuration.Creator.IDynamicsCreator→Ocelot.Configuration.RouteOcelot.Configuration.Creator.IHttpHandlerOptionsCreator→Ocelot.Configuration.HttpHandlerOptionsOcelot.Configuration.Creator.IInternalConfigurationCreator→Ocelot.Configuration.IInternalConfigurationOcelot.Configuration.Creator.ILoadBalancerOptionsCreator→Ocelot.Configuration.LoadBalancerOptions
- Direction
- Configuration.Creator uses Configuration, so a change to Configuration can break Configuration.Creator, while a change to Configuration.Creator can't break Configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→21 Configuration.Creator uses Cache part of a loop✕
- Connections
- 1 pair of types, where a type in Configuration.Creator uses a type in Cache.
- The types involved
Ocelot.Configuration.Creator.UpstreamTemplatePatternCreator→Ocelot.Cache.IOcelotCache
- Direction
- Configuration.Creator uses Cache, so a change to Cache can break Configuration.Creator, while a change to Configuration.Creator can't break Cache.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→34 Configuration.Creator uses Administration part of a loop✕
- Connections
- 1 pair of types, where a type in Configuration.Creator uses a type in Administration.
- The types involved
Ocelot.Configuration.Creator.ConfigurationCreator→Ocelot.Administration.IAdministrationPath
- Direction
- Configuration.Creator uses Administration, so a change to Administration can break Configuration.Creator, while a change to Configuration.Creator can't break Administration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→1 Configuration uses Values✕
- Connections
- 5 pairs of types, where a type in Configuration uses a type in Values.
- The types involved
Ocelot.Configuration.DownstreamRoute→Ocelot.Values.DownstreamPathTemplateOcelot.Configuration.DownstreamRoute→Ocelot.Values.UpstreamHeaderTemplateOcelot.Configuration.DownstreamRoute→Ocelot.Values.UpstreamPathTemplateOcelot.Configuration.Route→Ocelot.Values.UpstreamHeaderTemplateOcelot.Configuration.Route→Ocelot.Values.UpstreamPathTemplate
- Direction
- Configuration uses Values, so a change to Values can break Configuration, while a change to Configuration can't break Values.
- Position
- Below the diagonal: Configuration uses a module listed above it, which is the healthy direction.
20→2 Configuration uses Configuration.File✕
- Connections
- 8 pairs of types, where a type in Configuration uses a type in Configuration.File.
- The types involved
Ocelot.Configuration.AuthenticationOptions→Ocelot.Configuration.File.FileAuthenticationOptionsOcelot.Configuration.CacheOptions→Ocelot.Configuration.File.FileCacheOptionsOcelot.Configuration.HttpHandlerOptions→Ocelot.Configuration.File.FileHttpHandlerOptionsOcelot.Configuration.LoadBalancerOptions→Ocelot.Configuration.File.FileLoadBalancerOptionsOcelot.Configuration.MetadataOptions→Ocelot.Configuration.File.FileMetadataOptionsOcelot.Configuration.QoSOptions→Ocelot.Configuration.File.FileQoSOptionsOcelot.Configuration.RateLimitOptions→Ocelot.Configuration.File.FileRateLimitByHeaderRuleOcelot.Configuration.Route→Ocelot.Configuration.File.AggregateRouteConfig
- Direction
- Configuration uses Configuration.File, so a change to Configuration.File can break Configuration, while a change to Configuration can't break Configuration.File.
- Position
- Below the diagonal: Configuration uses a module listed above it, which is the healthy direction.
20→5 Configuration uses DownstreamRouteFinder.UrlMatcher✕
- Connections
- 1 pair of types, where a type in Configuration uses a type in DownstreamRouteFinder.UrlMatcher.
- The types involved
Ocelot.Configuration.Route→Ocelot.DownstreamRouteFinder.UrlMatcher.PlaceholderNameAndValue
- Direction
- Configuration uses DownstreamRouteFinder.UrlMatcher, so a change to DownstreamRouteFinder.UrlMatcher can break Configuration, while a change to Configuration can't break DownstreamRouteFinder.UrlMatcher.
- Position
- Below the diagonal: Configuration uses a module listed above it, which is the healthy direction.
20→19 Configuration uses Configuration.Creator✕
- Connections
- 1 pair of types, where a type in Configuration uses a type in Configuration.Creator.
- The types involved
Ocelot.Configuration.DownstreamRoute→Ocelot.Configuration.Creator.AddHeader
- Direction
- Configuration uses Configuration.Creator, so a change to Configuration.Creator can break Configuration, while a change to Configuration can't break Configuration.Creator.
- Position
- Below the diagonal: Configuration uses a module listed above it, which is the healthy direction.
21→7 Cache uses Logging✕
- Connections
- 1 pair of types, where a type in Cache uses a type in Logging.
- The types involved
Ocelot.Cache.OutputCacheMiddleware→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- Cache uses Logging, so a change to Logging can break Cache, while a change to Cache can't break Logging.
- Position
- Below the diagonal: Cache uses a module listed above it, which is the healthy direction.
21→9 Cache uses Request.Middleware✕
- Connections
- 2 pairs of types, where a type in Cache uses a type in Request.Middleware.
- The types involved
Ocelot.Cache.DefaultCacheKeyGenerator→Ocelot.Request.Middleware.DownstreamRequestOcelot.Cache.ICacheKeyGenerator→Ocelot.Request.Middleware.DownstreamRequest
- Direction
- Cache uses Request.Middleware, so a change to Request.Middleware can break Cache, while a change to Cache can't break Request.Middleware.
- Position
- Below the diagonal: Cache uses a module listed above it, which is the healthy direction.
21→10 Cache uses Middleware✕
- Connections
- 2 pairs of types, where a type in Cache uses a type in Middleware.
- The types involved
Ocelot.Cache.OutputCacheMiddleware→Ocelot.Middleware.DownstreamResponseOcelot.Cache.OutputCacheMiddleware→Ocelot.Middleware.OcelotMiddleware
- Direction
- Cache uses Middleware, so a change to Middleware can break Cache, while a change to Cache can't break Middleware.
- Position
- Below the diagonal: Cache uses a module listed above it, which is the healthy direction.
21→20 Cache uses Configuration✕
- Connections
- 2 pairs of types, where a type in Cache uses a type in Configuration.
- The types involved
Ocelot.Cache.DefaultCacheKeyGenerator→Ocelot.Configuration.DownstreamRouteOcelot.Cache.ICacheKeyGenerator→Ocelot.Configuration.DownstreamRoute
- Direction
- Cache uses Configuration, so a change to Configuration can break Cache, while a change to Cache can't break Configuration.
- Position
- Below the diagonal: Cache uses a module listed above it, which is the healthy direction.
22→3 Claims uses Responses✕
- Connections
- 2 pairs of types, where a type in Claims uses a type in Responses.
- The types involved
Ocelot.Claims.AddClaimsToRequest→Ocelot.Responses.ResponseOcelot.Claims.IAddClaimsToRequest→Ocelot.Responses.Response
- Direction
- Claims uses Responses, so a change to Responses can break Claims, while a change to Claims can't break Responses.
- Position
- Below the diagonal: Claims uses a module listed above it, which is the healthy direction.
22→15 Claims uses Infrastructure.Claims✕
- Connections
- 1 pair of types, where a type in Claims uses a type in Infrastructure.Claims.
- The types involved
Ocelot.Claims.AddClaimsToRequest→Ocelot.Infrastructure.Claims.IClaimsParser
- Direction
- Claims uses Infrastructure.Claims, so a change to Infrastructure.Claims can break Claims, while a change to Claims can't break Infrastructure.Claims.
- Position
- Below the diagonal: Claims uses a module listed above it, which is the healthy direction.
22→20 Claims uses Configuration✕
- Connections
- 2 pairs of types, where a type in Claims uses a type in Configuration.
- The types involved
Ocelot.Claims.AddClaimsToRequest→Ocelot.Configuration.ClaimToThingOcelot.Claims.IAddClaimsToRequest→Ocelot.Configuration.ClaimToThing
- Direction
- Claims uses Configuration, so a change to Configuration can break Claims, while a change to Claims can't break Configuration.
- Position
- Below the diagonal: Claims uses a module listed above it, which is the healthy direction.
23→2 DependencyInjection uses Configuration.File✕
- Connections
- 1 pair of types, where a type in DependencyInjection uses a type in Configuration.File.
- The types involved
Ocelot.DependencyInjection.ConfigurationBuilderExtensions→Ocelot.Configuration.File.FileConfiguration
- Direction
- DependencyInjection uses Configuration.File, so a change to Configuration.File can break DependencyInjection, while a change to DependencyInjection can't break Configuration.File.
- Position
- Below the diagonal: DependencyInjection uses a module listed above it, which is the healthy direction.
23→4 DependencyInjection uses ServiceDiscovery.Providers✕
- Connections
- 2 pairs of types, where a type in DependencyInjection uses a type in ServiceDiscovery.Providers.
- The types involved
Ocelot.DependencyInjection.IOcelotBuilder→Ocelot.ServiceDiscovery.Providers.IServiceDiscoveryProviderOcelot.DependencyInjection.OcelotBuilder→Ocelot.ServiceDiscovery.Providers.IServiceDiscoveryProvider
- Direction
- DependencyInjection uses ServiceDiscovery.Providers, so a change to ServiceDiscovery.Providers can break DependencyInjection, while a change to DependencyInjection can't break ServiceDiscovery.Providers.
- Position
- Below the diagonal: DependencyInjection uses a module listed above it, which is the healthy direction.
23→10 DependencyInjection uses Middleware✕
- Connections
- 2 pairs of types, where a type in DependencyInjection uses a type in Middleware.
- The types involved
Ocelot.DependencyInjection.IOcelotBuilder→Ocelot.Middleware.OcelotMiddlewareConfigurationDelegateOcelot.DependencyInjection.OcelotBuilder→Ocelot.Middleware.OcelotMiddlewareConfigurationDelegate
- Direction
- DependencyInjection uses Middleware, so a change to Middleware can break DependencyInjection, while a change to DependencyInjection can't break Middleware.
- Position
- Below the diagonal: DependencyInjection uses a module listed above it, which is the healthy direction.
23→20 DependencyInjection uses Configuration✕
- Connections
- 2 pairs of types, where a type in DependencyInjection uses a type in Configuration.
- The types involved
Ocelot.DependencyInjection.IOcelotBuilder→Ocelot.Configuration.DownstreamRouteOcelot.DependencyInjection.OcelotBuilder→Ocelot.Configuration.DownstreamRoute
- Direction
- DependencyInjection uses Configuration, so a change to Configuration can break DependencyInjection, while a change to DependencyInjection can't break Configuration.
- Position
- Below the diagonal: DependencyInjection uses a module listed above it, which is the healthy direction.
24→3 DownstreamRouteFinder.Finder uses Responses✕
- Connections
- 3 pairs of types, where a type in DownstreamRouteFinder.Finder uses a type in Responses.
- The types involved
Ocelot.DownstreamRouteFinder.Finder.DiscoveryDownstreamRouteFinder→Ocelot.Responses.ResponseOcelot.DownstreamRouteFinder.Finder.DownstreamRouteFinder→Ocelot.Responses.ResponseOcelot.DownstreamRouteFinder.Finder.IDownstreamRouteProvider→Ocelot.Responses.Response
- Direction
- DownstreamRouteFinder.Finder uses Responses, so a change to Responses can break DownstreamRouteFinder.Finder, while a change to DownstreamRouteFinder.Finder can't break Responses.
- Position
- Below the diagonal: DownstreamRouteFinder.Finder uses a module listed above it, which is the healthy direction.
24→5 DownstreamRouteFinder.Finder uses DownstreamRouteFinder.UrlMatcher✕
- Connections
- 2 pairs of types, where a type in DownstreamRouteFinder.Finder uses a type in DownstreamRouteFinder.UrlMatcher.
- The types involved
Ocelot.DownstreamRouteFinder.Finder.DownstreamRouteFinder→Ocelot.DownstreamRouteFinder.UrlMatcher.IPlaceholderNameAndValueFinderOcelot.DownstreamRouteFinder.Finder.DownstreamRouteFinder→Ocelot.DownstreamRouteFinder.UrlMatcher.IUrlPathToUrlTemplateMatcher
- Direction
- DownstreamRouteFinder.Finder uses DownstreamRouteFinder.UrlMatcher, so a change to DownstreamRouteFinder.UrlMatcher can break DownstreamRouteFinder.Finder, while a change to DownstreamRouteFinder.Finder can't break DownstreamRouteFinder.UrlMatcher.
- Position
- Below the diagonal: DownstreamRouteFinder.Finder uses a module listed above it, which is the healthy direction.
24→7 DownstreamRouteFinder.Finder uses Logging✕
- Connections
- 2 pairs of types, where a type in DownstreamRouteFinder.Finder uses a type in Logging.
- The types involved
Ocelot.DownstreamRouteFinder.Finder.DownstreamRouteProviderFactory→Ocelot.Logging.IOcelotLoggerOcelot.DownstreamRouteFinder.Finder.DownstreamRouteProviderFactory→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- DownstreamRouteFinder.Finder uses Logging, so a change to Logging can break DownstreamRouteFinder.Finder, while a change to DownstreamRouteFinder.Finder can't break Logging.
- Position
- Below the diagonal: DownstreamRouteFinder.Finder uses a module listed above it, which is the healthy direction.
24→11 DownstreamRouteFinder.Finder uses Errors✕
- Connections
- 1 pair of types, where a type in DownstreamRouteFinder.Finder uses a type in Errors.
- The types involved
Ocelot.DownstreamRouteFinder.Finder.UnableToFindDownstreamRouteError→Ocelot.Errors.Error
- Direction
- DownstreamRouteFinder.Finder uses Errors, so a change to Errors can break DownstreamRouteFinder.Finder, while a change to DownstreamRouteFinder.Finder can't break Errors.
- Position
- Below the diagonal: DownstreamRouteFinder.Finder uses a module listed above it, which is the healthy direction.
24→19 DownstreamRouteFinder.Finder uses Configuration.Creator✕
- Connections
- 2 pairs of types, where a type in DownstreamRouteFinder.Finder uses a type in Configuration.Creator.
- The types involved
Ocelot.DownstreamRouteFinder.Finder.DiscoveryDownstreamRouteFinder→Ocelot.Configuration.Creator.IRouteKeyCreatorOcelot.DownstreamRouteFinder.Finder.DiscoveryDownstreamRouteFinder→Ocelot.Configuration.Creator.IUpstreamHeaderTemplatePatternCreator
- Direction
- DownstreamRouteFinder.Finder uses Configuration.Creator, so a change to Configuration.Creator can break DownstreamRouteFinder.Finder, while a change to DownstreamRouteFinder.Finder can't break Configuration.Creator.
- Position
- Below the diagonal: DownstreamRouteFinder.Finder uses a module listed above it, which is the healthy direction.
24→20 DownstreamRouteFinder.Finder uses Configuration✕
- Connections
- 9 pairs of types, where a type in DownstreamRouteFinder.Finder uses a type in Configuration.
- The types involved
Ocelot.DownstreamRouteFinder.Finder.DiscoveryDownstreamRouteFinder→Ocelot.Configuration.IInternalConfigurationOcelot.DownstreamRouteFinder.Finder.DiscoveryDownstreamRouteFinder→Ocelot.Configuration.RouteOcelot.DownstreamRouteFinder.Finder.DownstreamRouteFinder→Ocelot.Configuration.IInternalConfigurationOcelot.DownstreamRouteFinder.Finder.DownstreamRouteFinder→Ocelot.Configuration.RouteOcelot.DownstreamRouteFinder.Finder.DownstreamRouteProviderFactory→Ocelot.Configuration.IInternalConfigurationOcelot.DownstreamRouteFinder.Finder.DownstreamRouteProviderFactory→Ocelot.Configuration.ServiceProviderConfigurationOcelot.DownstreamRouteFinder.Finder.IDownstreamRouteProvider→Ocelot.Configuration.IInternalConfigurationOcelot.DownstreamRouteFinder.Finder.IDownstreamRouteProvider→Ocelot.Configuration.RouteOcelot.DownstreamRouteFinder.Finder.IDownstreamRouteProviderFactory→Ocelot.Configuration.IInternalConfiguration
- Direction
- DownstreamRouteFinder.Finder uses Configuration, so a change to Configuration can break DownstreamRouteFinder.Finder, while a change to DownstreamRouteFinder.Finder can't break Configuration.
- Position
- Below the diagonal: DownstreamRouteFinder.Finder uses a module listed above it, which is the healthy direction.
25→1 DownstreamUrlCreator uses Values✕
- Connections
- 3 pairs of types, where a type in DownstreamUrlCreator uses a type in Values.
- The types involved
Ocelot.DownstreamUrlCreator.DownstreamPathPlaceholderReplacer→Ocelot.Values.DownstreamPathOcelot.DownstreamUrlCreator.DownstreamUrlCreatorMiddleware→Ocelot.Values.DownstreamPathOcelot.DownstreamUrlCreator.IDownstreamPathPlaceholderReplacer→Ocelot.Values.DownstreamPath
- Direction
- DownstreamUrlCreator uses Values, so a change to Values can break DownstreamUrlCreator, while a change to DownstreamUrlCreator can't break Values.
- Position
- Below the diagonal: DownstreamUrlCreator uses a module listed above it, which is the healthy direction.
25→5 DownstreamUrlCreator uses DownstreamRouteFinder.UrlMatcher✕
- Connections
- 3 pairs of types, where a type in DownstreamUrlCreator uses a type in DownstreamRouteFinder.UrlMatcher.
- The types involved
Ocelot.DownstreamUrlCreator.DownstreamPathPlaceholderReplacer→Ocelot.DownstreamRouteFinder.UrlMatcher.PlaceholderNameAndValueOcelot.DownstreamUrlCreator.DownstreamUrlCreatorMiddleware→Ocelot.DownstreamRouteFinder.UrlMatcher.PlaceholderNameAndValueOcelot.DownstreamUrlCreator.IDownstreamPathPlaceholderReplacer→Ocelot.DownstreamRouteFinder.UrlMatcher.PlaceholderNameAndValue
- Direction
- DownstreamUrlCreator uses DownstreamRouteFinder.UrlMatcher, so a change to DownstreamRouteFinder.UrlMatcher can break DownstreamUrlCreator, while a change to DownstreamUrlCreator can't break DownstreamRouteFinder.UrlMatcher.
- Position
- Below the diagonal: DownstreamUrlCreator uses a module listed above it, which is the healthy direction.
25→7 DownstreamUrlCreator uses Logging✕
- Connections
- 1 pair of types, where a type in DownstreamUrlCreator uses a type in Logging.
- The types involved
Ocelot.DownstreamUrlCreator.DownstreamUrlCreatorMiddleware→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- DownstreamUrlCreator uses Logging, so a change to Logging can break DownstreamUrlCreator, while a change to DownstreamUrlCreator can't break Logging.
- Position
- Below the diagonal: DownstreamUrlCreator uses a module listed above it, which is the healthy direction.
25→9 DownstreamUrlCreator uses Request.Middleware✕
- Connections
- 1 pair of types, where a type in DownstreamUrlCreator uses a type in Request.Middleware.
- The types involved
Ocelot.DownstreamUrlCreator.DownstreamUrlCreatorMiddleware→Ocelot.Request.Middleware.DownstreamRequest
- Direction
- DownstreamUrlCreator uses Request.Middleware, so a change to Request.Middleware can break DownstreamUrlCreator, while a change to DownstreamUrlCreator can't break Request.Middleware.
- Position
- Below the diagonal: DownstreamUrlCreator uses a module listed above it, which is the healthy direction.
25→10 DownstreamUrlCreator uses Middleware✕
- Connections
- 1 pair of types, where a type in DownstreamUrlCreator uses a type in Middleware.
- The types involved
Ocelot.DownstreamUrlCreator.DownstreamUrlCreatorMiddleware→Ocelot.Middleware.OcelotMiddleware
- Direction
- DownstreamUrlCreator uses Middleware, so a change to Middleware can break DownstreamUrlCreator, while a change to DownstreamUrlCreator can't break Middleware.
- Position
- Below the diagonal: DownstreamUrlCreator uses a module listed above it, which is the healthy direction.
25→20 DownstreamUrlCreator uses Configuration✕
- Connections
- 2 pairs of types, where a type in DownstreamUrlCreator uses a type in Configuration.
- The types involved
Ocelot.DownstreamUrlCreator.DownstreamUrlCreatorMiddleware→Ocelot.Configuration.DownstreamRouteOcelot.DownstreamUrlCreator.DownstreamUrlCreatorMiddleware→Ocelot.Configuration.IInternalConfiguration
- Direction
- DownstreamUrlCreator uses Configuration, so a change to Configuration can break DownstreamUrlCreator, while a change to DownstreamUrlCreator can't break Configuration.
- Position
- Below the diagonal: DownstreamUrlCreator uses a module listed above it, which is the healthy direction.
26→3 Headers uses Responses✕
- Connections
- 8 pairs of types, where a type in Headers uses a type in Responses.
- The types involved
Ocelot.Headers.AddHeadersToRequest→Ocelot.Responses.ResponseOcelot.Headers.HttpContextRequestHeaderReplacer→Ocelot.Responses.ResponseOcelot.Headers.HttpResponseHeaderReplacer→Ocelot.Responses.ResponseOcelot.Headers.IAddHeadersToRequest→Ocelot.Responses.ResponseOcelot.Headers.IHttpContextRequestHeaderReplacer→Ocelot.Responses.ResponseOcelot.Headers.IHttpResponseHeaderReplacer→Ocelot.Responses.ResponseOcelot.Headers.IRemoveOutputHeaders→Ocelot.Responses.ResponseOcelot.Headers.RemoveOutputHeaders→Ocelot.Responses.Response
- Direction
- Headers uses Responses, so a change to Responses can break Headers, while a change to Headers can't break Responses.
- Position
- Below the diagonal: Headers uses a module listed above it, which is the healthy direction.
26→7 Headers uses Logging✕
- Connections
- 4 pairs of types, where a type in Headers uses a type in Logging.
- The types involved
Ocelot.Headers.AddHeadersToRequest→Ocelot.Logging.IOcelotLoggerOcelot.Headers.AddHeadersToRequest→Ocelot.Logging.IOcelotLoggerFactoryOcelot.Headers.AddHeadersToResponse→Ocelot.Logging.IOcelotLoggerOcelot.Headers.AddHeadersToResponse→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- Headers uses Logging, so a change to Logging can break Headers, while a change to Headers can't break Logging.
- Position
- Below the diagonal: Headers uses a module listed above it, which is the healthy direction.
26→9 Headers uses Request.Middleware✕
- Connections
- 2 pairs of types, where a type in Headers uses a type in Request.Middleware.
- The types involved
Ocelot.Headers.AddHeadersToRequest→Ocelot.Request.Middleware.DownstreamRequestOcelot.Headers.IAddHeadersToRequest→Ocelot.Request.Middleware.DownstreamRequest
- Direction
- Headers uses Request.Middleware, so a change to Request.Middleware can break Headers, while a change to Headers can't break Request.Middleware.
- Position
- Below the diagonal: Headers uses a module listed above it, which is the healthy direction.
26→10 Headers uses Middleware✕
- Connections
- 4 pairs of types, where a type in Headers uses a type in Middleware.
- The types involved
Ocelot.Headers.AddHeadersToResponse→Ocelot.Middleware.DownstreamResponseOcelot.Headers.IAddHeadersToResponse→Ocelot.Middleware.DownstreamResponseOcelot.Headers.IRemoveOutputHeaders→Ocelot.Middleware.HeaderOcelot.Headers.RemoveOutputHeaders→Ocelot.Middleware.Header
- Direction
- Headers uses Middleware, so a change to Middleware can break Headers, while a change to Headers can't break Middleware.
- Position
- Below the diagonal: Headers uses a module listed above it, which is the healthy direction.
26→14 Headers uses Infrastructure✕
- Connections
- 3 pairs of types, where a type in Headers uses a type in Infrastructure.
- The types involved
Ocelot.Headers.AddHeadersToRequest→Ocelot.Infrastructure.IPlaceholdersOcelot.Headers.AddHeadersToResponse→Ocelot.Infrastructure.IPlaceholdersOcelot.Headers.HttpResponseHeaderReplacer→Ocelot.Infrastructure.IPlaceholders
- Direction
- Headers uses Infrastructure, so a change to Infrastructure can break Headers, while a change to Headers can't break Infrastructure.
- Position
- Below the diagonal: Headers uses a module listed above it, which is the healthy direction.
26→15 Headers uses Infrastructure.Claims✕
- Connections
- 1 pair of types, where a type in Headers uses a type in Infrastructure.Claims.
- The types involved
Ocelot.Headers.AddHeadersToRequest→Ocelot.Infrastructure.Claims.IClaimsParser
- Direction
- Headers uses Infrastructure.Claims, so a change to Infrastructure.Claims can break Headers, while a change to Headers can't break Infrastructure.Claims.
- Position
- Below the diagonal: Headers uses a module listed above it, which is the healthy direction.
26→19 Headers uses Configuration.Creator✕
- Connections
- 4 pairs of types, where a type in Headers uses a type in Configuration.Creator.
- The types involved
Ocelot.Headers.AddHeadersToRequest→Ocelot.Configuration.Creator.AddHeaderOcelot.Headers.AddHeadersToResponse→Ocelot.Configuration.Creator.AddHeaderOcelot.Headers.IAddHeadersToRequest→Ocelot.Configuration.Creator.AddHeaderOcelot.Headers.IAddHeadersToResponse→Ocelot.Configuration.Creator.AddHeader
- Direction
- Headers uses Configuration.Creator, so a change to Configuration.Creator can break Headers, while a change to Headers can't break Configuration.Creator.
- Position
- Below the diagonal: Headers uses a module listed above it, which is the healthy direction.
26→20 Headers uses Configuration✕
- Connections
- 6 pairs of types, where a type in Headers uses a type in Configuration.
- The types involved
Ocelot.Headers.AddHeadersToRequest→Ocelot.Configuration.ClaimToThingOcelot.Headers.HttpContextRequestHeaderReplacer→Ocelot.Configuration.HeaderFindAndReplaceOcelot.Headers.HttpResponseHeaderReplacer→Ocelot.Configuration.HeaderFindAndReplaceOcelot.Headers.IAddHeadersToRequest→Ocelot.Configuration.ClaimToThingOcelot.Headers.IHttpContextRequestHeaderReplacer→Ocelot.Configuration.HeaderFindAndReplaceOcelot.Headers.IHttpResponseHeaderReplacer→Ocelot.Configuration.HeaderFindAndReplace
- Direction
- Headers uses Configuration, so a change to Configuration can break Headers, while a change to Headers can't break Configuration.
- Position
- Below the diagonal: Headers uses a module listed above it, which is the healthy direction.
27→1 LoadBalancer.Interfaces uses Values✕
- Connections
- 1 pair of types, where a type in LoadBalancer.Interfaces uses a type in Values.
- The types involved
Ocelot.LoadBalancer.Interfaces.ILoadBalancer→Ocelot.Values.ServiceHostAndPort
- Direction
- LoadBalancer.Interfaces uses Values, so a change to Values can break LoadBalancer.Interfaces, while a change to LoadBalancer.Interfaces can't break Values.
- Position
- Below the diagonal: LoadBalancer.Interfaces uses a module listed above it, which is the healthy direction.
27→3 LoadBalancer.Interfaces uses Responses✕
- Connections
- 4 pairs of types, where a type in LoadBalancer.Interfaces uses a type in Responses.
- The types involved
Ocelot.LoadBalancer.Interfaces.ILoadBalancer→Ocelot.Responses.ResponseOcelot.LoadBalancer.Interfaces.ILoadBalancerCreator→Ocelot.Responses.ResponseOcelot.LoadBalancer.Interfaces.ILoadBalancerFactory→Ocelot.Responses.ResponseOcelot.LoadBalancer.Interfaces.ILoadBalancerHouse→Ocelot.Responses.Response
- Direction
- LoadBalancer.Interfaces uses Responses, so a change to Responses can break LoadBalancer.Interfaces, while a change to LoadBalancer.Interfaces can't break Responses.
- Position
- Below the diagonal: LoadBalancer.Interfaces uses a module listed above it, which is the healthy direction.
27→4 LoadBalancer.Interfaces uses ServiceDiscovery.Providers✕
- Connections
- 1 pair of types, where a type in LoadBalancer.Interfaces uses a type in ServiceDiscovery.Providers.
- The types involved
Ocelot.LoadBalancer.Interfaces.ILoadBalancerCreator→Ocelot.ServiceDiscovery.Providers.IServiceDiscoveryProvider
- Direction
- LoadBalancer.Interfaces uses ServiceDiscovery.Providers, so a change to ServiceDiscovery.Providers can break LoadBalancer.Interfaces, while a change to LoadBalancer.Interfaces can't break ServiceDiscovery.Providers.
- Position
- Below the diagonal: LoadBalancer.Interfaces uses a module listed above it, which is the healthy direction.
27→20 LoadBalancer.Interfaces uses Configuration✕
- Connections
- 5 pairs of types, where a type in LoadBalancer.Interfaces uses a type in Configuration.
- The types involved
Ocelot.LoadBalancer.Interfaces.ILoadBalancerCreator→Ocelot.Configuration.DownstreamRouteOcelot.LoadBalancer.Interfaces.ILoadBalancerFactory→Ocelot.Configuration.DownstreamRouteOcelot.LoadBalancer.Interfaces.ILoadBalancerFactory→Ocelot.Configuration.ServiceProviderConfigurationOcelot.LoadBalancer.Interfaces.ILoadBalancerHouse→Ocelot.Configuration.DownstreamRouteOcelot.LoadBalancer.Interfaces.ILoadBalancerHouse→Ocelot.Configuration.ServiceProviderConfiguration
- Direction
- LoadBalancer.Interfaces uses Configuration, so a change to Configuration can break LoadBalancer.Interfaces, while a change to LoadBalancer.Interfaces can't break Configuration.
- Position
- Below the diagonal: LoadBalancer.Interfaces uses a module listed above it, which is the healthy direction.
28→2 Multiplexer uses Configuration.File✕
- Connections
- 1 pair of types, where a type in Multiplexer uses a type in Configuration.File.
- The types involved
Ocelot.Multiplexer.MultiplexingMiddleware→Ocelot.Configuration.File.AggregateRouteConfig
- Direction
- Multiplexer uses Configuration.File, so a change to Configuration.File can break Multiplexer, while a change to Multiplexer can't break Configuration.File.
- Position
- Below the diagonal: Multiplexer uses a module listed above it, which is the healthy direction.
28→3 Multiplexer uses Responses✕
- Connections
- 2 pairs of types, where a type in Multiplexer uses a type in Responses.
- The types involved
Ocelot.Multiplexer.IDefinedAggregatorProvider→Ocelot.Responses.ResponseOcelot.Multiplexer.ServiceLocatorDefinedAggregatorProvider→Ocelot.Responses.Response
- Direction
- Multiplexer uses Responses, so a change to Responses can break Multiplexer, while a change to Multiplexer can't break Responses.
- Position
- Below the diagonal: Multiplexer uses a module listed above it, which is the healthy direction.
28→5 Multiplexer uses DownstreamRouteFinder.UrlMatcher✕
- Connections
- 1 pair of types, where a type in Multiplexer uses a type in DownstreamRouteFinder.UrlMatcher.
- The types involved
Ocelot.Multiplexer.MultiplexingMiddleware→Ocelot.DownstreamRouteFinder.UrlMatcher.PlaceholderNameAndValue
- Direction
- Multiplexer uses DownstreamRouteFinder.UrlMatcher, so a change to DownstreamRouteFinder.UrlMatcher can break Multiplexer, while a change to Multiplexer can't break DownstreamRouteFinder.UrlMatcher.
- Position
- Below the diagonal: Multiplexer uses a module listed above it, which is the healthy direction.
28→7 Multiplexer uses Logging✕
- Connections
- 1 pair of types, where a type in Multiplexer uses a type in Logging.
- The types involved
Ocelot.Multiplexer.MultiplexingMiddleware→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- Multiplexer uses Logging, so a change to Logging can break Multiplexer, while a change to Multiplexer can't break Logging.
- Position
- Below the diagonal: Multiplexer uses a module listed above it, which is the healthy direction.
28→10 Multiplexer uses Middleware✕
- Connections
- 3 pairs of types, where a type in Multiplexer uses a type in Middleware.
- The types involved
Ocelot.Multiplexer.IDefinedAggregator→Ocelot.Middleware.DownstreamResponseOcelot.Multiplexer.MultiplexingMiddleware→Ocelot.Middleware.OcelotMiddlewareOcelot.Multiplexer.SimpleJsonResponseAggregator→Ocelot.Middleware.Header
- Direction
- Multiplexer uses Middleware, so a change to Middleware can break Multiplexer, while a change to Multiplexer can't break Middleware.
- Position
- Below the diagonal: Multiplexer uses a module listed above it, which is the healthy direction.
28→11 Multiplexer uses Errors✕
- Connections
- 1 pair of types, where a type in Multiplexer uses a type in Errors.
- The types involved
Ocelot.Multiplexer.CouldNotFindAggregatorError→Ocelot.Errors.Error
- Direction
- Multiplexer uses Errors, so a change to Errors can break Multiplexer, while a change to Multiplexer can't break Errors.
- Position
- Below the diagonal: Multiplexer uses a module listed above it, which is the healthy direction.
28→20 Multiplexer uses Configuration✕
- Connections
- 9 pairs of types, where a type in Multiplexer uses a type in Configuration.
- The types involved
Ocelot.Multiplexer.IDefinedAggregatorProvider→Ocelot.Configuration.RouteOcelot.Multiplexer.IResponseAggregator→Ocelot.Configuration.RouteOcelot.Multiplexer.IResponseAggregatorFactory→Ocelot.Configuration.RouteOcelot.Multiplexer.InMemoryResponseAggregatorFactory→Ocelot.Configuration.RouteOcelot.Multiplexer.MultiplexingMiddleware→Ocelot.Configuration.DownstreamRouteOcelot.Multiplexer.MultiplexingMiddleware→Ocelot.Configuration.RouteOcelot.Multiplexer.ServiceLocatorDefinedAggregatorProvider→Ocelot.Configuration.RouteOcelot.Multiplexer.SimpleJsonResponseAggregator→Ocelot.Configuration.RouteOcelot.Multiplexer.UserDefinedResponseAggregator→Ocelot.Configuration.Route
- Direction
- Multiplexer uses Configuration, so a change to Configuration can break Multiplexer, while a change to Multiplexer can't break Configuration.
- Position
- Below the diagonal: Multiplexer uses a module listed above it, which is the healthy direction.
29→1 PathManipulation uses Values✕
- Connections
- 2 pairs of types, where a type in PathManipulation uses a type in Values.
- The types involved
Ocelot.PathManipulation.ChangeDownstreamPathTemplate→Ocelot.Values.DownstreamPathTemplateOcelot.PathManipulation.IChangeDownstreamPathTemplate→Ocelot.Values.DownstreamPathTemplate
- Direction
- PathManipulation uses Values, so a change to Values can break PathManipulation, while a change to PathManipulation can't break Values.
- Position
- Below the diagonal: PathManipulation uses a module listed above it, which is the healthy direction.
29→3 PathManipulation uses Responses✕
- Connections
- 2 pairs of types, where a type in PathManipulation uses a type in Responses.
- The types involved
Ocelot.PathManipulation.ChangeDownstreamPathTemplate→Ocelot.Responses.ResponseOcelot.PathManipulation.IChangeDownstreamPathTemplate→Ocelot.Responses.Response
- Direction
- PathManipulation uses Responses, so a change to Responses can break PathManipulation, while a change to PathManipulation can't break Responses.
- Position
- Below the diagonal: PathManipulation uses a module listed above it, which is the healthy direction.
29→5 PathManipulation uses DownstreamRouteFinder.UrlMatcher✕
- Connections
- 2 pairs of types, where a type in PathManipulation uses a type in DownstreamRouteFinder.UrlMatcher.
- The types involved
Ocelot.PathManipulation.ChangeDownstreamPathTemplate→Ocelot.DownstreamRouteFinder.UrlMatcher.PlaceholderNameAndValueOcelot.PathManipulation.IChangeDownstreamPathTemplate→Ocelot.DownstreamRouteFinder.UrlMatcher.PlaceholderNameAndValue
- Direction
- PathManipulation uses DownstreamRouteFinder.UrlMatcher, so a change to DownstreamRouteFinder.UrlMatcher can break PathManipulation, while a change to PathManipulation can't break DownstreamRouteFinder.UrlMatcher.
- Position
- Below the diagonal: PathManipulation uses a module listed above it, which is the healthy direction.
29→15 PathManipulation uses Infrastructure.Claims✕
- Connections
- 1 pair of types, where a type in PathManipulation uses a type in Infrastructure.Claims.
- The types involved
Ocelot.PathManipulation.ChangeDownstreamPathTemplate→Ocelot.Infrastructure.Claims.IClaimsParser
- Direction
- PathManipulation uses Infrastructure.Claims, so a change to Infrastructure.Claims can break PathManipulation, while a change to PathManipulation can't break Infrastructure.Claims.
- Position
- Below the diagonal: PathManipulation uses a module listed above it, which is the healthy direction.
29→20 PathManipulation uses Configuration✕
- Connections
- 2 pairs of types, where a type in PathManipulation uses a type in Configuration.
- The types involved
Ocelot.PathManipulation.ChangeDownstreamPathTemplate→Ocelot.Configuration.ClaimToThingOcelot.PathManipulation.IChangeDownstreamPathTemplate→Ocelot.Configuration.ClaimToThing
- Direction
- PathManipulation uses Configuration, so a change to Configuration can break PathManipulation, while a change to PathManipulation can't break Configuration.
- Position
- Below the diagonal: PathManipulation uses a module listed above it, which is the healthy direction.
30→7 QualityOfService uses Logging✕
- Connections
- 6 pairs of types, where a type in QualityOfService uses a type in Logging.
- The types involved
Ocelot.QualityOfService.CircuitBreakerDelegatingHandler→Ocelot.Logging.IOcelotLoggerOcelot.QualityOfService.CircuitBreakerDelegatingHandler→Ocelot.Logging.IOcelotLoggerFactoryOcelot.QualityOfService.QosDelegatingHandler→Ocelot.Logging.IOcelotLoggerFactoryOcelot.QualityOfService.QosDelegatingHandlerDelegate→Ocelot.Logging.IOcelotLoggerFactoryOcelot.QualityOfService.QualityOfServiceFactory→Ocelot.Logging.IOcelotLoggerOcelot.QualityOfService.QualityOfServiceFactory→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- QualityOfService uses Logging, so a change to Logging can break QualityOfService, while a change to QualityOfService can't break Logging.
- Position
- Below the diagonal: QualityOfService uses a module listed above it, which is the healthy direction.
30→11 QualityOfService uses Errors✕
- Connections
- 1 pair of types, where a type in QualityOfService uses a type in Errors.
- The types involved
Ocelot.QualityOfService.UnableToFindQoSProviderError→Ocelot.Errors.Error
- Direction
- QualityOfService uses Errors, so a change to Errors can break QualityOfService, while a change to QualityOfService can't break Errors.
- Position
- Below the diagonal: QualityOfService uses a module listed above it, which is the healthy direction.
30→20 QualityOfService uses Configuration✕
- Connections
- 6 pairs of types, where a type in QualityOfService uses a type in Configuration.
- The types involved
Ocelot.QualityOfService.CircuitBreakerDelegatingHandler→Ocelot.Configuration.DownstreamRouteOcelot.QualityOfService.CircuitBreakerDelegatingHandler→Ocelot.Configuration.QoSOptionsOcelot.QualityOfService.IQualityOfServiceFactory→Ocelot.Configuration.DownstreamRouteOcelot.QualityOfService.QosDelegatingHandler→Ocelot.Configuration.DownstreamRouteOcelot.QualityOfService.QosDelegatingHandlerDelegate→Ocelot.Configuration.DownstreamRouteOcelot.QualityOfService.QualityOfServiceFactory→Ocelot.Configuration.DownstreamRoute
- Direction
- QualityOfService uses Configuration, so a change to Configuration can break QualityOfService, while a change to QualityOfService can't break Configuration.
- Position
- Below the diagonal: QualityOfService uses a module listed above it, which is the healthy direction.
31→3 QueryStrings uses Responses✕
- Connections
- 2 pairs of types, where a type in QueryStrings uses a type in Responses.
- The types involved
Ocelot.QueryStrings.AddQueriesToRequest→Ocelot.Responses.ResponseOcelot.QueryStrings.IAddQueriesToRequest→Ocelot.Responses.Response
- Direction
- QueryStrings uses Responses, so a change to Responses can break QueryStrings, while a change to QueryStrings can't break Responses.
- Position
- Below the diagonal: QueryStrings uses a module listed above it, which is the healthy direction.
31→7 QueryStrings uses Logging✕
- Connections
- 1 pair of types, where a type in QueryStrings uses a type in Logging.
- The types involved
Ocelot.QueryStrings.ClaimsToQueryStringMiddleware→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- QueryStrings uses Logging, so a change to Logging can break QueryStrings, while a change to QueryStrings can't break Logging.
- Position
- Below the diagonal: QueryStrings uses a module listed above it, which is the healthy direction.
31→9 QueryStrings uses Request.Middleware✕
- Connections
- 2 pairs of types, where a type in QueryStrings uses a type in Request.Middleware.
- The types involved
Ocelot.QueryStrings.AddQueriesToRequest→Ocelot.Request.Middleware.DownstreamRequestOcelot.QueryStrings.IAddQueriesToRequest→Ocelot.Request.Middleware.DownstreamRequest
- Direction
- QueryStrings uses Request.Middleware, so a change to Request.Middleware can break QueryStrings, while a change to QueryStrings can't break Request.Middleware.
- Position
- Below the diagonal: QueryStrings uses a module listed above it, which is the healthy direction.
31→10 QueryStrings uses Middleware✕
- Connections
- 1 pair of types, where a type in QueryStrings uses a type in Middleware.
- The types involved
Ocelot.QueryStrings.ClaimsToQueryStringMiddleware→Ocelot.Middleware.OcelotMiddleware
- Direction
- QueryStrings uses Middleware, so a change to Middleware can break QueryStrings, while a change to QueryStrings can't break Middleware.
- Position
- Below the diagonal: QueryStrings uses a module listed above it, which is the healthy direction.
31→15 QueryStrings uses Infrastructure.Claims✕
- Connections
- 1 pair of types, where a type in QueryStrings uses a type in Infrastructure.Claims.
- The types involved
Ocelot.QueryStrings.AddQueriesToRequest→Ocelot.Infrastructure.Claims.IClaimsParser
- Direction
- QueryStrings uses Infrastructure.Claims, so a change to Infrastructure.Claims can break QueryStrings, while a change to QueryStrings can't break Infrastructure.Claims.
- Position
- Below the diagonal: QueryStrings uses a module listed above it, which is the healthy direction.
31→20 QueryStrings uses Configuration✕
- Connections
- 2 pairs of types, where a type in QueryStrings uses a type in Configuration.
- The types involved
Ocelot.QueryStrings.AddQueriesToRequest→Ocelot.Configuration.ClaimToThingOcelot.QueryStrings.IAddQueriesToRequest→Ocelot.Configuration.ClaimToThing
- Direction
- QueryStrings uses Configuration, so a change to Configuration can break QueryStrings, while a change to QueryStrings can't break Configuration.
- Position
- Below the diagonal: QueryStrings uses a module listed above it, which is the healthy direction.
32→7 RateLimiting uses Logging✕
- Connections
- 1 pair of types, where a type in RateLimiting uses a type in Logging.
- The types involved
Ocelot.RateLimiting.RateLimitingMiddleware→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- RateLimiting uses Logging, so a change to Logging can break RateLimiting, while a change to RateLimiting can't break Logging.
- Position
- Below the diagonal: RateLimiting uses a module listed above it, which is the healthy direction.
32→10 RateLimiting uses Middleware✕
- Connections
- 2 pairs of types, where a type in RateLimiting uses a type in Middleware.
- The types involved
Ocelot.RateLimiting.RateLimitingMiddleware→Ocelot.Middleware.DownstreamResponseOcelot.RateLimiting.RateLimitingMiddleware→Ocelot.Middleware.OcelotMiddleware
- Direction
- RateLimiting uses Middleware, so a change to Middleware can break RateLimiting, while a change to RateLimiting can't break Middleware.
- Position
- Below the diagonal: RateLimiting uses a module listed above it, which is the healthy direction.
32→11 RateLimiting uses Errors✕
- Connections
- 1 pair of types, where a type in RateLimiting uses a type in Errors.
- The types involved
Ocelot.RateLimiting.QuotaExceededError→Ocelot.Errors.Error
- Direction
- RateLimiting uses Errors, so a change to Errors can break RateLimiting, while a change to RateLimiting can't break Errors.
- Position
- Below the diagonal: RateLimiting uses a module listed above it, which is the healthy direction.
32→20 RateLimiting uses Configuration✕
- Connections
- 6 pairs of types, where a type in RateLimiting uses a type in Configuration.
- The types involved
Ocelot.RateLimiting.IRateLimiting→Ocelot.Configuration.RateLimitOptionsOcelot.RateLimiting.IRateLimiting→Ocelot.Configuration.RateLimitRuleOcelot.RateLimiting.RateLimiting→Ocelot.Configuration.RateLimitOptionsOcelot.RateLimiting.RateLimiting→Ocelot.Configuration.RateLimitRuleOcelot.RateLimiting.RateLimitingMiddleware→Ocelot.Configuration.DownstreamRouteOcelot.RateLimiting.RateLimitingMiddleware→Ocelot.Configuration.RateLimitOptions
- Direction
- RateLimiting uses Configuration, so a change to Configuration can break RateLimiting, while a change to RateLimiting can't break Configuration.
- Position
- Below the diagonal: RateLimiting uses a module listed above it, which is the healthy direction.
33→3 Security uses Responses✕
- Connections
- 2 pairs of types, where a type in Security uses a type in Responses.
- The types involved
Ocelot.Security.IPSecurityPolicy→Ocelot.Responses.ResponseOcelot.Security.ISecurityPolicy→Ocelot.Responses.Response
- Direction
- Security uses Responses, so a change to Responses can break Security, while a change to Security can't break Responses.
- Position
- Below the diagonal: Security uses a module listed above it, which is the healthy direction.
33→7 Security uses Logging✕
- Connections
- 1 pair of types, where a type in Security uses a type in Logging.
- The types involved
Ocelot.Security.SecurityMiddleware→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- Security uses Logging, so a change to Logging can break Security, while a change to Security can't break Logging.
- Position
- Below the diagonal: Security uses a module listed above it, which is the healthy direction.
33→10 Security uses Middleware✕
- Connections
- 1 pair of types, where a type in Security uses a type in Middleware.
- The types involved
Ocelot.Security.SecurityMiddleware→Ocelot.Middleware.OcelotMiddleware
- Direction
- Security uses Middleware, so a change to Middleware can break Security, while a change to Security can't break Middleware.
- Position
- Below the diagonal: Security uses a module listed above it, which is the healthy direction.
33→11 Security uses Errors✕
- Connections
- 2 pairs of types, where a type in Security uses a type in Errors.
- The types involved
Ocelot.Security.SecurityError→Ocelot.Errors.ErrorOcelot.Security.SecurityMiddleware→Ocelot.Errors.Error
- Direction
- Security uses Errors, so a change to Errors can break Security, while a change to Security can't break Errors.
- Position
- Below the diagonal: Security uses a module listed above it, which is the healthy direction.
33→20 Security uses Configuration✕
- Connections
- 2 pairs of types, where a type in Security uses a type in Configuration.
- The types involved
Ocelot.Security.IPSecurityPolicy→Ocelot.Configuration.DownstreamRouteOcelot.Security.ISecurityPolicy→Ocelot.Configuration.DownstreamRoute
- Direction
- Security uses Configuration, so a change to Configuration can break Security, while a change to Security can't break Configuration.
- Position
- Below the diagonal: Security uses a module listed above it, which is the healthy direction.
34→2 Administration uses Configuration.File✕
- Connections
- 1 pair of types, where a type in Administration uses a type in Configuration.File.
- The types involved
Ocelot.Administration.FileConfigurationController→Ocelot.Configuration.File.FileConfiguration
- Direction
- Administration uses Configuration.File, so a change to Configuration.File can break Administration, while a change to Administration can't break Configuration.File.
- Position
- Below the diagonal: Administration uses a module listed above it, which is the healthy direction.
34→8 Administration uses Configuration.Repository✕
- Connections
- 2 pairs of types, where a type in Administration uses a type in Configuration.Repository.
- The types involved
Ocelot.Administration.FileConfigurationController→Ocelot.Configuration.Repository.IFileConfigurationRepositoryOcelot.Administration.FileConfigurationController→Ocelot.Configuration.Repository.IFileConfigurationSetter
- Direction
- Administration uses Configuration.Repository, so a change to Configuration.Repository can break Administration, while a change to Administration can't break Configuration.Repository.
- Position
- Below the diagonal: Administration uses a module listed above it, which is the healthy direction.
34→21 Administration uses Cache✕
- Connections
- 2 pairs of types, where a type in Administration uses a type in Cache.
- The types involved
Ocelot.Administration.OutputCacheController→Ocelot.Cache.CachedResponseOcelot.Administration.OutputCacheController→Ocelot.Cache.IOcelotCache
- Direction
- Administration uses Cache, so a change to Cache can break Administration, while a change to Administration can't break Cache.
- Position
- Below the diagonal: Administration uses a module listed above it, which is the healthy direction.
35→1 LoadBalancer uses Values✕
- Connections
- 3 pairs of types, where a type in LoadBalancer uses a type in Values.
- The types involved
Ocelot.LoadBalancer.Lease→Ocelot.Values.ServiceHostAndPortOcelot.LoadBalancer.LeaseEventArgs→Ocelot.Values.ServiceOcelot.LoadBalancer.StickySession→Ocelot.Values.ServiceHostAndPort
- Direction
- LoadBalancer uses Values, so a change to Values can break LoadBalancer, while a change to LoadBalancer can't break Values.
- Position
- Below the diagonal: LoadBalancer uses a module listed above it, which is the healthy direction.
35→3 LoadBalancer uses Responses✕
- Connections
- 2 pairs of types, where a type in LoadBalancer uses a type in Responses.
- The types involved
Ocelot.LoadBalancer.LoadBalancerFactory→Ocelot.Responses.ResponseOcelot.LoadBalancer.LoadBalancerHouse→Ocelot.Responses.Response
- Direction
- LoadBalancer uses Responses, so a change to Responses can break LoadBalancer, while a change to LoadBalancer can't break Responses.
- Position
- Below the diagonal: LoadBalancer uses a module listed above it, which is the healthy direction.
35→7 LoadBalancer uses Logging✕
- Connections
- 1 pair of types, where a type in LoadBalancer uses a type in Logging.
- The types involved
Ocelot.LoadBalancer.LoadBalancingMiddleware→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- LoadBalancer uses Logging, so a change to Logging can break LoadBalancer, while a change to LoadBalancer can't break Logging.
- Position
- Below the diagonal: LoadBalancer uses a module listed above it, which is the healthy direction.
35→10 LoadBalancer uses Middleware✕
- Connections
- 1 pair of types, where a type in LoadBalancer uses a type in Middleware.
- The types involved
Ocelot.LoadBalancer.LoadBalancingMiddleware→Ocelot.Middleware.OcelotMiddleware
- Direction
- LoadBalancer uses Middleware, so a change to Middleware can break LoadBalancer, while a change to LoadBalancer can't break Middleware.
- Position
- Below the diagonal: LoadBalancer uses a module listed above it, which is the healthy direction.
35→16 LoadBalancer uses ServiceDiscovery✕
- Connections
- 1 pair of types, where a type in LoadBalancer uses a type in ServiceDiscovery.
- The types involved
Ocelot.LoadBalancer.LoadBalancerFactory→Ocelot.ServiceDiscovery.IServiceDiscoveryProviderFactory
- Direction
- LoadBalancer uses ServiceDiscovery, so a change to ServiceDiscovery can break LoadBalancer, while a change to LoadBalancer can't break ServiceDiscovery.
- Position
- Below the diagonal: LoadBalancer uses a module listed above it, which is the healthy direction.
35→20 LoadBalancer uses Configuration✕
- Connections
- 4 pairs of types, where a type in LoadBalancer uses a type in Configuration.
- The types involved
Ocelot.LoadBalancer.LoadBalancerFactory→Ocelot.Configuration.DownstreamRouteOcelot.LoadBalancer.LoadBalancerFactory→Ocelot.Configuration.ServiceProviderConfigurationOcelot.LoadBalancer.LoadBalancerHouse→Ocelot.Configuration.DownstreamRouteOcelot.LoadBalancer.LoadBalancerHouse→Ocelot.Configuration.ServiceProviderConfiguration
- Direction
- LoadBalancer uses Configuration, so a change to Configuration can break LoadBalancer, while a change to LoadBalancer can't break Configuration.
- Position
- Below the diagonal: LoadBalancer uses a module listed above it, which is the healthy direction.
35→27 LoadBalancer uses LoadBalancer.Interfaces✕
- Connections
- 7 pairs of types, where a type in LoadBalancer uses a type in LoadBalancer.Interfaces.
- The types involved
Ocelot.LoadBalancer.LoadBalancerFactory→Ocelot.LoadBalancer.Interfaces.ILoadBalancerOcelot.LoadBalancer.LoadBalancerFactory→Ocelot.LoadBalancer.Interfaces.ILoadBalancerCreatorOcelot.LoadBalancer.LoadBalancerFactory→Ocelot.LoadBalancer.Interfaces.ILoadBalancerFactoryOcelot.LoadBalancer.LoadBalancerHouse→Ocelot.LoadBalancer.Interfaces.ILoadBalancerOcelot.LoadBalancer.LoadBalancerHouse→Ocelot.LoadBalancer.Interfaces.ILoadBalancerFactoryOcelot.LoadBalancer.LoadBalancerHouse→Ocelot.LoadBalancer.Interfaces.ILoadBalancerHouseOcelot.LoadBalancer.LoadBalancingMiddleware→Ocelot.LoadBalancer.Interfaces.ILoadBalancerHouse
- Direction
- LoadBalancer uses LoadBalancer.Interfaces, so a change to LoadBalancer.Interfaces can break LoadBalancer, while a change to LoadBalancer can't break LoadBalancer.Interfaces.
- Position
- Below the diagonal: LoadBalancer uses a module listed above it, which is the healthy direction.
36→3 LoadBalancer.Creators uses Responses✕
- Connections
- 5 pairs of types, where a type in LoadBalancer.Creators uses a type in Responses.
- The types involved
Ocelot.LoadBalancer.Creators.CookieStickySessionsCreator→Ocelot.Responses.ResponseOcelot.LoadBalancer.Creators.DelegateInvokingLoadBalancerCreator→Ocelot.Responses.ResponseOcelot.LoadBalancer.Creators.LeastConnectionCreator→Ocelot.Responses.ResponseOcelot.LoadBalancer.Creators.NoLoadBalancerCreator→Ocelot.Responses.ResponseOcelot.LoadBalancer.Creators.RoundRobinCreator→Ocelot.Responses.Response
- Direction
- LoadBalancer.Creators uses Responses, so a change to Responses can break LoadBalancer.Creators, while a change to LoadBalancer.Creators can't break Responses.
- Position
- Below the diagonal: LoadBalancer.Creators uses a module listed above it, which is the healthy direction.
36→4 LoadBalancer.Creators uses ServiceDiscovery.Providers✕
- Connections
- 5 pairs of types, where a type in LoadBalancer.Creators uses a type in ServiceDiscovery.Providers.
- The types involved
Ocelot.LoadBalancer.Creators.CookieStickySessionsCreator→Ocelot.ServiceDiscovery.Providers.IServiceDiscoveryProviderOcelot.LoadBalancer.Creators.DelegateInvokingLoadBalancerCreator→Ocelot.ServiceDiscovery.Providers.IServiceDiscoveryProviderOcelot.LoadBalancer.Creators.LeastConnectionCreator→Ocelot.ServiceDiscovery.Providers.IServiceDiscoveryProviderOcelot.LoadBalancer.Creators.NoLoadBalancerCreator→Ocelot.ServiceDiscovery.Providers.IServiceDiscoveryProviderOcelot.LoadBalancer.Creators.RoundRobinCreator→Ocelot.ServiceDiscovery.Providers.IServiceDiscoveryProvider
- Direction
- LoadBalancer.Creators uses ServiceDiscovery.Providers, so a change to ServiceDiscovery.Providers can break LoadBalancer.Creators, while a change to LoadBalancer.Creators can't break ServiceDiscovery.Providers.
- Position
- Below the diagonal: LoadBalancer.Creators uses a module listed above it, which is the healthy direction.
36→20 LoadBalancer.Creators uses Configuration✕
- Connections
- 5 pairs of types, where a type in LoadBalancer.Creators uses a type in Configuration.
- The types involved
Ocelot.LoadBalancer.Creators.CookieStickySessionsCreator→Ocelot.Configuration.DownstreamRouteOcelot.LoadBalancer.Creators.DelegateInvokingLoadBalancerCreator→Ocelot.Configuration.DownstreamRouteOcelot.LoadBalancer.Creators.LeastConnectionCreator→Ocelot.Configuration.DownstreamRouteOcelot.LoadBalancer.Creators.NoLoadBalancerCreator→Ocelot.Configuration.DownstreamRouteOcelot.LoadBalancer.Creators.RoundRobinCreator→Ocelot.Configuration.DownstreamRoute
- Direction
- LoadBalancer.Creators uses Configuration, so a change to Configuration can break LoadBalancer.Creators, while a change to LoadBalancer.Creators can't break Configuration.
- Position
- Below the diagonal: LoadBalancer.Creators uses a module listed above it, which is the healthy direction.
36→27 LoadBalancer.Creators uses LoadBalancer.Interfaces✕
- Connections
- 10 pairs of types, where a type in LoadBalancer.Creators uses a type in LoadBalancer.Interfaces.
- The types involved
Ocelot.LoadBalancer.Creators.CookieStickySessionsCreator→Ocelot.LoadBalancer.Interfaces.ILoadBalancerOcelot.LoadBalancer.Creators.CookieStickySessionsCreator→Ocelot.LoadBalancer.Interfaces.ILoadBalancerCreatorOcelot.LoadBalancer.Creators.DelegateInvokingLoadBalancerCreator→Ocelot.LoadBalancer.Interfaces.ILoadBalancerOcelot.LoadBalancer.Creators.DelegateInvokingLoadBalancerCreator→Ocelot.LoadBalancer.Interfaces.ILoadBalancerCreatorOcelot.LoadBalancer.Creators.LeastConnectionCreator→Ocelot.LoadBalancer.Interfaces.ILoadBalancerOcelot.LoadBalancer.Creators.LeastConnectionCreator→Ocelot.LoadBalancer.Interfaces.ILoadBalancerCreatorOcelot.LoadBalancer.Creators.NoLoadBalancerCreator→Ocelot.LoadBalancer.Interfaces.ILoadBalancerOcelot.LoadBalancer.Creators.NoLoadBalancerCreator→Ocelot.LoadBalancer.Interfaces.ILoadBalancerCreatorOcelot.LoadBalancer.Creators.RoundRobinCreator→Ocelot.LoadBalancer.Interfaces.ILoadBalancerOcelot.LoadBalancer.Creators.RoundRobinCreator→Ocelot.LoadBalancer.Interfaces.ILoadBalancerCreator
- Direction
- LoadBalancer.Creators uses LoadBalancer.Interfaces, so a change to LoadBalancer.Interfaces can break LoadBalancer.Creators, while a change to LoadBalancer.Creators can't break LoadBalancer.Interfaces.
- Position
- Below the diagonal: LoadBalancer.Creators uses a module listed above it, which is the healthy direction.
37→3 Requester uses Responses✕
- Connections
- 2 pairs of types, where a type in Requester uses a type in Responses.
- The types involved
Ocelot.Requester.IHttpRequester→Ocelot.Responses.ResponseOcelot.Requester.MessageInvokerHttpRequester→Ocelot.Responses.Response
- Direction
- Requester uses Responses, so a change to Responses can break Requester, while a change to Requester can't break Responses.
- Position
- Below the diagonal: Requester uses a module listed above it, which is the healthy direction.
37→7 Requester uses Logging✕
- Connections
- 7 pairs of types, where a type in Requester uses a type in Logging.
- The types involved
Ocelot.Requester.DelegatingHandlerFactory→Ocelot.Logging.IOcelotLoggerOcelot.Requester.DelegatingHandlerFactory→Ocelot.Logging.IOcelotLoggerFactoryOcelot.Requester.DelegatingHandlerFactory→Ocelot.Logging.ITracingHandlerFactoryOcelot.Requester.MessageInvokerHttpRequester→Ocelot.Logging.IOcelotLoggerOcelot.Requester.MessageInvokerHttpRequester→Ocelot.Logging.IOcelotLoggerFactoryOcelot.Requester.MessageInvokerPool→Ocelot.Logging.IOcelotLoggerOcelot.Requester.MessageInvokerPool→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- Requester uses Logging, so a change to Logging can break Requester, while a change to Requester can't break Logging.
- Position
- Below the diagonal: Requester uses a module listed above it, which is the healthy direction.
37→11 Requester uses Errors✕
- Connections
- 6 pairs of types, where a type in Requester uses a type in Errors.
- The types involved
Ocelot.Requester.BadRequestError→Ocelot.Errors.ErrorOcelot.Requester.ConnectionToDownstreamServiceError→Ocelot.Errors.ErrorOcelot.Requester.HttpExceptionToErrorMapper→Ocelot.Errors.ErrorOcelot.Requester.IExceptionToErrorMapper→Ocelot.Errors.ErrorOcelot.Requester.RequestCanceledError→Ocelot.Errors.ErrorOcelot.Requester.UnableToCompleteRequestError→Ocelot.Errors.Error
- Direction
- Requester uses Errors, so a change to Errors can break Requester, while a change to Requester can't break Errors.
- Position
- Below the diagonal: Requester uses a module listed above it, which is the healthy direction.
37→20 Requester uses Configuration✕
- Connections
- 5 pairs of types, where a type in Requester uses a type in Configuration.
- The types involved
Ocelot.Requester.DelegatingHandlerFactory→Ocelot.Configuration.DownstreamRouteOcelot.Requester.IDelegatingHandlerFactory→Ocelot.Configuration.DownstreamRouteOcelot.Requester.IMessageInvokerPool→Ocelot.Configuration.DownstreamRouteOcelot.Requester.MessageInvokerCacheKey→Ocelot.Configuration.DownstreamRouteOcelot.Requester.MessageInvokerPool→Ocelot.Configuration.DownstreamRoute
- Direction
- Requester uses Configuration, so a change to Configuration can break Requester, while a change to Requester can't break Configuration.
- Position
- Below the diagonal: Requester uses a module listed above it, which is the healthy direction.
37→30 Requester uses QualityOfService✕
- Connections
- 1 pair of types, where a type in Requester uses a type in QualityOfService.
- The types involved
Ocelot.Requester.DelegatingHandlerFactory→Ocelot.QualityOfService.IQualityOfServiceFactory
- Direction
- Requester uses QualityOfService, so a change to QualityOfService can break Requester, while a change to Requester can't break QualityOfService.
- Position
- Below the diagonal: Requester uses a module listed above it, which is the healthy direction.
38→10 Responder uses Middleware✕
- Connections
- 3 pairs of types, where a type in Responder uses a type in Middleware.
- The types involved
Ocelot.Responder.HttpContextResponder→Ocelot.Middleware.DownstreamResponseOcelot.Responder.HttpContextResponder→Ocelot.Middleware.HeaderOcelot.Responder.IHttpResponder→Ocelot.Middleware.DownstreamResponse
- Direction
- Responder uses Middleware, so a change to Middleware can break Responder, while a change to Responder can't break Middleware.
- Position
- Below the diagonal: Responder uses a module listed above it, which is the healthy direction.
38→11 Responder uses Errors✕
- Connections
- 2 pairs of types, where a type in Responder uses a type in Errors.
- The types involved
Ocelot.Responder.ErrorsToHttpStatusCodeMapper→Ocelot.Errors.ErrorOcelot.Responder.IErrorsToHttpStatusCodeMapper→Ocelot.Errors.Error
- Direction
- Responder uses Errors, so a change to Errors can break Responder, while a change to Responder can't break Errors.
- Position
- Below the diagonal: Responder uses a module listed above it, which is the healthy direction.
38→26 Responder uses Headers✕
- Connections
- 1 pair of types, where a type in Responder uses a type in Headers.
- The types involved
Ocelot.Responder.HttpContextResponder→Ocelot.Headers.IRemoveOutputHeaders
- Direction
- Responder uses Headers, so a change to Headers can break Responder, while a change to Responder can't break Headers.
- Position
- Below the diagonal: Responder uses a module listed above it, which is the healthy direction.
39→1 LoadBalancer.Balancers uses Values✕
- Connections
- 7 pairs of types, where a type in LoadBalancer.Balancers uses a type in Values.
- The types involved
Ocelot.LoadBalancer.Balancers.CookieStickySessions→Ocelot.Values.ServiceHostAndPortOcelot.LoadBalancer.Balancers.LeastConnection→Ocelot.Values.ServiceOcelot.LoadBalancer.Balancers.LeastConnection→Ocelot.Values.ServiceHostAndPortOcelot.LoadBalancer.Balancers.NoLoadBalancer→Ocelot.Values.ServiceOcelot.LoadBalancer.Balancers.NoLoadBalancer→Ocelot.Values.ServiceHostAndPortOcelot.LoadBalancer.Balancers.RoundRobin→Ocelot.Values.ServiceOcelot.LoadBalancer.Balancers.RoundRobin→Ocelot.Values.ServiceHostAndPort
- Direction
- LoadBalancer.Balancers uses Values, so a change to Values can break LoadBalancer.Balancers, while a change to LoadBalancer.Balancers can't break Values.
- Position
- Below the diagonal: LoadBalancer.Balancers uses a module listed above it, which is the healthy direction.
39→3 LoadBalancer.Balancers uses Responses✕
- Connections
- 4 pairs of types, where a type in LoadBalancer.Balancers uses a type in Responses.
- The types involved
Ocelot.LoadBalancer.Balancers.CookieStickySessions→Ocelot.Responses.ResponseOcelot.LoadBalancer.Balancers.LeastConnection→Ocelot.Responses.ResponseOcelot.LoadBalancer.Balancers.NoLoadBalancer→Ocelot.Responses.ResponseOcelot.LoadBalancer.Balancers.RoundRobin→Ocelot.Responses.Response
- Direction
- LoadBalancer.Balancers uses Responses, so a change to Responses can break LoadBalancer.Balancers, while a change to LoadBalancer.Balancers can't break Responses.
- Position
- Below the diagonal: LoadBalancer.Balancers uses a module listed above it, which is the healthy direction.
39→14 LoadBalancer.Balancers uses Infrastructure✕
- Connections
- 1 pair of types, where a type in LoadBalancer.Balancers uses a type in Infrastructure.
- The types involved
Ocelot.LoadBalancer.Balancers.CookieStickySessions→Ocelot.Infrastructure.IBus
- Direction
- LoadBalancer.Balancers uses Infrastructure, so a change to Infrastructure can break LoadBalancer.Balancers, while a change to LoadBalancer.Balancers can't break Infrastructure.
- Position
- Below the diagonal: LoadBalancer.Balancers uses a module listed above it, which is the healthy direction.
39→27 LoadBalancer.Balancers uses LoadBalancer.Interfaces✕
- Connections
- 4 pairs of types, where a type in LoadBalancer.Balancers uses a type in LoadBalancer.Interfaces.
- The types involved
Ocelot.LoadBalancer.Balancers.CookieStickySessions→Ocelot.LoadBalancer.Interfaces.ILoadBalancerOcelot.LoadBalancer.Balancers.LeastConnection→Ocelot.LoadBalancer.Interfaces.ILoadBalancerOcelot.LoadBalancer.Balancers.NoLoadBalancer→Ocelot.LoadBalancer.Interfaces.ILoadBalancerOcelot.LoadBalancer.Balancers.RoundRobin→Ocelot.LoadBalancer.Interfaces.ILoadBalancer
- Direction
- LoadBalancer.Balancers uses LoadBalancer.Interfaces, so a change to LoadBalancer.Interfaces can break LoadBalancer.Balancers, while a change to LoadBalancer.Balancers can't break LoadBalancer.Interfaces.
- Position
- Below the diagonal: LoadBalancer.Balancers uses a module listed above it, which is the healthy direction.
39→35 LoadBalancer.Balancers uses LoadBalancer✕
- Connections
- 5 pairs of types, where a type in LoadBalancer.Balancers uses a type in LoadBalancer.
- The types involved
Ocelot.LoadBalancer.Balancers.CookieStickySessions→Ocelot.LoadBalancer.StickySessionOcelot.LoadBalancer.Balancers.LeastConnection→Ocelot.LoadBalancer.LeaseOcelot.LoadBalancer.Balancers.LeastConnection→Ocelot.LoadBalancer.LeaseEventArgsOcelot.LoadBalancer.Balancers.RoundRobin→Ocelot.LoadBalancer.LeaseOcelot.LoadBalancer.Balancers.RoundRobin→Ocelot.LoadBalancer.LeaseEventArgs
- Direction
- LoadBalancer.Balancers uses LoadBalancer, so a change to LoadBalancer can break LoadBalancer.Balancers, while a change to LoadBalancer.Balancers can't break LoadBalancer.
- Position
- Below the diagonal: LoadBalancer.Balancers uses a module listed above it, which is the healthy direction.
40→3 Requester.Middleware uses Responses✕
- Connections
- 1 pair of types, where a type in Requester.Middleware uses a type in Responses.
- The types involved
Ocelot.Requester.Middleware.HttpRequesterMiddleware→Ocelot.Responses.Response
- Direction
- Requester.Middleware uses Responses, so a change to Responses can break Requester.Middleware, while a change to Requester.Middleware can't break Responses.
- Position
- Below the diagonal: Requester.Middleware uses a module listed above it, which is the healthy direction.
40→7 Requester.Middleware uses Logging✕
- Connections
- 1 pair of types, where a type in Requester.Middleware uses a type in Logging.
- The types involved
Ocelot.Requester.Middleware.HttpRequesterMiddleware→Ocelot.Logging.IOcelotLoggerFactory
- Direction
- Requester.Middleware uses Logging, so a change to Logging can break Requester.Middleware, while a change to Requester.Middleware can't break Logging.
- Position
- Below the diagonal: Requester.Middleware uses a module listed above it, which is the healthy direction.
40→10 Requester.Middleware uses Middleware✕
- Connections
- 1 pair of types, where a type in Requester.Middleware uses a type in Middleware.
- The types involved
Ocelot.Requester.Middleware.HttpRequesterMiddleware→Ocelot.Middleware.OcelotMiddleware
- Direction
- Requester.Middleware uses Middleware, so a change to Middleware can break Requester.Middleware, while a change to Requester.Middleware can't break Middleware.
- Position
- Below the diagonal: Requester.Middleware uses a module listed above it, which is the healthy direction.
40→37 Requester.Middleware uses Requester✕
- Connections
- 1 pair of types, where a type in Requester.Middleware uses a type in Requester.
- The types involved
Ocelot.Requester.Middleware.HttpRequesterMiddleware→Ocelot.Requester.IHttpRequester
- Direction
- Requester.Middleware uses Requester, so a change to Requester can break Requester.Middleware, while a change to Requester.Middleware can't break Requester.
- Position
- Below the diagonal: Requester.Middleware uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 34 | High / Critical |
| A02:2025 — Security Misconfiguration | 31 | High / Critical |
| A07:2025 — Authentication Failures | 4 | High / Critical |
Roadmap
Top priorities: Stop accepting every TLS certificate: remove the always-true validation callback so the platform verifies the chain, hostname and expiry. If one self-signed certificate must be trusted, pin it by public key or thumbprint on the single handler that needs it and reject all others — never process-wide; Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.); Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). | +4.3 pts | Low | Secret Scanning |
| Stop accepting every TLS certificate: remove the always-true validation callback so the platform verifies the chain, hostname and expiry. If one self-signed certificate must be trusted, pin it by public key or thumbprint on the single handler that needs it and reject all others — never process-wide. | +7.1 pts | Medium | Web-Security Posture |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED, REDACTED. | +2.8 pts | Low | Static Analysis (SAST) |
| Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.). | +5.1 pts | Medium | Data Protection |
| Resolve the 8 Critical IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (2). | +2.1 pts | Low | IaC & Container Security |
| Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). | +1.7 pts | Low | Secrets (history) |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. | +1.7 pts | Low | Static Analysis (SAST) |
| Resolve the 12 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (3), REDACTED (2). | +3.2 pts | Medium | IaC & Container Security |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.1 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.5 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/RateLimiting/RateLimiting.cs | 5.8 | Mixed | Explicit Debt: FileScopedPragmaDisable |
| src/WebSockets/WebSocketsProxyMiddleware.cs | 5.8 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| unit/DependencyInjection/ConfigurationBuilderExtensionsTests.cs | 5.8 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Ocelot.csproj | 5.9 | Mixed | Explicit Debt: NoWarnInCsproj |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/Multiplexer/SimpleJsonResponseAggregator.cs | 6.0 | Mixed | Explicit Debt: TodoComment |
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 68 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 68 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, 572 of 588 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — 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. Coverage NOT READ here — but this repository measures it: a Codecov configuration (.github/codecov.yml) and a coverage step in CI (`coverlet`) shows that coverage is collected and tracked in your own CI. The suite could not be built/run in-image and no machine-readable report was present in the working tree at scan time, so the number could not be read — it is excluded from the score rather than treated as unmeasured-by-the-team. To have it read, commit the lcov/Cobertura artifact your CI produces (a hosted scan measures a clone of the repository, so only a committed report reaches it — `git add -f` that one file if it is gitignored), or make the suite runnable in-image. For context only, test code is ≈ 100% of production LoC (44,655 test / 18,418 production) — a rough proxy, NOT a coverage measurement. You can widen what we reach: optional: commit the lcov/Cobertura artifact your CI produces (a hosted scan measures a clone of the repository, so only a committed report reaches it — `git add -f` that one file if it is gitignored), or make the suite runnable in-image, and the real number is read.
- D11 Test Reliability — 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. Test reliability is scored on the 1 tier(s) that produced comparable repeat runs; 1 tier(s) did not, and are excluded from the measurement rather than counted (unit: measured (0 flaky); other: not included — too large to re-run within its budget). This is OUR limitation, not a defect in the repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: /usr/share/dotnet/sdk/10.0.400/NuGet.targets(521,5): error MSB3202: The project file "src/Ocelot/Ocelot.csproj" was not found. [samples/ServiceFabric/Ocelot.Samples.ServiceFabric.sln].
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
- D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A scan loads every live solution in the repository into one workspace. Every score, lens, and finding here reflects the projects of `Ocelot.slnx`, `Ocelot.Samples.slnx`, `samples/ServiceFabric/Ocelot.Samples.ServiceFabric.sln`, `samples/Kubernetes/OcelotKube.sln`, `samples/GraphQL/OcelotGraphQL.sln`, `samples/Eureka/OcelotEureka.sln`; 3 further solution(s) found in this tree (`samples/Eureka/OcelotEureka.sln`, `samples/GraphQL/OcelotGraphQL.sln`, `samples/Kubernetes/OcelotKube.sln`) could not be added to it — their project list could not be read, or none of their projects opened — so their code is not represented in the headline. (This is a count of the solutions discovery found and could not show to be covered by the analyzed ones — not a claim about how many solution files the repository contains.) If one of them is an archived or vendored tree, declaring it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — excludes it from discovery the same way generated code is. You can widen what we reach: if one of these solutions is live code, check that it opens on its own (`dotnet build <solution>`); if it is archived or vendored, declare it so.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `manual/ocelot.identityserver4.json`, `manual/ocelot.json`, `REDACTED` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Configuration/File/AggregateRouteConfig.cs`, `src/DownstreamRouteFinder/UrlMatcher/PlaceholderNameAndValue.cs`, `src/Errors/RequestTimedOutError.cs` 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.
- 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 DockerCompose (manual/docker-compose.yaml). compose up failed (exit 17 — an image could not be built) — failed to solve: failed to compute cache key: failed to calculate checksum of ref a3821073-0411-451b-9e1e-e88c2f309d12::y97ndl26mw9c8c9lciy2y84vu: "/unit": not found; runtime evidence skipped.
- ED5 Idempotency — 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 a handler's ENTRY METHODS to decide whether its mutation is safe to re-run. On these types it walked none of them, yet the same write oracle finds a persistent write in the type — so the mutation is there and the limit is in our entry-point recognition, not in the repository. Known shapes: a handler contract method implemented as an EXPLICIT INTERFACE IMPLEMENTATION, and a STATIC handler method (the Wolverine default).
- 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. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them. The .NET and Node.js version checks are a different kind and still publish.
- 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.
- PF3 Async & latency hygiene — 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. 141 further occurrence(s) are not listed individually; the score already reflects all 181.
- X2 Cancellation propagation — 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. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ErrorsToHttpStatusCodeMapper.Map at 18. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being RateLimitOptionsCreator.Create at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Configuration/Creator/RateLimitOptionsCreator.cs (RateLimitOptionsCreator.Create at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with ErrorsToHttpStatusCodeMapper.Map (cyclomatic 18). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was ClaimsAuthorizer.Authorize at 30.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with ClaimsAuthorizer.Authorize (cognitive 30), UpstreamTemplatePatternCreator.Create (cognitive 20), StreamHttpContent.CopyAsync (cognitive 19). — 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 4 together lifts Cognitive Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with AcceptanceSteps.cs, DownstreamRouteBuilder.cs, ConcurrentSteps.cs. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
2 duplicated block group(s) detected. A further 54 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 2 of the 56 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 3 Edited copy of a member (22 corresponding lines) finding(s) in Code Duplication — start with AddHeadersToRequest.cs, ClaimsToHeadersMiddleware.cs, DiskFileConfigurationRepository.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (28 corresponding lines) finding(s) in Code Duplication — start with CacheOptionsCreator.cs, LoadBalancerOptionsCreator.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with DynamicRoutesCreator.cs, OcelotLogger.cs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
66 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
2 of 73 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with AcceptanceSteps.cs, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D10 · Test Quality
3 skipped (3 with a documented reason), 11 zero-assertion, 6 synchronised by a fixed sleep, 2 depending on a live external host, 1 mock references across 1864 tests.
What to do
- Resolve the 11 No assertions finding(s) in Test Quality — start with OcelotBuilderTests.cs (2), WebSocketsFactoryTests.cs, RouteClaimsRequirementBindingTests.cs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 6 Fixed-sleep synchronisation finding(s) in Test Quality — start with FileConfigurationPollerTests.cs (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 Depends on a live external host finding(s) in Test Quality — start with MessageInvokerPoolTests.cs (2). — One of this dimension's main actionable groups (2 warning-level).
D11 · Test Reliability
Only 1 of 2 test tiers measured — the score covers those alone. 0 flaky across 1 measured tier(s). unit: measured (0 flaky); other: not included — too large to re-run within its budget.
D13 · Secret Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D14 · License Compliance
0 of 281 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 41 direct `PackageReference`(s), and 209 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 a Python pyproject.toml/requirements.txt (pip/uv/Poetry), 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.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is testing/Steps/ConcurrentSteps.cs. Counted over 92 of the 416 production source files in this repository: 323 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
D17 · Explicit Debt
159 deducted debt markers + 17 dead symbols across 18418 LoC in the .NET projects (2.6/KLoC) → score 4.9.
What to do
- Resolve the 15 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED (2), MyServiceDiscoveryProvider.cs (2), DiscoverySteps.cs (2). — One of this dimension's main actionable groups (15 issue-level).
- Resolve the 10 NoWarnInCsproj finding(s) in Explicit Debt — start with Ocelot.Acceptance.csproj (2), Ocelot.Benchmarks.csproj (2), Ocelot.ManualTest.csproj (2). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 1 FileScopedPragmaDisable finding(s) in Explicit Debt — start with RateLimiting.cs. — One of this dimension's main actionable groups (1 issue-level).
D18 · Solution Shape
66 projects, 2316 source files, 63063 hand-written lines of code (18418 production / 44645 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 93 inter-project edges (build status unknown — did not finish). Measured across 6 solutions loaded as one workspace: `Ocelot.slnx`, `Ocelot.Samples.slnx`, `samples/ServiceFabric/Ocelot.Samples.ServiceFabric.sln`, `samples/Kubernetes/OcelotKube.sln`, `samples/GraphQL/OcelotGraphQL.sln`, `samples/Eureka/OcelotEureka.sln`.
What to do
- Resolve the 2 Solution references a project that does not exist finding(s) in Solution Shape — start with Ocelot.Samples.ServiceFabric.sln, OcelotGraphQL.sln. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Solution references 2 projects that do not exist finding(s) in Solution Shape — start with OcelotKube.sln, OcelotEureka.sln. — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 39 document(s) read across 2 unit(s).
D24 · Comment Value
24 of 960 judged comments only repeat the code they sit on (2.5 %). 684 comment(s) in another language or script were not judged.
What to do
- Resolve the 20 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (9), ClientHeaderRateLimitingTests.cs (2), CircuitBreakerTests.cs (2). — One of this dimension's main actionable groups (20 recommendation-level).
D26 · Project Cohesion
1 of 22 projects flagged as possibly oversized/incoherent.
D27 · Navigability
82 % of calls cross a namespace and 2 % go through an interface, but 85 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What to do
- Resolve the 1 Pass-through layer finding(s) in Navigability — start with ClientWebSocketOptionsProxy.cs. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D29 · Static Analysis (SAST)
34 finding(s): 0 critical, 20 high, 14 medium, 0 low. 16 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 22 file(s) — `acceptance/Administration/CacheManagerTests.cs` (lines 28–32), `acceptance/Aggregation/AggregateTests.cs` (line 602), `acceptance/LoadBalancer/LoadBalancerTests.cs` (line 46), `acceptance/QualityOfService/QualityOfServiceTests.cs` (line 622), `acceptance/Request/MultipartFormDataTests.cs` (lines 10–39, line 54, line 108, …), … (+17 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 10 of those file(s) — `acceptance/Aggregation/AggregateTests.cs`, `acceptance/Request/MultipartFormDataTests.cs`, `src/Configuration/File/AggregateRouteConfig.cs`, `src/DownstreamRouteFinder/UrlMatcher/PlaceholderNameAndValue.cs`, `src/Errors/RequestTimedOutError.cs`, … (+5 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 3 of those file(s) — `acceptance/Request/MultipartFormDataTests.cs`, `testing/ServiceHandler.cs`, `unit/DownstreamRouteFinder/DownstreamRouteFinderTests.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 16 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (16 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (osv). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
D31 · IaC & Container Security
31 finding(s): 8 critical, 10 high, 12 medium, 1 low.
What to do
- Resolve the 12 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 10 High IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 8 Critical IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (8 issue-level).
D34 · Knowledge Freshness
29 of 93 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is testing/ServiceHandler.cs. Counted over 93 of the 416 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with ServiceHandler.cs, CircuitBreaker.cs, ConfigurationExtensions.cs. — One of this dimension's main actionable groups (29 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: HttpExceptionToErrorMapper.cs↔ErrorsToHttpStatusCodeMapper.cs 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with HttpExceptionToErrorMapper.cs. — One of this dimension's main actionable groups (1 issue-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 23 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
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
- `QualityOfServiceFactory` is a singleton (one shared instance) but mutates instance state outside any lock (_logger; e.g. `_logger` at line 71). — src/QualityOfService/QualityOfServiceFactory.cs:10
- `Placeholders` is a singleton (one shared instance) but mutates instance state outside any lock (_placeholders; e.g. `_placeholders` at line 65). — src/Infrastructure/Placeholders.cs:12
- `RateLimitRule` keeps one instance of itself in the static `Empty`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_periodSpan, _waitSpan; e.g. `_periodSpan` at line 30). — src/Configuration/RateLimitRule.cs:6
- `DownstreamRoute` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (defaultTimeoutSeconds; e.g. `defaultTimeoutSeconds` at line 136). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Configuration/DownstreamRoute.cs:7
- `ConfigurationBuilderExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (MergedConfigJObject, MergedConfigJson; e.g. `MergedConfigJObject` at line 166). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/DependencyInjection/ConfigurationBuilderExtensions.cs:14
- `Ocelot` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ocelotAssembly; e.g. `ocelotAssembly` at line 10). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — testing/Ocelot.cs:7
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- The namespaces Ocelot.Administration ↔ Ocelot.Cache ↔ Ocelot.Configuration ↔ Ocelot.Configuration.ChangeTracking ↔ Ocelot.Configuration.Creator ↔ Ocelot.Configuration.File ↔ Ocelot.Configuration.Parser ↔ Ocelot.Configuration.Repository ↔ Ocelot.Configuration.Validator ↔ Ocelot.DownstreamRouteFinder.UrlMatcher ↔ Ocelot.Errors ↔ Ocelot.Infrastructure ↔ Ocelot.Infrastructure.RequestData ↔ Ocelot.Logging ↔ Ocelot.Middleware ↔ Ocelot.Request.Creator ↔ Ocelot.Request.Mapper ↔ Ocelot.Request.Middleware ↔ Ocelot.Responses ↔ Ocelot.ServiceDiscovery depend on each other. The lightest dependency in the cycle is Ocelot.Administration → Ocelot.Configuration.File (Ocelot.Administration.FileConfigurationController → Ocelot.Configuration.File.FileConfiguration, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Administration/FileConfigurationController.cs:4
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX5 · Architecture & structure
AX6 · Interface segregation
- `IOcelotBuilder` declares 19 members under just 12 distinct name(s): `Services`, `Configuration`, `MvcCoreBuilder`, `AddConfigurationDelegate`, `AddConfigurationPoller`, `AddConfigurationDiscoveryPoller`, `AddConfigurationPoller`, `AddDelegatingHandler`, `AddDelegatingHandler`, `AddSingletonDefinedAggregator`, `AddTransientDefinedAggregator`, `AddCustomLoadBalancer`, `AddCustomLoadBalancer`, `AddCustomLoadBalancer`, `AddCustomLoadBalancer`, `AddCustomLoadBalancer`, `AddConfigPlaceholders`, `AddQualityOfService`, `AddQualityOfService`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 19 separate responsibilities: a caller binds to 12 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 19 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/DependencyInjection/IOcelotBuilder.cs:15
What to do
- Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
AX8 · Test isolation
- `Ocelot.Testing` ships in a production host and references `Moq`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. — testing/Ocelot.Testing.csproj:38
- `Ocelot.Testing` ships in a production host and references `Shouldly`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. — testing/Ocelot.Testing.csproj:39
What to do
- Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/Request/Mapper/StreamHttpContent.cs:32
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- A test is skipped with reason "TODO: Requires redevelopment after deprecation of Ocelot.Administration.IdentityServer4 package." — the behavior it asserts is UNVERIFIED and this skip is likely the only marker of a real bug. It ages invisibly: fix the flakiness or track the bug somewhere that can't be forgotten. — acceptance/Administration/CacheManagerTests.cs:19
- A test is skipped with reason "TODO Actually testing the Kestrel web server requires setting up a Windows user to run under using "setspn" command." — the behavior it asserts is UNVERIFIED and this skip is likely the only marker of a real bug. It ages invisibly: fix the flakiness or track the bug somewhere that can't be forgotten. — acceptance/Authentication/WindowsAuthTests.cs:72
- A test is skipped with reason "TODO: HTTP/2 (SSL) vs WebSocket is unsupported scenario by Ocelot Core currently, unfortunately..." — the behavior it asserts is UNVERIFIED and this skip is likely the only marker of a real bug. It ages invisibly: fix the flakiness or track the bug somewhere that can't be forgotten. — acceptance/WebSockets/ClientWebSocketTests.cs:115
- `Create` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/Configuration/Creator/UpstreamHeaderTemplatePatternCreator.cs:23
- `CreateContentReadStreamAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Request/Mapper/StreamHttpContent.cs:32
- `WithDefaultKestrelServerOptions` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — testing/ServiceHandler.cs:148
- `WithoutServices` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — REDACTED:29
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×14) — manual/Actions/Basic.cs:21, manual/Actions/Basic.cs:22, manual/Actions/Basic.cs:41, …
- 11 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/Configuration/File/FileRateLimitByHeaderRule.cs:49
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Describe the projects a newcomer cannot place from the root README: 9 of 18 have no README of their own, in their folder or in their family's project (`src`, `samples/Basic`, `samples/Web`, `samples/Configuration`, `samples/Kubernetes/ApiGateway` and 4 more).
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- docs/features/websockets.rst names Ocelot 24, but the manifest declares `Ocelot` 25.0.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/features/websockets.rst:24
What to do
- Reconcile the README with reality: docs/features/websockets.rst names Ocelot 24, but the manifest declares `Ocelot` 25.0.1.
P1 · CI/CD gates
P10 · Library API & versioning
- `Ocelot.Authorization.ClaimValueNotAuthorizedError` (src/Authorization/ClaimValueNotAuthorizedError.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net8.0)`, `Ocelot.Benchmarks(net8.0)`, `Ocelot.ManualTest(net8.0)`, `Ocelot.Samples.Basic(net8.0)`, `Ocelot.Samples.Configuration(net8.0)`, `Ocelot.Samples.GraphQL(net8.0)`, `Ocelot.Samples.Metadata(net8.0)`, `Ocelot.Samples.MultipartFormData(net8.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net8.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net8.0)`, `Ocelot.Samples.WebSocket(net8.0)`, `Ocelot.Testing(net8.0)`, `Ocelot.UnitTests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Authorization/ClaimValueNotAuthorizedError.cs:5
- `Ocelot.Authorization.ClaimValueNotAuthorizedError` (src/Authorization/ClaimValueNotAuthorizedError.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net9.0)`, `Ocelot.Benchmarks(net9.0)`, `Ocelot.ManualTest(net9.0)`, `Ocelot.Samples.Basic(net9.0)`, `Ocelot.Samples.Configuration(net9.0)`, `Ocelot.Samples.GraphQL(net9.0)`, `Ocelot.Samples.Metadata(net9.0)`, `Ocelot.Samples.MultipartFormData(net9.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net9.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net9.0)`, `Ocelot.Samples.WebSocket(net9.0)`, `Ocelot.Testing(net9.0)`, `Ocelot.UnitTests(net9.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Authorization/ClaimValueNotAuthorizedError.cs:5
- `Ocelot.Authorization.ClaimValueNotAuthorizedError` (src/Authorization/ClaimValueNotAuthorizedError.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net10.0)`, `Ocelot.Benchmarks(net10.0)`, `Ocelot.ManualTest(net10.0)`, `Ocelot.Samples.Basic(net10.0)`, `Ocelot.Samples.Configuration(net10.0)`, `Ocelot.Samples.GraphQL(net10.0)`, `Ocelot.Samples.Metadata(net10.0)`, `Ocelot.Samples.MultipartFormData(net10.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net10.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net10.0)`, `Ocelot.Samples.WebSocket(net10.0)`, `Ocelot.Testing(net10.0)`, `Ocelot.UnitTests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Authorization/ClaimValueNotAuthorizedError.cs:5
- `Ocelot.Infrastructure.CannotRemovePlaceholderError` (src/Infrastructure/CannotRemovePlaceholderError.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net8.0)`, `Ocelot.Benchmarks(net8.0)`, `Ocelot.ManualTest(net8.0)`, `Ocelot.Samples.Basic(net8.0)`, `Ocelot.Samples.Configuration(net8.0)`, `Ocelot.Samples.GraphQL(net8.0)`, `Ocelot.Samples.Metadata(net8.0)`, `Ocelot.Samples.MultipartFormData(net8.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net8.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net8.0)`, `Ocelot.Samples.WebSocket(net8.0)`, `Ocelot.Testing(net8.0)`, `Ocelot.UnitTests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Infrastructure/CannotRemovePlaceholderError.cs:5
- `Ocelot.Infrastructure.CannotRemovePlaceholderError` (src/Infrastructure/CannotRemovePlaceholderError.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net9.0)`, `Ocelot.Benchmarks(net9.0)`, `Ocelot.ManualTest(net9.0)`, `Ocelot.Samples.Basic(net9.0)`, `Ocelot.Samples.Configuration(net9.0)`, `Ocelot.Samples.GraphQL(net9.0)`, `Ocelot.Samples.Metadata(net9.0)`, `Ocelot.Samples.MultipartFormData(net9.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net9.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net9.0)`, `Ocelot.Samples.WebSocket(net9.0)`, `Ocelot.Testing(net9.0)`, `Ocelot.UnitTests(net9.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Infrastructure/CannotRemovePlaceholderError.cs:5
- `Ocelot.Infrastructure.CannotRemovePlaceholderError` (src/Infrastructure/CannotRemovePlaceholderError.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net10.0)`, `Ocelot.Benchmarks(net10.0)`, `Ocelot.ManualTest(net10.0)`, `Ocelot.Samples.Basic(net10.0)`, `Ocelot.Samples.Configuration(net10.0)`, `Ocelot.Samples.GraphQL(net10.0)`, `Ocelot.Samples.Metadata(net10.0)`, `Ocelot.Samples.MultipartFormData(net10.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net10.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net10.0)`, `Ocelot.Samples.WebSocket(net10.0)`, `Ocelot.Testing(net10.0)`, `Ocelot.UnitTests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Infrastructure/CannotRemovePlaceholderError.cs:5
- `Ocelot.Infrastructure.RegexGlobal` (src/Infrastructure/RegexGlobal.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net8.0)`, `Ocelot.Benchmarks(net8.0)`, `Ocelot.ManualTest(net8.0)`, `Ocelot.Samples.Basic(net8.0)`, `Ocelot.Samples.Configuration(net8.0)`, `Ocelot.Samples.GraphQL(net8.0)`, `Ocelot.Samples.Metadata(net8.0)`, `Ocelot.Samples.MultipartFormData(net8.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net8.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net8.0)`, `Ocelot.Samples.WebSocket(net8.0)`, `Ocelot.Testing(net8.0)`, `Ocelot.UnitTests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Infrastructure/RegexGlobal.cs:5
- `Ocelot.Infrastructure.RegexGlobal` (src/Infrastructure/RegexGlobal.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net9.0)`, `Ocelot.Benchmarks(net9.0)`, `Ocelot.ManualTest(net9.0)`, `Ocelot.Samples.Basic(net9.0)`, `Ocelot.Samples.Configuration(net9.0)`, `Ocelot.Samples.GraphQL(net9.0)`, `Ocelot.Samples.Metadata(net9.0)`, `Ocelot.Samples.MultipartFormData(net9.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net9.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net9.0)`, `Ocelot.Samples.WebSocket(net9.0)`, `Ocelot.Testing(net9.0)`, `Ocelot.UnitTests(net9.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Infrastructure/RegexGlobal.cs:5
- `Ocelot.Infrastructure.RegexGlobal` (src/Infrastructure/RegexGlobal.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net10.0)`, `Ocelot.Benchmarks(net10.0)`, `Ocelot.ManualTest(net10.0)`, `Ocelot.Samples.Basic(net10.0)`, `Ocelot.Samples.Configuration(net10.0)`, `Ocelot.Samples.GraphQL(net10.0)`, `Ocelot.Samples.Metadata(net10.0)`, `Ocelot.Samples.MultipartFormData(net10.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net10.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net10.0)`, `Ocelot.Samples.WebSocket(net10.0)`, `Ocelot.Testing(net10.0)`, `Ocelot.UnitTests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Infrastructure/RegexGlobal.cs:5
- `Ocelot.QualityOfService.UnableToFindQoSProviderError` (src/QualityOfService/UnableToFindQoSProviderError.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net8.0)`, `Ocelot.Benchmarks(net8.0)`, `Ocelot.ManualTest(net8.0)`, `Ocelot.Samples.Basic(net8.0)`, `Ocelot.Samples.Configuration(net8.0)`, `Ocelot.Samples.GraphQL(net8.0)`, `Ocelot.Samples.Metadata(net8.0)`, `Ocelot.Samples.MultipartFormData(net8.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net8.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net8.0)`, `Ocelot.Samples.WebSocket(net8.0)`, `Ocelot.Testing(net8.0)`, `Ocelot.UnitTests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/QualityOfService/UnableToFindQoSProviderError.cs:6
- `Ocelot.QualityOfService.UnableToFindQoSProviderError` (src/QualityOfService/UnableToFindQoSProviderError.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net9.0)`, `Ocelot.Benchmarks(net9.0)`, `Ocelot.ManualTest(net9.0)`, `Ocelot.Samples.Basic(net9.0)`, `Ocelot.Samples.Configuration(net9.0)`, `Ocelot.Samples.GraphQL(net9.0)`, `Ocelot.Samples.Metadata(net9.0)`, `Ocelot.Samples.MultipartFormData(net9.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net9.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net9.0)`, `Ocelot.Samples.WebSocket(net9.0)`, `Ocelot.Testing(net9.0)`, `Ocelot.UnitTests(net9.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/QualityOfService/UnableToFindQoSProviderError.cs:6
- `Ocelot.QualityOfService.UnableToFindQoSProviderError` (src/QualityOfService/UnableToFindQoSProviderError.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net10.0)`, `Ocelot.Benchmarks(net10.0)`, `Ocelot.ManualTest(net10.0)`, `Ocelot.Samples.Basic(net10.0)`, `Ocelot.Samples.Configuration(net10.0)`, `Ocelot.Samples.GraphQL(net10.0)`, `Ocelot.Samples.Metadata(net10.0)`, `Ocelot.Samples.MultipartFormData(net10.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net10.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net10.0)`, `Ocelot.Samples.WebSocket(net10.0)`, `Ocelot.Testing(net10.0)`, `Ocelot.UnitTests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/QualityOfService/UnableToFindQoSProviderError.cs:6
- `Ocelot.RequestId.DefaultRequestIdKey` (src/RequestId/DefaultRequestIdKey.cs:3) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net8.0)`, `Ocelot.Benchmarks(net8.0)`, `Ocelot.ManualTest(net8.0)`, `Ocelot.Samples.Basic(net8.0)`, `Ocelot.Samples.Configuration(net8.0)`, `Ocelot.Samples.GraphQL(net8.0)`, `Ocelot.Samples.Metadata(net8.0)`, `Ocelot.Samples.MultipartFormData(net8.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net8.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net8.0)`, `Ocelot.Samples.WebSocket(net8.0)`, `Ocelot.Testing(net8.0)`, `Ocelot.UnitTests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/RequestId/DefaultRequestIdKey.cs:3
- `Ocelot.RequestId.DefaultRequestIdKey` (src/RequestId/DefaultRequestIdKey.cs:3) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net9.0)`, `Ocelot.Benchmarks(net9.0)`, `Ocelot.ManualTest(net9.0)`, `Ocelot.Samples.Basic(net9.0)`, `Ocelot.Samples.Configuration(net9.0)`, `Ocelot.Samples.GraphQL(net9.0)`, `Ocelot.Samples.Metadata(net9.0)`, `Ocelot.Samples.MultipartFormData(net9.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net9.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net9.0)`, `Ocelot.Samples.WebSocket(net9.0)`, `Ocelot.Testing(net9.0)`, `Ocelot.UnitTests(net9.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/RequestId/DefaultRequestIdKey.cs:3
- `Ocelot.RequestId.DefaultRequestIdKey` (src/RequestId/DefaultRequestIdKey.cs:3) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net10.0)`, `Ocelot.Benchmarks(net10.0)`, `Ocelot.ManualTest(net10.0)`, `Ocelot.Samples.Basic(net10.0)`, `Ocelot.Samples.Configuration(net10.0)`, `Ocelot.Samples.GraphQL(net10.0)`, `Ocelot.Samples.Metadata(net10.0)`, `Ocelot.Samples.MultipartFormData(net10.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net10.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net10.0)`, `Ocelot.Samples.WebSocket(net10.0)`, `Ocelot.Testing(net10.0)`, `Ocelot.UnitTests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/RequestId/DefaultRequestIdKey.cs:3
- `Ocelot.RequestId.RequestId` (src/RequestId/RequestId.cs:3) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net8.0)`, `Ocelot.Benchmarks(net8.0)`, `Ocelot.ManualTest(net8.0)`, `Ocelot.Samples.Basic(net8.0)`, `Ocelot.Samples.Configuration(net8.0)`, `Ocelot.Samples.GraphQL(net8.0)`, `Ocelot.Samples.Metadata(net8.0)`, `Ocelot.Samples.MultipartFormData(net8.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net8.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net8.0)`, `Ocelot.Samples.WebSocket(net8.0)`, `Ocelot.Testing(net8.0)`, `Ocelot.UnitTests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/RequestId/RequestId.cs:3
- `Ocelot.RequestId.RequestId` (src/RequestId/RequestId.cs:3) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net9.0)`, `Ocelot.Benchmarks(net9.0)`, `Ocelot.ManualTest(net9.0)`, `Ocelot.Samples.Basic(net9.0)`, `Ocelot.Samples.Configuration(net9.0)`, `Ocelot.Samples.GraphQL(net9.0)`, `Ocelot.Samples.Metadata(net9.0)`, `Ocelot.Samples.MultipartFormData(net9.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net9.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net9.0)`, `Ocelot.Samples.WebSocket(net9.0)`, `Ocelot.Testing(net9.0)`, `Ocelot.UnitTests(net9.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/RequestId/RequestId.cs:3
- `Ocelot.RequestId.RequestId` (src/RequestId/RequestId.cs:3) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net10.0)`, `Ocelot.Benchmarks(net10.0)`, `Ocelot.ManualTest(net10.0)`, `Ocelot.Samples.Basic(net10.0)`, `Ocelot.Samples.Configuration(net10.0)`, `Ocelot.Samples.GraphQL(net10.0)`, `Ocelot.Samples.Metadata(net10.0)`, `Ocelot.Samples.MultipartFormData(net10.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net10.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net10.0)`, `Ocelot.Samples.WebSocket(net10.0)`, `Ocelot.Testing(net10.0)`, `Ocelot.UnitTests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/RequestId/RequestId.cs:3
- `Ocelot.ServiceDiscovery.UnableToFindServiceDiscoveryProviderError` (src/ServiceDiscovery/UnableToFindServiceDiscoveryProviderError.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net8.0)`, `Ocelot.Benchmarks(net8.0)`, `Ocelot.ManualTest(net8.0)`, `Ocelot.Samples.Basic(net8.0)`, `Ocelot.Samples.Configuration(net8.0)`, `Ocelot.Samples.GraphQL(net8.0)`, `Ocelot.Samples.Metadata(net8.0)`, `Ocelot.Samples.MultipartFormData(net8.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net8.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net8.0)`, `Ocelot.Samples.WebSocket(net8.0)`, `Ocelot.Testing(net8.0)`, `Ocelot.UnitTests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ServiceDiscovery/UnableToFindServiceDiscoveryProviderError.cs:5
- `Ocelot.ServiceDiscovery.UnableToFindServiceDiscoveryProviderError` (src/ServiceDiscovery/UnableToFindServiceDiscoveryProviderError.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net9.0)`, `Ocelot.Benchmarks(net9.0)`, `Ocelot.ManualTest(net9.0)`, `Ocelot.Samples.Basic(net9.0)`, `Ocelot.Samples.Configuration(net9.0)`, `Ocelot.Samples.GraphQL(net9.0)`, `Ocelot.Samples.Metadata(net9.0)`, `Ocelot.Samples.MultipartFormData(net9.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net9.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net9.0)`, `Ocelot.Samples.WebSocket(net9.0)`, `Ocelot.Testing(net9.0)`, `Ocelot.UnitTests(net9.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ServiceDiscovery/UnableToFindServiceDiscoveryProviderError.cs:5
- `Ocelot.ServiceDiscovery.UnableToFindServiceDiscoveryProviderError` (src/ServiceDiscovery/UnableToFindServiceDiscoveryProviderError.cs:5) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net10.0)`, `Ocelot.Benchmarks(net10.0)`, `Ocelot.ManualTest(net10.0)`, `Ocelot.Samples.Basic(net10.0)`, `Ocelot.Samples.Configuration(net10.0)`, `Ocelot.Samples.GraphQL(net10.0)`, `Ocelot.Samples.Metadata(net10.0)`, `Ocelot.Samples.MultipartFormData(net10.0)`, `Ocelot.Samples.ServiceDiscovery.ApiGateway(net10.0)`, `Ocelot.Samples.ServiceFabric.ApiGateway(net10.0)`, `Ocelot.Samples.WebSocket(net10.0)`, `Ocelot.Testing(net10.0)`, `Ocelot.UnitTests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ServiceDiscovery/UnableToFindServiceDiscoveryProviderError.cs:5
- `Ocelot.Testing.Boxing.FileRouteBox` (testing/Boxing/FileRouteBox.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net8.0)`, `Ocelot.Benchmarks(net8.0)`, `Ocelot.ManualTest(net8.0)`, `Ocelot.UnitTests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — testing/Boxing/FileRouteBox.cs:6
- `Ocelot.Testing.Boxing.FileRouteBox` (testing/Boxing/FileRouteBox.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net9.0)`, `Ocelot.Benchmarks(net9.0)`, `Ocelot.ManualTest(net9.0)`, `Ocelot.UnitTests(net9.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — testing/Boxing/FileRouteBox.cs:6
- `Ocelot.Testing.Boxing.FileRouteBox` (testing/Boxing/FileRouteBox.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net10.0)`, `Ocelot.Benchmarks(net10.0)`, `Ocelot.ManualTest(net10.0)`, `Ocelot.UnitTests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — testing/Boxing/FileRouteBox.cs:6
- `Ocelot.Testing.Steps.DynamicRoutingDiscoveryProvider` (testing/Steps/DiscoverySteps.cs:76) is public, and the library's own code uses it, but no other project in this repository uses it (read: `Ocelot.Acceptance(net8.0)`, `Ocelot.Benchmarks(net8.0)`, `Ocelot.ManualTest(net8.0)`, `Ocelot.UnitTests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — testing/Steps/DiscoverySteps.cs:76
What to do
- Make `Ocelot.Authorization.ClaimValueNotAuthorizedError` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.Authorization.ClaimValueNotAuthorizedError` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.Authorization.ClaimValueNotAuthorizedError` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.Infrastructure.CannotRemovePlaceholderError` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.Infrastructure.CannotRemovePlaceholderError` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.Infrastructure.CannotRemovePlaceholderError` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.Infrastructure.RegexGlobal` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.Infrastructure.RegexGlobal` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.Infrastructure.RegexGlobal` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.QualityOfService.UnableToFindQoSProviderError` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.QualityOfService.UnableToFindQoSProviderError` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.QualityOfService.UnableToFindQoSProviderError` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.RequestId.DefaultRequestIdKey` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.RequestId.DefaultRequestIdKey` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.RequestId.DefaultRequestIdKey` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.RequestId.RequestId` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.RequestId.RequestId` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.RequestId.RequestId` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.ServiceDiscovery.UnableToFindServiceDiscoveryProviderError` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.ServiceDiscovery.UnableToFindServiceDiscoveryProviderError` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.ServiceDiscovery.UnableToFindServiceDiscoveryProviderError` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.Testing.Boxing.FileRouteBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.Testing.Boxing.FileRouteBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.Testing.Boxing.FileRouteBox` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Ocelot.Testing.Steps.DynamicRoutingDiscoveryProvider` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
P2 · Observability
- `samples/ServiceFabric/DownstreamService/ApiGateway.cs` reports through `Console.Write…` at line 28 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — samples/ServiceFabric/DownstreamService/ApiGateway.cs:28
What to do
- Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
- `acceptance/Authentication/WindowsAuthApp/WindowsAuthWebApp.csproj` 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`. — acceptance/Authentication/WindowsAuthApp/WindowsAuthWebApp.csproj:16
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — 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
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read — confirm the gate is enforced before production promotion.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `builder.Services // Learn more about configuring Swagger/OpenAPI at https://a...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). (×2) — samples/Kubernetes/DownstreamService/Program.cs:8, samples/ServiceDiscovery/DownstreamService/Program.cs:9
- `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). (×2) — REDACTED:113, REDACTED:181
What to do
- Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
- 15 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×13) — src/Configuration/Repository/FileConfigurationPoller.cs:138, src/Infrastructure/InMemoryBus.cs:33, src/LoadBalancer/Balancers/CookieStickySessions.cs:87, …
- `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — REDACTED:218, REDACTED:224
- Only 2/166 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
- `await _repo.GetAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Administration/FileConfigurationController.cs:31
- `await _setter.SetAsync(configuration, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Administration/FileConfigurationController.cs:48
- `await _next(context)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Authentication/AuthenticationMiddleware.cs:29
- `await AuthenticateAsync(context, route)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Authentication/AuthenticationMiddleware.cs:35
- `await _next.Invoke(context)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×3) — src/Authentication/AuthenticationMiddleware.cs:46, src/Authorization/AuthorizationMiddleware.cs:69, src/Authorization/AuthorizationMiddleware.cs:85
- `await context.AuthenticateAsync(scheme)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Authentication/AuthenticationMiddleware.cs:70
- `await downstreamRequest.Request.Content.ReadAsStringAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Cache/DefaultCacheKeyGenerator.cs:31
- `await _next.Invoke(httpContext)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×3) — src/Cache/OutputCacheMiddleware.cs:30, src/Cache/OutputCacheMiddleware.cs:51, src/Claims/Middleware/ClaimsToClaimsMiddleware.cs:40
- `await _cacheGenerator.GenerateRequestCacheKey(downstreamRequest, downstreamRoute)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Cache/OutputCacheMiddleware.cs:36
- `await CreateCachedResponse(downstreamResponse)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Cache/OutputCacheMiddleware.cs:60
- `await response.Content.ReadAsByteArrayAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Cache/OutputCacheMiddleware.cs:95
- `await _configurationValidator.IsValid(fileConfiguration)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Configuration/Creator/FileInternalConfigurationCreator.cs:32
- `await _semaphore.WaitAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Configuration/Repository/DiskFileConfigurationRepository.cs:62, src/Configuration/Repository/DiskFileConfigurationRepository.cs:102
- `await FileIO.ReadAllTextAsync(_environmentFile.FullName, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Configuration/Repository/DiskFileConfigurationRepository.cs:65
- `await FileIO.WriteAllTextAsync(_environmentFile.FullName, json, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Configuration/Repository/DiskFileConfigurationRepository.cs:108
- `await FileIO.WriteAllTextAsync(_ocelotFile.FullName, json, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Configuration/Repository/DiskFileConfigurationRepository.cs:113
- `await _repo.SetAsync(configuration, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Configuration/Repository/FileAndInternalConfigurationSetter.cs:33
- `await _configCreator.Create(configuration)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Configuration/Repository/FileAndInternalConfigurationSetter.cs:35
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
- In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
S1 · Web-Security Posture
- `RemoteCertificateValidationCallback` is assigned a callback that returns `true` unconditionally, so every TLS peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Delete the override and let the platform validate. If a specific self-signed or internally-issued certificate genuinely has to be trusted, pin THAT one — compare the presented certificate's public key or thumbprint against the expected value and return `false` for everything else — and scope it to the single handler that talks to that host rather than to the whole process. If the override exists only to get past a development certificate, gate it on a build configuration or an explicit opt-in setting so it cannot ship. — src/Requester/MessageInvokerPool.cs:112
- MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — src/Cache/MD5Helper.cs:10
- The value is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — REDACTED:91
- `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path. — REDACTED:49
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×32) — manual/Actions/Basic.cs:11, samples/Basic/Program.cs:4, samples/Configuration/Program.cs:11, …
- No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.) — src/LoadBalancer/Balancers/CookieStickySessions.cs:75
What to do
- Stop accepting every TLS certificate: remove the always-true validation callback so the platform verifies the chain, hostname and expiry. If one self-signed certificate must be trusted, pin it by public key or thumbprint on the single handler that needs it and reject all others — never process-wide.
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
- Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations.
- Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
- Set secure cookie flags — CookieSecurePolicy.Always, HttpOnly, and SameSite (Strict/Lax) on auth/session cookies. Skip only if the app sets no cookies.
X1 · Async correctness
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×14) — src/Configuration/Repository/FileConfigurationPoller.cs:138, src/Infrastructure/InMemoryBus.cs:33, testing/AcceptanceSteps.cs:150, …
- This blocks on a Task **while holding a `lock`**, which is worse than an ordinary sync-over-async in two ways. `await` is illegal inside a `lock` body, so the usual fix — make the caller `async` and await it — cannot be applied where this block stands. And the thread parks while still holding the lock, so it occupies the critical section doing no work: every other caller serialises behind an operation that is only waiting, and if the awaited task itself needs a thread the pool has run out of, they wait forever. Do the async work OUTSIDE the critical section: take the lock only to read the shared state, release it, await the call, then re-take the lock to publish the result — re-checking on re-entry whether another caller won the race and, if so, discarding your result rather than overwriting theirs. Where the critical section genuinely has to span the async call, `lock` is the wrong primitive: use an async-aware one (`SemaphoreSlim` with `await WaitAsync()`) so waiters yield their thread instead of parking it. — src/LoadBalancer/Balancers/CookieStickySessions.cs:87
- `Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead. — testing/Steps/ConcurrentSteps.cs:173
- Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×2) — testing/Steps/ConcurrentSteps.cs:197, testing/Steps/ConcurrentSteps.cs:214
What to do
- Sync-over-async (deadlock risk)
X12 · Unreachable branch
X14 · Bypassable address classification
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `md5` is a `MD5`, which implements `IDisposable`, and it is created here (line 10). Every use of it in `GenerateMd5` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var md5 = …;`), which releases it at the end of the scope on every path including a throw. — src/Cache/MD5Helper.cs:10
- `_logger` (line 9) holds a `IOcelotLogger` that `ClaimsToThingCreator` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `ClaimsToThingCreator` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `_logger` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `ClaimsToThingCreator`. Implement `IDisposable` and release `_logger` there, or take the instance from the caller so its owner ends it. — src/Configuration/Creator/ClaimsToThingCreator.cs:9
- `_logger` (line 13) holds a `IOcelotLogger` that `HeaderFindAndReplaceCreator` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `HeaderFindAndReplaceCreator` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `_logger` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `HeaderFindAndReplaceCreator`. Implement `IDisposable` and release `_logger` there, or take the instance from the caller so its owner ends it. — src/Configuration/Creator/HeaderFindAndReplaceCreator.cs:13
- `FileConfigurationPoller` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_logger` itself (line 21), which makes that instance its own. But `_logger` is named in none of the methods the disposal search covered: `Dispose` (line 206) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_logger?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/Configuration/Repository/FileConfigurationPoller.cs:21
- `_logger` (line 10) holds a `IOcelotLogger` that `DownstreamRouteProviderFactory` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `DownstreamRouteProviderFactory` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `_logger` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `DownstreamRouteProviderFactory`. Implement `IDisposable` and release `_logger` there, or take the instance from the caller so its owner ends it. — src/DownstreamRouteFinder/Finder/DownstreamRouteProviderFactory.cs:10
- `_logger` (line 17) holds a `IOcelotLogger` that `AddHeadersToRequest` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `AddHeadersToRequest` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `_logger` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `AddHeadersToRequest`. Implement `IDisposable` and release `_logger` there, or take the instance from the caller so its owner ends it. — src/Headers/AddHeadersToRequest.cs:17
- `_logger` (line 11) holds a `IOcelotLogger` that `AddHeadersToResponse` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `AddHeadersToResponse` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `_logger` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `AddHeadersToResponse`. Implement `IDisposable` and release `_logger` there, or take the instance from the caller so its owner ends it. — src/Headers/AddHeadersToResponse.cs:11
- `_logger` (line 9) holds a `IOcelotLogger` that `OcelotDiagnosticListener` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `OcelotDiagnosticListener` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `_logger` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `OcelotDiagnosticListener`. Implement `IDisposable` and release `_logger` there, or take the instance from the caller so its owner ends it. — src/Logging/OcelotDiagnosticListener.cs:9
- `_logger` (line 13) holds a `IOcelotLogger` that `DelegatingHandlerFactory` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `DelegatingHandlerFactory` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `_logger` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `DelegatingHandlerFactory`. Implement `IDisposable` and release `_logger` there, or take the instance from the caller so its owner ends it. — src/Requester/DelegatingHandlerFactory.cs:13
- `_logger` (line 10) holds a `IOcelotLogger` that `MessageInvokerHttpRequester` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `MessageInvokerHttpRequester` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `_logger` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `MessageInvokerHttpRequester`. Implement `IDisposable` and release `_logger` there, or take the instance from the caller so its owner ends it. — src/Requester/MessageInvokerHttpRequester.cs:10
- `_logger` (line 12) holds a `IOcelotLogger` that `MessageInvokerPool` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `MessageInvokerPool` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `_logger` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `MessageInvokerPool`. Implement `IDisposable` and release `_logger` there, or take the instance from the caller so its owner ends it. — src/Requester/MessageInvokerPool.cs:12
- `_logger` (line 15) holds a `IOcelotLogger` that `ServiceDiscoveryProviderFactory` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `ServiceDiscoveryProviderFactory` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `_logger` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `ServiceDiscoveryProviderFactory`. Implement `IDisposable` and release `_logger` there, or take the instance from the caller so its owner ends it. — src/ServiceDiscovery/ServiceDiscoveryProviderFactory.cs:15
- `logger` is a `IOcelotLogger`, which implements `IDisposable`, and it is created here (line 18). Every use of it in `PreErrorResponderMiddleware` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var logger = …;`), which releases it at the end of the scope on every path including a throw. — samples/Metadata/MyMiddlewares.cs:18
- `logger` is a `IOcelotLogger`, which implements `IDisposable`, and it is created here (line 72). Every use of it in `ResponderMiddleware` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var logger = …;`), which releases it at the end of the scope on every path including a throw. — samples/Metadata/MyMiddlewares.cs:72
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X2 · Cancellation propagation
- Only 35/82 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×18) — manual/Actions/Basic.cs:8, src/Cache/DefaultCacheKeyGenerator.cs:10, src/Cache/OutputCacheMiddleware.cs:82, …
- No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken. — src/Multiplexer/MultiplexingMiddleware.cs:120
- No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. (×19) — src/Multiplexer/MultiplexingMiddleware.cs:203, src/Multiplexer/SimpleJsonResponseAggregator.cs:16, src/Requester/MessageInvokerHttpRequester.cs:28, …
- No CancellationToken parameter, and the token `originalContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `originalContext.RequestAborted` on, or take a CancellationToken. — src/Multiplexer/UserDefinedResponseAggregator.cs:16
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
- `LogDebug` at line 44 is called with an argument built by `string.Join(", ", response.Data.DownstreamRoute.Select(r => r.DownstreamPathTemplate.Value))` (line 44), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — src/DownstreamRouteFinder/DownstreamRouteFinderMiddleware.cs:44
What to do
- Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is C#'s evaluation order, not a guess — then put the construction behind the same level check the sink applies: `if (logger.IsEnabled(LogLevel.Trace))` for Microsoft.Extensions.Logging, the repository's own debug flag where it has one, or a message template whose ARGUMENTS the logging framework only formats when the level is on. Moving the call is not the fix: it is the join/projection in the argument that is paid, wherever the call sits.
X24 · Document value interpolated into markup unescaped
- `htmlContent` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — samples/WebSocket/Program.cs:31
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — samples/ServiceFabric/ApiGateway/WebCommunicationListener.cs:85
What to do
- Swallowed exception (empty catch)
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. — src/Logging/OcelotLogger.cs:87
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- This method contradicts itself about `services`: line 35 writes `services?.Count`, which says `services` can be null, but line 48 then dereferences it directly as `services.FindIndex` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `services` truly cannot be null here, the `?.` is misleading. Settle it one way — test `services` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/LoadBalancer/Balancers/LeastConnection.cs:48
- This method contradicts itself about `route`: line 68 writes `route?.`, which says `route` can be null, but line 71 then dereferences it directly as `route.MetadataOptions` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `route` truly cannot be null here, the `?.` is misleading. Settle it one way — test `route` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Metadata/DownstreamRouteExtensions.cs:71
- This method contradicts itself about `route`: line 23 writes `route?.`, which says `route` can be null, but line 35 then dereferences it directly as `route.GetMetadata` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `route` truly cannot be null here, the `?.` is misleading. Settle it one way — test `route` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — samples/Metadata/MetadataResponder.cs:35
- 16/19 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
- ~1.3 `!` suppressions per 1k syntax nodes — 32 suppression(s) across the 24797 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 61% | Adequate | Acceptable, with room to improve. |
| Architecture | 72% | Strong | Strongest area. |
| Maturity | 64% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 45% | Weak — gated by D13, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 36% | Weak — gated by D29, D31, C1, S1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 54% | Adequate — gated by PF3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 4 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 4 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 43 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.
- AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
- 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 — compose up failed (exit 17 — an image could not be built) — failed to solve: failed to compute cache key: failed to calculate checksum of ref a3821073-0411-451b-9e1e-e88c2f309d12::y97ndl26mw9c8c9lciy2y84vu: "/unit": not found; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; html not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (18,418 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — Not assessed, and this one is on us: 3 of the 3 handler(s) found here write to persistent state through an entry point this check does not yet recognise (an explicitly-implemented interface method, or a static handler method). Idempotency was neither confirmed nor ruled out for them — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 75 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField acceptance/Core/LoadTests.cs:15
- WriteOnlyPrivateField acceptance/QualityOfService/FakeQualityOfServiceDelegatingHandler.cs:10
- WriteOnlyPrivateField acceptance/Requester/MessageInvokerPoolTests.cs:46
- WriteOnlyPrivateField REDACTED:16
- WriteOnlyPrivateField samples/ServiceDiscovery/DownstreamService/Controllers/WeatherForecastController.cs:14
- WriteOnlyPrivateField samples/ServiceDiscovery/ApiGateway/ServiceDiscovery/MyServiceDiscoveryProvider.cs:10
- WriteOnlyPrivateField testing/Steps/DiscoverySteps.cs:78
- WriteOnlyPrivateField samples/ServiceDiscovery/ApiGateway/ServiceDiscovery/MyServiceDiscoveryProvider.cs:11
- WriteOnlyPrivateField testing/Steps/DiscoverySteps.cs:79
- WriteOnlyPrivateField samples/ServiceDiscovery/ApiGateway/ServiceDiscovery/MyServiceDiscoveryProviderFactory.cs:11
- WriteOnlyPrivateField src/Configuration/Builder/DownstreamRouteBuilder.cs:13
- WriteOnlyPrivateField src/Requester/DelegatingHandlerFactory.cs:13
- WriteOnlyPrivateField src/Requester/MessageInvokerHttpRequester.cs:10
- WriteOnlyPrivateField src/WebSockets/WebSocketsProxyMiddleware.cs:32
- WriteOnlyPrivateField unit/DependencyInjection/ConfigurationBuilderExtensionsTests.cs:14
- NoWarnInCsproj acceptance/Ocelot.Acceptance.csproj:19
- NoWarnInCsproj benchmark/Ocelot.Benchmarks.csproj:16
- NoWarnInCsproj manual/Ocelot.ManualTest.csproj:10
- NoWarnInCsproj unit/Ocelot.UnitTests.csproj:17
- NoWarnInCsproj acceptance/Ocelot.Acceptance.csproj:19
- NoWarnInCsproj benchmark/Ocelot.Benchmarks.csproj:16
- NoWarnInCsproj manual/Ocelot.ManualTest.csproj:10
- NoWarnInCsproj unit/Ocelot.UnitTests.csproj:17
- NoWarnInCsproj src/Ocelot.csproj:21
- NoWarnInCsproj src/Ocelot.csproj:47
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Production project references a test package: Ocelot.Testing → Moq testing/Ocelot.Testing.csproj:38
- Production project references a test package: Ocelot.Testing → Shouldly testing/Ocelot.Testing.csproj:39
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle src/Administration/FileConfigurationController.cs:4
- FileScopedPragmaDisable src/RateLimiting/RateLimiting.cs:13
- Boundary-crossing change coupling: HttpExceptionToErrorMapper.cs ↔ ErrorsToHttpStatusCodeMapper.cs src/Requester/HttpExceptionToErrorMapper.cs:1
- TLS certificate validation disabled src/Requester/MessageInvokerPool.cs:112
- Cryptographic key material is a compile-time constant REDACTED:91
- Blocking wait while holding a `lock` src/LoadBalancer/Balancers/CookieStickySessions.cs:87
Serious — 350 finding(s)
- TodoComment acceptance/Administration/OcelotBuilderExtensions.cs:143
- TodoComment acceptance/Administration/OcelotBuilderExtensions.cs:150
- TodoComment acceptance/Aggregation/AggregateTests.cs:138
- TodoComment acceptance/Aggregation/AggregateTests.cs:159
- TodoComment acceptance/Authentication/MultipleAuthSchemesFeatureTests.cs:40
- TodoComment acceptance/Authentication/MultipleAuthSchemesFeatureTests.cs:102
- TodoComment acceptance/Authentication/WindowsAuthTests.cs:73
- TodoComment acceptance/Authentication/WindowsAuthTests.cs:74
- TodoComment acceptance/Authentication/WindowsAuthTests.cs:134
- TodoComment acceptance/Authorization/AuthorizationTests.cs:140
- TodoComment acceptance/Configuration/DownstreamHttpVersionTests.cs:73
- TodoComment acceptance/QualityOfService/QualityOfServiceTests.cs:220
- TodoComment acceptance/Request/StreamContentTests.cs:11
- TodoComment acceptance/Request/StreamContentTests.cs:39
- TodoComment acceptance/Routing/RoutingWithQueryStringTests.cs:365
- TodoComment acceptance/ServiceDiscovery/DynamicRoutingTests.cs:618
- TodoComment acceptance/WebSockets/ClientWebSocketTests.cs:71
- TodoComment acceptance/WebSockets/ClientWebSocketTests.cs:135
- TodoComment acceptance/WebSockets/DiscoveryWebSocketTests.cs:31
- TodoComment samples/Metadata/MyMiddlewares.cs:36
- TodoComment samples/Web/DownstreamHostBuilder.cs:25
- TodoComment samples/Web/OcelotHostBuilder.cs:25
- TodoComment src/Administration/FileConfigurationController.cs:10
- TodoComment src/Administration/OutputCacheController.cs:7
- TodoComment src/Authorization/AuthorizationMiddleware.cs:42
- Awaits without ConfigureAwait(false)
- Awaits without ConfigureAwait(false) src/Administration/FileConfigurationController.cs:31
- Awaits without ConfigureAwait(false) src/Administration/FileConfigurationController.cs:48
- Awaits without ConfigureAwait(false) src/Authentication/AuthenticationMiddleware.cs:29
- Awaits without ConfigureAwait(false) src/Authentication/AuthenticationMiddleware.cs:35
- Awaits without ConfigureAwait(false) src/Authentication/AuthenticationMiddleware.cs:46
- Awaits without ConfigureAwait(false) src/Authentication/AuthenticationMiddleware.cs:70
- Awaits without ConfigureAwait(false) src/Authorization/AuthorizationMiddleware.cs:69
- Awaits without ConfigureAwait(false) src/Authorization/AuthorizationMiddleware.cs:85
- Awaits without ConfigureAwait(false) src/Cache/DefaultCacheKeyGenerator.cs:31
- Awaits without ConfigureAwait(false) src/Cache/OutputCacheMiddleware.cs:30
- Awaits without ConfigureAwait(false) src/Cache/OutputCacheMiddleware.cs:36
- Awaits without ConfigureAwait(false) src/Cache/OutputCacheMiddleware.cs:51
- Awaits without ConfigureAwait(false) src/Cache/OutputCacheMiddleware.cs:60
- Awaits without ConfigureAwait(false) src/Cache/OutputCacheMiddleware.cs:95
- Awaits without ConfigureAwait(false) src/Claims/Middleware/ClaimsToClaimsMiddleware.cs:40
- Awaits without ConfigureAwait(false) src/Configuration/Creator/FileInternalConfigurationCreator.cs:32
- Awaits without ConfigureAwait(false) src/Configuration/Repository/DiskFileConfigurationRepository.cs:62
- Awaits without ConfigureAwait(false) src/Configuration/Repository/DiskFileConfigurationRepository.cs:65
- Awaits without ConfigureAwait(false) src/Configuration/Repository/DiskFileConfigurationRepository.cs:102
- Awaits without ConfigureAwait(false) src/Configuration/Repository/DiskFileConfigurationRepository.cs:108
- Awaits without ConfigureAwait(false) src/Configuration/Repository/DiskFileConfigurationRepository.cs:113
- Awaits without ConfigureAwait(false) src/Configuration/Repository/FileAndInternalConfigurationSetter.cs:33
- Awaits without ConfigureAwait(false) src/Configuration/Repository/FileAndInternalConfigurationSetter.cs:35
- Async method without CancellationToken: RunAsync manual/Actions/Basic.cs:8
- Async method without CancellationToken: GenerateRequestCacheKey src/Cache/DefaultCacheKeyGenerator.cs:10
- Async method without CancellationToken: CreateCachedResponse src/Cache/OutputCacheMiddleware.cs:82
- Async method without CancellationToken: Create src/Configuration/Creator/FileInternalConfigurationCreator.cs:30
- Async method without CancellationToken: IsValid src/Configuration/Validator/FileConfigurationFluentValidator.cs:80
- Async method without CancellationToken: OperationAsync src/Infrastructure/DesignPatterns/Retry.cs:83
- Async method without CancellationToken: UseOcelot src/Middleware/OcelotMiddlewareExtensions.cs:19
- Async method without CancellationToken: UseOcelot src/Middleware/OcelotMiddlewareExtensions.cs:25
- Async method without CancellationToken: UseOcelot src/Middleware/OcelotMiddlewareExtensions.cs:32
- Async method without CancellationToken: UseOcelot src/Middleware/OcelotMiddlewareExtensions.cs:44
- Async method without CancellationToken: CreateConfiguration src/Middleware/OcelotMiddlewareExtensions.cs:72
- Async method without CancellationToken: ProcessRoutesWithRouteKeysAsync src/Multiplexer/MultiplexingMiddleware.cs:120
- Async method without CancellationToken: Aggregate src/Multiplexer/UserDefinedResponseAggregator.cs:16
- Async method without CancellationToken: GivenThereIsAConfigurationAsync testing/AcceptanceSteps.cs:117
- Async method without CancellationToken: GivenOcelotIsRunningAsync testing/AcceptanceSteps.cs:199
- Async method without CancellationToken: GivenOcelotHostIsRunning testing/AcceptanceSteps.cs:250
- Async method without CancellationToken: GivenIHaveAToken REDACTED:157
- Async method without CancellationToken: GivenIHaveATokenWithUrlPath REDACTED:167
- Async method without CancellationToken: GivenToken REDACTED:179
- Async method without CancellationToken: AddOrStopAsync testing/ServiceHandler.cs:34
- CommentedOutCode acceptance/Administration/OcelotBuilderExtensions.cs:95
- CommentedOutCode acceptance/Administration/OcelotBuilderExtensions.cs:106
- CommentedOutCode acceptance/Administration/OcelotBuilderExtensions.cs:126
- CommentedOutCode samples/Metadata/MetadataResponder.cs:146
- CommentedOutCode acceptance/Administration/OcelotBuilderExtensions.cs:144
- CommentedOutCode acceptance/Aggregation/AggregateTests.cs:594
- CommentedOutCode manual/Actions/Basic.cs:39
- CommentedOutCode acceptance/Authentication/WindowsAuthTests.cs:134
- CommentedOutCode acceptance/WebSockets/WebSocketsSecurityTests.cs:86
- CommentedOutCode unit/Requester/MessageInvokerPoolTests.cs:127
- CommentedOutCode unit/Requester/MessageInvokerPoolTests.cs:334
- CommentedOutCode src/Configuration/File/FileRateLimitByHeaderRule.cs:49
- CommentedOutCode REDACTED:7
- CommentedOutCode REDACTED:56
- CommentedOutCode REDACTED:100
- CommentedOutCode REDACTED:140
- CommentedOutCode REDACTED:219
- CommentedOutCode REDACTED:72
- CommentedOutCode REDACTED:73
- Dead code: GivenThereIsOcelotInternalJwtAuthServiceRunning acceptance/Administration/AdministrationSteps.cs:8
- Dead code: GetIdentityServerConfiguration acceptance/Administration/OcelotBuilderExtensions.cs:78
- Dead code: WindowsAuthMessageInvokerPool acceptance/Authentication/WindowsAuthMessageInvokerPool.cs:8
- Dead code: IISExpressAuthApp acceptance/Authentication/WindowsAuthTests.cs:344
- Dead code: ConfigureIISExpress acceptance/Authentication/WindowsAuthTests.cs:348
- Dead code: Usings acceptance/Usings.cs:23
- Dead code: Bug930_StepsToReproduce acceptance/WebSockets/ClientWebSocketTests.cs:192
- Dead code: GetMetadataNode src/Metadata/DownstreamRouteExtensions.cs:75
- Dead code: SetBaseUrl testing/AcceptanceSteps.cs:245
- Dead code: HttpContentStub unit/Cache/DefaultCacheKeyGeneratorTests.cs:117
- Dead code: UpstreamPathTemplate unit/DependencyInjection/ConfigurationBuilderExtensionsTests.cs:1318
- Dead code: TestRetry unit/TestRetry.cs:6
- Dead code: Usings unit/Usings.cs:23
- Dead code: MockWebSocket unit/WebSockets/MockWebSocket.cs:11
- Dead code: MockMiddleware unit/WebSockets/WebSocketsProxyMiddlewareTests.cs:426
- Dead code: CompressBrotliAsync samples/Metadata/MetadataResponder.cs:167
- Dead code: DecompressDeflateAsync samples/Metadata/MetadataResponder.cs:195
- Sync-over-async blocking
- Sync-over-async blocking src/Configuration/Repository/FileConfigurationPoller.cs:138
- Sync-over-async blocking src/Infrastructure/InMemoryBus.cs:33
- Sync-over-async blocking src/LoadBalancer/Balancers/CookieStickySessions.cs:87
- Sync-over-async blocking testing/AcceptanceSteps.cs:150
- Sync-over-async blocking testing/AcceptanceSteps.cs:484
- Sync-over-async blocking testing/AcceptanceSteps.cs:492
- Sync-over-async blocking testing/ServiceHandler.cs:104
- Sync-over-async blocking testing/ServiceHandler.cs:117
- Sync-over-async blocking testing/ServiceHandler.cs:130
- Sync-over-async blocking testing/ServiceHandler.cs:144
- Sync-over-async blocking testing/ServiceHandler.cs:161
- Sync-over-async blocking testing/ServiceHandler.cs:225
- Sync-over-async blocking REDACTED:218
- Sync-over-async blocking REDACTED:224
- Sync-over-async blocking samples/ServiceFabric/ApiGateway/WebCommunicationListener.cs:72
- Sync-over-async (deadlock risk) src/Configuration/Repository/FileConfigurationPoller.cs:138
- Sync-over-async (deadlock risk) src/Infrastructure/InMemoryBus.cs:33
- Sync-over-async (deadlock risk) testing/AcceptanceSteps.cs:150
- Sync-over-async (deadlock risk) testing/AcceptanceSteps.cs:483
- Sync-over-async (deadlock risk) testing/AcceptanceSteps.cs:491
- Sync-over-async (deadlock risk) testing/ServiceHandler.cs:104
- Sync-over-async (deadlock risk) testing/ServiceHandler.cs:117
- Sync-over-async (deadlock risk) testing/ServiceHandler.cs:130
- Sync-over-async (deadlock risk) testing/ServiceHandler.cs:144
- Sync-over-async (deadlock risk) testing/ServiceHandler.cs:161
- Sync-over-async (deadlock risk) testing/ServiceHandler.cs:224
- Sync-over-async (deadlock risk) REDACTED:218
- Sync-over-async (deadlock risk) REDACTED:224
- Sync-over-async (deadlock risk) samples/ServiceFabric/ApiGateway/WebCommunicationListener.cs:72
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions: ShouldProxyWebsocketInputToDownstreamServiceAndUseLoadBalancer acceptance/WebSockets/WebSocketsFactoryTests.cs:32
- No assertions: PostConfigure_NullOptions_DoesNothing unit/Authorization/RouteClaimsRequirementBindingTests.cs:22
- No assertions: Should_dispose_cleanly_without_starting unit/Configuration/Repository/FileConfigurationPollerTests.cs:217
- No assertions: Should_set_up_services unit/DependencyInjection/OcelotBuilderTests.cs:150
- No assertions: Should_set_up_without_passing_in_config unit/DependencyInjection/OcelotBuilderTests.cs:181
- No assertions: Should_release unit/LoadBalancer/CookieStickySessionsTests.cs:136
- No assertions: Should_be_able_to_lease_and_release_concurrently unit/LoadBalancer/LeastConnectionTests.cs:22
- No assertions: Release unit/LoadBalancer/NoLoadBalancerTests.cs:82
- No assertions: Release unit/LoadBalancer/RoundRobinTests.cs:150
- No assertions: Middleware_Multi_Parameters_Invoke unit/Middleware/OcelotPiplineBuilderTests.cs:79
- No assertions: Should_call_without_exception unit/Responder/HttpContextResponderTests.cs:110
- ObsoleteWithCallers src/Configuration/File/FileAuthenticationOptions.cs:29
- ObsoleteWithCallers src/Configuration/File/FileDynamicRoute.cs:8
- ObsoleteWithCallers src/Configuration/File/FileQoSOptions.cs:36
- ObsoleteWithCallers src/Configuration/File/FileQoSOptions.cs:40
- ObsoleteWithCallers src/Configuration/File/FileQoSOptions.cs:56
- ObsoleteWithCallers src/Configuration/File/FileRateLimitByHeaderRule.cs:77
- ObsoleteWithCallers src/Configuration/File/FileRateLimitByHeaderRule.cs:83
- ObsoleteWithCallers src/Configuration/File/FileRateLimitByHeaderRule.cs:91
- ObsoleteWithCallers src/Configuration/File/FileRateLimitByHeaderRule.cs:103
- ObsoleteWithCallers src/Configuration/File/FileRateLimitRule.cs:46
- ObsoleteWithCallers src/Configuration/File/FileRoute.cs:40
- Disposable acquired into a field and never released src/Configuration/Creator/ClaimsToThingCreator.cs:9
- Disposable acquired into a field and never released src/Configuration/Creator/HeaderFindAndReplaceCreator.cs:13
- Disposable acquired into a field and never released src/DownstreamRouteFinder/Finder/DownstreamRouteProviderFactory.cs:10
- Disposable acquired into a field and never released src/Headers/AddHeadersToRequest.cs:17
- Disposable acquired into a field and never released src/Headers/AddHeadersToResponse.cs:11
- Disposable acquired into a field and never released src/Logging/OcelotDiagnosticListener.cs:9
- Disposable acquired into a field and never released src/Requester/DelegatingHandlerFactory.cs:13
- Disposable acquired into a field and never released src/Requester/MessageInvokerHttpRequester.cs:10
- Disposable acquired into a field and never released src/Requester/MessageInvokerPool.cs:12
- Disposable acquired into a field and never released src/ServiceDiscovery/ServiceDiscoveryProviderFactory.cs:15
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Fixed-sleep synchronisation: StopAsync_Should_wait_for_running_timer_callback_to_complete unit/Configuration/Repository/FileConfigurationPollerTests.cs:182
- Fixed-sleep synchronisation: StopAsync_Should_prevent_new_timer_callbacks_after_change unit/Configuration/Repository/FileConfigurationPollerTests.cs:450
- Fixed-sleep synchronisation: StopAsync_Should_prevent_new_callbacks_and_complete unit/Configuration/Repository/FileConfigurationPollerTests.cs:478
- Fixed-sleep synchronisation: StopAsync_Should_prevent_use_of_disposed_timer_from_callbacks unit/Configuration/Repository/FileConfigurationPollerTests.cs:535
- Fixed-sleep synchronisation: Multiple_Start_Stop_Cycles_Should_work_correctly unit/Configuration/Repository/FileConfigurationPollerTests.cs:596
- Fixed-sleep synchronisation: StopAsync_Should_log_warning_when_timer_disposal_exceeds_timeout unit/Configuration/Repository/FileConfigurationPollerTests.cs:644
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- BareSuppressMessage acceptance/Caching/CachingTests.cs:248
- BareSuppressMessage acceptance/Caching/CachingTests.cs:249
- BareSuppressMessage acceptance/Usings.cs:21
- BareSuppressMessage unit/Usings.cs:21
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Outbound HTTP without resilience samples/Kubernetes/DownstreamService/Program.cs:8
- Outbound HTTP without resilience samples/ServiceDiscovery/DownstreamService/Program.cs:9
- Outbound HTTP without resilience REDACTED:113
- Outbound HTTP without resilience REDACTED:181
- Process-global static state: DownstreamRoute src/Configuration/DownstreamRoute.cs:7
- Process-global static state: ConfigurationBuilderExtensions src/DependencyInjection/ConfigurationBuilderExtensions.cs:14
- Process-global static state: Ocelot testing/Ocelot.cs:7
- TooManyMethods: AcceptanceSteps testing/AcceptanceSteps.cs
- TooManyMethods: DownstreamRouteBuilder src/Configuration/Builder/DownstreamRouteBuilder.cs
- TooManyMethods: ConcurrentSteps testing/Steps/ConcurrentSteps.cs
- Edited copy of a member (22 corresponding lines) src/Headers/AddHeadersToRequest.cs:27
- Edited copy of a member (22 corresponding lines) src/Headers/Middleware/ClaimsToHeadersMiddleware.cs:21
- Edited copy of a member (22 corresponding lines) src/Configuration/Repository/DiskFileConfigurationRepository.cs:76
- Skipped test marks a known-real bug acceptance/Administration/CacheManagerTests.cs:19
- Skipped test marks a known-real bug acceptance/Authentication/WindowsAuthTests.cs:72
- Skipped test marks a known-real bug acceptance/WebSockets/ClientWebSocketTests.cs:115
- Disposable created and abandoned in the method that made it src/Cache/MD5Helper.cs:10
- Disposable created and abandoned in the method that made it samples/Metadata/MyMiddlewares.cs:18
- Disposable created and abandoned in the method that made it samples/Metadata/MyMiddlewares.cs:72
- Symbol treated as nullable, then dereferenced unguarded src/LoadBalancer/Balancers/LeastConnection.cs:48
- Symbol treated as nullable, then dereferenced unguarded src/Metadata/DownstreamRouteExtensions.cs:71
- Symbol treated as nullable, then dereferenced unguarded samples/Metadata/MetadataResponder.cs:35
- Stateful singleton: QualityOfServiceFactory src/QualityOfService/QualityOfServiceFactory.cs:10
- Stateful singleton: Placeholders src/Infrastructure/Placeholders.cs:12
- Depends on a live external host: If_two_delegating_handlers_are_defined_then_these_should_be_call_in_order unit/Requester/MessageInvokerPoolTests.cs:57
- Depends on a live external host: Should_log_if_ignoring_ssl_errors unit/Requester/MessageInvokerPoolTests.cs:79
- Solution references a project that does not exist samples/ServiceFabric/Ocelot.Samples.ServiceFabric.sln
- Solution references a project that does not exist samples/GraphQL/OcelotGraphQL.sln
- Solution references 2 projects that do not exist samples/Kubernetes/OcelotKube.sln
- Solution references 2 projects that do not exist samples/Eureka/OcelotEureka.sln
- Edited copy of a member (28 corresponding lines) src/Configuration/Creator/CacheOptionsCreator.cs:26
- Edited copy of a member (28 corresponding lines) src/Configuration/Creator/LoadBalancerOptionsCreator.cs:26
- Edited copy of a member (4 corresponding lines) src/Configuration/Creator/DynamicRoutesCreator.cs:54
- Edited copy of a member (4 corresponding lines) src/Logging/OcelotLogger.cs:28
- Low cohesion: AcceptanceSteps (LCOM4 4) testing/AcceptanceSteps.cs:31
- Low cohesion: WebSocketsSteps (LCOM4 4) REDACTED:18
- Empty method body — does nothing with its inputs testing/ServiceHandler.cs:148
- Empty method body — does nothing with its inputs REDACTED:29
- Sync-over-async (deadlock risk) through `.Result` testing/Steps/ConcurrentSteps.cs:197
- Sync-over-async (deadlock risk) through `.Result` testing/Steps/ConcurrentSteps.cs:214
- Stateful shared instance: RateLimitRule src/Configuration/RateLimitRule.cs:6
- No data-protection/encryption
- ErrorsToHttpStatusCodeMapper.Map (cyclomatic 18) src/Responder/ErrorsToHttpStatusCodeMapper.cs:8
- BarePragmaDisable acceptance/Authentication/WindowsAuthTests.cs:25
- HackComment src/Configuration/Creator/UpstreamTemplatePatternCreator.cs:37
- ClaimsAuthorizer.Authorize (cognitive 30) src/Authorization/ClaimsAuthorizer.cs:24
- UpstreamTemplatePatternCreator.Create (cognitive 20) src/Configuration/Creator/UpstreamTemplatePatternCreator.cs:23
- StreamHttpContent.CopyAsync (cognitive 19) src/Request/Mapper/StreamHttpContent.cs:38
- SimpleJsonResponseAggregator.MapAggregateContent (cognitive 18) src/Multiplexer/SimpleJsonResponseAggregator.cs:16
- Edited copy of a member (41 corresponding lines) src/Configuration/Repository/FileConfigurationPoller.cs:111
- Edited copy of a member (35 corresponding lines) src/Infrastructure/DesignPatterns/Retry.cs:37
- Edited copy of a member (10 corresponding lines) src/DependencyInjection/ConfigurationBuilderExtensions.cs:441
- Edited copy of a member (24 corresponding lines) src/Configuration/Creator/AuthenticationOptionsCreator.cs:26
- Edited copy of a member (21 corresponding lines) src/Headers/AddHeadersToRequest.cs:51
- Edited copy of a member (9 corresponding lines) testing/Ocelot.cs:31
- Edited copy of a member (13 corresponding lines) REDACTED:50
- Edited copy of a member (17 corresponding lines) testing/AcceptanceSteps.cs:574
- Edited copy of a member (11 corresponding lines) src/Configuration/File/FileSecurityOptions.cs:21
- Edited copy of a member (6 corresponding lines) src/LoadBalancer/Balancers/LeastConnection.cs:68
- Edited copy of a member (7 corresponding lines) src/Configuration/File/FileMetadataOptions.cs:17
- Duplicated block (20 lines × 2) samples/Web/DownstreamHostBuilder.cs:7
- Duplicated block (7 lines × 2) samples/Kubernetes/DownstreamService/Program.cs:16
- Unfinished stub — throws NotImplementedException src/Request/Mapper/StreamHttpContent.cs:32
- Hollow method — returns a constant without doing the work src/Configuration/Creator/UpstreamHeaderTemplatePatternCreator.cs:23
- Unfinished stub — throws NotImplementedException src/Request/Mapper/StreamHttpContent.cs:32
- Coverage collected but not gated
- Weak hash algorithm src/Cache/MD5Helper.cs:10
- Sync-over-async (deadlock risk) through `Task.WaitAll` testing/Steps/ConcurrentSteps.cs:173
- Owned disposable field is never released src/Configuration/Repository/FileConfigurationPoller.cs:21
- Untrusted text written into markup unescaped samples/WebSocket/Program.cs:31
- Swallowed exception (empty catch) samples/ServiceFabric/ApiGateway/WebCommunicationListener.cs:85
Minor — 156 finding(s)
- No security response headers detected
- No security response headers detected manual/Actions/Basic.cs:11
- No security response headers detected samples/Basic/Program.cs:4
- No security response headers detected samples/Configuration/Program.cs:11
- No security response headers detected samples/Eureka/ApiGateway/Program.cs:8
- No security response headers detected samples/Eureka/DownstreamService/Program.cs:1
- No security response headers detected samples/GraphQL/Program.cs:23
- No security response headers detected samples/Kubernetes/ApiGateway/Program.cs:8
- No security response headers detected samples/Kubernetes/DownstreamService/Program.cs:6
- No security response headers detected samples/Metadata/Program.cs:7
- No security response headers detected samples/MultipartFormData/ApiGateway.cs:10
- No security response headers detected REDACTED:9
- No security response headers detected samples/OpenTracing/Program.cs:10
- No security response headers detected samples/ServiceDiscovery/ApiGateway/Program.cs:10
- No security response headers detected samples/ServiceDiscovery/DownstreamService/Program.cs:7
- No security response headers detected samples/ServiceFabric/ApiGateway/WebCommunicationListener.cs:48
- No security response headers detected samples/ServiceFabric/DownstreamService/ApiGateway.cs:32
- No security response headers detected samples/Web/DownstreamHostBuilder.cs:7
- No security response headers detected samples/Web/DownstreamHostBuilder.cs:10
- No security response headers detected samples/Web/DownstreamHostBuilder.cs:14
- No security response headers detected samples/Web/DownstreamHostBuilder.cs:18
- No security response headers detected samples/Web/OcelotHostBuilder.cs:7
- No security response headers detected samples/Web/OcelotHostBuilder.cs:10
- No security response headers detected samples/Web/OcelotHostBuilder.cs:14
- No security response headers detected samples/Web/OcelotHostBuilder.cs:18
- Orphaned file testing/ServiceHandler.cs:1
- Orphaned file src/Infrastructure/DesignPatterns/CircuitBreaker.cs:1
- Orphaned file src/DependencyInjection/ConfigurationExtensions.cs:1
- Orphaned file src/QualityOfService/CircuitBreakerDelegatingHandler.cs:1
- Orphaned file src/RateLimiting/RateLimiting.cs:1
- Orphaned file src/DownstreamRouteFinder/UrlMatcher/UrlPathPlaceholderNameAndValueFinder.cs:1
- Orphaned file src/RateLimiting/RateLimitingMiddleware.cs:1
- Orphaned file src/Metadata/DownstreamRouteExtensions.cs:1
- Orphaned file src/Configuration/File/FileRateLimitByHeaderRule.cs:1
- Orphaned file src/Infrastructure/DesignPatterns/Retry.cs:1
- Orphaned file src/Middleware/OcelotMiddlewareExtensions.cs:1
- Orphaned file src/Request/Mapper/StreamHttpContent.cs:1
- Orphaned file src/LoadBalancer/Balancers/RoundRobin.cs:1
- Orphaned file src/DependencyInjection/ServiceCollectionExtensions.cs:1
- Orphaned file testing/Boxing/FileRouteBox.cs:1
- Orphaned file src/LoadBalancer/Balancers/CookieStickySessions.cs:1
- Orphaned file src/Authorization/ClaimsAuthorizer.cs:1
- Orphaned file src/Request/Mapper/RequestMapper.cs:1
- Orphaned file src/Configuration/Creator/RateLimitOptionsCreator.cs:1
- Orphaned file src/Responder/HttpContextResponder.cs:1
- Orphaned file src/RateLimiting/IRateLimiting.cs:1
- Orphaned file src/Errors/ExceptionHandlerMiddleware.cs:1
- Orphaned file src/RequestId/Middleware/RequestIdMiddleware.cs:1
- Orphaned file src/LoadBalancer/Balancers/LeastConnection.cs:1
- Orphaned file src/QualityOfService/QualityOfServiceFactory.cs:1
- Public type used only inside its own library src/Authorization/ClaimValueNotAuthorizedError.cs:5
- Public type used only inside its own library src/Authorization/ClaimValueNotAuthorizedError.cs:5
- Public type used only inside its own library src/Authorization/ClaimValueNotAuthorizedError.cs:5
- Public type used only inside its own library src/Infrastructure/CannotRemovePlaceholderError.cs:5
- Public type used only inside its own library src/Infrastructure/CannotRemovePlaceholderError.cs:5
- Public type used only inside its own library src/Infrastructure/CannotRemovePlaceholderError.cs:5
- Public type used only inside its own library src/Infrastructure/RegexGlobal.cs:5
- Public type used only inside its own library src/Infrastructure/RegexGlobal.cs:5
- Public type used only inside its own library src/Infrastructure/RegexGlobal.cs:5
- Public type used only inside its own library src/QualityOfService/UnableToFindQoSProviderError.cs:6
- Public type used only inside its own library src/QualityOfService/UnableToFindQoSProviderError.cs:6
- Public type used only inside its own library src/QualityOfService/UnableToFindQoSProviderError.cs:6
- Public type used only inside its own library src/RequestId/DefaultRequestIdKey.cs:3
- Public type used only inside its own library src/RequestId/DefaultRequestIdKey.cs:3
- Public type used only inside its own library src/RequestId/DefaultRequestIdKey.cs:3
- Public type used only inside its own library src/RequestId/RequestId.cs:3
- Public type used only inside its own library src/RequestId/RequestId.cs:3
- Public type used only inside its own library src/RequestId/RequestId.cs:3
- Public type used only inside its own library src/ServiceDiscovery/UnableToFindServiceDiscoveryProviderError.cs:5
- Public type used only inside its own library src/ServiceDiscovery/UnableToFindServiceDiscoveryProviderError.cs:5
- Public type used only inside its own library src/ServiceDiscovery/UnableToFindServiceDiscoveryProviderError.cs:5
- Public type used only inside its own library testing/Boxing/FileRouteBox.cs:6
- Public type used only inside its own library testing/Boxing/FileRouteBox.cs:6
- Public type used only inside its own library testing/Boxing/FileRouteBox.cs:6
- Public type used only inside its own library testing/Steps/DiscoverySteps.cs:76
- redundant comment acceptance/Properties/AssemblyInfo.cs:4
- redundant comment acceptance/Properties/AssemblyInfo.cs:11
- redundant comment acceptance/Properties/AssemblyInfo.cs:15
- redundant comment acceptance/RateLimiting/ClientHeaderRateLimitingTests.cs:363
- redundant comment acceptance/RateLimiting/ClientHeaderRateLimitingTests.cs:389
- redundant comment benchmark/Properties/AssemblyInfo.cs:4
- redundant comment benchmark/Properties/AssemblyInfo.cs:11
- redundant comment benchmark/Properties/AssemblyInfo.cs:15
- redundant comment src/DownstreamRouteFinder/UrlMatcher/UrlPathPlaceholderNameAndValueFinder.cs:36
- redundant comment unit/Configuration/Repository/FileConfigurationPollerTests.cs:727
- redundant comment unit/Infrastructure/DesignPatterns/CircuitBreakerTests.cs:225
- redundant comment unit/Infrastructure/DesignPatterns/CircuitBreakerTests.cs:472
- redundant comment unit/Multiplexer/MultiplexingMiddlewareTests.cs:613
- redundant comment unit/Properties/AssemblyInfo.cs:4
- redundant comment unit/Properties/AssemblyInfo.cs:11
- redundant comment unit/Properties/AssemblyInfo.cs:15
- redundant comment unit/QualityOfService/CircuitBreakerDelegatingHandlerTests.cs:73
- redundant comment unit/Request/Mapper/RequestMapperTests.cs:197
- redundant comment unit/Request/Mapper/RequestMapperTests.cs:233
- redundant comment unit/Requester/MessageInvokerHttpRequesterTests.cs:120
- Commented-out code manual/Actions/Basic.cs:21
- Commented-out code manual/Actions/Basic.cs:22
- Commented-out code manual/Actions/Basic.cs:41
- Commented-out code src/Configuration/File/FileRateLimitByHeaderRule.cs:49
- Commented-out code src/LoadBalancer/Balancers/RoundRobin.cs:121
- Commented-out code src/RateLimiting/RateLimiting.cs:138
- Commented-out code testing/AcceptanceSteps.cs:280
- Commented-out code testing/Boxing/FileRouteBox.cs:22
- Commented-out code testing/Boxing/FileRouteBox.cs:38
- Commented-out code testing/Boxing/FileRouteBox.cs:55
- Commented-out code testing/Boxing/FileRouteBox.cs:69
- Commented-out code testing/Boxing/FileRouteBox.cs:79
- Commented-out code testing/Boxing/FileRouteBox.cs:99
- Commented-out code testing/Boxing/FileRouteBox.cs:107
- Commented-out code testing/PortFinder.cs:48
- Duplicated predicate testing/AcceptanceSteps.cs:580
- Duplicated predicate src/Configuration/Creator/AuthenticationOptionsCreator.cs:29
- Duplicated predicate src/Configuration/Creator/CacheOptionsCreator.cs:29
- Duplicated predicate src/Configuration/Creator/AuthenticationOptionsCreator.cs:43
- Duplicated predicate src/Configuration/Creator/CacheOptionsCreator.cs:42
- Duplicated predicate src/Configuration/Creator/CacheOptionsCreator.cs:47
- Duplicated predicate src/Configuration/Creator/AuthenticationOptionsCreator.cs:38
- Duplicated predicate src/Configuration/Creator/AuthenticationOptionsCreator.cs:33
- Silent fallback default in catch testing/PortFinder.cs:58
- Silent fallback default in catch samples/Metadata/MetadataResponder.cs:86
- Fat interface: IOcelotBuilder (19 members) src/DependencyInjection/IOcelotBuilder.cs:15
- Partial data-retention evidence
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion src/Ocelot.csproj:1
- Pass-through layer src/WebSockets/ClientWebSocketOptionsProxy.cs:7
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- README/code drift docs/features/websockets.rst:24
- Sleep-based test synchronization
- Console output used as the logging channel samples/ServiceFabric/DownstreamService/ApiGateway.cs:28
- No SAST REDACTED:3
- No dependency-update automation acceptance/Authentication/WindowsAuthApp/WindowsAuthWebApp.csproj:16
- No rollback/health safety
- OIDC metadata fetched over HTTP REDACTED:49
- Secure cookie flags not detected src/LoadBalancer/Balancers/CookieStickySessions.cs:75
- Not all async methods take a CancellationToken
- Diagnostic log message is built whether or not it is wanted src/DownstreamRouteFinder/DownstreamRouteFinderMiddleware.cs:44
- Interpolated log message defeats structured logging src/Logging/OcelotLogger.cs:87
- Nullable reference types not enabled everywhere
- Null-forgiving operator (`!`) suppressions override nullable warnings
- Silent fallback default on parse failure src/DownstreamRouteFinder/UrlMatcher/UrlPathPlaceholderNameAndValueFinder.cs:116
- Silent fallback default on configuration miss src/Middleware/BaseUrlFinder.cs:19
Minor — 7 finding(s)
- Skipped (documented): ShouldClearCacheRegionViaAdministrationAPI acceptance/Administration/CacheManagerTests.cs:19
- Skipped (documented): ShouldUseDefaultCredentialsForKestrelServer acceptance/Authentication/WindowsAuthTests.cs:72
- Skipped (documented): Http20ClientWhenOcelotInTheMiddleThenShouldConnect acceptance/WebSockets/ClientWebSocketTests.cs:115
- doc comments repeat the names src/Authorization/ClaimsAuthorizer.cs:9
- doc comments repeat the names acceptance/Metadata/DownstreamMetadataTests.cs:390
- doc comments repeat the names REDACTED:105
- Mock framework: Moq
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-ee8b62288bc744f799832a0cf4b5bea6/history.json --exit-code 0 --source . | 13 | 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-ee8b62288bc744f799832a0cf4b5bea6/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 . | 34 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-724f9a0600ab40508d1b0a574ff09e3e | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 31 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 3 file(s) — `src/Configuration/File/AggregateRouteConfig.cs`, `src/DownstreamRouteFinder/UrlMatcher/PlaceholderNameAndValue.cs`, `src/Errors/RequestTimedOutError.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-724f9a0600ab40508d1b0a574ff09e3e | 0 | artifacts/raw/osv-scanner.json |