Public report of dodyg/practical-aspnetcore, published 23 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 23 October 2026, 10:01 UTC · Survey ID cd_0f06a268bddf4cb9a73b85872f27474e
dodyg/practical-aspnetcore
Measured 23 October 2026, 09:55 UTC, at code version d4acfb4
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Code coverage is not measured: No coverage collector is wired up.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
Knowledge freshness is not measured: Freshness signal contradicted by repo activity.
CAI scoreProvisionalDown 5 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 22,104 lines of product code in 565 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Production Readiness, 20
Findings by how serious they are
94 critical257 serious358 minor
7 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
23 October 2026, 09:55 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The code didn't build, so the score is provisional
Watchdog couldn't build the code: the build stopped with 2 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: CS1022: Type or namespace definition, or end-of-file expected
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
83of 87 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
687of 709 findings point to an exact file and line, so you can open each one in the code. The other 22 concern the repository as a whole, such as missing documentation.
87dimensions across 7 lenses, read from 22,104 lines of product code in 565 projects.
dodyg/practical-aspnetcore scores 35 out of 100, but the score is provisional because the code didn't build, so the ratings below may change once it does.
The weakest lens counts most in the score, and here that is Production Readiness, which scores 20 and is rated Critical. Its CI/CD gates dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 1 Leaked secret finding(s) in Secret Scanning and to resolve the 1 NoWarnInCsproj repeated across 11 files finding(s) in Explicit Debt, and if Production Readiness rose to 70, the score would rise from 35 to about 47.
94 findings are critical: 35 in Page structure, 24 in Forms & labels, 17 in Explicit Debt, six in Text alternatives, five in Web-Security Posture, three in Dependency Vulnerabilities, two in IaC & Container Security, one in Keyboard semantics and one in Secret Scanning.
Watchdog couldn't measure Dependency Hygiene, IL Efficiency and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 22,104 lines, which would take an estimated 0.1 person-years, around €13,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 20 to 70, the lowest score rated Strong, the score would rise from 35 to about 47.
Code composition: what the lines of code areMost of the hand-written code is supporting code, such as wiring, settings and declarations, and business logic is 4% of it. That is normal for a service that mainly connects other systems or stores and fetches records, and worth a look if this product is meant to hold complex business rules.
Business logic 4%Supporting code 92%Tests 1%Generated by tools 3%
New since the last survey: 107 findings
These 107 critical or serious findings weren't in the previous survey, on 9 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 589 findings
These 589 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one. The first 100 are listed here.
Coupling · Off the main sequence: RouteDebugger
Coupling · Off the main sequence: Wasm (blazor-ssr/RazorComponentEight/Wasm)
Coupling · Off the main sequence: Wasm (blazor-ssr/RazorComponentTen/Wasm)
Coupling · Off the main sequence: Wasm (blazor-ssr/RazorComponentThirteen/Wasm)
Coupling · Off the main sequence: CustomElement (blazor-wasm/ComponentTwenty/CustomElement)
Coupling · Off the main sequence: CustomElement (blazor-wasm/ComponentTwentyOne/CustomElement)
Coupling · Off the main sequence: CustomElement (blazor-wasm/ComponentTwentyTwo/CustomElement)
Coupling · Off the main sequence: ClassLibrary
Coupling · Off the main sequence: RazorClassLibrary1 (mvc/razor-class-library/razor-class-library-1/src/RazorClassLibrary1)
Coupling · Off the main sequence: RazorClassLibrary2 (mvc/razor-class-library/razor-class-library-1/src/RazorClassLibrary2)
Coupling · Off the main sequence: RazorClassLibrary1 (mvc/razor-class-library/razor-class-library-with-controllers/src/RazorClassLibrary1)
€4,500 to €21,000, for 75 to 217 hours of work, about 0.1 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 35. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 22,104 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 9 points · Low effort · Secret Scanning
2
Resolve the 1 NoWarnInCsproj repeated across 11 files finding(s) in Explicit Debt — start with nswag.csproj.
Raises the score by about 2 points · Low effort · Explicit Debt
3
Resolve the 1 NoWarnInCsproj repeated across 16 files finding(s) in Explicit Debt — start with writeline-activity.csproj.
Raises the score by about 2 points · Low effort · Explicit Debt
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.
If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: CS1022: Type or namespace definition, or end-of-file expected
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €13,000 to build again, about 0.1 person-years of work. Its weakest lens is Production Readiness, at 20 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
48 modules, with 7 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; 8 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.
Minimal.Api.Pokedex.Services uses Minimal.Api.Pokedex.Models, so a change to Minimal.Api.Pokedex.Models can break Minimal.Api.Pokedex.Services, while a change to Minimal.Api.Pokedex.Services can't break Minimal.Api.Pokedex.Models.
Position
Below the diagonal: Minimal.Api.Pokedex.Services uses a module listed above it, which is the healthy direction.
RazorClassLibrary1 uses RazorClassLibraries.Mvc, so a change to RazorClassLibraries.Mvc can break RazorClassLibrary1, while a change to RazorClassLibrary1 can't break RazorClassLibraries.Mvc.
Position
Below the diagonal: RazorClassLibrary1 uses a module listed above it, which is the healthy direction.
RazorClassLibrary2 uses RazorClassLibraries.Mvc, so a change to RazorClassLibraries.Mvc can break RazorClassLibrary2, while a change to RazorClassLibrary2 can't break RazorClassLibraries.Mvc.
Position
Below the diagonal: RazorClassLibrary2 uses a module listed above it, which is the healthy direction.
XmlValidation.Controllers uses XmlValidation.Models, so a change to XmlValidation.Models can break XmlValidation.Controllers, while a change to XmlValidation.Controllers can't break XmlValidation.Models.
Position
Below the diagonal: XmlValidation.Controllers uses a module listed above it, which is the healthy direction.
PracticalAspNetCore.Controllers uses (global), so a change to (global) can break PracticalAspNetCore.Controllers, while a change to PracticalAspNetCore.Controllers can't break (global).
Position
Below the diagonal: PracticalAspNetCore.Controllers uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 47% · Weak · gated by D18, X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
74
Medium
A02:2025 — Security Misconfiguration
6
High / Critical
A03:2025 — Software Supply Chain Failures
4
High / Critical
A07:2025 — Authentication Failures
1
High / Critical
Roadmap
Immediately resolve the leaked secret in REDACTED and establish a CI pipeline to build and test every change. Implement infrastructure-as-code for disaster recovery by documenting RTO/RPO and restore procedures, while ensuring backups are properly credited. Finally, fix keyboard accessibility for custom controls and integrate static analysis tools into the new workflow to prevent security regressions.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Run 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 — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Per-file score 0–10 — a quality signature. Of 93 files carrying findings, judged against the Production bar: 2% slop · 72% mixed · 26% near-clean.
File
Score
Band
Worst signal
REDACTED
3.4
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
3.9
Slop
Explicit Debt: WriteOnlyPrivateField
REDACTED
5.1
Mixed
IaC & Container Security: High IaC: REDACTED
REDACTED
5.4
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
5.5
Mixed
Explicit Debt: WriteOnlyPrivateField
REDACTED
5.5
Mixed
Explicit Debt: WriteOnlyPrivateField
REDACTED
5.5
Mixed
Explicit Debt: WriteOnlyPrivateField
REDACTED
5.5
Mixed
Explicit Debt: WriteOnlyPrivateField
REDACTED
5.8
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
5.9
Mixed
Static Analysis (SAST): Medium: REDACTED
projects/json/json-7/Program.cs
6.0
Mixed
Explicit Debt: DeadPreprocessorBranch
REDACTED
6.3
Mixed
Static Analysis (SAST): Medium: REDACTED
projects/json/json-8/Program.cs
6.7
Mixed
Explicit Debt: DeadPreprocessorBranch
REDACTED
6.9
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
6.9
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
6.9
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
6.9
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
6.9
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
6.9
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
6.9
Mixed
Static 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 — 94
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 — 257
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 — 358
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 7
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 83 of 87 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 87 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 687 of 709 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Dependency Hygiene couldn't be assessed within its 5-minute budget on a solution this large — not included in this run.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (40 contributor(s) across 3707 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 39 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'projects/route-debugger-web/route-debugger-web/RouteDebuggerWeb.csproj' with message: A FrameworkReference for 'Microsoft.AspNetCore.App' was included in the project. This is implicitly referenced by the .NET SDK and you do not typically need to reference it from your project. For more informatio….
D18 Solution Shape — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The scored solution `projects/yarp/basic-demo/Yarp.Demo.sln`, `projects/mini/minimal-api-pokedex/Minimal.Api.Pokedex.sln`, `projects/blazor-ssr/RazorComponentEight/RazorComponentEight.sln`, `projects/blazor-ssr/RazorComponentTen/RazorComponentTen.sln`, `projects/blazor-ssr/RazorComponentThirteen/RazorComponentThirteen.sln`, `projects/security/dataprotection/ef-key-store/EFCoreKeyStore.sln`, `projects/xml/xml-validation/XmlValidation.sln`, `projects/route-debugger-web/route-debugger-web.sln`, `projects/blazor-ssr/RazorMixMatchFour/RazorMixMatchOne.sln`, `projects/blazor-ssr/RazorMixMatchOne/RazorMixMatchOne.sln`, `projects/hydro/component-2/component-1.sln`, `projects/hydro/cookies/cookies.sln`, `projects/hydro/event-child-parent/event-child-parent.sln`, `projects/hydro/event-global-subject/event-global-subject.sln`, `projects/hydro/event-global/event-global.sln`, `projects/security/dataprotection/azure-keyvault-storage-blob-key-store/AzKeyVaultStorageBlobKeyStore.sln`, `projects/security/dataprotection/azure-storage-blob-key-store/AzStorageBlobKeyStore.sln`, `projects/blazor-ss/Localization/Localization.sln`, `projects/blazor-ssr/RazorMixMatchTwo/RazorMixMatchTwo.sln`, `projects/hydro/component-1/component-1.sln`, `projects/blazor-ssr/RazorComponentEleven/RazorComponentEleven.sln`, `projects/blazor-ssr/RazorComponentFive/RazorComponentFive.sln`, `projects/blazor-ssr/RazorComponentNine/RazorComponentNine.sln`, `projects/blazor-ssr/RazorComponentOne/RazorComponentOne.sln`, `projects/blazor-ssr/RazorComponentSeven/RazorComponentSeven.sln`, `projects/blazor-ssr/RazorComponentSix/RazorComponentSix.sln`, `projects/blazor-ssr/RazorComponentThree/RazorComponentThree.sln`, `projects/blazor-ssr/RazorComponentTwelve/RazorComponentTwelve.sln`, `projects/blazor-ssr/RazorComponentTwo/RazorComponentTwo.sln`, `projects/blazor-ssr/RazorFormHandlingFive/RazorFormHandlingFive.sln`, `projects/blazor-ssr/RazorFormHandlingFour/RazorFormHandlingFour.sln`, `projects/blazor-ssr/RazorFormHandlingOne/RazorFormHandlingOne.sln`, `projects/blazor-ssr/RazorFormHandlingThree/RazorFormHandlingThree.sln`, `projects/blazor-ssr/RazorFormHandlingTwo/RazorFormHandlingTwo.sln`, `projects/blazor-ssr/RazorMixMatchThree/RazorMixMatchThree.sln`, `projects/blazor-wasm/ComponentTwentyFive/ComponentTwentyFive.sln`, `projects/blazor-wasm/ComponentTwentySeven/ComponentTwentySeven.sln`, `projects/blazor-wasm/ComponentTwentySix/ComponentTwentySix.sln`, `projects/blazor-wasm/ComponentTwentyThree/ComponentTwentyThree.sln`, `projects/endpoint-routing/new-routing-11/new-routing-11.sln`, `projects/endpoint-routing/new-routing-12/new-routing-12.sln`, `projects/hydro/hello-world/hello-world.sln`, `projects/polly/rate-limiter-http-client/rate-limiter-http-client.sln`, `projects/application-environment/application-environment.sln`, `projects/device-detection/device-detection.sln`, `projects/sse/sse.sln`, `projects/caching/redis-cache/redis-cache.sln`, `projects/datastar/backend-patch-signals-2/backend-patch-signals-2.sln`, `projects/datastar/backend-patch-signals-4/backend-patch-signals-4.sln`, `projects/datastar/backend-patch-signals/backend-patch-signals.sln`, `projects/datastar/data-attr/data-attr.sln`, `projects/datastar/data-bind/data-bind.sln`, `projects/datastar/data-class/data-class.sln`, `projects/datastar/data-computed/data-computed.sln`, `projects/datastar/data-effect/data-effect.sln`, `projects/datastar/data-ignore/data-ignore.sln`, `projects/datastar/data-indicator/data-indicator.sln`, `projects/datastar/data-on-click/data-on-click.sln`, `projects/datastar/data-on-custom-event/data-on-custom-event.sln`, `projects/datastar/data-on-interval/data-on-interval.sln`, `projects/datastar/data-on-signal-patch-filter/data-on-signal-patch-filter.sln`, `projects/datastar/data-on-signal-patch/data-on-signal-patch.sln`, `projects/datastar/data-patch-elements-outer/data-patch-elements-outer.sln`, `projects/datastar/data-ref/data-ref.sln`, `projects/datastar/data-show/data-show.sln`, `projects/datastar/data-style/data-style.sln`, `projects/datastar/hello-world/hello-world.sln`, `projects/dependency-injection/keyed-service-2/keyed-service-2.sln`, `projects/dependency-injection/keyed-service/keyed-service.sln`, `projects/elsa/composite-activity/composite-activity.sln`, `projects/elsa/for-activity/for-activity.sln`, `projects/elsa/foreach-activity/foreach-activity.sln`, `projects/elsa/fork-activity-2/fork-activity-2.sln`, `projects/elsa/fork-activity/fork-activity.sln`, `projects/elsa/if-activity/if-activity.sln`, `projects/elsa/readline-activity/readline-activity.sln`, `projects/elsa/sequence-activity/sequence-activity.sln`, `projects/elsa/setname-activity/setname-activity.sln`, `projects/elsa/setvariable-activity/setvariable-activity.sln`, `projects/elsa/while-activity/while-activity.sln`, `projects/elsa/workflow-3/workflow-3.sln`, `projects/elsa/workflow-4/workflow-4.sln`, `projects/elsa/workflow-5/workflow-5.sln`, `projects/elsa/workflow/workflow.sln`, `projects/elsa/writeline-activity/writeline-activity.sln`, `projects/exception-handler-middleware/iexception-handler-2/iexception-handler-2.sln`, `projects/exception-handler-middleware/iexception-handler/iexception-handler.sln`, `projects/htmx/all-verbs/all-verbs.sln`, `projects/htmx/boost/boost.sln`, `projects/htmx/form-2/form-2.sln`, `projects/htmx/form/form.sln`, `projects/htmx/header-hx-replace-url/header-hx-replace-url.sln`, `projects/htmx/header-hx-retarget/header-hx-retarget.sln`, `projects/htmx/header-hx-trigger-2/header-hx-trigger-2.sln`, `projects/htmx/header-hx-trigger-3/header-hx-trigger-3.sln`, `projects/htmx/header-hx-trigger-4/header-hx-trigger-4.sln`, `projects/htmx/header-hx-trigger/header-hx-trigger.sln`, `projects/htmx/htmx-config-request/htmx-config-request.sln`, `projects/htmx/htmx-response-error/htmx-response-error.sln`, `projects/htmx/hx-confirm/hx-confirm.sln`, `projects/htmx/hx-headers/hx-headers.sln`, `projects/htmx/hx-include/hx-include.sln`, `projects/htmx/hx-indicator/hx-indicator.sln`, `projects/htmx/hx-on-2/all-verbs.sln`, `projects/htmx/hx-on/hx-on.sln`, `projects/htmx/hx-preserve/hx-preserve.sln`, `projects/htmx/hx-prompt/hx-prompt.sln`, `projects/htmx/hx-replace-url-2/hx-replace-url-2.sln`, `projects/htmx/hx-replace-url/hx-replace-url.sln`, `projects/htmx/modal-bootstrap/modal-bootstrap.sln`, `projects/htmx/push-url/push-url.sln`, `projects/htmx/select-2/select.sln`, `projects/htmx/select-oob/select-oob.sln`, `projects/htmx/select/select.sln`, `projects/htmx/swap-2/swap-2.sln`, `projects/htmx/target/target.sln`, `projects/htmx/trigger-every/trigger-every.sln`, `projects/htmx/trigger-load-2/trigger-load-2.sln`, `projects/htmx/trigger-load/trigger-load.sln`, `projects/htmx/trigger-once/trigger-once.sln`, `projects/logging/logging-4/logging-4.sln`, `projects/logging/logging-5/logging-5.sln`, `projects/minimal-api/minimal-api-form-model-binding/minimal-api-form-model-binding.sln`, `projects/minimal-api/open-api-1/open-api-1.sln`, `projects/minimal-api/open-api-2/open-api-2.sln`, `projects/mvc/jwt/jwt.sln`, `projects/mvc/nswag-2/nswag-2.sln`, `projects/mvc/nswag/nswag.sln`, `projects/net10/open-api-10/open-api-10.sln`, `projects/net10/open-api-11/open-api-11.sln`, `projects/net10/open-api-8/open-api-8.sln`, `projects/net10/open-api-9/open-api-9.sln`, `projects/net10/redirect-http-result-is-local-url/redirect-http-result-is-local-url.sln`, `projects/net10/sse-2/sse-2.sln`, `projects/net10/sse-3/sse-3.sln`, `projects/net10/sse-4/sse-4.sln`, `projects/net10/validation-1/validation-1.sln`, `projects/net10/validation-2/validation-2.sln`, `projects/net10/validation-3/validation-3.sln`, `projects/net9/open-api-3/open-api-3.sln`, `projects/net9/open-api-4/open-api-4.sln`, `projects/net9/typed-results-2/typed-results-2.sln`, `projects/open-telemetry/open-telemetry-1/open-telemetry-1.sln`, `projects/open-telemetry/open-telemetry-2/open-telemetry-2.sln`, `projects/orleans/orleans-2/orleans-2.sln`, `projects/orleans/orleans-3/orleans-3.sln`, `projects/orleans/orleans-4/orleans-4.sln`, `projects/orleans/orleans-5/orleans-5.sln`, `projects/orleans/reminder/reminder.sln`, `projects/request-timeouts-middleware/request-timeout-3/request-timeout-3.sln`, `projects/request-timeouts-middleware/request-timeout-4/request-timeout-4.sln`, `projects/request-timeouts-middleware/request-timeout-5/request-timeout-5.sln`, `projects/request-timeouts-middleware/request-timeout-6/request-timeout-6.sln`, `projects/sfa/wiki/wiki.sln`, `projects/unpoly/up-flashes/up-flashes.sln`, `projects/unpoly/up-hungry/up-hungry.sln`, `projects/unpoly/up-poll/up-poll.sln`, `projects/unpoly/up-target-2/up-target-2.sln`, `projects/unpoly/up-target/up-target.sln` is not representative of this repository — it references only 792 of 2770 discovered C# files (29 %). Lenses that need the product's source (domain modelling, event-driven, event sourcing) abstain because the aggregates, EF configs, and domain events under the product tree were not loaded. You can widen what we reach: point the scan at the product solution, or scan its directory directly, so the whole codebase is analyzed rather than a build-tooling sub-solution.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (22,099 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `REDACTED`, `REDACTED`, `REDACTED`, `projects/blazor-wasm/ComponentTwentySeven/Program.cs`, `projects/datastar/backend-patch-signals-2/Program.cs`, … (+77 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.
D34 Knowledge Freshness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 136 commits in the last 90 days, yet 79 of 120 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
AC3 Page structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 443 further occurrence(s) are not listed individually; the score already reflects all 483.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/bui…; runtime evidence skipped.
S1 Web-Security Posture — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 318 further occurrence(s) are not listed individually; the score already reflects all 358.
X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 29 further occurrence(s) are not listed individually; the score already reflects all 69.
X24 Document value interpolated into markup unescaped — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 102 further occurrence(s) are not listed individually; the score already reflects all 142.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
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.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
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.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
The LLM boundary
LLM-set scores this run (4): D19, D21, D24, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
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.
Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with StringUtils.ToSnakeCase (cognitive 27), StringUtils.ToSnakeCaseNewtonsoft (cognitive 27). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes10.0 / 10Exemplary✓ 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.
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.
25 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Duplicated block (67 lines × 2) finding(s) in Code Duplication — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (13 lines × 3) finding(s) in Code Duplication — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ 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.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
1 test methods: 1 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3 tests.
✓ On the Gold path — maintain.
Detailed fixes: d10_recommendation.md.
Do you agree with this assessment?
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.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 606 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 86 direct `PackageReference`(s), and 164 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
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.
44 deducted debt markers + unmeasured dead symbols across 22099 LoC in the .NET projects (1.8/KLoC) → score 6.5. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
Resolve the 15 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED (6), REDACTED (3), Index.cshtml.cs (3). — One of this dimension's main actionable groups (15 issue-level).
Resolve the 1 NoWarnInCsproj repeated across 11 files finding(s) in Explicit Debt — start with nswag.csproj. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 NoWarnInCsproj repeated across 16 files finding(s) in Explicit Debt — start with writeline-activity.csproj. — One of this dimension's main actionable groups (1 issue-level).
Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.
Do you agree with this assessment?
D18 · Solution Shape3.0 / 10Weak✓ 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.
565 projects, 659 source files, 22120 hand-written lines of code (22099 production / 21 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 699 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 15 inter-project edges (build failed). Measured across 159 solutions loaded as one workspace: `projects/yarp/basic-demo/Yarp.Demo.sln`, `projects/mini/minimal-api-pokedex/Minimal.Api.Pokedex.sln`, `projects/blazor-ssr/RazorComponentEight/RazorComponentEight.sln`, `projects/blazor-ssr/RazorComponentTen/RazorComponentTen.sln`, `projects/blazor-ssr/RazorComponentThirteen/RazorComponentThirteen.sln`, `projects/security/dataprotection/ef-key-store/EFCoreKeyStore.sln`, `projects/xml/xml-validation/XmlValidation.sln`, `projects/route-debugger-web/route-debugger-web.sln`, `projects/blazor-ssr/RazorMixMatchFour/RazorMixMatchOne.sln`, `projects/blazor-ssr/RazorMixMatchOne/RazorMixMatchOne.sln`, `projects/hydro/component-2/component-1.sln`, `projects/hydro/cookies/cookies.sln`, `projects/hydro/event-child-parent/event-child-parent.sln`, `projects/hydro/event-global-subject/event-global-subject.sln`, `projects/hydro/event-global/event-global.sln`, `projects/security/dataprotection/azure-keyvault-storage-blob-key-store/AzKeyVaultStorageBlobKeyStore.sln`, `projects/security/dataprotection/azure-storage-blob-key-store/AzStorageBlobKeyStore.sln`, `projects/blazor-ss/Localization/Localization.sln`, `projects/blazor-ssr/RazorMixMatchTwo/RazorMixMatchTwo.sln`, `projects/hydro/component-1/component-1.sln`, `projects/blazor-ssr/RazorComponentEleven/RazorComponentEleven.sln`, `projects/blazor-ssr/RazorComponentFive/RazorComponentFive.sln`, `projects/blazor-ssr/RazorComponentNine/RazorComponentNine.sln`, `projects/blazor-ssr/RazorComponentOne/RazorComponentOne.sln`, `projects/blazor-ssr/RazorComponentSeven/RazorComponentSeven.sln`, `projects/blazor-ssr/RazorComponentSix/RazorComponentSix.sln`, `projects/blazor-ssr/RazorComponentThree/RazorComponentThree.sln`, `projects/blazor-ssr/RazorComponentTwelve/RazorComponentTwelve.sln`, `projects/blazor-ssr/RazorComponentTwo/RazorComponentTwo.sln`, `projects/blazor-ssr/RazorFormHandlingFive/RazorFormHandlingFive.sln`, `projects/blazor-ssr/RazorFormHandlingFour/RazorFormHandlingFour.sln`, `projects/blazor-ssr/RazorFormHandlingOne/RazorFormHandlingOne.sln`, `projects/blazor-ssr/RazorFormHandlingThree/RazorFormHandlingThree.sln`, `projects/blazor-ssr/RazorFormHandlingTwo/RazorFormHandlingTwo.sln`, `projects/blazor-ssr/RazorMixMatchThree/RazorMixMatchThree.sln`, `projects/blazor-wasm/ComponentTwentyFive/ComponentTwentyFive.sln`, `projects/blazor-wasm/ComponentTwentySeven/ComponentTwentySeven.sln`, `projects/blazor-wasm/ComponentTwentySix/ComponentTwentySix.sln`, `projects/blazor-wasm/ComponentTwentyThree/ComponentTwentyThree.sln`, `projects/endpoint-routing/new-routing-11/new-routing-11.sln`, `projects/endpoint-routing/new-routing-12/new-routing-12.sln`, `projects/hydro/hello-world/hello-world.sln`, `projects/polly/rate-limiter-http-client/rate-limiter-http-client.sln`, `projects/application-environment/application-environment.sln`, `projects/device-detection/device-detection.sln`, `projects/sse/sse.sln`, `projects/caching/redis-cache/redis-cache.sln`, `projects/datastar/backend-patch-signals-2/backend-patch-signals-2.sln`, `projects/datastar/backend-patch-signals-4/backend-patch-signals-4.sln`, `projects/datastar/backend-patch-signals/backend-patch-signals.sln`, `projects/datastar/data-attr/data-attr.sln`, `projects/datastar/data-bind/data-bind.sln`, `projects/datastar/data-class/data-class.sln`, `projects/datastar/data-computed/data-computed.sln`, `projects/datastar/data-effect/data-effect.sln`, `projects/datastar/data-ignore/data-ignore.sln`, `projects/datastar/data-indicator/data-indicator.sln`, `projects/datastar/data-on-click/data-on-click.sln`, `projects/datastar/data-on-custom-event/data-on-custom-event.sln`, `projects/datastar/data-on-interval/data-on-interval.sln`, `projects/datastar/data-on-signal-patch-filter/data-on-signal-patch-filter.sln`, `projects/datastar/data-on-signal-patch/data-on-signal-patch.sln`, `projects/datastar/data-patch-elements-outer/data-patch-elements-outer.sln`, `projects/datastar/data-ref/data-ref.sln`, `projects/datastar/data-show/data-show.sln`, `projects/datastar/data-style/data-style.sln`, `projects/datastar/hello-world/hello-world.sln`, `projects/dependency-injection/keyed-service-2/keyed-service-2.sln`, `projects/dependency-injection/keyed-service/keyed-service.sln`, `projects/elsa/composite-activity/composite-activity.sln`, `projects/elsa/for-activity/for-activity.sln`, `projects/elsa/foreach-activity/foreach-activity.sln`, `projects/elsa/fork-activity-2/fork-activity-2.sln`, `projects/elsa/fork-activity/fork-activity.sln`, `projects/elsa/if-activity/if-activity.sln`, `projects/elsa/readline-activity/readline-activity.sln`, `projects/elsa/sequence-activity/sequence-activity.sln`, `projects/elsa/setname-activity/setname-activity.sln`, `projects/elsa/setvariable-activity/setvariable-activity.sln`, `projects/elsa/while-activity/while-activity.sln`, `projects/elsa/workflow-3/workflow-3.sln`, `projects/elsa/workflow-4/workflow-4.sln`, `projects/elsa/workflow-5/workflow-5.sln`, `projects/elsa/workflow/workflow.sln`, `projects/elsa/writeline-activity/writeline-activity.sln`, `projects/exception-handler-middleware/iexception-handler-2/iexception-handler-2.sln`, `projects/exception-handler-middleware/iexception-handler/iexception-handler.sln`, `projects/htmx/all-verbs/all-verbs.sln`, `projects/htmx/boost/boost.sln`, `projects/htmx/form-2/form-2.sln`, `projects/htmx/form/form.sln`, `projects/htmx/header-hx-replace-url/header-hx-replace-url.sln`, `projects/htmx/header-hx-retarget/header-hx-retarget.sln`, `projects/htmx/header-hx-trigger-2/header-hx-trigger-2.sln`, `projects/htmx/header-hx-trigger-3/header-hx-trigger-3.sln`, `projects/htmx/header-hx-trigger-4/header-hx-trigger-4.sln`, `projects/htmx/header-hx-trigger/header-hx-trigger.sln`, `projects/htmx/htmx-config-request/htmx-config-request.sln`, `projects/htmx/htmx-response-error/htmx-response-error.sln`, `projects/htmx/hx-confirm/hx-confirm.sln`, `projects/htmx/hx-headers/hx-headers.sln`, `projects/htmx/hx-include/hx-include.sln`, `projects/htmx/hx-indicator/hx-indicator.sln`, `projects/htmx/hx-on-2/all-verbs.sln`, `projects/htmx/hx-on/hx-on.sln`, `projects/htmx/hx-preserve/hx-preserve.sln`, `projects/htmx/hx-prompt/hx-prompt.sln`, `projects/htmx/hx-replace-url-2/hx-replace-url-2.sln`, `projects/htmx/hx-replace-url/hx-replace-url.sln`, `projects/htmx/modal-bootstrap/modal-bootstrap.sln`, `projects/htmx/push-url/push-url.sln`, `projects/htmx/select-2/select.sln`, `projects/htmx/select-oob/select-oob.sln`, `projects/htmx/select/select.sln`, `projects/htmx/swap-2/swap-2.sln`, `projects/htmx/target/target.sln`, `projects/htmx/trigger-every/trigger-every.sln`, `projects/htmx/trigger-load-2/trigger-load-2.sln`, `projects/htmx/trigger-load/trigger-load.sln`, `projects/htmx/trigger-once/trigger-once.sln`, `projects/logging/logging-4/logging-4.sln`, `projects/logging/logging-5/logging-5.sln`, `projects/minimal-api/minimal-api-form-model-binding/minimal-api-form-model-binding.sln`, `projects/minimal-api/open-api-1/open-api-1.sln`, `projects/minimal-api/open-api-2/open-api-2.sln`, `projects/mvc/jwt/jwt.sln`, `projects/mvc/nswag-2/nswag-2.sln`, `projects/mvc/nswag/nswag.sln`, `projects/net10/open-api-10/open-api-10.sln`, `projects/net10/open-api-11/open-api-11.sln`, `projects/net10/open-api-8/open-api-8.sln`, `projects/net10/open-api-9/open-api-9.sln`, `projects/net10/redirect-http-result-is-local-url/redirect-http-result-is-local-url.sln`, `projects/net10/sse-2/sse-2.sln`, `projects/net10/sse-3/sse-3.sln`, `projects/net10/sse-4/sse-4.sln`, `projects/net10/validation-1/validation-1.sln`, `projects/net10/validation-2/validation-2.sln`, `projects/net10/validation-3/validation-3.sln`, `projects/net9/open-api-3/open-api-3.sln`, `projects/net9/open-api-4/open-api-4.sln`, `projects/net9/typed-results-2/typed-results-2.sln`, `projects/open-telemetry/open-telemetry-1/open-telemetry-1.sln`, `projects/open-telemetry/open-telemetry-2/open-telemetry-2.sln`, `projects/orleans/orleans-2/orleans-2.sln`, `projects/orleans/orleans-3/orleans-3.sln`, `projects/orleans/orleans-4/orleans-4.sln`, `projects/orleans/orleans-5/orleans-5.sln`, `projects/orleans/reminder/reminder.sln`, `projects/request-timeouts-middleware/request-timeout-3/request-timeout-3.sln`, `projects/request-timeouts-middleware/request-timeout-4/request-timeout-4.sln`, `projects/request-timeouts-middleware/request-timeout-5/request-timeout-5.sln`, `projects/request-timeouts-middleware/request-timeout-6/request-timeout-6.sln`, `projects/sfa/wiki/wiki.sln`, `projects/unpoly/up-flashes/up-flashes.sln`, `projects/unpoly/up-hungry/up-hungry.sln`, `projects/unpoly/up-poll/up-poll.sln`, `projects/unpoly/up-target-2/up-target-2.sln`, `projects/unpoly/up-target/up-target.sln`.
Build failed
Thin analysable surface across projects: ClassLibraryprojects/mvc/localization/mvc-localization-7/ProjectWithResources/ClassLibrary.csproj
What to do
Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Thin analysable surface across projects finding(s) in Solution Shape — start with ClassLibrary.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README documents itself and provides links to ASP.NET Core 11 samples, previous versions, other samples, and a table of sections. It also includes an exercises/pathway-1/README that documents its own directory (exercises for beginning developers), projects/authentication/readme.md that documents its own directory, and projects/blazor-ssr/readme.md that documents its own directory; none of these are the repository root. The visible content is mostly a README with links to samples rather than an overview, installation, or usage guide for the project as a whole. The READMEs for the projects directories (e.g. GRPC, health-check, HTMX, IHttpClientFactory) are each self-contained documentation of that directory rather than the repository; they cover usage examples and point to subdirectories for further detail. The XML-doc coverage is thin across most projects but shows a few solid docs (nswag 7%, open-api 10–12%) with no architecture or design docs, so the lack of an overview and sparse documentation are the main gaps. (13 of 25 sampled documents could not be assessed: 2 of 4 evaluation groups failed.)
Documentation: no project overview · ×2projects/authentication/readme.md
Resolve the 2 Documentation finding(s) in Documentation Quality — start with readme.md, README.md. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
3 naming inconsistencies across 200 sampled symbols.
Inconsistent naming for greeting-related concepts: 'MorningGreeting' and 'EveningGreeting' use a specific time qualifier as a prefix, while 'Greeting' is a generic base concept. Additionally, 'Greeting' exposes a method 'Greet()' (verb) while the others expose a 'Message' property (noun). This suggests 'Greeting' might be a base class or interface, but the naming convention for the specific instances (TimeQualifier + Greeting) differs from the generic concept (Greeting).
Inconsistent tense usage in lifecycle event names: 'OnStopping' (present participle) vs 'OnStopped' (past participle). While this may reflect different stages of the lifecycle, consistency in tense (e.g., 'OnStart'/'OnStop' or 'Starting'/'Stopped') is preferred for clarity.
Use of numeric suffix '2' in type name 'Message2' suggests a lack of descriptive naming for a distinct concept. 'Message' and 'Message2' are likely related but distinct types, and the numeric suffix is not descriptive.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
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.
80 % of calls cross a namespace and 3 % 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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
74 finding(s): 0 critical, 0 high, 73 medium, 1 low. semgrep hit a parse error in 84 file(s) — `REDACTED` (line 33, line 49, lines 49–50, …), `REDACTED` (line 17), `REDACTED` (line 29, line 95, lines 95–96, …), `projects/blazor-wasm/ComponentTwentySeven/Program.cs` (line 19), `projects/datastar/backend-patch-signals-2/Program.cs` (line 19, line 21, line 34), … (+79 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 3 of those file(s) — `projects/blazor-wasm/ComponentTwentySeven/Program.cs`, `projects/minimal-api/minimal-api-form-model-binding/Program.cs`, `projects/polly/rate-limiter-http-client/Pages/Index.cshtml.cs` — 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 4 of those file(s) — `projects/htmx/htmx-after-init/Program.cs`, `projects/htmx/htmx-after-on-load/Program.cs`, `projects/htmx/hx-replace-url-2/Program.cs`, `projects/htmx/hx-vals/Program.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 33 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (15), REDACTED (9), REDACTED (5). — One of this dimension's main actionable groups (33 warning-level).
Resolve the 22 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (12), REDACTED (5), REDACTED (4). — One of this dimension's main actionable groups (22 warning-level).
Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
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.
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.
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. Scored 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. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 200 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives3.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×6) — projects/minimal-hosting/web-application-use-file-server/wwwroot/index.html:10, projects/mvc/tag-helper/tag-helper-4/Views/Home/Index.cshtml:14, projects/mvc/tag-helper/tag-helper-5/Views/Home/Index.cshtml:13, …
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
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 <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×4) — projects/blazor-ss/ChatR/Components/Pages/Index.razor:31, projects/blazor-ss/ChatR/Components/Pages/Index.razor:34, projects/blazor-wasm/RadioButton/Pages/Index.razor:17, …
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. (×4) — projects/blazor-ss/ChatR/Components/Pages/Index.razor:32, projects/blazor-ss/ChatR/Components/Pages/Index.razor:35, projects/blazor-wasm/ComponentEighteen/Pages/Index.razor:7, …
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×16) — projects/blazor-wasm/ComponentNineteen/Pages/Form.razor:1, projects/blazor-wasm/ComponentThirteen/Pages/All.razor:2, projects/blazor-wasm/DataBinding/Pages/Index.razor:18, …
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.
Do you agree with this assessment?
AC3 · Page structure4.1 / 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.
A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet). (×20) — projects/blazor-ss/ChatR/Components/Pages/Index.razor:5, projects/blazor-ss/ComponentEvents-2/Components/Pages/Index.razor:4, projects/blazor-ss/ComponentEvents/Components/Pages/Index.razor:3, …
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×15) — projects/blazor-ss/ChatR/Pages/Index.cshtml:3, projects/blazor-ss/ComponentEvents-2/Pages/Index.cshtml:3, projects/blazor-ss/ComponentEvents/Pages/Index.cshtml:3, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This layout renders the routed page body, so it is where the landmark belongs: wrap @Body in <main>. (×5) — projects/blazor-ss/ComponentEvents-2/Components/Shared/MainLayout.razor:3, projects/blazor-ss/ComponentEvents/Components/Shared/MainLayout.razor:3, projects/blazor-ss/Layout/Components/Pages/NestedLayout.razor:4, …
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.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM). (×10) — projects/mini/pdf-viewer/Pages/Index.cshtml:49, projects/mini/pdf-viewer/Pages/Index.cshtml:56, projects/mini/pdf-viewer/Pages/Index.cshtml:59, …
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — projects/yarp/basic-demo/Yarp.Demo.FrontEnd/Shared/NavMenu.razor:8
An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. — projects/yarp/basic-demo/Yarp.Demo.FrontEnd/wwwroot/index.html:20
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
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.
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.
`input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.css:552
`#viewerContainer` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.css:717
`#thumbnailView > a:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.css:1732
`#loadingBar .progress` moves (`transition: width 200ms`) 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. — projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.css:850
`#loadingBar .progress.indeterminate .glimmer` moves (`animation: progressIndeterminate 1s linear infinite`) 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. — projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.css:892
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.
Do you agree with this assessment?
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 528 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.
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.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`Accumulator` is a singleton (one shared instance) but mutates instance state outside any lock (Total; e.g. `Total` at line 79). — projects/grpc/grpc-17/Program.cs:75
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
C1 · Data 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.
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.
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.
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. — projects/health-check/health-check-3/Program.cs:18
A placeholder string ("<!DOCTYPE html>
<html lang="en">
<head>
…") is still in shipped code — typical of generated boilerplate that was never filled in. — projects/net11/async-validation/Program.cs:4
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`World` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — projects/endpoint-routing/endpoint-routing-4/Program.cs:71, projects/endpoint-routing/endpoint-routing-6/Program.cs:70
`Goodbye` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — projects/endpoint-routing/endpoint-routing-4/Program.cs:74, projects/endpoint-routing/endpoint-routing-6/Program.cs:73
`CallMe` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — projects/endpoint-routing/endpoint-routing-4/Program.cs:77, projects/endpoint-routing/endpoint-routing-6/Program.cs:76
`Away` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — projects/endpoint-routing/endpoint-routing-4/Program.cs:89, projects/endpoint-routing/endpoint-routing-6/Program.cs:88
`CheckHealthAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — projects/health-check/health-check-3/Program.cs:18
`InvokeAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — projects/mvc/view-component/view-component-3/Views/Shared/Components/HelloWorld/HelloWorld.cs:13
A placeholder e-mail address ("taken@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — projects/net11/async-validation/Program.cs:101
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 200 of 565 project(s) that lack one — worth up to 0.7 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
Only 17/565 projects share a common root namespace — the code's module identity is inconsistent.
What to do
Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
README claims a .NET Aspire samples repo exists but there is no aspire-samples project or directory — searched for: `aspire-samples`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:1
projects/configurations/README.md links to `/project/configurations/configuration-bind-option`, but `project/configurations/configuration-bind-option` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — projects/configurations/README.md:46
projects/configurations/README.md links to `/project/configurations/configuration-IOption`, but `project/configurations/configuration-IOption` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — projects/configurations/README.md:52
projects/datastar/README.md links to `data-compute`, but `projects/datastar/data-compute` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — projects/datastar/README.md:37
projects/mini/README.md names .NET 5, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — projects/mini/README.md:3
projects/blazor-ss/ComponentEvents-2/README.md links to `ComponentEvents`, but `projects/blazor-ss/ComponentEvents-2/ComponentEvents` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — projects/blazor-ss/ComponentEvents-2/README.md:3
What to do
Reconcile the README with reality: README claims a .NET Aspire samples repo exists but there is no aspire-samples project or directory; projects/configurations/README.md links to `/project/configurations/configuration-bind-option`, but `project/configurations/configuration-bind-option` does not exist; projects/configurations/README.md links to `/project/configurations/configuration-IOption`, but `project/configurations/configuration-IOption` does not exist; projects/datastar/README.md links to `data-compute`, but `projects/datastar/data-compute` does not exist; projects/mini/README.md names .NET 5, but the projects target .NET 10, 11.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
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.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Do you agree with this assessment?
P10 · Library API & versioning2.0 / 10Critical✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
26/26 types (100%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
What to do
Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
Do you agree with this assessment?
P2 · Observability7.2 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 41/500 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 500, 497 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Run 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 — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ 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.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — projects/blazor-ss/RssReader-2/Services/RssNews.cs:14
`new HttpClient(handler)` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). (×3) — projects/grpc/grpc-10/client/Program.cs:11, projects/grpc/grpc-11/client/Program.cs:13, projects/grpc/grpc-12/client/Program.cs:14
`builder.Services.AddHttpClient<HttpStatusCodeHealthCheck>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — projects/health-check/health-check-4/Program.cs:11
`builder.Services.AddHttpClient<OKHttpStatusCodeHealthCheck>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). (×2) — projects/health-check/health-check-5/Program.cs:11, projects/health-check/health-check-6/Program.cs:11
`builder.Services.AddHttpClient<ErrorHttpStatusCodeHealthCheck>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — projects/health-check/health-check-5/Program.cs:12
`builder.Services.AddHttpClient<Error2HttpStatusCodeHealthCheck>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — projects/health-check/health-check-6/Program.cs:12
`builder.Services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). (×2) — REDACTED:2, projects/orleans/orleans-5/Program.cs:7
`builder.Services.AddHttpClient("rss", c => { // Configure your http client he...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — REDACTED:3
`builder.Services.AddHttpClient<RssReader>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — REDACTED:3
`builder.Services.AddHttpClient<IRss, RssReader>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — REDACTED:3
`new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) }` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — projects/yarp/basic-demo/Yarp.Demo.FrontEnd/Program.cs:7
What to do
Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 19 use(s) across 37,490 production line(s) (~0.5/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
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.
The value is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. (×5) — REDACTED:25, REDACTED:80, REDACTED:24, …
`https://cdn.jsdelivr.net/npm/jquery@3.6.0/dist/jquery.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 28 such include(s) across the repository's markup. — projects/security/dataprotection/azure-keyvault-storage-blob-key-store/src/Pages/Shared/_Layout.cshtml:32
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×33) — REDACTED:7, REDACTED:5, REDACTED:9, …
What to do
Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations. This repository constructs key or salt material fixed at compile time at 5 sites, not one: `REDACTED:25` (token-signing key), `REDACTED:80` (token-signing key), `REDACTED:24` (token-signing key), `REDACTED:187` (token-signing key), `REDACTED:13` (token-signing key). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
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.
`StreamReader.ReadToEnd` blocks the thread on I/O while `StreamReader.ReadToEndAsync` exists to wait without one — inside a method that is already `async`, await the twin. — projects/file-provider/file-provider-custom/Program.cs:17
What to do
Blocking `StreamReader.ReadToEnd` inside an `async` method
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`random` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 40). Every use of it in `GetRandom` 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 random = …;`), which releases it at the end of the scope on every path including a throw. — projects/elsa/composite-activity/Program.cs:40
`random` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 21). Every use of it in `Build` 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 random = …;`), which releases it at the end of the scope on every path including a throw. — projects/elsa/workflow-3/Program.cs:21
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 26/87 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.
This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on. (×17) — projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/PokedexApiEndpoint.cs:19, projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/PokedexApiEndpoint.cs:33, projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/PokedexApiEndpoint.cs:42, …
No CancellationToken parameter — this work can't be stopped early once started. (×21) — projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/Services/PokedexRepository.cs:20, projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/Services/PokedexRepository.cs:27, projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/Services/PokedexService.cs:13, …
No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken. — projects/features/features-server-addresses-2/Program.cs:19
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
The guard on line 112 rejects `reminder` and line 113 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(reminder)` is true of a value that is NOT null: it is satisfied by an EMPTY `reminder`, and on that path `reminder` 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 the empty 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` for the empty case, or split the guard and throw each on its own condition. — projects/orleans/orleans-4/Program.cs:113
The guard on line 126 rejects `reminder` and line 127 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(reminder)` is true of a value that is NOT null: it is satisfied by an EMPTY `reminder`, and on that path `reminder` 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 the empty 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` for the empty case, or split the guard and throw each on its own condition. — projects/orleans/orleans-4/Program.cs:127
The guard on line 108 rejects `reminder` and line 109 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(reminder)` is true of a value that is NOT null: it is satisfied by an EMPTY `reminder`, and on that path `reminder` 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 the empty 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` for the empty case, or split the guard and throw each on its own condition. — projects/orleans/reminder/Program.cs:109
The guard on line 120 rejects `reminder` and line 121 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(reminder)` is true of a value that is NOT null: it is satisfied by an EMPTY `reminder`, and on that path `reminder` 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 the empty 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` for the empty case, or split the guard and throw each on its own condition. — projects/orleans/reminder/Program.cs:121
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.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped1.9 / 10Critical✓ 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.
`JwtBearerDefaults.AuthenticationScheme` is text this program did not author, and it is written into the text of an element through `Text(…, "text/html")` 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:36
`htmlString` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — projects/blazor-ss/RenderTreeBuilder/Program.cs:53
`n.Description` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` 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. (×2) — REDACTED:9, REDACTED:9
`_showMessage` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` 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. (×5) — projects/blazor-ssr/RazorFormHandlingFive/Pages/Index.razor:7, projects/blazor-ssr/RazorFormHandlingFour/Pages/Index.razor:6, projects/blazor-ssr/RazorFormHandlingOne/Pages/Index.razor:6, …
`greeting.Message` is text this program did not author, and it is written into the text of an element through `Content(…, "text/html")` 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. (×2) — projects/dependency-injection/keyed-service-2/Program.cs:45, projects/dependency-injection/keyed-service/Program.cs:29
`c.Name` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. (×4) — projects/file-provider/serve-static-files-4/Program.cs:30, projects/file-provider/serve-static-files-5/Program.cs:34, projects/file-provider/serve-static-files-5/Program.cs:39, …
`c.Name` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — projects/file-provider/serve-static-files-4/Program.cs:32
`Message` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` 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. — projects/grpc/grpc-12/client/Pages/Index.razor:6
`token.HeaderName` is text this program did not author, and it is written into a quoted attribute value through `Content(…, "text/html")` 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. (×19) — projects/htmx/all-verbs/Program.cs:18, projects/htmx/header-hx-refresh/Program.cs:24, projects/htmx/header-hx-replace-url/Program.cs:24, …
`token.FormFieldName` is text this program did not author, and it is written into a quoted attribute value through `Content(…, "text/html")` 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. (×2) — projects/htmx/form-2/Program.cs:27, projects/htmx/form/Program.cs:28
`title` is text this program did not author, and it is written into the text of an element through `Content(…, "text/html")` 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. — projects/htmx/history-config/Program.cs:14
`message` is text this program did not author, and it is written into the text of an element through `Content(…, "text/html")` 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. — projects/htmx/history-config/Program.cs:24
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.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (System.OverflowException)` 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. — projects/grpc/grpc-4/client/Program.cs:34
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×33) — projects/polly/rate-limiter-http-client/Pages/Index.cshtml.cs:37, projects/polly/rate-limiter-http-client/Pages/Index.cshtml.cs:42, projects/orleans/orleans-3/Program.cs:80, …
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.
This method contradicts itself about `targetFramework`: line 9 assigns it with `as System.Runtime.Versioning.TargetFrameworkAttribute`, which hands back null rather than throwing when the value is not a `System.Runtime.Versioning.TargetFrameworkAttribute`, but line 10 then dereferences it directly as `targetFramework.FrameworkName` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `targetFramework` once before the first use and handle the null case, or cast with `(System.Runtime.Versioning.TargetFrameworkAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side. — projects/application-environment/Program.cs:10
This method contradicts itself about `route`: line 17 assigns it with `as IEndpointRouteBuilder`, which hands back null rather than throwing when the value is not a `IEndpointRouteBuilder`, but line 19 then dereferences it directly as `route.DataSources` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `route` once before the first use and handle the null case, or cast with `(IEndpointRouteBuilder)` so the failure is reported where it happens — rather than leaving the two readings side by side. — projects/endpoint-routing/new-routing-6/Program.cs:19
This method contradicts itself about `contentPhysical`: line 10 assigns it with `as PhysicalFileProvider`, which hands back null rather than throwing when the value is not a `PhysicalFileProvider`, but line 13 then dereferences it directly as `contentPhysical.Root` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `contentPhysical` once before the first use and handle the null case, or cast with `(PhysicalFileProvider)` so the failure is reported where it happens — rather than leaving the two readings side by side. — projects/file-provider/file-provider-physical/Program.cs:13
This method contradicts itself about `webPhysical`: line 25 assigns it with `as PhysicalFileProvider`, which hands back null rather than throwing when the value is not a `PhysicalFileProvider`, but line 28 then dereferences it directly as `webPhysical.Root` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `webPhysical` once before the first use and handle the null case, or cast with `(PhysicalFileProvider)` so the failure is reported where it happens — rather than leaving the two readings side by side. — projects/file-provider/file-provider-physical/Program.cs:28
This method contradicts itself about `p`: line 32 assigns it with `as Person`, which hands back null rather than throwing when the value is not a `Person`, but line 35 then dereferences it directly as `p.Name` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `p` once before the first use and handle the null case, or cast with `(Person)` so the failure is reported where it happens — rather than leaving the two readings side by side. — projects/json/json-11/Program.cs:35
This method contradicts itself about `host`: line 81 assigns it with `as IWebHostEnvironment`, which hands back null rather than throwing when the value is not a `IWebHostEnvironment`, but line 83 then dereferences it directly as `host.EnvironmentName` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `host` once before the first use and handle the null case, or cast with `(IWebHostEnvironment)` so the failure is reported where it happens — rather than leaving the two readings side by side. — projects/mvc/api-problem-details-2/Program.cs:83
33/564 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
~2.4 `!` suppressions per 1k syntax nodes — 39 suppression(s) across the 16198 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
Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 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).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X8 JS interop contract — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
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.
AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/bui…; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D12 Dependency Hygiene — Dependency Hygiene not included (time budget)
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 82 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
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.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 value object(s))
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 3 event handler(s); a message-bus package
ED5 Idempotency — 3 mutating command handler(s)/consumer(s) detected and 6 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — no CI workflow found
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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
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 — 94 finding(s)
AC3 · Page structure· Routed page without a <PageTitle> · ×20
Routed page without a <PageTitle> projects/blazor-ss/ChatR/Components/Pages/Index.razor:5— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/ComponentEvents-2/Components/Pages/Index.razor:4— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/ComponentEvents/Components/Pages/Index.razor:3— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/DependencyInjection/Components/Pages/Index.razor:6— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/HelloWorld/Components/Pages/Index.razor:3— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/JsIntegration/Components/Pages/Index.razor:4— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/Layout/Components/Pages/Index.razor:4— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/Layout/Components/Pages/PageUsingNestedLayout.razor:4— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/Layout/Components/Pages/PageUsingNestedLayout2.razor:4— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/Localization-2/Components/Pages/Index.razor:2— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/Localization-3/Components/Pages/Index.razor:2— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/Localization-4/Components/Pages/Index.razor:2— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/Localization/Components/Pages/Index.razor:2— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/RssReader-2/Components/Pages/Index.razor:3— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/RssReader/Components/Pages/Index.razor:3— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/StartingVariation/Components/Pages/About.razor:3— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/StartingVariation/Components/Pages/Index.razor:3— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/StartingVariation/Components/Pages/Manage.razor:3— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/StartingVariation/Components/Pages/Secure/Index.razor:3— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
Routed page without a <PageTitle> projects/blazor-ss/StartingVariation/Components/Pages/Secure/Screen.razor:3— A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
AC2 · Forms & labels· <input> without a programmatic label · ×15
<input> without a programmatic label projects/blazor-ss/ChatR/Components/Pages/Index.razor:32— 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.
<input> without a programmatic label projects/blazor-wasm/ComponentEighteen/Pages/Index.razor:7— 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.
<input> without a programmatic label projects/blazor-wasm/ComponentNineteen/Pages/Form.razor:1— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label projects/blazor-wasm/ComponentThirteen/Pages/All.razor:2— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label projects/blazor-wasm/DataBinding/Pages/Index.razor:18— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label projects/blazor-wasm/DataBinding/Pages/Index.razor:30— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label projects/razor-pages/custom-html-generator/Pages/Index.cshtml:27— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label projects/razor-pages/custom-html-generator/Pages/Index.cshtml:28— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label projects/razor-pages/custom-html-generator/Pages/Index.cshtml:29— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label projects/razor-pages/custom-html-generator/Pages/Index.cshtml:30— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label projects/razor-pages/razor-pages-mvc/Pages/RazorPages/Create.cshtml:10— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label projects/razor-pages/razor-pages-mvc/Pages/RazorPages/Create.cshtml:11— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label projects/razor-pages/razor-pages-mvc/Views/Entry/Create.cshtml:11— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label projects/razor-pages/razor-pages-mvc/Views/Entry/Create.cshtml:12— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label projects/signalr/signalr-1/Client/Views/Home/Index.cshtml:10— 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.
<html> without a lang projects/blazor-ss/ChatR/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/ComponentEvents-2/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/ComponentEvents/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/DependencyInjection/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/HelloWorld/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/JsIntegration/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/Layout/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/Localization-2/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/Localization-3/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/Localization-4/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/Localization/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/RssReader-2/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/RssReader/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/StartingVariation/Pages/Admin/Blazor.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang projects/blazor-ss/StartingVariation/Pages/Index.cshtml:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
WriteOnlyPrivateField projects/authentication/authentication-4/Controllers/WeatherForecastController.cs:15— private ILogger<WeatherForecastController> _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 REDACTED:14— private ILogger<WeatherForecastController> _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 projects/endpoint-routing/new-routing-10/Program.cs:14— private LinkGenerator _linkGenerator — 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 projects/endpoint-routing/new-routing-11/Program.cs:15— private LinkGenerator _linkGenerator — 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 projects/endpoint-routing/new-routing-12/Program.cs:15— private LinkGenerator _linkGenerator — 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 projects/endpoint-routing/new-routing-13/Program.cs:14— private LinkGenerator _linkGenerator — 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 projects/mvc/result-json/Program.cs:30— private IWebHostEnvironment _env — 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 projects/orleans/orleans-5/Program.cs:50— private ILogger _log — 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 REDACTED:16— private ILogger<ErrorModel> _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 REDACTED:16— private ILogger<ErrorModel> _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 REDACTED:16— private ILogger<ErrorModel> _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 projects/security/dataprotection/azure-keyvault-storage-blob-key-store/src/Pages/Index.cshtml.cs:12— private ILogger<IndexModel> _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 projects/security/dataprotection/azure-storage-blob-key-store/src/Pages/Index.cshtml.cs:12— private ILogger<IndexModel> _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 projects/security/dataprotection/ef-key-store/src/Pages/Index.cshtml.cs:12— private ILogger<IndexModel> _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 REDACTED:12— private ILogger<HomeController> _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.
AC1 · Text alternatives· <img> without a text alternative · ×6
<img> without a text alternative projects/minimal-hosting/web-application-use-file-server/wwwroot/index.html:10— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative projects/mvc/tag-helper/tag-helper-4/Views/Home/Index.cshtml:14— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative projects/mvc/tag-helper/tag-helper-5/Views/Home/Index.cshtml:13— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative projects/mvc/tag-helper/tag-helper-5/Views/Home/Index.cshtml:19— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative projects/mvc/tag-helper/tag-helper-img/Views/Home/Index.cshtml:10— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative projects/orchard-core/static-files/ForumModule/Views/Home/Index.cshtml:8— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
S1 · Web-Security Posture· Cryptographic key material is a compile-time constant · ×5
Cryptographic key material is a compile-time constant REDACTED:25— The value is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
Cryptographic key material is a compile-time constant REDACTED:80— The value is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
Cryptographic key material is a compile-time constant REDACTED:24— The value is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
Cryptographic key material is a compile-time constant REDACTED:187— The value is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
Cryptographic key material is a compile-time constant REDACTED:13— The value is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
AC2 · Forms & labels· <label> that labels no control · ×4
<label> that labels no control projects/blazor-ss/ChatR/Components/Pages/Index.razor:31— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control projects/blazor-ss/ChatR/Components/Pages/Index.razor:34— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control projects/blazor-wasm/RadioButton/Pages/Index.razor:17— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control projects/blazor-wasm/RadioButton/Pages/Index.razor:33— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC2 · Forms & labels· <textarea> without a programmatic label · ×4
<textarea> without a programmatic label projects/blazor-ss/ChatR/Components/Pages/Index.razor:35— 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.
<textarea> without a programmatic label projects/blazor-wasm/DataBinding/Pages/Index.razor:21— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label projects/xml/xml-validation/Views/Home/Index.cshtml:40— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label projects/xml/xml-validation/Views/Home/Index.cshtml:46— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <select> without a programmatic label · ×1
<select> without a programmatic label projects/blazor-wasm/DataBinding/Pages/Index.razor:24— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×1
Click handler on a non-interactive <div> projects/yarp/basic-demo/Yarp.Demo.FrontEnd/Shared/NavMenu.razor:8— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
NoWarnInCsproj repeated across 11 files projects/mvc/nswag/nswag.csproj:7— The identical NoWarnInCsproj (`1591`) appears in 11 files (11 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 11 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
NoWarnInCsproj repeated across 16 files projects/elsa/writeline-activity/writeline-activity.csproj:5— The identical NoWarnInCsproj (`ASP0000`) appears in 16 files (16 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 16 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
Serious — 257 finding(s)
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×40
Untrusted text written into markup unescaped REDACTED:36— `JwtBearerDefaults.AuthenticationScheme` is text this program did not author, and it is written into the text of an element through `Text(…, "text/html")` 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 projects/blazor-ss/RenderTreeBuilder/Program.cs:53— `htmlString` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:9— `n.Description` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` 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:9— `n.Description` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` 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 projects/blazor-ssr/RazorFormHandlingFive/Pages/Index.razor:7— `_showMessage` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` 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 projects/blazor-ssr/RazorFormHandlingFour/Pages/Index.razor:6— `_showMessage` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` 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 projects/blazor-ssr/RazorFormHandlingOne/Pages/Index.razor:6— `_showMessage` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` 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 projects/blazor-ssr/RazorFormHandlingThree/Pages/Index.razor:6— `_showMessage` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` 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 projects/blazor-ssr/RazorFormHandlingTwo/Pages/Index.razor:6— `_showMessage` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` 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 projects/dependency-injection/keyed-service-2/Program.cs:45— `greeting.Message` is text this program did not author, and it is written into the text of an element through `Content(…, "text/html")` 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 projects/dependency-injection/keyed-service/Program.cs:29— `greeting.Message` is text this program did not author, and it is written into the text of an element through `Content(…, "text/html")` 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 projects/file-provider/serve-static-files-4/Program.cs:30— `c.Name` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped projects/file-provider/serve-static-files-4/Program.cs:32— `c.Name` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped projects/file-provider/serve-static-files-5/Program.cs:34— `c.Name` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped projects/file-provider/serve-static-files-5/Program.cs:39— `c.Name` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped projects/file-provider/serve-static-files-5/Program.cs:41— `c.Name` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped projects/grpc/grpc-12/client/Pages/Index.razor:6— `Message` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` 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 projects/htmx/all-verbs/Program.cs:18— `token.HeaderName` is text this program did not author, and it is written into a quoted attribute value through `Content(…, "text/html")` 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 projects/htmx/form-2/Program.cs:27— `token.FormFieldName` is text this program did not author, and it is written into a quoted attribute value through `Content(…, "text/html")` 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 projects/htmx/form/Program.cs:28— `token.FormFieldName` is text this program did not author, and it is written into a quoted attribute value through `Content(…, "text/html")` 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 projects/htmx/header-hx-refresh/Program.cs:24— `token.HeaderName` is text this program did not author, and it is written into a quoted attribute value through `Content(…, "text/html")` 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 projects/htmx/header-hx-replace-url/Program.cs:24— `token.HeaderName` is text this program did not author, and it is written into a quoted attribute value through `Content(…, "text/html")` 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 projects/htmx/header-hx-reselect/Program.cs:24— `token.HeaderName` is text this program did not author, and it is written into a quoted attribute value through `Content(…, "text/html")` 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 projects/htmx/header-hx-retarget/Program.cs:24— `token.HeaderName` is text this program did not author, and it is written into a quoted attribute value through `Content(…, "text/html")` 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 projects/htmx/header-hx-trigger-2/Program.cs:24— `token.HeaderName` is text this program did not author, and it is written into a quoted attribute value through `Content(…, "text/html")` 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.
X2 · Cancellation propagation· Async method without CancellationToken · ×22
Async method without CancellationToken: Read projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/Services/PokedexRepository.cs:20— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadPokemons projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/Services/PokedexRepository.cs:27— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllAsync projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/Services/PokedexService.cs:13— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAsync projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/Services/PokedexService.cs:19— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAsync projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/Services/PokedexService.cs:25— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SearchAsync projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/Services/PokedexService.cs:31— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OnGet projects/polly/rate-limiter-http-client/Pages/Index.cshtml.cs:10— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadProductsJsonAsync projects/polly/rate-limiter-http-client/Pages/Index.cshtml.cs:32— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SayHello projects/orleans/orleans-2/Program.cs:74— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetCurrentTime projects/orleans/orleans-5/Program.cs:60— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Index projects/request-timeouts-middleware/request-timeout-4/Program.cs:18— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Index projects/request-timeouts-middleware/request-timeout-5/Program.cs:30— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Index projects/request-timeouts-middleware/request-timeout-6/Program.cs:29— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Broadcast projects/blazor-ss/ChatR/NotificationHub.cs:24— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ServerMessage projects/blazor-ss/ChatR/NotificationHub.cs:30— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ConnectAsync projects/blazor-ss/ChatR/Services/NotificationService.cs:19— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: BroadcastAsync projects/blazor-ss/ChatR/Services/NotificationService.cs:47— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetMultipleNewsAsync projects/blazor-ss/RssReader-2/Services/RssNews.cs:19— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetNewsAsync projects/blazor-ss/RssReader-2/Services/RssNews.cs:27— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetNewsAsync REDACTED:8— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: IncrementCount projects/blazor-wasm/ComponentFive/Pages/GreetingBase.cs:14— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Invoke projects/features/features-server-addresses-2/Program.cs:19— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async endpoint handler without CancellationToken: (lambda) projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/PokedexApiEndpoint.cs:19— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: (lambda) projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/PokedexApiEndpoint.cs:33— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: (lambda) projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/PokedexApiEndpoint.cs:42— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: (lambda) projects/mini/minimal-api-pokedex/src/Minimal.Api.Pokedex/PokedexApiEndpoint.cs:57— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: / projects/htmx/hx-indicator/Program.cs:108— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: / projects/htmx/hx-indicator/Program.cs:114— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: / projects/htmx/hx-indicator/Program.cs:120— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: / projects/htmx/hx-indicator/Program.cs:126— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: / projects/htmx/hx-indicator/Program.cs:132— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: / projects/orleans/orleans-2/Program.cs:29— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: / projects/orleans/orleans-3/Program.cs:29— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: / projects/orleans/orleans-4/Program.cs:30— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /set-reminder projects/orleans/orleans-4/Program.cs:57— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /remove-reminder projects/orleans/orleans-4/Program.cs:66— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: / projects/orleans/orleans-5/Program.cs:23— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: / projects/request-timeouts-middleware/request-timeout-3/Program.cs:19— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /slow projects/htmx/htmx-error/Program.cs:25— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Outbound HTTP without resilience projects/blazor-ss/RssReader-2/Services/RssNews.cs:14— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience projects/grpc/grpc-10/client/Program.cs:11— `new HttpClient(handler)` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience projects/grpc/grpc-11/client/Program.cs:13— `new HttpClient(handler)` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience projects/grpc/grpc-12/client/Program.cs:14— `new HttpClient(handler)` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience projects/health-check/health-check-4/Program.cs:11— `builder.Services.AddHttpClient<HttpStatusCodeHealthCheck>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience projects/health-check/health-check-5/Program.cs:11— `builder.Services.AddHttpClient<OKHttpStatusCodeHealthCheck>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience projects/health-check/health-check-5/Program.cs:12— `builder.Services.AddHttpClient<ErrorHttpStatusCodeHealthCheck>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience projects/health-check/health-check-6/Program.cs:11— `builder.Services.AddHttpClient<OKHttpStatusCodeHealthCheck>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience projects/health-check/health-check-6/Program.cs:12— `builder.Services.AddHttpClient<Error2HttpStatusCodeHealthCheck>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience REDACTED:2— `builder.Services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience REDACTED:3— `builder.Services.AddHttpClient("rss", c => { // Configure your http client he...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience REDACTED:3— `builder.Services.AddHttpClient<RssReader>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience REDACTED:3— `builder.Services.AddHttpClient<IRss, RssReader>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience projects/orleans/orleans-5/Program.cs:7— `builder.Services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience projects/yarp/basic-demo/Yarp.Demo.FrontEnd/Program.cs:7— `new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) }` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Hollow method — returns a constant without doing the work projects/endpoint-routing/endpoint-routing-4/Program.cs:71— `World` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work projects/endpoint-routing/endpoint-routing-4/Program.cs:74— `Goodbye` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work projects/endpoint-routing/endpoint-routing-4/Program.cs:77— `CallMe` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work projects/endpoint-routing/endpoint-routing-4/Program.cs:89— `Away` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work projects/endpoint-routing/endpoint-routing-6/Program.cs:70— `World` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work projects/endpoint-routing/endpoint-routing-6/Program.cs:73— `Goodbye` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work projects/endpoint-routing/endpoint-routing-6/Program.cs:76— `CallMe` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work projects/endpoint-routing/endpoint-routing-6/Program.cs:88— `Away` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×6
Symbol treated as nullable, then dereferenced unguarded projects/application-environment/Program.cs:10— This method contradicts itself about `targetFramework`: line 9 assigns it with `as System.Runtime.Versioning.TargetFrameworkAttribute`, which hands back null rather than throwing when the value is not a `System.Runtime.Versioning.TargetFrameworkAttribute`, but line 10 then dereferences it directly as `targetFramework.FrameworkName` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `targetFramework` once before the first use and handle the null case, or cast with `(System.Runtime.Versioning.TargetFrameworkAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded projects/endpoint-routing/new-routing-6/Program.cs:19— This method contradicts itself about `route`: line 17 assigns it with `as IEndpointRouteBuilder`, which hands back null rather than throwing when the value is not a `IEndpointRouteBuilder`, but line 19 then dereferences it directly as `route.DataSources` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `route` once before the first use and handle the null case, or cast with `(IEndpointRouteBuilder)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded projects/file-provider/file-provider-physical/Program.cs:13— This method contradicts itself about `contentPhysical`: line 10 assigns it with `as PhysicalFileProvider`, which hands back null rather than throwing when the value is not a `PhysicalFileProvider`, but line 13 then dereferences it directly as `contentPhysical.Root` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `contentPhysical` once before the first use and handle the null case, or cast with `(PhysicalFileProvider)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded projects/file-provider/file-provider-physical/Program.cs:28— This method contradicts itself about `webPhysical`: line 25 assigns it with `as PhysicalFileProvider`, which hands back null rather than throwing when the value is not a `PhysicalFileProvider`, but line 28 then dereferences it directly as `webPhysical.Root` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `webPhysical` once before the first use and handle the null case, or cast with `(PhysicalFileProvider)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded projects/json/json-11/Program.cs:35— This method contradicts itself about `p`: line 32 assigns it with `as Person`, which hands back null rather than throwing when the value is not a `Person`, but line 35 then dereferences it directly as `p.Name` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `p` once before the first use and handle the null case, or cast with `(Person)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded projects/mvc/api-problem-details-2/Program.cs:83— This method contradicts itself about `host`: line 81 assigns it with `as IWebHostEnvironment`, which hands back null rather than throwing when the value is not a `IWebHostEnvironment`, but line 83 then dereferences it directly as `host.EnvironmentName` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `host` once before the first use and handle the null case, or cast with `(IWebHostEnvironment)` so the failure is reported where it happens — rather than leaving the two readings side by side.
AC3 · Page structure· Page without a main landmark · ×5
Page without a main landmark projects/blazor-ss/ComponentEvents-2/Components/Shared/MainLayout.razor:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This layout renders the routed page body, so it is where the landmark belongs: wrap @Body in <main>.
Page without a main landmark projects/blazor-ss/ComponentEvents/Components/Shared/MainLayout.razor:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This layout renders the routed page body, so it is where the landmark belongs: wrap @Body in <main>.
Page without a main landmark projects/blazor-ss/Layout/Components/Pages/NestedLayout.razor:4— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This layout renders the routed page body, so it is where the landmark belongs: wrap @Body in <main>.
Page without a main landmark projects/blazor-ss/Layout/Components/Pages/NestedLayout2.razor:4— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This layout renders the routed page body, so it is where the landmark belongs: wrap @Body in <main>.
Page without a main landmark projects/blazor-ss/Layout/Components/Pages/TopLayout.razor:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This layout renders the routed page body, so it is where the landmark belongs: wrap @Body in <main>.
X20 · Mistyped argument guard· Argument guard throws the exception its own condition disproves · ×4
Argument guard throws the exception its own condition disproves projects/orleans/orleans-4/Program.cs:113— The guard on line 112 rejects `reminder` and line 113 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(reminder)` is true of a value that is NOT null: it is satisfied by an EMPTY `reminder`, and on that path `reminder` 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 the empty 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` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves projects/orleans/orleans-4/Program.cs:127— The guard on line 126 rejects `reminder` and line 127 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(reminder)` is true of a value that is NOT null: it is satisfied by an EMPTY `reminder`, and on that path `reminder` 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 the empty 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` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves projects/orleans/reminder/Program.cs:109— The guard on line 108 rejects `reminder` and line 109 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(reminder)` is true of a value that is NOT null: it is satisfied by an EMPTY `reminder`, and on that path `reminder` 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 the empty 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` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves projects/orleans/reminder/Program.cs:121— The guard on line 120 rejects `reminder` and line 121 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(reminder)` is true of a value that is NOT null: it is satisfied by an EMPTY `reminder`, and on that path `reminder` 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 the empty 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` for the empty case, or split the guard and throw each on its own condition.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×3
Focus outline removed in CSS without a :focus replacement projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.css:552— `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.css:717— `#viewerContainer` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.css:1732— `#thumbnailView > a:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Duplicated block (15 lines × 2) projects/blazor-ss/RssReader-2/Services/RssNews.cs:34— projects/blazor-ss/RssReader-2/Services/RssNews.cs:34-48 | REDACTED:14-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `projects/blazor-ss/RssReader-2/Services/RssNews.cs:50` calls `Delay` and `REDACTED:30` 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 (15 lines × 2) REDACTED:80— REDACTED:80-94 | REDACTED:187-201 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 15 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) projects/generic-host/generic-host-3/Program.cs:24— projects/generic-host/generic-host-3/Program.cs:24-82 | projects/generic-host/generic-host-4/Program.cs:30-44 — 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 `projects/generic-host/generic-host-3/Program.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. 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.
Positive tabindex (1) projects/mini/pdf-viewer/Pages/Index.cshtml:49— A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
Positive tabindex (1) projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.html:44— A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
Positive tabindex (2) projects/mini/pdf-viewer/Pages/Index.cshtml:56— A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
Positive tabindex (2) projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.html:51— A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
Positive tabindex (3) projects/mini/pdf-viewer/Pages/Index.cshtml:59— A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
Positive tabindex (3) projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.html:54— A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
Positive tabindex (4) projects/mini/pdf-viewer/Pages/Index.cshtml:62— A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
Positive tabindex (4) projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.html:57— A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
Positive tabindex (5) projects/mini/pdf-viewer/Pages/Index.cshtml:65— A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
Positive tabindex (5) projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.html:60— A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×2
Animation without a prefers-reduced-motion guard projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.css:850— `#loadingBar .progress` moves (`transition: width 200ms`) 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.
Animation without a prefers-reduced-motion guard projects/mini/pdf-viewer/wwwroot/js/pdfjs-viewer/viewer.css:892— `#loadingBar .progress.indeterminate .glimmer` moves (`animation: progressIndeterminate 1s linear infinite`) 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.
DeadPreprocessorBranch projects/json/json-7/Program.cs:91— #if HAVE_CHAR_TO_LOWER_WITH_CULTURE — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch projects/json/json-8/Program.cs:70— #if HAVE_CHAR_TO_LOWER_WITH_CULTURE — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
Duplicated block (67 lines × 2) projects/json/json-7/Program.cs:52— projects/json/json-7/Program.cs:52-118 | projects/json/json-8/Program.cs:31-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (67 lines × 2) projects/mvc/nswag-2/Program.cs:22— projects/mvc/nswag-2/Program.cs:22-114 | REDACTED:32-98 — `projects/mvc/nswag-2/Program.cs` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 93 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `projects/mvc/nswag-2/Program.cs:22` 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. 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 (13 lines × 3) projects/json/json-2/Program.cs:36— projects/json/json-2/Program.cs:36-48 | projects/json/json-5/Program.cs:42-54 | projects/json/json/Program.cs:25-37 — `projects/json/json-2/Program.cs` and `projects/json/json-5/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 13 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `projects/json/json-2/Program.cs:36` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) projects/grpc/grpc-11/server/Program.cs:26— projects/grpc/grpc-11/server/Program.cs:26-38 | projects/grpc/grpc-12/server/Program.cs:33-45 | projects/grpc/grpc-2/server/Program.cs:25-37 — before extracting anything, compare `projects/grpc/grpc-11/server/Program.cs` and `projects/grpc/grpc-12/server/Program.cs` as WHOLE FILES: 90% 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. 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 (10 lines × 2) projects/health-check/health-check-4/Program.cs:59— projects/health-check/health-check-4/Program.cs:59-68 | projects/health-check/health-check-5/Program.cs:80-89 — 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 `projects/health-check/health-check-4/Program.cs:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) projects/dependency-injection/keyed-service-2/Program.cs:28— projects/dependency-injection/keyed-service-2/Program.cs:28-37 | projects/dependency-injection/keyed-service/Program.cs:12-21 — `projects/dependency-injection/keyed-service-2/Program.cs` and `projects/dependency-injection/keyed-service/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 10 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (10 lines × 4) projects/blazor-ss/Localization-2/Pages/Switch.cshtml:10— projects/blazor-ss/Localization-2/Pages/Switch.cshtml:10-19 | projects/blazor-ss/Localization-3/Pages/Switch.cshtml:11-20 | projects/blazor-ss/Localization-4/Pages/Switch.cshtml:11-20 | projects/blazor-ss/Localization/Pages/Switch.cshtml:11-20 — before extracting anything, compare `projects/blazor-ss/Localization-2/Pages/Switch.cshtml` and `projects/blazor-ss/Localization-3/Pages/Switch.cshtml` as WHOLE FILES: 100% 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. 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 (10 lines × 4) projects/datastar/backend-patch-signals-4/Program.cs:12— projects/datastar/backend-patch-signals-4/Program.cs:12-21 | projects/datastar/data-indicator/Program.cs:12-21 | projects/datastar/data-on-signal-patch-filter/Program.cs:12-21 | projects/datastar/data-on-signal-patch/Program.cs:12-21 — `projects/datastar/backend-patch-signals-4/Program.cs` and `projects/datastar/data-on-signal-patch-filter/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 17 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `projects/datastar/backend-patch-signals-4/Program.cs:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `projects/datastar/backend-patch-signals-4/Program.cs:23` calls `Contains` and `projects/datastar/data-indicator/Program.cs:22` 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 (8 lines × 2) projects/datastar/backend-patch-signals-2/Program.cs:12— projects/datastar/backend-patch-signals-2/Program.cs:12-19 | projects/datastar/backend-patch-signals-3/Program.cs:12-19 — `projects/datastar/backend-patch-signals-2/Program.cs` and `projects/datastar/backend-patch-signals-3/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 15 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `projects/datastar/backend-patch-signals-2/Program.cs:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `projects/datastar/backend-patch-signals-3/Program.cs:21` calls `Contains` and `projects/datastar/backend-patch-signals-2/Program.cs:21` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) projects/blazor-ssr/RazorFormHandlingFour/Pages/Index.razor:75— projects/blazor-ssr/RazorFormHandlingFour/Pages/Index.razor:75-82 | projects/blazor-ssr/RazorFormHandlingThree/Pages/Index.razor:77-84 — before extracting anything, compare `projects/blazor-ssr/RazorFormHandlingFour/Pages/Index.razor` and `projects/blazor-ssr/RazorFormHandlingThree/Pages/Index.razor` 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 2 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. 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.
Duplicated block (11 lines × 2) projects/generic-host/generic-host-1/Program.cs:26— projects/generic-host/generic-host-1/Program.cs:26-36 | projects/generic-host/generic-host-2/Program.cs:26-36 — `projects/generic-host/generic-host-1/Program.cs` and `projects/generic-host/generic-host-2/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 11 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (11 lines × 2) projects/generic-host/generic-host-configure-app/Program.cs:38— projects/generic-host/generic-host-configure-app/Program.cs:38-48 | projects/generic-host/generic-host-configure-host/Program.cs:37-47 — `projects/generic-host/generic-host-configure-app/Program.cs` and `projects/generic-host/generic-host-configure-host/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 11 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×2
Disposable created and abandoned in the method that made it projects/elsa/composite-activity/Program.cs:40— `random` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 40). Every use of it in `GetRandom` 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 random = …;`), 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 projects/elsa/workflow-3/Program.cs:21— `random` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 21). Every use of it in `Build` 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 random = …;`), which releases it at the end of the scope on every path including a throw.
AC4 · Keyboard semantics· Anchor without href · ×1
Anchor without href projects/yarp/basic-demo/Yarp.Demo.FrontEnd/wwwroot/index.html:20— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — 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 528 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.
Stateful singleton: Accumulator projects/grpc/grpc-17/Program.cs:75— `Accumulator` is a singleton (one shared instance) but mutates instance state outside any lock (Total; e.g. `Total` at line 79).
Build failed — The target solution did not build cleanly (errors: 2), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS1022: Type or namespace definition, or end-of-file expected.
StringUtils.ToSnakeCase (cognitive 27) projects/json/json-7/Program.cs:50— StringUtils.ToSnakeCase has cognitive complexity 27 (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.
StringUtils.ToSnakeCaseNewtonsoft (cognitive 27) projects/json/json-8/Program.cs:29— StringUtils.ToSnakeCaseNewtonsoft has cognitive complexity 27 (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.
Change coupling: REDACTED ↔ REDACTED projects/rewrite/rewrite-1/Program.cs:1— `projects/rewrite/rewrite-1/Program.cs` and `projects/rewrite/rewrite-2/Program.cs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `58a346b9` Fix warnings; `91556f0e` Upgrade to .NET 6; `337a3238` Move off src — run `git show` on any of them.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) projects/datastar/backend-patch-signals-2/Program.cs:12— projects/datastar/backend-patch-signals-2/Program.cs:12-22 | projects/datastar/backend-patch-signals-3/Program.cs:12-23 | projects/datastar/backend-patch-signals-4/Program.cs:12-27 | projects/datastar/data-indicator/Program.cs:12-22 | projects/datastar/data-on-signal-patch-filter/Program.cs:12-22 | projects/datastar/data-on-signal-patch/Program.cs:12-22 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (13 lines × 2) projects/markdown-server-middleware/Program.cs:43— projects/markdown-server-middleware/Program.cs:43-55 | projects/markdown-server-middleware/Program.cs:65-77 — 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 (11 lines × 4) projects/blazor-ssr/RazorFormHandlingFour/Pages/Index.razor:84— projects/blazor-ssr/RazorFormHandlingFour/Pages/Index.razor:84-94 | projects/blazor-ssr/RazorFormHandlingOne/Pages/Index.razor:66-76 | projects/blazor-ssr/RazorFormHandlingThree/Pages/Index.razor:86-96 | projects/blazor-ssr/RazorFormHandlingTwo/Pages/Index.razor:65-75 — before extracting anything, compare `projects/blazor-ssr/RazorFormHandlingFour/Pages/Index.razor` and `projects/blazor-ssr/RazorFormHandlingOne/Pages/Index.razor` as WHOLE FILES: 88% 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. 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 `projects/blazor-ssr/RazorFormHandlingFour/Pages/Index.razor:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) projects/health-check/health-check-5/Program.cs:73— projects/health-check/health-check-5/Program.cs:73-81 | projects/health-check/health-check-6/Program.cs:72-80 — 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 `projects/health-check/health-check-5/Program.cs:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 6) projects/datastar/backend-patch-signals-2/Program.cs:12— projects/datastar/backend-patch-signals-2/Program.cs:12-18 | projects/datastar/backend-patch-signals-3/Program.cs:12-18 | projects/datastar/backend-patch-signals-4/Program.cs:12-18 | projects/datastar/data-indicator/Program.cs:12-18 | projects/datastar/data-on-signal-patch-filter/Program.cs:12-18 | projects/datastar/data-on-signal-patch/Program.cs:12-18 — `projects/datastar/backend-patch-signals-2/Program.cs` and `projects/datastar/backend-patch-signals-3/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 15 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `projects/datastar/backend-patch-signals-2/Program.cs:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `projects/datastar/backend-patch-signals-3/Program.cs:21` calls `Contains` and `projects/datastar/backend-patch-signals-2/Program.cs:21` 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 (7 lines × 2) projects/blazor-ss/Localization-3/Program.cs:62— projects/blazor-ss/Localization-3/Program.cs:62-68 | projects/blazor-ss/Localization-4/Program.cs:59-65 — `projects/blazor-ss/Localization-3/Program.cs` and `projects/blazor-ss/Localization-4/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 7 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (17 lines × 2) projects/mvc/localization/mvc-localization-10/Program.cs:66— projects/mvc/localization/mvc-localization-10/Program.cs:66-83 | projects/mvc/localization/mvc-localization-9/Program.cs:56-72 — 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 `projects/mvc/localization/mvc-localization-10/Program.cs:66` 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. 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 (25 lines × 2) projects/mvc/tag-helper/tag-helper-3/Program.cs:25— projects/mvc/tag-helper/tag-helper-3/Program.cs:25-49 | projects/mvc/tag-helper/tag-helper-4/Program.cs:23-73 — `projects/mvc/tag-helper/tag-helper-3/Program.cs` and `projects/mvc/tag-helper/tag-helper-4/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `projects/mvc/tag-helper/tag-helper-3/Program.cs:25` 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. 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 (6 lines × 3) projects/security/dataprotection/azure-keyvault-storage-blob-key-store/src/Program.cs:13— projects/security/dataprotection/azure-keyvault-storage-blob-key-store/src/Program.cs:13-18 | projects/security/dataprotection/azure-storage-blob-key-store/src/Program.cs:13-18 | projects/security/dataprotection/ef-key-store/src/Program.cs:13-18 — 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.
Duplicated block (8 lines × 5) projects/unpoly/up-flashes/Program.cs:58— projects/unpoly/up-flashes/Program.cs:58-65 | projects/unpoly/up-hungry/Program.cs:55-62 | projects/unpoly/up-poll/Program.cs:39-46 | projects/unpoly/up-target-2/Program.cs:61-68 | projects/unpoly/up-target/Program.cs:66-73 — `projects/unpoly/up-flashes/Program.cs` and `projects/unpoly/up-hungry/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 8 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) projects/minimal-api/map-group-1/Program.cs:30— projects/minimal-api/map-group-1/Program.cs:30-35 | projects/minimal-api/map-group-2/Program.cs:40-45 — `projects/minimal-api/map-group-1/Program.cs` and `projects/minimal-api/map-group-2/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 6 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
Unfinished stub — throws NotImplementedException projects/health-check/health-check-3/Program.cs:18— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException projects/health-check/health-check-3/Program.cs:18— `CheckHealthAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Fake-async — async method never awaits projects/mvc/view-component/view-component-3/Views/Shared/Components/HelloWorld/HelloWorld.cs:13— `InvokeAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Third-party script without Subresource Integrity projects/security/dataprotection/azure-keyvault-storage-blob-key-store/src/Pages/Shared/_Layout.cshtml:32— `https://cdn.jsdelivr.net/npm/jquery@3.6.0/dist/jquery.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 28 such include(s) across the repository's markup.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Blocking `StreamReader.ReadToEnd` inside an `async` method projects/file-provider/file-provider-custom/Program.cs:17— `StreamReader.ReadToEnd` blocks the thread on I/O while `StreamReader.ReadToEndAsync` exists to wait without one — inside a method that is already `async`, await the twin.
Swallowed exception (caught, then discarded) projects/grpc/grpc-4/client/Program.cs:34— `catch (System.OverflowException)` 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.
Unresolved JS interop binding projects/blazor-ss/ChatR/Services/NotificationService.cs:49— `Broadcast` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 500 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `Broadcast`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No security response headers detected REDACTED:7— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected REDACTED:5— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected REDACTED:9— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/authentication/authentication-4/Program.cs:3— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/authentication/authentication-5/Program.cs:4— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/ChatR/Program.cs:4— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/ComponentEvents-2/Program.cs:1— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/ComponentEvents/Program.cs:4— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/DependencyInjection/Program.cs:3— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/HelloWorld/Program.cs:1— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/JsIntegration/Program.cs:1— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/Layout/Program.cs:1— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/Localization-2/Program.cs:4— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/Localization-3/Program.cs:8— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/Localization-4/Program.cs:8— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/Localization/Program.cs:4— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/RenderTreeBuilder/Program.cs:17— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/RssReader-2/Program.cs:3— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/RssReader/Program.cs:3— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/StartingVariation/Program.cs:6— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ss/WallOfCounters/Program.cs:1— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ssr/RazorComponentEight/RazorComponentEight/Program.cs:1— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ssr/RazorComponentEleven/Program.cs:1— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected projects/blazor-ssr/RazorComponentFive/Program.cs:4— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
Interpolated log message defeats structured logging projects/polly/rate-limiter-http-client/Pages/Index.cshtml.cs:37— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging projects/polly/rate-limiter-http-client/Pages/Index.cshtml.cs:42— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging projects/orleans/orleans-3/Program.cs:80— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging projects/orleans/orleans-4/Program.cs:102— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging projects/orleans/orleans-4/Program.cs:107— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging projects/orleans/orleans-4/Program.cs:119— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging projects/orleans/orleans-4/Program.cs:133— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:101— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:153— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:155— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:183— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:185— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:662— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:676— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:682— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:692— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:715— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:721— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:737— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging projects/blazor-ss/ChatR/NotificationHub.cs:26— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging projects/blazor-ss/ChatR/NotificationHub.cs:32— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging projects/caching/caching-3/Program.cs:31— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging projects/caching/caching-4/Program.cs:39— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging projects/caching/caching-4/Program.cs:54— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging projects/file-provider/serve-static-files-8/Program.cs:8— 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.
README/code drift README.md:1— README claims a .NET Aspire samples repo exists but there is no aspire-samples project or directory — searched for: `aspire-samples`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
README/code drift projects/configurations/README.md:46— projects/configurations/README.md links to `/project/configurations/configuration-bind-option`, but `project/configurations/configuration-bind-option` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift projects/configurations/README.md:52— projects/configurations/README.md links to `/project/configurations/configuration-IOption`, but `project/configurations/configuration-IOption` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift projects/datastar/README.md:37— projects/datastar/README.md links to `data-compute`, but `projects/datastar/data-compute` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift projects/mini/README.md:3— projects/mini/README.md names .NET 5, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift projects/blazor-ss/ComponentEvents-2/README.md:3— projects/blazor-ss/ComponentEvents-2/README.md links to `ComponentEvents`, but `projects/blazor-ss/ComponentEvents-2/ComponentEvents` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Duplicated predicate projects/json/json-7/Program.cs:78— `!char.IsUpper(nextChar) && nextChar != '_'` appears character-identically in 2 files — projects/json/json-7/Program.cs, projects/json/json-8/Program.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 projects/file-provider/serve-static-files-4/Program.cs:29— `c.Name.Contains(".png") || c.Name.Contains(".jpg")` appears character-identically in 2 files — projects/file-provider/serve-static-files-4/Program.cs, projects/file-provider/serve-static-files-5/Program.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 projects/sse/Program.cs:11— `true && !cancellationToken.IsCancellationRequested` appears character-identically in 4 files — projects/net10/sse-2/Program.cs, projects/net10/sse-3/Program.cs, projects/net10/sse-4/Program.cs, projects/sse/Program.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.
Documentation: no project overview projects/authentication/readme.md— The Authentication section lists five sample paths but does not explain what authentication is and which projects use it. Add an overview paragraph describing authentication (JWT, cookie, mixed) and where each sample lives.
Documentation: no project overview projects/grpc/README.md— The README is a directory listing pointing to subdirectories (e.g. Unary, Server Streaming) but gives no description of what gRPC samples show or how they relate to the project. Add an overview paragraph explaining that this directory hosts gRPC samples showing request/response, streaming, and oneof types for Protocol Buffers.
Thin analysable surface across projects: ClassLibrary projects/mvc/localization/mvc-localization-7/ProjectWithResources/ClassLibrary.csproj— 1 project(s) carry only a thin slice of real code; `ClassLibrary` has 12 significant line(s). The mean analysable-surface weight is 100 %; this project lowers Solution Shape by about 0.01 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
Inconsistent naming for greeting-related concepts: 'MorningGreeting' and 'EveningGreeting' use a specific time qualifier as a prefix, while 'Greeting' is a generic base concept. Additionally, 'Greeting' exposes a method 'Greet()' (verb) while the others expose a 'Message' property (noun). This suggests 'Greeting' might be a base class or interface, but the naming convention for the specific instances (TimeQualifier + Greeting) differs from the generic concept (Greeting). — Standardize on a consistent pattern for greeting types, e.g., 'MorningGreeting', 'EveningGreeting', and 'GenericGreeting' or 'BaseGreeting', and ensure their members follow the same grammatical role (e.g., all return a 'Message' property or all have a 'Say()' method). (symbols: Property: public string MorningGreeting.Message, Property: public string EveningGreeting.Message, Property: public string Greeting.Greet())
Inconsistent tense usage in lifecycle event names: 'OnStopping' (present participle) vs 'OnStopped' (past participle). While this may reflect different stages of the lifecycle, consistency in tense (e.g., 'OnStart'/'OnStop' or 'Starting'/'Stopped') is preferred for clarity. — Align the tense of lifecycle event names, e.g., 'OnStopping' and 'OnStopped' could be 'OnStop' and 'OnStopped', or 'Starting' and 'Stopped' depending on the exact semantics. (symbols: Type: public HelloWorldService, Method: public void HelloWorldService.OnStopping(), Method: private void HelloWorldService.OnStopped())
D21 · Naming Consistency· Use of numeric suffix '2' in type name 'Message2' suggests a lack of descriptive naming for a distinct concept. 'Message' and 'Message2' are likely related but distinct types, and the numeric suffix is not descriptive. · ×1
Use of numeric suffix '2' in type name 'Message2' suggests a lack of descriptive naming for a distinct concept. 'Message' and 'Message2' are likely related but distinct types, and the numeric suffix is not descriptive. — Rename 'Message2' to a descriptive name that reflects its specific purpose or difference from 'Message' (e.g., 'ExtendedMessage', 'SecondaryMessage', or 'NotificationMessage'). (symbols: Type: public Component3.Pages.Components.Message, Type: public Component3.Pages.Components.Message2)
redundant comment REDACTED:44— "read more https://docs.microsoft.com/en-us/aspnet/core/security/authentication/cookie?view=aspnetcore-6.0" — ignore - duplicate comment on the same line, not a WHY
GD1 · Unfinished & placeholder code· Placeholder literal left in code · ×1
Placeholder literal left in code projects/net11/async-validation/Program.cs:4— A placeholder string ("<!DOCTYPE html>
<html lang="en">
<head>
…") is still in shipped code — typical of generated boilerplate that was never filled in.
IC1 · Incompleteness & stubs· Placeholder data left in code · ×1
Placeholder data left in code projects/net11/async-validation/Program.cs:101— A placeholder e-mail address ("taken@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Inconsistent root namespaces — Only 17/565 projects share a common root namespace — the code's module identity is inconsistent.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 26/26 types (100%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
P10 · Library API & versioning· No explicit versioning · ×1
No explicit versioning — No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
Logging is not universal — Only 41/500 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 500, 497 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 26/87 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.
Nullable reference types not enabled everywhere — 33/564 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~2.4 `!` suppressions per 1k syntax nodes — 39 suppression(s) across the 16198 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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 82 file(s) — `REDACTED`, `REDACTED`, `REDACTED`, `projects/blazor-wasm/ComponentTwentySeven/Program.cs`, `projects/datastar/backend-patch-signals-2/Program.cs`, … (+77 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1682f-e371-7b13-bbf3-bd333cde74ee · 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 — 18 field(s) across 3 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 94 · Warnings: 257 · Recommendations: 99 · Info: 259 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 09:55 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.