Public report — netcorepal-cloud-framework, published 3 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
201findings with an exact file:lineof 253 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
70/108dimensions across the health lenses18941 LoC · 245 projects — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
netcorepal/netcorepal-cloud-framework carries serious risk (44%). Several issues below can materially affect reliability, security, or the cost of change and warrant near-term attention.
It is strongest in Domain Modelling (100%) — the domain model is expressive and well-guarded. Event-Driven (100%) is solid too.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Accessibility (33%) — it raises ongoing delivery and operational cost. Readiness (42%) is the next concern — operating, monitoring and recovering the system safely is harder.
Leadership focus, highest impact first: Make custom controls keyboard-operable (role + tabindex + key handler) (Keyboard semantics); accessibility in the test suite you already have (A11y enforcement); Give every control a programmatic label (a <label for> /… (Forms & labels).
For scale: Small (~18,941 production lines); rebuilding it from scratch would take roughly ~0.8 person-years (~1–2 engineers). Approximate, ±~30%.
It builds on a genuinely strong Domain Modelling foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
Business logic 17%Plumbing 27%Tests 42%Generated 7%Analyzers 7%
New since the last scan (100+)
201 finding(s) are new versus the previous scan (2026-07-29) — surfaced by this scheduled scan itself, no pull request required. Showing the first 100; the full set is in the report.
D5 · Off the main sequence: NetCorePal.Extensions.CodeAnalysis(net8.0)
D5 · Off the main sequence: NetCorePal.Extensions.Dto(net8.0)
D5 · Off the main sequence: NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity(net8.0)
D5 · Off the main sequence: NetCorePal.Context.Shared(net8.0)
D8 · Coverage not measured — test suite did not build
D10 · No assertions (empty test): HttpClientDiagnosticContextProcessor_Tests test/NetCorePal.Context.AspNetCore.UnitTests/HttpClientDiagnosticContextProcessorTests.cs
D10 · No assertions: Test test/NetCorePal.Extensions.Domain.Abstractions.UnitTests/MediatorTest.cs
D10 · No assertions: AsyncTest test/NetCorePal.Web.UnitTests/AsyncTests.cs
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
This codebase represents roughly ~0.8 person-years of build effort (about ~€110,000 to rebuild). Its weakest lens is Accessibility at 33% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Very high (×2.0) — service/app, DDD/clean architecture, CQRS, domain model, event-driven integration, high decision density × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
Value concentrated against a weak lens · High · Value at risk
This is a Small asset (~0.8 person-years to rebuild), and its weakest lens is Accessibility at 33%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Accessibility first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture — module dependency matrix
73 modules, 63 dependencies — 2 dependency cycles, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
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
A06:2021 — Vulnerable & Outdated Components
33
High / Critical
A03:2021 — Injection
10
High / Critical
Roadmap
Begin by making custom controls keyboard-operable and ensuring anchors have valid links. Next, enforce accessibility in the test suite by asserting invariants over rendered HTML and gating those tests in CI to prevent regressions. Then, ensure every form control and button has a proper programmatic label rather than relying on placeholders. Finally, improve page structure by adding language attributes, titles, and landmarks, while also addressing visual safety by maintaining focus styles, respecting reduced motion preferences, and fixing color contrast.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
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.
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
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.
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. 68 of 70 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — 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 — 70 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, 201 of 253 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.
D24 Comment Value — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
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 (jscpd) — 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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality 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.
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.
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 the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
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 clean result is "no unlabelled native 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.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D19, D20, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These 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.
16 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Program.GenerateVisualization at 58. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being NewtonsoftDeletedTimeJsonConverter.ReadJson at 25 — they are counted neither in the figure above nor in this dimension's score.
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 Program.GenerateVisualization (cyclomatic 58) finding(s) in Cyclomatic Complexity — start with Program.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 AggregateRelationMermaidVisualizer.GenerateMermaid (cyclomatic 39) finding(s) in Cyclomatic Complexity — start with AggregateRelationMermaidVisualizer.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Program.AddSnapshot (cyclomatic 37) finding(s) in Cyclomatic Complexity — start with Program.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 24 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 Program.GenerateVisualization (cognitive 97) finding(s) in Cognitive Complexity — start with Program.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 CommandHandlerMetadataGenerator.Initialize (cognitive 59) finding(s) in Cognitive Complexity — start with CommandHandlerMetadataGenerator.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 EndpointMetadataGenerator.Initialize (cognitive 58) finding(s) in Cognitive Complexity — start with EndpointMetadataGenerator.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.5 / 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.
+ 21 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with Program.cs, VisualizationMarkdownBuilder.cs, MongoDBNetCorePalDataStorage.cs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 4 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with CodeFlowAnalysisHelper.cs (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Program.cs, CodeFlowAnalysisHelper.cs, MongoDBNetCorePalDataStorage.cs. — One of this dimension's main actionable groups (3 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.9 / 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.
1207 test methods: 1207 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 Quality9.8 / 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.
2 skipped (2 with a documented reason), 4 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 401 tests.
No assertions (empty test): HttpClientDiagnosticContextProcessor_Teststest/NetCorePal.Context.AspNetCore.UnitTests/HttpClientDiagnosticContextProcessorTests.cs:5
No assertions: Test · ×3test/NetCorePal.Extensions.Domain.Abstractions.UnitTests/MediatorTest.cs:8
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.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 dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
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.
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: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
9 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/NetCorePal.Extensions.CodeAnalysis/VisualizationMarkdownBuilder.cs.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D17 · Explicit Debt8.5 / 10Strong✓ Tool-verified
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with NetCorePal.Web.csproj, Directory.Build.props. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 20 BarePragmaDisable finding(s) in Explicit Debt — start with NetCorePalStorageMockHost.cs (4), ServiceCollectionExtension.cs (2), ContainerJobActivator.cs (2). — One of this dimension's main actionable groups (20 warning-level).
Resolve the 3 CommentedOutCode finding(s) in Explicit Debt — start with Employee.cs, NetCorePalDataStorageDbContext.cs, ProgramTests.cs. — One of this dimension's main actionable groups (3 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
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 README is a strong tactical framework description plus a dedicated CAP MongoDB provider README. The main document is a single English README with an outline of DeepWiki, 'How to Use', and the full roadmap (core features, templates, usage, Roadmap, components, code analysis), but it is clipped mid-usage section for the full body. The CAP MongoDB package README is complete and well-structured.
The CAP MongoDB README is a provider-specific package with an overview and usage example that is clipped mid-usage.src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/README.md
Resolve the 1 The CAP MongoDB README is a provider-specific package with an overview… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
1 naming inconsistencies across 200 sampled symbols.
The name 'PublishedMessage' is used for two distinct concepts: a persistence entity (CAP message) and a routing route. This creates ambiguity between the domain event/message and the routing mechanism.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
87 % of calls cross a namespace and 3 % go through an interface, but 97 % 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: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
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).
High: github-actions-mutable-action-tag · ×10.github/workflows/docs.yml:12detected by semgrep finding
What to do
Resolve the 10 High finding(s) in Static Analysis (SAST) — start with docs.yml (3), docker-compose.yml (3), dotnet.yml (2). — One of this dimension's main actionable groups (10 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
2 of 74 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/NetCorePal.OpenTelemetry.Diagnostics/DiagnosticListener.cs.
Further orphaned files (smaller)
✓ On the Gold path — maintain.
Detailed fixes: d34_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; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PR-triggered workflow without a permissions block finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Secret passed as a command-line argument finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels4.3 / 10Weak✓ 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, 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.
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. — visualization-template.html:512
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.9 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — visualization-template.html:2
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — visualization-template.html:517
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 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.
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — visualization-template.html:530, visualization-template.html:537
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
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.
`.nav-item.active` sets color: white on background-color: #3498db — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — visualization-template.html:10
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.
No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge.
What to do
Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
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.
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 — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
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.
`InMemoryJwtSettingStore` is a singleton (one shared instance) but mutates instance state outside any lock (_secretKeySettings; e.g. `_secretKeySettings` at line 15). — InMemoryJwtSettingStore.cs:3
`ConsulWorkerIdGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (IsHealth, _sessionId; e.g. `IsHealth` at line 102). — ConsulWorkerIdGenerator.cs:10
`RedisWorkerIdGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (IsHealth; e.g. `IsHealth` at line 93). — RedisWorkerIdGenerator.cs:9
`DefaultServiceDiscoveryClient` is a singleton (one shared instance) but mutates instance state outside any lock (_changeToken; e.g. `_changeToken` at line 25). — DefaultServiceDiscoveryClient.cs:6
`K8SServiceDiscoveryProvider` is a singleton (one shared instance) but mutates instance state outside any lock (_serviceDescriptors, _lastResourceVersion, Clusters, _cts, _token; e.g. `_serviceDescriptors` at line 74). — K8SServiceDiscoveryProvider.cs:14
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 dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
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 member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
C1 · Data Protection3.5 / 10Weak✓ 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.
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
Do you agree with this assessment?
C3 · Audit Trail7.5 / 10Strong✓ Tool-verified
Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.
An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
What to do
Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
Do you agree with this assessment?
C4 · Data Retention10.0 / 10Exemplary✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
Other · Domain Modelling — Whether entities protect their state (private/init-only setters) instead of exposing public setters that bypass invariants. Softened when a rehydration framework (Marten/EF) is present.
Method: Roslyn (DDD-gated): public setters on entities detected; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
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. (×3) — NetCorePalVirtualDataSourceRoute.cs:50, PublishedMessageVirtualDataSourceRoute.cs:25, NetCorePalTenantVirtualDataSourceRoute.cs:38
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
`AutoDiscoverProjects` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Program.cs:616
`AddDataSourceName` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×3) — NetCorePalVirtualDataSourceRoute.cs:48, PublishedMessageVirtualDataSourceRoute.cs:23, NetCorePalTenantVirtualDataSourceRoute.cs:36
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×4) — AppDbContextBaseCapDataStorageSourceGenerator.cs:75, ITenantShardingDatabaseProvider.cs:18, ITenantShardingDatabaseProvider.cs:21, …
A test is skipped ("Integration test - requires building projects") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — ProgramTests.cs:76, ProgramTests.cs:111
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — 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 81 of 85 project(s) that lack one — worth up to 1.9 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents 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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
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.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ 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. Exhaustive, deterministic.
1172/1275 types (92%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
What to do
Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
Do you agree with this assessment?
P2 · Observability6.9 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 10/33 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 33, 1 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
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 (it analyses VB.NET too), or a security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Roslyn scan: Polly resilience markers (Retry, CircuitBreaker, Timeout) on outbound HTTP invocations. Computed per type, deterministic.
Outbound HTTP calls were found with no timeout or retry policy around them. This codebase ships libraries/tools rather than a service it operates, so the failure lands differently: an unbounded call hangs the caller's process — a build step, a CLI run, a UI thread — with no way out.
What to do
Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
Readiness · Performance — Whether the library 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 — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
No benchmark suite was found. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
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.
Raise allocation-aware density on the hot paths — currently 41 use(s) across 22,831 production line(s) (~1.8/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code keeps its host responsive — a library awaits with ConfigureAwait(false) (so it never captures and stalls the host's context) and avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock.
Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a library with ≥5 awaits — the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock in a consumer with a synchronization context.
Only 14/334 awaits use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult() in library code.
In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. — K8SServiceDiscoveryProvider.cs:66
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.
Only 69/97 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. (×4) — KnownExceptionHandleMiddleware.cs:32, Program.cs:246, Program.cs:773, …
No CancellationToken parameter — this work can't be stopped early once started. (×21) — Program.cs:616, Program.cs:1054, EnvIntegrationEventHandlerFilter.cs:83, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
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.
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. Deterministic.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.9 `!` suppressions per 1k syntax nodes — 81 suppression(s) across the 95099 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 12 of 55 WCAG 2.2 Level A/AA success criteria (22%; ≈24% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 43 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.
Not included — 38 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
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.
D14 License Compliance — license scan produced no result — the tool ran but its JSON output could not be parsed; the offline NuGet fallback resolved nothing
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Bounded contexts not declared
D24 Comment Value — LLM evaluation failed
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — Data compliance (PII/GDPR) was not assessed in this scan — no ruleset is currently available for it. This says nothing about how this repository handles personal data, in either direction.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
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.
D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
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 — test suite did not build
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
ED3 Event naming — no domain or integration events detected — event-naming check not applicable
ED4 Outbox / dual-write — no persistence writes or publishes observed in handlers — atomicity not assessable
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
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) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
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.
High CVE: System.Security.Cryptography.Xml 9.0.0 — System.Security.Cryptography.Xml 9.0.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 9.0.0 — System.Security.Cryptography.Xml 9.0.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 9.0.0 — System.Security.Cryptography.Xml 9.0.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 9.0.0 — System.Security.Cryptography.Xml 9.0.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 9.0.0 — System.Security.Cryptography.Xml 9.0.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 9.0.0 — System.Security.Cryptography.Xml 9.0.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 9.0.0 — System.Security.Cryptography.Xml 9.0.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 9.0.0 — System.Security.Cryptography.Xml 9.0.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Snappier 1.0.0 — Snappier 1.0.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: SQLitePCLRaw.lib.e_sqlite3 2.1.11 — SQLitePCLRaw.lib.e_sqlite3 2.1.11 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: SQLitePCLRaw.lib.e_sqlite3 2.1.6 — SQLitePCLRaw.lib.e_sqlite3 2.1.6 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: SQLitePCLRaw.lib.e_sqlite3 2.1.10 — SQLitePCLRaw.lib.e_sqlite3 2.1.10 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 10.0.0 — System.Security.Cryptography.Xml 10.0.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 10.0.0 — System.Security.Cryptography.Xml 10.0.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 10.0.0 — System.Security.Cryptography.Xml 10.0.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 10.0.0 — System.Security.Cryptography.Xml 10.0.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 10.0.0 — System.Security.Cryptography.Xml 10.0.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 10.0.0 — System.Security.Cryptography.Xml 10.0.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 10.0.0 — System.Security.Cryptography.Xml 10.0.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 10.0.0 — System.Security.Cryptography.Xml 10.0.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 8.0.2 — System.Security.Cryptography.Xml 8.0.2 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 8.0.2 — System.Security.Cryptography.Xml 8.0.2 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 8.0.2 — System.Security.Cryptography.Xml 8.0.2 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 8.0.2 — System.Security.Cryptography.Xml 8.0.2 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Security.Cryptography.Xml 8.0.2 — System.Security.Cryptography.Xml 8.0.2 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High: github-actions-mutable-action-tag .github/workflows/docs.yml:12— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v3`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/docs.yml:13— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-python@<40-character SHA>`. This step references `actions/setup-python@v4`; resolve the SHA it points at today with `gh api repos/actions/setup-python/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/docs.yml:17— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/cache@<40-character SHA>`. This step references `actions/cache@v3`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/dotnet.yml:16— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v3`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/dotnet.yml:18— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/release.yml:11— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v3`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/release.yml:13— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v5 --jq .sha`.
High: privileged-service docker/docker-compose.yml:97— Service 'gaussdb' is running in privileged mode. This grants the container the equivalent of root capabilities on the host machine. This can lead to container escapes, privilege escalation, and other security concerns. Remove the 'privileged' key to disable this capability.
High: privileged-service docker/docker-compose.yml:112— Service 'kingbasees' is running in privileged mode. This grants the container the equivalent of root capabilities on the host machine. This can lead to container escapes, privilege escalation, and other security concerns. Remove the 'privileged' key to disable this capability.
High: privileged-service docker/docker-compose.yml:122— Service 'dmdb' is running in privileged mode. This grants the container the equivalent of root capabilities on the host machine. This can lead to container escapes, privilege escalation, and other security concerns. Remove the 'privileged' key to disable this capability.
NoWarnInCsproj test/NetCorePal.Web/NetCorePal.Web.csproj:12— CS1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:19— CS1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
D10 · Test Quality· No assertions (empty test) · ×1
No assertions (empty test): HttpClientDiagnosticContextProcessor_Tests test/NetCorePal.Context.AspNetCore.UnitTests/HttpClientDiagnosticContextProcessorTests.cs:5— Test method has an empty body — it asserts nothing and exercises no code.
BarePragmaDisable src/NetCorePal.Extensions.AspNetCore/CommandLocks/CommandLockBehavior.cs:13— #pragma warning disable S3604 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.AspNetCore/CommandLocks/CommandLockFailedException.cs:4— #pragma warning disable S3925 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.Snowflake/WorkerIdConflictException.cs:9— #pragma warning disable S3925 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.AspNetCore/ServiceCollectionExtension.cs:126— #pragma warning disable S1133 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.AspNetCore/ServiceCollectionExtension.cs:155— #pragma warning disable S1133 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.Hangfire/ContainerJobActivator.cs:23— #pragma warning disable S1133 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.DistributedTransactions.Abstractions/ServiceCollectionExtensions.cs:61— #pragma warning disable S112 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.Domain.Abstractions/EntityIdTypeConverter.cs:58— #pragma warning disable S112 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.Snowflake.Consul/ConsulWorkerIdGenerator.cs:75— #pragma warning disable S112 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.Snowflake.Redis/RedisWorkerIdGenerator.cs:54— #pragma warning disable S112 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.DistributedTransactions.CAP/CapTransactionUnitOfWork.cs:8— #pragma warning disable S3881 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.DistributedTransactions.CAP/NetCorePalCapEFDbTransaction.cs:8— #pragma warning disable S3881 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.Domain.Abstractions/Entity.cs:82— #pragma warning disable S3249 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.Hangfire/ContainerJobActivator.cs:9— #pragma warning disable S2933 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable src/NetCorePal.Extensions.Repository.EntityFrameworkCore/Behaviors/CommandUnitOfWorkBehavior.cs:11— #pragma warning disable S2743 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable test/NetCorePal.Extensions.DistributedTransactions.CAP.DMDB.UnitTests/NetCorePalStorageMockHost.cs:62— #pragma warning disable CS4014 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable test/NetCorePal.Extensions.DistributedTransactions.CAP.GaussDB.UnitTests/NetCorePalStorageMockHost.cs:60— #pragma warning disable CS4014 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable test/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB.UnitTests/MongoDBNetCorePalDataStorageTests.cs:69— #pragma warning disable CS4014 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable test/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB.UnitTests/NetCorePalStorageMockHost.cs:61— #pragma warning disable CS4014 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
BarePragmaDisable test/NetCorePal.Extensions.DistributedTransactions.CAP.Sqlite.UnitTests/NetCorePalStorageMockHost.cs:56— #pragma warning disable CS4014 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.
Duplicated block (13 lines × 2) src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:632— src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:632-644 | src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:664-676 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:632` it begins part-way through the construct above it, 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 × 2) src/NetCorePal.Extensions.CodeAnalysis/VisualizationMarkdownBuilder.cs:264— src/NetCorePal.Extensions.CodeAnalysis/VisualizationMarkdownBuilder.cs:264-276 | src/NetCorePal.Extensions.CodeAnalysis/VisualizationMarkdownBuilder.cs:286-298 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis/VisualizationMarkdownBuilder.cs:264` it begins part-way through the construct above it, 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 × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:215— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:215-227 | src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:239-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:215` it begins part-way through the construct above it, 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 × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:76— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:76-88 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalMonitoringApi.cs:76-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:76` it begins part-way through the construct above it, 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 × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.PostgreSql/EntityTypeConfigurations/PublishedMessageConfiguration.cs:21— src/NetCorePal.Extensions.DistributedTransactions.CAP.PostgreSql/EntityTypeConfigurations/PublishedMessageConfiguration.cs:21-33 | src/NetCorePal.Extensions.DistributedTransactions.CAP.SqlServer/EntityTypeConfigurations/PublishedMessageConfiguration.cs:20-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.SourceGenerators/CapIntegrationConvertDomainEventHandlerSourceGenerator.cs:13— src/NetCorePal.Extensions.DistributedTransactions.CAP.SourceGenerators/CapIntegrationConvertDomainEventHandlerSourceGenerator.cs:13-26 | src/NetCorePal.Extensions.DistributedTransactions.CAP.SourceGenerators/CapSubscriberSourceGenerator.cs:13-25 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.SourceGenerators/CapIntegrationConvertDomainEventHandlerSourceGenerator.cs:13` 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 × 2) src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityDbContextBase.cs:67— src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityDbContextBase.cs:67-79 | src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityUserContextBase.cs:63-75 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityDbContextBase.cs:67` it begins part-way through the construct above it, 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.
Medium CVE: OpenTelemetry.Api 1.9.0 — OpenTelemetry.Api 1.9.0 (transitive) has a Medium advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: SharpCompress 0.30.1 — SharpCompress 0.30.1 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: OpenTelemetry.Api 1.12.0 — OpenTelemetry.Api 1.12.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: OpenTelemetry.Exporter.OpenTelemetryProtocol 1.9.0 — OpenTelemetry.Exporter.OpenTelemetryProtocol 1.9.0 (transitive) has a Medium advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Duplicated block (6 lines × 2) src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:347— src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:347-352 | src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:376-381 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:347` 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 (6 lines × 2) src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:436— src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:436-441 | src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:466-471 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:436` 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 (6 lines × 2) src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:630— src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:630-635 | src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:660-665 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:630` 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 (6 lines × 2) src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:689— src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:689-694 | src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:719-724 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:689` 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.
Off the main sequence: NetCorePal.Extensions.CodeAnalysis(net8.0) — NetCorePal.Extensions.CodeAnalysis(net8.0): abstractness 0.03, instability 0.00, distance 0.97 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: NetCorePal.Extensions.Dto(net8.0) — NetCorePal.Extensions.Dto(net8.0): abstractness 0.13, instability 0.00, distance 0.88 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity(net8.0) — NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity(net8.0): abstractness 0.86, instability 1.00, distance 0.86 — zone of uselessness — abstract and unstable, so it's likely unused.
Off the main sequence: NetCorePal.Context.Shared(net8.0) — NetCorePal.Context.Shared(net8.0): abstractness 0.00, instability 0.25, distance 0.75 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
No assertions: Test test/NetCorePal.Extensions.Domain.Abstractions.UnitTests/MediatorTest.cs:8— Test method exercises code but verifies nothing — add an assertion.
No assertions: AsyncTest test/NetCorePal.Web.UnitTests/AsyncTests.cs:7— Test method exercises code but verifies nothing — add an assertion.
No assertions: GenerateRsaKeysTest test/NetCorePal.Web.UnitTests/JwtTests.cs:9— Test method exercises code but verifies nothing — add an assertion.
Change coupling: AppIdentityDbContextBase.cs ↔ AppIdentityUserContextBase.cs src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityDbContextBase.cs— `src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityDbContextBase.cs` and `src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityUserContextBase.cs` change together 75% of the time (9 of the 12 commits that touched the less-changed of the two, renames followed). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking.
Change coupling: AppDbContextBase.cs ↔ CommandUnitOfWorkBehavior.cs src/NetCorePal.Extensions.Repository.EntityFrameworkCore/AppDbContextBase.cs— `src/NetCorePal.Extensions.Repository.EntityFrameworkCore/AppDbContextBase.cs` and `src/NetCorePal.Extensions.Repository.EntityFrameworkCore/Behaviors/CommandUnitOfWorkBehavior.cs` change together 61% of the time (11 of the 18 commits that touched the less-changed of the two, renames followed). 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.
Change coupling: EntityIdCodeGenerators.cs ↔ MermaidDomainCodeGenerators.cs src/NetCorePal.Extensions.Domain.SourceGenerators/EntityIdCodeGenerators.cs— `src/NetCorePal.Extensions.Domain.SourceGenerators/EntityIdCodeGenerators.cs` and `src/NetCorePal.Extensions.Domain.SourceGenerators/MermaidDomainCodeGenerators.cs` change together 60% of the time (6 of the 10 commits that touched the less-changed of the two, renames followed). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking.
Duplicated block (7 lines × 2) src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:1395— src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:1395-1405 | src/NetCorePal.Extensions.CodeAnalysis/Snapshots/CodeFlowAnalysisSnapshotHelper.cs:333-339 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:1395` 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 (7 lines × 2) src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:567— src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:567-573 | src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:599-605 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:567` 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 (7 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:461— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:461-467 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs:378-384 — before extracting anything, compare `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs` and `src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:461` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:496— src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:496-500 | src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:566-570 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:496` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:525— src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:525-529 | src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:598-602 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:525` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:562— src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:562-566 | src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:594-598 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:562` 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.
TodoComment test/NetCorePal.Extensions.CodeAnalysis.UnitTests/SourceGenerators/CommandHandlerEntityMethodMetadataGeneratorTests.cs:12— // TODO: 补充具体断言 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/NetCorePal.Extensions.CodeAnalysis.UnitTests/SourceGenerators/CommandSenderMetadataGeneratorTests.cs:12— // TODO: 补充具体断言 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (20 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:232— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:232-251 | src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:269-288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:232` it begins part-way through the construct above it, 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 (20 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalMonitoringApi.cs:229— src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalMonitoringApi.cs:229-248 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalMonitoringApi.cs:263-282 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalMonitoringApi.cs:229` it begins part-way through the construct above it, 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 (17 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:124— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:124-140 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs:113-139 — before extracting anything, compare `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs` and `src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:441— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:441-457 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs:358-374 — before extracting anything, compare `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs` and `src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:441` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandSenderMethodMetadataGenerator.cs:14— src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandSenderMethodMetadataGenerator.cs:14-21 | src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/ControllerMethodMetadataGenerator.cs:14-21 | src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/EndpointMetadataGenerator.cs:14-21 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandSenderMethodMetadataGenerator.cs:14` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:382— src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:382-390 | src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:412-419 | src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:472-480 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:382` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:87— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:87-94 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs:82-89 — before extracting anything, compare `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs` and `src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:132— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:132-139 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalMonitoringApi.cs:132-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 3) src/NetCorePal.Extensions.DistributedTransactions.CAP.MySql/EntityTypeConfigurations/PublishedMessageConfiguration.cs:10— src/NetCorePal.Extensions.DistributedTransactions.CAP.MySql/EntityTypeConfigurations/PublishedMessageConfiguration.cs:10-15 | src/NetCorePal.Extensions.DistributedTransactions.CAP.PostgreSql/EntityTypeConfigurations/PublishedMessageConfiguration.cs:12-17 | src/NetCorePal.Extensions.DistributedTransactions.CAP.Sqlite/EntityTypeConfigurations/PublishedMessageConfiguration.cs:10-15 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MySql/EntityTypeConfigurations/PublishedMessageConfiguration.cs:10` 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 (6 lines × 3) src/NetCorePal.Extensions.DistributedTransactions.CAP.MySql/EntityTypeConfigurations/ReceivedMessageConfiguration.cs:9— src/NetCorePal.Extensions.DistributedTransactions.CAP.MySql/EntityTypeConfigurations/ReceivedMessageConfiguration.cs:9-14 | src/NetCorePal.Extensions.DistributedTransactions.CAP.PostgreSql/EntityTypeConfigurations/ReceivedMessageConfiguration.cs:9-14 | src/NetCorePal.Extensions.DistributedTransactions.CAP.Sqlite/EntityTypeConfigurations/ReceivedMessageConfiguration.cs:9-14 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MySql/EntityTypeConfigurations/ReceivedMessageConfiguration.cs:9` 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.
Program.GenerateVisualization (cyclomatic 58) src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:246— Program.GenerateVisualization has cyclomatic complexity 58 (threshold 15). Of this number, 54 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AggregateRelationMermaidVisualizer.GenerateMermaid (cyclomatic 39) src/NetCorePal.Extensions.CodeAnalysis/MermaidVisualizers/AggregateRelationMermaidVisualizer.cs:57— AggregateRelationMermaidVisualizer.GenerateMermaid has cyclomatic complexity 39 (threshold 15). Of this number, 27 points are the body's own statements and 12 belong to 5 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Program.AddSnapshot (cyclomatic 37) src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:773— Program.AddSnapshot has cyclomatic complexity 37 (threshold 15). Of this number, 34 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EntityMetadataGenerator.Initialize (cyclomatic 29) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/EntityMetadataGenerator.cs:14— EntityMetadataGenerator.Initialize has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to one function literal inside it that branches (line 24). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
EndpointMetadataGenerator.Initialize (cyclomatic 26) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/EndpointMetadataGenerator.cs:13— EndpointMetadataGenerator.Initialize has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to one function literal inside it that branches (line 23). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
CommandSenderMethodMetadataGenerator.Initialize (cyclomatic 25) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandSenderMethodMetadataGenerator.cs:13— CommandSenderMethodMetadataGenerator.Initialize has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to one function literal inside it that branches (line 23). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
DiagnosticListener.OnNext (cyclomatic 25) src/NetCorePal.OpenTelemetry.Diagnostics/DiagnosticListener.cs:28— DiagnosticListener.OnNext has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ControllerMethodMetadataGenerator.Initialize (cyclomatic 24) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/ControllerMethodMetadataGenerator.cs:13— ControllerMethodMetadataGenerator.Initialize has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to one function literal inside it that branches (line 23). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ArchitectureOverviewMermaidVisualizer.GenerateMermaid (cyclomatic 22) src/NetCorePal.Extensions.CodeAnalysis/MermaidVisualizers/ArchitectureOverviewMermaidVisualizer.cs:15— ArchitectureOverviewMermaidVisualizer.GenerateMermaid has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
CommandHandlerMetadataGenerator.Initialize (cyclomatic 21) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandHandlerMetadataGenerator.cs:14— CommandHandlerMetadataGenerator.Initialize has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 24, 18, 20). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
IntegrationEventHandlerMetadataGenerator.Initialize (cyclomatic 20) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/IntegrationEventHandlerMetadataGenerator.cs:13— IntegrationEventHandlerMetadataGenerator.Initialize has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 23, 17, 19). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
EntityMethodMetadataGenerator.ProcessMethods (cyclomatic 19) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/EntityMethodMetadataGenerator.cs:42— EntityMethodMetadataGenerator.ProcessMethods has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EntityMethodMetadataGenerator.ProcessConstructors (cyclomatic 19) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/EntityMethodMetadataGenerator.cs:111— EntityMethodMetadataGenerator.ProcessConstructors has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Program.AutoDiscoverProjects (cyclomatic 19) src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:616— Program.AutoDiscoverProjects has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ProcessingFlowMermaidVisualizer.GenerateMermaid (cyclomatic 19) src/NetCorePal.Extensions.CodeAnalysis/MermaidVisualizers/ProcessingFlowMermaidVisualizer.cs:15— ProcessingFlowMermaidVisualizer.GenerateMermaid has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CommandHandlerEntityMethodMetadataGenerator.Initialize (cyclomatic 17) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandHandlerEntityMethodMetadataGenerator.cs:13— CommandHandlerEntityMethodMetadataGenerator.Initialize has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 23, 17, 19). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Program.GenerateVisualization (cognitive 97) src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:246— Program.GenerateVisualization has cognitive complexity 97 (threshold 15). Of this number, 91 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CommandHandlerMetadataGenerator.Initialize (cognitive 59) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandHandlerMetadataGenerator.cs:14— CommandHandlerMetadataGenerator.Initialize has cognitive complexity 59 (threshold 15). Most of this is not in the body itself: 0 of the 59 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 24, 18, 20). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
EndpointMetadataGenerator.Initialize (cognitive 58) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/EndpointMetadataGenerator.cs:13— EndpointMetadataGenerator.Initialize has cognitive complexity 58 (threshold 15). Most of this is not in the body itself: 0 of the 58 points are its own statements and the rest belongs to one function literal inside it that branches (line 23). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Program.AddSnapshot (cognitive 56) src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:773— Program.AddSnapshot has cognitive complexity 56 (threshold 15). Of this number, 52 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
IntegrationEventHandlerMetadataGenerator.Initialize (cognitive 55) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/IntegrationEventHandlerMetadataGenerator.cs:13— IntegrationEventHandlerMetadataGenerator.Initialize has cognitive complexity 55 (threshold 15). Most of this is not in the body itself: 0 of the 55 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 23, 17, 19). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ControllerMethodMetadataGenerator.Initialize (cognitive 54) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/ControllerMethodMetadataGenerator.cs:13— ControllerMethodMetadataGenerator.Initialize has cognitive complexity 54 (threshold 15). Most of this is not in the body itself: 0 of the 54 points are its own statements and the rest belongs to one function literal inside it that branches (line 23). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
CommandSenderMethodMetadataGenerator.Initialize (cognitive 50) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandSenderMethodMetadataGenerator.cs:13— CommandSenderMethodMetadataGenerator.Initialize has cognitive complexity 50 (threshold 15). Most of this is not in the body itself: 0 of the 50 points are its own statements and the rest belongs to one function literal inside it that branches (line 23). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
CommandHandlerEntityMethodMetadataGenerator.Initialize (cognitive 46) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandHandlerEntityMethodMetadataGenerator.cs:13— CommandHandlerEntityMethodMetadataGenerator.Initialize has cognitive complexity 46 (threshold 15). Most of this is not in the body itself: 0 of the 46 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 23, 17, 19). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
EntityMetadataGenerator.Initialize (cognitive 42) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/EntityMetadataGenerator.cs:14— EntityMetadataGenerator.Initialize has cognitive complexity 42 (threshold 15). Most of this is not in the body itself: 0 of the 42 points are its own statements and the rest belongs to one function literal inside it that branches (line 24). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
EntityMethodMetadataGenerator.ProcessMethods (cognitive 40) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/EntityMethodMetadataGenerator.cs:42— EntityMethodMetadataGenerator.ProcessMethods has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
EntityMethodMetadataGenerator.ProcessConstructors (cognitive 40) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/EntityMethodMetadataGenerator.cs:111— EntityMethodMetadataGenerator.ProcessConstructors has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AggregateRelationMermaidVisualizer.GenerateMermaid (cognitive 40) src/NetCorePal.Extensions.CodeAnalysis/MermaidVisualizers/AggregateRelationMermaidVisualizer.cs:57— AggregateRelationMermaidVisualizer.GenerateMermaid has cognitive complexity 40 (threshold 15). Of this number, 35 points are the body's own statements and 5 belong to 5 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DomainEventHandlerMetadataGenerator.Initialize (cognitive 36) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/DomainEventHandlerMetadataGenerator.cs:13— DomainEventHandlerMetadataGenerator.Initialize has cognitive complexity 36 (threshold 15). Most of this is not in the body itself: 0 of the 36 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 23, 17, 19). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ProcessingFlowMermaidVisualizer.GenerateMermaid (cognitive 36) src/NetCorePal.Extensions.CodeAnalysis/MermaidVisualizers/ProcessingFlowMermaidVisualizer.cs:15— ProcessingFlowMermaidVisualizer.GenerateMermaid has cognitive complexity 36 (threshold 15). Of this number, 35 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program.AutoDiscoverProjects (cognitive 33) src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:616— Program.AutoDiscoverProjects has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MermaidDomainCodeGenerators.Initialize (cognitive 32) src/NetCorePal.Extensions.Domain.SourceGenerators/MermaidDomainCodeGenerators.cs:18— MermaidDomainCodeGenerators.Initialize has cognitive complexity 32 (threshold 15). Most of this is not in the body itself: 0 of the 32 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 34, 21). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
GeneratorExtensions.GetSentCommandTypes (cognitive 26) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/GeneratorExtensions.cs:134— GeneratorExtensions.GetSentCommandTypes has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Program.LoadSnapshotsFromProjectAssemblies (cognitive 25) src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:1054— Program.LoadSnapshotsFromProjectAssemblies has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DiagnosticListener.OnNext (cognitive 25) src/NetCorePal.OpenTelemetry.Diagnostics/DiagnosticListener.cs:28— DiagnosticListener.OnNext has cognitive complexity 25 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Program.FindNuGetConfig (cognitive 22) src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:33— Program.FindNuGetConfig has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectAnalysisHelpers.GetProjectPathsFromSolution (cognitive 22) src/NetCorePal.Extensions.CodeAnalysis.Tools/ProjectAnalysisHelpers.cs:113— ProjectAnalysisHelpers.GetProjectPathsFromSolution has cognitive complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AppIdentityDbContextBase.UpdateNetCorePalTypesBeforeSaveChanges (cognitive 22) src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityDbContextBase.cs:174— AppIdentityDbContextBase.UpdateNetCorePalTypesBeforeSaveChanges has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AppIdentityUserContextBase.UpdateNetCorePalTypesBeforeSaveChanges (cognitive 22) src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityUserContextBase.cs:174— AppIdentityUserContextBase.UpdateNetCorePalTypesBeforeSaveChanges has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AppDbContextBase.UpdateNetCorePalTypesBeforeSaveChanges (cognitive 22) src/NetCorePal.Extensions.Repository.EntityFrameworkCore/AppDbContextBase.cs:203— AppDbContextBase.UpdateNetCorePalTypesBeforeSaveChanges has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
EtcdWorkerIdGenerator.GenWorkId (cognitive 19) src/NetCorePal.Extensions.Snowflake.Etcd/EtcdWorkerIdGenerator.cs:58— EtcdWorkerIdGenerator.GenWorkId has cognitive complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntityIdJsonConverter.Read (cognitive 18) src/NetCorePal.Extensions.Domain.Abstractions/Json/EntityIdJsonConverter.cs:16— EntityIdJsonConverter.Read has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppDbContextBaseCapDataStorageSourceGenerator.Initialize (cognitive 17) src/NetCorePal.Extensions.DistributedTransactions.CAP.SourceGenerators/AppDbContextBaseCapDataStorageSourceGenerator.cs:16— AppDbContextBaseCapDataStorageSourceGenerator.Initialize has cognitive complexity 17 (threshold 15). Most of this is not in the body itself: 0 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 26). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
EntityIdTypeConverter.ConvertFrom (cognitive 17) src/NetCorePal.Extensions.Domain.Abstractions/EntityIdTypeConverter.cs:28— EntityIdTypeConverter.ConvertFrom has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArchitectureOverviewMermaidVisualizer.GenerateMermaid (cognitive 16) src/NetCorePal.Extensions.CodeAnalysis/MermaidVisualizers/ArchitectureOverviewMermaidVisualizer.cs:15— ArchitectureOverviewMermaidVisualizer.GenerateMermaid has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LLM evaluation failed — JSON parse error: Expected depth to be zero at the end of the JSON payload. There is an open JSON object or array that should be closed. Path: $.notable[4].suggestion | LineNumber: 0 | BytePositionInLine: 925.
ClassTooLong: Program src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:0— ClassTooLong — 749 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
FileTooLong: NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs src/NetCorePal.Extensions.CodeAnalysis.Tools/Program.cs:0— FileTooLong — 760 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
TooManyMethods: CodeFlowAnalysisHelper src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:0— TooManyMethods — 476 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 11 floating ref(s) across 4 workflow file(s). Each floating ref is itemized at file:line by the SAST (D29) lens.
D36 · Supply-chain Provenance & Signing· PR-triggered workflow without a permissions block · ×1
PR-triggered workflow without a permissions block — 1 workflow(s) triggered by pull_request declare no `permissions:` block (pr.yml) and so run with the repository's default GITHUB_TOKEN scope, while 3 sibling workflows in the same repository are already scoped. Pull-request runs build the least-trusted code in the repository; give each of these workflows its own least-privilege block — `permissions: {contents: read}` at the top of the workflow, widened per job only where a job genuinely writes.
D36 · Supply-chain Provenance & Signing· Secret passed as a command-line argument · ×1
Secret passed as a command-line argument — 2 CI command(s) pass a credential as a bare command-line argument, where it is visible in the runner's process table to any other process on the host (and to anything that logs a command line): release.yml: dotnet nuget push '*.nupkg' -s https://api.nuget.org/v3/index.json -k ${{ secrets.NUGET_API_KEY }} --skip-duplicate; dotnet.yml: dotnet nuget push '*.nupkg' -s https://www.myget.org/F/netcorepal/api/v3/index.json -k ${{ secrets.MYGET_API_KEY }} --skip-duplicate. Pass the credential through the environment instead (an `env:` mapping on the step, read by the tool from its own variable) or on stdin, so it never appears in an argument vector.
Duplicated block (29 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:327— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:327-355 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs:198-226 — before extracting anything, compare `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs` and `src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:327` it begins part-way through the construct above it, 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 (28 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:381— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:381-408 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs:252-279 — before extracting anything, compare `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs` and `src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:381` it begins part-way through the construct above it, 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 (25 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:473— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:473-497 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs:389-413 — before extracting anything, compare `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs` and `src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:473` it begins part-way through the construct above it, 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 (23 lines × 4) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:105— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:105-127 | src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:147-169 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalMonitoringApi.cs:105-127 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalMonitoringApi.cs:147-169 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalMonitoringApi.cs:105` it begins part-way through the construct above it, 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 (22 lines × 3) src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityDbContextBase.cs:140— src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityDbContextBase.cs:140-161 | src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityUserContextBase.cs:140-161 | src/NetCorePal.Extensions.Repository.EntityFrameworkCore/AppDbContextBase.cs:169-190 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityDbContextBase.cs:140` it begins part-way through the construct above it, 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 (18 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:416— src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:416-433 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs:333-350 — before extracting anything, compare `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs` and `src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/MongoDBNetCorePalDataStorage.cs:416` it begins part-way through the construct above it, 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 (15 lines × 3) src/NetCorePal.Extensions.ShardingCore.SourceGenerators/AppDbContextShardingCoreSourceGenerator.cs:153— src/NetCorePal.Extensions.ShardingCore.SourceGenerators/AppDbContextShardingCoreSourceGenerator.cs:153-167 | src/NetCorePal.Extensions.DistributedTransactions.CAP.SourceGenerators/AppDbContextBaseCapDataStorageSourceGenerator.cs:218-232 | src/NetCorePal.Extensions.Repository.EntityFrameworkCore.SourceGenerators/AppDbContextBaseSourceGenerator.cs:164-178 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.ShardingCore.SourceGenerators/AppDbContextShardingCoreSourceGenerator.cs:153` it begins part-way through the construct above it, 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 (13 lines × 5) src/NetCorePal.Extensions.DistributedTransactions.CAP.DMDB/EntityTypeConfigurations/PublishedMessageConfiguration.cs:18— src/NetCorePal.Extensions.DistributedTransactions.CAP.DMDB/EntityTypeConfigurations/PublishedMessageConfiguration.cs:18-31 | src/NetCorePal.Extensions.DistributedTransactions.CAP.GaussDB/EntityTypeConfigurations/PublishedMessageConfiguration.cs:18-30 | src/NetCorePal.Extensions.DistributedTransactions.CAP.KingbaseES/EntityTypeConfigurations/PublishedMessageConfiguration.cs:18-30 | src/NetCorePal.Extensions.DistributedTransactions.CAP.MySql/EntityTypeConfigurations/PublishedMessageConfiguration.cs:19-31 | src/NetCorePal.Extensions.DistributedTransactions.CAP.Sqlite/EntityTypeConfigurations/PublishedMessageConfiguration.cs:19-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (13 lines × 3) src/NetCorePal.Extensions.ShardingCore.SourceGenerators/AppDbContextShardingCoreSourceGenerator.cs:133— src/NetCorePal.Extensions.ShardingCore.SourceGenerators/AppDbContextShardingCoreSourceGenerator.cs:133-145 | src/NetCorePal.Extensions.DistributedTransactions.CAP.SourceGenerators/AppDbContextBaseCapDataStorageSourceGenerator.cs:198-210 | src/NetCorePal.Extensions.Repository.EntityFrameworkCore.SourceGenerators/AppDbContextBaseSourceGenerator.cs:144-156 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.ShardingCore.SourceGenerators/AppDbContextShardingCoreSourceGenerator.cs:133` it begins part-way through the construct above it, 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 (12 lines × 2) src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs:290— src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs:290-301 | src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs:308-319 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalDataStorage.cs:290` it begins part-way through the construct above it, 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 (11 lines × 4) src/NetCorePal.Extensions.ShardingCore.SourceGenerators/AppDbContextShardingCoreSourceGenerator.cs:21— src/NetCorePal.Extensions.ShardingCore.SourceGenerators/AppDbContextShardingCoreSourceGenerator.cs:21-31 | src/NetCorePal.Extensions.DistributedTransactions.CAP.SourceGenerators/AppDbContextBaseCapDataStorageSourceGenerator.cs:21-31 | src/NetCorePal.Extensions.Domain.SourceGenerators/EntityIdCodeGenerators.cs:19-29 | src/NetCorePal.Extensions.Repository.EntityFrameworkCore.SourceGenerators/AppDbContextBaseSourceGenerator.cs:22-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.ShardingCore.SourceGenerators/AppDbContextShardingCoreSourceGenerator.cs:21` it begins part-way through the construct above it, 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 (11 lines × 3) src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityDbContextBase.cs:194— src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityDbContextBase.cs:194-204 | src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityUserContextBase.cs:194-204 | src/NetCorePal.Extensions.Repository.EntityFrameworkCore/AppDbContextBase.cs:223-233 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.Repository.EntityFrameworkCore.Identity/AppIdentityDbContextBase.cs:194` it begins part-way through the construct above it, 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 (11 lines × 2) src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:663— src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:663-673 | src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:722-732 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis/CodeFlowAnalysisHelper.cs:663` 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) src/NetCorePal.Extensions.CodeAnalysis/VisualizationHtmlBuilder.cs:221— src/NetCorePal.Extensions.CodeAnalysis/VisualizationHtmlBuilder.cs:221-229 | src/NetCorePal.Extensions.CodeAnalysis/VisualizationHtmlBuilder.cs:231-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 7) src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandHandlerEntityMethodMetadataGenerator.cs:14— src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandHandlerEntityMethodMetadataGenerator.cs:14-21 | src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandHandlerMetadataGenerator.cs:15-22 | src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandMetadataGenerator.cs:14-21 | src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/DomainEventHandlerMetadataGenerator.cs:14-21 | src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/DomainEventMetadataGenerator.cs:14-21 | src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/IntegrationEventConverterMetadataGenerator.cs:14-21 | src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/IntegrationEventHandlerMetadataGenerator.cs:14-21 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.CodeAnalysis.SourceGenerators/CommandHandlerEntityMethodMetadataGenerator.cs:14` 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 (6 lines × 5) src/NetCorePal.Extensions.DistributedTransactions.CAP.DMDB/EntityTypeConfigurations/CapLockConfiguration.cs:9— src/NetCorePal.Extensions.DistributedTransactions.CAP.DMDB/EntityTypeConfigurations/CapLockConfiguration.cs:9-14 | src/NetCorePal.Extensions.DistributedTransactions.CAP.GaussDB/EntityTypeConfigurations/CapLockConfiguration.cs:9-14 | src/NetCorePal.Extensions.DistributedTransactions.CAP.KingbaseES/EntityTypeConfigurations/CapLockConfiguration.cs:9-14 | src/NetCorePal.Extensions.DistributedTransactions.CAP.PostgreSql/EntityTypeConfigurations/CapLockConfiguration.cs:9-14 | src/NetCorePal.Extensions.DistributedTransactions.CAP.SqlServer/EntityTypeConfigurations/CapLockConfiguration.cs:9-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.DMDB/EntityTypeConfigurations/CapLockConfiguration.cs:9` 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 (6 lines × 4) src/NetCorePal.Extensions.DistributedTransactions.CAP.DMDB/EntityTypeConfigurations/ReceivedMessageConfiguration.cs:9— src/NetCorePal.Extensions.DistributedTransactions.CAP.DMDB/EntityTypeConfigurations/ReceivedMessageConfiguration.cs:9-14 | src/NetCorePal.Extensions.DistributedTransactions.CAP.GaussDB/EntityTypeConfigurations/ReceivedMessageConfiguration.cs:9-14 | src/NetCorePal.Extensions.DistributedTransactions.CAP.KingbaseES/EntityTypeConfigurations/ReceivedMessageConfiguration.cs:9-14 | src/NetCorePal.Extensions.DistributedTransactions.CAP.SqlServer/EntityTypeConfigurations/ReceivedMessageConfiguration.cs:9-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/NetCorePal.Extensions.DistributedTransactions.CAP.DMDB/EntityTypeConfigurations/ReceivedMessageConfiguration.cs:9` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Coverage not measured — test suite did not build — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 3 significant file(s) lose their only recent owner: src/NetCorePal.Extensions.DistributedTransactions.CAP/Persistence/NetCorePalMonitoringApi.cs, src/NetCorePal.SkyApm.Diagnostics/NetCorePalTracingDiagnosticProcessor.cs, src/NetCorePal.Extensions.CodeAnalysis/MermaidVisualizers/ProcessingFlowMermaidVisualizer.cs. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (9 single-owned of 74 analysed files in total, counted over production source files of roughly 100 lines or more, excluding tests, vendored, generated and example/demo trees, largest first). They are anonymized user #2 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above.
D19 · Documentation Quality· The CAP MongoDB README is a provider-specific package with an overview and usage example that is clipped mid-usage. · ×1
The CAP MongoDB README is a provider-specific package with an overview and usage example that is clipped mid-usage. src/NetCorePal.Extensions.DistributedTransactions.CAP.MongoDB/README.md— Complete the Usage section so the full body is visible.
No ADRs found — No ADRs found at common paths; consider documenting architectural decisions in Docs/ADL/ or similar.
D21 · Naming Consistency· The name 'PublishedMessage' is used for two distinct concepts · ×1
The name 'PublishedMessage' is used for two distinct concepts: a persistence entity (CAP message) and a routing route. This creates ambiguity between the domain event/message and the routing mechanism. — Rename 'NetCorePal.Extensions.Repository.EntityFrameworkCore.PublishedMessage' to something more specific like 'PublishedMessageRoute' or 'PublishedMessageDataSourceRoute' to distinguish it from the CAP persistence class. (symbols: NetCorePal.Extensions.DistributedTransactions.CAP.Persistence.PublishedMessage, NetCorePal.Extensions.Repository.EntityFrameworkCore.PublishedMessageVirtualDataSourceRoute)
D23 · Boundary Type-Coupling· Bounded contexts not declared · ×1
Bounded contexts not declared — At 18941 LoC spread over 245 projects the codebase is both large and multi-module, so explicit bounded contexts are needed. 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"]`.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 2 of 74 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 100 lines or more, excluding tests, vendored, generated and example/demo trees, largest first). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — largest first: src/NetCorePal.OpenTelemetry.Diagnostics/DiagnosticListener.cs, src/NetCorePal.OpenTelemetry.Diagnostics/DiagnosticSourceSubscriber.cs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No build provenance — No SLSA provenance generation or build attestation found in CI — nothing binds a released artifact to the build that produced it, so a consumer cannot tell your artifact from a substituted one. On GitHub Actions, `actions/attest-build-provenance` (or slsa-github-generator) emits one from the job's own OIDC identity; elsewhere, run `cosign attest` over the released artifact from the release pipeline and publish the attestation beside it.
No artifact signing — No artifact signing found in CI — sign your released artifacts with whatever your ecosystem ships (a GPG/minisign detached signature — or `cosign sign-blob` — over the release archives, or over a checksum file published alongside them, Authenticode via signtool, or `dotnet nuget sign` for packages) so consumers can verify what you built.
D36 · Supply-chain Provenance & Signing· No SBOM · ×1
No SBOM — No SBOM generation or committed SBOM found — produce one with what your ecosystem ships (`sbom-tool generate` (install it with `dotnet tool install --global Microsoft.Sbom.DotNetTool`) or `dotnet CycloneDX` over the solution, `syft` (or `anchore/sbom-action` in CI) over the source tree or released image). Publish it as a release asset (`*.spdx.json` / `*.cdx.json`) so consumers can see what they are installing.
Skipped (documented): Main_GenerateCommand_WithRealProject_CreatesOutputFile test/NetCorePal.Extensions.CodeAnalysis.Tools.UnitTests/ProgramTests.cs:76— Skipped with a documented reason — a deferral, not lazy debt: Integration test - requires building projects
Skipped (documented): Main_GenerateCommand_WithCustomTitle_UsesCustomTitle test/NetCorePal.Extensions.CodeAnalysis.Tools.UnitTests/ProgramTests.cs:111— Skipped with a documented reason — a deferral, not lazy debt: Integration test - requires building projects
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — Data compliance (PII/GDPR) was not assessed in this scan — no ruleset is currently available for it. This says nothing about how this repository handles personal data, in either direction.
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
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.
0
—
Run 019fc791-22cd-72d0-800a-8602bbb5d98c · 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 — 1 field(s) across 1 category, 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 with a deliberately specific classifier (the same one the GDPR dimensions use, so CardDefinition or FileName don't trip); informational — it feeds no score.
Issues: 42 · Warnings: 136 · Recommendations: 23 · Info: 52 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 03-08-2026 @ 12:20 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.