Public report of reactiveui/refit, published 12 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 12 November 2026, 01:05 UTC · Survey ID cd_cdc1836f5e4e42f290edb2f067062992

reactiveui/refit

Measured 12 November 2026, 01:03 UTC, at code version 89779cd

Code coverage is not measured: No coverage collector is wired up.

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

CAI score 58out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey

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

A medium codebase: 57,160 lines of product code in 157 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Security and Compliance, 48

Findings by how serious they are

35 critical 230 serious 54 minor

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

This survey was produced by

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

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

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

65of 65 dimensions measured by tools.
303of 319 findings point to an exact file and line, so you can open each one in the code. The other 16 concern the repository as a whole, such as missing documentation.
65dimensions across 6 lenses, read from 57,160 lines of product code in 157 projects.
Chapters

Executive summary

reactiveui/refit falls short of our standard for production, in part because we found no encryption of stored data, no key vault and no enforced HTTPS. It scores 58 out of 100 and is rated Adequate, and 11 of its 35 critical findings are security problems.

Security and Compliance, at 48, is the weakest lens and counts most in the score. The best first step is encrypting the sensitive stored data and keeping its keys in a vault, worth about 9 points. Recording design decisions comes next, worth about 3 points. Raising Security and Compliance to 70 would lift the score to about 67.

Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one password or key is open to anyone who can read the repository. Pinning each tool to an exact version, setting a waiting period for automatic updates and replacing the exposed password or key would close these risks. The 19 analysis rules switched off in the settings need switching back on in the settings file.

The product code is 57,160 lines, about €150,000 to rebuild.

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

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

If Security and Compliance rose from 48 to 70, the lowest score rated Strong, the score would rise from 58 to about 67.

Code composition: what the lines of code are
Business logic 8%Supporting code 18%Tests 62%Code analyzers 12%
New since the last survey: 79 findings

These 79 critical or serious findings weren't in the previous survey, on 23 October 2026.

  • Cyclomatic Complexity · top-level statements (cyclomatic 36) src/Refit.NativeAotSmoke/Program.cs
  • Cognitive Complexity · top-level statements (cognitive 37) src/Refit.NativeAotSmoke/Program.cs
  • Code Duplication · Edited copy of a member (36 corresponding lines) src/InterfaceStubGenerator.Shared/InlineRequestEmission.cs
  • Code Duplication · Edited copy of a member (47 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs
  • Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs
  • Code Duplication · Edited copy of a member (32 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs
  • Code Duplication · Edited copy of a member (13 corresponding lines) src/InterfaceStubGenerator.Shared/Models/RequestModel.cs
  • Code Duplication · Edited copy of a member (34 corresponding lines) src/Refit/GeneratedRequestRunner.cs
  • Code Duplication · Edited copy of a member (19 corresponding lines) src/Refit/GeneratedRequestRunner.cs
  • Code Duplication · Edited copies of one member (3 members, 27+ corresponding lines) src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs
  • Code Duplication · Edited copy of a member (25 corresponding lines) src/InterfaceStubGenerator.Shared/InterfaceMemberParsing.cs
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/InterfaceStubGenerator.Shared/Models/InlineValueFormatModel.cs
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/InterfaceStubGenerator.Shared/Models/InterfaceModel.cs
  • Code Duplication · Edited copy of a member (21 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs
  • Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) src/Refit.Reflection/ReflectionPropertyHelpers.cs
  • Code Duplication · Edited copy of a member (24 corresponding lines) src/Refit.Reflection/RequestBuilderImplementation.Payload.cs
  • Code Duplication · Edited copy of a member (9 corresponding lines) src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs
  • Code Duplication · Edited copy of a member (9 corresponding lines) src/InterfaceStubGenerator.Shared/RequestParameterParsing.cs
  • Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) src/InterfaceStubGenerator.Shared/MultipartParameterParsing.cs
  • Code Duplication · Edited copy of a member (17 corresponding lines) src/InterfaceStubGenerator.Shared/QueryValueEmission.cs
  • Code Duplication · Edited copy of a member (9 corresponding lines) src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs
  • Code Duplication · Edited copy of a member (18 corresponding lines) src/Refit.Xml/XmlContentSerializer.cs
  • Code Duplication · Edited copy of a member (14 corresponding lines) src/Refit.Reflection/FormObjectFlattener.cs
  • Code Duplication · Edited copy of a member (23 corresponding lines) src/InterfaceStubGenerator.Shared/RequestParsing.cs
  • Code Duplication · Edited copy of a member (16 corresponding lines) src/Refit/SystemTextJsonContentSerializer.cs
  • Code Duplication · Edited copy of a member (18 corresponding lines) src/Refit.Reflection/RestMethodInfoInternal.AttributeReading.cs
  • Code Duplication · Edited copy of a member (13 corresponding lines) src/Refit/GeneratedRequestRunner.cs
  • Code Duplication · Edited copy of a member (21 corresponding lines) src/Refit.Reflection/RequestBuilderImplementation.Execution.cs
  • Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) src/InterfaceStubGenerator.Shared/MultipartParameterParsing.cs
  • Code Duplication · Edited copy of a member (12 corresponding lines) src/InterfaceStubGenerator.Shared/QueryFormatterEmission.cs
  • Code Duplication · Edited copy of a member (22 corresponding lines) src/Refit.Reflection/RestMethodInfoInternal.AttributeReading.cs
  • Code Duplication · Edited copy of a member (14 corresponding lines) src/InterfaceStubGenerator.Shared/MethodSignatureParsing.cs
  • Code Duplication · Edited copy of a member (27 corresponding lines) src/Refit.Reflection/RestMethodInfoInternal.AttributeReading.cs
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/InterfaceStubGenerator.Shared/ParameterMetadataEmission.cs
  • Code Duplication · Edited copy of a member (14 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs
  • Code Duplication · Edited copy of a member (14 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs
  • Code Duplication · Edited copy of a member (9 corresponding lines) src/InterfaceStubGenerator.Shared/QueryObjectPropertyParsing.cs
  • Code Duplication · Edited copy of a member (9 corresponding lines) src/InterfaceStubGenerator.Shared/QueryParameterParsing.cs
  • Code Duplication · Edited copy of a member (14 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/InterfaceStubGenerator.Shared/MultipartParameterParsing.cs
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/InterfaceStubGenerator.Shared/Parser.cs
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs
  • Code Duplication · Edited copy of a member (5 corresponding lines) src/InterfaceStubGenerator.Shared/LiteralEmissionHelpers.cs
  • Code Duplication · Edited copy of a member (6 corresponding lines) src/InterfaceStubGenerator.Shared/RequestParsing.cs
  • Code Duplication · Edited copy of a member (11 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs
  • Code Duplication · Duplicated block (17 lines × 2) src/InterfaceStubGenerator.Shared/MethodSignatureEmission.cs
  • Code Duplication · Duplicated block (10 lines × 2) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs
  • Code Duplication · Edited copy of a member (13 corresponding lines) src/examples/BlazorWasmSample/Pages/Index.razor
  • Code Duplication · Duplicated block (7 lines × 2) src/examples/Documentation/Tooling/PolyfillSample.cs
  • Churn × Complexity Hotspots · Hotspot: src/Refit.NativeAotSmoke/Program.cs src/Refit.NativeAotSmoke/Program.cs
  • Churn × Complexity Hotspots · Repeated repair: src/Refit/GeneratedRequestRunner.cs src/Refit/GeneratedRequestRunner.cs
  • Churn × Complexity Hotspots · Repeated repair: src/Refit/ApiException.cs src/Refit/ApiException.cs
  • Churn × Complexity Hotspots · Repeated repair: src/Refit/RequestExecutionHelpers.cs src/Refit/RequestExecutionHelpers.cs
  • Churn × Complexity Hotspots · Repeated repair: src/InterfaceStubGenerator.Shared/InterfaceStubGeneratorV2.cs src/InterfaceStubGenerator.Shared/InterfaceStubGeneratorV2.cs
  • Churn × Complexity Hotspots · Repeated repair: src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs
  • Churn × Complexity Hotspots · Repeated repair: src/Refit.Newtonsoft.Json/NewtonsoftJsonContentSerializer.cs src/Refit.Newtonsoft.Json/NewtonsoftJsonContentSerializer.cs
  • Churn × Complexity Hotspots · Repeated repair: src/Refit/DefaultUrlParameterFormatter.cs src/Refit/DefaultUrlParameterFormatter.cs
  • Churn × Complexity Hotspots · Repeated repair: src/Refit/GeneratedOnlyRequestBuilder.cs src/Refit/GeneratedOnlyRequestBuilder.cs
  • Explicit Debt · CoverageExclusion src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs
  • Explicit Debt · CoverageExclusion src/Refit/AsyncEnumerableObservable{T}.cs
  • Explicit Debt · CoverageExclusion src/Refit/RequestExecutionHelpers.cs
  • Explicit Debt · CoverageExclusion src/Refit/FormFieldNames.cs
  • Explicit Debt · CoverageExclusion src/Refit/JsonLinesContent{T}.cs
  • Explicit Debt · CoverageExclusion src/Refit/RequestExecutionHelpers.cs
  • Cancellation propagation · Async delegate without CancellationToken: ToStreamingHttpContent src/Refit/SystemTextJsonContentSerializer.cs
  • Cancellation propagation · Async method without CancellationToken: HandWrittenGetAsync src/benchmarks/Refit.Benchmarks/HandWrittenClientComparisonBenchmark.cs
  • Cancellation propagation · Async method without CancellationToken: RefitGetAsync src/benchmarks/Refit.Benchmarks/HandWrittenClientComparisonBenchmark.cs
  • Cancellation propagation · Async method without CancellationToken: HandWrittenListAsync src/benchmarks/Refit.Benchmarks/HandWrittenClientComparisonBenchmark.cs
  • Cancellation propagation · Async method without CancellationToken: RefitListAsync src/benchmarks/Refit.Benchmarks/HandWrittenClientComparisonBenchmark.cs
  • Cancellation propagation · Async method without CancellationToken: RefitCreateAsync src/benchmarks/Refit.Benchmarks/HandWrittenClientComparisonBenchmark.cs
  • Stateful singletons · Stateful shared instance: RefitRequestsSettings src/Refit/RefitRequestsSettings.cs
  • Stateful singletons · Stateful shared instance: QueryAttribute src/Refit/QueryAttribute.cs
  • Stateful singletons · Stateful shared instance: BufferingHandler src/examples/Documentation/Clients/BufferingHandler.cs
  • Stateful singletons · Stateful shared instance: DispatchHandler src/examples/Documentation/RuntimeHelpers/DispatchHandler.cs
  • Stateful singletons · Process-global static state: HttpClientFactoryReflectionCore src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs

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

Fixed since the last survey: 148 findings

These 148 critical or serious findings were in the previous survey, on 23 October 2026, and are gone from this one. The first 100 are listed here.

  • God Classes · TooManyMethods: RestService src/Refit/RestService.cs
  • Code Duplication · Duplicated block (20–22 lines × 2) src/InterfaceStubGenerator.Shared/MethodSignatureEmission.cs
  • Code Duplication · Duplicated block (15 lines × 2) src/Refit.HttpClientFactory/HttpClientFactoryCore.cs
  • Code Duplication · Duplicated block (11 lines × 2) src/Refit.HttpClientFactory/HttpClientFactoryCore.cs
  • Code Duplication · Duplicated block (7–8 lines × 2) src/examples/Documentation/Serialization/Other/OtherSerializers.cs
  • Cohesion (LCOM4) · Low cohesion: SystemTextJsonContentSerializer (LCOM4 6) src/Refit/SystemTextJsonContentSerializer.cs
  • Code Coverage · Coverage not measured — no coverage collector is wired up
  • Explicit Debt · CoverageExclusion src/Polyfills/DynamicDependencyAttribute.cs
  • Explicit Debt · CoverageExclusion src/Refit.HttpClientFactory/HttpClientFactoryCore.cs
  • Explicit Debt · CoverageExclusion src/Refit/RequestExecutionHelpers.cs
  • Explicit Debt · CoverageExclusion src/Refit/ReflectionRequestBuilderResolver.cs
  • Explicit Debt · BareSuppressMessage src/Refit/SystemTextJsonContentSerializer.JsonContext.cs
  • Explicit Debt · BareSuppressMessage src/Refit/SystemTextJsonContentSerializer.JsonContext.cs
  • Cancellation propagation · Async method without CancellationToken: Create src/Refit/ApiException.cs
  • Cancellation propagation · Async method without CancellationToken: ThrowsApiExceptionAsync src/Refit/ApiResponse{T}.cs
  • Cancellation propagation · Async method without CancellationToken: CreateExceptionAsync src/Refit/DefaultApiExceptionFactory.cs
  • Cancellation propagation · Async method without CancellationToken: CreateAsync src/Refit/ValidationApiException.cs
  • Cancellation propagation · Async method without CancellationToken: CreateExceptionsAsync src/examples/Documentation/Errors/Errors.cs
  • Cancellation propagation · Async method without CancellationToken: ShowCustomFactoryDiscrepancyAsync src/examples/Documentation/Errors/Errors.cs
  • Cancellation propagation · Async method without CancellationToken: ShowCustomDeserializationDiscrepancyAsync src/examples/Documentation/Errors/Errors.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: ShowClientAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: ShowCapturedEncodingAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: ShowRoutesAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: SendOtherMethodsAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: ShowMatchersAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: ShowDuplicateQueryAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: ShowRepliesAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: ShowReplyPropertiesAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: ShowVerificationAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: ShowAdditionalRouteAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: ShowOneShotRaceAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: ShowFaultsAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: ShowResponseStubsAsync src/examples/Documentation/Testing/Testing.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Testing/TestingStreaming.cs
  • Cancellation propagation · Async method without CancellationToken: ShowEarlyItemsAsync src/examples/Documentation/Testing/TestingStreaming.cs
  • Cancellation propagation · Async method without CancellationToken: ShowDisconnectAsync src/examples/Documentation/Testing/TestingStreaming.cs
  • Cancellation propagation · Async method without CancellationToken: ShowFixedStreamsAsync src/examples/Documentation/Testing/TestingStreaming.cs
  • Cancellation propagation · Async method without CancellationToken: ShowUploadAsync src/examples/Documentation/Testing/TestingStreaming.cs
  • Cancellation propagation · Async method without CancellationToken: ShowBoundedCaptureAsync src/examples/Documentation/Testing/TestingStreaming.cs
  • Cancellation propagation · Async method without CancellationToken: ShowSimulatedDelayAsync src/examples/Documentation/Testing/TestingStreaming.cs
  • Cancellation propagation · Async method without CancellationToken: ShowVerificationTimeoutAsync src/examples/Documentation/Testing/TestingStreaming.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Clients/Clients.cs
  • Cancellation propagation · Async method without CancellationToken: CheckNamingWithContextAsync src/examples/Documentation/Clients/Clients.cs
  • Cancellation propagation · Async method without CancellationToken: CheckNamingSettingsAsync src/examples/Documentation/Clients/Clients.cs
  • Cancellation propagation · Async method without CancellationToken: CheckOwnedClientAsync src/examples/Documentation/Clients/Clients.cs
  • Cancellation propagation · Async method without CancellationToken: CheckContextClientsAsync src/examples/Documentation/Clients/Clients.cs
  • Cancellation propagation · Async method without CancellationToken: CheckFactoryClientsAsync src/examples/Documentation/Clients/Clients.cs
  • Cancellation propagation · Async method without CancellationToken: CheckEmptyAuthorizationAsync src/examples/Documentation/Clients/Clients.cs
  • Cancellation propagation · Async method without CancellationToken: CheckAuthorizationAsync src/examples/Documentation/Clients/Clients.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Clients/SettingsPolicies.cs
  • Cancellation propagation · Async method without CancellationToken: CheckBufferingAsync src/examples/Documentation/Clients/SettingsPolicies.cs
  • Cancellation propagation · Async method without CancellationToken: CheckUnmatchedAsync src/examples/Documentation/Clients/SettingsPolicies.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/GettingStarted/GettingStarted.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/ReturnTypes/ReturnTypes.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Routes/Routes.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Queries/Converters.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Queries/Formatters.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Queries/Queries.cs
  • Cancellation propagation · Async method without CancellationToken: CheckSerializerNamesAsync src/examples/Documentation/Queries/Queries.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Queries/QueryOptions.cs
  • Cancellation propagation · Async method without CancellationToken: CheckStringObjectsAsync src/examples/Documentation/Queries/QueryOptions.cs
  • Cancellation propagation · Async method without CancellationToken: CheckCollectionsAsync src/examples/Documentation/Queries/QueryOptions.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Headers/Headers.cs
  • Cancellation propagation · Async method without CancellationToken: CheckHeaderValidationAsync src/examples/Documentation/Headers/Headers.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Headers/RequestContext.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Bodies/Bodies.cs
  • Cancellation propagation · Async method without CancellationToken: CheckGzipAsync src/examples/Documentation/Bodies/Bodies.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Bodies/BodyPolicies.cs
  • Cancellation propagation · Async method without CancellationToken: CheckModesAsync src/examples/Documentation/Bodies/BodyPolicies.cs
  • Cancellation propagation · Async method without CancellationToken: CheckCompressionAsync src/examples/Documentation/Bodies/BodyPolicies.cs
  • Cancellation propagation · Async method without CancellationToken: CheckCompressedAsync src/examples/Documentation/Bodies/BodyPolicies.cs
  • Cancellation propagation · Async method without CancellationToken: CheckResolutionAsync src/examples/Documentation/Bodies/BodyPolicies.cs
  • Cancellation propagation · Async method without CancellationToken: CheckTimeoutAsync src/examples/Documentation/Bodies/BodyPolicies.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Bodies/JsonLinesUploadSample.cs
  • Cancellation propagation · Async method without CancellationToken: UploadAListYouAlreadyHaveAsync src/examples/Documentation/Bodies/JsonLinesUploadSample.cs
  • Cancellation propagation · Async method without CancellationToken: UploadABaseTypeWithItsDiscriminatorAsync src/examples/Documentation/Bodies/JsonLinesUploadSample.cs
  • Cancellation propagation · Async method without CancellationToken: SendAKnownContentLengthAsync src/examples/Documentation/Bodies/JsonLinesUploadSample.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Rationale/Rationale.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Aot/Aot.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/JsonContexts/ContextClientSample.cs
  • Cancellation propagation · Async method without CancellationToken: ShowRejectedOrderAsync src/examples/Documentation/JsonContexts/ContextClientSample.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/JsonContexts/ExistingSettingsSample.cs
  • Cancellation propagation · Async method without CancellationToken: KeepNamingAndConvertersAsync src/examples/Documentation/JsonContexts/ExistingSettingsSample.cs
  • Cancellation propagation · Async method without CancellationToken: UseJsonContextAsync src/examples/Documentation/JsonContexts/ExistingSettingsSample.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/JsonContexts/JsonContextSample.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/JsonContexts/JsonDefaultsSample.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/JsonContexts/JsonTypeInfoParameterSample.cs
  • Cancellation propagation · Async method without CancellationToken: PassMetadataToEachCallAsync src/examples/Documentation/JsonContexts/JsonTypeInfoParameterSample.cs
  • Cancellation propagation · Async method without CancellationToken: SkipMetadataAsync src/examples/Documentation/JsonContexts/JsonTypeInfoParameterSample.cs
  • Cancellation propagation · Async method without CancellationToken: PreferMetadataOverSettingsAsync src/examples/Documentation/JsonContexts/JsonTypeInfoParameterSample.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/JsonContexts/JsonTypeInfoSerializerSample.cs
  • Cancellation propagation · Async method without CancellationToken: ReadStreamAsync src/examples/Documentation/JsonContexts/JsonTypeInfoSerializerSample.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/JsonContexts/OwnOptionsSample.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/JsonContexts/ReflectionFallbackSample.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync src/examples/Documentation/Resilience/Resilience.cs
  • Cancellation propagation · Async method without CancellationToken: RetryReadAsync src/examples/Documentation/Resilience/Resilience.cs
  • Cancellation propagation · Async method without CancellationToken: SkipUnsafeMethodAsync src/examples/Documentation/Resilience/Resilience.cs
  • Cancellation propagation · Async method without CancellationToken: SkipBadJsonAsync src/examples/Documentation/Resilience/Resilience.cs
  • Cancellation propagation · Async method without CancellationToken: RefreshTokenPerAttemptAsync src/examples/Documentation/Resilience/Resilience.cs
Rebuild cost: about €150,000 · Estimate
Cost to rebuild€48,000 to €240,000, for 805 to 2,564 hours of work, about 1.0 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 58. 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.
SizeMedium: 57,160 lines of product code, of which 39% is declarations and boilerplate, 21% straight logic and 39% logic with branches
Comment linesThe estimate prices 42,386 lines. Comment lines count towards the size of 57,160 lines but aren't priced as work.
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
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.).
Raises the score by about 9 points · Medium effort · Data Protection
2
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 3 points · Low effort · ADR Quality
3
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.
Raises the score by about 4 points · Medium effort · Web-Security Posture

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €150,000 to build again, about 1.0 person-years of work. Its weakest lens is Security and Compliance, at 48 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Of all the actions in this report, it raises the score most for the work it takes: about 9 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — bounded-context dependency graph

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

arch Refit Refit Refit.HttpClientFactory HttpClientFactory Refit.HttpClientFactory->Refit Refit.HttpClientFactory.Reflection Reflection Refit.HttpClientFactory.Reflection->Refit Refit.HttpClientFactory.Reflection->Refit.HttpClientFactory Refit.Reflection Reflection Refit.HttpClientFactory.Reflection->Refit.Reflection Refit.Newtonsoft.Json Json Refit.Newtonsoft.Json->Refit Refit.Reflection->Refit Refit.Xml Xml Refit.Xml->Refit advanced-index advanced-index advanced-index->Refit advanced-index->Refit.HttpClientFactory advanced-index->Refit.HttpClientFactory.Reflection advanced-index->Refit.Newtonsoft.Json advanced-index->Refit.Reflection advanced-index->Refit.Xml advanced-method-metadata advanced-method-metadata advanced-method-metadata->Refit advanced-method-metadata->Refit.HttpClientFactory advanced-method-metadata->Refit.HttpClientFactory.Reflection advanced-method-metadata->Refit.Newtonsoft.Json advanced-method-metadata->Refit.Reflection advanced-method-metadata->Refit.Xml advanced-query-builder advanced-query-builder advanced-query-builder->Refit advanced-query-builder->Refit.HttpClientFactory advanced-query-builder->Refit.HttpClientFactory.Reflection advanced-query-builder->Refit.Newtonsoft.Json advanced-query-builder->Refit.Reflection advanced-query-builder->Refit.Xml advanced-request-helpers advanced-request-helpers advanced-request-helpers->Refit advanced-request-helpers->Refit.HttpClientFactory advanced-request-helpers->Refit.HttpClientFactory.Reflection advanced-request-helpers->Refit.Newtonsoft.Json advanced-request-helpers->Refit.Reflection advanced-request-helpers->Refit.Xml aot aot aot->Refit aot->Refit.HttpClientFactory aot->Refit.HttpClientFactory.Reflection aot->Refit.Newtonsoft.Json aot->Refit.Reflection aot->Refit.Xml clients-creation clients-creation clients-creation->Refit clients-creation->Refit.HttpClientFactory clients-creation->Refit.HttpClientFactory.Reflection clients-creation->Refit.Newtonsoft.Json clients-creation->Refit.Reflection clients-creation->Refit.Xml clients-dependency-injection clients-dependency-injection clients-dependency-injection->Refit clients-dependency-injection->Refit.HttpClientFactory clients-dependency-injection->Refit.HttpClientFactory.Reflection clients-dependency-injection->Refit.Newtonsoft.Json clients-dependency-injection->Refit.Reflection clients-dependency-injection->Refit.Xml clients-index clients-index clients-index->Refit clients-index->Refit.HttpClientFactory clients-index->Refit.HttpClientFactory.Reflection clients-index->Refit.Newtonsoft.Json clients-index->Refit.Reflection clients-index->Refit.Xml clients-request-builders clients-request-builders clients-request-builders->Refit clients-request-builders->Refit.HttpClientFactory clients-request-builders->Refit.HttpClientFactory.Reflection clients-request-builders->Refit.Newtonsoft.Json clients-request-builders->Refit.Reflection clients-request-builders->Refit.Xml clients-resilience clients-resilience clients-resilience->Refit clients-resilience->Refit.HttpClientFactory clients-resilience->Refit.HttpClientFactory.Reflection clients-resilience->Refit.Newtonsoft.Json clients-resilience->Refit.Reflection clients-resilience->Refit.Xml clients-settings clients-settings clients-settings->Refit clients-settings->Refit.HttpClientFactory clients-settings->Refit.HttpClientFactory.Reflection clients-settings->Refit.Newtonsoft.Json clients-settings->Refit.Reflection clients-settings->Refit.Xml clients-telemetry clients-telemetry clients-telemetry->Refit clients-telemetry->Refit.HttpClientFactory clients-telemetry->Refit.HttpClientFactory.Reflection clients-telemetry->Refit.Newtonsoft.Json clients-telemetry->Refit.Reflection clients-telemetry->Refit.Xml index index index->Refit index->Refit.HttpClientFactory index->Refit.HttpClientFactory.Reflection index->Refit.Newtonsoft.Json index->Refit.Reflection index->Refit.Xml requests-bodies requests-bodies requests-bodies->Refit requests-bodies->Refit.HttpClientFactory requests-bodies->Refit.HttpClientFactory.Reflection requests-bodies->Refit.Newtonsoft.Json requests-bodies->Refit.Reflection requests-bodies->Refit.Xml __more__ +45 more projects

Architecture: which parts of the code depend on which

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

15 modules, with 5 dependencies between them. Every module uses only modules listed above it, so there are no loops.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 (global)2 Refit3 Refit.Buffers4 Refit.CodeFixes5 Refit.Internal6 Refit.NativeAotPackageSmoke7 Refit.NetFrameworkSmoke8 System9 System.Collections.Specialized10 System.Diagnostics.CodeAnalysis11 System.Runtime.CompilerServices12 Refit.Generator13 Refit.NativeAotSmoke14 System.Net.Http15 Refit.Analyzers
1 (global)
2 Refit
3 Refit.Buffers
4 Refit.CodeFixes
5 Refit.Internal
6 Refit.NativeAotPackageSmoke
7 Refit.NetFrameworkSmoke
8 System
9 System.Collections.Specialized
10 System.Diagnostics.CodeAnalysis
11 System.Runtime.CompilerServices
12 Refit.Generator7
13 Refit.NativeAotSmoke1
14 System.Net.Http1
15 Refit.Analyzers15
Uses a module listed above itPart of a loopThe module itself
1 (global)2 Refit3 Refit.Buffers4 Refit.CodeFixes5 Refit.Internal6 Refit.NativeAotPackageSmoke7 Refit.NetFrameworkSmoke8 System9 System.Collections.Specialized10 System.Diagnostics.CodeAnalysis11 System.Runtime.CompilerServices12 Refit.Generator13 Refit.NativeAotSmoke14 System.Net.Http15 Refit.Analyzers(global)1Refit2Refit.Buffers3Refit.CodeFixes4Refit.Internal5Refit.NativeAotPackageSmoke6Refit.NetFrameworkSmoke7System8System.Collections.Specialized9System.Diagnostics.CodeAnalysis10System.Runtime.CompilerServices11Refit.Generator12Refit.NativeAotSmoke13System.Net.Http14Refit.Analyzers1571115

At a glance — Code Health · 66% · Adequate ·

At a glance — Architecture · 74% · Adequate · gated by AX2 ·

At a glance — Maturity · 63% · Adequate · gated by M2 ·

At a glance — Readiness · 79% · Strong ·

At a glance — Security · 48% · Weak · gated by D36, C1 ·

At a glance — Performance · 77% · Strong ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection10High / Critical
A03:2025 — Software Supply Chain Failures3Medium
A07:2025 — Authentication Failures2High / Critical

Roadmap

Top priorities: 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.); 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; Resolve the 1 No ADRs found finding(s) in ADR Quality.

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

Do thisHelpsEffortDimension
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.).+9.0 ptsMediumData Protection
Resolve the 1 No ADRs found finding(s) in ADR Quality.+2.5 ptsLowADR Quality
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.+4.4 ptsMediumWeb-Security Posture
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.9 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.9 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.9 ptsLowSupply-chain Provenance & Signing
Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with RequestBuilderImplementation.cs.+1.6 ptsLowExplicit Debt
Resolve the 4 NoWarnInCsproj finding(s) in Explicit Debt — start with Refit.Newtonsoft.Json.Tests.csproj, Refit.Reflection.Tests.csproj, Refit.Testing.Tests.csproj.+1.6 ptsLowExplicit Debt

File quality

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

FileScoreBandWorst signal
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
src/examples/Documentation/.editorconfig5.2MixedExplicit Debt: AnalyzerSeverityNone
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
src/Refit/SystemTextJsonContentSerializer.cs6.0MixedExplicit Debt: CoverageExclusion
src/Refit/RequestExecutionHelpers.cs6.0MixedExplicit Debt: CoverageExclusion
src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs6.0MixedExplicit Debt: CoverageExclusion
src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs6.0MixedExplicit Debt: CoverageExclusion
src/InterfaceStubGenerator.Shared/RequestParsing.cs6.0MixedExplicit Debt: CoverageExclusion
src/InterfaceStubGenerator.Shared/QueryParameterParsing.cs6.0MixedExplicit Debt: CoverageExclusion
src/Refit.Reflection/RequestBuilderImplementation.cs6.1MixedExplicit Debt: EmptyCatchBlock
.editorconfig6.4MixedExplicit Debt: AnalyzerSeverityNone
src/Refit/ApiResponse{T}.cs6.6MixedExplicit Debt: BareSuppressMessage
src/InterfaceStubGenerator.Shared/InterfaceMemberParsing.cs6.7MixedExplicit Debt: CoverageExclusion
src/InterfaceStubGenerator.Shared/QueryValueEmission.cs6.7MixedExplicit Debt: CoverageExclusion
src/Refit.Reflection/RequestBuilderImplementation.Execution.cs6.7MixedExplicit Debt: CoverageExclusion
src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.Helpers.cs6.7MixedExplicit Debt: CoverageExclusion
src/InterfaceStubGenerator.Shared/QueryParameterEmission.cs6.7MixedExplicit Debt: CoverageExclusion
src/Refit/JsonContentSerializer.cs6.7MixedExplicit Debt: CoverageExclusion
src/InterfaceStubGenerator.Shared/HttpMethodAttributeParsing.cs6.9MixedExplicit Debt: CoverageExclusion
src/Refit/IApiResponse.cs6.9MixedExplicit Debt: BareSuppressMessage

How the grades work

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

Critical — 35

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 230

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 54

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

Could not be resolved — 6

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 65 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

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

What we checked — 65 dimensions across the health lenses
D1D2D3D4D5D6D10D13D14D15D16D17D18D19D20D24D26D27D28D29D34D35D36D37D43D44AX1AX10AX2AX3AX4AX5AX6AX8C1C2GD1IC1M1M2M3M4P1P2P3P4P6PF1PF3S1X1X12X16X18X2X20X21X23X24X25X27X28X29X3X5

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

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 303 of 319 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1cd47-cb41-7c25-9403-fddeaffbe9f1.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — 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. Coverage NOT MEASURED: this repository runs its tests on Microsoft.Testing.Platform (its global.json opts in), where coverage comes from a coverage extension the test project references — and none is wired up: no build file names `Microsoft.Testing.Extensions.CodeCoverage` or `coverlet.MTP`. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment. Add one of those PackageReferences to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `Microsoft.Testing.Extensions.CodeCoverage` (or `coverlet.MTP`) package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry), so no test ever ran. This is OUR limitation, not a defect in the repo — it is excluded from the score. We track the analyzer-image gap so it can be closed.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
  • D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'src/Refit/Refit.csproj' with message: IsAotCompatible and EnableAotAnalyzer are not supported for the target framework. Consider multi-targeting to a supported framework to enable ahead-of-time compilation analysis, and set IsAotCompatible only for the supported frameworks. For example: <IsAotCom….
  • 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.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • 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.
  • D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (57,160 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • 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/InterfaceStubGenerator.Shared/BodyContentEmission.cs`, `src/InterfaceStubGenerator.Shared/Emitter.cs`, `src/InterfaceStubGenerator.Shared/FormFieldEmission.cs`, `src/InterfaceStubGenerator.Shared/InlineRequestEmission.cs`, `src/InterfaceStubGenerator.Shared/IsExternalInit.cs`, … (+86 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • 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.
  • 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. 142 further occurrence(s) are not listed individually; the score already reflects all 182.
  • Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/examples/Documentation/Pages/index/index.csproj, src/examples/Documentation/Pages/advanced-index/advanced-index.csproj, src/examples/Documentation/Pages/advanced-method-metadata/advanced-method-metadata.csproj, src/examples/Documentation/Pages/advanced-query-builder/advanced-query-builder.csproj, src/examples/Documentation/Pages/advanced-request-helpers/advanced-request-helpers.csproj and 79 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.

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

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

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

  • 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.
  • 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.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • 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").
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity9.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was top-level statements at 36. 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 LiteralEmissionHelpers.AppendEscapedCharacter at 17 — 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/InterfaceStubGenerator.Shared/LiteralEmissionHelpers.cs (LiteralEmissionHelpers.AppendEscapedCharacter at 17). 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.

top-level statements (cyclomatic 36)src/Refit.NativeAotSmoke/Program.cs:9

What to do

  1. Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with top-level statements (cyclomatic 36). — Refactoring it lifts Cyclomatic Complexity from 9.0 to about 10.0/10.

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

D2 · Cognitive Complexity9.0 / 10Strong✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

1 method(s) exceeded the cognitive complexity threshold of 15; the worst was top-level statements at 37.

top-level statements (cognitive 37)src/Refit.NativeAotSmoke/Program.cs:9

What to do

  1. Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with top-level statements (cognitive 37). — Refactoring it lifts Cognitive Complexity from 9.0 to about 10.0/10.

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

D3 · God Classes9.2 / 10Stronggated by 10 serious findings✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

10 god class(es) detected.

TooManyMethods: RequestBuilderImplementation · ×6src/Refit.Reflection/RequestBuilderImplementation.cs
ClassTooLong: InlineRequestEmission · ×3src/InterfaceStubGenerator.Shared/InlineRequestEmission.cs
FileTooLong: InterfaceStubGenerator.Shared/RequestParameterParsing.cssrc/InterfaceStubGenerator.Shared/RequestParameterParsing.cs

What to do

  1. Resolve the 6 TooManyMethods finding(s) in God Classes — start with RequestBuilderImplementation.cs, GeneratedRequestRunner.cs, RestMethodInfoInternal.cs. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 3 ClassTooLong finding(s) in God Classes — start with InlineRequestEmission.cs, QueryObjectEmission.cs, RequestExecutionHelpers.cs. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 FileTooLong finding(s) in God Classes — start with RequestParameterParsing.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D4 · Code Duplication9.9 / 10Stronggated by 64 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

16 duplicated block group(s) detected. A further 61 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 5 of the 77 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.

Edited copy of a member (11 corresponding lines) · ×11src/InterfaceStubGenerator.Shared/Models/InlineValueFormatModel.cs:57
Edited copy of a member (9 corresponding lines) · ×5src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:567
Edited copy of a member (14 corresponding lines) · ×5src/Refit.Reflection/FormObjectFlattener.cs:65
Edited copy of a member (13 corresponding lines) · ×3src/InterfaceStubGenerator.Shared/Models/RequestModel.cs:76
Edited copy of a member (21 corresponding lines) · ×2src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:91

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

What to do

  1. Resolve the 11 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs (6), InlineValueFormatModel.cs, InterfaceModel.cs. — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 5 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with RequestParameterKindParsing.cs (2), RequestParameterParsing.cs, QueryObjectPropertyParsing.cs. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 5 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs (3), FormObjectFlattener.cs, MethodSignatureParsing.cs. — One of this dimension's main actionable groups (5 warning-level).

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

D5 · Coupling9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

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

Off the main sequence: Refit(net462)src/Refit/Refit.csproj:1

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling — start with Refit.csproj. — One of this dimension's main actionable groups (1 warning-level).

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 57 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2286 tests.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 7 packages use a banned license. ★ DEPTH: every package graded here is one this repository's MSBuild projects declare as a direct `PackageReference` (28 declared), and nothing beyond them was reached — this is the DECLARATION-SITE set, NOT the transitive closure. .NET has no lockfile a checkout is guaranteed to carry and this pass grades an unrestored tree, so a banned licence that only a direct dependency's OWN dependencies pull in is outside this verdict, exactly as the JVM arm's declaration-site verdict is.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 12 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

Top hotspots: src/Refit.NativeAotSmoke/Program.cs (3×36=108) Repeated repair below the complexity floor: src/Refit/GeneratedRequestRunner.cs (4 of 5 changes were fixes); src/Refit/ValidationApiException.cs (4 of 5 changes were fixes); src/Refit/ApiResponse{T}.cs (4 of 5 changes were fixes)

Repeated repair: src/Refit/GeneratedRequestRunner.cs · ×11src/Refit/GeneratedRequestRunner.cs:505
Hotspot: src/Refit.NativeAotSmoke/Program.cssrc/Refit.NativeAotSmoke/Program.cs:9

What to do

  1. Resolve the 11 Repeated repair finding(s) in Churn × Complexity Hotspots — start with GeneratedRequestRunner.cs, ValidationApiException.cs, ApiResponse{T}.cs. — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with Program.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D16 · Bus Factor7.8 / 10Strong✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

39 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/InterfaceStubGenerator.Shared/RequestParameterParsing.cs. Counted over 176 of the 369 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1

What to do

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

D17 · Explicit Debt6.5 / 10Adequate✓ Tool-verified

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

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

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

139 deducted debt markers + unmeasured dead symbols across 57160 LoC in the .NET projects (1.7/KLoC) → score 6.5. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

AnalyzerSeverityNone · ×19.editorconfig:789
NoWarnInCsproj — 12 warning codes suppressed in one element · ×4src/tests/Refit.Newtonsoft.Json.Tests/Refit.Newtonsoft.Json.Tests.csproj:10
EmptyCatchBlocksrc/Refit.Reflection/RequestBuilderImplementation.cs:395
CoverageExclusion · ×64src/InterfaceStubGenerator.Shared/HttpMethodAttributeParsing.cs:18
BareSuppressMessage · ×6src/Refit/ApiResponse{T}.cs:149

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

What to do

  1. Resolve the 19 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (19). — One of this dimension's main actionable groups (19 issue-level).
  2. Resolve the 4 NoWarnInCsproj finding(s) in Explicit Debt — start with Refit.Newtonsoft.Json.Tests.csproj, Refit.Reflection.Tests.csproj, Refit.Testing.Tests.csproj. — One of this dimension's main actionable groups (4 issue-level).
  3. Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with RequestBuilderImplementation.cs. — One of this dimension's main actionable groups (1 issue-level).

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

D18 · Solution Shape10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

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

156 projects, 12029 source files, 118321 hand-written lines of code (56669 production / 61652 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), 513 inter-project edges (build status unknown — did not finish).

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

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

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

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

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

2 of 2 documentation facets pass in full. 5 document(s) read across 16 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

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

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

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

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value8.9 8.8 / 10Strong✓ Tool-verified

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

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

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

8 of 701 judged comments only repeat the code they sit on (1.1 %). 6 comment(s) in another language or script were not judged.

redundant comment · ×8src/InterfaceStubGenerator.Shared/SharedInfrastructureEmission.cs:49
doc comments repeat the names · ×21src/InterfaceStubGenerator.Shared/BodyContentEmission.cs:245

What to do

  1. Resolve the 8 redundant comment finding(s) in Comment Value — start with IGitHubService.cs (3), SharedInfrastructureEmission.cs, RequestBuilderImplementation.QueryAndHeaders.cs. — One of this dimension's main actionable groups (8 recommendation-level).

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

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 of 88 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability9.7 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

17 % of calls cross a namespace and 1 % go through an interface, but 98 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)8.4 / 10Adequategated by 10 critical findings✓ Tool-verified

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

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

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

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

10 finding(s): 0 critical, 10 high, 0 medium, 0 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 127 file(s) — `src/InterfaceStubGenerator.Shared/BodyContentEmission.cs` (line 43, line 50, line 79, …), `src/InterfaceStubGenerator.Shared/Emitter.cs` (line 376, lines 383–384, line 557, …), `src/InterfaceStubGenerator.Shared/FormFieldEmission.cs` (line 35, line 79), `src/InterfaceStubGenerator.Shared/InlineRequestEmission.cs` (line 96, line 348, line 372), `src/InterfaceStubGenerator.Shared/IsExternalInit.cs` (lines 23–28), … (+122 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 58 of those file(s) — `src/InterfaceStubGenerator.Shared/Models/WellKnownTypes.cs`, `src/InterfaceStubGenerator.Shared/QueryParameterEmission.cs`, `src/Polyfills/CallerArgumentExpressionAttribute.cs`, `src/Polyfills/CompilerFeatureRequiredAttribute.cs`, `src/Polyfills/DoesNotReturnIfAttribute.cs`, … (+53 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 9 of those file(s) — `src/Refit.Reflection/ObjectToInferredTypesConverter.cs`, `src/Refit.Reflection/RestMethodInfoInternal.ParameterBinding.cs`, `src/Refit.Testing/StreamSource.cs`, `src/Refit/ApiResponseExtensions.cs`, `src/Refit/EnumerableExtensions.cs`, … (+4 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. No action in Static Analysis (SAST) — all 7 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 (7 issue-level, 0 of them charged here).
  3. No action in Static Analysis (SAST) — all 2 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 (2 issue-level, 0 of them charged here).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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

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

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

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 176 of the 369 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.9 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: JsonContentSerializer.cs↔RefitSettings.cs 80%; ApiException.cs↔JsonContentSerializer.cs 60%

Change coupling: JsonContentSerializer.cs ↔ RefitSettings.cs · ×2src/Refit/JsonContentSerializer.cs:1

What to do

  1. Resolve the 2 Change coupling finding(s) in Change Coupling — start with JsonContentSerializer.cs, ApiException.cs. — One of this dimension's main actionable groups (2 warning-level).

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

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

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

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

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

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

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

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

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 88 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition9.4 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

  • `RefitRequestsSettings` is not registered, but the singleton `RefitSettings` creates it and keeps it in `Requests`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_requestOptions; e.g. `_requestOptions` at line 67). — src/Refit/RefitRequestsSettings.cs:8
  • `QueryAttribute` is not registered, but `RequestBuilderImplementation` creates it and keeps it in the static `DefaultQueryAttribute`, 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 (_collectionFormat; e.g. `_collectionFormat` at line 115). — src/Refit/QueryAttribute.cs:10
  • `BufferingHandler` is not registered, but `SettingsPolicies` creates it and keeps it in the static `Handler`, 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 (LengthBeforeRead; e.g. `LengthBeforeRead` at line 19). — src/examples/Documentation/Clients/BufferingHandler.cs:7
  • `DispatchHandler` is not registered, but `DispatchSample` creates it and keeps it in the static `Handler`, 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 (RequestCount, LastResponse; e.g. `RequestCount` at line 25). — src/examples/Documentation/RuntimeHelpers/DispatchHandler.cs:10
  • `HttpClientFactoryReflectionCore` 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 (_requestBuilderGenericForTypeMethod; e.g. `_requestBuilderGenericForTypeMethod` at line 243). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:11

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

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

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

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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

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

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `IGitHubService` declares 16 members: `GetUsersTaskAsync`, `PostUsersTaskAsync`, `GetUsersTaskStringAsync`, `PostUsersTaskStringAsync`, `GetUsersTaskStreamAsync`, `PostUsersTaskStreamAsync`, `GetUsersTaskHttpContentAsync`, `PostUsersTaskHttpContentAsync`, `GetUsersTaskHttpResponseMessageAsync`, `PostUsersTaskHttpResponseMessageAsync`, `GetUsersObservableHttpResponseMessage`, `PostUsersObservableHttpResponseMessage`, `GetUsersTaskTAsync`, `PostUsersTaskTAsync`, `GetUsersTaskApiResponseTAsync`, `PostUsersTaskApiResponseTAsync`. 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. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/benchmarks/Refit.Benchmarks/IGitHubService.cs:9

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

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

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

C1 · Data Protection0.0 / 10Critical✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

  • 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.).
  • Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C2 · Access Controls10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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

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

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

M1 · Documentation (README)7.6 / 10Strong✓ Tool-verified

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

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

What to do

  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Describe the projects a newcomer cannot place from the root README: 58 of 68 have no README of their own, in their folder or in their family's project (`src/InterfaceStubGenerator.Roslyn48`, `src/Refit.Analyzers.Roslyn48`, `src/Refit.CodeFixes.Roslyn48`, `src/Refit.HttpClientFactory.Reflection`, `src/Refit.HttpClientFactory` and 53 more).
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

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

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

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

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

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

  • README.md names .NET 8, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:88

What to do

  • Reconcile the README with reality: README.md names .NET 8, but the projects target .NET 10, 11.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P2 · Observability6.1 / 10Adequate✓ Tool-verified

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

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

  • Only 2/68 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 68, 8 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
  • Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling8.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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

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

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

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

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

PF1 · Benchmark discipline10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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

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

  • 3 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). (×3) — src/Refit.Reflection/RequestBuilderImplementation.cs:244, src/Refit.Reflection/RequestBuilderImplementation.cs:256, src/Refit.Testing/StreamSourceContent.cs:92

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • 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. — src/examples/SampleUsingLocalApi/RestApiforTest/Program.cs:26
  • No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. — src/examples/SampleUsingLocalApi/RestApiforTest/Program.cs:26

What to do

  • 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.
  • Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
X1 · Async correctness7.8 / 10Strong✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • 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. (×2) — src/Refit.Reflection/RequestBuilderImplementation.cs:244, src/Refit.Reflection/RequestBuilderImplementation.cs:256

What to do

  • Sync-over-async (deadlock risk)
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation5.4 / 10Adequate✓ Tool-verified

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 56/237 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.
  • Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. — src/Refit.NativeAotSmoke/Program.cs:257
  • 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. — src/Refit.Reflection/RequestBuilderImplementation.RequestBuilding.cs:332
  • No CancellationToken parameter — this work can't be stopped early once started. (×36) — src/Refit/ApiException.cs:303, src/Refit/RequestExecutionHelpers.cs:545, src/benchmarks/Refit.Benchmarks/EndToEndBenchmark.cs:133, …
  • Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`). — src/Refit/SystemTextJsonContentSerializer.cs:151

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard6.1 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

  • The `when` guard on line 598 changes `(seenInheritedProperties ??= [with(comparer: SymbolEqualityComparer.Default)])` with `(seenInheritedProperties ??= [with(comparer: SymbolEqualityComparer.Default)]).Add(property)` while deciding whether its arm matches. A guard answers "does this arm apply?" and the runtime evaluates it during PATTERN MATCHING — so the change lands on arms that are then NOT selected, and `&&` short-circuits, so it is skipped altogether whenever the operand to its left already decides the answer. The accounting therefore depends on evaluation order and on how many labels the subject was compared against, not on any statement a reader can point at: the update is missed on exactly the path the left operand rules out, so a counter kept this way cannot reach a limit it is checked against on that path. Move the change out of the guard — leave the clause reading only (test the state without changing it: a peek, a lookup, a count) and make the call in the arm's BODY, where it runs precisely when the arm is chosen, or hoist it above the switch if it must happen for every subject. — src/InterfaceStubGenerator.Shared/Parser.cs:598

What to do

  • Each finding names the mutation inside the guard and the short-circuiting operator that decides whether it happens at all. Confirm from the two, then move the change out of the guard: a `when` clause is asked whether an arm MATCHES, and it is evaluated during pattern matching — on arms that are then not selected, and not at all once an operand to its left has answered. Leave the guard reading only (`when Failures + 1 >= Max`) and put the increment in the arm's BODY, where it runs exactly when the arm is chosen, or hoist it above the switch if it must happen on every subject.
X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.1 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • 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. — src/Refit.Reflection/RequestBuilderImplementation.cs:395
  • `catch (InvalidOperationException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×3) — src/examples/Documentation/Testing/TestingStreaming.cs:363, src/examples/Documentation/Paging/PagingSample.cs:148, src/examples/Documentation/Serialization/Other/OtherSerializers.cs:138
  • `catch (ArgumentException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×5) — src/examples/Documentation/Clients/SettingsPolicies.cs:60, src/examples/Documentation/Queries/Formatters.cs:95, src/examples/Documentation/Queries/Formatters.cs:105, …
  • `catch (NotSupportedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/examples/Documentation/Queries/Converters.cs:71
  • `catch (ArgumentNullException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/examples/Documentation/Queries/Formatters.cs:115
  • `catch (FormatException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/examples/Documentation/Headers/Headers.cs:113
  • `catch (IndexOutOfRangeException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/examples/Documentation/RuntimeHelpers/AttributeSample.cs:38
  • `catch (PlatformNotSupportedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/examples/Documentation/RuntimeHelpers/BodySample.cs:103
  • `catch (ObjectDisposedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/examples/Documentation/RuntimeHelpers/DispatchSample.cs:140

What to do

  • Swallowed exception (empty catch)
X5 · Nullable reference types8.4 / 10Strong✓ Tool-verified

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

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

  • ~2.0 `!` suppressions per 1k syntax nodes — 422 suppression(s) across the 213361 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

What to do

  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Reference — by lens

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

LensScoreRatingImpact
Code Health66%AdequateAcceptable, with room to improve.
Architecture74%Adequate — gated by AX2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity63%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness79%StrongStrongest area.
Security48%Weak — gated by D36, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance77%StrongSolid.
Unscored — 3 check(s) recorded observations but carry no score

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

  • P12 CI test-gate honesty — 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 — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

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

  • 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.
  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, 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 — 45 check(s) not relevant to this codebase

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

  • 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.
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • D11 Test Reliability — Test reliability not measured — analyzer environment
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D21 Naming Consistency — D21 withholds its bool missing the peers' prefix rows: 1 candidate(s) found and not reported.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D30 Dependency Vulnerabilities — 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
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 91 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — no coverage collector is wired up
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (48 value object(s))
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
  • 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
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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)

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

Critical — 35 finding(s)
D17 · Explicit Debt · AnalyzerSeverityNone · ×19
  • AnalyzerSeverityNone .editorconfig:789 — IDE0011 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:814 — IDE0280 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:18 — SST1486 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:19 — SST1471 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:21 — SST1148 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:23 — SST1662 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:25 — PSH1418 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:28 — SST2202 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:29 — IDE0090 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:31 — SST1531 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:33 — SST2221 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:34 — IDE0058 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:35 — CA1806 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:37 — PSH1410 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:44 — SST1600 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:45 — SST1601 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:46 — SST1663 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:49 — SST2334 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/examples/Documentation/.editorconfig:52 — XUNIT1051 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · NoWarnInCsproj · ×4
  • NoWarnInCsproj — 12 warning codes suppressed in one element src/tests/Refit.Newtonsoft.Json.Tests/Refit.Newtonsoft.Json.Tests.csproj:10 — A single <NoWarn> suppresses 12 warning codes (IL2026;IL2046;IL2067;IL2072;IL2075;IL2091;IL2109;IL3050;IL3051;RF003;RF004;RF005) in one stroke — one team-wide decision, not 12 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
  • NoWarnInCsproj — 12 warning codes suppressed in one element src/tests/Refit.Reflection.Tests/Refit.Reflection.Tests.csproj:10 — A single <NoWarn> suppresses 12 warning codes (IL2026;IL2046;IL2067;IL2072;IL2075;IL2091;IL2109;IL3050;IL3051;RF003;RF004;RF005) in one stroke — one team-wide decision, not 12 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
  • NoWarnInCsproj — 12 warning codes suppressed in one element src/tests/Refit.Testing.Tests/Refit.Testing.Tests.csproj:10 — A single <NoWarn> suppresses 12 warning codes (IL2026;IL2046;IL2067;IL2072;IL2075;IL2091;IL2109;IL3050;IL3051;RF003;RF004;RF005) in one stroke — one team-wide decision, not 12 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
  • NoWarnInCsproj — 12 warning codes suppressed in one element src/tests/Refit.Tests/Refit.Tests.csproj:10 — A single <NoWarn> suppresses 12 warning codes (IL2026;IL2046;IL2067;IL2072;IL2075;IL2091;IL2109;IL3050;IL3051;RF003;RF004;RF005) in one stroke — one team-wide decision, not 12 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · EmptyCatchBlock · ×1
  • EmptyCatchBlock src/Refit.Reflection/RequestBuilderImplementation.cs:395 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 230 finding(s)
D17 · Explicit Debt · CoverageExclusion · ×64
  • CoverageExclusion src/InterfaceStubGenerator.Shared/HttpMethodAttributeParsing.cs:18 — method MapKnownHttpVerb — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/HttpMethodAttributeParsing.cs:89 — method FindMethodPropertyGetter — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/HttpMethodAttributeParsing.cs:109 — method GetterReturnExpression — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/InterfaceMemberParsing.cs:105 — method GetInterfacePropertyRequestKey — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/InterfaceStubGeneratorV2.cs:230 — method IsInterfaceMethodDeclaration — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/MultipartContentEmission.cs:145 — method AppendMultipartAddArguments — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/Polyfills/Index.cs:18 — record Index — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/Polyfills/Range.cs:18 — record Range — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/QueryParameterEmission.cs:256 — method AppendInlineQueryStatement — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/QueryParameterParsing.cs:301 — method ResolveIndexedCollectionFormatValue — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/QueryParameterParsing.cs:413 — method GetSoleTypeArgument — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/QueryParameterParsing.cs:710 — method TryReadEnumMemberValue — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/QueryParameterParsing.cs:777 — method CanElementBeNull — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/QueryValueEmission.cs:121 — method ComputeFastPathExpression — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:113 — method IsUri — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/RequestParsing.cs:471 — method TryReadQueryUriFormat — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/RequestParsing.cs:503 — method TryReadTimeout — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/InterfaceStubGenerator.Shared/SpanBufferEmission.cs:35 — method Indent — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Polyfills/ArgumentExceptionHelper.cs:14 — class ArgumentExceptionHelper — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Polyfills/ArgumentOutOfRangeExceptionHelper.cs:11 — class ArgumentOutOfRangeExceptionHelper — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Polyfills/CallerArgumentExpressionAttribute.cs:13 — class CallerArgumentExpressionAttribute — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Polyfills/CollectionExtensions.cs:16 — class CollectionExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Polyfills/CompilerFeatureRequiredAttribute.cs:10 — class CompilerFeatureRequiredAttribute — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Polyfills/DoesNotReturnIfAttribute.cs:12 — class DoesNotReturnIfAttribute — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Polyfills/DynamicallyAccessedMembersAttribute.cs:21 — class DynamicallyAccessedMembersAttribute — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • + 39 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×36
  • Async method without CancellationToken: GetContentAsAsync src/Refit/ApiException.cs:303 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateDeserializationExceptionAsync src/Refit/RequestExecutionHelpers.cs:545 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Task_Async src/benchmarks/Refit.Benchmarks/EndToEndBenchmark.cs:133 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TaskString_Async src/benchmarks/Refit.Benchmarks/EndToEndBenchmark.cs:155 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TaskStream_Async src/benchmarks/Refit.Benchmarks/EndToEndBenchmark.cs:179 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TaskHttpContent_Async src/benchmarks/Refit.Benchmarks/EndToEndBenchmark.cs:203 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TaskT_Async src/benchmarks/Refit.Benchmarks/EndToEndBenchmark.cs:257 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ProduceAsync src/benchmarks/Refit.Benchmarks/FormBodySerializationBenchmark.cs:124 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: HandWrittenGetAsync src/benchmarks/Refit.Benchmarks/HandWrittenClientComparisonBenchmark.cs:80 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RefitGetAsync src/benchmarks/Refit.Benchmarks/HandWrittenClientComparisonBenchmark.cs:88 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: HandWrittenListAsync src/benchmarks/Refit.Benchmarks/HandWrittenClientComparisonBenchmark.cs:95 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RefitListAsync src/benchmarks/Refit.Benchmarks/HandWrittenClientComparisonBenchmark.cs:103 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: HandWrittenCreateAsync src/benchmarks/Refit.Benchmarks/HandWrittenClientComparisonBenchmark.cs:109 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RefitCreateAsync src/benchmarks/Refit.Benchmarks/HandWrittenClientComparisonBenchmark.cs:123 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ProduceAsync src/benchmarks/Refit.Benchmarks/RequestBodySerializationBenchmark.cs:73 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RefitBufferedAsync src/benchmarks/Refit.Benchmarks/StreamingBenchmark.cs:71 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RefitBufferedAsync src/benchmarks/Refit.Benchmarks/StreamingProfiledBenchmarks.cs:67 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync src/examples/Documentation/Serialization/Serialization.cs:27 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunContextSerializerAsync src/examples/Documentation/Serialization/Serialization.cs:63 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunContextClientAsync src/examples/Documentation/Serialization/Serialization.cs:75 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunDefaultsAsync src/examples/Documentation/Serialization/Serialization.cs:102 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunFastPathAsync src/examples/Documentation/Serialization/Serialization.cs:122 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunCombinedContextsAsync src/examples/Documentation/Serialization/Serialization.cs:137 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync src/examples/Documentation/Responses/Responses.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ShowSuccessAsync src/examples/Documentation/Responses/Responses.cs:25 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 11 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×14
  • Swallowed exception (caught, then discarded) src/examples/Documentation/Testing/TestingStreaming.cs:363 — `catch (InvalidOperationException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/Clients/SettingsPolicies.cs:60 — `catch (ArgumentException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/Queries/Converters.cs:71 — `catch (NotSupportedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/Queries/Formatters.cs:95 — `catch (ArgumentException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/Queries/Formatters.cs:105 — `catch (ArgumentException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/Queries/Formatters.cs:115 — `catch (ArgumentNullException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/Headers/Headers.cs:113 — `catch (FormatException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/Clients/Reflection/ReflectionClients.cs:121 — `catch (ArgumentException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/Paging/PagingSample.cs:148 — `catch (InvalidOperationException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/RuntimeHelpers/AttributeSample.cs:38 — `catch (IndexOutOfRangeException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/RuntimeHelpers/BodySample.cs:103 — `catch (PlatformNotSupportedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/RuntimeHelpers/DispatchSample.cs:140 — `catch (ObjectDisposedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/RuntimeHelpers/PathSample.cs:67 — `catch (ArgumentException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/examples/Documentation/Serialization/Other/OtherSerializers.cs:138 — `catch (InvalidOperationException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
D15 · Churn × Complexity Hotspots · Repeated repair · ×11
  • Repeated repair: src/Refit/GeneratedRequestRunner.cs src/Refit/GeneratedRequestRunner.cs:505 — src/Refit/GeneratedRequestRunner.cs changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is GeneratedRequestRunner.SetHeader at line 505), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix!: read problem details without a serializer, move reflection to Refit.Reflection, drop deprecated .NET 8/9 (#2374)”; “fix(headers): stop rewriting raw header values (#2310)”; “fix(generator): ship a single Roslyn analyzer slot (#2305)”; “build: raise the analyzer rules to error and fix the reported code (#2299)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:26:14 +00:00' --until='2026-11-03 15:26:14 +00:00' --full-history --no-merges -- src/Refit/GeneratedRequestRunner.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Refit/ValidationApiException.cs src/Refit/ValidationApiException.cs:247 — src/Refit/ValidationApiException.cs changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is ValidationApiException.ReadExtensionValue at line 247), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix!: read problem details without a serializer, move reflection to Refit.Reflection, drop deprecated .NET 8/9 (#2374)”; “fix: disambiguate case-differing parameters, preserve ContentLength header, and surface buffering exceptions (#2360)”; “fix(debugging): stop debugger displays rendering as a bare null (#2315)”; “build: raise the analyzer rules to error and fix the reported code (#2299)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:26:14 +00:00' --until='2026-11-03 15:26:14 +00:00' --full-history --no-merges -- src/Refit/ValidationApiException.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Refit/ApiResponse{T}.cs src/Refit/ApiResponse{T}.cs:76 — src/Refit/ApiResponse{T}.cs changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is ApiResponse.IsSuccessfulWithContent.get at line 76), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: disambiguate case-differing parameters, preserve ContentLength header, and surface buffering exceptions (#2360)”; “fix(debugging): stop debugger displays rendering as a bare null (#2315)”; “fix(generator): ship a single Roslyn analyzer slot (#2305)”; “build: raise the analyzer rules to error and fix the reported code (#2299)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:26:14 +00:00' --until='2026-11-03 15:26:14 +00:00' --full-history --no-merges -- src/Refit/ApiResponse{T}.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Refit/ApiException.cs src/Refit/ApiException.cs:380 — src/Refit/ApiException.cs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is ApiException.ReadContentCappedAsync at line 380), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix!: read problem details without a serializer, move reflection to Refit.Reflection, drop deprecated .NET 8/9 (#2374)”; “fix: disambiguate case-differing parameters, preserve ContentLength header, and surface buffering exceptions (#2360)”; “build: raise the analyzer rules to error and fix the reported code (#2299)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:26:14 +00:00' --until='2026-11-03 15:26:14 +00:00' --full-history --no-merges -- src/Refit/ApiException.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Refit/RequestExecutionHelpers.cs src/Refit/RequestExecutionHelpers.cs:109 — src/Refit/RequestExecutionHelpers.cs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is RequestExecutionHelpers.SendAndProcessResponseAsync at line 109), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix!: read problem details without a serializer, move reflection to Refit.Reflection, drop deprecated .NET 8/9 (#2374)”; “fix: disambiguate case-differing parameters, preserve ContentLength header, and surface buffering exceptions (#2360)”; “build: raise the analyzer rules to error and fix the reported code (#2299)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:26:14 +00:00' --until='2026-11-03 15:26:14 +00:00' --full-history --no-merges -- src/Refit/RequestExecutionHelpers.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/InterfaceStubGenerator.Shared/InterfaceStubGeneratorV2.cs src/InterfaceStubGenerator.Shared/InterfaceStubGeneratorV2.cs:287 — src/InterfaceStubGenerator.Shared/InterfaceStubGeneratorV2.cs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is InterfaceStubGeneratorV2.IsPotentialCustomHttpMethodSyntax at line 287), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix!: read problem details without a serializer, move reflection to Refit.Reflection, drop deprecated .NET 8/9 (#2374)”; “fix(generator): ship a single Roslyn analyzer slot (#2305)”; “build: raise the analyzer rules to error and fix the reported code (#2299)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:26:14 +00:00' --until='2026-11-03 15:26:14 +00:00' --full-history --no-merges -- src/InterfaceStubGenerator.Shared/InterfaceStubGeneratorV2.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs:208 — src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is RequestBuilderImplementation.ParseQueryStringInto at line 208), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix!: read problem details without a serializer, move reflection to Refit.Reflection, drop deprecated .NET 8/9 (#2374)”; “fix(headers): stop rewriting raw header values (#2310)”; “build: raise the analyzer rules to error and fix the reported code (#2299)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:26:14 +00:00' --until='2026-11-03 15:26:14 +00:00' --full-history --no-merges -- src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Refit.Testing/StubApiResponse.cs src/Refit.Testing/StubApiResponse.cs:71 — src/Refit.Testing/StubApiResponse.cs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is StubApiResponse.HasRequestError at line 71), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(debugging): stop debugger displays rendering as a bare null (#2315)”; “fix(generator): ship a single Roslyn analyzer slot (#2305)”; “build: raise the analyzer rules to error and fix the reported code (#2299)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:26:14 +00:00' --until='2026-11-03 15:26:14 +00:00' --full-history --no-merges -- src/Refit.Testing/StubApiResponse.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Refit.Newtonsoft.Json/NewtonsoftJsonContentSerializer.cs src/Refit.Newtonsoft.Json/NewtonsoftJsonContentSerializer.cs:117 — src/Refit.Newtonsoft.Json/NewtonsoftJsonContentSerializer.cs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is NewtonsoftJsonContentSerializer.GetEncoding at line 117), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix!: read problem details without a serializer, move reflection to Refit.Reflection, drop deprecated .NET 8/9 (#2374)”; “fix(generator): ship a single Roslyn analyzer slot (#2305)”; “build: raise the analyzer rules to error and fix the reported code (#2299)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:26:14 +00:00' --until='2026-11-03 15:26:14 +00:00' --full-history --no-merges -- src/Refit.Newtonsoft.Json/NewtonsoftJsonContentSerializer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Refit/DefaultUrlParameterFormatter.cs src/Refit/DefaultUrlParameterFormatter.cs:106 — src/Refit/DefaultUrlParameterFormatter.cs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is DefaultUrlParameterFormatter.ResolveFormatString at line 106), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix!: read problem details without a serializer, move reflection to Refit.Reflection, drop deprecated .NET 8/9 (#2374)”; “fix(generator): ship a single Roslyn analyzer slot (#2305)”; “build: raise the analyzer rules to error and fix the reported code (#2299)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:26:14 +00:00' --until='2026-11-03 15:26:14 +00:00' --full-history --no-merges -- src/Refit/DefaultUrlParameterFormatter.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Refit/GeneratedOnlyRequestBuilder.cs src/Refit/GeneratedOnlyRequestBuilder.cs:11 — src/Refit/GeneratedOnlyRequestBuilder.cs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is GeneratedOnlyRequestBuilder.GeneratedOnlyRequestBuilder.ctor at line 11), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix!: read problem details without a serializer, move reflection to Refit.Reflection, drop deprecated .NET 8/9 (#2374)”; “fix(generator): ship a single Roslyn analyzer slot (#2305)”; “build: raise the analyzer rules to error and fix the reported code (#2299)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:26:14 +00:00' --until='2026-11-03 15:26:14 +00:00' --full-history --no-merges -- src/Refit/GeneratedOnlyRequestBuilder.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×11
  • Edited copy of a member (11 corresponding lines) src/InterfaceStubGenerator.Shared/Models/InlineValueFormatModel.cs:57 — src/InterfaceStubGenerator.Shared/Models/InlineValueFormatModel.cs:57-67 | src/InterfaceStubGenerator.Shared/Models/PagingModel.cs:50-60 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/InterfaceStubGenerator.Shared/Models/InterfaceModel.cs:39 — src/InterfaceStubGenerator.Shared/Models/InterfaceModel.cs:39-49 | src/InterfaceStubGenerator.Shared/Models/QueryObjectPropertyModel.cs:61-73 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/InterfaceStubGenerator.Shared/ParameterMetadataEmission.cs:155 — src/InterfaceStubGenerator.Shared/ParameterMetadataEmission.cs:155-165 | src/InterfaceStubGenerator.Shared/PathObjectParameterParsing.cs:324-334 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/InterfaceStubGenerator.Shared/MultipartParameterParsing.cs:47 — src/InterfaceStubGenerator.Shared/MultipartParameterParsing.cs:47-57 | src/InterfaceStubGenerator.Shared/PagedMethodParsing.cs:131-141 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:213 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:213-223 | src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.ServiceCollection.cs:356-366 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:239 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:239-249 | src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.ServiceCollection.cs:410-420 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/InterfaceStubGenerator.Shared/Parser.cs:757 — src/InterfaceStubGenerator.Shared/Parser.cs:757-773 | src/InterfaceStubGenerator.Shared/RequestParameterParsingHelpers.cs:83-93 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:266 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:266-276 | src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.ServiceCollection.cs:466-476 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:20 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:20-30 | src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.ServiceCollection.cs:20-30 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:39 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:39-49 | src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.ServiceCollection.cs:60-70 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:59 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:59-69 | src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.ServiceCollection.cs:102-112 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D17 · Explicit Debt · BareSuppressMessage · ×6
  • BareSuppressMessage src/Refit/ApiResponse{T}.cs:149 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage src/Refit/ApiResponse{T}.cs:161 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage src/Refit/IApiResponse.cs:71 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage src/Refit/IApiResponse.cs:80 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage src/Refit/IApiResponse.cs:90 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage src/tests/Refit.GeneratedCode.TestModels/Scenarios/IGeneratedUserApi.cs:39 — System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
D3 · God Classes · TooManyMethods · ×6
  • TooManyMethods: RequestBuilderImplementation src/Refit.Reflection/RequestBuilderImplementation.cs — TooManyMethods — 1518 significant lines (blank, comment-only and punctuation-only lines excluded), 102 methods, declared across 6 files: Refit.Reflection/RequestBuilderImplementation.cs (26), Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs (25), Refit.Reflection/RequestBuilderImplementation.RequestBuilding.cs (24), Refit.Reflection/RequestBuilderImplementation.Payload.cs (13), +2 more file(s). The bar is 30 methods; this is 72 over it, 3.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GeneratedRequestRunner src/Refit/GeneratedRequestRunner.cs — TooManyMethods — 591 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods, declared across 5 files: Refit/GeneratedRequestRunner.cs (36), Refit/GeneratedRequestRunner.BodyContent.cs (10), Refit/GeneratedRequestRunner.Sending.cs (7), Refit/GeneratedRequestRunner.JsonTypeInfo.cs (5), +1 more file(s). The bar is 30 methods; this is 29 over it, 1.97× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: RestMethodInfoInternal src/Refit.Reflection/RestMethodInfoInternal.cs — TooManyMethods — 690 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods, declared across 4 files: Refit.Reflection/RestMethodInfoInternal.cs (21), Refit.Reflection/RestMethodInfoInternal.ParameterBinding.cs (19), Refit.Reflection/RestMethodInfoInternal.AttributeReading.cs (10), Refit.Reflection/RestMethodInfoInternal.PathPrefix.cs (1). The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: RequestParameterParsing src/InterfaceStubGenerator.Shared/RequestParameterParsing.cs — TooManyMethods — 561 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: SystemTextJsonContentSerializer src/Refit/SystemTextJsonContentSerializer.cs — TooManyMethods — 268 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods, declared across 2 files: Refit/SystemTextJsonContentSerializer.cs (21), Refit/SystemTextJsonContentSerializer.JsonContext.cs (14). The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: RefitInterfaceAnalyzer src/Refit.Analyzers.Shared/RefitInterfaceAnalyzer.cs — TooManyMethods — 288 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×5
  • Edited copy of a member (9 corresponding lines) src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:567 — src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:567-575 | src/InterfaceStubGenerator.Shared/RequestParameterParsing.cs:556-569 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/InterfaceStubGenerator.Shared/RequestParameterParsing.cs:556 — src/InterfaceStubGenerator.Shared/RequestParameterParsing.cs:556-569 | src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:567-575 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:378 — src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:378-386 | src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:527-535 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/InterfaceStubGenerator.Shared/QueryObjectPropertyParsing.cs:114 — src/InterfaceStubGenerator.Shared/QueryObjectPropertyParsing.cs:114-122 | src/InterfaceStubGenerator.Shared/QueryParameterParsing.cs:762-770 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) src/InterfaceStubGenerator.Shared/QueryParameterParsing.cs:762 — src/InterfaceStubGenerator.Shared/QueryParameterParsing.cs:762-770 | src/InterfaceStubGenerator.Shared/QueryObjectPropertyParsing.cs:114-122 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×5
  • Edited copy of a member (14 corresponding lines) src/Refit.Reflection/FormObjectFlattener.cs:65 — src/Refit.Reflection/FormObjectFlattener.cs:65-78 | src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs:353-367 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/InterfaceStubGenerator.Shared/MethodSignatureParsing.cs:150 — src/InterfaceStubGenerator.Shared/MethodSignatureParsing.cs:150-163 | src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:617-630 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:138 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:138-151 | src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.ServiceCollection.cs:228-241 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:162 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:162-175 | src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.ServiceCollection.cs:278-291 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:187 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:187-200 | src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.ServiceCollection.cs:330-343 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
AX2 · Stateful singletons · Stateful shared instance · ×4
  • Stateful shared instance: RefitRequestsSettings src/Refit/RefitRequestsSettings.cs:8 — `RefitRequestsSettings` is not registered, but the singleton `RefitSettings` creates it and keeps it in `Requests`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_requestOptions; e.g. `_requestOptions` at line 67).
  • Stateful shared instance: QueryAttribute src/Refit/QueryAttribute.cs:10 — `QueryAttribute` is not registered, but `RequestBuilderImplementation` creates it and keeps it in the static `DefaultQueryAttribute`, 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 (_collectionFormat; e.g. `_collectionFormat` at line 115).
  • Stateful shared instance: BufferingHandler src/examples/Documentation/Clients/BufferingHandler.cs:7 — `BufferingHandler` is not registered, but `SettingsPolicies` creates it and keeps it in the static `Handler`, 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 (LengthBeforeRead; e.g. `LengthBeforeRead` at line 19).
  • Stateful shared instance: DispatchHandler src/examples/Documentation/RuntimeHelpers/DispatchHandler.cs:10 — `DispatchHandler` is not registered, but `DispatchSample` creates it and keeps it in the static `Handler`, 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 (RequestCount, LastResponse; e.g. `RequestCount` at line 25).
PF3 · Async & latency hygiene · Sync-over-async blocking · ×4
  • Sync-over-async blocking — 3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Refit.Reflection/RequestBuilderImplementation.cs:244 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Refit.Reflection/RequestBuilderImplementation.cs:256 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Refit.Testing/StreamSourceContent.cs:92 — `.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).
D3 · God Classes · ClassTooLong · ×3
  • ClassTooLong: InlineRequestEmission src/InterfaceStubGenerator.Shared/InlineRequestEmission.cs — ClassTooLong — 475 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 75 over it, 1.19× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: QueryObjectEmission src/InterfaceStubGenerator.Shared/QueryObjectEmission.cs — ClassTooLong — 429 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 29 over it, 1.07× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • ClassTooLong: RequestExecutionHelpers src/Refit/RequestExecutionHelpers.cs — ClassTooLong — 415 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods, declared across 2 files: Refit/RequestExecutionHelpers.cs (19), Refit/RequestExecutionHelpers.Streaming.cs (3). The bar is 400 significant lines; this is 15 over it, 1.04× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×3
  • Edited copy of a member (13 corresponding lines) src/InterfaceStubGenerator.Shared/Models/RequestModel.cs:76 — src/InterfaceStubGenerator.Shared/Models/RequestModel.cs:76-88 | src/InterfaceStubGenerator.Shared/Models/RequestParameterModel.cs:72-85 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Refit/GeneratedRequestRunner.cs:30 — src/Refit/GeneratedRequestRunner.cs:30-42 | src/Refit/GeneratedRequestRunner.cs:56-68 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/examples/BlazorWasmSample/Pages/Index.razor:18 — src/examples/BlazorWasmSample/Pages/Index.razor:18-30 | src/examples/BlazorWasmSample/Pages/Status.razor:18-30 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D35 · Change Coupling · Change coupling · ×2
  • Change coupling: JsonContentSerializer.cs ↔ RefitSettings.cs src/Refit/JsonContentSerializer.cs:1 — `src/Refit/JsonContentSerializer.cs` and `src/Refit/RefitSettings.cs` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `aa78fc08` Housekeeping Update tests to remove need for comments (#1697) (at that commit the files were still `Refit/JsonContentSerializer.cs` and `Refit/RefitSettings.cs`); `0dd5a229` Rename IContentSerializer to IHttpContentSerializer and related metho… (at that commit the files were still `Refit/JsonContentSerializer.cs` and `Refit/RefitSettings.cs`); `fc263f9d` First pass at NRT annotations (at that commit the files were still `Refit/JsonContentSerializer.cs` and `Refit/RefitSettings.cs`) — run `git show` on any of them.
  • Change coupling: ApiException.cs ↔ JsonContentSerializer.cs src/Refit/ApiException.cs:1 — `src/Refit/ApiException.cs` and `src/Refit/JsonContentSerializer.cs` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `aa78fc08` Housekeeping Update tests to remove need for comments (#1697) (at that commit the files were still `Refit/ApiException.cs` and `Refit/JsonContentSerializer.cs`); `0dd5a229` Rename IContentSerializer to IHttpContentSerializer and related metho… (at that commit the files were still `Refit/ApiException.cs` and `Refit/JsonContentSerializer.cs`); `fc263f9d` First pass at NRT annotations (at that commit the files were still `Refit/ApiException.cs` and `Refit/JsonContentSerializer.cs`) — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×2
  • Edited copy of a member (21 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:91 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:91-115 | src/Refit.HttpClientFactory/HttpClientFactoryCore.cs:27-47 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Refit.Reflection/RequestBuilderImplementation.Execution.cs:50 — src/Refit.Reflection/RequestBuilderImplementation.Execution.cs:50-75 | src/Refit.Reflection/RequestBuilderImplementation.Execution.cs:225-245 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×2
  • Edited copy of a member (18 corresponding lines) src/Refit.Xml/XmlContentSerializer.cs:84 — src/Refit.Xml/XmlContentSerializer.cs:84-103 | src/Refit.Xml/XmlContentSerializer.cs:111-128 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Refit.Reflection/RestMethodInfoInternal.AttributeReading.cs:150 — src/Refit.Reflection/RestMethodInfoInternal.AttributeReading.cs:150-169 | src/Refit.Reflection/RestMethodInfoInternal.AttributeReading.cs:175-192 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:30 — src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:30-42 | src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:119-131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:133` calls `AppendText` and `src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:44` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 2) src/InterfaceStubGenerator.Shared/Parser.cs:783 — src/InterfaceStubGenerator.Shared/Parser.cs:783-795 | src/Refit.Analyzers.Shared/RefitInterfaceAnalyzer.cs:466-478 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×2
  • Duplicated block (10 lines × 2) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:222 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:222-231 | src/Refit.HttpClientFactory/HttpClientFactoryCore.cs:81-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:222` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) src/Refit/GeneratedRequestRunner.cs:30 — src/Refit/GeneratedRequestRunner.cs:30-40 | src/Refit/GeneratedRequestRunner.cs:56-65 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Refit/GeneratedRequestRunner.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) src/InterfaceStubGenerator.Shared/QueryObjectEmission.cs:35 — src/InterfaceStubGenerator.Shared/QueryObjectEmission.cs:35-43 | src/InterfaceStubGenerator.Shared/QueryObjectEmission.cs:701-709 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) src/InterfaceStubGenerator.Shared/QueryDictionaryEmission.cs:48 — src/InterfaceStubGenerator.Shared/QueryDictionaryEmission.cs:48-57 | src/InterfaceStubGenerator.Shared/QueryObjectEmission.cs:182-190 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2
  • Duplicated block (5 lines × 2) src/InterfaceStubGenerator.Shared/QueryParameterEmission.cs:370 — src/InterfaceStubGenerator.Shared/QueryParameterEmission.cs:370-374 | src/InterfaceStubGenerator.Shared/QueryParameterEmission.cs:518-522 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 2) src/examples/Documentation/Clients/Clients.cs:117 — src/examples/Documentation/Clients/Clients.cs:117-121 | src/examples/Documentation/Clients/Clients.cs:143-147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/examples/Documentation/Clients/Clients.cs:117` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) src/examples/Documentation/Serialization/Other/OtherSerializers.cs:38 — src/examples/Documentation/Serialization/Other/OtherSerializers.cs:38-43 | src/examples/Documentation/Serialization/Other/OtherSerializers.cs:89-94 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) src/examples/Documentation/Serialization/Serialization.cs:140 — src/examples/Documentation/Serialization/Serialization.cs:140-145 | src/examples/Documentation/Serialization/Serialization.cs:149-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
X1 · Async correctness · Sync-over-async (deadlock risk) · ×2
  • Sync-over-async (deadlock risk) src/Refit.Reflection/RequestBuilderImplementation.cs:244 — 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.
  • Sync-over-async (deadlock risk) src/Refit.Reflection/RequestBuilderImplementation.cs:256 — 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.
AX2 · Stateful singletons · Process-global static state · ×1
  • Process-global static state: HttpClientFactoryReflectionCore src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:11 — `HttpClientFactoryReflectionCore` 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 (_requestBuilderGenericForTypeMethod; e.g. `_requestBuilderGenericForTypeMethod` at line 243). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption — 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.
D1 · Cyclomatic Complexity · top-level statements (cyclomatic 36) · ×1
  • top-level statements (cyclomatic 36) src/Refit.NativeAotSmoke/Program.cs:9 — top-level statements has cyclomatic complexity 36 (threshold 15). Of this number, 34 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D15 · Churn × Complexity Hotspots · Hotspot · ×1
  • Hotspot: src/Refit.NativeAotSmoke/Program.cs src/Refit.NativeAotSmoke/Program.cs:9 — src/Refit.NativeAotSmoke/Program.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in top-level statements at line 9. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:26:14 +00:00' --until='2026-11-03 15:26:14 +00:00' --full-history --no-merges -- src/Refit.NativeAotSmoke/Program.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D17 · Explicit Debt · XxxComment · ×1
  • XxxComment src/tests/Refit.Tests/IntegrationTestHelper.cs:28 — // XXX: This is an evil hack, but it's okay for a unit test — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D2 · Cognitive Complexity · top-level statements (cognitive 37) · ×1
  • top-level statements (cognitive 37) src/Refit.NativeAotSmoke/Program.cs:9 — top-level statements has cognitive complexity 37 (threshold 15). Of this number, 34 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: InterfaceStubGenerator.Shared/RequestParameterParsing.cs src/InterfaceStubGenerator.Shared/RequestParameterParsing.cs — FileTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 65 over it, 1.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×1
  • Edited copy of a member (36 corresponding lines) src/InterfaceStubGenerator.Shared/InlineRequestEmission.cs:466 — src/InterfaceStubGenerator.Shared/InlineRequestEmission.cs:466-501 | src/InterfaceStubGenerator.Shared/InlineRequestEmission.cs:517-559 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (47 corresponding lines) · ×1
  • Edited copy of a member (47 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:27 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:27-73 | src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:130-180 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 37+ corresponding lines) src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:15 — src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:15-51 | src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:60-97 | src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:104-141 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×1
  • Edited copy of a member (32 corresponding lines) src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:200 — src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionCore.cs:200-238 | src/Refit.HttpClientFactory/HttpClientFactoryCore.cs:66-97 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×1
  • Edited copy of a member (34 corresponding lines) src/Refit/GeneratedRequestRunner.cs:101 — src/Refit/GeneratedRequestRunner.cs:101-134 | src/Refit/GeneratedRequestRunner.cs:243-276 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) src/Refit/GeneratedRequestRunner.cs:153 — src/Refit/GeneratedRequestRunner.cs:153-171 | src/Refit/GeneratedRequestRunner.cs:191-215 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 27+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 27+ corresponding lines) src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:399 — src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:399-427 | src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:440-469 | src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:488-514 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) src/InterfaceStubGenerator.Shared/InterfaceMemberParsing.cs:206 — src/InterfaceStubGenerator.Shared/InterfaceMemberParsing.cs:206-230 | src/InterfaceStubGenerator.Shared/MethodSignatureParsing.cs:201-228 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 30+ corresponding lines) src/Refit.Reflection/ReflectionPropertyHelpers.cs:19 — src/Refit.Reflection/ReflectionPropertyHelpers.cs:19-49 | src/Refit.Reflection/RequestBuilderImplementation.RequestBuilding.cs:280-309 | src/Refit.Reflection/RestMethodInfoInternal.cs:245-274 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) src/Refit.Reflection/RequestBuilderImplementation.Payload.cs:567 — src/Refit.Reflection/RequestBuilderImplementation.Payload.cs:567-602 | src/Refit/FormValueMultimap.cs:179-202 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 9+ corresponding lines) src/InterfaceStubGenerator.Shared/MultipartParameterParsing.cs:171 — src/InterfaceStubGenerator.Shared/MultipartParameterParsing.cs:171-179 | src/InterfaceStubGenerator.Shared/RequestParameterParsing.cs:582-595 | src/InterfaceStubGenerator.Shared/RequestParameterParsing.cs:979-987 | src/InterfaceStubGenerator.Shared/RequestParameterParsing.cs:998-1006 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×1
  • Edited copy of a member (17 corresponding lines) src/InterfaceStubGenerator.Shared/QueryValueEmission.cs:30 — src/InterfaceStubGenerator.Shared/QueryValueEmission.cs:30-53 | src/InterfaceStubGenerator.Shared/QueryValueEmission.cs:96-112 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) src/InterfaceStubGenerator.Shared/RequestParsing.cs:817 — src/InterfaceStubGenerator.Shared/RequestParsing.cs:817-839 | src/InterfaceStubGenerator.Shared/RequestParsing.cs:848-870 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) src/Refit/SystemTextJsonContentSerializer.cs:149 — src/Refit/SystemTextJsonContentSerializer.cs:149-167 | src/Refit/SystemTextJsonContentSerializer.JsonContext.cs:98-113 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 17+ corresponding lines) src/InterfaceStubGenerator.Shared/MultipartParameterParsing.cs:324 — src/InterfaceStubGenerator.Shared/MultipartParameterParsing.cs:324-340 | src/InterfaceStubGenerator.Shared/MultipartParameterParsing.cs:347-364 | src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs:131-147 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) src/InterfaceStubGenerator.Shared/QueryFormatterEmission.cs:18 — src/InterfaceStubGenerator.Shared/QueryFormatterEmission.cs:18-30 | src/InterfaceStubGenerator.Shared/QueryFormatterEmission.cs:85-96 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) src/Refit.Reflection/RestMethodInfoInternal.AttributeReading.cs:198 — src/Refit.Reflection/RestMethodInfoInternal.AttributeReading.cs:198-219 | src/Refit.Reflection/RestMethodInfoInternal.AttributeReading.cs:239-263 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) src/Refit.Reflection/RestMethodInfoInternal.AttributeReading.cs:115 — src/Refit.Reflection/RestMethodInfoInternal.AttributeReading.cs:115-143 | src/Refit.Reflection/RestMethodInfoInternal.ParameterBinding.cs:551-577 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×1
  • Edited copy of a member (5 corresponding lines) src/InterfaceStubGenerator.Shared/LiteralEmissionHelpers.cs:270 — src/InterfaceStubGenerator.Shared/LiteralEmissionHelpers.cs:270-274 | src/InterfaceStubGenerator.Shared/RequestPropertyEmission.cs:42-46 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) src/InterfaceStubGenerator.Shared/RequestParsing.cs:398 — src/InterfaceStubGenerator.Shared/RequestParsing.cs:398-403 | src/Refit.Analyzers.Shared/RefitInterfaceAnalyzer.cs:38-46 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (15–21 lines × 2) · ×1
  • Duplicated block (15–21 lines × 2) src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.Helpers.cs:95 — src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.Helpers.cs:95-115 | src/Refit/GeneratedRequestRunner.cs:506-520 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.Helpers.cs:95` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) src/InterfaceStubGenerator.Shared/MethodSignatureEmission.cs:31 — src/InterfaceStubGenerator.Shared/MethodSignatureEmission.cs:31-47 | src/InterfaceStubGenerator.Shared/MethodSignatureEmission.cs:108-124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) src/InterfaceStubGenerator.Shared/RequestParameterParsingHelpers.cs:116 — src/InterfaceStubGenerator.Shared/RequestParameterParsingHelpers.cs:116-131 | src/Refit.Reflection/RestMethodInfoInternal.PathPrefix.cs:18-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (4–11 lines × 3) · ×1
  • Duplicated block (4–11 lines × 3) src/InterfaceStubGenerator.Shared/QueryObjectEmission.cs:289 — src/InterfaceStubGenerator.Shared/QueryObjectEmission.cs:289-299 | src/InterfaceStubGenerator.Shared/QueryObjectEmission.cs:384-393 | src/InterfaceStubGenerator.Shared/QueryObjectEmission.cs:517-520 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/InterfaceStubGenerator.Shared/QueryObjectEmission.cs:289` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:24 — src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:24-31 | src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:69-76 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/InterfaceStubGenerator.Shared/ReflectionArgumentEmission.cs:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) src/examples/Documentation/Tooling/PolyfillSample.cs:40 — src/examples/Documentation/Tooling/PolyfillSample.cs:40-46 | src/examples/Documentation/Tooling/PolyfillSample.cs:67-73 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: Refit(net462) src/Refit/Refit.csproj:1 — Refit(net462): abstractness 0.16, instability 0.00, distance 0.84 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
P12 · CI test-gate honesty · Coverage collected but not gated · ×1
  • Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
X2 · Cancellation propagation · Async local function without CancellationToken · ×1
  • Async local function without CancellationToken: ProduceUploadRecordsAsync src/Refit.NativeAotSmoke/Program.cs:257 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
X2 · Cancellation propagation · Async delegate without CancellationToken · ×1
  • Async delegate without CancellationToken: ToStreamingHttpContent src/Refit/SystemTextJsonContentSerializer.cs:151 — Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`).
X21 · Side-effecting pattern guard · Pattern guard mutates state while matching · ×1
  • Pattern guard mutates state while matching src/InterfaceStubGenerator.Shared/Parser.cs:598 — The `when` guard on line 598 changes `(seenInheritedProperties ??= [with(comparer: SymbolEqualityComparer.Default)])` with `(seenInheritedProperties ??= [with(comparer: SymbolEqualityComparer.Default)]).Add(property)` while deciding whether its arm matches. A guard answers "does this arm apply?" and the runtime evaluates it during PATTERN MATCHING — so the change lands on arms that are then NOT selected, and `&&` short-circuits, so it is skipped altogether whenever the operand to its left already decides the answer. The accounting therefore depends on evaluation order and on how many labels the subject was compared against, not on any statement a reader can point at: the update is missed on exactly the path the left operand rules out, so a counter kept this way cannot reach a limit it is checked against on that path. Move the change out of the guard — leave the clause reading only (test the state without changing it: a peek, a lookup, a count) and make the call in the arm's BODY, where it runs precisely when the arm is chosen, or hoist it above the switch if it must happen for every subject.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) src/Refit.Reflection/RequestBuilderImplementation.cs:395 — 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.
Minor — 33 finding(s)
D24 · Comment Value · redundant comment · ×8
  • redundant comment src/InterfaceStubGenerator.Shared/SharedInfrastructureEmission.cs:49 — "add the attribute text" repeats the code it sits on: 3 of its 3 words (add, attribute, text) are already in `addSource("PreserveAttribute.g.cs", SourceText.From(attributeText, Encoding.UTF8));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs:388 — "Add RefitSetting.HttpRequestMessageOptions to the HttpRequestMessage" repeats the code it sits on: 6 of its 7 words (add, setting, http, request, message, options) are already in `if (_settings.HttpRequestMessageOptions is not null)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Refit/ValueStringBuilder.cs:361 — "same as Array.MaxLength" repeats the code it sits on: 3 of its 3 words (array, max, length) are already in `const uint ArrayMaxLength = 0x7FFFFFC7; // same as Array.MaxLength`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/benchmarks/Refit.Benchmarks/IGitHubService.cs:59 — "Task<HttpResponseMessage>" repeats the code it sits on: 4 of its 4 words (task, http, response, message) are already in `[Get("/users")]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/benchmarks/Refit.Benchmarks/IGitHubService.cs:72 — "IObservable<HttpResponseMessage>" repeats the code it sits on: 4 of its 4 words (observable, http, response, message) are already in `[Get("/users")]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/benchmarks/Refit.Benchmarks/IGitHubService.cs:98 — "Task<ApiResponse<T>>" repeats the code it sits on: 3 of its 3 words (task, api, response) are already in `[Get("/users")]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/tests/Refit.Tests/MultipartTests.cs:392 — "get calling assembly" repeats the code it sits on: 3 of its 3 words (get, calling, assembly) are already in `var assembly = System.Reflection.Assembly.GetCallingAssembly();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/tests/Refit.Tests/RestServiceIntegrationTests.cs:566 — "get calling assembly" repeats the code it sits on: 3 of its 3 words (get, calling, assembly) are already in `var assembly = System.Reflection.Assembly.GetCallingAssembly();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
X10 · Duplicated predicate · Duplicated predicate · ×7
  • Duplicated predicate src/InterfaceStubGenerator.Shared/RequestParsing.cs:400 — `!arguments.IsEmpty && arguments[0].Value is string path` appears character-identically in 2 files — src/InterfaceStubGenerator.Shared/RequestParsing.cs, src/Refit.Analyzers.Shared/RefitInterfaceAnalyzer.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/InterfaceStubGenerator.Shared/InterfaceMemberParsing.cs:117 — `!arguments.IsEmpty && arguments[0].Value is string { Length: > 0 } key` appears character-identically in 2 files — src/InterfaceStubGenerator.Shared/InterfaceMemberParsing.cs, src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/InterfaceStubGenerator.Shared/Parser.cs:787 — `member is IMethodSymbol method && IsRefitMethod(method, httpMethodAttribute)` appears character-identically in 2 files — src/InterfaceStubGenerator.Shared/Parser.cs, src/Refit.Analyzers.Shared/RefitInterfaceAnalyzer.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs:329 — `method == HttpMethod.Get || method == HttpMethod.Head` appears character-identically in 2 files — src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs, src/Refit/GeneratedRequestRunner.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs:134 — `queryParamsToAdd is not null && queryParamsToAdd.Count != 0` appears character-identically in 2 files — src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.cs, src/Refit.Reflection/RequestBuilderImplementation.RequestBuilding.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.Helpers.cs:107 — `request.Content is not null && HttpHeaderApplier.ContainsHeader(request.Content.Headers, name)` appears character-identically in 2 files — src/Refit.Reflection/RequestBuilderImplementation.QueryAndHeaders.Helpers.cs, src/Refit/GeneratedRequestRunner.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Refit/GeneratedRequestRunner.BodyContent.cs:83 — `streamBody && !UsesSynchronousSerialization(settings)` appears character-identically in 2 files — src/Refit/GeneratedRequestRunner.BodyContent.cs, src/Refit/GeneratedRequestRunner.JsonTypeInfo.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
S1 · Web-Security Posture · No security response headers detected · ×2
  • No security response headers detected — 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.)
  • No security response headers detected src/examples/SampleUsingLocalApi/RestApiforTest/Program.cs:26 — 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.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×2
  • No app-layer HTTPS enforcement detected — No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • No app-layer HTTPS enforcement detected src/examples/SampleUsingLocalApi/RestApiforTest/Program.cs:26 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IGitHubService (16 members) src/benchmarks/Refit.Benchmarks/IGitHubService.cs:9 — `IGitHubService` declares 16 members: `GetUsersTaskAsync`, `PostUsersTaskAsync`, `GetUsersTaskStringAsync`, `PostUsersTaskStringAsync`, `GetUsersTaskStreamAsync`, `PostUsersTaskStreamAsync`, `GetUsersTaskHttpContentAsync`, `PostUsersTaskHttpContentAsync`, `GetUsersTaskHttpResponseMessageAsync`, `PostUsersTaskHttpResponseMessageAsync`, `GetUsersObservableHttpResponseMessage`, `PostUsersObservableHttpResponseMessage`, `GetUsersTaskTAsync`, `PostUsersTaskTAsync`, `GetUsersTaskApiResponseTAsync`, `PostUsersTaskApiResponseTAsync`. 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. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 39 significant file(s) lose their only recent owner: src/InterfaceStubGenerator.Shared/RequestParameterParsing.cs, src/InterfaceStubGenerator.Shared/RequestParsing.cs, src/Refit.Reflection/RestMethodInfoInternal.cs, src/InterfaceStubGenerator.Shared/RequestParameterKindParsing.cs, src/Refit.Reflection/RestMethodInfoInternal.ParameterBinding.cs, src/InterfaceStubGenerator.Shared/InterfaceStubGeneratorV2.cs, src/Refit/ApiException.cs, src/InterfaceStubGenerator.Shared/MultipartParameterParsing.cs (+31 more). Pair on, review, or document these before any departure.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — 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.
M4 · Documentation accuracy · README/code drift · ×1
  • README/code drift README.md:88 — README.md names .NET 8, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
P12 · CI test-gate honesty · Sleep-based test synchronization · ×1
  • Sleep-based test synchronization — 6 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 2/68 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 68, 8 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 56/237 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.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions override nullable warnings · ×1
  • Null-forgiving operator (`!`) suppressions override nullable warnings — ~2.0 `!` suppressions per 1k syntax nodes — 422 suppression(s) across the 213361 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.
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • Silent fallback default in catch src/Refit/HttpHeaderApplier.cs:68 — `ContainsHeader` swallows `InvalidOperationException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×1
  • Silent fallback default on parse failure src/examples/SampleUsingLocalApi/ConsoleApplication/Program.cs:50 — `Main` falls back to `InvalidOption` when `int.TryParse(line, out var option)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Minor — 21 finding(s)
D24 · Comment Value · doc comments repeat the names · ×21
  • doc comments repeat the names src/InterfaceStubGenerator.Shared/BodyContentEmission.cs:245 — 58 of 1860 documented parameters and 8 of 989 summaries in `InterfaceStubGenerator.Roslyn48` only repeat the member or parameter name (e.g. "The explicit name literal, or ." for `explicitNameLiteral`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Refit/AliasAsAttribute.cs:8 — 109 of 984 documented parameters and 30 of 933 summaries in `Refit(net462)` only repeat the member or parameter name (e.g. "The name." for `name`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Refit.Analyzers.Shared/FallbackExplanation.cs:50 — 9 of 111 documented parameters and 0 of 80 summaries in `Refit.Analyzers.Roslyn48` only repeat the member or parameter name (e.g. "The method's HTTP method attribute." for `httpMethodAttribute`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/tests/Refit.Analyzers.Tests/AnalyzerFixture.cs:220 — 2 of 31 documented parameters and 0 of 54 summaries in `Refit.Analyzers.Tests(net10.0)` only repeat the member or parameter name (e.g. "The option key." for `optionKey`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/benchmarks/Refit.Benchmarks/FormBenchmarkModel.cs:19 — 2 of 54 documented parameters and 9 of 525 summaries in `Refit.Benchmarks(net10.0)` only repeat the member or parameter name (e.g. "Gets or sets the email." for `Email`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Refit.CodeFixes.Shared/RefitInterfaceCodeFixProvider.cs:77 — 2 of 6 documented parameters and 0 of 6 summaries in `Refit.CodeFixes.Roslyn48` only repeat the member or parameter name (e.g. "The cancellation token." for `cancellationToken`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/tests/Refit.CodeFixes.Tests/CodeFixFixture.cs:167 — 1 of 11 documented parameters and 1 of 21 summaries in `Refit.CodeFixes.Tests(net10.0)` only repeat the member or parameter name (e.g. "The diagnostic ID." for `diagnosticId`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/tests/Refit.GeneratedCode.TestModels/Scenarios/IGeneratedUserApi.cs:13 — 1 of 38 documented parameters and 2 of 30 summaries in `Refit.GeneratedCode.TestModels(net10.0)` only repeat the member or parameter name (e.g. "Gets a user." for `GetUserAsync`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/benchmarks/Refit.Generator.Benchmarks/PathHeaderBindingGenerationBenchmarks.cs:48 — 0 of 10 documented parameters and 2 of 115 summaries in `Refit.Generator.Benchmarks(net10.0)` only repeat the member or parameter name (e.g. "The path-only compilation." for `_pathOnlyCompilation`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/tests/Refit.GeneratorTests/GeneratedRequestBuildingFallbackReasonTests.cs:314 — 28 of 461 documented parameters and 14 of 1138 summaries in `Refit.GeneratorTests(net10.0)` only repeat the member or parameter name (e.g. "The method name." for `methodName`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Polyfills/DynamicallyAccessedMemberTypes.cs:25 — 3 of 84 documented parameters and 15 of 154 summaries in `Refit.HttpClientFactory(net462)` only repeat the member or parameter name (e.g. "The public parameterless constructor." for `PublicParameterlessConstructor`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Refit.HttpClientFactory.Reflection/HttpClientFactoryReflectionExtensions.HttpClientBuilder.cs:17 — 16 of 82 documented parameters and 0 of 44 summaries in `Refit.HttpClientFactory.Reflection(net462)` only repeat the member or parameter name (e.g. "The type of the Refit interface." for `refitInterfaceType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Refit.NativeAotPackageSmoke/Check.cs:11 — 1 of 29 documented parameters and 0 of 39 summaries in `Refit.NativeAotPackageSmoke` only repeat the member or parameter name (e.g. "The expected value." for `expected`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/tests/Refit.Newtonsoft.Json.Tests/NewtonsoftJsonSecurityTests.cs:113 — 0 of 62 documented parameters and 3 of 196 summaries in `Refit.Newtonsoft.Json.Tests(net10.0)` only repeat the member or parameter name (e.g. "Gets or sets the name." for `Name`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Refit.Reflection/GeneratedTypeResolver.cs:11 — 11 of 502 documented parameters and 4 of 334 summaries in `Refit.Reflection(net462)` only repeat the member or parameter name (e.g. "The Refit interface type." for `refitInterfaceType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/benchmarks/Refit.Reflection.Benchmarks/IReflectionRequestService.cs:30 — 4 of 29 documented parameters and 8 of 277 summaries in `Refit.Reflection.Benchmarks(net10.0)` only repeat the member or parameter name (e.g. "The status." for `status`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/tests/Refit.Reflection.Tests/ICompressedBodyApi.cs:12 — 4 of 63 documented parameters and 0 of 211 summaries in `Refit.Reflection.Tests(net10.0)` only repeat the member or parameter name (e.g. "The body value." for `body`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Refit.Testing/StreamSource.cs:255 — 2 of 152 documented parameters and 1 of 242 summaries in `Refit.Testing(net462)` only repeat the member or parameter name (e.g. "The item." for `item`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/tests/Refit.Testing.Tests/IUserApi.cs:16 — 0 of 102 documented parameters and 1 of 293 summaries in `Refit.Testing.Tests(net10.0)` only repeat the member or parameter name (e.g. "Creates a user." for `CreateUser`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/tests/Refit.Tests/Address.cs:13 — 46 of 1089 documented parameters and 78 of 3605 summaries in `Refit.Tests(net10.0)` only repeat the member or parameter name (e.g. "Gets the street value." for `Street`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Refit.Xml/XmlContentSerializer.cs:26 — 5 of 8 documented parameters and 6 of 24 summaries in `Refit.Xml(net462)` only repeat the member or parameter name (e.g. "The settings." for `settings`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-aea074677c4647be9ce87a5f101a2a53/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-aea074677c4647be9ce87a5f101a2a53/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .10artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—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 scan0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 91 file(s) — `src/InterfaceStubGenerator.Shared/BodyContentEmission.cs`, `src/InterfaceStubGenerator.Shared/Emitter.cs`, `src/InterfaceStubGenerator.Shared/FormFieldEmission.cs`, `src/InterfaceStubGenerator.Shared/InlineRequestEmission.cs`, `src/InterfaceStubGenerator.Shared/IsExternalInit.cs`, … (+86 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-71183ef3407c45dfa143bbb12c0a73ac0artifacts/raw/osv-scanner.json

Run 01a1cd47-cb41-7c25-9403-fddeaffbe9f1 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 6 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Name — 4 field(s)
  • FormBenchmarkModel.FirstName src/benchmarks/Refit.Benchmarks/FormBenchmarkModel.cs:13
  • FormBenchmarkModel.LastName src/benchmarks/Refit.Benchmarks/FormBenchmarkModel.cs:17
  • ContactForm.FullName src/examples/Documentation/Bodies/ContactForm.cs:11
  • GitHubRepo.FullName src/examples/Documentation/Paging/GitHubRepo.cs:14
Email — 2 field(s)
  • FormBenchmarkModel.Email src/benchmarks/Refit.Benchmarks/FormBenchmarkModel.cs:20
  • ReflectionUserModel.Email src/benchmarks/Refit.Reflection.Benchmarks/ReflectionUserModel.cs:18

Downloadable artifacts

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

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