Public report of FastEndpoints/FastEndpoints, published 22 October 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 reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog 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, 22 October 2026, 05:35 UTC · Survey ID cd_3afc3403c3ba487883c40a4c0026292d
FastEndpoints/FastEndpoints
Measured 22 October 2026, 05:26 UTC, at code version 5eadfd9
Code coverage is not measured: No coverage collector is wired up.
Test reliability is not measured: No test run produced results.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
IL efficiency is not measured: The target did not build.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 2 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: 51,172 lines of product code in 82 projects, tests not counted · Estimated rebuild effort: about 1.1 person-years · Weakest lens: Security and Compliance, 43
Findings by how serious they are
70 critical447 serious143 minor
4 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 05:26 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 Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸
74of 79 dimensions measured by tools. The other 5 are advisory notes from an AI model, which explain the code but don't count towards the score.
628of 660 findings point to an exact file and line, so you can open each one in the code. The other 32 concern the repository as a whole, such as missing documentation.
79dimensions across 6 lenses, read from 51,172 lines of product code in 82 projects.
FastEndpoints/FastEndpoints scores 48 out of 100 and is rated Weak, while four of its six lenses score higher still: Architecture at 90 and Performance at 73, both rated Strong, Maturity at 58, rated Adequate, and Code Health at 49, rated Weak.
The score is lower than those four because the weakest lens counts most, and here that is Security and Compliance, which scores 43 and is rated Weak. Its Supply-chain Provenance & Signing dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to resolve the 1 Vulnerable finding(s) in Dependency Hygiene and to resolve the 4 REDACTED finding(s) in Static Analysis (SAST), and if Security and Compliance rose to 70, the score would rise from 48 to about 53.
70 findings are critical: 60 in Explicit Debt, five in Static Analysis (SAST), two in Dependency Vulnerabilities, one in Dependency Hygiene, one in Secret Scanning and one in Secrets (history).
Watchdog couldn't measure Schema migrations in this code, so that dimension is left out of the score. The product code is 51,172 lines, which would take an estimated 1.1 person-years, around €170,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 forThe 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.
Async correctness · Blocking `SemaphoreSlim.Wait` inside an `async` method Src/JobQueues/JobQueue.cs
Async correctness · Blocking `SemaphoreSlim.Wait` inside an `async` method Src/Messaging/Messaging.Remote.Core/Client/Events/EventExecutorWorker.cs
Async correctness · Blocking `SemaphoreSlim.Wait` inside an `async` method Src/Messaging/Messaging.Remote/Server/Events/HubContext.cs
Async correctness · Sync-over-async (deadlock risk) through `.Result` Src/Testing/AppFixture.Aot.cs
Cancellation propagation · Async method without CancellationToken: WriteJson Src/HealthChecks/ServiceHealthChecksStartupFilter.cs
Cancellation propagation · Async method without CancellationToken: OkAsync Src/Library/Endpoint/Endpoint.Send.cs
Cancellation propagation · Async method without CancellationToken: SendError Src/Library/Middleware/FinancialIdempotency/FinancialIdempotencyMiddleware.cs
Cancellation propagation · Async local function without CancellationToken: DrainExecutionsAsync Src/Messaging/Messaging.Remote.Core/Client/Events/EventExecutorWorker.cs
Exception handling · Swallowed exception (caught, then discarded) Src/JobQueues/JobQueue.cs
Incompleteness & stubs · Hollow method — returns a constant without doing the work TestHarness/Web/[Features]/Customers/[EventHandlers]/SendOrderConfirmation.cs
Watchdog compares 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: 16 findings
These 16 critical or serious findings were in the previous survey, on 7 October 2026, and are gone from this one.
Coupling · Off the main sequence: FastEndpoints.OpenApi.Kiota
Coupling · Off the main sequence: FastEndpoints.Attributes(netstandard2.0)
Coupling · Off the main sequence: FastEndpoints.OpenApi
Exception handling · Swallowed exception (caught, then discarded) Src/Swagger/Extensions.cs
Exception handling · Swallowed exception (caught, then discarded) Src/Swagger/SystemTextJsonUtilities.cs
Rebuild cost: about €170,000 · Estimate
Cost to rebuild
€54,000 to €280,000, for 902 to 2,915 hours of work, about 1.1 person-years for 1 to 3 engineers
Difficulty of the problem
High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 51,172 lines of product code, of which 37% is declarations and boilerplate, 20% straight logic and 43% logic with branches
Comment lines
The estimate prices 42,016 lines. Comment lines count towards the size of 51,172 lines but aren't priced as work.
How the estimate is made: Watchdog prices 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
Resolve the 1 Vulnerable finding(s) in Dependency Hygiene.
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 3 points · Low effort · Secret Scanning
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 €170,000 to build again, about 1.1 person-years of work. Its weakest lens is Security and Compliance, at 43 (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
Resolve the 1 Vulnerable finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for low effort, because it clears the 1 Dependency Hygiene findings. 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.
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.
143 modules, with 130 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 103 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
Customers.Create uses FastEndpoints, so a change to FastEndpoints can break Customers.Create, while a change to Customers.Create can't break FastEndpoints.
Position
Below the diagonal: Customers.Create uses a module listed above it, which is the healthy direction.
Customers.Create uses Web.Services, so a change to Web.Services can break Customers.Create, while a change to Customers.Create can't break Web.Services.
Position
Below the diagonal: Customers.Create uses a module listed above it, which is the healthy direction.
Customers.CreateWithPropertiesDI uses FastEndpoints, so a change to FastEndpoints can break Customers.CreateWithPropertiesDI, while a change to Customers.CreateWithPropertiesDI can't break FastEndpoints.
Position
Below the diagonal: Customers.CreateWithPropertiesDI uses a module listed above it, which is the healthy direction.
Customers.CreateWithPropertiesDI uses Web.Services, so a change to Web.Services can break Customers.CreateWithPropertiesDI, while a change to Customers.CreateWithPropertiesDI can't break Web.Services.
Position
Below the diagonal: Customers.CreateWithPropertiesDI uses a module listed above it, which is the healthy direction.
Customers.EventHandlers uses FastEndpoints, so a change to FastEndpoints can break Customers.EventHandlers, while a change to Customers.EventHandlers can't break FastEndpoints.
Position
Below the diagonal: Customers.EventHandlers uses a module listed above it, which is the healthy direction.
Customers.EventHandlers uses Web.SystemEvents, so a change to Web.SystemEvents can break Customers.EventHandlers, while a change to Customers.EventHandlers can't break Web.SystemEvents.
Position
Below the diagonal: Customers.EventHandlers uses a module listed above it, which is the healthy direction.
Customers.List.Recent uses FastEndpoints, so a change to FastEndpoints can break Customers.List.Recent, while a change to Customers.List.Recent can't break FastEndpoints.
Position
Below the diagonal: Customers.List.Recent uses a module listed above it, which is the healthy direction.
Customers.Login uses FastEndpoints, so a change to FastEndpoints can break Customers.Login, while a change to Customers.Login can't break FastEndpoints.
Position
Below the diagonal: Customers.Login uses a module listed above it, which is the healthy direction.
Customers.Update uses FastEndpoints, so a change to FastEndpoints can break Customers.Update, while a change to Customers.Update can't break FastEndpoints.
Position
Below the diagonal: Customers.Update uses a module listed above it, which is the healthy direction.
Customers.UpdateWithHeader uses FastEndpoints, so a change to FastEndpoints can break Customers.UpdateWithHeader, while a change to Customers.UpdateWithHeader can't break FastEndpoints.
Position
Below the diagonal: Customers.UpdateWithHeader uses a module listed above it, which is the healthy direction.
FastEndpoints.Agents uses FastEndpoints, so a change to FastEndpoints can break FastEndpoints.Agents, while a change to FastEndpoints.Agents can't break FastEndpoints.
Position
Below the diagonal: FastEndpoints.Agents uses a module listed above it, which is the healthy direction.
FastEndpoints.OData uses FastEndpoints, so a change to FastEndpoints can break FastEndpoints.OData, while a change to FastEndpoints.OData can't break FastEndpoints.
Position
Below the diagonal: FastEndpoints.OData uses a module listed above it, which is the healthy direction.
FastEndpoints.OpenApi uses FastEndpoints, so a change to FastEndpoints can break FastEndpoints.OpenApi, while a change to FastEndpoints.OpenApi can't break FastEndpoints.
Position
Below the diagonal: FastEndpoints.OpenApi uses a module listed above it, which is the healthy direction.
FastEndpoints.OpenApi uses FastEndpoints.OpenApi.ValidationProcessor, so a change to FastEndpoints.OpenApi.ValidationProcessor can break FastEndpoints.OpenApi, while a change to FastEndpoints.OpenApi can't break FastEndpoints.OpenApi.ValidationProcessor.
Position
Below the diagonal: FastEndpoints.OpenApi uses a module listed above it, which is the healthy direction.
FastEndpoints.Security uses FastEndpoints, so a change to FastEndpoints can break FastEndpoints.Security, while a change to FastEndpoints.Security can't break FastEndpoints.
Position
Below the diagonal: FastEndpoints.Security uses a module listed above it, which is the healthy direction.
FastEndpoints.Swagger uses FastEndpoints, so a change to FastEndpoints can break FastEndpoints.Swagger, while a change to FastEndpoints.Swagger can't break FastEndpoints.
Position
Below the diagonal: FastEndpoints.Swagger uses a module listed above it, which is the healthy direction.
FastEndpoints.Swagger uses FastEndpoints.Swagger.ValidationProcessor, so a change to FastEndpoints.Swagger.ValidationProcessor can break FastEndpoints.Swagger, while a change to FastEndpoints.Swagger can't break FastEndpoints.Swagger.ValidationProcessor.
Position
Below the diagonal: FastEndpoints.Swagger uses a module listed above it, which is the healthy direction.
Inventory.GetProduct uses FastEndpoints, so a change to FastEndpoints can break Inventory.GetProduct, while a change to Inventory.GetProduct can't break FastEndpoints.
Position
Below the diagonal: Inventory.GetProduct uses a module listed above it, which is the healthy direction.
Inventory.List.Recent uses FastEndpoints, so a change to FastEndpoints can break Inventory.List.Recent, while a change to Inventory.List.Recent can't break FastEndpoints.
Position
Below the diagonal: Inventory.List.Recent uses a module listed above it, which is the healthy direction.
Inventory.Manage.Create uses FastEndpoints, so a change to FastEndpoints can break Inventory.Manage.Create, while a change to Inventory.Manage.Create can't break FastEndpoints.
Position
Below the diagonal: Inventory.Manage.Create uses a module listed above it, which is the healthy direction.
Inventory.Manage.Delete uses FastEndpoints, so a change to FastEndpoints can break Inventory.Manage.Delete, while a change to Inventory.Manage.Delete can't break FastEndpoints.
Position
Below the diagonal: Inventory.Manage.Delete uses a module listed above it, which is the healthy direction.
Inventory.Manage.Update uses FastEndpoints, so a change to FastEndpoints can break Inventory.Manage.Update, while a change to Inventory.Manage.Update can't break FastEndpoints.
Position
Below the diagonal: Inventory.Manage.Update uses a module listed above it, which is the healthy direction.
NativeAotChecker.Endpoints.Binding uses FastEndpoints, so a change to FastEndpoints can break NativeAotChecker.Endpoints.Binding, while a change to NativeAotChecker.Endpoints.Binding can't break FastEndpoints.
Position
Below the diagonal: NativeAotChecker.Endpoints.Binding uses a module listed above it, which is the healthy direction.
NativeAotChecker.Endpoints.CommandRules uses FastEndpoints, so a change to FastEndpoints can break NativeAotChecker.Endpoints.CommandRules, while a change to NativeAotChecker.Endpoints.CommandRules can't break FastEndpoints.
Position
Below the diagonal: NativeAotChecker.Endpoints.CommandRules uses a module listed above it, which is the healthy direction.
32 pairs of types, where a type in NativeAotChecker.Endpoints.Commands uses a type in FastEndpoints. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
NativeAotChecker.Endpoints.Commands uses FastEndpoints, so a change to FastEndpoints can break NativeAotChecker.Endpoints.Commands, while a change to NativeAotChecker.Endpoints.Commands can't break FastEndpoints.
Position
Below the diagonal: NativeAotChecker.Endpoints.Commands uses a module listed above it, which is the healthy direction.
NativeAotChecker.Endpoints.Events uses FastEndpoints, so a change to FastEndpoints can break NativeAotChecker.Endpoints.Events, while a change to NativeAotChecker.Endpoints.Events can't break FastEndpoints.
Position
Below the diagonal: NativeAotChecker.Endpoints.Events uses a module listed above it, which is the healthy direction.
NativeAotChecker.Endpoints.Jobs uses FastEndpoints, so a change to FastEndpoints can break NativeAotChecker.Endpoints.Jobs, while a change to NativeAotChecker.Endpoints.Jobs can't break FastEndpoints.
Position
Below the diagonal: NativeAotChecker.Endpoints.Jobs uses a module listed above it, which is the healthy direction.
NativeAotChecker.Endpoints.Json uses FastEndpoints, so a change to FastEndpoints can break NativeAotChecker.Endpoints.Json, while a change to NativeAotChecker.Endpoints.Json can't break FastEndpoints.
Position
Below the diagonal: NativeAotChecker.Endpoints.Json uses a module listed above it, which is the healthy direction.
NativeAotChecker.Endpoints.Mapping uses FastEndpoints, so a change to FastEndpoints can break NativeAotChecker.Endpoints.Mapping, while a change to NativeAotChecker.Endpoints.Mapping can't break FastEndpoints.
Position
Below the diagonal: NativeAotChecker.Endpoints.Mapping uses a module listed above it, which is the healthy direction.
NativeAotChecker.Endpoints.Processors uses FastEndpoints, so a change to FastEndpoints can break NativeAotChecker.Endpoints.Processors, while a change to NativeAotChecker.Endpoints.Processors can't break FastEndpoints.
Position
Below the diagonal: NativeAotChecker.Endpoints.Processors uses a module listed above it, which is the healthy direction.
Shipping.EventHandlers uses FastEndpoints, so a change to FastEndpoints can break Shipping.EventHandlers, while a change to Shipping.EventHandlers can't break FastEndpoints.
Position
Below the diagonal: Shipping.EventHandlers uses a module listed above it, which is the healthy direction.
Shipping.EventHandlers uses Web.SystemEvents, so a change to Web.SystemEvents can break Shipping.EventHandlers, while a change to Shipping.EventHandlers can't break Web.SystemEvents.
Position
Below the diagonal: Shipping.EventHandlers uses a module listed above it, which is the healthy direction.
TestCases.CommandBusTest uses FastEndpoints, so a change to FastEndpoints can break TestCases.CommandBusTest, while a change to TestCases.CommandBusTest can't break FastEndpoints.
Position
Below the diagonal: TestCases.CommandBusTest uses a module listed above it, which is the healthy direction.
TestCases.CommandBusTest uses Web.Services, so a change to Web.Services can break TestCases.CommandBusTest, while a change to TestCases.CommandBusTest can't break Web.Services.
Position
Below the diagonal: TestCases.CommandBusTest uses a module listed above it, which is the healthy direction.
TestCases.EventHandlingTest uses FastEndpoints, so a change to FastEndpoints can break TestCases.EventHandlingTest, while a change to TestCases.EventHandlingTest can't break FastEndpoints.
Position
Below the diagonal: TestCases.EventHandlingTest uses a module listed above it, which is the healthy direction.
FastEndpoints.A2A uses FastEndpoints, so a change to FastEndpoints can break FastEndpoints.A2A, while a change to FastEndpoints.A2A can't break FastEndpoints.
Position
Below the diagonal: FastEndpoints.A2A uses a module listed above it, which is the healthy direction.
FastEndpoints.A2A uses FastEndpoints.Agents, so a change to FastEndpoints.Agents can break FastEndpoints.A2A, while a change to FastEndpoints.A2A can't break FastEndpoints.Agents.
Position
Below the diagonal: FastEndpoints.A2A uses a module listed above it, which is the healthy direction.
FastEndpoints.Mcp uses FastEndpoints, so a change to FastEndpoints can break FastEndpoints.Mcp, while a change to FastEndpoints.Mcp can't break FastEndpoints.
Position
Below the diagonal: FastEndpoints.Mcp uses a module listed above it, which is the healthy direction.
FastEndpoints.Mcp uses FastEndpoints.Agents, so a change to FastEndpoints.Agents can break FastEndpoints.Mcp, while a change to FastEndpoints.Mcp can't break FastEndpoints.Agents.
Position
Below the diagonal: FastEndpoints.Mcp uses a module listed above it, which is the healthy direction.
Sales.Orders.Create uses FastEndpoints, so a change to FastEndpoints can break Sales.Orders.Create, while a change to Sales.Orders.Create can't break FastEndpoints.
Position
Below the diagonal: Sales.Orders.Create uses a module listed above it, which is the healthy direction.
Sales.Orders.Create uses Web.Services, so a change to Web.Services can break Sales.Orders.Create, while a change to Sales.Orders.Create can't break Web.Services.
Position
Below the diagonal: Sales.Orders.Create uses a module listed above it, which is the healthy direction.
Sales.Orders.Create uses TestCases.EventHandlingTest, so a change to TestCases.EventHandlingTest can break Sales.Orders.Create, while a change to Sales.Orders.Create can't break TestCases.EventHandlingTest.
Position
Below the diagonal: Sales.Orders.Create uses a module listed above it, which is the healthy direction.
TestCases.RefreshTokensTest uses FastEndpoints, so a change to FastEndpoints can break TestCases.RefreshTokensTest, while a change to TestCases.RefreshTokensTest can't break FastEndpoints.
Position
Below the diagonal: TestCases.RefreshTokensTest uses a module listed above it, which is the healthy direction.
TestCases.RefreshTokensTest uses FastEndpoints.Security, so a change to FastEndpoints.Security can break TestCases.RefreshTokensTest, while a change to TestCases.RefreshTokensTest can't break FastEndpoints.Security.
Position
Below the diagonal: TestCases.RefreshTokensTest uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 49% · Weak · gated by D17 ·
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 category
Findings
Severity
A05:2025 — Injection
13
High / Critical
A03:2025 — Software Supply Chain Failures
9
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
Immediately encrypt sensitive data at rest and resolve the single vulnerable dependency and leaked secret in REDACTED to secure core assets. Re-enable token audience validation by supplying the correct values rather than disabling the check, ensuring only legitimate tokens are accepted. Finally, integrate a SAST step into the CI pipeline to automatically block security regressions before they reach production.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Vulnerable finding(s) in Dependency Hygiene.
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.).
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 — 70
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 — 447
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 — 143
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 4
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
Watchdog 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. 74 of 79 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 79 dimensions across the health lenses
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
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, 628 of 660 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.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (107 contributor(s) across 3563 commit(s) sampled, automation and bot accounts excluded). One of them holds 84% of the history; the other 106 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
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 — Watchdog 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 (51,172 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 — Watchdog 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. `Benchmark/FastEndpointsBench/CodeGenEndpoint.cs`, `Src/Agents/A2A/A2ASkillCatalog.cs`, `Src/Agents/A2A/A2ASkillDispatcher.cs`, `Src/Agents/A2A/AgentCardBuilder.cs`, `Src/Agents/Mcp/EndpointMcpToolSource.cs`, … (+115 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.
D39 IL Efficiency — 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. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 50 further occurrence(s) are not listed individually; the score already reflects all 90.
P8 Schema migrations — not measured this run — Watchdog 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. Every other migration runner — DbUp, FluentMigrator, Evolve, Flyway, Liquibase, RoundhousE, a hand-rolled versioned-SQL runner — is invisible to the detector, so an absence here is our blind spot rather than a missing migration strategy in the repository. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool other than EF Core migrations, naming it lets us teach the detector to read it.
X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 86 further occurrence(s) are not listed individually; the score already reflects all 126.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
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.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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.
The LLM boundary
LLM-set scores this run (5): D19, D21, D24, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
42 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Md5.ComputeHash at 71. A further 4 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 OperationSchemaHelpers.CloneSchemaMemberValue at 22 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Src/OpenApi/Schemas/OpenApiSchemaExtensions.cs (OperationSchemaHelpers.CloneSchemaMemberValue at 22), Src/OpenApi/Schemas/OpenApiTypeSchemaFactory.cs (OperationSchemaHelpers.TryCreatePrimitiveSchema at 21), Src/Library/Extensions/ReflectionExtensions.cs (.IsComplexType at 19). 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.
+ 37 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with Md5.ComputeHash (cyclomatic 71). — Refactoring it lifts Cyclomatic Complexity from 6.4 to about 6.5/10.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 81 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with EndpointRouteMapper.Map (cognitive 82), EventExecutorWorker.RunAsync (cognitive 67), TypeInfo.TypeInfo.ctor (cognitive 62). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 6.1 to about 6.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.9 / 10Strong✓ 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.
Resolve the 6 TooManyMethods finding(s) in God Classes — start with REDACTED, EndpointDefinition.cs, OpenApiSchemaExtensions.cs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 MethodTooLong finding(s) in God Classes — start with ComplexSourceBinder.cs, EventExecutorWorker.cs, DocumentRegistration.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 FileTooLong finding(s) in God Classes — start with Endpoints.cs, OperationProcessor.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
23 duplicated block group(s) detected. 3 of the 23 are in trees this repository does not ship — vendored, example/demo, 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.
+ 10 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with LoggingExtensions.cs, SchemaNameGenerator.cs, Program.TypeResolution.cs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with JobQueue.cs, AgentRequestBuilder.cs, AccessControlGenerator.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with X402Middleware.cs, Models.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
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.
Resolve the 1 Unstable project FastEndpoints.Generator finding(s) in Coupling — start with FastEndpoints.Generator.csproj. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
2542 test methods: 2542 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Stronggated by 1 serious finding✓ 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.
0 skipped, 1 zero-assertion, 1 mock references across 1316 tests.
No assertions: VoidTests/IntegrationTests/FastEndpoints/RPCTests/VoidCommand.cs:5
Mock framework: FakeItEasy
What to do
Resolve the 1 No assertions finding(s) in Test Quality — start with VoidCommand.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
Resolve the 1 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 issue-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 of 249 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 43 direct `PackageReference`(s), and 212 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
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.
Resolve the 9 Hotspot finding(s) in Churn × Complexity Hotspots — start with OperationTransformer.Requests.cs, REDACTED, ComplexSourceBinder.cs. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
NoWarnInCsproj repeated across 13 files · ×2TestHarness/OpenApi.Kiota/OpenApi.Kiota.csproj:9
+ 10 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 25 FileScopedPragmaDisable finding(s) in Explicit Debt — start with REDACTED (3), Benchmarks.cs, CommandHandlerBenchmarks.cs. — One of this dimension's main actionable groups (25 issue-level).
Resolve the 18 EmptyCatchBlock finding(s) in Explicit Debt — start with AppFixture.Aot.cs (3), X402FacilitatorClient.cs (2), REDACTED (2). — One of this dimension's main actionable groups (18 issue-level).
Resolve the 10 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (2), OpenApi.Kiota.csproj (2), Web.csproj. — One of this dimension's main actionable groups (10 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
82 projects, 2008 source files, 85665 hand-written lines of code (51172 production / 34493 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), 132 inter-project edges. Measured across 3 solutions loaded as one workspace: `FastEndpoints.slnx`, `NativeAot.slnx`, `TestHarness/Sandbox/Sandbox.slnx`.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
FastEndpoints is a developer-friendly ASP.NET Minimal API alternative with an excellent README and architecture doc. The root README gives the project purpose (REPR endpoint pipeline) and links to the official website, plus a sponsored Meet Our Sponsors section. Benchmark/LoadTests/README.md documents its load-testing tier with run commands and test setup; Src/Generator.Cli/README.md is a focused tool README covering installation, usage, what it generates, and full CLI options. The architecture doc (architecture.md) is comprehensive: style (library monorepo, REPR pattern), components (project references diagram), startup/mapping split with Request path explanation, and an outline of OpenAPI validation ownership, dependency rules, communication, persistence, security/auth invariants, and sources.
Documentation: contradicts the code.okf/architecture.md
Resolve the 1 Documentation finding(s) in Documentation Quality — start with architecture.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
2 of 46 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.6 / 10Strong✓ 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.
69 % of calls cross a namespace and 9 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
Resolve the 3 Pass-through layer finding(s) in Navigability — start with ValidationContext.cs (2), JobTracker.cs. — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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).
13 finding(s): 0 critical, 5 high, 8 medium, 0 low. 4 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 247 file(s) — `Benchmark/FastEndpointsBench/CodeGenEndpoint.cs` (line 11), `Src/Agents/A2A/A2ASkillCatalog.cs` (line 6), `Src/Agents/A2A/A2ASkillDispatcher.cs` (line 12, line 65), `Src/Agents/A2A/AgentCardBuilder.cs` (line 7), `Src/Agents/Mcp/EndpointMcpToolSource.cs` (line 21), … (+242 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 177 of those file(s) — `Src/Agents/A2A/A2ASkillCatalog.cs`, `Src/Agents/A2A/A2ASkillDispatcher.cs`, `Src/Agents/A2A/AgentCardBuilder.cs`, `Src/Agents/Mcp/EndpointMcpToolSource.cs`, `Src/Agents/Shared/AgentRequestBuilder.cs`, … (+172 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 5 of those file(s) — `Src/Generator/AccessControlGenerator.cs`, `Src/Generator/ReflectionGenerator.cs`, `Src/Generator/ServiceRegistrationGenerator.cs`, `TestHarness/Web/[Features]/TestCases/Messaging/CommandHandlerTest/ScopedServiceCheckEndpoint.cs`, `Tests/UnitTests/FastEndpoints/EventQueueTests.AckTimeout.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 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
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
4 of 243 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Src/Swagger/SystemTextJsonUtilities.cs. Counted over 243 of the 608 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
Resolve the 4 Change coupling finding(s) in Change Coupling — start with VersioningOptions.cs, RemoteConnectionExtensions.cs, Endpoint.Validation.cs. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 12 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.
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.
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.
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.
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.
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.
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
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.
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.
Do you agree with this assessment?
C4 · Data Retention7.5 / 10Strong✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
What to do
Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×23) — Src/Library/Endpoint/Endpoint.Base.cs:31, Src/Library/Endpoint/Endpoint.Base.cs:35, Src/Library/Endpoint/Endpoint.Base.cs:38, …
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
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.
`MarkEventAsCompleteAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — Src/Messaging/Messaging.Remote.Core/Client/Events/Storage/InMemoryEventSubscriberStorage.cs:32, Src/Messaging/Messaging.Remote/Server/Events/Storage/InMemoryEventHubStorage.cs:48
`PurgeStaleRecordsAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Src/Messaging/Messaging.Remote.Core/Client/Events/Storage/InMemoryEventSubscriberStorage.cs:35
`GetCustomAttributes` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — Src/OData/ODataParamInfo.cs:21, Src/OData/ODataParamInfo.cs:24
`IsDefined` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Src/OData/ODataParamInfo.cs:27
`Parse` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — TestHarness/NativeAotChecker/Endpoints/Binding/NonJsonBindingEndpoint.cs:38
`HandleAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — TestHarness/Web/[Features]/Customers/[EventHandlers]/SendOrderConfirmation.cs:7
`HandleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×3) — TestHarness/Web/[Features]/TestCases/Processors/PostProcessorTest/Endpoint.cs:40, TestHarness/Web/[Features]/TestCases/Processors/PostProcessorTest/Endpoint.cs:52, TestHarness/Web/[Features]/TestCases/Processors/ProcessorAttributesTest/Endpoint.cs:62
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×26) — Src/Library/Endpoint/Auxiliary/HitCounter.cs:61, Src/Library/Endpoint/Auxiliary/HitCounter.cs:67, Src/Library/Endpoint/Auxiliary/HitCounter.cs:71, …
`HandleAsync`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional. — Src/OData/ODataEndpoint.cs:48
A placeholder value ("John Doe") is still in shipped code — sample/mock data that was never replaced with the real thing. (×2) — TestHarness/NativeAotChecker/Endpoints/SerializerCtxGen/FluentNoReqResMapEndpoint.cs:39, TestHarness/OData/Model/AppDbContextExtensions.cs:20
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
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 a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 44 of 46 project(s) that lack one — worth up to 1.9 pts.
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.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Only 25/46 projects share a common root namespace — the code's module identity is inconsistent.
What to do
Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Src/Generator.Cli/README.md installs the package `FastEndpoints.Generator` (`dotnet add package FastEndpoints.Generator`), but no project or props file references it. 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. — Src/Generator.Cli/README.md:93
What to do
Reconcile the README with reality: Src/Generator.Cli/README.md installs the package `FastEndpoints.Generator` (`dotnet add package FastEndpoints.Generator`), but no project or props file references it.
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.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability6.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 16/31 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 31, 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 OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2227 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — Src/Testing/AppFixture.Aot.cs:473
What to do
Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
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.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 145 use(s) across 53,167 production line(s) (~2.7/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
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 the language 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.
4 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). (×4) — Src/Library/Middleware/FinancialIdempotency/FinancialResponseCapture.cs:193, Src/Library/Testing/HttpClientExtensions.cs:639, Src/Library/Testing/HttpClientExtensions.cs:651, …
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
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.
`ValidateAudience`, `ValidateIssuer` are all set to `false`, which means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent. — Src/Security/AuthExtensions.cs:39
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. (×8) — Benchmark/FastEndpointsBench/Program.cs:4, Benchmark/MinimalApi/Program.cs:5, Benchmark/MvcControllers/Program.cs:4, …
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. (×8) — Benchmark/FastEndpointsBench/Program.cs:4, Benchmark/MinimalApi/Program.cs:5, Benchmark/MvcControllers/Program.cs:4, …
What to do
Re-enable token validation — `ValidateAudience` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
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.
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.
`SemaphoreSlim.Wait` parks the thread while it queues for the semaphore. `await semaphore.WaitAsync(…)` yields the thread instead. (×3) — Src/JobQueues/JobQueue.cs:467, Src/Messaging/Messaging.Remote.Core/Client/Events/EventExecutorWorker.cs:136, Src/Messaging/Messaging.Remote/Server/Events/HubContext.cs:175
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. (×4) — Src/Library/Middleware/FinancialIdempotency/FinancialResponseCapture.cs:193, Src/Library/Testing/HttpClientExtensions.cs:639, Src/Library/Testing/HttpClientExtensions.cs:651, …
Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. — Src/Testing/AppFixture.Aot.cs:65
What to do
Blocking `SemaphoreSlim.Wait` inside an `async` method
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.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. 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 `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
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.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
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.
`Counter` declares a finalizer (line 115), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — Src/Library/Endpoint/Auxiliary/HitCounter.cs:115
`app.Services.CreateScope()` (line 175) creates an `IServiceScope`, and it is dropped: `CreateScope().ServiceProvider` never names the scope, so nothing can release it. A scope owns every scoped service resolved from it — the `DbContext`, its connection, anything registered `AddScoped` — and releases them only when the scope itself is disposed; nothing here ever does, so each scope's services stay alive until the process ends. Create it with `using var scope = …CreateScope();` (or `await using` for `CreateAsyncScope`), or, when it must outlive the method, dispose it from the owning type's `Dispose`. — REDACTED:175
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
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 208/284 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter, and the token `ctx.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `ctx.RequestAborted` on, or take a CancellationToken. (×3) — Src/HealthChecks/ServiceHealthChecksStartupFilter.cs:42, Src/Library/Middleware/FinancialIdempotency/FinancialIdempotencyMiddleware.cs:104, Src/Library/Middleware/FinancialIdempotency/FinancialIdempotencyMiddleware.cs:225
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. (×21) — Src/JobQueues/JobQueue.cs:233, Src/JobQueues/JobQueue.cs:345, Src/JobQueues/JobQueue.cs:455, …
No CancellationToken parameter — this work can't be stopped early once started. (×13) — Src/JobQueues/JobQueue.cs:481, Src/JobQueues/JobQueue.cs:530, Src/Library/Endpoint/Endpoint.Send.cs:376, …
No CancellationToken parameter, and the token `request.HttpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `request.HttpContext.RequestAborted` on, or take a CancellationToken. — Src/Library/Binder/RequestBinder.cs:292
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/Messaging/Messaging.Remote.Core/Client/Events/EventExecutorWorker.cs:144
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
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.
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.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
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.
Do you agree with this assessment?
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.
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.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
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.
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.
`catch` 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/Generator.Cli/Program.ProjectInspection.cs:197
`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/JobQueues/JobQueue.cs:203
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. (×16) — Src/JobQueues/JobQueue.cs:230, Src/Library/Endpoint/Endpoint.Properties.cs:108, Src/Library/X402/X402FacilitatorClient.cs:60, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). (×2) — Src/OpenApi.Kiota/Extensions.cs:344, Src/Testing/AppFixture.Aot.cs:514
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×4) — TestHarness/Web/PipelineBehaviors/PostProcessors/MyResponseLogger.cs:12, TestHarness/Web/PipelineBehaviors/PreProcessors/MyRequestLogger.cs:10, TestHarness/Web/[Features]/Customers/[EventHandlers]/SendOrderConfirmation.cs:9, …
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~1.4 `!` suppressions per 1k syntax nodes — 329 suppression(s) across the 238025 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.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
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.
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 — 4 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 — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
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.
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 — 36 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.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
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 — no test run produced results
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
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
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) — 120 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — IL not measured — the target did not build
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.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — 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.
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (6 value object(s))
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 22 event handler(s); 93 CQRS handler(s)
ED5 Idempotency — 95 mutating command handler(s)/consumer(s) detected and 77 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P8 Schema migrations — EF Core is used, but the schema-migration mechanism could not be identified — this check only recognises EF migrations, so any other migration runner reads as an absence. Our limit, not a verdict on this repository.
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
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
FileScopedPragmaDisable Benchmark/Runner/Benchmarks.cs:6— #pragma warning disable CA1822 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Benchmark/Runner/CommandHandlerBenchmarks.cs:4— #pragma warning disable CA1822 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Benchmark/Runner/EmptyRequestBenchmarks.cs:4— #pragma warning disable CA1822 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Library/Binder/BinderContext.cs:7— #pragma warning disable CA1822 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Library/Extensions/HttpContextExtensions.cs:3— #pragma warning disable CA1822 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Tests/UnitTests/FastEndpoints.Testing/PriorityTestHelpers.cs:6— #pragma warning disable CA1822 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Attributes/Contracts/ReflectionCache.cs:7— #pragma warning disable CS1591 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Attributes/Enums/Source.cs:3— #pragma warning disable CS1591 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Attributes/JetBrains/Annotations.cs:27— #pragma warning disable 1591 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/ClientGen.Kiota/Extensions.cs:15— #pragma warning disable VSTHRD200 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/OpenApi.Kiota/Extensions.cs:18— #pragma warning disable VSTHRD200 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Library/Binder/PropCache.cs:5— #pragma warning disable CS8618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Library/Endpoint/Processor/PostProcessorContext.cs:5— #pragma warning disable CS8618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Library/Endpoint/Processor/PreProcessorContext.cs:4— #pragma warning disable CS8618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Library/Endpoint/Summary/DefaultProducesResponseMetadata.cs:3— #pragma warning disable CS8618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/OData/ODataParamInfo.cs:3— #pragma warning disable CS8618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Tests/IntegrationTests/FastEndpoints.Agents/EndpointInvokerBindingTests.cs:7— #pragma warning disable CS8618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Tests/IntegrationTests/FastEndpoints.Agents/McpToolDuplicateNameTests.cs:8— #pragma warning disable CS8618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Library/Config/Config.cs:4— #pragma warning disable RCS1102,CA1822 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Library/DTOs/EmptyRequest.cs:1— #pragma warning disable RCS1074 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Library/Extensions/HttpResponseExtensions.cs:12— #pragma warning disable IL2026 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Messaging/Messaging.Remote.Testing/Extensions.cs:4— #pragma warning disable IDE0022 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Src/Security/JwtCreationOptions.cs:60— #pragma warning disable CS1574 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable TestHarness/Web/[Features]/TestCases/Swagger/Review/Endpoints.cs:5— #pragma warning disable CS1574, CS1584, CS1581, CS1580, CS1734 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable Tests/IntegrationTests/FastEndpoints/FixtureTests/AssemblyFixtureTests.cs:29— #pragma warning disable xUnit1041 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
EmptyCatchBlock Src/Agents/A2A/A2AJsonRpcEndpoint.cs:55— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/JobQueues/JobQueue.cs:230— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Library/Endpoint/Endpoint.Properties.cs:108— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Library/X402/X402FacilitatorClient.cs:60— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Library/X402/X402FacilitatorClient.cs:74— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Messaging/Messaging.Remote.Core/Client/Events/EventDeliveryAckReceiver.cs:133— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Messaging/Messaging.Remote.Core/Client/Events/EventExecutorWorker.cs:219— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Messaging/Messaging.Remote.Core/Client/Events/EventReceiverWorker.cs:84— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Messaging/Messaging.Remote.Core/Client/Events/Storage/EventSubscriberStorage.cs:33— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Messaging/Messaging.Remote/Server/Events/EventDispatcherWorker.cs:105— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Messaging/Messaging.Remote/Server/Events/Storage/EventHubStorage.cs:33— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/OpenApi.Kiota/Extensions.cs:296— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/OpenApi.Kiota/Extensions.cs:344— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/OpenApi/Schemas/Transformers/PolymorphismSchemaTransformer.cs:36— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Swagger/ValidationSchemaProcessor.cs:231— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Testing/AppFixture.Aot.cs:67— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Testing/AppFixture.Aot.cs:493— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Src/Testing/AppFixture.Aot.cs:514— 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.
NoWarnInCsproj — 8 warning codes suppressed in one element TestHarness/Web/Web.csproj:9— A single <NoWarn> suppresses 8 warning codes (CS1591;1701;1702;CA2016;RCS1090;CA2254;CS8618;ASP0014) in one stroke — one team-wide decision, not 8 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 — 8 warning codes suppressed in one element Src/Library/FastEndpoints.csproj:3— A single <NoWarn> suppresses 8 warning codes (1701;1702;CS1591;CS1573;CA2254;RCS1079;CS8618;IDE0022) in one stroke — one team-wide decision, not 8 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 — 8 warning codes suppressed in one element Tests/Directory.Build.props:7— A single <NoWarn> suppresses 8 warning codes (CS1587;CS1591;CS1998;NU5105;RCS1102;IDE1006;xUnit1051;CS8002) in one stroke — one team-wide decision, not 8 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 Benchmark/Directory.Build.props:7— A single <NoWarn> suppresses 12 warning codes (1701;1702;RCS1090;RCS1163;RCS1102;CA2016;CS1587;CS1591;CS1998;NU5105;IDE1006;IDE0060) 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 TestHarness/OpenApi.Kiota/OpenApi.Kiota.csproj:9— CA2016 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj TestHarness/Sandbox/Source/Sandbox.csproj:8— CA2016 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj TestHarness/OpenApi.Kiota/OpenApi.Kiota.csproj:9— ASP0014 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Src/Security/FastEndpoints.Security.csproj:4— IDE0022 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Src/Generator/FastEndpoints.Generator.csproj:13— NU5128 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
NoWarnInCsproj Src/Generator.Cli/FastEndpoints.Generator.Cli.csproj:13— RS1035 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
WriteOnlyPrivateField Src/Testing/TestFramework/TestAssemblyRunner.cs:13— private TestCaseOrderer _testCaseOrderer — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField Tests/IntegrationTests/FastEndpoints/RPCTests/EventQueue.cs:9— private Sut _app — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
NoWarnInCsproj repeated across 13 files TestHarness/OpenApi.Kiota/OpenApi.Kiota.csproj:9— The identical NoWarnInCsproj (`1701`) appears in 13 files (13 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 13 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
NoWarnInCsproj repeated across 13 files TestHarness/OpenApi.Kiota/OpenApi.Kiota.csproj:9— The identical NoWarnInCsproj (`1702`) appears in 13 files (13 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 13 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
NoWarnInCsproj repeated across 20 files TestHarness/OpenApi.Kiota/OpenApi.Kiota.csproj:9— The identical NoWarnInCsproj (`CS1591`) appears in 20 files (20 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 20 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
NoWarnInCsproj repeated across 11 files Src/Swagger/FastEndpoints.Swagger.csproj:4— The identical NoWarnInCsproj (`CS1573`) appears in 11 files (11 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 11 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
AnalyzerSeverityNone .editorconfig:21— CS8618 — 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.
Dead code: WithVersionSet Src/AspVersioning/Extensions.cs:67— Method WithVersionSet — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.AspVersioning, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ApiVersion Src/AspVersioning/Extensions.cs:85— Method ApiVersion — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.AspVersioning, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetX402RequestContext Src/Library/X402/X402HttpContextExtensions.cs:12— Method GetX402RequestContext — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: MapRemoteCore Src/Messaging/Messaging.Remote.Core/Client/RemoteConnectionCoreExtensions.cs:23— Method MapRemoteCore — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.Messaging.Remote.Core(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: RegisterEvent Src/Messaging/Messaging.Remote/Client/RemoteConnection.cs:59— Method RegisterEvent — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.Messaging.Remote(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: MapRemote Src/Messaging/Messaging.Remote/Client/RemoteConnectionExtensions.cs:24— Method MapRemote — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.Messaging.Remote(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ListenInterProcess Src/Messaging/Messaging.Remote/Server/KestrelExtensions.cs:17— Method ListenInterProcess — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.Messaging.Remote(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: IsNotGenerationMode Src/OpenApi.Kiota/Extensions.cs:159— Method IsNotGenerationMode — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.OpenApi.Kiota(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: IsNotGenerationMode Src/OpenApi.Kiota/Extensions.cs:186— Method IsNotGenerationMode — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.OpenApi.Kiota(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: SwaggerIgnore Src/OpenApi/Extensions.cs:93— Method SwaggerIgnore — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.OpenApi(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: IsNotExportMode Src/OpenApi/Extensions.cs:110— Method IsNotExportMode — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.OpenApi(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: IsNotJsonExportMode Src/OpenApi/Extensions.cs:122— Method IsNotJsonExportMode — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.OpenApi(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: IsNotHttpExportMode Src/OpenApi/Extensions.cs:134— Method IsNotHttpExportMode — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.OpenApi(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: IsNotExportMode Src/OpenApi/Extensions.cs:149— Method IsNotExportMode — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.OpenApi(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: IsNotJsonExportMode Src/OpenApi/Extensions.cs:161— Method IsNotJsonExportMode — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.OpenApi(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: IsNotHttpExportMode Src/OpenApi/Extensions.cs:173— Method IsNotHttpExportMode — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.OpenApi(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ExportOpenApiDocsAndExitAsync Src/OpenApi/Extensions.cs:244— Method ExportOpenApiDocsAndExitAsync — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.OpenApi(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ExportHttpFilesAndExitAsync Src/OpenApi/Extensions.cs:275— Method ExportHttpFilesAndExitAsync — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.OpenApi(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: HasClaimType Src/Security/AuthExtensions.cs:127— Method HasClaimType — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.Security(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CookieAuth Src/Security/CookieAuth.cs:11— NamedType CookieAuth — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.Security(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CreateCustomToken Src/Security/RefreshTokens/RefreshTokenService.cs:138— Method CreateCustomToken — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.Security(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: AddHandlers Src/Testing/ClientOptions.cs:53— Method AddHandlers — Roslyn's SymbolFinder walked every project the solution loads, including FastEndpoints.Testing(net10.0), and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CodeGenEndpoint Benchmark/FastEndpointsBench/CodeGenEndpoint.cs:41— NamedType CodeGenEndpoint — Roslyn's SymbolFinder walked every project the solution loads, including FEBench, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CommandHandlerEndpoint1 Benchmark/FastEndpointsBench/CommandHandlerEndpoint.cs:7— NamedType CommandHandlerEndpoint1 — Roslyn's SymbolFinder walked every project the solution loads, including FEBench, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CommandHandlerEndpoint2 Benchmark/FastEndpointsBench/CommandHandlerEndpoint.cs:19— NamedType CommandHandlerEndpoint2 — Roslyn's SymbolFinder walked every project the solution loads, including FEBench, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Unfinished stub — throws NotImplementedException Src/Library/Endpoint/Endpoint.Base.cs:31— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Library/Endpoint/Endpoint.Base.cs:35— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Library/Endpoint/Endpoint.Base.cs:38— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Library/Endpoint/Endpoint.Base.cs:43— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Library/Endpoint/Endpoint.cs:175— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Library/Endpoint/Endpoint.cs:184— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Library/Endpoint/Endpoint.cs:388— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Library/Endpoint/Endpoint.cs:403— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Library/Endpoint/Endpoint.cs:426— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Library/Endpoint/Endpoint.cs:441— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Messaging/Messaging.Remote.Core/Client/Events/Storage/InMemoryEventSubscriberStorage.cs:32— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Messaging/Messaging.Remote.Core/Client/Events/Storage/InMemoryEventSubscriberStorage.cs:35— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Messaging/Messaging.Remote/Server/Commands/BaseHandlerExecutor.cs:24— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Messaging/Messaging.Remote/Server/Commands/BaseHandlerExecutor.cs:27— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Messaging/Messaging.Remote/Server/Commands/BaseHandlerExecutor.cs:30— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Messaging/Messaging.Remote/Server/Events/Storage/InMemoryEventHubStorage.cs:48— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/OData/ODataParamInfo.cs:21— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/OData/ODataParamInfo.cs:24— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/OData/ODataParamInfo.cs:27— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException TestHarness/Web/[Features]/TestCases/Processors/PostProcessorTest/Endpoint.cs:40— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException TestHarness/Web/[Features]/TestCases/Processors/PostProcessorTest/Endpoint.cs:52— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException TestHarness/Web/[Features]/TestCases/Processors/ProcessorAttributesTest/Endpoint.cs:62— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException TestHarness/NativeAotChecker/Endpoints/Binding/NonJsonBindingEndpoint.cs:38— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Swallowed exception (empty catch) Src/JobQueues/JobQueue.cs:230— 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.
Swallowed exception (empty catch) Src/Library/Endpoint/Endpoint.Properties.cs:108— 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.
Swallowed exception (empty catch) Src/Library/X402/X402FacilitatorClient.cs:60— 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.
Swallowed exception (empty catch) Src/Library/X402/X402FacilitatorClient.cs:74— 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.
Swallowed exception (empty catch) Src/Messaging/Messaging.Remote.Core/Client/Events/EventDeliveryAckReceiver.cs:133— 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.
Swallowed exception (empty catch) Src/Messaging/Messaging.Remote.Core/Client/Events/EventExecutorWorker.cs:219— 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.
Swallowed exception (empty catch) Src/Messaging/Messaging.Remote.Core/Client/Events/EventReceiverWorker.cs:84— 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.
Swallowed exception (empty catch) Src/Messaging/Messaging.Remote.Core/Client/Events/Storage/EventSubscriberStorage.cs:33— 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.
Swallowed exception (empty catch) Src/Messaging/Messaging.Remote/Server/Events/EventDispatcherWorker.cs:105— 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.
Swallowed exception (empty catch) Src/Messaging/Messaging.Remote/Server/Events/Storage/EventHubStorage.cs:33— 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.
Swallowed exception (empty catch) Src/OpenApi.Kiota/Extensions.cs:296— 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.
Swallowed exception (empty catch) Src/OpenApi.Kiota/Extensions.cs:344— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) Src/OpenApi/Schemas/Transformers/PolymorphismSchemaTransformer.cs:36— 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.
Swallowed exception (empty catch) Src/Testing/AppFixture.Aot.cs:67— 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.
Swallowed exception (empty catch) Src/Testing/AppFixture.Aot.cs:493— 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.
Swallowed exception (empty catch) Src/Testing/AppFixture.Aot.cs:514— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) Src/Agents/A2A/A2AJsonRpcEndpoint.cs:55— 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.
Swallowed exception (empty catch) Src/Swagger/ValidationSchemaProcessor.cs:231— 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.
X2 · Cancellation propagation· Async method without CancellationToken · ×17
Async method without CancellationToken: WriteJson Src/HealthChecks/ServiceHealthChecksStartupFilter.cs:42— No CancellationToken parameter, and the token `ctx.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `ctx.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: DrainExecutions Src/JobQueues/JobQueue.cs:481— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RetryUntilSuccessOrShutdownAsync Src/JobQueues/JobQueue.cs:530— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: BindPlainTextBody Src/Library/Binder/RequestBinder.cs:292— No CancellationToken parameter, and the token `request.HttpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `request.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: OkAsync Src/Library/Endpoint/Endpoint.Send.cs:376— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SendResultAsync Src/Library/Extensions/HttpResponseExtensions.cs:592— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ExecuteAndSettle Src/Library/Middleware/FinancialIdempotency/FinancialIdempotencyMiddleware.cs:104— No CancellationToken parameter, and the token `ctx.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `ctx.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: SendError Src/Library/Middleware/FinancialIdempotency/FinancialIdempotencyMiddleware.cs:225— No CancellationToken parameter, and the token `ctx.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `ctx.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: SnapshotAsync Src/Library/Middleware/FinancialIdempotency/FinancialResponseCapture.cs:162— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: POSTAsync Src/Library/Testing/HttpClientExtensions.cs:99— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PATCHAsync Src/Library/Testing/HttpClientExtensions.cs:182— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PUTAsync Src/Library/Testing/HttpClientExtensions.cs:265— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GETAsync Src/Library/Testing/HttpClientExtensions.cs:343— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: QUERYAsync Src/Library/Testing/HttpClientExtensions.cs:430— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DELETEAsync Src/Library/Testing/HttpClientExtensions.cs:508— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SENDAsync Src/Library/Testing/HttpClientExtensions.cs:545— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StaleJobPurgingTask Src/Messaging/Messaging.Remote.Core/Client/Events/Storage/EventSubscriberStorage.cs:15— No CancellationToken parameter — this work can't be stopped early once started.
BarePragmaDisable Src/Library/Config/ErrorOptions.cs:77— #pragma warning disable CA1822 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. 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 and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Src/Library/Endpoint/Auxiliary/Group.cs:70— #pragma warning disable CA1822 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. 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 and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Src/Testing/AppFixture.Waf.cs:26— #pragma warning disable CA1822 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. 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 and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Src/Testing/AssemblyFixture/TestBaseWithAssemblyFixture.cs:19— #pragma warning disable CA1822 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. 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 and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Src/Testing/StateFixture.cs:12— #pragma warning disable CA1822 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. 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 and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Src/Testing/TestBase.cs:19— #pragma warning disable CA1822 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. 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 and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Src/Library/Messaging/Commands/CommandHandler.cs:37— #pragma warning disable CS8424 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. 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 and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Src/Messaging/Messaging.Core/Interfaces/ICommandHandler.cs:53— #pragma warning disable CS8424 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. 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 and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Src/Messaging/Messaging.Core/Interfaces/ICommandHandler.cs:85— #pragma warning disable CS8424 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. 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 and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable Src/Messaging/Messaging/Commands/IStreamCommandMiddleware.cs:19— #pragma warning disable CS8424 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. 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 and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
Unfinished stub — throws NotImplementedException Src/Messaging/Messaging.Remote.Core/Client/Events/Storage/InMemoryEventSubscriberStorage.cs:32— `MarkEventAsCompleteAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Messaging/Messaging.Remote.Core/Client/Events/Storage/InMemoryEventSubscriberStorage.cs:35— `PurgeStaleRecordsAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/Messaging/Messaging.Remote/Server/Events/Storage/InMemoryEventHubStorage.cs:48— `MarkEventAsCompleteAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/OData/ODataParamInfo.cs:21— `GetCustomAttributes` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/OData/ODataParamInfo.cs:24— `GetCustomAttributes` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Src/OData/ODataParamInfo.cs:27— `IsDefined` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException TestHarness/NativeAotChecker/Endpoints/Binding/NonJsonBindingEndpoint.cs:38— `Parse` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException TestHarness/Web/[Features]/TestCases/Processors/PostProcessorTest/Endpoint.cs:40— `HandleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException TestHarness/Web/[Features]/TestCases/Processors/PostProcessorTest/Endpoint.cs:52— `HandleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException TestHarness/Web/[Features]/TestCases/Processors/ProcessorAttributesTest/Endpoint.cs:62— `HandleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Hotspot: Src/OpenApi/Operations/OperationTransformer.Requests.cs Src/OpenApi/Operations/OperationTransformer.Requests.cs:168— Src/OpenApi/Operations/OperationTransformer.Requests.cs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in RequestOperationTransformer.ApplyBodySchemaMetadata at line 168. 2 of those changes were fix/bug commits, and the other 10 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-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 06:12:48 +05:30' --until='2026-10-22 06:12:48 +05:30' --full-history --no-merges -- Src/OpenApi/Operations/OperationTransformer.Requests.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.
Hotspot: REDACTED REDACTED:18— REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in EndpointRouteMapper.Map at line 18. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 06:12:48 +05:30' --until='2026-10-22 06:12:48 +05:30' --full-history --no-merges -- REDACTED`: 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.
Hotspot: Src/Library/Binder/ComplexSourceBinder.cs Src/Library/Binder/ComplexSourceBinder.cs:50— Src/Library/Binder/ComplexSourceBinder.cs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in ComplexSourceBinder.BindPropertiesRecursively at line 50. 1 of those changes was a fix/bug commit, and the other 3 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-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 06:12:48 +05:30' --until='2026-10-22 06:12:48 +05:30' --full-history --no-merges -- Src/Library/Binder/ComplexSourceBinder.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.
Hotspot: Src/Library/Testing/HttpClientExtensions.cs Src/Library/Testing/HttpClientExtensions.cs:613— Src/Library/Testing/HttpClientExtensions.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in .GetTestUrlFor at line 613. 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-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 06:12:48 +05:30' --until='2026-10-22 06:12:48 +05:30' --full-history --no-merges -- Src/Library/Testing/HttpClientExtensions.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.
Hotspot: Src/Security/Revocation/JwtRevocationMiddleware.cs Src/Security/Revocation/JwtRevocationMiddleware.cs:25— Src/Security/Revocation/JwtRevocationMiddleware.cs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in JwtRevocationMiddleware.Invoke at line 25. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 06:12:48 +05:30' --until='2026-10-22 06:12:48 +05:30' --full-history --no-merges -- Src/Security/Revocation/JwtRevocationMiddleware.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.
Hotspot: Src/Library/Main/MainExtensions.cs Src/Library/Main/MainExtensions.cs:158— Src/Library/Main/MainExtensions.cs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in MainExtensions.BuildRoute at line 158. 1 of those changes was a fix/bug commit, and the other 3 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-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 06:12:48 +05:30' --until='2026-10-22 06:12:48 +05:30' --full-history --no-merges -- Src/Library/Main/MainExtensions.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.
Hotspot: Src/Library/Endpoint/Endpoint.cs Src/Library/Endpoint/Endpoint.cs:55— Src/Library/Endpoint/Endpoint.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in Endpoint.ExecAsync at line 55. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 06:12:48 +05:30' --until='2026-10-22 06:12:48 +05:30' --full-history --no-merges -- Src/Library/Endpoint/Endpoint.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.
Hotspot: Src/OpenApi/Schemas/Transformers/XmlDocSchemaTransformer.cs Src/OpenApi/Schemas/Transformers/XmlDocSchemaTransformer.cs:9— Src/OpenApi/Schemas/Transformers/XmlDocSchemaTransformer.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in XmlDocSchemaTransformer.TransformAsync at line 9. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 06:12:48 +05:30' --until='2026-10-22 06:12:48 +05:30' --full-history --no-merges -- Src/OpenApi/Schemas/Transformers/XmlDocSchemaTransformer.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.
Hotspot: Src/OpenApi/Operations/Requests/RequestBodyOverrideApplicator.cs Src/OpenApi/Operations/Requests/RequestBodyOverrideApplicator.cs:9— Src/OpenApi/Operations/Requests/RequestBodyOverrideApplicator.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in RequestBodyOverrideApplicator.Apply at line 9. 1 of those changes was a fix/bug commit, and the other 1 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-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 06:12:48 +05:30' --until='2026-10-22 06:12:48 +05:30' --full-history --no-merges -- Src/OpenApi/Operations/Requests/RequestBodyOverrideApplicator.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.
TooManyMethods: Program REDACTED— TooManyMethods — 1144 significant lines (blank, comment-only and punctuation-only lines excluded), 77 methods, declared across 9 files: REDACTED (24), Generator.Cli/Program.TypeResolution.cs (13), Generator.Cli/Program.ProjectInspection.cs (12), Generator.Cli/Program.EndpointDiscovery.cs (9), +5 more file(s). The bar is 30 methods; this is 47 over it, 2.57× 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: EndpointDefinition Src/Library/Endpoint/Auxiliary/EndpointDefinition.cs— TooManyMethods — 374 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 30 methods; this is 29 over it, 1.97× 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: OperationSchemaHelpers Src/OpenApi/Schemas/OpenApiSchemaExtensions.cs— TooManyMethods — 441 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods, declared across 4 files: Schemas/OpenApiSchemaExtensions.cs (29), Schemas/OperationSchemaHelpers.cs (16), Schemas/OpenApiTypeSchemaFactory.cs (9), Schemas/OpenApiJsonHelpers.cs (4). The bar is 30 methods; this is 28 over it, 1.93× 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: OperationProcessor Src/Swagger/OperationProcessor.cs— TooManyMethods — 595 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 30 methods; this is 15 over it, 1.50× 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: Endpoint Src/Library/Endpoint/Endpoint.cs— TooManyMethods — 311 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods, declared across 5 files: Endpoint/Endpoint.cs (12), Endpoint/Endpoint.Hooks.cs (10), Endpoint/Endpoint.Validation.cs (10), Endpoint/Endpoint.Static.cs (6), +1 more file(s). The bar is 30 methods; this is 9 over it, 1.30× 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: RequestOperationTransformer Src/OpenApi/Operations/OperationTransformer.Requests.cs— TooManyMethods — 399 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods, declared across 2 files: Operations/OperationTransformer.Requests.cs (17), Operations/OperationTransformer.RequestExamples.cs (14). The bar is 30 methods; this is 1 over it, 1.03× 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.
Duplicated block (8 lines × 2) Src/ClientGen.Kiota/LoggingExtensions.cs:16— Src/ClientGen.Kiota/LoggingExtensions.cs:16-23 | Src/OpenApi.Kiota/LoggingExtensions.cs:16-23 — 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.
Duplicated block (8 lines × 2) Src/OpenApi/Schemas/SchemaNameGenerator.cs:104— Src/OpenApi/Schemas/SchemaNameGenerator.cs:104-111 | Src/Swagger/SchemaNameGenerator.cs:43-50 — 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/OpenApi/Schemas/SchemaNameGenerator.cs:104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Src/Generator.Cli/Program.TypeResolution.cs:189— Src/Generator.Cli/Program.TypeResolution.cs:189-196 | Src/Generator.Cli/Program.TypeResolution.cs:198-205 — 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/Generator.Cli/Program.TypeResolution.cs:198` 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.
Duplicated block (8 lines × 2) Src/Messaging/Messaging.Remote/Server/Commands/ClientStreamHandlerExecutor.cs:26— Src/Messaging/Messaging.Remote/Server/Commands/ClientStreamHandlerExecutor.cs:26-33 | Src/Messaging/Messaging.Remote/Server/Commands/ServerStreamHandlerExecutor.cs:29-36 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Src/Messaging/Messaging.Remote/Server/Commands/ServerStreamHandlerExecutor.cs:27` calls `AddCommand` and `Src/Messaging/Messaging.Remote/Server/Commands/ClientStreamHandlerExecutor.cs:25` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) Src/OpenApi/Operations/OperationTransformer.Requests.cs:350— Src/OpenApi/Operations/OperationTransformer.Requests.cs:350-357 | Src/OpenApi/Operations/OperationTransformer.Requests.cs:361-368 — 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/OpenApi/Operations/OperationTransformer.Requests.cs:350` 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.
Duplicated block (8 lines × 2) TestHarness/Web/[Features]/Uploads/Image/Save/Models.cs:16— TestHarness/Web/[Features]/Uploads/Image/Save/Models.cs:16-23 | TestHarness/Web/[Features]/Uploads/Image/SaveTyped/Models.cs:25-32 — `TestHarness/Web/[Features]/Uploads/Image/Save/Models.cs` and `TestHarness/Web/[Features]/Uploads/Image/SaveTyped/Models.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 8 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
Sync-over-async blocking — 4 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/Library/Middleware/FinancialIdempotency/FinancialResponseCapture.cs:193— `.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/Library/Testing/HttpClientExtensions.cs:639— `.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/Library/Testing/HttpClientExtensions.cs:651— `.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/Testing/AppFixture.Aot.cs:65— `.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).
TodoComment Src/Core/ServiceResolver/IServiceResolver.cs:21— //todo: need to figure out how to get rid of this from this interface! — 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.
TodoComment Src/Swagger/OperationProcessor.cs:174— //todo: this is not ideal in case two consumes dtos has a prop with the same name. — 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.
TodoComment Src/Swagger/OperationProcessor.cs:711— //todo: remove when .net 9 sdk bug is fixed — 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.
TodoComment Src/Swagger/ValidationSchemaProcessor.cs:186— //todo: figure out how to obtain the concrete instances of child validators from PolymorphicValidator<> — 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.
MethodTooLong: ComplexSourceBinder.BindPropertiesRecursively Src/Library/Binder/ComplexSourceBinder.cs:50— MethodTooLong — BindPropertiesRecursively runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventExecutorWorker.RunAsync Src/Messaging/Messaging.Remote.Core/Client/Events/EventExecutorWorker.cs:15— MethodTooLong — RunAsync runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DocumentRegistration.AddOpenApiDocuments TestHarness/Web/DocumentRegistration.cs:5— MethodTooLong — AddOpenApiDocuments runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Md5.ComputeHash Src/Messaging/Messaging.Core/Extensions.cs:13— MethodTooLong — ComputeHash runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Change coupling: VersioningOptions.cs ↔ MainExtensions.cs Src/Library/Config/VersioningOptions.cs:1— `Src/Library/Config/VersioningOptions.cs` and `Src/Library/Main/MainExtensions.cs` change together 91% of the time (10 of the 11 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 different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `a44cecd5` add `DontVersion()` method for skipping default version for endpoints; `2c28a3ee` version number placement strategy; `93f2efca` add package `FastEndpoints.AspVersioning` — run `git show` on any of them.
Change coupling: RemoteConnectionExtensions.cs ↔ HandlerServerExtensions.cs Src/Messaging/Messaging.Remote/Client/RemoteConnectionExtensions.cs:1— `Src/Messaging/Messaging.Remote/Client/RemoteConnectionExtensions.cs` and `Src/Messaging/Messaging.Remote/Server/HandlerServerExtensions.cs` change together 50% of the time (8 of the 16 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 different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these 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 `4f39280f` more extension blocks; `90d2c04a` code cleanups (at that commit the files were still `Src/Messaging.Remote/Client/RemoteConnectionExtensions.cs` and `Src/Messaging.Remote/Server/HandlerServerExtensions.cs`); `0b9d462a` remote pub/sub messaging (at that commit the files were still `Src/Messaging.Remote/Client/RemoteConnectionExtensions.cs` and `Src/Messaging.Remote/Server/HandlerServerExtensions.cs`) — run `git show` on any of them.
Change coupling: Endpoint.Validation.cs ↔ ValidationContext.cs Src/Library/Endpoint/Endpoint.Validation.cs:1— `Src/Library/Endpoint/Endpoint.Validation.cs` and `Src/Library/Validation/ValidationContext.cs` change together 50% of the time (5 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 different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `22bfda82` error code and severity support for `ThrowError()` method; `a11ed3f8` manual error adding fix; `4313f3bf` improve nullable member expression parameters — run `git show` on any of them.
Change coupling: MainExtensions.cs ↔ TestingExtensions.cs Src/Library/Main/MainExtensions.cs:1— `Src/Library/Main/MainExtensions.cs` and `Src/Library/Testing/TestingExtensions.cs` change together 50% of the time (5 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 different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `58dd369d` improve surfacing aot warnings to consumers; `9936215b` switch to suppression attribute; `7bee7986` aot cleanups — run `git show` on any of them.
Sync-over-async (deadlock risk) Src/Library/Middleware/FinancialIdempotency/FinancialResponseCapture.cs:193— 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/Library/Testing/HttpClientExtensions.cs:639— 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/Library/Testing/HttpClientExtensions.cs:651— 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/Testing/AppFixture.Aot.cs:65— 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.
Duplicated block (9 lines × 2) Src/JobQueues/JobQueue.cs:159— Src/JobQueues/JobQueue.cs:159-167 | Src/JobQueues/JobQueue.cs:173-181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) Src/Agents/Shared/AgentRequestBuilder.cs:377— Src/Agents/Shared/AgentRequestBuilder.cs:377-385 | Src/OpenApi/Infrastructure/RouteTemplateHelpers.cs:41-49 — 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.
Duplicated block (9 lines × 2) Src/Generator/AccessControlGenerator.cs:596— Src/Generator/AccessControlGenerator.cs:596-605 | Src/Library/Endpoint/Endpoint.Base.cs:54-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. 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.
Blocking `SemaphoreSlim.Wait` inside an `async` method Src/JobQueues/JobQueue.cs:467— `SemaphoreSlim.Wait` parks the thread while it queues for the semaphore. `await semaphore.WaitAsync(…)` yields the thread instead.
Blocking `SemaphoreSlim.Wait` inside an `async` method Src/Messaging/Messaging.Remote.Core/Client/Events/EventExecutorWorker.cs:136— `SemaphoreSlim.Wait` parks the thread while it queues for the semaphore. `await semaphore.WaitAsync(…)` yields the thread instead.
Blocking `SemaphoreSlim.Wait` inside an `async` method Src/Messaging/Messaging.Remote/Server/Events/HubContext.cs:175— `SemaphoreSlim.Wait` parks the thread while it queues for the semaphore. `await semaphore.WaitAsync(…)` yields the thread instead.
D17 · Explicit Debt· Whole file has no live code · ×2
Whole file has no live code — 1 debt marker inside it TestHarness/Sandbox/Contracts/MyENDPOINT.cs:1— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 1 debt marker inside it TestHarness/Sandbox/Tests/EndpointTests/EndpointTests.cs:1— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
FileTooLong: Review/Endpoints.cs TestHarness/Web/[Features]/TestCases/Swagger/Review/Endpoints.cs— FileTooLong — 805 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 305 over it, 1.61× 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.
FileTooLong: Swagger/OperationProcessor.cs Src/Swagger/OperationProcessor.cs— FileTooLong — 695 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 195 over it, 1.39× 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.
Duplicated block (7 lines × 2) Src/Library/X402/X402Middleware.cs:79— Src/Library/X402/X402Middleware.cs:79-85 | Src/Library/X402/X402Middleware.cs:114-120 — 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/Library/X402/X402Middleware.cs:79` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Src/Library/X402/X402Middleware.cs:113` calls `Clear` and `Src/Library/X402/X402Middleware.cs:78` 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 (7 lines × 2) TestHarness/Web/[Features]/Inventory/Manage/Create/Models.cs:11— TestHarness/Web/[Features]/Inventory/Manage/Create/Models.cs:11-18 | TestHarness/Web/[Features]/Inventory/Manage/Update/Models.cs:8-14 — 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.
P12 · CI test-gate honesty· CI test gate excludes suites by filter · ×2
CI test gate excludes suites by filter REDACTED:33— `dotnet test FastEndpoints.slnx -c Release --framework net10.0 --verbosity minimal --filter "ExcludeInCiCd!=Yes" --max-parallel-test-modul…` filters with `ExcludeInCiCd!=Yes` — the suites it excludes. Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:36— `dotnet test FastEndpoints.slnx -c Release --framework net11.0 --verbosity minimal --filter "ExcludeInCiCd!=Yes" --max-parallel-test-modul…` filters with `ExcludeInCiCd!=Yes` — the suites it excludes. Run what it drops in another job before merge (a complementary filter), or remove the filter.
Swallowed exception (caught, then discarded) Src/Generator.Cli/Program.ProjectInspection.cs:197— `catch` 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/JobQueues/JobQueue.cs:203— `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.
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.
Md5.ComputeHash (cyclomatic 71) Src/Messaging/Messaging.Core/Extensions.cs:13— Md5.ComputeHash has cyclomatic complexity 71 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TypeInfo.TypeInfo.ctor (cyclomatic 48) Src/Generator/ReflectionGenerator.cs:234— TypeInfo.TypeInfo.ctor has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ComplexSourceBinder.BindPropertiesRecursively (cyclomatic 37) Src/Library/Binder/ComplexSourceBinder.cs:50— ComplexSourceBinder.BindPropertiesRecursively has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 14 of the 37 points are its own statements and the rest belongs to 7 function items inside it that branch (BindFormFileCollectionProp, BindSimpleCollection, BindCollectionType, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
EndpointRouteMapper.Map (cyclomatic 37) REDACTED:18— EndpointRouteMapper.Map has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AccessControlGenerator.Initialize (cyclomatic 34) Src/Generator/AccessControlGenerator.cs:27— AccessControlGenerator.Initialize has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to 7 function items inside it that branch (QualifyPartial, GetStringConstants, QualifyCustom, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
EventExecutorWorker.RunAsync (cyclomatic 33) Src/Messaging/Messaging.Remote.Core/Client/Events/EventExecutorWorker.cs:15— EventExecutorWorker.RunAsync has cyclomatic complexity 33 (threshold 15). Of this number, 30 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JobQueue.CommandExecutorTask (cyclomatic 31) Src/JobQueues/JobQueue.cs:233— JobQueue.CommandExecutorTask has cyclomatic complexity 31 (threshold 15). Of this number, 21 points are the body's own statements and 10 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RequestBinder.RequestBinder.ctor (cyclomatic 28) Src/Library/Binder/RequestBinder.cs:42— RequestBinder.RequestBinder.ctor has cyclomatic complexity 28 (threshold 15). Of this number, 25 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
.GetTestUrlFor (cyclomatic 27) Src/Library/Testing/HttpClientExtensions.cs:613— .GetTestUrlFor has cyclomatic complexity 27 (threshold 15). Of this number, 24 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HttpClientExtensions.AddObjectToForm (cyclomatic 26) Src/Library/Testing/HttpClientExtensions.cs:906— HttpClientExtensions.AddObjectToForm has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 9 of the 26 points are its own statements and the rest belongs to 3 function items inside it that branch (AddValueToForm, ShouldSkipFormField, AddCollectionToForm). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
DocumentProcessor.Process (cyclomatic 24) Src/Swagger/DocumentProcessor.cs:40— DocumentProcessor.Process has cyclomatic complexity 24 (threshold 15). Of this number, 17 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HttpClientExtensions.GetValueAsString (cyclomatic 23) Src/Library/Testing/HttpClientExtensions.cs:1051— HttpClientExtensions.GetValueAsString has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 2 function items inside it that branch (ToInvariantIsoString, TryGetParsableString). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
AgentRequestBuilder.BuildRequest (cyclomatic 23) Src/Agents/Shared/AgentRequestBuilder.cs:28— AgentRequestBuilder.BuildRequest has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OperationProcessor.CreateParam (cyclomatic 23) Src/Swagger/OperationProcessor.cs:564— OperationProcessor.CreateParam has cyclomatic complexity 23 (threshold 15). 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.
EndpointData.BuildEndpointDefinitions (cyclomatic 22) Src/Library/Main/EndpointData.cs:51— EndpointData.BuildEndpointDefinitions has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 118). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
SchemaPlaceholderBuilder.Build (cyclomatic 22) Src/OpenApi/Export/SchemaPlaceholderBuilder.cs:16— SchemaPlaceholderBuilder.Build has cyclomatic complexity 22 (threshold 15). 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.
OperationMetadataTransformer.ApplyAutoTag (cyclomatic 22) Src/OpenApi/Operations/Metadata/OperationTransformer.Metadata.cs:15— OperationMetadataTransformer.ApplyAutoTag has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Endpoint.ExecAsync (cyclomatic 21) Src/Library/Endpoint/Endpoint.cs:55— Endpoint.ExecAsync has cyclomatic complexity 21 (threshold 15). 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.
.GenerateSampleJsonNode (cyclomatic 21) Src/OpenApi/Schemas/OpenApiSampleGenerator.cs:40— .GenerateSampleJsonNode has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ValidationSchemaProcessor.CreateDefaultRules (cyclomatic 20) Src/Swagger/ValidationSchemaProcessor.cs:239— ValidationSchemaProcessor.CreateDefaultRules has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 336, 309, 367, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AssemblyScanner.ScanForTypes (cyclomatic 19) Src/Core/AssemblyScanner/AssemblyScanner.cs:32— AssemblyScanner.ScanForTypes has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (IsTypeMatch, ImplementsAny, a function literal at line 51). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Program.ResolveTypeName (cyclomatic 19) Src/Generator.Cli/Program.TypeResolution.cs:31— Program.ResolveTypeName has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Program.ResolveFullTypeExpression (cyclomatic 19) Src/Generator.Cli/Program.TypeResolution.cs:326— Program.ResolveFullTypeExpression has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JobQueue.ExecuteCommand (cyclomatic 19) Src/JobQueues/JobQueue.cs:345— JobQueue.ExecuteCommand has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Endpoint.ValidateRequest (cyclomatic 19) Src/Library/Endpoint/Endpoint.Validation.cs:13— Endpoint.ValidateRequest has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (ValidateRecursively, AppendToPropertyPath). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
RequestBinder.BindFormValues (cyclomatic 18) Src/Library/Binder/RequestBinder.cs:304— RequestBinder.BindFormValues has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
A2AJsonRpcEndpoint.HandleAsync (cyclomatic 18) Src/Agents/A2A/A2AJsonRpcEndpoint.cs:11— A2AJsonRpcEndpoint.HandleAsync has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
GenericProcessorTypesGenerator.Transform (cyclomatic 17) Src/Generator/GenericProcessorTypesGenerator.cs:37— GenericProcessorTypesGenerator.Transform has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
.ValueParser (cyclomatic 17) Src/Library/Binder/BinderExtensions.cs:108— .ValueParser has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function items inside it that branch (GetOrCompileParser, a function literal at line 129). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
HttpClientExtensions.HasCompatibleDtoShape::HasCompatibleShape (cyclomatic 17) Src/Library/Testing/HttpClientExtensions.cs:759— HttpClientExtensions.HasCompatibleDtoShape::HasCompatibleShape has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
X402Middleware.TryValidatePayload (cyclomatic 17) Src/Library/X402/X402Middleware.cs:173— X402Middleware.TryValidatePayload has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RequestOperationTransformer.CreateSampleFromSchema (cyclomatic 17) Src/OpenApi/Operations/OperationTransformer.RequestExamples.cs:172— RequestOperationTransformer.CreateSampleFromSchema has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RequestOperationTransformer.ApplyBodySchemaMetadata (cyclomatic 17) Src/OpenApi/Operations/OperationTransformer.Requests.cs:168— RequestOperationTransformer.ApplyBodySchemaMetadata has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OpenApiSchemaGraphTransformer.TransformDocumentSchemas (cyclomatic 17) Src/OpenApi/Schemas/OpenApiSchemaGraphTransformer.cs:7— OpenApiSchemaGraphTransformer.TransformDocumentSchemas has cyclomatic complexity 17 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
JwtRevocationMiddleware.Invoke (cyclomatic 17) Src/Security/Revocation/JwtRevocationMiddleware.cs:25— JwtRevocationMiddleware.Invoke has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EndpointInvoker.InvokeAsync (cyclomatic 17) Src/Agents/Shared/EndpointInvoker.cs:28— EndpointInvoker.InvokeAsync has cyclomatic complexity 17 (threshold 15). 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.
FluentValidationSchemaEnricher.Enrich (cyclomatic 17) Src/Agents/Shared/FluentValidationSchemaEnricher.cs:30— FluentValidationSchemaEnricher.Enrich has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RequestBinder.BindAsync (cyclomatic 16) Src/Library/Binder/RequestBinder.cs:235— RequestBinder.BindAsync has cyclomatic complexity 16 (threshold 15). 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.
EndpointExtensions.Initialize (cyclomatic 16) Src/Library/Endpoint/Auxiliary/EndpointExtensions.cs:27— EndpointExtensions.Initialize has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainExtensions.BuildRoute (cyclomatic 16) Src/Library/Main/MainExtensions.cs:158— MainExtensions.BuildRoute has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EventDeliveryAckDispatcher.RunAsync (cyclomatic 16) Src/Messaging/Messaging.Remote/Server/Events/EventDeliveryAckDispatcher.cs:12— EventDeliveryAckDispatcher.RunAsync has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ReflectionExtension.IsSubClassOfGeneric (cyclomatic 16) Src/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs:8— ReflectionExtension.IsSubClassOfGeneric has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
No assertions: Void Tests/IntegrationTests/FastEndpoints/RPCTests/VoidCommand.cs:5— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D17 · Explicit Debt· BareSuppressMessage repeated 10 times in 7 files · ×1
BareSuppressMessage repeated 10 times in 7 files Src/Agents/A2A/A2AInvocationResultMapper.cs:93— The identical BareSuppressMessage (`SuppressMessage`) appears 10 times in 7 files — one decision applied repeatedly (e.g. the same rule silenced on every overload of a fluent API), not 10 independent debts. Decide it once — at the type or project level, or by fixing the underlying pattern — rather than occurrence-by-occurrence. (Every occurrence still counts toward the score and metrics.)
BareSuppressMessage repeated across 39 files Src/AspVersioning/Extensions.cs:20— The identical BareSuppressMessage (`UnconditionalSuppressMessage`) appears in 39 files (94 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 94 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
EndpointRouteMapper.Map (cognitive 82) REDACTED:18— EndpointRouteMapper.Map has cognitive complexity 82 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventExecutorWorker.RunAsync (cognitive 67) Src/Messaging/Messaging.Remote.Core/Client/Events/EventExecutorWorker.cs:15— EventExecutorWorker.RunAsync has cognitive complexity 67 (threshold 15). Of this number, 66 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypeInfo.TypeInfo.ctor (cognitive 62) Src/Generator/ReflectionGenerator.cs:234— TypeInfo.TypeInfo.ctor has cognitive complexity 62 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JobQueue.CommandExecutorTask (cognitive 62) Src/JobQueues/JobQueue.cs:233— JobQueue.CommandExecutorTask has cognitive complexity 62 (threshold 15). Of this number, 57 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComplexSourceBinder.BindPropertiesRecursively (cognitive 48) Src/Library/Binder/ComplexSourceBinder.cs:50— ComplexSourceBinder.BindPropertiesRecursively has cognitive complexity 48 (threshold 15). Most of this is not in the body itself: 15 of the 48 points are its own statements and the rest belongs to 7 function items inside it that branch (BindSimpleCollection, BindFormFileCollectionProp, BindComplexCollection, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
.GetTestUrlFor (cognitive 48) Src/Library/Testing/HttpClientExtensions.cs:613— .GetTestUrlFor has cognitive complexity 48 (threshold 15). Of this number, 47 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestBinder.RequestBinder.ctor (cognitive 42) Src/Library/Binder/RequestBinder.cs:42— RequestBinder.RequestBinder.ctor has cognitive complexity 42 (threshold 15). Of this number, 38 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentRequestBuilder.BuildRequest (cognitive 41) Src/Agents/Shared/AgentRequestBuilder.cs:28— AgentRequestBuilder.BuildRequest has cognitive complexity 41 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EndpointData.BuildEndpointDefinitions (cognitive 37) Src/Library/Main/EndpointData.cs:51— EndpointData.BuildEndpointDefinitions has cognitive complexity 37 (threshold 15). Of this number, 26 points are the body's own statements and 11 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HttpClientExtensions.AddObjectToForm (cognitive 37) Src/Library/Testing/HttpClientExtensions.cs:906— HttpClientExtensions.AddObjectToForm has cognitive complexity 37 (threshold 15). Of this number, 16 points are the body's own statements and 21 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OperationMetadataTransformer.ApplyAutoTag (cognitive 35) Src/OpenApi/Operations/Metadata/OperationTransformer.Metadata.cs:15— OperationMetadataTransformer.ApplyAutoTag has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestBinder.BindFormValues (cognitive 34) Src/Library/Binder/RequestBinder.cs:304— RequestBinder.BindFormValues has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocumentProcessor.Process (cognitive 33) Src/Swagger/DocumentProcessor.cs:40— DocumentProcessor.Process has cognitive complexity 33 (threshold 15). Of this number, 27 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestOperationTransformer.ApplyBodySchemaMetadata (cognitive 32) Src/OpenApi/Operations/OperationTransformer.Requests.cs:168— RequestOperationTransformer.ApplyBodySchemaMetadata has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JwtRevocationMiddleware.Invoke (cognitive 30) Src/Security/Revocation/JwtRevocationMiddleware.cs:25— JwtRevocationMiddleware.Invoke has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.BuildAnalysisInputs (cognitive 29) Src/Generator.Cli/Program.SourceParsing.cs:25— Program.BuildAnalysisInputs has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.ApplyGenericParameterMap (cognitive 28) Src/Generator.Cli/Program.TypeResolution.cs:225— Program.ApplyGenericParameterMap has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.ResolveFullTypeExpression (cognitive 27) Src/Generator.Cli/Program.TypeResolution.cs:326— Program.ResolveFullTypeExpression has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ValidationSchemaApplier.RecurseComposite (cognitive 27) Src/OpenApi/Validation/ValidationSchemaApplier.cs:81— ValidationSchemaApplier.RecurseComposite has cognitive complexity 27 (threshold 15). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 100). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ReflectionExtension.IsSubClassOfGeneric (cognitive 26) Src/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs:8— ReflectionExtension.IsSubClassOfGeneric has cognitive complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JobQueue.ExecuteCommand (cognitive 25) Src/JobQueues/JobQueue.cs:345— JobQueue.ExecuteCommand has cognitive complexity 25 (threshold 15). Of this number, 23 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Endpoint.ExecAsync (cognitive 25) Src/Library/Endpoint/Endpoint.cs:55— Endpoint.ExecAsync has cognitive complexity 25 (threshold 15). 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
EventDeliveryAckDispatcher.RunAsync (cognitive 25) Src/Messaging/Messaging.Remote/Server/Events/EventDeliveryAckDispatcher.cs:12— EventDeliveryAckDispatcher.RunAsync has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SchemaPlaceholderBuilder.Build (cognitive 25) Src/OpenApi/Export/SchemaPlaceholderBuilder.cs:16— SchemaPlaceholderBuilder.Build has cognitive complexity 25 (threshold 15). 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.
DocumentSchemaHelpers.DeduplicateOperationSchemaVariants (cognitive 25) Src/OpenApi/Schemas/DocumentSchemaHelpers.cs:150— DocumentSchemaHelpers.DeduplicateOperationSchemaVariants has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
.GenerateSampleJsonNode (cognitive 25) Src/OpenApi/Schemas/OpenApiSampleGenerator.cs:40— .GenerateSampleJsonNode has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenApiSchemaGraphTransformer.TransformDocumentSchemas (cognitive 25) Src/OpenApi/Schemas/OpenApiSchemaGraphTransformer.cs:7— OpenApiSchemaGraphTransformer.TransformDocumentSchemas has cognitive complexity 25 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
FluentValidationSchemaEnricher.Enrich (cognitive 25) Src/Agents/Shared/FluentValidationSchemaEnricher.cs:30— FluentValidationSchemaEnricher.Enrich has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReflectionExtension.IsSubClassOfGeneric (cognitive 25) Src/Swagger/ValidationProcessor/Extensions/ReflectionExtensions.cs:7— ReflectionExtension.IsSubClassOfGeneric has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocumentVersionFilter.Apply (cognitive 24) Src/OpenApi/Documents/DocumentVersionFilter.cs:37— DocumentVersionFilter.Apply has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OperationProcessor.CreateParam (cognitive 24) Src/Swagger/OperationProcessor.cs:564— OperationProcessor.CreateParam has cognitive complexity 24 (threshold 15). 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ValidationSchemaProcessor.ApplyValidationRule (cognitive 24) Src/Swagger/ValidationSchemaProcessor.cs:174— ValidationSchemaProcessor.ApplyValidationRule has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.ResolveTypeName (cognitive 23) Src/Generator.Cli/Program.TypeResolution.cs:31— Program.ResolveTypeName has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.ShouldSkipType (cognitive 23) Src/Generator.Cli/Program.TypeResolution.cs:115— Program.ShouldSkipType has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OperationProcessor.AddAttributeBasedParameters (cognitive 23) Src/Swagger/OperationProcessor.cs:295— OperationProcessor.AddAttributeBasedParameters has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ValidationSchemaProcessor.CreateDefaultRules (cognitive 23) Src/Swagger/ValidationSchemaProcessor.cs:239— ValidationSchemaProcessor.CreateDefaultRules has cognitive complexity 23 (threshold 15). None of this is in the body itself: all 23 points belong to 6 function literals inside it that branch (lines 367, 336, 309, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
.IsMalformedJsonArrayString (cognitive 22) Src/Library/Binder/BinderExtensions.cs:437— .IsMalformedJsonArrayString has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResponseOperationTransformer.ApplyParamDescriptions (cognitive 22) Src/OpenApi/Operations/OperationTransformer.Responses.cs:161— ResponseOperationTransformer.ApplyParamDescriptions has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestParameterMetadataApplicator.Apply (cognitive 22) Src/OpenApi/Operations/Parameters/RequestParameterMetadataApplicator.cs:15— RequestParameterMetadataApplicator.Apply has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenApiSchemaReferenceCollector.CollectReferencedSchemas (cognitive 22) Src/OpenApi/Schemas/OpenApiSchemaReferenceCollector.cs:29— OpenApiSchemaReferenceCollector.CollectReferencedSchemas has cognitive complexity 22 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Program.ReadNuGetPackageCompileAssemblies (cognitive 21) REDACTED:48— Program.ReadNuGetPackageCompileAssemblies has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReflectionGenerator.RenderClass (cognitive 21) Src/Generator/ReflectionGenerator.cs:63— ReflectionGenerator.RenderClass has cognitive complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EndpointExtensions.Initialize (cognitive 21) Src/Library/Endpoint/Auxiliary/EndpointExtensions.cs:27— EndpointExtensions.Initialize has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XmlDocSchemaTransformer.TransformAsync (cognitive 21) Src/OpenApi/Schemas/Transformers/XmlDocSchemaTransformer.cs:9— XmlDocSchemaTransformer.TransformAsync has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssemblyScanner.ScanForTypes (cognitive 20) Src/Core/AssemblyScanner/AssemblyScanner.cs:32— AssemblyScanner.ScanForTypes has cognitive complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 3 function items inside it that branch (IsTypeMatch, ImplementsAny, a function literal at line 51). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Program.SplitBalanced (cognitive 20) Src/Generator.Cli/Program.EndpointDiscovery.cs:156— Program.SplitBalanced has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.SelectAssetsTargetKey (cognitive 20) REDACTED:115— Program.SelectAssetsTargetKey has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
.AddSwaggerDefaults (cognitive 20) Src/Library/Main/EndpointProducesMetadata.cs:12— .AddSwaggerDefaults has cognitive complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function literal 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
EndpointProducesMetadata.RouteParamNames (cognitive 20) Src/Library/Main/EndpointProducesMetadata.cs:121— EndpointProducesMetadata.RouteParamNames has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IdempotencyPolicy.CacheRequestAsync (cognitive 20) Src/Library/Middleware/Idempotency/IdempotencyPolicy.cs:12— IdempotencyPolicy.CacheRequestAsync has cognitive complexity 20 (threshold 15). 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
OpenApiSchemaGraphTransformer.RewritePathItemSchemas (cognitive 20) Src/OpenApi/Schemas/OpenApiSchemaGraphTransformer.cs:61— OpenApiSchemaGraphTransformer.RewritePathItemSchemas has cognitive complexity 20 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
OpenApiSchemaReferenceCollector.CollectPathItemRefs (cognitive 20) Src/OpenApi/Schemas/OpenApiSchemaReferenceCollector.cs:77— OpenApiSchemaReferenceCollector.CollectPathItemRefs has cognitive complexity 20 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
AppFixture.EnumerateProjectBuildInputs (cognitive 20) Src/Testing/AppFixture.Aot.cs:298— AppFixture.EnumerateProjectBuildInputs has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentRequestBuilder.AddQueryValues (cognitive 20) Src/Agents/Shared/AgentRequestBuilder.cs:209— AgentRequestBuilder.AddQueryValues has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.ProcessTypeExpression (cognitive 19) Src/Generator.Cli/Program.TypeResolution.cs:271— Program.ProcessTypeExpression has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GenericProcessorTypesGenerator.Transform (cognitive 19) Src/Generator/GenericProcessorTypesGenerator.cs:37— GenericProcessorTypesGenerator.Transform has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
.ValueParser (cognitive 19) Src/Library/Binder/BinderExtensions.cs:108— .ValueParser has cognitive complexity 19 (threshold 15). None of this is in the body itself: all 19 points belong to 2 function items inside it that branch (GetOrCompileParser, a function literal at line 129). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
MainExtensions.BuildRoute (cognitive 19) Src/Library/Main/MainExtensions.cs:158— MainExtensions.BuildRoute has cognitive complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OperationProcessor.BuildRequestParamDescriptions (cognitive 19) Src/Swagger/OperationProcessor.cs:881— OperationProcessor.BuildRequestParamDescriptions has cognitive complexity 19 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
OperationProcessor.ApplyRequestExamples (cognitive 19) Src/Swagger/OperationProcessor.cs:966— OperationProcessor.ApplyRequestExamples has cognitive complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Endpoint.ValidateRequest::ValidateRecursively (cognitive 18) Src/Library/Endpoint/Endpoint.Validation.cs:36— Endpoint.ValidateRequest::ValidateRecursively has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocumentPolymorphicOneOf.Apply (cognitive 18) Src/OpenApi/Documents/DocumentPolymorphicOneOf.cs:12— DocumentPolymorphicOneOf.Apply has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PropertyNameResolver.ConvertPropertyPath (cognitive 18) Src/OpenApi/Infrastructure/PropertyNameResolver.cs:23— PropertyNameResolver.ConvertPropertyPath has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestOperationTransformer.CreateSampleFromSchema (cognitive 18) Src/OpenApi/Operations/OperationTransformer.RequestExamples.cs:172— RequestOperationTransformer.CreateSampleFromSchema has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenApiSchemaTraversal.RewriteChildSchemas (cognitive 18) Src/OpenApi/Schemas/OpenApiSchemaTraversal.cs:92— OpenApiSchemaTraversal.RewriteChildSchemas has cognitive complexity 18 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
AgentPublishedNameResolver.SanitizeGenerated (cognitive 18) Src/Agents/Shared/AgentPublishedNameResolver.cs:42— AgentPublishedNameResolver.SanitizeGenerated has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NuGetPackageTypeLoader.ResolveFullNameCore (cognitive 17) Src/Generator.Cli/NuGetPackageTypeLoader.cs:139— NuGetPackageTypeLoader.ResolveFullNameCore has cognitive complexity 17 (threshold 15). 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.
AccessControlGenerator.Initialize (cognitive 17) Src/Generator/AccessControlGenerator.cs:27— AccessControlGenerator.Initialize has cognitive complexity 17 (threshold 15). None of this is in the body itself: all 17 points belong to 7 function items inside it that branch (TransformCustom, GetStringConstants, TryGetStringConstant, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
.ComplexBindMeta (cognitive 17) Src/Library/Binder/BinderExtensions.cs:222— .ComplexBindMeta has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RequestBinder.BindUserClaims (cognitive 17) Src/Library/Binder/RequestBinder.cs:465— RequestBinder.BindUserClaims has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EndpointSecurityPolicies.AddSecurityPolicy (cognitive 17) Src/Library/Main/EndpointSecurityPolicies.cs:34— EndpointSecurityPolicies.AddSecurityPolicy has cognitive complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 41, 52, 60, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
HttpClientExtensions.HasCompatibleDtoShape (cognitive 17) Src/Library/Testing/HttpClientExtensions.cs:755— HttpClientExtensions.HasCompatibleDtoShape has cognitive complexity 17 (threshold 15). None of this is in the body itself: all 17 points belong to 2 function items inside it that branch (HasCompatibleShape, TryBuildDtoPropertyMap). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
RequestBodyOverrideApplicator.Apply (cognitive 17) Src/OpenApi/Operations/Requests/RequestBodyOverrideApplicator.cs:9— RequestBodyOverrideApplicator.Apply has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ValidationSchemaMutation.ResolveItemsSchema (cognitive 17) Src/OpenApi/Validation/ValidationSchemaMutation.cs:40— ValidationSchemaMutation.ResolveItemsSchema has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
A2AJsonRpcEndpoint.HandleAsync (cognitive 17) Src/Agents/A2A/A2AJsonRpcEndpoint.cs:11— A2AJsonRpcEndpoint.HandleAsync has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
McpStructuredContentMapper.ValidateJsonObject (cognitive 17) Src/Agents/Mcp/McpStructuredContentMapper.cs:84— McpStructuredContentMapper.ValidateJsonObject has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SchemaNameGenerator.Generate (cognitive 17) Src/Swagger/SchemaNameGenerator.cs:15— SchemaNameGenerator.Generate has cognitive complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (GenericArgString, TypeNameWithoutGenericArgs). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ParentPrefixIndex.EnsureInitialized (cognitive 16) Src/Library/Binder/IPrefixedValueSource.cs:132— ParentPrefixIndex.EnsureInitialized has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestBinder.BindAsync (cognitive 16) Src/Library/Binder/RequestBinder.cs:235— RequestBinder.BindAsync has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
RequestBinder.Bind (cognitive 16) Src/Library/Binder/RequestBinder.cs:435— RequestBinder.Bind has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OpenApiExporter.ExportRequestedFormatsAsync (cognitive 16) Src/OpenApi/Export/OpenApiExporter.cs:31— OpenApiExporter.ExportRequestedFormatsAsync has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestOperationTransformer.HandleParameters (cognitive 16) Src/OpenApi/Operations/OperationTransformer.Requests.cs:60— RequestOperationTransformer.HandleParameters has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResponseOperationTransformer.FixBinaryFormats (cognitive 16) Src/OpenApi/Operations/OperationTransformer.Responses.cs:77— ResponseOperationTransformer.FixBinaryFormats has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EndpointInvoker.InvokeAsync (cognitive 16) Src/Agents/Shared/EndpointInvoker.cs:28— EndpointInvoker.InvokeAsync has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
FluentValidationSchemaEnricher.ParsePropertyPath (cognitive 16) Src/Agents/Shared/FluentValidationSchemaEnricher.cs:146— FluentValidationSchemaEnricher.ParsePropertyPath has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Extensions.GetAllRequestProperties (cognitive 16) Src/Swagger/Extensions.cs:423— Extensions.GetAllRequestProperties has cognitive complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function items inside it that branch (TraverseProperties, IsCollectionType). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassTooLong: RequestBinder Src/Library/Binder/RequestBinder.cs— ClassTooLong — 408 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 8 over it, 1.02× 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.
Duplicated block (31 lines × 2) Src/Agents/A2A/A2ASkillAttribute.cs:17— Src/Agents/A2A/A2ASkillAttribute.cs:17-47 | Src/Agents/A2A/A2ASkillInfo.cs:19-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (20 lines × 2) Src/Generator.Cli/Program.TypeResolution.cs:362— Src/Generator.Cli/Program.TypeResolution.cs:362-381 | Src/Generator.Cli/Program.TypeResolution.cs:418-437 — 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/Generator.Cli/Program.TypeResolution.cs:362` 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 (19 lines × 2) Src/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs:59— Src/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs:59-77 | Src/Swagger/ValidationProcessor/Extensions/ReflectionExtensions.cs:58-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) Src/Messaging/Messaging.Core/Interfaces/ICommandReceiver.cs:35— Src/Messaging/Messaging.Core/Interfaces/ICommandReceiver.cs:35-48 | Src/Messaging/Messaging.Core/Interfaces/IEventReceiver.cs:35-48 — 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. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `match` to `Func<TCommand, bool>` in one and `Func<TEvent, bool>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) Src/OpenApi/Documents/DocumentVersionFilter.cs:21— Src/OpenApi/Documents/DocumentVersionFilter.cs:21-31 | Src/Swagger/DocumentProcessor.cs:22-32 — 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.
Duplicated block (10 lines × 2) Src/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs:20— Src/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs:20-29 | Src/Swagger/ValidationProcessor/Extensions/ReflectionExtensions.cs:17-26 — 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/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs:20` 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 before the matched lines, `Src/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs:18` calls `GetFullTypeDefinition` and `Src/Swagger/ValidationProcessor/Extensions/ReflectionExtensions.cs:15` does not — after which the two agree again for 4 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 (11–12 lines × 2) Src/Messaging/Messaging.Remote.Core/Client/Events/EventDeliveryAckSubscriber.cs:8— Src/Messaging/Messaging.Remote.Core/Client/Events/EventDeliveryAckSubscriber.cs:8-19 | Src/Messaging/Messaging.Remote.Core/Client/Events/EventSubscriber.cs:13-23 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Src/Messaging/Messaging.Remote.Core/Client/Events/EventDeliveryAckSubscriber.cs:8` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Src/OpenApi/Infrastructure/LoggingExtensions.cs:7— Src/OpenApi/Infrastructure/LoggingExtensions.cs:7-11 | Src/Swagger/LoggingExtensions.cs:10-14 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Src/Swagger/LoggingExtensions.cs:7` calls `LoggerMessage`, `NoValidatorsFound` and `Src/OpenApi/Infrastructure/LoggingExtensions.cs:6` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) Src/Generator.Cli/Program.SourceParsing.cs:174— Src/Generator.Cli/Program.SourceParsing.cs:174-179 | Src/Generator.Cli/Program.SourceParsing.cs:205-210 — 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/Generator.Cli/Program.SourceParsing.cs:174` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) Src/Messaging/Messaging.Remote.Core/Client/Events/Storage/EventSubscriberStorage.cs:15— Src/Messaging/Messaging.Remote.Core/Client/Events/Storage/EventSubscriberStorage.cs:15-38 | Src/Messaging/Messaging.Remote/Server/Events/Storage/EventHubStorage.cs:15-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 6) Src/Library/Extensions/HttpResponseExtensions.cs:465— Src/Library/Extensions/HttpResponseExtensions.cs:465-471 | Src/Library/Extensions/HttpResponseExtensions.cs:498-504 | Src/Library/Extensions/HttpResponseExtensions.cs:512-518 | Src/Library/Extensions/HttpResponseExtensions.cs:526-532 | Src/Library/Extensions/HttpResponseExtensions.cs:540-546 | Src/Library/Extensions/HttpResponseExtensions.cs:727-733 — all 6 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) TestHarness/Web/[Features]/Customers/Create/Endpoint.cs:5— TestHarness/Web/[Features]/Customers/Create/Endpoint.cs:5-20 | TestHarness/Web/[Features]/Customers/CreateWithPropertiesDI/Endpoint.cs:5-20 — 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 `TestHarness/Web/[Features]/Customers/Create/Endpoint.cs:5` 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.
Coverage not measured — no coverage collector is wired up — 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.
Hollow method — returns a constant without doing the work TestHarness/Web/[Features]/Customers/[EventHandlers]/SendOrderConfirmation.cs:7— `HandleAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
P12 · CI test-gate honesty· Test suite runs only after the merge · ×1
Test suite runs only after the merge — `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
Outbound HTTP without resilience Src/Testing/AppFixture.Aot.cs:473— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Token validation disabled Src/Security/AuthExtensions.cs:39— `ValidateAudience`, `ValidateIssuer` are all set to `false`, which means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent.
Sync-over-async (deadlock risk) through `.Result` Src/Testing/AppFixture.Aot.cs:65— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
X18 · Disposal-pattern correctness· Finalizer on a type that owns no unmanaged resource · ×1
Finalizer on a type that owns no unmanaged resource Src/Library/Endpoint/Auxiliary/HitCounter.cs:115— `Counter` declares a finalizer (line 115), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
X18 · Disposal-pattern correctness· DI scope created and never disposed · ×1
DI scope created and never disposed REDACTED:175— `app.Services.CreateScope()` (line 175) creates an `IServiceScope`, and it is dropped: `CreateScope().ServiceProvider` never names the scope, so nothing can release it. A scope owns every scoped service resolved from it — the `DbContext`, its connection, anything registered `AddScoped` — and releases them only when the scope itself is disposed; nothing here ever does, so each scope's services stay alive until the process ends. Create it with `using var scope = …CreateScope();` (or `await using` for `CreateAsyncScope`), or, when it must outlive the method, dispose it from the owning type's `Dispose`.
X2 · Cancellation propagation· Async local function without CancellationToken · ×1
Async local function without CancellationToken: DrainExecutionsAsync Src/Messaging/Messaging.Remote.Core/Client/Events/EventExecutorWorker.cs:144— 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.
Commented-out code Src/Library/Endpoint/Auxiliary/HitCounter.cs:61— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Library/Endpoint/Auxiliary/HitCounter.cs:67— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Library/Endpoint/Auxiliary/HitCounter.cs:71— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Library/Endpoint/Auxiliary/HitCounter.cs:79— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Library/Endpoint/Auxiliary/HitCounter.cs:85— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Library/Endpoint/Auxiliary/HitCounter.cs:90— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Swagger/DocumentProcessor.cs:102— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Swagger/DocumentProcessor.cs:103— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Swagger/DocumentProcessor.cs:104— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Swagger/ValidationSchemaProcessor.cs:269— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Swagger/ValidationSchemaProcessor.cs:273— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Swagger/ValidationSchemaProcessor.cs:274— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Swagger/ValidationSchemaProcessor.cs:297— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Swagger/ValidationSchemaProcessor.cs:301— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Src/Swagger/ValidationSchemaProcessor.cs:302— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code TestHarness/Web/DocumentRegistration.cs:166— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code TestHarness/Web/DocumentRegistration.cs:167— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code TestHarness/Web/DocumentRegistration.cs:168— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code TestHarness/Web/DocumentRegistration.cs:174— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code TestHarness/Web/DocumentRegistration.cs:175— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code TestHarness/Web/DocumentRegistration.cs:176— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code TestHarness/Web/DocumentRegistration.cs:177— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code TestHarness/Web/DocumentRegistration.cs:183— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code TestHarness/Web/DocumentRegistration.cs:198— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code TestHarness/Web/DocumentRegistration.cs:199— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Duplicated predicate Src/Messaging/Messaging.Core/Interfaces/ICommandReceiver.cs:37— `!ct.IsCancellationRequested && DateTime.Now.Subtract(start).TotalSeconds < timeoutSeconds` appears character-identically in 2 files — Src/Messaging/Messaging.Core/Interfaces/ICommandReceiver.cs, Src/Messaging/Messaging.Core/Interfaces/IEventReceiver.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 TestHarness/NativeAotChecker/Endpoints/Jobs/JobQueueEndpoint.cs:24— `!ct.IsCancellationRequested && result is null` appears character-identically in 2 files — TestHarness/NativeAotChecker/Endpoints/Jobs/JobQueueEndpoint.cs, TestHarness/NativeAotChecker/Endpoints/Jobs/JobQueueIdempotencyEndpoint.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/Generator/DiscoveredTypesGenerator.cs:69— `a.AttributeClass!.Name == DontRegisterAttribute || type.AllInterfaces.Length == 0` appears character-identically in 2 files — Src/Generator/DiscoveredTypesGenerator.cs, Src/Generator/ReflectionGenerator.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/OpenApi/Operations/OperationTransformer.Requests.cs:364— `cAttrib.IsRequired || cAttrib.RemoveFromSchema` appears character-identically in 2 files — Src/OpenApi/Operations/OperationTransformer.Requests.cs, Src/Swagger/OperationProcessor.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/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs:23— `child != null && child != typeof(object)` appears character-identically in 2 files — Src/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs, Src/Swagger/ValidationProcessor/Extensions/ReflectionExtensions.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/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs:67— `childArguments[i].Assembly == parentArguments[i].Assembly && childArguments[i].Name == parentArguments[i].Name && childArguments[i].Namespac…` appears character-identically in 2 files — Src/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs, Src/Swagger/ValidationProcessor/Extensions/ReflectionExtensions.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/OpenApi/ValidationProcessor/Extensions/ValidationExtensions.cs:102— `component.HasCondition || component.HasAsyncCondition` appears character-identically in 2 files — Src/OpenApi/ValidationProcessor/Extensions/ValidationExtensions.cs, Src/Swagger/ValidationProcessor/Extensions/ValidationExtensions.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/Generator/DiscoveredTypesGenerator.cs:67— `ctx.SemanticModel.GetDeclaredSymbol(ctx.Node) is not ITypeSymbol type || type.IsAbstract || type.GetAttributes().Any(a => a.AttributeClass!.…` appears character-identically in 2 files — Src/Generator/DiscoveredTypesGenerator.cs, Src/Generator/ReflectionGenerator.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/OpenApi/Operations/OperationTransformer.Requests.cs:353— `hAttrib.IsRequired || hAttrib.RemoveFromSchema` appears character-identically in 2 files — Src/OpenApi/Operations/OperationTransformer.Requests.cs, Src/Swagger/OperationProcessor.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/Generator/AccessControlGenerator.cs:599— `i < base64Hash.Length && count < code.Length` appears character-identically in 2 files — Src/Generator/AccessControlGenerator.cs, Src/Library/Endpoint/Endpoint.Base.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/Library/Extensions/ReflectionExtensions.cs:100— `i.IsGenericType && i.GetGenericTypeDefinition() == typeof(IEnumerable<>)` appears character-identically in 2 files — Src/Library/Extensions/ReflectionExtensions.cs, Src/Messaging/Messaging.Remote.Reflection/ProtobufMarshaller.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 TestHarness/Web/[Features]/TestCases/Messaging/JobQueueTest/TestStorageProvider.cs:31— `j.QueueID == r.QueueID && j.IdempotencyKey == key` appears character-identically in 2 files — TestHarness/NativeAotChecker/Endpoints/Jobs/JobQueueEndpoint.cs, TestHarness/Web/[Features]/TestCases/Messaging/JobQueueTest/TestStorageProvider.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/Messaging/Messaging.Remote.Reflection/ProtobufMarshaller.cs:130— `p is { CanRead: true, CanWrite: true } && p.GetIndexParameters().Length == 0` appears character-identically in 2 files — Src/Messaging/Messaging.Remote.Reflection/ProtobufMarshaller.cs, Src/OpenApi/Schemas/OpenApiSchemaExtensions.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/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs:20— `parameters is { Length: > 0 } && (parameters[0].Attributes & TypeAttributes.BeforeFieldInit) == TypeAttributes.BeforeFieldInit` appears character-identically in 2 files — Src/OpenApi/ValidationProcessor/Extensions/ReflectionExtensions.cs, Src/Swagger/ValidationProcessor/Extensions/ReflectionExtensions.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/Messaging/Messaging.Remote.Core/Client/Events/Storage/EventSubscriberRetentionPolicy.cs:33— `r.IsComplete || DateTime.UtcNow >= r.ExpireOn` appears character-identically in 2 files — Src/Messaging/Messaging.Remote.Core/Client/Events/Storage/EventSubscriberRetentionPolicy.cs, Src/Messaging/Messaging.Remote/Server/Events/Storage/EventHubStorage.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/OpenApi/ValidationProcessor/Extensions/ValidationExtensions.cs:91— `validationRule.Member is null || string.IsNullOrEmpty(validationRule.PropertyName)` appears character-identically in 2 files — Src/OpenApi/ValidationProcessor/Extensions/ValidationExtensions.cs, Src/Swagger/ValidationProcessor/Extensions/ValidationExtensions.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.
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 Benchmark/FastEndpointsBench/Program.cs:4— 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.
No security response headers detected Benchmark/MinimalApi/Program.cs:5— 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.
No security response headers detected Benchmark/MvcControllers/Program.cs:4— 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.
No security response headers detected TestHarness/NativeAotChecker/Program.cs:11— 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.
No security response headers detected TestHarness/OData/Program.cs:8— 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.
No security response headers detected TestHarness/OpenApi.Kiota/Program.cs:8— 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.
No security response headers detected TestHarness/Sandbox/Source/Program.cs:1— 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.
No security response headers detected REDACTED:23— 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.
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 Benchmark/FastEndpointsBench/Program.cs:4— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected Benchmark/MinimalApi/Program.cs:5— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected Benchmark/MvcControllers/Program.cs:4— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected TestHarness/NativeAotChecker/Program.cs:11— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected TestHarness/OData/Program.cs:8— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected TestHarness/OpenApi.Kiota/Program.cs:8— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected TestHarness/Sandbox/Source/Program.cs:1— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected REDACTED:23— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
Silent fallback default in catch Src/Generator.Cli/Program.ProjectInspection.cs:135— `GetRootNamespace` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch Src/Generator.Cli/Program.ProjectInspection.cs:157— `GetTargetFramework` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch Src/Generator.Cli/Program.ProjectInspection.cs:231— `ReadCacheState` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch Src/OpenApi/Schemas/OpenApiJsonHelpers.cs:54— `TrySerializeToNode` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch Src/Swagger/Extensions.cs:377— `GetExampleJToken` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch Src/Swagger/SystemTextJsonUtilities.cs:51— `IsCamelCaseEnumNamingPolicy` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Orphaned file Src/Swagger/SystemTextJsonUtilities.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Src/HealthChecks/HealthChecksExtensions.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Src/Library/Validation/PropertyChainExtensions.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file TestHarness/NativeAotChecker/Endpoints/Commands/GenericCommandHandlerEndpoint.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Interpolated log message defeats structured logging TestHarness/Web/PipelineBehaviors/PostProcessors/MyResponseLogger.cs:12— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging TestHarness/Web/PipelineBehaviors/PreProcessors/MyRequestLogger.cs:10— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging TestHarness/Web/[Features]/Customers/[EventHandlers]/SendOrderConfirmation.cs:9— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging TestHarness/Web/[Features]/Shipping/[EventHandlers]/StartOrderProcessing.cs:9— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Pass-through layer Src/JobQueues/JobTracker.cs:48— JobTracker: all 3 public methods forward their arguments unchanged to JobQueueBase and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call JobQueueBase directly, or give the layer a job.
Pass-through layer Src/Library/Validation/ValidationContext.cs:13— ValidationContext: all 6 public methods forward their arguments unchanged to ValidationFailures and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call ValidationFailures directly, or give the layer a job.
Pass-through layer Src/Library/Validation/ValidationContext.cs:89— ValidationContext: all 3 public methods forward their arguments unchanged to ValidationFailures and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call ValidationFailures directly, or give the layer a job.
IC1 · Incompleteness & stubs· Placeholder data left in code · ×2
Placeholder data left in code TestHarness/NativeAotChecker/Endpoints/SerializerCtxGen/FluentNoReqResMapEndpoint.cs:39— A placeholder value ("John Doe") is still in shipped code — sample/mock data that was never replaced with the real thing.
Placeholder data left in code TestHarness/OData/Model/AppDbContextExtensions.cs:20— A placeholder value ("John Doe") is still in shipped code — sample/mock data that was never replaced with the real thing.
Silent fallback default on parse failure Src/OpenApi/Operations/OperationTransformer.Responses.cs:275— `ParseStatusCode` falls back to `0` when `int.TryParse(statusCode, out var code)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure Src/Swagger/OperationProcessor.cs:1145— `TypeForRouteParam` falls back to `Types.String` when `_paramMap.TryGetValue(paramName, out var tParam)` 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.
C4 · Data Retention· Partial data-retention evidence · ×1
Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
Documentation: contradicts the code .okf/architecture.md— The architecture diagram shows Generator.Cli as a project reference, but the generator tool lives in Src/Generator.Cli. Correct the package graph to reflect the actual location of Generator.Cli.
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/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 46 project(s) overshoot their size bounds, lowering Project Cohesion to 9.1/10. The most over is `Web(net10.0)` (6250 LoC, 290 public types across 77 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 4 of 243 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 243 of the 608 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: Src/Swagger/SystemTextJsonUtilities.cs, Src/HealthChecks/HealthChecksExtensions.cs, Src/Library/Validation/PropertyChainExtensions.cs, TestHarness/NativeAotChecker/Endpoints/Commands/GenericCommandHandlerEndpoint.cs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
IC1 · Incompleteness & stubs· Member throws NotSupportedException · ×1
Member throws NotSupportedException Src/OData/ODataEndpoint.cs:48— `HandleAsync`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional.
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.
README/code drift Src/Generator.Cli/README.md:93— Src/Generator.Cli/README.md installs the package `FastEndpoints.Generator` (`dotnet add package FastEndpoints.Generator`), but no project or props file references it. 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 — 11 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.
Logging is not universal — Only 16/31 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 31, 8 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2227 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 208/284 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.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~1.4 `!` suppressions per 1k syntax nodes — 329 suppression(s) across the 238025 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.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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 120 file(s) — `Benchmark/FastEndpointsBench/CodeGenEndpoint.cs`, `Src/Agents/A2A/A2ASkillCatalog.cs`, `Src/Agents/A2A/A2ASkillDispatcher.cs`, `Src/Agents/A2A/AgentCardBuilder.cs`, `Src/Agents/Mcp/EndpointMcpToolSource.cs`, … (+115 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
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.
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.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a16213-39fa-7718-9254-fe26af662c29 · 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 — 97 field(s) across 5 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.
Issues: 70 · Warnings: 447 · Recommendations: 101 · Info: 42 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 05:26 UTC.
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.