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

MarsonShine/MS.Microservice

Measured 8 November 2026, 12:05 UTC, at code version fca8208

First survey, so nothing to compare with yet Code coverage: not measuredBoundary Type-Coupling: not measured

Code coverage is not measured: Suite not runnable in-image and no committed report.

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

CAI score 49out of 100 At risk

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: 47,904 lines of product code in 116 projects, tests not counted · Estimated rebuild effort: about 1.9 person-years · Weakest lens: Accessibility, 42

Findings by how serious they are

50 critical 615 serious 161 minor

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

This survey was produced by

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

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

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

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

93of 93 dimensions measured by tools.
724of 826 findings point to an exact file and line, so you can open each one in the code. The other 102 concern the repository as a whole, such as missing documentation.
93dimensions across 9 lenses, read from 47,904 lines of product code in 116 projects.
Chapters

Executive summary

MarsonShine/MS.Microservice is rated At risk because critical security findings are open. It scores 49 out of 100, which the At risk rating leaves unchanged.

Accessibility, at 42, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 5 points. Fixing focus, motion and contrast would lift Accessibility itself, worth about 3 points.

Eight known security holes in the packages the code depends on can be used by attackers. Three passwords or keys in the code and three in the code's history are open to anyone who can read the repository, and eighteen errors are caught and ignored, so failures can go unnoticed. Updating the vulnerable packages, replacing each exposed password or key and handling or logging the ignored errors would close these risks. Pinning each tool to an exact version would fix the two pipeline tools referenced by a changeable name, and fixing the weaknesses the scanner points to would deal with the security weakness in the code. The four data fields that are written but never read need removing.

The product code is 47,904 lines, about €280,000 to rebuild.

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Accessibility 42 · counts for 45%Production Readiness 45 · counts for 25%Performance 47 · counts for 14%Code Health 72 · counts for 8%Security and Compliance 80 · counts for 4%Domain Modelling 83 · counts for 2%Maturity 84 · counts for 1%Architecture 85 · counts for 1%Event-Driven 87 · counts for 0%

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

Code composition: what the lines of code are
Business logic 19%Supporting code 26%Tests 50%Generated by tools 5%
Rebuild cost: about €280,000 · Estimate
Cost to rebuild€92,000 to €470,000, for 1,533 to 4,956 hours of work, about 1.9 person-years for 1 to 4 engineers
Difficulty of the problemVery 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 49. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 47,904 lines of product code
Comment linesThe estimate prices 45,204 lines. Comment lines count towards the size of 47,904 lines but aren't priced as work.
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.
Raises the score by about 5 points · Low effort · REDACTED Scanning
2
Resolve the 4 Prerelease dependency finding(s) in Dependency Hygiene.
Raises the score by about 3 points · Low effort · Dependency Hygiene
3
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Raises the score by about 4 points · Medium effort · Async & latency hygiene

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 €280,000 to build again, about 1.9 person-years of work. Its weakest lens is Accessibility, at 42 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 3 REDACTED Scanning 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.

arch Microservice.Documents.Rendering Microservice.Documents.Rendering Microservice.Lab Microservice.Lab ctx:Microservice.AspNetCore Microservice.AspNetCore AspNetCore Microservice.Lab->ctx:Microservice.AspNetCore ctx:Microservice.Audio Microservice.Audio Audio Microservice.Lab->ctx:Microservice.Audio ctx:Microservice.Excel Microservice.Excel Excel Microservice.Lab->ctx:Microservice.Excel ctx:Microservice.Lab Microservice.Lab Domain · Infrastructure · Persistence Microservice.Lab->ctx:Microservice.Lab ctx:Microservice.Logging.AspNetCore Microservice.Logging.AspNetCore AspNetCore Microservice.Lab->ctx:Microservice.Logging.AspNetCore ctx:Microservice.Media Microservice.Media Media Microservice.Lab->ctx:Microservice.Media ctx:Microservice.Reference Microservice.Reference Application · Domain · Persistence Microservice.Lab->ctx:Microservice.Reference Microservice.Lab.DatabaseMigrator Microservice.Lab.DatabaseMigrator Microservice.Lab.DatabaseMigrator->ctx:Microservice.Lab Microservice.Reference.DatabaseMigrator Microservice.Reference.DatabaseMigrator Microservice.Reference.DatabaseMigrator->ctx:Microservice.Reference Microservice.Reference.Web Microservice.Reference.Web Microservice.Reference.Web->ctx:Microservice.AspNetCore Microservice.Reference.Web->ctx:Microservice.Logging.AspNetCore Microservice.Reference.Web->ctx:Microservice.Reference ctx:Microservice.AI.Abstractions Microservice.AI.Abstractions Abstractions ctx:Microservice.AI.Core Microservice.AI.Core Core ctx:Microservice.AI.Core->ctx:Microservice.AI.Abstractions ctx:Microservice.Core Microservice.Core Core ctx:Microservice.AspNetCore->ctx:Microservice.Core ctx:Microservice.Domain.Primitives Microservice.Domain.Primitives Primitives ctx:Microservice.Core->ctx:Microservice.Domain.Primitives ctx:Microservice.Excel->ctx:Microservice.Core ctx:Microservice.Lab->ctx:Microservice.Audio ctx:Microservice.Lab->ctx:Microservice.Core ctx:Microservice.Lab->ctx:Microservice.Domain.Primitives ctx:Microservice.Lab->ctx:Microservice.Excel ctx:Microservice.Logging.Core Microservice.Logging.Core Core ctx:Microservice.Logging.AspNetCore->ctx:Microservice.Logging.Core ctx:Microservice.Messaging.Abstractions Microservice.Messaging.Abstractions Abstractions ctx:Microservice.Messaging.Wolverine Microservice.Messaging.Wolverine Wolverine ctx:Microservice.Messaging.Wolverine->ctx:Microservice.Messaging.Abstractions ctx:Microservice.Reference->ctx:Microservice.Core ctx:Microservice.Reference->ctx:Microservice.Domain.Primitives ctx:Microservice.Reference->ctx:Microservice.Messaging.Abstractions ctx:Microservice.Reference->ctx:Microservice.Messaging.Wolverine __more__ +32 more contexts

Architecture: which parts of the code depend on which

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

129 modules, with 75 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; 89 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 .github.skills.mcp-builder.scripts.connections2 MS.Microservice.AI.Abstractions3 MS.Microservice.AI.QuestionGeneration.Contracts4 MS.Microservice.AI.QuestionGeneration.Serialization5 MS.Microservice.Caching6 MS.Microservice.Core.Common.Advance.Resilience7 MS.Microservice.Core.Domain.Entity.Enums8 MS.Microservice.Core.Domain.Repository.SqlSugar9 MS.Microservice.Core.Functional10 MS.Microservice.Core.IO11 MS.Microservice.Core.Messaging12 MS.Microservice.Core.Specification13 MS.Microservice.Infrastructure.Utils14 MS.Microservice.Media.Images15 MS.Microservice.Messaging16 MS.Microservice.Persistence.EFCore.Auditing17 MS.Microservice.Tasks18 .github.skills.mcp-builder.scripts19 MS.Microservice.AI.Core20 MS.Microservice.AI.QuestionGeneration.AIChat21 MS.Microservice.AI.QuestionGeneration.Pipeline22 MS.Microservice.AI.QuestionGeneration.Prompts23 MS.Microservice.Caching.Redis24 MS.Microservice.Core.Dto25 MS.Microservice.Core.Functional.Data.LinkedList26 MS.Microservice.EventBus.Events27 MS.Microservice.Media.Inference28 MS.Microservice.Messaging.RabbitMQ29 MS.Microservice.Persistence.SqlSugar30 MS.Microservice.AI.DeepSeek31 MS.Microservice.AI.OpenAI32 MS.Microservice.AI.Qwen33 MS.Microservice.Core.Domain.Repository34 MS.Microservice.Core.Extension35 MS.Microservice.Media.Inference.WatermarkRemoval36 MS.Microservice.Messaging.Wolverine37 Microsoft.Extensions.DependencyInjection38 MS.Microservice.Core.Domain.Repository.Extensions39 MS.Microservice.Media.Inference.Ocr40 MS.Microservice.Persistence.SqlSugar.DbContext
1 .github.skills.mcp-builder.scripts.connections
2 MS.Microservice.AI.Abstractions
3 MS.Microservice.AI.QuestionGeneration.Contracts
4 MS.Microservice.AI.QuestionGeneration.Serialization
5 MS.Microservice.Caching
6 MS.Microservice.Core.Common.Advance.Resilience
7 MS.Microservice.Core.Domain.Entity.Enums
8 MS.Microservice.Core.Domain.Repository.SqlSugar
9 MS.Microservice.Core.Functional
10 MS.Microservice.Core.IO
11 MS.Microservice.Core.Messaging
12 MS.Microservice.Core.Specification
13 MS.Microservice.Infrastructure.Utils
14 MS.Microservice.Media.Images
15 MS.Microservice.Messaging
16 MS.Microservice.Persistence.EFCore.Auditing
17 MS.Microservice.Tasks
18 .github.skills.mcp-builder.scripts1
19 MS.Microservice.AI.Core115
20 MS.Microservice.AI.QuestionGeneration.AIChat4101
21 MS.Microservice.AI.QuestionGeneration.Pipeline39
22 MS.Microservice.AI.QuestionGeneration.Prompts4
23 MS.Microservice.Caching.Redis1
24 MS.Microservice.Core.Dto1
25 MS.Microservice.Core.Functional.Data.LinkedList3
26 MS.Microservice.EventBus.Events1
27 MS.Microservice.Media.Inference2
28 MS.Microservice.Messaging.RabbitMQ6
29 MS.Microservice.Persistence.SqlSugar1
30 MS.Microservice.AI.DeepSeek4
31 MS.Microservice.AI.OpenAI16
32 MS.Microservice.AI.Qwen717
33 MS.Microservice.Core.Domain.Repository112
34 MS.Microservice.Core.Extension21
35 MS.Microservice.Media.Inference.WatermarkRemoval3
36 MS.Microservice.Messaging.Wolverine142
37 Microsoft.Extensions.DependencyInjection411
38 MS.Microservice.Core.Domain.Repository.Extensions1831
39 MS.Microservice.Media.Inference.Ocr11
40 MS.Microservice.Persistence.SqlSugar.DbContext22242
Uses a module listed above itPart of a loopThe module itself
1 .github.skills.mcp-builder.scripts.connections2 MS.Microservice.AI.Abstractions3 MS.Microservice.AI.QuestionGeneration.Contracts4 MS.Microservice.AI.QuestionGeneration.Serialization5 MS.Microservice.Caching6 MS.Microservice.Core.Common.Advance.Resilience7 MS.Microservice.Core.Domain.Entity.Enums8 MS.Microservice.Core.Domain.Repository.SqlSugar9 MS.Microservice.Core.Functional10 MS.Microservice.Core.IO11 MS.Microservice.Core.Messaging12 MS.Microservice.Core.Specification13 MS.Microservice.Infrastructure.Utils14 MS.Microservice.Media.Images15 MS.Microservice.Messaging16 MS.Microservice.Persistence.EFCore.Auditing17 MS.Microservice.Tasks18 .github.skills.mcp-builder.scripts19 MS.Microservice.AI.Core20 MS.Microservice.AI.QuestionGeneration.AIChat21 MS.Microservice.AI.QuestionGeneration.Pipeline22 MS.Microservice.AI.QuestionGeneration.Prompts23 MS.Microservice.Caching.Redis24 MS.Microservice.Core.Dto25 MS.Microservice.Core.Functional.Data.LinkedList26 MS.Microservice.EventBus.Events27 MS.Microservice.Media.Inference28 MS.Microservice.Messaging.RabbitMQ29 MS.Microservice.Persistence.SqlSugar30 MS.Microservice.AI.DeepSeek31 MS.Microservice.AI.OpenAI32 MS.Microservice.AI.Qwen33 MS.Microservice.Core.Domain.Repository34 MS.Microservice.Core.Extension35 MS.Microservice.Media.Inference.WatermarkRemoval36 MS.Microservice.Messaging.Wolverine37 Microsoft.Extensions.DependencyInjection38 MS.Microservice.Core.Domain.Repository.Extensions39 MS.Microservice.Media.Inference.Ocr40 MS.Microservice.Persistence.SqlSugar.DbContext.github.skills.mcp-builder.scripts.connections1MS.Microservice.AI.Abstractions2MS.Microservice.AI.QuestionGeneration.Contracts3MS.Microservice.AI.QuestionGeneration.Serialization4MS.Microservice.Caching5MS.Microservice.Core.Common.Advance.Resilience6MS.Microservice.Core.Domain.Entity.Enums7MS.Microservice.Core.Domain.Repository.SqlSugar8MS.Microservice.Core.Functional9MS.Microservice.Core.IO10MS.Microservice.Core.Messaging11MS.Microservice.Core.Specification12MS.Microservice.Infrastructure.Utils13MS.Microservice.Media.Images14MS.Microservice.Messaging15MS.Microservice.Persistence.EFCore.Auditing16MS.Microservice.Tasks17.github.skills.mcp-builder.scripts18MS.Microservice.AI.Core19MS.Microservice.AI.QuestionGeneration.AIChat20MS.Microservice.AI.QuestionGeneration.Pipeline21MS.Microservice.AI.QuestionGeneration.Prompts22MS.Microservice.Caching.Redis23MS.Microservice.Core.Dto24MS.Microservice.Core.Functional.Data.LinkedList25MS.Microservice.EventBus.Events26MS.Microservice.Media.Inference27MS.Microservice.Messaging.RabbitMQ28MS.Microservice.Persistence.SqlSugar29MS.Microservice.AI.DeepSeek30MS.Microservice.AI.OpenAI31MS.Microservice.AI.Qwen32MS.Microservice.Core.Domain.Repository33MS.Microservice.Core.Extension34MS.Microservice.Media.Inference.WatermarkRemoval35MS.Microservice.Messaging.Wolverine36Microsoft.Extensions.DependencyInjection37MS.Microservice.Core.Domain.Repository.Extensions38MS.Microservice.Media.Inference.Ocr39MS.Microservice.Persistence.SqlSugar.DbContext4011154101394113126141671711221314241118311122242+89 more modules (most-connected shown)

At a glance — Code Health · 72% · Strong ·

At a glance — Architecture · 85% · Strong ·

At a glance — Maturity · 84% · Strong ·

At a glance — Readiness · 45% · Weak · gated by D13, P3 ·

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

At a glance — Domain Modelling · 83% · Strong ·

At a glance — Event-Driven · 87% · Strong ·

At a glance — Accessibility · 42% · Weak · gated by AC6 ·

At a glance — Performance · 47% · Weak · gated by PF3 ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection95High / Critical
A03:2025 — Software Supply Chain Failures14High / Critical
A07:2025 — Authentication Failures7High / Critical
A02:2025 — Security Misconfiguration6Medium

Roadmap

Top priorities: Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED; Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult(); Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.

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

Do thisHelpsEffortDimension
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.+4.8 ptsLowREDACTED Scanning
Resolve the 4 Prerelease dependency finding(s) in Dependency Hygiene.+3.0 ptsLowDependency Hygiene
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().+3.8 ptsMediumAsync & latency hygiene
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.+3.5 ptsMediumVisual & motion safety
Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props (2).+1.6 ptsLowDependency Hygiene
Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with Directory.Packages.props (2).+1.6 ptsLowDependency Hygiene
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.+2.8 ptsMediumSecurity & performance tooling
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).+2.3 ptsMediumBenchmark discipline

File quality

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

FileScoreBandWorst signal
REDACTED1.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.2SlopExplicit Debt: EmptyCatchBlock
src/MS.Microservice.Excel/CsvHelper.cs3.6SlopExplicit Debt: EmptyCatchBlock
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedDependency Vulnerabilities: High CVE: REDACTED
src/MS.Microservice.Audio/AudioProcessorExtensions.cs4.5MixedExplicit Debt: EmptyCatchBlock
Directory.Packages.props4.6MixedExplicit Debt: NoWarnInCsproj
REDACTED5.1MixedREDACTED Scanning: Leaked secret: REDACTED
MS.Microservice.Media/src/MS.Microservice.Media.Inference/VideoWatermarkRemoval/VideoWatermarkRemover.cs5.4MixedExplicit Debt: EmptyCatchBlock
src/MS.Microservice.Audio/AudioProcessor.cs5.6MixedExplicit Debt: EmptyCatchBlock
REDACTED5.7MixedREDACTED Scanning: Leaked secret: REDACTED
samples/Lab/MS.Microservice.Lab.Domain/Managers/UserManager.cs5.8MixedExplicit Debt: WriteOnlyPrivateField
samples/Lab/MS.Microservice.Lab/Controller/AccountController.cs5.8MixedExplicit Debt: WriteOnlyPrivateField
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED

How the grades work

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

Critical — 50

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 — 615

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 — 161

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

Could not be resolved — 10

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 93 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

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

What we checked — 93 dimensions across the health lenses
D1D2D3D4D5D6D7D9D10D11D12D13D14D15D16D17D18D19D22D24D26D27D28D29D30D31D34D35D36D43D44AC2AC3AC5AC6AC7AX1AX10AX2AX3AX4AX5AX6AX8AX9C1C2C3C4DM12DM6ED1ED3ED4ED5GD1IC1M1M2M3P1P2P3P4P5PF1PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1bb0c-4666-7d93-896c-7029f849e727.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The test suite couldn't be built/run in-image and no coverage report is committed, so line coverage was not measured — and it is EXCLUDED from the score rather than scored on a LoC-ratio proxy. Your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes. You can widen what we reach: optional: your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes, or make the suite runnable in-image, and real coverage will be measured.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 2,479 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 5 test source file(s) (.py) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D20 ADR Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The ADR lexicon (adr-lexicon-1) covers de, en, it, nl. A record identified as another language, or whose language could not be identified (fewer than 25 words of prose, or no clear winner), is never read with English rules: its missing-section, status, consequence-cost and same-question rules abstain, and only the structural rules (title, single option, dangling link, enforcement field) run.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (46,676 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs`, `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionServices.cs`, `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProviderConcurrency.cs`, `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIResponseReader.cs`, `MS.Microservice.AI/src/MS.Microservice.AI.QuestionGeneration/AIChat/AIChatQuestionModelClient.cs`, … (+98 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — time="2026-11-08T12:05:25Z" level=warning msg="The \"KEYCLOAK_ADMIN_PASSWORD\" variable is not set. Defaulting to a blank string." time="2026-11-08T12:05:25Z" level=warning msg="The \"MS_REFERENCE_OPS_SECRET\" variable is not set. Defaulting to a blank string." container ms-reference-lab-postgres-1 exited (1); runtime evidence skipped.
  • M4 Documentation accuracy — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. M4 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
  • P10 Library API & versioning — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • P11 BDD / executable specs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • P7 Outbound HTTP resilience — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • PF3 Async & latency hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 219 further occurrence(s) are not listed individually; the score already reflects all 259.
  • X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 131 further occurrence(s) are not listed individually; the score already reflects all 171.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • 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.
  • D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
  • 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.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • 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".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.

Dimensions

D1 · Cyclomatic Complexity6.8 / 10Adequate✓ Tool-verified

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

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

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

70 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TableRecognizer.ValidateResult at 45. A further 6 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 AuditScalarJson.Write at 23 — 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: MS.Microservice.Persistence/src/MS.Microservice.Persistence.EFCore/Auditing/AuditScalarJson.cs (AuditScalarJson.Write at 23), src/MS.Microservice.Audio/AudioFileFormatDetector.cs (AudioFileFormatDetector.DetectFormatFromStream at 19), MS.Microservice.Media/src/MS.Microservice.Media.Inference/SuperResolution/Swin2SrUpscaler.cs (Swin2SrUpscaler.CreateAsync at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

TableRecognizer.ValidateResult (cyclomatic 45)MS.Microservice.Media/src/MS.Microservice.Media.Inference/Tables/TableRecognizer.cs:58
VideoWatermarkRemover.RemoveCoreAsync (cyclomatic 41)MS.Microservice.Media/src/MS.Microservice.Media.Inference/VideoWatermarkRemoval/VideoWatermarkRemover.cs:39
PackageReader.StoryAsync (cyclomatic 39)src/MS.Microservice.Documents/Word/WordTextExtractor.cs:159
top-level statements (cyclomatic 38)benchmarks/MS.Microservice.Search.Benchmarks/Program.cs:13
top-level statements (cyclomatic 37)MS.Microservice.Persistence/benchmarks/MS.Microservice.Persistence.Auditing.Benchmarks/Program.cs:14

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

What to do

  1. Bring the 8 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with TableRecognizer.ValidateResult (cyclomatic 45), VideoWatermarkRemover.RemoveCoreAsync (cyclomatic 41), PackageReader.StoryAsync (cyclomatic 39). — 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 8 together lifts Cyclomatic Complexity from 6.9 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
  2. 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.

D2 · Cognitive Complexity6.2 / 10Adequate✓ Tool-verified

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

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

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

83 method(s) exceeded the cognitive complexity threshold of 15; the worst was run_eval.run_single_query at 79.

run_eval.run_single_query (cognitive 79).github/skills/skill-creator/scripts/run_eval.py:35
top-level statements (cognitive 65)MS.Microservice.Persistence/benchmarks/MS.Microservice.Persistence.Auditing.Benchmarks/Program.cs:14
PackageReader.StoryAsync (cognitive 60)src/MS.Microservice.Documents/Word/WordTextExtractor.cs:159
aggregate_benchmark.load_run_results (cognitive 58).github/skills/skill-creator/scripts/aggregate_benchmark.py:67
run_loop.run_loop (cognitive 55).github/skills/skill-creator/scripts/run_loop.py:47

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with run_eval.run_single_query (cognitive 79), top-level statements (cognitive 65). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.2 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. 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.

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

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

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

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

9 god class(es) detected.

TooManyMethods: ExcelHelper · ×4src/MS.Microservice.Excel/ExcelHelper.cs
MethodTooLong: QuestionGenerationHarness.RunAsync · ×2MS.Microservice.AI/src/MS.Microservice.AI.QuestionGeneration/Pipeline/QuestionGenerationHarness.cs:28
ClassTooLong: VideoProcessor · ×2MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Editing.cs
FileTooLong: MS.Microservice.Excel/ExcelHelper.cssrc/MS.Microservice.Excel/ExcelHelper.cs

What to do

  1. Resolve the 4 TooManyMethods finding(s) in God Classes — start with ExcelHelper.cs, CoravelScheduleCatalog.cs, AudioProcessor.cs. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 2 MethodTooLong finding(s) in God Classes — start with QuestionGenerationHarness.cs, RedisCacheBenchmark.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 ClassTooLong finding(s) in God Classes — start with VideoProcessor.Editing.cs, QuestionGenerationHarness.cs. — One of this dimension's main actionable groups (2 warning-level).
  4. 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.

D4 · Code Duplication9.7 / 10Stronggated by 33 serious findings✓ Tool-verified

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

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

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

33 duplicated block group(s) detected. 9 of the 33 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (8 lines × 2) · ×6MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/SelfManagedPublisher.cs:24
Duplicated block (5 lines × 2) · ×5MS.Microservice.Tasks/src/MS.Microservice.Tasks.EFCore/JobModelBuilderExtensions.cs:18
Duplicated block (7 lines × 2) · ×3MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs:25
Duplicated block (11 lines × 2) · ×2MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleMediaProviderBase.cs:91
Duplicated block (6 lines × 2) · ×2MS.Microservice.Media/src/MS.Microservice.Media/Images/ImageProcessingOptions.cs:21

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

What to do

  1. Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with SelfManagedPublisher.cs, BaseContext.cs, AudioFileFormatDetector.cs. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with JobModelBuilderExtensions.cs, BiRefNetBackgroundRemover.cs, AuditRecord.cs. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with AIProductionPipeline.cs, MessageEntries.cs, ImageToolForms.cs. — One of this dimension's main actionable groups (3 warning-level).
  4. 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.

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

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

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

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

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

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

Off the main sequence: MS.Microservice.Logging.Core · ×4MS.Microservice.Logging/src/MS.Microservice.Logging.Core/MS.Microservice.Logging.Core.csproj:1

What to do

  1. Resolve the 4 Off the main sequence finding(s) in Coupling — start with MS.Microservice.Logging.Core.csproj, MS.Microservice.Threading.csproj, MS.Microservice.Tasks.csproj. — One of this dimension's main actionable groups (4 warning-level).
  2. 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.

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

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

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

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

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

1 of 167 classes have LCOM4 above 3.

Low cohesion: UserController (LCOM4 4)REDACTED:16

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d7_recommendation.md.

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.

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

2479 test methods: 2477 unit, 2 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Adequategated by 1 critical 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.

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

0 skipped, 1 zero-assertion, 3 racing the wall clock, 16 mock references across 2479 tests. Measured on the C# suite only — at least 5 test source file(s) (.py) went unread, so its test quality is unmeasured and is not in these counts.

No assertions (empty test): Test1test/MS.Microservice.Core.Tests/UnitTest1.cs:5
Races the wall clock: EventIdentityUsesLosslessStorageInsteadOfDatabaseTimestampPrecision · ×3MS.Microservice.Messaging/test/MS.Microservice.Messaging.SelfManaged.Tests/EventTimePrecisionTests.cs:10
Mock framework: NSubstitute · ×16

What to do

  1. Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with UnitTest1.cs. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 3 Races the wall clock finding(s) in Test Quality — start with ProfileServiceTests.cs (2), EventTimePrecisionTests.cs. — One of this dimension's main actionable groups (3 warning-level).
  3. 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.

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D12 · Dependency Hygiene6.0 / 10Adequate✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

69 outdated, 0 vulnerable, 2 deprecated, 4 prerelease packages.

Prerelease dependency: SqlSugarCore · ×4
Deprecated: xunit · ×2Directory.Packages.props:100
Outdated: coverlet.collector · ×2Directory.Packages.props:9
Outdated: Microsoft.EntityFrameworkCore.Sqlite · ×67

What to do

  1. Resolve the 4 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props (2). — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with Directory.Packages.props (2). — One of this dimension's main actionable groups (2 recommendation-level).

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

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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

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

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

3 secret(s) detected.

REDACTED

What to do

  1. Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  2. Enforce REDACTED 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.

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

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

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

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

0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 81 direct `PackageReference`(s), and 169 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

Top hotspots: src/MS.Microservice.Documents.Rendering/RenderWorkerSupervisor.cs (2×35=70); src/MS.Microservice.Excel/ExcelHelper.cs (3×18=54); samples/Reference/MS.Microservice.Reference.Web/HttpIdempotency/ReferenceHttpIdempotencyExecutor.cs (3×17=51)

Hotspot: src/MS.Microservice.Documents.Rendering/RenderWorkerSupervisor.cs · ×3src/MS.Microservice.Documents.Rendering/RenderWorkerSupervisor.cs:20

What to do

  1. Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with RenderWorkerSupervisor.cs, ExcelHelper.cs, ReferenceHttpIdempotencyExecutor.cs. — One of this dimension's main actionable groups (3 warning-level).

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

D16 · Bus Factor8.0 / 10Strong✓ Tool-verified

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

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

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

53 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/MS.Microservice.Excel/ExcelHelper.cs. Counted over 181 of the 474 production source files in this repository: 288 are under the ~2,400-byte size floor this dimension measures over, and the remaining 5 have no attributable history left to measure.

Off-boarding risk: anonymized user #1

What to do

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

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

D17 · Explicit Debt7.4 / 10Adequategated by 25 critical findings✓ Tool-verified

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

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

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

36 deducted debt markers + 144 dead symbols across 46676 LoC in the .NET projects (1.3/KLoC) → score 7.4.

EmptyCatchBlock · ×18MS.Microservice.Media/src/MS.Microservice.Media.Inference/VideoWatermarkRemoval/VideoWatermarkRemover.cs:131
WriteOnlyPrivateField · ×4MS.Microservice.AI/src/MS.Microservice.AI.Qwen/QwenImageReferenceEditClient.cs:18
NoWarnInCsproj · ×3Directory.Build.props:12
Dead code: RealModel_PortraitTransparentEdgesAndExifPreserveRgbAndSourceAlphaWithMatchingMatte · ×144MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/BackgroundRemoval/BiRefNetBackgroundRemoverTests.cs:28
TodoComment · ×4samples/Lab/MS.Microservice.Lab.Domain/Aggregates/IdentityModel/Repository/IRoleRepository.cs:3

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

What to do

  1. Resolve the 18 EmptyCatchBlock finding(s) in Explicit Debt — start with REDACTED (3), REDACTED (2), CsvHelper.cs (2). — One of this dimension's main actionable groups (18 issue-level).
  2. Resolve the 4 WriteOnlyPrivateField finding(s) in Explicit Debt — start with QwenImageReferenceEditClient.cs, UserManager.cs, SignInManager.cs. — One of this dimension's main actionable groups (4 issue-level).
  3. Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (2), Directory.Packages.props. — One of this dimension's main actionable groups (3 issue-level).
  4. 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.

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

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

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

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

109 projects, 1086 source files, 94340 hand-written lines of code (46340 production / 48000 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), plus 4742 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 166 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation Quality9.5 / 10Exemplary✓ Tool-verified

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

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

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

1 of 2 documentation facets pass in full; short on: F2 example. 273 document(s) read across 57 unit(s).

Documentation: no build, run or usage example · ×3MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/README.md:1

✓ On the Gold path — maintain.

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d22_recommendation.md.

D24 · Comment Value8.5 5.0 / 10Adequate✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 59% · ceiling Documented

3 of 201 judged comments only repeat the code they sit on (1.5 %). 212 comment(s) in another language or script were not judged.

redundant comment · ×3MS.Microservice.AI/src/MS.Microservice.AI.Qwen/QwenImageEditProvider.cs:25
doc comments repeat the names · ×6MS.Microservice.AI/src/MS.Microservice.AI.Abstractions/AIImageEditRequest.cs:38

What to do

  1. Resolve the 3 redundant comment finding(s) in Comment Value — start with QwenImageEditProvider.cs, QwenImageReferenceEditClient.cs, ExcelHelper.cs. — One of this dimension's main actionable groups (3 recommendation-level).

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

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

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

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

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

2 of 116 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×2src/MS.Microservice.Core/MS.Microservice.Core.csproj:1
Split MS.Microservice.Coresrc/MS.Microservice.Core/MS.Microservice.Core.csproj:1

✓ On the Gold path — maintain.

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

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

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

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

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

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

75 % of calls cross a namespace and 7 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

Pass-through layersrc/MS.Microservice.Audio/AudioProcessor.cs:508

✓ On the Gold path — maintain.

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

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

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

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

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

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

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

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

96 finding(s): 0 critical, 3 high, 92 medium, 1 low. 2 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 166 file(s) — `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs` (lines 11–17, line 17), `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionServices.cs` (line 17, line 64, line 119, …), `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProviderConcurrency.cs` (line 7), `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIResponseReader.cs` (lines 35–36, line 67, line 100), `MS.Microservice.AI/src/MS.Microservice.AI.QuestionGeneration/AIChat/AIChatQuestionModelClient.cs` (lines 12–15, line 16, line 17, …), … (+161 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 138 of those file(s) — `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs`, `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionServices.cs`, `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProviderConcurrency.cs`, `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIResponseReader.cs`, `MS.Microservice.AI/src/MS.Microservice.AI.QuestionGeneration/AIChat/AIChatQuestionModelClient.cs`, … (+133 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 27 of those file(s) — `MS.Microservice.AI/src/MS.Microservice.AI.QuestionGeneration/Pipeline/QuestionGenerationHarness.cs`, `MS.Microservice.Messaging/src/MS.Microservice.Messaging.Abstractions/Contracts.cs`, `MS.Microservice.Persistence/src/MS.Microservice.Persistence.EFCore/DbContext/EFCoreQueryableExtensions.cs`, `MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/SqlSugarQueryableExtensions.cs`, `MS.Microservice.Tasks/src/MS.Microservice.Tasks/JobContracts.cs`, … (+22 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 76 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (11), REDACTED (9), REDACTED (8). — One of this dimension's main actionable groups (76 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities6.2 / 10Adequate✓ Tool-verified

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

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

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

8 finding(s): 1 critical, 7 high, 0 medium, 0 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.

REDACTED
REDACTED

What to do

  1. Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
  2. Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D31 · IaC & Container Security9.5 / 10Stronggated by 5 serious findings✓ Tool-verified

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

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

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

6 finding(s): 0 critical, 0 high, 5 medium, 1 low.

REDACTED
REDACTED

What to do

  1. Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

5 of 186 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs. Counted over 186 of the 474 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×5MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

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

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC2 · Forms & labels6.3 / 10Adequate✓ Tool-verified

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

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

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

  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — .github/skills/skill-creator/eval-viewer/viewer.html:604

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure4.9 / 10Weak✓ Tool-verified

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

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

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

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — .github/skills/baoyu-url-to-markdown/scripts/html-to-markdown.ts:174
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — .github/skills/baoyu-url-to-markdown/scripts/html-to-markdown.ts:174
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — .github/skills/baoyu-url-to-markdown/scripts/html-to-markdown.ts:174, .github/skills/skill-creator/assets/eval_review.html:2, .github/skills/skill-creator/eval-viewer/viewer.html:2

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

AC6 · Visual & motion safety1.4 / 10Critical✓ Tool-verified

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

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

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

  • `.btn-add` sets color: white on background-color: #6a9bcc — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .github/skills/skill-creator/assets/eval_review.html:17
  • `.btn-export` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .github/skills/skill-creator/assets/eval_review.html:19
  • `.grades-toggle .arrow` moves (`transition: transform 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — .github/skills/skill-creator/eval-viewer/viewer.html:275
  • `.section-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .github/skills/skill-creator/eval-viewer/viewer.html:83
  • `.output-file-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .github/skills/skill-creator/eval-viewer/viewer.html:136
  • `.output-file-content .download-link` sets color: #d97757 on background-color: #faf9f5 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .github/skills/skill-creator/eval-viewer/viewer.html:197
  • `.prev-feedback` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .github/skills/skill-creator/eval-viewer/viewer.html:221
  • `.grade-pass` sets color: #788c5d on background-color: #eef2e8 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .github/skills/skill-creator/eval-viewer/viewer.html:302
  • `.grade-fail` sets color: #c44 on background-color: #fceaea — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .github/skills/skill-creator/eval-viewer/viewer.html:303
  • `.done-btn.ready` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .github/skills/skill-creator/eval-viewer/viewer.html:467
  • `.nav-item.active` sets color: #635bdf on background-color: #eeedfc — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — MS.Microservice.Tasks/src/MS.Microservice.Tasks.Dashboard/Assets/dashboard.css:20
  • `th` sets color: #8c96aa on background-color: #f8f9fc — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — MS.Microservice.Tasks/src/MS.Microservice.Tasks.Dashboard/Assets/dashboard.css:74

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 4 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — .github/skills/baoyu-url-to-markdown/scripts/package.json:5

What to do

  • Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons6.4 / 10Adequate✓ Tool-verified

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

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

  • `JobExecutionOptions` is a singleton (one shared instance) but mutates instance state outside any lock (_queues; e.g. `_queues` at line 52). — MS.Microservice.Tasks/src/MS.Microservice.Tasks/JobExecutionContracts.cs:38
  • `EventTypeRegistry` is a singleton (one shared instance) but mutates instance state outside any lock (_eventTypes, _eventNames; e.g. `_eventTypes` at line 18). — samples/Lab/MS.Microservice.Lab.Infrastructure/EventSourcing/Serialization/SystemTextJsonEventSerializer.cs:8
  • `ToolInferenceRuntime` is a singleton (one shared instance) but mutates instance state outside any lock (_repair, _automatic, _upscaler, _background; e.g. `_repair` at line 37). — samples/Lab/MS.Microservice.Lab/Application/Tools/ToolInferenceRuntime.cs:10
  • `RedisCacheBenchmark` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_checksum; e.g. `_checksum` at line 83). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — benchmarks/MS.Microservice.Framework.Benchmarks/RedisCacheBenchmark.cs:10

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
  • A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

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

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

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

  • `IRepositoryBase<T>` declares 22 members under just 13 distinct name(s): `AnyAsync`, `AddAsync`, `AddAReturnIdsync`, `AddReturnEntitysync`, `AddListAsync`, `GetModelAsync`, `GetPagesAsync`, `GetListAsync`, `GetListAsync`, `GetListAsync`, `UpdateAsync`, `UpdateAsync`, `UpdateAsync`, `DeleteAsync`, `DeleteAsync`, `DeleteAsync`, `FirstOrDefaultAsync`, `FirstOrDefaultAsync`, `ListAsync`, `ListAsync`, `CountAsync`, `AnyAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 22 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 22 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/IRepositoryBase.cs:12
  • `IJobStore` declares 16 members: `SubmitAsync`, `StageAsync`, `GetAsync`, `ListAsync`, `GetAttemptsAsync`, `GetDueAsync`, `GetRunningExecutionsAsync`, `GetExecutionStatusAsync`, `TryStartAsync`, `ReportProgressAsync`, `CompleteAsync`, `FailAsync`, `InterruptAsync`, `RecoverAsync`, `CancelAsync`, `RetryAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — MS.Microservice.Tasks/src/MS.Microservice.Tasks/JobContracts.cs:26

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
  • Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

C1 · Data Protection8.5 / 10Strong✓ 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 in-app HTTPS enforcement, but ForwardedHeaders / 127.0.0.1 binding indicates a reverse-proxy topology — adding UseHttpsRedirection in the app would be wrong in this layout. Verify the reverse proxy enforces TLS. — REDACTED:75

What to do

  • Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
C2 · Access Controls10.0 / 10Exemplary○ Nothing flagged

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

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

C3 · Audit Trail10.0 / 10Exemplary✓ Tool-verified

Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.

Method: Roslyn scan: audit-trail mechanism graded (SaveChanges interceptor/immutable AuditLog/[Audited] strong; bare IAuditable/AddAuditing weak). Deterministic.

C4 · Data Retention10.0 / 10Exemplary✓ 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.

DM12 · Ambient inputs in the domain9.8 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.

Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.

  • `OutboxMessage` reads `DateTimeOffset.UtcNow` inside `Create` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has. — samples/Lab/MS.Microservice.Lab.Domain/Events/OutboxMessage.cs:48
  • `PasswordSaltHelper` reads `DateTime.Now` inside `Generate` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has. — samples/Lab/MS.Microservice.Lab.Domain/Aggregates/IdentityModel/PasswordSaltHelper.cs:12
  • `User` reads `DateTime.Now` inside `Delete` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has. — samples/Lab/MS.Microservice.Lab.Domain/Aggregates/IdentityModel/User.cs:103

What to do

  • Route the listed sites through the clock abstraction this repo already declares, so the domain's rules can be exercised at a chosen instant.
DM6 · Domain ↔ infrastructure boundary7.1 / 10Strong✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

  • `LogRepository` (a domain rule: it decides over the repository's entities) names `ActivationDbContext` from `MS.Microservice.Persistence.EFCore.DbContext` — a persistence/infrastructure type (in a member signature). Move the queries to the caller and pass the loaded values to a pure decision method. (×2) — samples/Lab/MS.Microservice.Lab.Persistence/Repository/LogRepository.cs:16, samples/Lab/MS.Microservice.Lab.Persistence/Repository/LogRepository.cs:18
  • `LogRepository` (a domain rule: it decides over the repository's entities) names `EntityState` from `Microsoft.EntityFrameworkCore` — a persistence type (in a method body). Move the queries to the caller and pass the loaded values to a pure decision method. — samples/Lab/MS.Microservice.Lab.Persistence/Repository/LogRepository.cs:65

What to do

  • Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
ED1 · Handler temporal coupling10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).

Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.

ED3 · Event naming8.8 / 10Strong✓ Tool-verified

Other · Event-Driven — Whether events are named in the past tense (a clarity nudge — low weight).

Method: Roslyn scan (event-driven gated): domain and integration events checked for past-tense naming (-ed/-en suffix or irregular set). Naming nudge, low-weight advisory.

  • `IntegrationEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. (×2) — src/MS.Microservice.Core/Messaging/EventContracts.cs:31, src/MS.Microservice.EventBus/Events/IntegrationEvent.cs:7

What to do

  • Name events in the past tense — they record facts that already happened.
ED4 · Outbox / dual-write7.8 / 10Strong✓ Tool-verified

Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.

Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.

  • `SmtpEmailSender.SendAsync` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — REDACTED:30

What to do

  • Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
ED5 · Idempotency10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — samples/Lab/MS.Microservice.Lab/Infrastructure/ActivationDbContextSeed.cs:30

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs9.0 / 10Strong✓ Tool-verified

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.

  • 2 guards above `return AudioFormat.Auto;` also return `AudioFormat.Auto`, so no input can make them matter. Implement the distinction that was intended, or delete the guards. — src/MS.Microservice.Audio/AudioFileFormatDetector.cs:70
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×2) — src/MS.Microservice.Core/Common/NumberConverter.cs:33, REDACTED:279

What to do

  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)8.8 / 10Strong✓ Tool-verified

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

  • 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 a README to the 16 of 66 project(s) that lack one — worth up to 0.5 pts.
M2 · Architecture documentation7.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Grow the ADR log (currently 4) — reach 8 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P2 · Observability8.7 / 10Strong✓ Tool-verified

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

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

  • Only 23/41 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 41, 8 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
  • `benchmarks/MS.Microservice.Core.HttpLogging.Benchmarks/Program.cs` reports through `Console.Write…` at line 49 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — benchmarks/MS.Microservice.Core.HttpLogging.Benchmarks/Program.cs:49

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.
  • Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add 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 2080 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:8
  • `Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Directory.Packages.props:8

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
  • Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
PF1 · Benchmark discipline6.0 / 10Adequate✓ Tool-verified

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

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

  • No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

What to do

  • Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene3.7 / 10Weak✓ Tool-verified

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

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

  • 13 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). (×11) — benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:41, benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:42, benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:43, …
  • Only 180/426 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
  • `await using … = await rateLimiter.AcquireAsync(context, cancellationToken).Configur...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs:30, MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs:58
  • `await using … = await httpResponse.Content.ReadAsStreamAsync(requestCancellationTok...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleAsrProviderBase.cs:40
  • `await using … = ParseStreamAsync(stream, model, request, streamCancellation.Token)....` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleChatProviderBase.cs:129
  • `await using … = await httpResponse.Content.ReadAsStreamAsync(cancellationToken).Con...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleChatProviderBase.cs:308, MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleImageGenerationProviderBase.cs:67
  • `await using … = await httpResponse.Content.ReadAsStreamAsync(cancellationToken) .Co...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.AI/src/MS.Microservice.AI.Qwen/QwenImageEditProvider.cs:111
  • `await context.Set<IdempotencyRecord>().AsNoTracking().SingleOrDefaultAsync( row => ...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Idempotency/src/MS.Microservice.Idempotency.EFCore/EfCoreIdempotencyStore.cs:17
  • `await context.SaveChangesAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — MS.Microservice.Idempotency/src/MS.Microservice.Idempotency.EFCore/EfCoreIdempotencyStore.cs:53, MS.Microservice.Idempotency/src/MS.Microservice.Idempotency.EFCore/EfCoreIdempotencyStore.cs:62
  • `await operation(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Idempotency/src/MS.Microservice.Idempotency.EFCore/EfCoreIdempotencyStore.cs:55
  • `await _next(context)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Logging/src/MS.Microservice.Logging.AspNetCore/MsRequestLoggingMiddleware.cs:41
  • `await unitOfWork.ExecuteAsync(async token => { await operation(token); return true;...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.Abstractions/Contracts.cs:31
  • `await operation(token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.Abstractions/Contracts.cs:31
  • `await ConsumeSessionAsync(stoppingToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:17
  • `await Task.Delay(options.ReconnectDelay, stoppingToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:20
  • `await using … = await factory.CreateConnectionAsync(session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:28
  • `await factory.CreateConnectionAsync(session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:28
  • `await using … = await connection.CreateChannelAsync( new CreateChannelOptions(publi...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:29
  • `await connection.CreateChannelAsync( new CreateChannelOptions(publisherConfirmation...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:29
  • `await channel.ExchangeDeclarePassiveAsync(options.Exchange, session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:36
  • `await channel.BasicQosAsync(0, options.PrefetchCount, global: false, session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:37
  • `await channel.QueueDeclarePassiveAsync(queue, session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:41
  • `await channel.QueueDeclarePassiveAsync(queue + ".dead", session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:42
  • `await channel.BasicConsumeAsync(queue, autoAck: false, consumer, session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:47
  • `await disconnected.Task.WaitAsync(session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:49
  • `await session.CancelAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:53

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
  • In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
S1 · Web-Security Posture8.5 / 10Strong✓ Tool-verified

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

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

  • MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — src/MS.Microservice.Core/Security/Summary/Md5.cs:13
  • `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path. — samples/Lab/MS.Microservice.Lab/Infrastructure/Extensions/IServiceCollectionExtensions.cs:228
  • Set: Content-Security-Policy, Cross-Origin-Resource-Policy, Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−0.5 on this card.) — REDACTED:26

What to do

  • Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
  • Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
  • Add Strict-Transport-Security beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
X1 · Async correctness7.1 / 10Strong✓ Tool-verified

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

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

  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×11) — benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:41, benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:42, benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:43, …
  • `MemoryStream.Write` blocks the thread on I/O while `MemoryStream.WriteAsync` exists to wait without one — inside a method that is already `async`, await the twin. (×4) — MS.Microservice.Media/src/MS.Microservice.Media/Images/ImageCodec.cs:21, samples/Lab/MS.Microservice.Lab/Application/Tools/ImageBatchJobs.cs:302, src/MS.Microservice.Documents.Rendering/RenderWorkerSupervisor.cs:154, …
  • `SemaphoreSlim.Wait` parks the thread while it queues for the semaphore. `await semaphore.WaitAsync(…)` yields the thread instead. (×2) — MS.Microservice.Tasks/src/MS.Microservice.Tasks/JobExecutor.cs:80, src/MS.Microservice.Caching/GovernedCache.cs:92

What to do

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

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

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

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.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

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.

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.

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

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

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

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.

X18 · Disposal-pattern correctness6.8 / 10Adequate✓ Tool-verified

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.

  • `_session` is a `InferenceSession` that `MiganInpainter` never creates — every assignment to it takes a constructor parameter — and this type disposes it here (line 101). The caller that hands it over at `new MiganInpainter(session, options.Limits)` (MiganInpainter.cs line 38) releases the same value itself, so it kept ownership: this release is a second one, on a value that is still the caller's, and it ends the caller's instance while the caller may still be using it. Drop the call and leave the release to the caller that created the value — or, if this type is meant to own it, stop releasing it at the construction site so ownership is stated once. — MS.Microservice.Media/src/MS.Microservice.Media.Inference/MiganInpainter.cs:101
  • `md5` is a `MD5`, which implements `IDisposable`, and it is created here (line 13). Every use of it in `Encrypt` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var md5 = …;`), which releases it at the end of the scope on every path including a throw. — src/MS.Microservice.Core/Security/Summary/Md5.cs:13
  • `output` is a `Stream`, which implements `IDisposable`, and it is created here (line 92). Every use of it in `RunAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var output = …;`), which releases it at the end of the scope on every path including a throw. — src/MS.Microservice.Documents.Rendering/HtmlRenderWorker.cs:92
  • `destination` is a `Stream`, which implements `IDisposable`, and it is created here (line 54). Every use of it in `RunAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var destination = …;`), which releases it at the end of the scope on every path including a throw. — src/MS.Microservice.Documents.Rendering/WordRenderWorker.cs:54

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.
X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

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.

X2 · Cancellation propagation8.0 / 10Strong✓ Tool-verified

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

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

  • Only 333/502 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 — 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. (×4) — benchmarks/MS.Microservice.Framework.Benchmarks/RedisCacheBenchmark.cs:18, MS.Microservice.Tasks/src/MS.Microservice.Tasks/JobExecutor.cs:112, samples/Lab/MS.Microservice.Lab/Controller/AccountController.cs:45, …
  • 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. (×4) — MS.Microservice.Persistence/benchmarks/MS.Microservice.Persistence.Auditing.Benchmarks/Program.cs:73, MS.Microservice.Persistence/benchmarks/MS.Microservice.Persistence.Auditing.Benchmarks/Program.cs:104, samples/Lab/MS.Microservice.Lab.DatabaseMigrator/Program.cs:49, …
  • No CancellationToken parameter — this work can't be stopped early once started. (×31) — MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:28, MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:33, MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:35, …

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard5.5 / 10Adequate✓ Tool-verified

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.

  • The guard on line 45 rejects `connectionString` and line 47 reports that rejection as `ArgumentNullException` — but the condition's own test `connectionString.IsNullOrEmpty()` is true of a value that is NOT null: it reads a member of `connectionString`, so it can only be evaluated on a non-null `connectionString` (a null one would throw `NullReferenceException` before the guard decided anything). So a caller whose `connectionString` is present but fails that test is told it was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — samples/Lab/MS.Microservice.Lab.Persistence/Microsoft/Extensions/DependencyInjection/EfCorePersistenceServiceCollectionExtensions.cs:47
  • The guard on line 23 rejects `optionsAccessor` and line 25 reports that rejection as `ArgumentNullException` — but the condition's own test `optionsAccessor.Value == null` is true of a value that is NOT null: it reads a member of `optionsAccessor`, so it can only be evaluated on a non-null `optionsAccessor` (a null one would throw `NullReferenceException` before the guard decided anything). So a caller whose `optionsAccessor` is present but fails that test is told it was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — samples/Lab/MS.Microservice.Lab/Application/Identity/SignInManager.cs:25
  • The guard on line 51 rejects `sheetName` and line 51 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sheetName)` is true of a value that is NOT null: it is satisfied by an EMPTY `sheetName`, and on that path `sheetName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/MS.Microservice.Excel/MiniExcelHelper.cs:51

What to do

  • Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

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. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.

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.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

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

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

X24 · Document value interpolated into markup unescaped2.7 / 10Weak✓ Tool-verified

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.

  • `request.HtmlBody` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:119
  • `email.HtmlBody` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:50

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob5.4 / 10Adequate✓ Tool-verified

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.

  • `benchmarks/MS.Microservice.Search.Benchmarks/Program.cs` is this program's entry point and formats with `CultureInfo.InvariantCulture` on line 163 — `id.ToString("D8", CultureInfo.InvariantCulture)` — yet writes 3 number(s) to standard output through a culture-sensitive format specifier with no format provider: `{id + 1:N0}` on line 60. Nothing in the project sets `CultureInfo.CurrentCulture` or `DefaultThreadCurrentCulture`, or turns on invariant globalization, so these numbers are spelled by whatever locale the host runs under: `70.3` on an en-US machine is `70,3` on a da-DK one, and a script or CI step that parses this output reads a different value, or fails, depending on where it ran. Set the culture once at the top of the entry point (`CultureInfo.CurrentCulture = CultureInfo.InvariantCulture;`) — or, if this output is meant for people in their own locale, pass `CultureInfo.CurrentCulture` explicitly so the omission stops reading as an oversight. — benchmarks/MS.Microservice.Search.Benchmarks/Program.cs:60

What to do

  • Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

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

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

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

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

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

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

X3 · Exception handling6.0 / 10Adequate✓ Tool-verified

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×17) — benchmarks/MS.Microservice.Framework.Benchmarks/AuditCaptureBenchmark.cs:33, MS.Microservice.Media/src/MS.Microservice.Media.Inference/VideoWatermarkRemoval/VideoWatermarkRemover.cs:131, MS.Microservice.Media/src/MS.Microservice.Media.Inference/WatermarkRemoval/WatermarkRemover.cs:73, …
  • `ContinueWith` with a continuation that does nothing discards the antecedent's failure — the task it returns completes successfully whether or not the work faulted, so the failure vanishes with no log and no rethrow. Await the task and handle the exception, or report the fault from the continuation (`t.Exception`). (×3) — samples/Lab/MS.Microservice.Lab/Application/BackgroundServices/BadPracticeBackgroundService.cs:41, samples/Lab/MS.Microservice.Lab/Application/BackgroundServices/HighPerformanceBackgroundService.cs:47, src/MS.Microservice.Processes/ProcessRunner.cs:79
  • 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). — samples/Lab/MS.Microservice.Lab/Application/Tools/ToolDemoSupport.cs:159
  • `catch (UglyToad.PdfPig.Exceptions.PdfDocumentEncryptedException)` 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. — REDACTED:114
  • `catch (Exception) when (…)` 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/MS.Microservice.Excel/ExcelHelper.cs:287

What to do

  • Swallowed exception (empty catch)
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.

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.

X4 · Structured logging7.4 / 10Strong✓ Tool-verified

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. — samples/Lab/MS.Microservice.Lab/Infrastructure/Authentications/ValidateTokenMiddleware.cs:86

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types9.4 / 10Exemplary✓ Tool-verified

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

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

  • ~0.7 `!` suppressions per 1k syntax nodes — 228 suppression(s) across the 328071 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 `!`.

WCAG coverage — what static analysis assessed

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

DimensionWCAG 2.2 A/AA criteriaCoverage
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

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

Reference — by lens

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

LensScoreRatingImpact
Code Health72%StrongSolid.
Architecture85%StrongSolid.
Maturity84%StrongSolid.
Readiness45%Weak — gated by D13, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security80%Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling83%StrongSolid.
Event-Driven87%StrongStrongest area.
Accessibility42%Weak — gated by AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance47%Weak — gated by PF3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 4 check(s) recorded observations but carry no score

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

  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • X10 Duplicated predicate — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.

  • 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.
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 28 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 image/media element found in the parsed markup — AC1 not applicable here.
  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — time="2026-11-08T12:05:25Z" level=warning msg="The \"KEYCLOAK_ADMIN_PASSWORD\" variable is not set. Defaulting to a blank string." time="2026-11-08T12:05:25Z" level=warning msg="The \"MS_REFERENCE_OPS_SECRET\" variable is not set. Defaulting to a blank string." container ms-reference-lab-postgres-1 exited (1); runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • D20 ADR Quality — 4 ADR(s) are written in a language our ADR lexicon does not cover, or are too short to tell (undetermined); their sections and statuses were not judged.
  • D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, Python not measured.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
  • D32 Data Compliance (PII/GDPR) — 103 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 analyzer's build of the target did not succeed
  • 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.
  • D8 Code Coverage — Coverage not measured
  • DM1 Domain Modelling — applicable but not scored (6 signals for this style, 3 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (entities that raise its domain events); 4 aggregate root(s) (AggregateRoot/IAggregateRoot); 30 value object(s); 2 domain event(s); a Domain/Aggregates/ValueObjects layer; 6 aggregate-constrained repository/repositories (IRepository<T> where T : IAggregateRoot); 2 per-aggregate domain namespaces (…/BasketAggregate, …/OrderAggregate); a top-level samples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
  • ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
  • ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an append-only event-store seam (IEventStore/Append-of-events))
  • M4 Documentation accuracy — Not measured: the documents' checkable claims are in prose of a language M4 has no cue lexicon for (see the gaps), so none was checked.
  • P10 Library API & versioning — Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P11 BDD / executable specs — BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P7 Outbound HTTP resilience — Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P8 Schema migrations — Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about 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
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 50 finding(s)
D17 · Explicit Debt · EmptyCatchBlock · ×18
  • EmptyCatchBlock MS.Microservice.Media/src/MS.Microservice.Media.Inference/VideoWatermarkRemoval/VideoWatermarkRemover.cs:131 — 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 MS.Microservice.Media/src/MS.Microservice.Media.Inference/WatermarkRemoval/WatermarkRemover.cs:73 — 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 MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/SqlSugarUnitOfWorkExtensions.cs:122 — 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 benchmarks/MS.Microservice.Framework.Benchmarks/AuditCaptureBenchmark.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 samples/Lab/MS.Microservice.Lab/Application/Tools/ToolDemoSupport.cs:159 — 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/MS.Microservice.Audio/AudioProcessor.cs:815 — 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/MS.Microservice.Audio/AudioProcessorExtensions.cs:333 — 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/MS.Microservice.Core/IO/LocalFileStorage.cs:98 — 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 REDACTED:281 — 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 REDACTED:282 — 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/MS.Microservice.Core/Text/TextEncodingConverter.cs:54 — 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/MS.Microservice.Excel/CsvHelper.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/MS.Microservice.Excel/CsvHelper.cs:239 — 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 REDACTED:71 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock REDACTED:80 — 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 REDACTED: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/MS.Microservice.Notifications/Inbox/LocalNotificationInbox.cs:85 — 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/MS.Microservice.Storage.S3/S3FileStorage.cs:124 — 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.
D30 · Dependency Vulnerabilities · High CVE · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · WriteOnlyPrivateField · ×4
  • WriteOnlyPrivateField MS.Microservice.AI/src/MS.Microservice.AI.Qwen/QwenImageReferenceEditClient.cs:18 — private IOptions<AIPayloadLimitOptions>? payloadLimits — 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 samples/Lab/MS.Microservice.Lab.Domain/Managers/UserManager.cs:7 — private IUserRepository _userRepository — 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 samples/Lab/MS.Microservice.Lab/Application/Identity/SignInManager.cs:15 — private ILogger<SignInManager> _logger — 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 samples/Lab/MS.Microservice.Lab/Controller/AccountController.cs:23 — private SignInManager _signInManager — 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.
D13 · REDACTED Scanning · Leaked secret · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · NoWarnInCsproj · ×3
  • NoWarnInCsproj Directory.Build.props:12 — 1591 — 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 Directory.Build.props:12 — EXTEXP0018 — 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 Directory.Packages.props:5 — NU1507 — 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.
D28 · Secrets (history) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×3
  • Domain depends on infrastructure: LogRepository samples/Lab/MS.Microservice.Lab.Persistence/Repository/LogRepository.cs:16 — `LogRepository` (a domain rule: it decides over the repository's entities) names `ActivationDbContext` from `MS.Microservice.Persistence.EFCore.DbContext` — a persistence/infrastructure type (in a member signature). Move the queries to the caller and pass the loaded values to a pure decision method.
  • Domain depends on infrastructure: LogRepository samples/Lab/MS.Microservice.Lab.Persistence/Repository/LogRepository.cs:18 — `LogRepository` (a domain rule: it decides over the repository's entities) names `ActivationDbContext` from `MS.Microservice.Persistence.EFCore.DbContext` — a persistence/infrastructure type (in a member signature). Move the queries to the caller and pass the loaded values to a pure decision method.
  • Domain depends on infrastructure: LogRepository samples/Lab/MS.Microservice.Lab.Persistence/Repository/LogRepository.cs:65 — `LogRepository` (a domain rule: it decides over the repository's entities) names `EntityState` from `Microsoft.EntityFrameworkCore` — a persistence type (in a method body). Move the queries to the caller and pass the loaded values to a pure decision method.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <textarea> without a programmatic label · ×1
  • <textarea> without a programmatic label .github/skills/skill-creator/eval-viewer/viewer.html:604 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC3 · Page structure · <html> without a lang · ×1
  • <html> without a lang .github/skills/baoyu-url-to-markdown/scripts/html-to-markdown.ts:174 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure · Document without a <title> · ×1
  • Document without a <title> .github/skills/baoyu-url-to-markdown/scripts/html-to-markdown.ts:174 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
D10 · Test Quality · No assertions (empty test) · ×1
  • No assertions (empty test): Test1 test/MS.Microservice.Core.Tests/UnitTest1.cs:5 — Test method has an empty body — it asserts nothing and exercises no code.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×1
  • REDACTED
ED4 · Outbox / dual-write · Dual write (no outbox) · ×1
  • Dual write (no outbox): SmtpEmailSender.SendAsync REDACTED:30 — `SmtpEmailSender.SendAsync` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Serious — 615 finding(s)
D17 · Explicit Debt · Dead code · ×144
  • Dead code: RealModel_PortraitTransparentEdgesAndExifPreserveRgbAndSourceAlphaWithMatchingMatte MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/BackgroundRemoval/BiRefNetBackgroundRemoverTests.cs:28 — Method RealModel_PortraitTransparentEdgesAndExifPreserveRgbAndSourceAlphaWithMatchingMatte — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: QueuedCancellationAndDisposal_DoNotReadQueuedInputsOrReleaseActiveSessionEarly MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/BackgroundRemoval/BiRefNetBackgroundRemoverTests.cs:105 — Method QueuedCancellationAndDisposal_DoNotReadQueuedInputsOrReleaseActiveSessionEarly — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: EncodedAndRasterLimits_RejectBeforeInferenceAndLeaveStreamsOpen MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/BackgroundRemoval/BiRefNetBackgroundRemoverTests.cs:136 — Method EncodedAndRasterLimits_RejectBeforeInferenceAndLeaveStreamsOpen — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: RealModel_PngOutsidePixelsMatchNormalizedBaselineIncludingSemitransparency MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/MiganInpainterTests.cs:183 — Method RealModel_PngOutsidePixelsMatchNormalizedBaselineIncludingSemitransparency — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: EmptyMask_IsIdentityEvenBelowModelMinimumDimensions MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/MiganInpainterTests.cs:234 — Method EmptyMask_IsIdentityEvenBelowModelMinimumDimensions — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: StreamAndMaskValidation_DoesNotCloseCallerStreams MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/MiganInpainterTests.cs:268 — Method StreamAndMaskValidation_DoesNotCloseCallerStreams — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: PreCancellationAndInputLimits_DoNotPublishOutput MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/MiganInpainterTests.cs:282 — Method PreCancellationAndInputLimits_DoNotPublishOutput — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: CancellationDuringInputRead_ReleasesGateAndLeavesCallerStreamsOpen MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/MiganInpainterTests.cs:299 — Method CancellationDuringInputRead_ReleasesGateAndLeavesCallerStreamsOpen — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: CancellationWhileQueued_DoesNotReadInputsOrCancelActiveRequest MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/MiganInpainterTests.cs:328 — Method CancellationWhileQueued_DoesNotReadInputsOrCancelActiveRequest — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: Dispose_WaitsForActiveOperationQueuedCallsObserveDisposedAndRepeatedDisposalIsSafe MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/MiganInpainterTests.cs:355 — Method Dispose_WaitsForActiveOperationQueuedCallsObserveDisposedAndRepeatedDisposalIsSafe — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: PrintedBilingualText_UsesActualModelsAndReturnsLocatedImmutableRegions MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/Ocr/OcrProcessorTests.cs:127 — Method PrintedBilingualText_UsesActualModelsAndReturnsLocatedImmutableRegions — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: BlankAndTransparentImages_ReturnNoInventedText MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/Ocr/OcrProcessorTests.cs:175 — Method BlankAndTransparentImages_ReturnNoInventedText — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: LongText_IsRecognizedWithoutSilentWidthClipping MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/Ocr/OcrProcessorTests.cs:189 — Method LongText_IsRecognizedWithoutSilentWidthClipping — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: NonSeekableAndExactEncodedBudget_PreserveCallerOwnership MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/Ocr/OcrProcessorTests.cs:237 — Method NonSeekableAndExactEncodedBudget_PreserveCallerOwnership — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: CompressedSource_UsesIndependentIntermediateBudget MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/Ocr/OcrProcessorTests.cs:249 — Method CompressedSource_UsesIndependentIntermediateBudget — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: CorruptModel_IsRejectedBeforeInferenceAndDoesNotUseAFallback MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/Ocr/OcrProcessorTests.cs:286 — Method CorruptModel_IsRejectedBeforeInferenceAndDoesNotUseAFallback — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: RealLearnedOutputIsNotAnOrdinaryPixelReplication MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/SuperResolution/Swin2SrUpscalerTests.cs:92 — Method RealLearnedOutputIsNotAnOrdinaryPixelReplication — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: BudgetsAreCheckedBeforeAnyDestinationBytesAreWritten MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/SuperResolution/Swin2SrUpscalerTests.cs:107 — Method BudgetsAreCheckedBeforeAnyDestinationBytesAreWritten — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: KeepsCurrentPositionsAndSupportsNonSeekableInput MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/SuperResolution/Swin2SrUpscalerTests.cs:118 — Method KeepsCurrentPositionsAndSupportsNonSeekableInput — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: CancellationAndDisposalDoNotPublishSuccessOrBreakALaterCall MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/SuperResolution/Swin2SrUpscalerTests.cs:135 — Method CancellationAndDisposalDoNotPublishSuccessOrBreakALaterCall — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: RejectsAliasedOrDamagedInputsAndEnforcesInputBytes MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/SuperResolution/Swin2SrUpscalerTests.cs:156 — Method RejectsAliasedOrDamagedInputsAndEnforcesInputBytes — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: BlankImage_ReturnsNeitherInventedGridNorText MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/Tables/TableRecognizerTests.cs:174 — Method BlankImage_ReturnsNeitherInventedGridNorText — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: TwoTables_StaySeparateAndAssignEveryRegionExactlyOnce MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/Tables/TableRecognizerTests.cs:189 — Method TwoTables_StaySeparateAndAssignEveryRegionExactlyOnce — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: MultilineEmptyCellsAndOutsideText_ArePreservedWithoutInventedContent MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/Tables/TableRecognizerTests.cs:203 — Method MultilineEmptyCellsAndOutsideText_ArePreservedWithoutInventedContent — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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: ActualTextCrossingCellBorder_RemainsUnassignedWithoutBeingDroppedOrDuplicated MS.Microservice.Media/test/MS.Microservice.Media.Inference.Tests/Tables/TableRecognizerTests.cs:215 — Method ActualTextCrossingCellBorder_RemainsUnassignedWithoutBeingDroppedOrDuplicated — Roslyn's SymbolFinder walked every project the solution loads, including MS.Microservice.Media.Inference.Tests, 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.
  • + 119 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 51 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×31
  • Async method without CancellationToken: AnyAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:28 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:33 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddAReturnIdsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:35 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddListAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:39 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetModelAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:45 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetPagesAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:47 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetListAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:59 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetListAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:65 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetListAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:67 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:69 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:75 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:81 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:88 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:94 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:100 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AnyAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs:25 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs:30 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddAReturnIdsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs:32 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddListAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs:36 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetModelAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetPagesAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs:44 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetListAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs:55 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetListAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs:60 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetListAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs:62 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateAsync MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs:64 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 6 more in this group — see findings.md.
PF3 · Async & latency hygiene · Awaits without ConfigureAwait(false) · ×28
  • Awaits without ConfigureAwait(false) — Only 180/426 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
  • Awaits without ConfigureAwait(false) MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs:30 — `await using … = await rateLimiter.AcquireAsync(context, cancellationToken).Configur...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs:58 — `await using … = await rateLimiter.AcquireAsync(context, cancellationToken).Configur...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleAsrProviderBase.cs:40 — `await using … = await httpResponse.Content.ReadAsStreamAsync(requestCancellationTok...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleChatProviderBase.cs:129 — `await using … = ParseStreamAsync(stream, model, request, streamCancellation.Token)....` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleChatProviderBase.cs:308 — `await using … = await httpResponse.Content.ReadAsStreamAsync(cancellationToken).Con...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleImageGenerationProviderBase.cs:67 — `await using … = await httpResponse.Content.ReadAsStreamAsync(cancellationToken).Con...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.AI/src/MS.Microservice.AI.Qwen/QwenImageEditProvider.cs:111 — `await using … = await httpResponse.Content.ReadAsStreamAsync(cancellationToken) .Co...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Idempotency/src/MS.Microservice.Idempotency.EFCore/EfCoreIdempotencyStore.cs:17 — `await context.Set<IdempotencyRecord>().AsNoTracking().SingleOrDefaultAsync( row => ...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Idempotency/src/MS.Microservice.Idempotency.EFCore/EfCoreIdempotencyStore.cs:53 — `await context.SaveChangesAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Idempotency/src/MS.Microservice.Idempotency.EFCore/EfCoreIdempotencyStore.cs:55 — `await operation(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Idempotency/src/MS.Microservice.Idempotency.EFCore/EfCoreIdempotencyStore.cs:62 — `await context.SaveChangesAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Logging/src/MS.Microservice.Logging.AspNetCore/MsRequestLoggingMiddleware.cs:41 — `await _next(context)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Messaging/src/MS.Microservice.Messaging.Abstractions/Contracts.cs:31 — `await unitOfWork.ExecuteAsync(async token => { await operation(token); return true;...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Messaging/src/MS.Microservice.Messaging.Abstractions/Contracts.cs:31 — `await operation(token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:17 — `await ConsumeSessionAsync(stoppingToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:20 — `await Task.Delay(options.ReconnectDelay, stoppingToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:28 — `await using … = await factory.CreateConnectionAsync(session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:28 — `await factory.CreateConnectionAsync(session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:29 — `await using … = await connection.CreateChannelAsync( new CreateChannelOptions(publi...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:29 — `await connection.CreateChannelAsync( new CreateChannelOptions(publisherConfirmation...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:36 — `await channel.ExchangeDeclarePassiveAsync(options.Exchange, session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:37 — `await channel.BasicQosAsync(0, options.PrefetchCount, global: false, session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:41 — `await channel.QueueDeclarePassiveAsync(queue, session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • Awaits without ConfigureAwait(false) MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/RabbitMqConsumerService.cs:42 — `await channel.QueueDeclarePassiveAsync(queue + ".dead", session.Token)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
  • + 3 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×18
  • Swallowed exception (empty catch) benchmarks/MS.Microservice.Framework.Benchmarks/AuditCaptureBenchmark.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) MS.Microservice.Media/src/MS.Microservice.Media.Inference/VideoWatermarkRemoval/VideoWatermarkRemover.cs:131 — 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) MS.Microservice.Media/src/MS.Microservice.Media.Inference/WatermarkRemoval/WatermarkRemover.cs:73 — 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) MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/SqlSugarUnitOfWorkExtensions.cs:122 — 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) samples/Lab/MS.Microservice.Lab/Application/Tools/ToolDemoSupport.cs:159 — 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/MS.Microservice.Audio/AudioProcessor.cs:815 — 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/MS.Microservice.Audio/AudioProcessorExtensions.cs:333 — 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/MS.Microservice.Core/IO/LocalFileStorage.cs:98 — 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) REDACTED:281 — 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) REDACTED:282 — 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/MS.Microservice.Core/Text/TextEncodingConverter.cs:54 — 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/MS.Microservice.Excel/CsvHelper.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.
  • Swallowed exception (empty catch) src/MS.Microservice.Excel/CsvHelper.cs:239 — 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) REDACTED:71 — 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) REDACTED:80 — 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) REDACTED: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/MS.Microservice.Notifications/Inbox/LocalNotificationInbox.cs:85 — 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/MS.Microservice.Storage.S3/S3FileStorage.cs:124 — 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.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×12
  • Sync-over-async blocking — 13 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 benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:41 — `.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 benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:42 — `.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 benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:43 — `.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 benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:44 — `.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 benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:45 — `.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 benchmarks/MS.Microservice.Framework.Benchmarks/RedisCacheBenchmark.cs:76 — `.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 benchmarks/MS.Microservice.Framework.Benchmarks/RedisCacheBenchmark.cs:78 — `.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 samples/Lab/MS.Microservice.Lab/Infrastructure/Applications/Users/CurrentUserResolver.cs:30 — `.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/MS.Microservice.Core/Common/Advance/Resilience/RetryExecutor.cs:112 — `.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 benchmarks/MS.Microservice.Core.HttpLogging.Benchmarks/Program.cs:58 — `.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 benchmarks/MS.Microservice.Core.HttpLogging.Benchmarks/Program.cs:59 — `.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).
X1 · Async correctness · Sync-over-async (deadlock risk) · ×11
  • Sync-over-async (deadlock risk) benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:41 — 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) benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:42 — 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) benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:43 — 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) benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:44 — 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) benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:45 — 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) benchmarks/MS.Microservice.Framework.Benchmarks/RedisCacheBenchmark.cs:76 — 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) benchmarks/MS.Microservice.Framework.Benchmarks/RedisCacheBenchmark.cs:78 — 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) samples/Lab/MS.Microservice.Lab/Infrastructure/Applications/Users/CurrentUserResolver.cs:30 — 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/MS.Microservice.Core/Common/Advance/Resilience/RetryExecutor.cs:112 — 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) benchmarks/MS.Microservice.Core.HttpLogging.Benchmarks/Program.cs:58 — 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) benchmarks/MS.Microservice.Core.HttpLogging.Benchmarks/Program.cs:59 — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×6
  • Duplicated block (8 lines × 2) MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/SelfManagedPublisher.cs:24 — MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/SelfManagedPublisher.cs:24-31 | MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/SelfManagedReceiver.cs:34-41 — 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 `MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/SelfManagedPublisher.cs:24` 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 (8 lines × 2) MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:50 — MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs:50-57 | MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs:46-53 — before extracting anything, compare `MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs` and `MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 (8 lines × 2) src/MS.Microservice.Audio/AudioFileFormatDetector.cs:146 — src/MS.Microservice.Audio/AudioFileFormatDetector.cs:146-153 | src/MS.Microservice.Audio/AudioProcessor.cs:580-587 — 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.
  • Duplicated block (8 lines × 2) .github/skills/skill-creator/scripts/run_eval.py:270 — .github/skills/skill-creator/scripts/run_eval.py:270-277 | .github/skills/skill-creator/scripts/run_loop.py:259-266 — 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, `.github/skills/skill-creator/scripts/run_loop.py:257` calls `add_argument` and `.github/skills/skill-creator/scripts/run_eval.py:269` 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) samples/Lab/MS.Microservice.Lab/Application/Tools/VideoToolForms.cs:96 — samples/Lab/MS.Microservice.Lab/Application/Tools/VideoToolForms.cs:96-103 | samples/Lab/MS.Microservice.Lab/Application/Tools/VideoToolForms.cs:108-115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) samples/Lab/MS.Microservice.Lab/Application/Commands/UserCreatedCommand.cs:14 — samples/Lab/MS.Microservice.Lab/Application/Commands/UserCreatedCommand.cs:14-21 | samples/Lab/MS.Microservice.Lab/Application/Commands/UserModifyCommand.cs:14-22 — 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.
D31 · IaC & Container Security · Medium IaC · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×5
  • Duplicated block (5 lines × 2) MS.Microservice.Tasks/src/MS.Microservice.Tasks.EFCore/JobModelBuilderExtensions.cs:18 — MS.Microservice.Tasks/src/MS.Microservice.Tasks.EFCore/JobModelBuilderExtensions.cs:18-22 | MS.Microservice.Tasks/src/MS.Microservice.Tasks.EFCore/JobModelBuilderExtensions.cs:30-34 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 2) MS.Microservice.Media/src/MS.Microservice.Media.Inference/BackgroundRemoval/BiRefNetBackgroundRemover.cs:94 — MS.Microservice.Media/src/MS.Microservice.Media.Inference/BackgroundRemoval/BiRefNetBackgroundRemover.cs:94-98 | MS.Microservice.Media/src/MS.Microservice.Media.Inference/SuperResolution/Swin2SrUpscaler.cs:108-112 — before extracting anything, compare `MS.Microservice.Media/src/MS.Microservice.Media.Inference/BackgroundRemoval/BiRefNetBackgroundRemover.cs` and `MS.Microservice.Media/src/MS.Microservice.Media.Inference/SuperResolution/Swin2SrUpscaler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (5 lines × 2) MS.Microservice.Persistence/src/MS.Microservice.Persistence.EFCore/Auditing/AuditRecord.cs:35 — MS.Microservice.Persistence/src/MS.Microservice.Persistence.EFCore/Auditing/AuditRecord.cs:35-39 | REDACTED:245-249 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/ocr_worker.py:33 — MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/ocr_worker.py:33-37 | MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/watermark_detector.py:27-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) samples/Lab/MS.Microservice.Lab.Domain/Identity/UserClaimHelper.cs:15 — samples/Lab/MS.Microservice.Lab.Domain/Identity/UserClaimHelper.cs:15-19 | samples/Lab/MS.Microservice.Lab/Application/Identity/SignInManager.cs:87-91 — 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×5
  • Swallowed exception (caught, then discarded) samples/Lab/MS.Microservice.Lab/Application/BackgroundServices/BadPracticeBackgroundService.cs:41 — `ContinueWith` with a continuation that does nothing discards the antecedent's failure — the task it returns completes successfully whether or not the work faulted, so the failure vanishes with no log and no rethrow. Await the task and handle the exception, or report the fault from the continuation (`t.Exception`).
  • Swallowed exception (caught, then discarded) samples/Lab/MS.Microservice.Lab/Application/BackgroundServices/HighPerformanceBackgroundService.cs:47 — `ContinueWith` with a continuation that does nothing discards the antecedent's failure — the task it returns completes successfully whether or not the work faulted, so the failure vanishes with no log and no rethrow. Await the task and handle the exception, or report the fault from the continuation (`t.Exception`).
  • Swallowed exception (caught, then discarded) REDACTED:114 — `catch (UglyToad.PdfPig.Exceptions.PdfDocumentEncryptedException)` 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/MS.Microservice.Excel/ExcelHelper.cs:287 — `catch (Exception) when (…)` 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/MS.Microservice.Processes/ProcessRunner.cs:79 — `ContinueWith` with a continuation that does nothing discards the antecedent's failure — the task it returns completes successfully whether or not the work faulted, so the failure vanishes with no log and no rethrow. Await the task and handle the exception, or report the fault from the continuation (`t.Exception`).
D12 · Dependency Hygiene · Prerelease dependency · ×4
  • Prerelease dependency: SqlSugarCore — SqlSugarCore resolves to 5.1.4.211-preview10, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: Lucene.Net — Lucene.Net resolves to 4.8.0-beta00018, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: Lucene.Net.Analysis.Common — Lucene.Net.Analysis.Common resolves to 4.8.0-beta00018, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
  • Prerelease dependency: Lucene.Net.Misc — Lucene.Net.Misc resolves to 4.8.0-beta00018, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
D17 · Explicit Debt · TodoComment · ×4
  • TodoComment samples/Lab/MS.Microservice.Lab.Domain/Aggregates/IdentityModel/Repository/IRoleRepository.cs:3 — // TODO: 待考虑 — 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 samples/Lab/MS.Microservice.Lab.Domain/Aggregates/MerchandiseAggregate/Enums/ThirdSystemEnum.cs:3 — // TODO: 抽象成表,要在界面上交互 — 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 samples/Lab/MS.Microservice.Lab/Application/BackgroundServices/BadPracticeBackgroundService.cs:32 — // TODO:后台作业待配置化 — 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/MS.Microservice.Core/EventBus/EventBusManager.cs:33 — // TODO:兼容多个相同类型的事件订阅 — 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.
D17 · Explicit Debt · HackComment · ×4
  • HackComment src/MS.Microservice.Core/Functional/Data/BinaryTree.cs:7 — // hack — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment src/MS.Microservice.Core/Functional/Data/BinaryTree.cs:10 — // hack — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment src/MS.Microservice.Core/Functional/Data/Bst.cs:16 — // hack — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment src/MS.Microservice.Core/Functional/Data/Bst.cs:19 — // hack — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D3 · God Classes · TooManyMethods · ×4
  • TooManyMethods: ExcelHelper src/MS.Microservice.Excel/ExcelHelper.cs — TooManyMethods — 644 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 30 methods; this is 25 over it, 1.83× 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: ObservedSchedule MS.Microservice.Tasks/src/MS.Microservice.Tasks.Dashboard/CoravelScheduleCatalog.cs — TooManyMethods — 47 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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: AudioProcessor src/MS.Microservice.Audio/AudioProcessor.cs — TooManyMethods — 303 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: EfCoreJobStore MS.Microservice.Tasks/src/MS.Microservice.Tasks.EFCore/EfCoreJobStore.cs — TooManyMethods — 278 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. 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.
D5 · Coupling · Off the main sequence · ×4
  • Off the main sequence: MS.Microservice.Logging.Core MS.Microservice.Logging/src/MS.Microservice.Logging.Core/MS.Microservice.Logging.Core.csproj:1 — MS.Microservice.Logging.Core: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: MS.Microservice.Threading src/MS.Microservice.Threading/MS.Microservice.Threading.csproj:1 — MS.Microservice.Threading: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: MS.Microservice.Tasks MS.Microservice.Tasks/src/MS.Microservice.Tasks/MS.Microservice.Tasks.csproj:1 — MS.Microservice.Tasks: abstractness 0.21, instability 0.00, distance 0.79 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: MS.Microservice.EventBus src/MS.Microservice.EventBus/MS.Microservice.EventBus.csproj:1 — MS.Microservice.EventBus: abstractness 0.71, instability 1.00, distance 0.71 — zone of uselessness — abstract and unstable, so it's likely unused.
X1 · Async correctness · Blocking `MemoryStream.Write` inside an `async` method · ×4
  • Blocking `MemoryStream.Write` inside an `async` method MS.Microservice.Media/src/MS.Microservice.Media/Images/ImageCodec.cs:21 — `MemoryStream.Write` blocks the thread on I/O while `MemoryStream.WriteAsync` exists to wait without one — inside a method that is already `async`, await the twin.
  • Blocking `MemoryStream.Write` inside an `async` method samples/Lab/MS.Microservice.Lab/Application/Tools/ImageBatchJobs.cs:302 — `MemoryStream.Write` blocks the thread on I/O while `MemoryStream.WriteAsync` exists to wait without one — inside a method that is already `async`, await the twin.
  • Blocking `MemoryStream.Write` inside an `async` method src/MS.Microservice.Documents.Rendering/RenderWorkerSupervisor.cs:154 — `MemoryStream.Write` blocks the thread on I/O while `MemoryStream.WriteAsync` exists to wait without one — inside a method that is already `async`, await the twin.
  • Blocking `MemoryStream.Write` inside an `async` method src/MS.Microservice.Notifications/Inbox/LocalNotificationInbox.cs:113 — `MemoryStream.Write` blocks the thread on I/O while `MemoryStream.WriteAsync` exists to wait without one — inside a method that is already `async`, await the twin.
X2 · Cancellation propagation · Async local function without CancellationToken · ×4
  • Async local function without CancellationToken: Execute MS.Microservice.Persistence/benchmarks/MS.Microservice.Persistence.Auditing.Benchmarks/Program.cs:73 — 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.
  • Async local function without CancellationToken: AuditCount MS.Microservice.Persistence/benchmarks/MS.Microservice.Persistence.Auditing.Benchmarks/Program.cs:104 — 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.
  • Async local function without CancellationToken: MigrateActivationAsync samples/Lab/MS.Microservice.Lab.DatabaseMigrator/Program.cs:49 — 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.
  • Async local function without CancellationToken: MigrateEventStoreAsync samples/Lab/MS.Microservice.Lab.DatabaseMigrator/Program.cs:71 — 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.
AC3 · Page structure · Page without a main landmark · ×3
  • Page without a main landmark .github/skills/baoyu-url-to-markdown/scripts/html-to-markdown.ts:174 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark .github/skills/skill-creator/assets/eval_review.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark .github/skills/skill-creator/eval-viewer/viewer.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.1 · ×3
  • Low contrast colour pair in CSS (2.1:1) .github/skills/skill-creator/eval-viewer/viewer.html:83 — `.section-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.1:1) .github/skills/skill-creator/eval-viewer/viewer.html:136 — `.output-file-header` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.1:1) .github/skills/skill-creator/eval-viewer/viewer.html:221 — `.prev-feedback` sets color: #b0aea5 on background-color: #faf9f5 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AX2 · Stateful singletons · Stateful singleton · ×3
  • Stateful singleton: JobExecutionOptions MS.Microservice.Tasks/src/MS.Microservice.Tasks/JobExecutionContracts.cs:38 — `JobExecutionOptions` is a singleton (one shared instance) but mutates instance state outside any lock (_queues; e.g. `_queues` at line 52).
  • Stateful singleton: EventTypeRegistry samples/Lab/MS.Microservice.Lab.Infrastructure/EventSourcing/Serialization/SystemTextJsonEventSerializer.cs:8 — `EventTypeRegistry` is a singleton (one shared instance) but mutates instance state outside any lock (_eventTypes, _eventNames; e.g. `_eventTypes` at line 18).
  • Stateful singleton: ToolInferenceRuntime samples/Lab/MS.Microservice.Lab/Application/Tools/ToolInferenceRuntime.cs:10 — `ToolInferenceRuntime` is a singleton (one shared instance) but mutates instance state outside any lock (_repair, _automatic, _upscaler, _background; e.g. `_repair` at line 37).
D10 · Test Quality · Races the wall clock · ×3
  • Races the wall clock: EventIdentityUsesLosslessStorageInsteadOfDatabaseTimestampPrecision MS.Microservice.Messaging/test/MS.Microservice.Messaging.SelfManaged.Tests/EventTimePrecisionTests.cs:10 — This test reads `DateTime.UtcNow` and compares it against the real system clock (`TimeProvider.System`) handed to the code under test. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
  • Races the wall clock: DuplicateIdentityDoesNotPublishAnotherChange test/MS.Microservice.Reference.Application.Tests/ProfileServiceTests.cs:31 — This test reads `DateTimeOffset.UtcNow` and compares it against the real system clock (`TimeProvider.System`) handed to the code under test. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
  • Races the wall clock: StaleVersionCannotChangeOrPublish test/MS.Microservice.Reference.Application.Tests/ProfileServiceTests.cs:44 — This test reads `DateTimeOffset.UtcNow` and compares it against the real system clock (`TimeProvider.System`) handed to the code under test. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
D15 · Churn × Complexity Hotspots · Hotspot · ×3
  • Hotspot: src/MS.Microservice.Documents.Rendering/RenderWorkerSupervisor.cs src/MS.Microservice.Documents.Rendering/RenderWorkerSupervisor.cs:20 — src/MS.Microservice.Documents.Rendering/RenderWorkerSupervisor.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in RenderWorkerSupervisor.RunCoreAsync at line 20. 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-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 11:26:01 +08:00' --until='2026-10-26 11:26:01 +08:00' --full-history --no-merges -- src/MS.Microservice.Documents.Rendering/RenderWorkerSupervisor.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/MS.Microservice.Excel/ExcelHelper.cs src/MS.Microservice.Excel/ExcelHelper.cs:251 — src/MS.Microservice.Excel/ExcelHelper.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in ExcelHelper.ReadRows at line 251. 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-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 11:26:01 +08:00' --until='2026-10-26 11:26:01 +08:00' --full-history --no-merges -- src/MS.Microservice.Excel/ExcelHelper.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: samples/Reference/MS.Microservice.Reference.Web/HttpIdempotency/ReferenceHttpIdempotencyExecutor.cs samples/Reference/MS.Microservice.Reference.Web/HttpIdempotency/ReferenceHttpIdempotencyExecutor.cs:26 — samples/Reference/MS.Microservice.Reference.Web/HttpIdempotency/ReferenceHttpIdempotencyExecutor.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in ReferenceHttpIdempotencyExecutor.ExecuteAsync at line 26. 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-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 11:26:01 +08:00' --until='2026-10-26 11:26:01 +08:00' --full-history --no-merges -- samples/Reference/MS.Microservice.Reference.Web/HttpIdempotency/ReferenceHttpIdempotencyExecutor.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs:25 — MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs:25-31 | MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs:53-59 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/MessageEntries.cs:9 — MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/MessageEntries.cs:9-15 | MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/MessageEntries.cs:42-48 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) samples/Lab/MS.Microservice.Lab/Application/Tools/ImageToolForms.cs:11 — samples/Lab/MS.Microservice.Lab/Application/Tools/ImageToolForms.cs:11-17 | samples/Lab/MS.Microservice.Lab/Application/Tools/VideoToolForms.cs:73-79 — 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.
DM12 · Ambient inputs in the domain · Domain type reads the wall clock · ×3
  • Domain type reads the wall clock: OutboxMessage samples/Lab/MS.Microservice.Lab.Domain/Events/OutboxMessage.cs:48 — `OutboxMessage` reads `DateTimeOffset.UtcNow` inside `Create` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has.
  • Domain type reads the wall clock: PasswordSaltHelper samples/Lab/MS.Microservice.Lab.Domain/Aggregates/IdentityModel/PasswordSaltHelper.cs:12 — `PasswordSaltHelper` reads `DateTime.Now` inside `Generate` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has.
  • Domain type reads the wall clock: User samples/Lab/MS.Microservice.Lab.Domain/Aggregates/IdentityModel/User.cs:103 — `User` reads `DateTime.Now` inside `Delete` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×3
  • Disposable created and abandoned in the method that made it src/MS.Microservice.Core/Security/Summary/Md5.cs:13 — `md5` is a `MD5`, which implements `IDisposable`, and it is created here (line 13). Every use of it in `Encrypt` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var md5 = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/MS.Microservice.Documents.Rendering/HtmlRenderWorker.cs:92 — `output` is a `Stream`, which implements `IDisposable`, and it is created here (line 92). Every use of it in `RunAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var output = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/MS.Microservice.Documents.Rendering/WordRenderWorker.cs:54 — `destination` is a `Stream`, which implements `IDisposable`, and it is created here (line 54). Every use of it in `RunAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var destination = …;`), which releases it at the end of the scope on every path including a throw.
X20 · Mistyped argument guard · Argument guard throws the exception its own condition disproves · ×3
  • Argument guard throws the exception its own condition disproves samples/Lab/MS.Microservice.Lab.Persistence/Microsoft/Extensions/DependencyInjection/EfCorePersistenceServiceCollectionExtensions.cs:47 — The guard on line 45 rejects `connectionString` and line 47 reports that rejection as `ArgumentNullException` — but the condition's own test `connectionString.IsNullOrEmpty()` is true of a value that is NOT null: it reads a member of `connectionString`, so it can only be evaluated on a non-null `connectionString` (a null one would throw `NullReferenceException` before the guard decided anything). So a caller whose `connectionString` is present but fails that test is told it was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves samples/Lab/MS.Microservice.Lab/Application/Identity/SignInManager.cs:25 — The guard on line 23 rejects `optionsAccessor` and line 25 reports that rejection as `ArgumentNullException` — but the condition's own test `optionsAccessor.Value == null` is true of a value that is NOT null: it reads a member of `optionsAccessor`, so it can only be evaluated on a non-null `optionsAccessor` (a null one would throw `NullReferenceException` before the guard decided anything). So a caller whose `optionsAccessor` is present but fails that test is told it was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves src/MS.Microservice.Excel/MiniExcelHelper.cs:51 — The guard on line 51 rejects `sheetName` and line 51 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sheetName)` is true of a value that is NOT null: it is satisfied by an EMPTY `sheetName`, and on that path `sheetName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.1 · ×2
  • Low contrast colour pair in CSS (3.1:1) .github/skills/skill-creator/assets/eval_review.html:19 — `.btn-export` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.1:1) .github/skills/skill-creator/eval-viewer/viewer.html:467 — `.done-btn.ready` sets color: white on background-color: #d97757 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D12 · Dependency Hygiene · Deprecated · ×2
  • Deprecated: xunit Directory.Packages.props:100 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: Microsoft.ApplicationInsights.AspNetCore Directory.Packages.props:24 — Microsoft.ApplicationInsights.AspNetCore 2.22.0 — Other
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · MethodTooLong · ×2
  • MethodTooLong: QuestionGenerationHarness.RunAsync MS.Microservice.AI/src/MS.Microservice.AI.QuestionGeneration/Pipeline/QuestionGenerationHarness.cs:28 — MethodTooLong — RunAsync runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× 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: RedisCacheBenchmark.RunAsync benchmarks/MS.Microservice.Framework.Benchmarks/RedisCacheBenchmark.cs:18 — MethodTooLong — RunAsync runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× 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.
D3 · God Classes · ClassTooLong · ×2
  • ClassTooLong: VideoProcessor MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Editing.cs — ClassTooLong — 427 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods, declared across 5 files: Video/VideoProcessor.Editing.cs (7), Video/VideoProcessor.cs (6), Video/VideoProcessor.Assets.cs (4), Video/VideoProcessor.Concatenation.cs (3), +1 more file(s). The bar is 400 significant lines; this is 27 over it, 1.07× 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.
  • ClassTooLong: QuestionGenerationHarness MS.Microservice.AI/src/MS.Microservice.AI.QuestionGeneration/Pipeline/QuestionGenerationHarness.cs — ClassTooLong — 419 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 19 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleMediaProviderBase.cs:91 — MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleMediaProviderBase.cs:91-101 | MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleMediaProviderBase.cs:248-258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleMediaProviderBase.cs:103` calls `Create` and `MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleMediaProviderBase.cs:260` 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 (11 lines × 2) samples/Lab/MS.Microservice.Lab/Application/BackgroundServices/BadPracticeBackgroundService.cs:44 — samples/Lab/MS.Microservice.Lab/Application/BackgroundServices/BadPracticeBackgroundService.cs:44-54 | samples/Lab/MS.Microservice.Lab/Application/BackgroundServices/HighPerformanceBackgroundService.cs:78-88 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) MS.Microservice.Media/src/MS.Microservice.Media/Images/ImageProcessingOptions.cs:21 — MS.Microservice.Media/src/MS.Microservice.Media/Images/ImageProcessingOptions.cs:21-26 | MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoEditOptions.cs:11-16 — 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 (6 lines × 2) .github/skills/skill-creator/scripts/run_eval.py:261 — .github/skills/skill-creator/scripts/run_eval.py:261-266 | .github/skills/skill-creator/scripts/run_loop.py:246-251 — 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 after the matched lines, `.github/skills/skill-creator/scripts/run_loop.py:253` calls `add_argument` and `.github/skills/skill-creator/scripts/run_eval.py:268` 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.
X1 · Async correctness · Blocking `SemaphoreSlim.Wait` inside an `async` method · ×2
  • Blocking `SemaphoreSlim.Wait` inside an `async` method MS.Microservice.Tasks/src/MS.Microservice.Tasks/JobExecutor.cs:80 — `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/MS.Microservice.Caching/GovernedCache.cs:92 — `SemaphoreSlim.Wait` parks the thread while it queues for the semaphore. `await semaphore.WaitAsync(…)` yields the thread instead.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×2
  • Untrusted text written into markup unescaped REDACTED:119 — `request.HtmlBody` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:50 — `email.HtmlBody` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.9 · ×1
  • Low contrast colour pair in CSS (2.9:1) .github/skills/skill-creator/assets/eval_review.html:17 — `.btn-add` sets color: white on background-color: #6a9bcc — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×1
  • Animation without a prefers-reduced-motion guard .github/skills/skill-creator/eval-viewer/viewer.html:275 — `.grades-toggle .arrow` moves (`transition: transform 0.15s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.0 · ×1
  • Low contrast colour pair in CSS (3.0:1) .github/skills/skill-creator/eval-viewer/viewer.html:197 — `.output-file-content .download-link` sets color: #d97757 on background-color: #faf9f5 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.2 · ×1
  • Low contrast colour pair in CSS (3.2:1) .github/skills/skill-creator/eval-viewer/viewer.html:302 — `.grade-pass` sets color: #788c5d on background-color: #eef2e8 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.0 · ×1
  • Low contrast colour pair in CSS (4.0:1) .github/skills/skill-creator/eval-viewer/viewer.html:303 — `.grade-fail` sets color: #c44 on background-color: #fceaea — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.4 · ×1
  • Low contrast colour pair in CSS (4.4:1) MS.Microservice.Tasks/src/MS.Microservice.Tasks.Dashboard/Assets/dashboard.css:20 — `.nav-item.active` sets color: #635bdf on background-color: #eeedfc — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.8 · ×1
  • Low contrast colour pair in CSS (2.8:1) MS.Microservice.Tasks/src/MS.Microservice.Tasks.Dashboard/Assets/dashboard.css:74 — `th` sets color: #8c96aa on background-color: #f8f9fc — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung .github/skills/baoyu-url-to-markdown/scripts/package.json:5 — No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 4 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
AX2 · Stateful singletons · Process-global static state · ×1
  • Process-global static state: RedisCacheBenchmark benchmarks/MS.Microservice.Framework.Benchmarks/RedisCacheBenchmark.cs:10 — `RedisCacheBenchmark` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_checksum; e.g. `_checksum` at line 83). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
D1 · Cyclomatic Complexity · TableRecognizer.ValidateResult (cyclomatic 45) · ×1
  • TableRecognizer.ValidateResult (cyclomatic 45) MS.Microservice.Media/src/MS.Microservice.Media.Inference/Tables/TableRecognizer.cs:58 — TableRecognizer.ValidateResult has cyclomatic complexity 45 (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.
D1 · Cyclomatic Complexity · VideoWatermarkRemover.RemoveCoreAsync (cyclomatic 41) · ×1
  • VideoWatermarkRemover.RemoveCoreAsync (cyclomatic 41) MS.Microservice.Media/src/MS.Microservice.Media.Inference/VideoWatermarkRemoval/VideoWatermarkRemover.cs:39 — VideoWatermarkRemover.RemoveCoreAsync has cyclomatic complexity 41 (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.
D1 · Cyclomatic Complexity · PackageReader.StoryAsync (cyclomatic 39) · ×1
  • PackageReader.StoryAsync (cyclomatic 39) src/MS.Microservice.Documents/Word/WordTextExtractor.cs:159 — PackageReader.StoryAsync has cyclomatic complexity 39 (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.
D1 · Cyclomatic Complexity · top-level statements (cyclomatic 38) · ×1
  • top-level statements (cyclomatic 38) benchmarks/MS.Microservice.Search.Benchmarks/Program.cs:13 — top-level statements has cyclomatic complexity 38 (threshold 15). Of this number, 31 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.
D1 · Cyclomatic Complexity · top-level statements (cyclomatic 37) · ×1
  • top-level statements (cyclomatic 37) MS.Microservice.Persistence/benchmarks/MS.Microservice.Persistence.Auditing.Benchmarks/Program.cs:14 — top-level statements has cyclomatic complexity 37 (threshold 15). Of this number, 34 points are the body's own statements and 3 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.
D1 · Cyclomatic Complexity · RenderWorkerSupervisor.RunCoreAsync (cyclomatic 35) · ×1
  • RenderWorkerSupervisor.RunCoreAsync (cyclomatic 35) src/MS.Microservice.Documents.Rendering/RenderWorkerSupervisor.cs:20 — RenderWorkerSupervisor.RunCoreAsync has cyclomatic complexity 35 (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.
D1 · Cyclomatic Complexity · WordRenderPolicy.CheckFields (cyclomatic 34) · ×1
  • WordRenderPolicy.CheckFields (cyclomatic 34) src/MS.Microservice.Documents.Rendering/WordRenderPolicy.cs:53 — WordRenderPolicy.CheckFields has cyclomatic complexity 34 (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.
D1 · Cyclomatic Complexity · run_eval.run_single_query (cyclomatic 32) · ×1
  • run_eval.run_single_query (cyclomatic 32) .github/skills/skill-creator/scripts/run_eval.py:35 — run_eval.run_single_query has cyclomatic complexity 32 (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.
D1 · Cyclomatic Complexity · HtmlPdfRenderer.Snapshot (cyclomatic 29) · ×1
  • HtmlPdfRenderer.Snapshot (cyclomatic 29) src/MS.Microservice.Documents.Rendering/HtmlPdfRenderer.cs:37 — HtmlPdfRenderer.Snapshot has cyclomatic complexity 29 (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.
D1 · Cyclomatic Complexity · RedisCacheBenchmark.RunAsync (cyclomatic 28) · ×1
  • RedisCacheBenchmark.RunAsync (cyclomatic 28) benchmarks/MS.Microservice.Framework.Benchmarks/RedisCacheBenchmark.cs:18 — RedisCacheBenchmark.RunAsync has cyclomatic complexity 28 (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.
D1 · Cyclomatic Complexity · VideoProcessor.ConcatenateAsync (cyclomatic 28) · ×1
  • VideoProcessor.ConcatenateAsync (cyclomatic 28) MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Concatenation.cs:9 — VideoProcessor.ConcatenateAsync has cyclomatic complexity 28 (threshold 15). Of this number, 21 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · VideoProcessor.ParseMetadata (cyclomatic 28) · ×1
  • VideoProcessor.ParseMetadata (cyclomatic 28) MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.cs:41 — VideoProcessor.ParseMetadata has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · WordTemplateProcessor.Replace (cyclomatic 28) · ×1
  • WordTemplateProcessor.Replace (cyclomatic 28) src/MS.Microservice.Documents/Word/WordTemplateProcessor.cs:83 — WordTemplateProcessor.Replace has cyclomatic complexity 28 (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.
D1 · Cyclomatic Complexity · run_loop.run_loop (cyclomatic 28) · ×1
  • run_loop.run_loop (cyclomatic 28) .github/skills/skill-creator/scripts/run_loop.py:47 — run_loop.run_loop has cyclomatic complexity 28 (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.
D1 · Cyclomatic Complexity · WordTextExtractor.ExtractAsync (cyclomatic 27) · ×1
  • WordTextExtractor.ExtractAsync (cyclomatic 27) src/MS.Microservice.Documents/Word/WordTextExtractor.cs:19 — WordTextExtractor.ExtractAsync has cyclomatic complexity 27 (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.
D1 · Cyclomatic Complexity · CodeProcessor.GenerateAsync (cyclomatic 25) · ×1
  • CodeProcessor.GenerateAsync (cyclomatic 25) MS.Microservice.Media/src/MS.Microservice.Media/Codes/CodeProcessor.cs:14 — CodeProcessor.GenerateAsync has cyclomatic complexity 25 (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.
D1 · Cyclomatic Complexity · TextDiff.Compare (cyclomatic 25) · ×1
  • TextDiff.Compare (cyclomatic 25) src/MS.Microservice.Core/Text/TextDiff.cs:17 — TextDiff.Compare has cyclomatic complexity 25 (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.
D1 · Cyclomatic Complexity · CsvHelper.ReadAsync (cyclomatic 25) · ×1
  • CsvHelper.ReadAsync (cyclomatic 25) src/MS.Microservice.Excel/CsvHelper.cs:24 — CsvHelper.ReadAsync has cyclomatic complexity 25 (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.
D1 · Cyclomatic Complexity · ExcelHelper.TryConvertValue (cyclomatic 25) · ×1
  • ExcelHelper.TryConvertValue (cyclomatic 25) src/MS.Microservice.Excel/ExcelHelper.cs:961 — ExcelHelper.TryConvertValue has cyclomatic complexity 25 (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.
D1 · Cyclomatic Complexity · ProcessRunner.RunAsync (cyclomatic 25) · ×1
  • ProcessRunner.RunAsync (cyclomatic 25) src/MS.Microservice.Processes/ProcessRunner.cs:22 — ProcessRunner.RunAsync has cyclomatic complexity 25 (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.
D1 · Cyclomatic Complexity · AIRequestValidator.ValidateChatRequest (cyclomatic 24) · ×1
  • AIRequestValidator.ValidateChatRequest (cyclomatic 24) MS.Microservice.AI/src/MS.Microservice.AI.Core/AIRequestValidator.cs:7 — AIRequestValidator.ValidateChatRequest has cyclomatic complexity 24 (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.
D1 · Cyclomatic Complexity · ImageProcessor.ProcessAsync (cyclomatic 23) · ×1
  • ImageProcessor.ProcessAsync (cyclomatic 23) MS.Microservice.Media/src/MS.Microservice.Media/Images/ImageProcessor.cs:7 — ImageProcessor.ProcessAsync has cyclomatic complexity 23 (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.
D1 · Cyclomatic Complexity · AuditedDbContext.Prepare (cyclomatic 23) · ×1
  • AuditedDbContext.Prepare (cyclomatic 23) MS.Microservice.Persistence/src/MS.Microservice.Persistence.EFCore/Auditing/AuditedDbContext.cs:63 — AuditedDbContext.Prepare has cyclomatic complexity 23 (threshold 15). Of this number, 20 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.
D1 · Cyclomatic Complexity · improve_description.improve_description (cyclomatic 23) · ×1
  • improve_description.improve_description (cyclomatic 23) .github/skills/skill-creator/scripts/improve_description.py:50 — improve_description.improve_description 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.
D1 · Cyclomatic Complexity · quick_validate.validate_skill (cyclomatic 23) · ×1
  • quick_validate.validate_skill (cyclomatic 23) .github/skills/skill-creator/scripts/quick_validate.py:12 — quick_validate.validate_skill 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.
D1 · Cyclomatic Complexity · video_watermark_worker.audio_info (cyclomatic 23) · ×1
  • video_watermark_worker.audio_info (cyclomatic 23) MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/video_watermark_worker.py:52 — video_watermark_worker.audio_info 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.
D1 · Cyclomatic Complexity · TaskDashboardEndpoints.MapTaskDashboard (cyclomatic 22) · ×1
  • TaskDashboardEndpoints.MapTaskDashboard (cyclomatic 22) REDACTED:34 — TaskDashboardEndpoints.MapTaskDashboard has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 65, 54, 73, …). 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.
D1 · Cyclomatic Complexity · generate_report.generate_html (cyclomatic 22) · ×1
  • generate_report.generate_html (cyclomatic 22) .github/skills/skill-creator/scripts/generate_report.py:16 — generate_report.generate_html 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.
D1 · Cyclomatic Complexity · VideoWatermarkRemovalRequest.Snapshot (cyclomatic 21) · ×1
  • VideoWatermarkRemovalRequest.Snapshot (cyclomatic 21) MS.Microservice.Media/src/MS.Microservice.Media.Inference/VideoWatermarkRemoval/VideoWatermarkRemovalOptions.cs:102 — VideoWatermarkRemovalRequest.Snapshot 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.
D1 · Cyclomatic Complexity · ZipArchiveHelper.ExtractZipAsync (cyclomatic 21) · ×1
  • ZipArchiveHelper.ExtractZipAsync (cyclomatic 21) REDACTED:71 — ZipArchiveHelper.ExtractZipAsync 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.
D1 · Cyclomatic Complexity · SensitiveValues.Protect (cyclomatic 21) · ×1
  • SensitiveValues.Protect (cyclomatic 21) src/MS.Microservice.Core/Security/SensitiveData/SensitiveValues.cs:25 — SensitiveValues.Protect has cyclomatic complexity 21 (threshold 15). Of this number, 20 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.
D1 · Cyclomatic Complexity · HtmlRenderWorker.RunAsync (cyclomatic 21) · ×1
  • HtmlRenderWorker.RunAsync (cyclomatic 21) src/MS.Microservice.Documents.Rendering/HtmlRenderWorker.cs:12 — HtmlRenderWorker.RunAsync has cyclomatic complexity 21 (threshold 15). Of this number, 15 points are the body's own statements and 6 belong to 2 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.
D1 · Cyclomatic Complexity · aggregate_benchmark.load_run_results (cyclomatic 21) · ×1
  • aggregate_benchmark.load_run_results (cyclomatic 21) .github/skills/skill-creator/scripts/aggregate_benchmark.py:67 — aggregate_benchmark.load_run_results 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.
D1 · Cyclomatic Complexity · AIOptionsValidator.Validate (cyclomatic 20) · ×1
  • AIOptionsValidator.Validate (cyclomatic 20) MS.Microservice.AI/src/MS.Microservice.AI.Core/AIOptionsValidator.cs:7 — AIOptionsValidator.Validate has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · OcrProcessor.ValidateResult (cyclomatic 20) · ×1
  • OcrProcessor.ValidateResult (cyclomatic 20) MS.Microservice.Media/src/MS.Microservice.Media.Inference/Ocr/OcrProcessor.cs:86 — OcrProcessor.ValidateResult has cyclomatic complexity 20 (threshold 15). Of this number, 14 points are the body's own statements and 6 belong to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · VideoProcessor.ExtractAudioAsync (cyclomatic 20) · ×1
  • VideoProcessor.ExtractAudioAsync (cyclomatic 20) MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Assets.cs:57 — VideoProcessor.ExtractAudioAsync has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to one function literal inside it that branches. 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.
D1 · Cyclomatic Complexity · ImageBatchesController.Submit (cyclomatic 20) · ×1
  • ImageBatchesController.Submit (cyclomatic 20) samples/Lab/MS.Microservice.Lab/Controller/ImageBatchesController.cs:40 — ImageBatchesController.Submit has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · CsvHelper.WriteAsync (cyclomatic 20) · ×1
  • CsvHelper.WriteAsync (cyclomatic 20) src/MS.Microservice.Excel/CsvHelper.cs:153 — CsvHelper.WriteAsync has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · generate_review.build_run (cyclomatic 20) · ×1
  • generate_review.build_run (cyclomatic 20) .github/skills/skill-creator/eval-viewer/generate_review.py:85 — generate_review.build_run has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · QuestionGenerationHarness.RunAsync (cyclomatic 19) · ×1
  • QuestionGenerationHarness.RunAsync (cyclomatic 19) MS.Microservice.AI/src/MS.Microservice.AI.QuestionGeneration/Pipeline/QuestionGenerationHarness.cs:28 — QuestionGenerationHarness.RunAsync 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.
D1 · Cyclomatic Complexity · DocumentSearchIndex.Search (cyclomatic 19) · ×1
  • DocumentSearchIndex.Search (cyclomatic 19) src/MS.Microservice.Search/DocumentSearchIndex.Query.cs:18 — DocumentSearchIndex.Search 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.
D1 · Cyclomatic Complexity · OcrEngine.recognize (cyclomatic 19) · ×1
  • OcrEngine.recognize (cyclomatic 19) MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/ocr_pipeline.py:55 — OcrEngine.recognize 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.
D1 · Cyclomatic Complexity · ImageCodec.DecodeAsync (cyclomatic 18) · ×1
  • ImageCodec.DecodeAsync (cyclomatic 18) MS.Microservice.Media/src/MS.Microservice.Media/Images/ImageCodec.cs:7 — ImageCodec.DecodeAsync 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.
D1 · Cyclomatic Complexity · ImageWatermarker.TextStamp (cyclomatic 18) · ×1
  • ImageWatermarker.TextStamp (cyclomatic 18) MS.Microservice.Media/src/MS.Microservice.Media/Images/ImageWatermarker.cs:85 — ImageWatermarker.TextStamp 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.
D1 · Cyclomatic Complexity · VideoProcessor.ProbeAudioAssetAsync (cyclomatic 18) · ×1
  • VideoProcessor.ProbeAudioAssetAsync (cyclomatic 18) MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Assets.cs:109 — VideoProcessor.ProbeAudioAssetAsync has cyclomatic complexity 18 (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.
D1 · Cyclomatic Complexity · VideoProcessor.BuildFilters (cyclomatic 18) · ×1
  • VideoProcessor.BuildFilters (cyclomatic 18) MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Editing.cs:76 — VideoProcessor.BuildFilters has cyclomatic complexity 18 (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.
D1 · Cyclomatic Complexity · SelfManagedReceiver.ReceiveAsync (cyclomatic 18) · ×1
  • SelfManagedReceiver.ReceiveAsync (cyclomatic 18) MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/SelfManagedReceiver.cs:13 — SelfManagedReceiver.ReceiveAsync has cyclomatic complexity 18 (threshold 15). Of this number, 17 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.
D1 · Cyclomatic Complexity · JobExecutor.ExecuteAsync (cyclomatic 18) · ×1
  • JobExecutor.ExecuteAsync (cyclomatic 18) MS.Microservice.Tasks/src/MS.Microservice.Tasks/JobExecutor.cs:112 — JobExecutor.ExecuteAsync 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.
D1 · Cyclomatic Complexity · VisualPlanValidator.Validate (cyclomatic 18) · ×1
  • VisualPlanValidator.Validate (cyclomatic 18) samples/AI/MS.Microservice.Samples.EducationalImages/Pipeline/VisualPlanValidator.cs:13 — VisualPlanValidator.Validate 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.
D1 · Cyclomatic Complexity · SentenceImageBatchOrchestrator.GenerateBatchAsync (cyclomatic 18) · ×1
  • SentenceImageBatchOrchestrator.GenerateBatchAsync (cyclomatic 18) samples/AI/MS.Microservice.Samples.EducationalImages/SentenceImageBatchOrchestrator.cs:34 — SentenceImageBatchOrchestrator.GenerateBatchAsync 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.
D1 · Cyclomatic Complexity · WordTemplateProcessor.FillAsync (cyclomatic 18) · ×1
  • WordTemplateProcessor.FillAsync (cyclomatic 18) src/MS.Microservice.Documents/Word/WordTemplateProcessor.cs:14 — WordTemplateProcessor.FillAsync 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.
D1 · Cyclomatic Complexity · ExcelHelper.ReadRows (cyclomatic 18) · ×1
  • ExcelHelper.ReadRows (cyclomatic 18) src/MS.Microservice.Excel/ExcelHelper.cs:251 — ExcelHelper.ReadRows 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.
D1 · Cyclomatic Complexity · video_watermark_worker.prepare (cyclomatic 18) · ×1
  • video_watermark_worker.prepare (cyclomatic 18) MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/video_watermark_worker.py:196 — video_watermark_worker.prepare has cyclomatic complexity 18 (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.
D1 · Cyclomatic Complexity · video_watermark_worker.validate (cyclomatic 18) · ×1
  • video_watermark_worker.validate (cyclomatic 18) MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/video_watermark_worker.py:336 — video_watermark_worker.validate 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.
D1 · Cyclomatic Complexity · ImageWatermarker.Validate (cyclomatic 17) · ×1
  • ImageWatermarker.Validate (cyclomatic 17) MS.Microservice.Media/src/MS.Microservice.Media/Images/ImageWatermarker.cs:65 — ImageWatermarker.Validate 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.
D1 · Cyclomatic Complexity · VideoProcessor.WatermarkAsync (cyclomatic 17) · ×1
  • VideoProcessor.WatermarkAsync (cyclomatic 17) MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Watermarks.cs:28 — VideoProcessor.WatermarkAsync has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · InboxStore.AcquireAsync (cyclomatic 17) · ×1
  • InboxStore.AcquireAsync (cyclomatic 17) MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/InboxStore.cs:13 — InboxStore.AcquireAsync has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ReferenceHttpIdempotencyExecutor.ExecuteAsync (cyclomatic 17) · ×1
  • ReferenceHttpIdempotencyExecutor.ExecuteAsync (cyclomatic 17) samples/Reference/MS.Microservice.Reference.Web/HttpIdempotency/ReferenceHttpIdempotencyExecutor.cs:26 — ReferenceHttpIdempotencyExecutor.ExecuteAsync has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · AudioEditor.Edit (cyclomatic 17) · ×1
  • AudioEditor.Edit (cyclomatic 17) src/MS.Microservice.Audio/AudioEditor.cs:45 — AudioEditor.Edit 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.
D1 · Cyclomatic Complexity · ExcelHelper.TryConvertFromDouble (cyclomatic 17) · ×1
  • ExcelHelper.TryConvertFromDouble (cyclomatic 17) src/MS.Microservice.Excel/ExcelHelper.cs:891 — ExcelHelper.TryConvertFromDouble 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.
D1 · Cyclomatic Complexity · AliyunSmsSender.SendAsync (cyclomatic 17) · ×1
  • AliyunSmsSender.SendAsync (cyclomatic 17) src/MS.Microservice.Notifications/Sms/AliyunSmsSender.cs:43 — AliyunSmsSender.SendAsync 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.
D1 · Cyclomatic Complexity · ImageWatermarker.Draw (cyclomatic 16) · ×1
  • ImageWatermarker.Draw (cyclomatic 16) MS.Microservice.Media/src/MS.Microservice.Media/Images/ImageWatermarker.cs:164 — ImageWatermarker.Draw 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.
D1 · Cyclomatic Complexity · Program.RunAsync (cyclomatic 16) · ×1
  • Program.RunAsync (cyclomatic 16) samples/Reference/MS.Microservice.Reference.DatabaseMigrator/Program.cs:38 — Program.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.
D1 · Cyclomatic Complexity · EntityHelper.EntityEquals (cyclomatic 16) · ×1
  • EntityHelper.EntityEquals (cyclomatic 16) src/MS.Microservice.Core/Domain/Entity/EntityHelper.cs:10 — EntityHelper.EntityEquals 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.
D1 · Cyclomatic Complexity · SensitiveValues.BuildPlan (cyclomatic 16) · ×1
  • SensitiveValues.BuildPlan (cyclomatic 16) src/MS.Microservice.Core/Security/SensitiveData/SensitiveValues.cs:65 — SensitiveValues.BuildPlan has cyclomatic complexity 16 (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.
D1 · Cyclomatic Complexity · WordPackage.CheckAsync (cyclomatic 16) · ×1
  • WordPackage.CheckAsync (cyclomatic 16) src/MS.Microservice.Documents/Word/WordPackage.cs:35 — WordPackage.CheckAsync 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.
D1 · Cyclomatic Complexity · ExcelHelper.ImportCsvWithReportAsync (cyclomatic 16) · ×1
  • ExcelHelper.ImportCsvWithReportAsync (cyclomatic 16) src/MS.Microservice.Excel/ExcelHelper.Csv.cs:11 — ExcelHelper.ImportCsvWithReportAsync 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.
D1 · Cyclomatic Complexity · SmtpEmailSender.SendAsync (cyclomatic 16) · ×1
  • SmtpEmailSender.SendAsync (cyclomatic 16) REDACTED:30 — SmtpEmailSender.SendAsync has cyclomatic complexity 16 (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.
D1 · Cyclomatic Complexity · DocumentSearchIndex.BuildQuery (cyclomatic 16) · ×1
  • DocumentSearchIndex.BuildQuery (cyclomatic 16) src/MS.Microservice.Search/DocumentSearchIndex.Query.cs:87 — DocumentSearchIndex.BuildQuery 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.
D1 · Cyclomatic Complexity · DocumentSearchIndex.ValidateRequest (cyclomatic 16) · ×1
  • DocumentSearchIndex.ValidateRequest (cyclomatic 16) src/MS.Microservice.Search/DocumentSearchIndex.Query.cs:160 — DocumentSearchIndex.ValidateRequest has cyclomatic complexity 16 (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.
D17 · Explicit Debt · CommentedOutCode · ×1
  • CommentedOutCode samples/Lab/MS.Microservice.Lab/Controller/AccountController.cs:73 — 3 consecutive commented-code lines
D17 · Explicit Debt · BarePragmaDisable · ×1
  • BarePragmaDisable src/MS.Microservice.Domain.Primitives/IAuditor.cs:16 — #pragma warning disable CS0618 — 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.
D2 · Cognitive Complexity · run_eval.run_single_query (cognitive 79) · ×1
  • run_eval.run_single_query (cognitive 79) .github/skills/skill-creator/scripts/run_eval.py:35 — run_eval.run_single_query has cognitive complexity 79 (threshold 15). Drivers by points: if/else 20 (66 pts), loops 3 (7 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 52). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · top-level statements (cognitive 65) · ×1
  • top-level statements (cognitive 65) MS.Microservice.Persistence/benchmarks/MS.Microservice.Persistence.Auditing.Benchmarks/Program.cs:14 — top-level statements has cognitive complexity 65 (threshold 15). Of this number, 55 points are the body's own statements and 10 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.
D2 · Cognitive Complexity · PackageReader.StoryAsync (cognitive 60) · ×1
  • PackageReader.StoryAsync (cognitive 60) src/MS.Microservice.Documents/Word/WordTextExtractor.cs:159 — PackageReader.StoryAsync has cognitive complexity 60 (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.
D2 · Cognitive Complexity · aggregate_benchmark.load_run_results (cognitive 58) · ×1
  • aggregate_benchmark.load_run_results (cognitive 58) .github/skills/skill-creator/scripts/aggregate_benchmark.py:67 — aggregate_benchmark.load_run_results has cognitive complexity 58 (threshold 15). Drivers by points: if/else 11 (31 pts), error handling 4 (15 pts), loops 4 (10 pts), boolean chains 2 (nesting depth added 37). 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.
D2 · Cognitive Complexity · run_loop.run_loop (cognitive 55) · ×1
  • run_loop.run_loop (cognitive 55) .github/skills/skill-creator/scripts/run_loop.py:47 — run_loop.run_loop has cognitive complexity 55 (threshold 15). Drivers by points: if/else 23 (44 pts), ternaries 5 (9 pts), boolean chains 1, loops 1 (nesting depth added 25). 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.
D2 · Cognitive Complexity · CsvHelper.ReadAsync (cognitive 54) · ×1
  • CsvHelper.ReadAsync (cognitive 54) src/MS.Microservice.Excel/CsvHelper.cs:24 — CsvHelper.ReadAsync has cognitive complexity 54 (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.
D2 · Cognitive Complexity · top-level statements (cognitive 51) · ×1
  • top-level statements (cognitive 51) benchmarks/MS.Microservice.Search.Benchmarks/Program.cs:13 — top-level statements has cognitive complexity 51 (threshold 15). Of this number, 47 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · SentenceImageBatchOrchestrator.GenerateBatchAsync (cognitive 49) · ×1
  • SentenceImageBatchOrchestrator.GenerateBatchAsync (cognitive 49) samples/AI/MS.Microservice.Samples.EducationalImages/SentenceImageBatchOrchestrator.cs:34 — SentenceImageBatchOrchestrator.GenerateBatchAsync has cognitive complexity 49 (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.
D2 · Cognitive Complexity · video_watermark_worker.audio_info (cognitive 45) · ×1
  • video_watermark_worker.audio_info (cognitive 45) MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/video_watermark_worker.py:52 — video_watermark_worker.audio_info has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (32 pts), boolean chains 7, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 23). 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.
D2 · Cognitive Complexity · generate_review.build_run (cognitive 44) · ×1
  • generate_review.build_run (cognitive 44) .github/skills/skill-creator/eval-viewer/generate_review.py:85 — generate_review.build_run has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (27 pts), error handling 3 (10 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 25). 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.
D2 · Cognitive Complexity · WordRenderPolicy.CheckFields (cognitive 43) · ×1
  • WordRenderPolicy.CheckFields (cognitive 43) src/MS.Microservice.Documents.Rendering/WordRenderPolicy.cs:53 — WordRenderPolicy.CheckFields has cognitive complexity 43 (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.
D2 · Cognitive Complexity · CsvHelper.WriteAsync (cognitive 42) · ×1
  • CsvHelper.WriteAsync (cognitive 42) src/MS.Microservice.Excel/CsvHelper.cs:153 — CsvHelper.WriteAsync has cognitive complexity 42 (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.
D2 · Cognitive Complexity · improve_description.improve_description (cognitive 42) · ×1
  • improve_description.improve_description (cognitive 42) .github/skills/skill-creator/scripts/improve_description.py:50 — improve_description.improve_description has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 5 (14 pts), loops 4 (10 pts), boolean chains 3 (nesting depth added 19). 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.
D2 · Cognitive Complexity · RenderWorkerSupervisor.RunCoreAsync (cognitive 40) · ×1
  • RenderWorkerSupervisor.RunCoreAsync (cognitive 40) src/MS.Microservice.Documents.Rendering/RenderWorkerSupervisor.cs:20 — RenderWorkerSupervisor.RunCoreAsync has cognitive complexity 40 (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.
D2 · Cognitive Complexity · generate_report.generate_html (cognitive 40) · ×1
  • generate_report.generate_html (cognitive 40) .github/skills/skill-creator/scripts/generate_report.py:16 — generate_report.generate_html has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 11 (23 pts), loops 7 (12 pts), if/else 4 (5 pts) (nesting depth added 18). 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.
D2 · Cognitive Complexity · ProcessRunner.RunAsync (cognitive 39) · ×1
  • ProcessRunner.RunAsync (cognitive 39) src/MS.Microservice.Processes/ProcessRunner.cs:22 — ProcessRunner.RunAsync has cognitive complexity 39 (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.
D2 · Cognitive Complexity · InpaintingPixels.CreateKnownMask (cognitive 38) · ×1
  • InpaintingPixels.CreateKnownMask (cognitive 38) MS.Microservice.Media/src/MS.Microservice.Media.Inference/InpaintingPixels.cs:30 — InpaintingPixels.CreateKnownMask has cognitive complexity 38 (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.
D2 · Cognitive Complexity · TableRecognizer.ValidateResult (cognitive 38) · ×1
  • TableRecognizer.ValidateResult (cognitive 38) MS.Microservice.Media/src/MS.Microservice.Media.Inference/Tables/TableRecognizer.cs:58 — TableRecognizer.ValidateResult has cognitive complexity 38 (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.
D2 · Cognitive Complexity · WordTextExtractor.ExtractAsync (cognitive 37) · ×1
  • WordTextExtractor.ExtractAsync (cognitive 37) src/MS.Microservice.Documents/Word/WordTextExtractor.cs:19 — WordTextExtractor.ExtractAsync has cognitive complexity 37 (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.
D2 · Cognitive Complexity · QuestionGenerationHarness.RunAsync (cognitive 36) · ×1
  • QuestionGenerationHarness.RunAsync (cognitive 36) MS.Microservice.AI/src/MS.Microservice.AI.QuestionGeneration/Pipeline/QuestionGenerationHarness.cs:28 — QuestionGenerationHarness.RunAsync has cognitive complexity 36 (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.
D2 · Cognitive Complexity · ExcelHelper.ReadRows (cognitive 34) · ×1
  • ExcelHelper.ReadRows (cognitive 34) src/MS.Microservice.Excel/ExcelHelper.cs:251 — ExcelHelper.ReadRows 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.
D2 · Cognitive Complexity · RedisCacheBenchmark.RunAsync (cognitive 33) · ×1
  • RedisCacheBenchmark.RunAsync (cognitive 33) benchmarks/MS.Microservice.Framework.Benchmarks/RedisCacheBenchmark.cs:18 — RedisCacheBenchmark.RunAsync has cognitive complexity 33 (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.
D2 · Cognitive Complexity · TextDiff.Compare (cognitive 32) · ×1
  • TextDiff.Compare (cognitive 32) src/MS.Microservice.Core/Text/TextDiff.cs:17 — TextDiff.Compare 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.
D2 · Cognitive Complexity · AuditedDbContext.Changes (cognitive 30) · ×1
  • AuditedDbContext.Changes (cognitive 30) MS.Microservice.Persistence/src/MS.Microservice.Persistence.EFCore/Auditing/AuditedDbContext.cs:111 — AuditedDbContext.Changes 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.
D2 · Cognitive Complexity · ExcelHelper.ImportCsvWithReportAsync (cognitive 29) · ×1
  • ExcelHelper.ImportCsvWithReportAsync (cognitive 29) src/MS.Microservice.Excel/ExcelHelper.Csv.cs:11 — ExcelHelper.ImportCsvWithReportAsync has cognitive complexity 29 (threshold 15). Of this number, 28 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.
D2 · Cognitive Complexity · quick_validate.validate_skill (cognitive 29) · ×1
  • quick_validate.validate_skill (cognitive 29) .github/skills/skill-creator/scripts/quick_validate.py:12 — quick_validate.validate_skill has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 2, error handling 1 (nesting depth added 7). 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.
D2 · Cognitive Complexity · AIOptionsValidator.Validate (cognitive 28) · ×1
  • AIOptionsValidator.Validate (cognitive 28) MS.Microservice.AI/src/MS.Microservice.AI.Core/AIOptionsValidator.cs:7 — AIOptionsValidator.Validate 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.
D2 · Cognitive Complexity · VideoProcessor.ConcatenateAsync (cognitive 28) · ×1
  • VideoProcessor.ConcatenateAsync (cognitive 28) MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Concatenation.cs:9 — VideoProcessor.ConcatenateAsync has cognitive complexity 28 (threshold 15). Of this number, 22 points are the body's own statements and 6 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.
D2 · Cognitive Complexity · AudioEditor.Process (cognitive 28) · ×1
  • AudioEditor.Process (cognitive 28) src/MS.Microservice.Audio/AudioEditor.cs:126 — AudioEditor.Process 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.
D2 · Cognitive Complexity · ZipArchiveHelper.ExtractZipAsync (cognitive 28) · ×1
  • ZipArchiveHelper.ExtractZipAsync (cognitive 28) REDACTED:71 — ZipArchiveHelper.ExtractZipAsync 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.
D2 · Cognitive Complexity · WordTemplateProcessor.Replace (cognitive 28) · ×1
  • WordTemplateProcessor.Replace (cognitive 28) src/MS.Microservice.Documents/Word/WordTemplateProcessor.cs:83 — WordTemplateProcessor.Replace 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.
D2 · Cognitive Complexity · ExcelHelper.TryConvertValue (cognitive 28) · ×1
  • ExcelHelper.TryConvertValue (cognitive 28) src/MS.Microservice.Excel/ExcelHelper.cs:961 — ExcelHelper.TryConvertValue 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.
D2 · Cognitive Complexity · AuditedDbContext.Prepare (cognitive 27) · ×1
  • AuditedDbContext.Prepare (cognitive 27) MS.Microservice.Persistence/src/MS.Microservice.Persistence.EFCore/Auditing/AuditedDbContext.cs:63 — AuditedDbContext.Prepare has cognitive 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, 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.
D2 · Cognitive Complexity · OcrEngine.recognize (cognitive 27) · ×1
  • OcrEngine.recognize (cognitive 27) MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/ocr_pipeline.py:55 — OcrEngine.recognize has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 5, loops 2 (nesting depth added 9). 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.
D2 · Cognitive Complexity · AIRequestValidator.ValidateChatRequest (cognitive 25) · ×1
  • AIRequestValidator.ValidateChatRequest (cognitive 25) MS.Microservice.AI/src/MS.Microservice.AI.Core/AIRequestValidator.cs:7 — AIRequestValidator.ValidateChatRequest 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.
D2 · Cognitive Complexity · VideoProcessor.ParseMetadata (cognitive 25) · ×1
  • VideoProcessor.ParseMetadata (cognitive 25) MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.cs:41 — VideoProcessor.ParseMetadata has cognitive complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs 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.
D2 · Cognitive Complexity · JobExecutor.ExecuteAsync (cognitive 25) · ×1
  • JobExecutor.ExecuteAsync (cognitive 25) MS.Microservice.Tasks/src/MS.Microservice.Tasks/JobExecutor.cs:112 — JobExecutor.ExecuteAsync has cognitive complexity 25 (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.
D2 · Cognitive Complexity · DocumentSearchIndex.Search (cognitive 25) · ×1
  • DocumentSearchIndex.Search (cognitive 25) src/MS.Microservice.Search/DocumentSearchIndex.Query.cs:18 — DocumentSearchIndex.Search 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.
D2 · Cognitive Complexity · table_pipeline.grid_cells (cognitive 24) · ×1
  • table_pipeline.grid_cells (cognitive 24) MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/table_pipeline.py:32 — table_pipeline.grid_cells has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 6, loops 3 (6 pts) (nesting depth added 10). 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.
D2 · Cognitive Complexity · VisualPlanRepairer.Repair (cognitive 23) · ×1
  • VisualPlanRepairer.Repair (cognitive 23) samples/AI/MS.Microservice.Samples.EducationalImages/Pipeline/VisualPlanRepairer.cs:12 — VisualPlanRepairer.Repair 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.
D2 · Cognitive Complexity · VisualPlanValidator.Validate (cognitive 23) · ×1
  • VisualPlanValidator.Validate (cognitive 23) samples/AI/MS.Microservice.Samples.EducationalImages/Pipeline/VisualPlanValidator.cs:13 — VisualPlanValidator.Validate 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.
D2 · Cognitive Complexity · WordImagePromptPipeline.FindOuterHintStart (cognitive 23) · ×1
  • WordImagePromptPipeline.FindOuterHintStart (cognitive 23) samples/AI/MS.Microservice.Samples.EducationalImages/WordImagePromptPipeline.cs:166 — WordImagePromptPipeline.FindOuterHintStart 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.
D2 · Cognitive Complexity · WordPackage.CheckAsync (cognitive 23) · ×1
  • WordPackage.CheckAsync (cognitive 23) src/MS.Microservice.Documents/Word/WordPackage.cs:35 — WordPackage.CheckAsync 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.
D2 · Cognitive Complexity · DocumentSearchIndex.BuildQuery (cognitive 23) · ×1
  • DocumentSearchIndex.BuildQuery (cognitive 23) src/MS.Microservice.Search/DocumentSearchIndex.Query.cs:87 — DocumentSearchIndex.BuildQuery 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.
D2 · Cognitive Complexity · video_watermark_worker.validate (cognitive 23) · ×1
  • video_watermark_worker.validate (cognitive 23) MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/video_watermark_worker.py:336 — video_watermark_worker.validate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 6, loops 2 (nesting depth added 6). 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.
D2 · Cognitive Complexity · top-level statements (cognitive 22) · ×1
  • top-level statements (cognitive 22) benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:12 — top-level statements has cognitive complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · VideoWatermarkRemovalRequest.Snapshot (cognitive 22) · ×1
  • VideoWatermarkRemovalRequest.Snapshot (cognitive 22) MS.Microservice.Media/src/MS.Microservice.Media.Inference/VideoWatermarkRemoval/VideoWatermarkRemovalOptions.cs:102 — VideoWatermarkRemovalRequest.Snapshot 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.
D2 · Cognitive Complexity · SelfManagedReceiver.ReceiveAsync (cognitive 22) · ×1
  • SelfManagedReceiver.ReceiveAsync (cognitive 22) MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/SelfManagedReceiver.cs:13 — SelfManagedReceiver.ReceiveAsync has cognitive complexity 22 (threshold 15). Of this number, 21 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.
D2 · Cognitive Complexity · AuditedDbContext.BuildRules (cognitive 22) · ×1
  • AuditedDbContext.BuildRules (cognitive 22) MS.Microservice.Persistence/src/MS.Microservice.Persistence.EFCore/Auditing/AuditedDbContext.cs:161 — AuditedDbContext.BuildRules has cognitive complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to 2 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.
D2 · Cognitive Complexity · DocumentSearchIndex.ApplyBatch (cognitive 22) · ×1
  • DocumentSearchIndex.ApplyBatch (cognitive 22) src/MS.Microservice.Search/DocumentSearchIndex.cs:91 — DocumentSearchIndex.ApplyBatch 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.
D2 · Cognitive Complexity · Program.RunAsync (cognitive 21) · ×1
  • Program.RunAsync (cognitive 21) samples/Reference/MS.Microservice.Reference.DatabaseMigrator/Program.cs:38 — Program.RunAsync has cognitive complexity 21 (threshold 15). Of this number, 19 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.
D2 · Cognitive Complexity · EntityHelper.EntityEquals (cognitive 21) · ×1
  • EntityHelper.EntityEquals (cognitive 21) src/MS.Microservice.Core/Domain/Entity/EntityHelper.cs:10 — EntityHelper.EntityEquals 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.
D2 · Cognitive Complexity · HtmlRenderWorker.RunAsync (cognitive 21) · ×1
  • HtmlRenderWorker.RunAsync (cognitive 21) src/MS.Microservice.Documents.Rendering/HtmlRenderWorker.cs:12 — HtmlRenderWorker.RunAsync has cognitive complexity 21 (threshold 15). Of this number, 15 points are the body's own statements and 6 belong to 2 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.
D2 · Cognitive Complexity · WordTemplateProcessor.FillAsync (cognitive 21) · ×1
  • WordTemplateProcessor.FillAsync (cognitive 21) src/MS.Microservice.Documents/Word/WordTemplateProcessor.cs:14 — WordTemplateProcessor.FillAsync 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.
D2 · Cognitive Complexity · QwenImageEditProvider.ParseMultimodalResponseAsync (cognitive 20) · ×1
  • QwenImageEditProvider.ParseMultimodalResponseAsync (cognitive 20) MS.Microservice.AI/src/MS.Microservice.AI.Qwen/QwenImageEditProvider.cs:98 — QwenImageEditProvider.ParseMultimodalResponseAsync 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.
D2 · Cognitive Complexity · OrderReadModelProjector.ProjectBatchAsync (cognitive 20) · ×1
  • OrderReadModelProjector.ProjectBatchAsync (cognitive 20) samples/Lab/MS.Microservice.Lab.Infrastructure/EventSourcing/Orders/OrderReadModelProjector.cs:53 — OrderReadModelProjector.ProjectBatchAsync 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.
D2 · Cognitive Complexity · AliyunSmsSender.SendAsync (cognitive 20) · ×1
  • AliyunSmsSender.SendAsync (cognitive 20) src/MS.Microservice.Notifications/Sms/AliyunSmsSender.cs:43 — AliyunSmsSender.SendAsync 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.
D2 · Cognitive Complexity · dashboard.refresh (cognitive 20) · ×1
  • dashboard.refresh (cognitive 20) MS.Microservice.Tasks/src/MS.Microservice.Tasks.Dashboard/Assets/dashboard.js:140 — dashboard.refresh has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 4, error handling 1 (nesting depth added 5). 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.
D2 · Cognitive Complexity · AIProductionPipeline.ExecuteStreamAsync (cognitive 19) · ×1
  • AIProductionPipeline.ExecuteStreamAsync (cognitive 19) MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs:49 — AIProductionPipeline.ExecuteStreamAsync 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.
D2 · Cognitive Complexity · VideoWatermarkRemover.RemoveCoreAsync (cognitive 19) · ×1
  • VideoWatermarkRemover.RemoveCoreAsync (cognitive 19) MS.Microservice.Media/src/MS.Microservice.Media.Inference/VideoWatermarkRemoval/VideoWatermarkRemover.cs:39 — VideoWatermarkRemover.RemoveCoreAsync has cognitive complexity 19 (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.
D2 · Cognitive Complexity · CodeProcessor.GenerateAsync (cognitive 19) · ×1
  • CodeProcessor.GenerateAsync (cognitive 19) MS.Microservice.Media/src/MS.Microservice.Media/Codes/CodeProcessor.cs:14 — CodeProcessor.GenerateAsync has cognitive complexity 19 (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.
D2 · Cognitive Complexity · AudioEditor.Edit (cognitive 19) · ×1
  • AudioEditor.Edit (cognitive 19) src/MS.Microservice.Audio/AudioEditor.cs:45 — AudioEditor.Edit has cognitive complexity 19 (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.
D2 · Cognitive Complexity · SensitiveValues.Protect (cognitive 19) · ×1
  • SensitiveValues.Protect (cognitive 19) src/MS.Microservice.Core/Security/SensitiveData/SensitiveValues.cs:25 — SensitiveValues.Protect has cognitive 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, 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.
D2 · Cognitive Complexity · table_pipeline.detect_tables (cognitive 19) · ×1
  • table_pipeline.detect_tables (cognitive 19) MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/table_pipeline.py:81 — table_pipeline.detect_tables has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 5, loops 1 (nesting depth added 6). 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.
D2 · Cognitive Complexity · video_watermark_worker.prepare (cognitive 19) · ×1
  • video_watermark_worker.prepare (cognitive 19) MS.Microservice.Media/src/MS.Microservice.Media.Inference/worker/video_watermark_worker.py:196 — video_watermark_worker.prepare has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9, boolean chains 4, loops 3 (4 pts), ternaries 2 (nesting depth added 1). 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.
D2 · Cognitive Complexity · OpenAICompatibleChatProviderBase.ParseStreamAsync (cognitive 18) · ×1
  • OpenAICompatibleChatProviderBase.ParseStreamAsync (cognitive 18) MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleChatProviderBase.cs:301 — OpenAICompatibleChatProviderBase.ParseStreamAsync 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.
D2 · Cognitive Complexity · ImageWatermarker.TextStamp (cognitive 18) · ×1
  • ImageWatermarker.TextStamp (cognitive 18) MS.Microservice.Media/src/MS.Microservice.Media/Images/ImageWatermarker.cs:85 — ImageWatermarker.TextStamp 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.
D2 · Cognitive Complexity · TaskDashboardEndpoints.MapTaskDashboard (cognitive 18) · ×1
  • TaskDashboardEndpoints.MapTaskDashboard (cognitive 18) REDACTED:34 — TaskDashboardEndpoints.MapTaskDashboard has cognitive complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 65, 54, 73, …). 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.
D2 · Cognitive Complexity · JobExecutor.TickAsync (cognitive 18) · ×1
  • JobExecutor.TickAsync (cognitive 18) MS.Microservice.Tasks/src/MS.Microservice.Tasks/JobExecutor.cs:66 — JobExecutor.TickAsync 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.
D2 · Cognitive Complexity · VisualPlanEnricher.Enrich (cognitive 18) · ×1
  • VisualPlanEnricher.Enrich (cognitive 18) samples/AI/MS.Microservice.Samples.EducationalImages/Pipeline/VisualPlanEnricher.cs:13 — VisualPlanEnricher.Enrich 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.
D2 · Cognitive Complexity · ReferenceHttpIdempotencyExecutor.ExecuteAsync (cognitive 18) · ×1
  • ReferenceHttpIdempotencyExecutor.ExecuteAsync (cognitive 18) samples/Reference/MS.Microservice.Reference.Web/HttpIdempotency/ReferenceHttpIdempotencyExecutor.cs:26 — ReferenceHttpIdempotencyExecutor.ExecuteAsync has cognitive complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs 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.
D2 · Cognitive Complexity · FileHashHelper.FindDuplicatesAsync (cognitive 18) · ×1
  • FileHashHelper.FindDuplicatesAsync (cognitive 18) src/MS.Microservice.Core/IO/FileHashHelper.cs:46 — FileHashHelper.FindDuplicatesAsync 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.
D2 · Cognitive Complexity · SecretField.HideSensitiveInfo (cognitive 18) · ×1
  • SecretField.HideSensitiveInfo (cognitive 18) src/MS.Microservice.Core/Security/SecretField.cs:50 — SecretField.HideSensitiveInfo 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.
D2 · Cognitive Complexity · ExcelHelper.ValidateReportColumns (cognitive 18) · ×1
  • ExcelHelper.ValidateReportColumns (cognitive 18) src/MS.Microservice.Excel/ExcelHelper.cs:664 — ExcelHelper.ValidateReportColumns 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.
D2 · Cognitive Complexity · utils.parse_skill_md (cognitive 18) · ×1
  • utils.parse_skill_md (cognitive 18) .github/skills/skill-creator/scripts/utils.py:7 — utils.parse_skill_md has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 7). 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.
D2 · Cognitive Complexity · InboxStore.AcquireAsync (cognitive 17) · ×1
  • InboxStore.AcquireAsync (cognitive 17) MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/InboxStore.cs:13 — InboxStore.AcquireAsync has cognitive complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · PdfProcessor.Save (cognitive 17) · ×1
  • PdfProcessor.Save (cognitive 17) REDACTED:94 — PdfProcessor.Save 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.
D2 · Cognitive Complexity · ExcelHelper.TryConvertFromDouble (cognitive 17) · ×1
  • ExcelHelper.TryConvertFromDouble (cognitive 17) src/MS.Microservice.Excel/ExcelHelper.cs:891 — ExcelHelper.TryConvertFromDouble has cognitive complexity 17 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · AuditCaptureBenchmark.Run (cognitive 16) · ×1
  • AuditCaptureBenchmark.Run (cognitive 16) benchmarks/MS.Microservice.Framework.Benchmarks/AuditCaptureBenchmark.cs:10 — AuditCaptureBenchmark.Run 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.
D2 · Cognitive Complexity · ImageWatermarker.Draw (cognitive 16) · ×1
  • ImageWatermarker.Draw (cognitive 16) MS.Microservice.Media/src/MS.Microservice.Media/Images/ImageWatermarker.cs:164 — ImageWatermarker.Draw 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.
D2 · Cognitive Complexity · QwenSafePromptBuilder.BuildEventCard (cognitive 16) · ×1
  • QwenSafePromptBuilder.BuildEventCard (cognitive 16) samples/AI/MS.Microservice.Samples.EducationalImages/Building/QwenSafePromptBuilder.cs:180 — QwenSafePromptBuilder.BuildEventCard has cognitive complexity 16 (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.
D2 · Cognitive Complexity · HtmlRenderWorker.PrintAsync (cognitive 16) · ×1
  • HtmlRenderWorker.PrintAsync (cognitive 16) src/MS.Microservice.Documents.Rendering/HtmlRenderWorker.cs:100 — HtmlRenderWorker.PrintAsync 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.
D2 · Cognitive Complexity · ExcelHelper.TryReadNonFormulaCellValue (cognitive 16) · ×1
  • ExcelHelper.TryReadNonFormulaCellValue (cognitive 16) src/MS.Microservice.Excel/ExcelHelper.cs:781 — ExcelHelper.TryReadNonFormulaCellValue has cognitive complexity 16 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: MS.Microservice.Excel/ExcelHelper.cs src/MS.Microservice.Excel/ExcelHelper.cs — FileTooLong — 679 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 179 over it, 1.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) MS.Microservice.AI/src/MS.Microservice.AI.Abstractions/AIImageEditRequest.cs:17 — MS.Microservice.AI/src/MS.Microservice.AI.Abstractions/AIImageEditRequest.cs:17-45 | MS.Microservice.AI/src/MS.Microservice.AI.Abstractions/AIImageGenerationRequest.cs:11-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) MS.Microservice.AI/src/MS.Microservice.AI.Qwen/QwenImageReferenceEditRequest.cs:9 — MS.Microservice.AI/src/MS.Microservice.AI.Qwen/QwenImageReferenceEditRequest.cs:9-34 | samples/AI/MS.Microservice.Samples.EducationalImages/Models/ReferenceImageEditRequest.cs:10-35 — 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.
D4 · Code Duplication · Duplicated block (25 lines × 3) · ×1
  • Duplicated block (25 lines × 3) MS.Microservice.AI/src/MS.Microservice.AI.Abstractions/AIImageEditRequest.cs:18 — MS.Microservice.AI/src/MS.Microservice.AI.Abstractions/AIImageEditRequest.cs:18-42 | MS.Microservice.AI/src/MS.Microservice.AI.Abstractions/AIImageGenerationRequest.cs:12-36 | samples/AI/MS.Microservice.Samples.EducationalImages/Models/ImageGenerationResultTypes.cs:12-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleChatProviderBase.cs:34 — MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleChatProviderBase.cs:34-51 | MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleMediaProviderBase.cs:33-50 — 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.
D4 · Code Duplication · Duplicated block (16–18 lines × 2) · ×1
  • Duplicated block (16–18 lines × 2) MS.Microservice.Media/src/MS.Microservice.Media.Inference/BackgroundRemoval/BiRefNetBackgroundRemover.cs:26 — MS.Microservice.Media/src/MS.Microservice.Media.Inference/BackgroundRemoval/BiRefNetBackgroundRemover.cs:26-41 | MS.Microservice.Media/src/MS.Microservice.Media.Inference/SuperResolution/Swin2SrUpscaler.cs:26-43 — before extracting anything, compare `MS.Microservice.Media/src/MS.Microservice.Media.Inference/BackgroundRemoval/BiRefNetBackgroundRemover.cs` and `MS.Microservice.Media/src/MS.Microservice.Media.Inference/SuperResolution/Swin2SrUpscaler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `MS.Microservice.Media/src/MS.Microservice.Media.Inference/BackgroundRemoval/BiRefNetBackgroundRemover.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `options` to `BiRefNetBackgroundRemovalOptions` in one and `Swin2SrOptions` 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.
D4 · Code Duplication · Duplicated block (12–16 lines × 2) · ×1
  • Duplicated block (12–16 lines × 2) MS.Microservice.Media/src/MS.Microservice.Media.Inference/BackgroundRemoval/BiRefNetBackgroundRemover.cs:55 — MS.Microservice.Media/src/MS.Microservice.Media.Inference/BackgroundRemoval/BiRefNetBackgroundRemover.cs:55-66 | MS.Microservice.Media/src/MS.Microservice.Media.Inference/SuperResolution/Swin2SrUpscaler.cs:75-90 — before extracting anything, compare `MS.Microservice.Media/src/MS.Microservice.Media.Inference/BackgroundRemoval/BiRefNetBackgroundRemover.cs` and `MS.Microservice.Media/src/MS.Microservice.Media.Inference/SuperResolution/Swin2SrUpscaler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `MS.Microservice.Media/src/MS.Microservice.Media.Inference/BackgroundRemoval/BiRefNetBackgroundRemover.cs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleImageGenerationProviderBase.cs:61 — MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleImageGenerationProviderBase.cs:61-84 | MS.Microservice.AI/src/MS.Microservice.AI.Qwen/QwenImageEditProvider.cs:104-118 — 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 `MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleImageGenerationProviderBase.cs:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/MessagingModelBuilderExtensions.cs:14 — MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/MessagingModelBuilderExtensions.cs:14-26 | MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/MessagingModelBuilderExtensions.cs:33-44 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Editing.cs:11 — MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Editing.cs:11-21 | src/MS.Microservice.Audio/AudioEditor.cs:22-30 — 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 `MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Editing.cs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) src/MS.Microservice.Documents.Rendering/WordPdfConverter.cs:50 — src/MS.Microservice.Documents.Rendering/WordPdfConverter.cs:50-54 | REDACTED:85-89 | src/MS.Microservice.Documents/Word/WordTextExtractor.cs:102-106 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:90` calls `ThrowIfCancellationRequested` and `src/MS.Microservice.Documents.Rendering/WordPdfConverter.cs:55` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) .github/skills/mcp-builder/scripts/evaluation.py:276 — .github/skills/mcp-builder/scripts/evaluation.py:276-287 | .github/skills/mcp-builder/scripts/evaluation.py:291-302 — 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) samples/AI/MS.Microservice.Samples.EducationalImages/SentenceImageBatchOrchestrator.cs:158 — samples/AI/MS.Microservice.Samples.EducationalImages/SentenceImageBatchOrchestrator.cs:158-179 | samples/AI/MS.Microservice.Samples.EducationalImages/SentenceImageBatchOrchestrator.cs:193-214 — 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 `samples/AI/MS.Microservice.Samples.EducationalImages/SentenceImageBatchOrchestrator.cs:158` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) samples/Lab/MS.Microservice.Lab/Application/Tools/ImageToolForms.cs:15 — samples/Lab/MS.Microservice.Lab/Application/Tools/ImageToolForms.cs:15-33 | samples/Lab/MS.Microservice.Lab/Application/Tools/VideoToolForms.cs:25-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) samples/AI/MS.Microservice.Samples.EducationalImages/Models/WordImagePromptPlan.cs:17 — samples/AI/MS.Microservice.Samples.EducationalImages/Models/WordImagePromptPlan.cs:17-29 | samples/AI/MS.Microservice.Samples.EducationalImages/Models/WordImageVisualPlan.cs:15-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (9–11 lines × 2) · ×1
  • Duplicated block (9–11 lines × 2) samples/Lab/MS.Microservice.Lab/Application/Demo/ChangePasswordAppService.cs:52 — samples/Lab/MS.Microservice.Lab/Application/Demo/ChangePasswordAppService.cs:52-62 | samples/Lab/MS.Microservice.Lab/Application/Demo/RegisterAccountAppService.cs:57-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `ChangePasswordCommand` in one and `RegisterAccountCommand` 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: UserController (LCOM4 4) REDACTED:16 — UserController's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
GD1 · Unfinished & placeholder code · Unfinished stub · ×1
  • Unfinished stub — throws NotImplementedException samples/Lab/MS.Microservice.Lab/Infrastructure/ActivationDbContextSeed.cs:30 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Guard cannot change the result · ×1
  • Guard cannot change the result — returns what the code already falls through to src/MS.Microservice.Audio/AudioFileFormatDetector.cs:70 — 2 guards above `return AudioFormat.Auto;` also return `AudioFormat.Auto`, so no input can make them matter. Implement the distinction that was intended, or delete the guards.
S1 · Web-Security Posture · Weak hash algorithm · ×1
  • Weak hash algorithm src/MS.Microservice.Core/Security/Summary/Md5.cs:13 — MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses.
X18 · Disposal-pattern correctness · Disposes a dependency it does not own · ×1
  • Disposes a dependency it does not own MS.Microservice.Media/src/MS.Microservice.Media.Inference/MiganInpainter.cs:101 — `_session` is a `InferenceSession` that `MiganInpainter` never creates — every assignment to it takes a constructor parameter — and this type disposes it here (line 101). The caller that hands it over at `new MiganInpainter(session, options.Limits)` (MiganInpainter.cs line 38) releases the same value itself, so it kept ownership: this release is a second one, on a value that is still the caller's, and it ends the caller's instance while the caller may still be using it. Drop the call and leave the release to the caller that created the value — or, if this type is meant to own it, stop releasing it at the construction site so ownership is stated once.
X25 · Inert configuration knob · Numbers written to standard output under the host's culture · ×1
  • Numbers written to standard output under the host's culture benchmarks/MS.Microservice.Search.Benchmarks/Program.cs:60 — `benchmarks/MS.Microservice.Search.Benchmarks/Program.cs` is this program's entry point and formats with `CultureInfo.InvariantCulture` on line 163 — `id.ToString("D8", CultureInfo.InvariantCulture)` — yet writes 3 number(s) to standard output through a culture-sensitive format specifier with no format provider: `{id + 1:N0}` on line 60. Nothing in the project sets `CultureInfo.CurrentCulture` or `DefaultThreadCurrentCulture`, or turns on invariant globalization, so these numbers are spelled by whatever locale the host runs under: `70.3` on an en-US machine is `70,3` on a da-DK one, and a script or CI step that parses this output reads a different value, or fails, depending on where it ran. Set the culture once at the top of the entry point (`CultureInfo.CurrentCulture = CultureInfo.InvariantCulture;`) — or, if this output is meant for people in their own locale, pass `CultureInfo.CurrentCulture` explicitly so the omission stops reading as an oversight.
Minor — 72 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×8
  • Duplicated predicate src/MS.Microservice.Core/Reflection/ExpressionPropertyAccessorStrategy.cs:28 — `!property.CanRead || property.GetMethod?.IsPublic != true` appears character-identically in 3 files — src/MS.Microservice.Core/Reflection/ExpressionPropertyAccessorStrategy.cs, src/MS.Microservice.Core/Reflection/IlPropertyAccessorStrategy.cs, src/MS.Microservice.Core/Reflection/PropertyAccessorStrategy.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 MS.Microservice.Media/src/MS.Microservice.Media.Inference/VideoWatermarkRemoval/VideoWatermarkRemover.cs:52 — `File.Exists(output) || Directory.Exists(output)` appears character-identically in 3 files — MS.Microservice.Media/src/MS.Microservice.Media.Inference/VideoWatermarkRemoval/VideoWatermarkRemover.cs, MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Assets.cs, MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Editing.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 samples/Lab/MS.Microservice.Lab/Application/Tools/AuditDemo.cs:62 — `directory.Equals(webRoot, comparison) || directory.StartsWith(webRoot + Path.DirectorySeparatorChar, comparison)` appears character-identically in 3 files — samples/Lab/MS.Microservice.Lab/Application/Tools/AuditDemo.cs, samples/Lab/MS.Microservice.Lab/Application/Tools/SensitiveDataDemo.cs, samples/Lab/MS.Microservice.Lab/Application/Tools/TaskCenterDemo.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 MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Editing.cs:28 — `info.Duration is { } length && options.Start >= length` appears character-identically in 2 files — MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Editing.cs, MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Watermarks.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 MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/InboxStore.cs:100 — `permanent || attempts > options.MaxRetryAttempts` appears character-identically in 2 files — MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/InboxStore.cs, MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/OutboxStore.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 MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Assets.cs:129 — `seconds is < 0 || seconds > TimeSpan.MaxValue.TotalSeconds` appears character-identically in 2 files — MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.Assets.cs, MS.Microservice.Media/src/MS.Microservice.Media/Video/VideoProcessor.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/MS.Microservice.Core/Text/TextDiff.cs:125 — `text[index] == '\r' && index + 1 < text.Length && text[index + 1] == '\n'` appears character-identically in 2 files — src/MS.Microservice.Core/Text/TextDiff.cs, src/MS.Microservice.Documents/Word/WordTemplateProcessor.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 MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/InboxStore.cs:69 — `x.MessageId == id && x.Consumer == consumer` appears character-identically in 2 files — MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/InboxStore.cs, MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/SelfManagedFailedMessageOperations.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.
X7 · Silent fallback defaults · Silent fallback default on configuration miss · ×7
  • Silent fallback default on configuration miss samples/Lab/MS.Microservice.Lab/Application/Identity/Token/LabTokenIssuerOptions.cs:27 — `ValidationOptions` reads `configuration.GetSection(SectionName).Get<LabTokenIssuerOptions>()` — a missing or misspelt key silently becomes `new()`, with no log or throw. Validate the options at startup (or log the miss); if that value is the specified default, document it on the member and the row stops firing.
  • Silent fallback default on configuration miss samples/Lab/MS.Microservice.Lab/Hosting/LabMessaging.cs:66 — `Map` reads `app.Configuration.GetValue("LabMessaging:Enabled", false)` — a missing or misspelt key silently becomes `false`, with no log or throw. Validate the options at startup (or log the miss); if that constant is the specified default, document it on the member and the row stops firing.
  • Silent fallback default on configuration miss samples/Lab/MS.Microservice.Lab/Infrastructure/Extensions/IServiceCollectionExtensions.cs:95 — `AddCorsService` reads `section.Get<CorsOptions>()` — a missing or misspelt key silently becomes `new CorsOptions()`, with no log or throw. Validate the options at startup (or log the miss); if that value is the specified default, document it on the member and the row stops firing.
  • Silent fallback default on configuration miss samples/Lab/MS.Microservice.Lab/Infrastructure/Extensions/IServiceCollectionExtensions.cs:129 — `AddHealthChecks` reads `configuration.GetConnectionString("ActivationConnection")` — a missing or misspelt key silently becomes `string.Empty`, with no log or throw. Validate the options at startup (or log the miss); if that value is the specified default, document it on the member and the row stops firing.
  • Silent fallback default on configuration miss src/MS.Microservice.AspNetCore/ExternalIdentity.Compatibility.cs:13 — `AddExternalIdentity` reads `configuration.GetSection("Authentication").Get<ExternalIdentityOptions>()` — a missing or misspelt key silently becomes `new()`, with no log or throw. Validate the options at startup (or log the miss); if that value is the specified default, document it on the member and the row stops firing.
  • Silent fallback default on configuration miss src/MS.Microservice.AspNetCore/ServiceHost.cs:41 — `AddPlatformHttp` reads `configuration.GetSection("Http:KnownProxies").Get<string[]>()` — a missing or misspelt key silently becomes `[]`, with no log or throw. Validate the options at startup (or log the miss); if that value is the specified default, document it on the member and the row stops firing.
  • Silent fallback default on configuration miss src/MS.Microservice.Observability/OpenTelemetryExtensions.cs:20 — `AddMsOpenTelemetry` reads `section.Get<TelemetryResourceOptions>()` — a missing or misspelt key silently becomes `new TelemetryResourceOptions()`, with no log or throw. Validate the options at startup (or log the miss); if that value is the specified default, document it on the member and the row stops firing.
X7 · Silent fallback defaults · Silent fallback default in catch · ×6
  • Silent fallback default in catch MS.Microservice.Messaging/src/MS.Microservice.Messaging.Abstractions/MessageMetadataLimits.cs:28 — `AreValid` swallows `EncoderFallbackException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch MS.Microservice.Messaging/src/MS.Microservice.Messaging.Abstractions/MessageRoutingKey.cs:23 — `IsValid` swallows `EncoderFallbackException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch samples/Lab/MS.Microservice.Lab.Infrastructure/FileSystem/NetworkShareAccessor.cs:184 — `IsShareAlreadyAccessible` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch samples/Lab/MS.Microservice.Lab/Application/Identity/UserPasswordService.cs:74 — `VerifyModernPassword` swallows `FormatException` into `return PasswordVerificationResult.Failed;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/MS.Microservice.Audio/AudioProcessorExtensions.cs:182 — `ValidateAudioFile` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch REDACTED:265 — `Exists` swallows `FileNotFoundException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
D34 · Knowledge Freshness · Orphaned file · ×5
  • Orphaned file MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.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 MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.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/MS.Microservice.Core/Functional/Either.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 MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/SqlSugarQueryableExtensions.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 MS.Microservice.Persistence/src/MS.Microservice.Persistence.EFCore/DbContext/EFCoreQueryableExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
X7 · Silent fallback defaults · Silent fallback default on unknown code · ×5
  • Silent fallback default on unknown code samples/AI/MS.Microservice.Samples.EducationalImages/Models/VisualContextGroup.cs:70 — `ParseReuseMode` maps every unrecognised code to `ImageReuseMode.GenerateAll`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
  • Silent fallback default on unknown code samples/Lab/MS.Microservice.Lab/Infrastructure/Http/ApiProblemDetails.cs:39 — `FromError` maps every unrecognised code to `StatusCodes.Status500InternalServerError`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
  • Silent fallback default on unknown code src/MS.Microservice.AspNetCore/ApplicationErrorResults.cs:19 — `ToProblem` maps every unrecognised code to `StatusCodes.Status500InternalServerError`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
  • Silent fallback default on unknown code src/MS.Microservice.Audio/AudioFileFormatDetector.cs:151 — `GetFormatFromExtension` maps every unrecognised code to `AudioFormat.Auto`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
  • Silent fallback default on unknown code src/MS.Microservice.Audio/AudioProcessor.cs:585 — `GetInputFormat` maps every unrecognised code to `AudioFormat.Auto`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
D19 · Documentation Quality · Documentation · ×3
  • Documentation: no build, run or usage example MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/README.md:1 — `MS.Microservice.Messaging.RabbitMQ` is a package (`IsPackable true`) and neither `MS.Microservice.Messaging/src/MS.Microservice.Messaging.RabbitMQ/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/README.md:1 — `MS.Microservice.Messaging.SelfManaged.EFCore` is a package (`IsPackable true`) and neither `MS.Microservice.Messaging/src/MS.Microservice.Messaging.SelfManaged.EFCore/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example MS.Microservice.Messaging/src/MS.Microservice.Messaging.Wolverine/README.md:1 — `MS.Microservice.Messaging.Wolverine` is a package (`IsPackable true`) and neither `MS.Microservice.Messaging/src/MS.Microservice.Messaging.Wolverine/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D24 · Comment Value · redundant comment · ×3
  • redundant comment MS.Microservice.AI/src/MS.Microservice.AI.Qwen/QwenImageEditProvider.cs:25 — "── Qwen multimodal reference-image edit ──" repeats the code it sits on: 4 of its 5 words (qwen, reference, image, edit) are already in `public async ValueTask<AIImageResponse> EditReferenceAsync(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment MS.Microservice.AI/src/MS.Microservice.AI.Qwen/QwenImageReferenceEditClient.cs:32 — "Resolve model via the standard AI model resolver" repeats the code it sits on: 4 of its 5 words (resolve, model, ai, resolver) are already in `var resolvedModel = modelResolver.ResolveImageEditModel(new AIImageEditRequest`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/MS.Microservice.Excel/ExcelHelper.cs:774 — "Non-formula cells: read directly from cell" repeats the code it sits on: 5 of its 6 words (non, formula, cells, read, cell) are already in `return TryReadNonFormulaCellValue(cell, cellType, targetTypeCode, targetType, out value);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
AX6 · Interface segregation · Fat interface · ×2
  • Fat interface: IRepositoryBase<T> (22 members) MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/IRepositoryBase.cs:12 — `IRepositoryBase<T>` declares 22 members under just 13 distinct name(s): `AnyAsync`, `AddAsync`, `AddAReturnIdsync`, `AddReturnEntitysync`, `AddListAsync`, `GetModelAsync`, `GetPagesAsync`, `GetListAsync`, `GetListAsync`, `GetListAsync`, `UpdateAsync`, `UpdateAsync`, `UpdateAsync`, `DeleteAsync`, `DeleteAsync`, `DeleteAsync`, `FirstOrDefaultAsync`, `FirstOrDefaultAsync`, `ListAsync`, `ListAsync`, `CountAsync`, `AnyAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 22 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 22 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: IJobStore (16 members) MS.Microservice.Tasks/src/MS.Microservice.Tasks/JobContracts.cs:26 — `IJobStore` declares 16 members: `SubmitAsync`, `StageAsync`, `GetAsync`, `ListAsync`, `GetAttemptsAsync`, `GetDueAsync`, `GetRunningExecutionsAsync`, `GetExecutionStatusAsync`, `TryStartAsync`, `ReportProgressAsync`, `CompleteAsync`, `FailAsync`, `InterruptAsync`, `RecoverAsync`, `CancelAsync`, `RetryAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D12 · Dependency Hygiene · Outdated · ×2
  • Outdated: coverlet.collector Directory.Packages.props:9 — coverlet.collector 6.0.4 → 10.1.0 available (referenced by MS.Microservice.AI.Core.Tests).
  • Outdated: Autofac.Extensions.DependencyInjection Directory.Packages.props:8 — Autofac.Extensions.DependencyInjection 8.0.0 → 11.0.2 available (referenced by MS.Microservice.Lab).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×2
  • Projects may be oversized for their cohesion src/MS.Microservice.Core/MS.Microservice.Core.csproj:1 — `MS.Microservice.Core` overshoots its size bounds (6852 LoC, 210 public types across 42 namespaces). 2 of 116 project(s) overshoot their size bounds, lowering Project Cohesion to 9.7/10. Review these for cohesion — split a project that spans unrelated responsibilities.
  • Projects may be oversized for their cohesion samples/Lab/MS.Microservice.Lab/MS.Microservice.Lab.csproj:1 — `MS.Microservice.Lab` overshoots its size bounds (7843 LoC, 225 public types across 40 namespaces). 2 of 116 project(s) overshoot their size bounds, lowering Project Cohesion to 9.7/10. Review these for cohesion — split a project that spans unrelated responsibilities.
ED3 · Event naming · Event not named in past tense · ×2
  • Event not named in past tense: IntegrationEvent src/MS.Microservice.Core/Messaging/EventContracts.cs:31 — `IntegrationEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
  • Event not named in past tense: IntegrationEvent src/MS.Microservice.EventBus/Events/IntegrationEvent.cs:7 — `IntegrationEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
IC1 · Incompleteness & stubs · Commented-out code · ×2
  • Commented-out code src/MS.Microservice.Core/Common/NumberConverter.cs:33 — 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 REDACTED:279 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 53 significant file(s) lose their only recent owner: src/MS.Microservice.Excel/ExcelHelper.cs, src/MS.Microservice.Audio/AudioProcessor.cs, MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleChatProviderBase.cs, MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionServices.cs, MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleMediaProviderBase.cs, MS.Microservice.AI/src/MS.Microservice.AI.Core/AIRequestValidator.cs, src/MS.Microservice.Core/Reflection/IlPropertyAccessorStrategy.cs, MS.Microservice.AI/src/MS.Microservice.AI.Core/AIOptions.cs (+45 more). Pair on, review, or document these before any departure.
D17 · Explicit Debt · ObsoleteWithoutCallers · ×1
  • ObsoleteWithoutCallers samples/Lab/MS.Microservice.Lab/Application/Models/UserPagedResponse.cs:23 — [Obsolete] UpdatorId
D26 · Project Cohesion · Split MS.Microservice.Core · ×1
  • Split MS.Microservice.Core src/MS.Microservice.Core/MS.Microservice.Core.csproj:1 — `MS.Microservice.Core` overshoots its size bounds (6852 LoC, 210 public types across 42 namespaces). These parts reach the rest of the project only through its shared core (`(root)`, `Dto`, `Functional`, `Microsoft`, `Net`, `Specification`), so they are the cleanest seams: `MS.Microservice.Core.IO` (9 types in 6 files): 0 of 39 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 0 times; `MS.Microservice.Core.FeatureManager` (5 types in 4 files): 0 of 7 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 0 times. Extract each into its own project.
D27 · Navigability · Pass-through layer · ×1
  • Pass-through layer src/MS.Microservice.Audio/AudioProcessor.cs:508 — NonClosingStreamWrapper: all 5 public methods forward their arguments unchanged to inner and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call inner directly, or give the layer a job.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 5 of 186 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 186 of the 474 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: MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/BaseContext.cs, MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/DbContext/SqlSugarDbContext.cs, src/MS.Microservice.Core/Functional/Either.cs, MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/SqlSugarQueryableExtensions.cs, MS.Microservice.Persistence/src/MS.Microservice.Persistence.EFCore/DbContext/EFCoreQueryableExtensions.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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
P12 · CI test-gate honesty · Sleep-based test synchronization · ×1
  • Sleep-based test synchronization — 42 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 23/41 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 41, 8 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P2 · Observability · Console output used as the logging channel · ×1
  • Console output used as the logging channel benchmarks/MS.Microservice.Core.HttpLogging.Benchmarks/Program.cs:49 — `benchmarks/MS.Microservice.Core.HttpLogging.Benchmarks/Program.cs` reports through `Console.Write…` at line 49 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:8 — 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 2080 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.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation Directory.Packages.props:8 — `Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
PF1 · Benchmark discipline · No performance benchmarks · ×1
  • No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
S1 · Web-Security Posture · OIDC metadata fetched over HTTP · ×1
  • OIDC metadata fetched over HTTP samples/Lab/MS.Microservice.Lab/Infrastructure/Extensions/IServiceCollectionExtensions.cs:228 — `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path.
S1 · Web-Security Posture · Security headers incomplete · ×1
  • Security headers incomplete REDACTED:26 — Set: Content-Security-Policy, Cross-Origin-Resource-Policy, Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−0.5 on this card.)
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 333/502 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.
X4 · Structured logging · Interpolated log message defeats structured logging · ×1
  • Interpolated log message defeats structured logging samples/Lab/MS.Microservice.Lab/Infrastructure/Authentications/ValidateTokenMiddleware.cs:86 — 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.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.7 `!` suppressions per 1k syntax nodes — 228 suppression(s) across the 328071 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.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×1
  • Hand-rolled JSON/XML parsing via regex samples/AI/MS.Microservice.Samples.EducationalImages/PlanGeneratorClient.cs:285 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×1
  • Silent fallback default on parse failure MS.Microservice.AI/src/MS.Microservice.AI.Core/OpenAICompatibleMediaProviderBase.cs:133 — `MapUsage` returns `AIUsage.Zero` when `root.TryGetProperty("usage", out var usageElement)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Minor — 89 finding(s)
D12 · Dependency Hygiene · Outdated · ×67
  • Outdated: Microsoft.EntityFrameworkCore.Sqlite — Microsoft.EntityFrameworkCore.Sqlite 10.0.6 → 10.0.14 available (referenced by MS.Microservice.Framework.Benchmarks).
  • Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 10.0.6 → 10.0.14 available (referenced by MS.Microservice.Framework.Benchmarks).
  • Outdated: Npgsql.EntityFrameworkCore.PostgreSQL — Npgsql.EntityFrameworkCore.PostgreSQL 10.0.0 → 10.0.3 available (referenced by MS.Microservice.Persistence.Auditing.Benchmarks).
  • Outdated: Microsoft.Extensions.Configuration.Binder — Microsoft.Extensions.Configuration.Binder 10.0.6 → 10.0.14 available (referenced by MS.Microservice.AI.Core).
  • Outdated: Microsoft.Extensions.Http — Microsoft.Extensions.Http 10.0.6 → 10.0.14 available (referenced by MS.Microservice.AI.Core).
  • Outdated: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions 10.0.6 → 10.0.14 available (referenced by MS.Microservice.AI.Core).
  • Outdated: Microsoft.Extensions.Options.ConfigurationExtensions — Microsoft.Extensions.Options.ConfigurationExtensions 10.0.6 → 10.0.14 available (referenced by MS.Microservice.AI.Core).
  • Outdated: Microsoft.Extensions.DependencyInjection.Abstractions — Microsoft.Extensions.DependencyInjection.Abstractions 10.0.6 → 10.0.14 available (referenced by MS.Microservice.AI.QuestionGeneration).
  • Outdated: Microsoft.Extensions.Options — Microsoft.Extensions.Options 10.0.6 → 10.0.14 available (referenced by MS.Microservice.AI.QuestionGeneration).
  • Outdated: FluentAssertions — FluentAssertions 8.6.0 → 8.11.0 available (referenced by MS.Microservice.AI.Core.Tests).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 17.14.1 → 18.11.0 available (referenced by MS.Microservice.AI.Core.Tests).
  • Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 3.1.1 → 4.0.1 available (referenced by MS.Microservice.AI.Core.Tests).
  • Outdated: Microsoft.EntityFrameworkCore.Relational — Microsoft.EntityFrameworkCore.Relational 10.0.6 → 10.0.14 available (referenced by MS.Microservice.Idempotency.EFCore).
  • Outdated: Microsoft.Extensions.Hosting — Microsoft.Extensions.Hosting 10.0.6 → 10.0.14 available (referenced by MS.Microservice.Logging.NLog).
  • Outdated: NLog — NLog 6.1.3 → 6.2.2 available (referenced by MS.Microservice.Logging.NLog).
  • Outdated: NLog.Extensions.Logging — NLog.Extensions.Logging 6.1.3 → 6.2.2 available (referenced by MS.Microservice.Logging.NLog).
  • Outdated: NLog.Web.AspNetCore — NLog.Web.AspNetCore 6.1.3 → 6.2.2 available (referenced by MS.Microservice.Logging.NLog).
  • Outdated: Serilog — Serilog 4.3.0 → 4.4.0 available (referenced by MS.Microservice.Logging.Serilog).
  • Outdated: Serilog.Extensions.Hosting — Serilog.Extensions.Hosting 9.0.0 → 10.0.0 available (referenced by MS.Microservice.Logging.Serilog).
  • Outdated: Serilog.Settings.Configuration — Serilog.Settings.Configuration 9.0.0 → 10.0.1 available (referenced by MS.Microservice.Logging.Serilog).
  • Outdated: Serilog.Sinks.Console — Serilog.Sinks.Console 6.0.0 → 6.1.1 available (referenced by MS.Microservice.Logging.Serilog).
  • Outdated: Microsoft.ML.OnnxRuntime — Microsoft.ML.OnnxRuntime 1.31.0 → 1.31.1 available (referenced by MS.Microservice.Media.Inference).
  • Outdated: SkiaSharp — SkiaSharp 4.153.1 → 4.155.0 available (referenced by MS.Microservice.Media).
  • Outdated: SkiaSharp.HarfBuzz — SkiaSharp.HarfBuzz 4.153.1 → 4.155.0 available (referenced by MS.Microservice.Media).
  • Outdated: SkiaSharp.NativeAssets.Linux.NoDependencies — SkiaSharp.NativeAssets.Linux.NoDependencies 4.153.1 → 4.155.0 available (referenced by MS.Microservice.Media).
  • + 42 more in this group — see findings.md.
D10 · Test Quality · Mock framework · ×16
  • Mock framework: NSubstitute — MS.Microservice.Messaging.IntegrationTests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Messaging.RabbitMQ.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Messaging.Wolverine.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Persistence.EFCore.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Persistence.SqlSugar.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Architecture.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Audio.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Core.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Excel.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.HealthChecks.Redis.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Lab.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Observability.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Reference.Application.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Reference.Web.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Storage.S3.Tests references NSubstitute.
  • Mock framework: NSubstitute — MS.Microservice.Threading.Tests references NSubstitute.
D24 · Comment Value · doc comments repeat the names · ×6
  • doc comments repeat the names MS.Microservice.AI/src/MS.Microservice.AI.Abstractions/AIImageEditRequest.cs:38 — 12 of 65 documented parameters and 2 of 238 summaries in `MS.Microservice.AI.Abstractions` only repeat the member or parameter name (e.g. "Response format, e.g. or ." for `ResponseFormat`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionServices.cs:272 — 0 of 7 documented parameters and 0 of 86 summaries in `MS.Microservice.AI.Core` only repeat the member or parameter name (e.g. "" for `name`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names MS.Microservice.AI/src/MS.Microservice.AI.Qwen/IQwenImageReferenceEditClient.cs:14 — 1 of 2 documented parameters and 0 of 17 summaries in `MS.Microservice.AI.Qwen` only repeat the member or parameter name (e.g. "Cancellation token." for `cancellationToken`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/MS.Microservice.Core/Linq/ExpressionStarter.cs:44 — 0 of 41 documented parameters and 6 of 76 summaries in `MS.Microservice.Core` only repeat the member or parameter name (e.g. "The default expression" for `DefaultExpression`). 48 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/MS.Microservice.Excel/PerformanceProbe.cs:168 — 1 of 10 documented parameters and 0 of 30 summaries in `MS.Microservice.Excel` only repeat the member or parameter name (e.g. "Total bytes allocated." for `TotalAllocatedBytes`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names MS.Microservice.Persistence/src/MS.Microservice.Persistence.SqlSugar/IRepositoryBase.cs:21 — 0 of 13 documented parameters and 0 of 0 summaries in `MS.Microservice.Persistence.SqlSugar` only repeat the member or parameter name (e.g. "" for `parm`). 4 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-13a1f6e6978c4f98b9dcd53f9e26d562/history.json --exit-code 0 --source .3artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-13a1f6e6978c4f98b9dcd53f9e26d562/tree.json --exit-code 0 --source .2artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude samples/Lab/MS.Microservice.Lab.Infrastructure/EventSourcing/Migrations --exclude samples/Lab/MS.Microservice.Lab.Persistence/Migrations --exclude samples/Reference/MS.Microservice.Reference.Persistence/Migrations .96artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan0—
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update8artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .6artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 103 file(s) — `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionPipeline.cs`, `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProductionServices.cs`, `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIProviderConcurrency.cs`, `MS.Microservice.AI/src/MS.Microservice.AI.Core/AIResponseReader.cs`, `MS.Microservice.AI/src/MS.Microservice.AI.QuestionGeneration/AIChat/AIChatQuestionModelClient.cs`, … (+98 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

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

Phone — 16 field(s)
  • PlainRow.Phone benchmarks/MS.Microservice.Framework.Benchmarks/AuditCaptureBenchmark.cs:70
  • ProtectedRow.Phone benchmarks/MS.Microservice.Framework.Benchmarks/AuditCaptureBenchmark.cs:76
  • BenchInput.Phone benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:128
  • User._telephone samples/Lab/MS.Microservice.Lab.Domain/Aggregates/IdentityModel/User.cs:17
  • User.Telephone samples/Lab/MS.Microservice.Lab.Domain/Aggregates/IdentityModel/User.cs:63
  • LogAggregateRoot.Telephone samples/Lab/MS.Microservice.Lab.Domain/Aggregates/LogAggregate/LogAggregateRoot.cs:32
  • RegisterAccountCommand.PhoneNumber samples/Lab/MS.Microservice.Lab/Application/Commands/RegisterAccountCommand.cs:12
  • UserCreatedCommand.Telephone samples/Lab/MS.Microservice.Lab/Application/Commands/UserCreatedCommand.cs:53
  • UserModifyCommand.Telephone samples/Lab/MS.Microservice.Lab/Application/Commands/UserModifyCommand.cs:58
  • UserPagedResponse.Telephone samples/Lab/MS.Microservice.Lab/Application/Models/UserPagedResponse.cs:13
  • SensitiveDemoEntity.Phone samples/Lab/MS.Microservice.Lab/Application/Tools/SensitiveDataDemo.cs:25
  • DemoSmsRequest.PhoneNumber REDACTED:50
  • SensitiveDemoRequest.Phone samples/Lab/MS.Microservice.Lab/Controller/SensitiveDataToolsController.cs:19
  • SensitiveDemoView.Phone samples/Lab/MS.Microservice.Lab/Controller/SensitiveDataToolsController.cs:26
  • CurrentUser.Phone samples/Lab/MS.Microservice.Lab/Infrastructure/Applications/Users/CurrentUser.cs:17
  • SmsMessage.PhoneNumber src/MS.Microservice.Notifications/Sms/SmsMessage.cs:3
Email — 14 field(s)
  • PlainRow.Email benchmarks/MS.Microservice.Framework.Benchmarks/AuditCaptureBenchmark.cs:71
  • ProtectedRow.Email benchmarks/MS.Microservice.Framework.Benchmarks/AuditCaptureBenchmark.cs:77
  • BenchInput.Email benchmarks/MS.Microservice.Framework.Benchmarks/Program.cs:129
  • User._email samples/Lab/MS.Microservice.Lab.Domain/Aggregates/IdentityModel/User.cs:21
  • User.Email samples/Lab/MS.Microservice.Lab.Domain/Aggregates/IdentityModel/User.cs:64
  • AuthenticateResult.Email samples/Lab/MS.Microservice.Lab.Domain/Identity/AuthenticateResult.cs:12
  • RegisterAccountCommand.Email samples/Lab/MS.Microservice.Lab/Application/Commands/RegisterAccountCommand.cs:11
  • UserCreatedCommand.Email samples/Lab/MS.Microservice.Lab/Application/Commands/UserCreatedCommand.cs:58
  • UserModifyCommand.Email samples/Lab/MS.Microservice.Lab/Application/Commands/UserModifyCommand.cs:64
  • UserPagedResponse.Email samples/Lab/MS.Microservice.Lab/Application/Models/UserPagedResponse.cs:32
  • SensitiveDemoEntity.Email samples/Lab/MS.Microservice.Lab/Application/Tools/SensitiveDataDemo.cs:26
  • SensitiveDemoRequest.Email samples/Lab/MS.Microservice.Lab/Controller/SensitiveDataToolsController.cs:20
  • SensitiveDemoView.Email samples/Lab/MS.Microservice.Lab/Controller/SensitiveDataToolsController.cs:26
  • CurrentUser.Email samples/Lab/MS.Microservice.Lab/Infrastructure/Applications/Users/CurrentUser.cs:16

Downloadable artifacts

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

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