Public report — LiteBus, 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.
Medium · 57,748 LoC · 99 projects · rebuild ~1.2 person-years · weakest lens: Security (50%)
Build did not compile — scores are provisional
The analysed solution did not compile (57 build error(s)). Dimensions that depend on the compiler — complexity, duplication, cohesion, dead code, API surface — ran on incomplete models, so the scores below are provisional. Fix the build, then re-run for a reliable grade. First errors: CS0281: Friend access was granted by 'LiteBus.Messaging, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Inbox.Abstractions, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Runtime.Extensions.Hosting, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Outbox.Abstractions, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Storage.PostgreSql, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.
Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸
89findings with an exact file:lineof 153 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
72/101dimensions across the health lenses57748 LoC · 99 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.
litenova/LiteBus is in a workable but fragile state (60%). It is not in crisis, but it carries material risk that makes change slower and incidents harder to contain if left unaddressed.
It is strongest in Event-Driven (100%) — its messaging keeps components properly decoupled. Code Health (88%) is solid too.
The area that most needs attention is Security (50%) — exposure to security and compliance incidents is elevated. Readiness (62%) is the next concern — operating, monitoring and recovering the system safely is harder.
Leadership focus, highest impact first: Encrypt sensitive data at rest (ASP.NET Core Data Protection /… (Data Protection); Back the audit convention with a structural mechanism (Audit Trail); 6 High finding(s) (Static Analysis (SAST)).
For scale: Medium (~57,748 production lines); rebuilding it from scratch would take roughly ~1.2 person-years (~1–3 engineers). Approximate, ±~30%.
It builds on a genuinely strong Event-Driven 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 11%Plumbing 37%Tests 49%Analyzers 3%
New since the last scan (1+)
1 finding(s) are new versus the previous scan (2026-07-29) — surfaced by this scheduled scan itself, no pull request required.
D38 · High CVE: [GHSA redacted] site/package-lock.json
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 ~1.2 person-years of build effort (about ~€180,000 to rebuild). Its weakest lens is Security at 50% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain High (×1.5) — service/app, CQRS, event-driven integration × a 0.8× 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
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Highest-leverage move: fix the build · Critical · Leverage
The solution doesn't compile, so every Roslyn-derived dimension (complexity, duplication, cohesion, dead code, API surface) ran on incomplete models and is PROVISIONAL. Fixing the build is the single change that makes the rest of the report trustworthy — do it first. The compiler reported: CS0281: Friend access was granted by 'LiteBus.Messaging, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Inbox.Abstractions, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Runtime.Extensions.Hosting, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Outbox.Abstractions, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Storage.PostgreSql, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly..
Evidence: D18 build: The compiler reported: CS0281: Friend access was granted by 'LiteBus.Messaging, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Inbox.Abstractions, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Runtime.Extensions.Hosting, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Outbox.Abstractions, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Storage.PostgreSql, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly..
→ Fix the build, then re-run for a reliable grade.
Value concentrated against a weak lens · Medium · Value at risk
This is a Medium asset (~1.2 person-years to rebuild), and its weakest lens is Security at 50%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Security first — highest risk-reduction per euro on an asset this size.
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
103 modules, 216 dependencies — 1 dependency cycle, 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.)
At a glance — Code Health · 88% · Adequate · gated by D18
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
A03:2021 — Injection
6
High / Critical
A06:2021 — Vulnerable & Outdated Components
6
High / Critical
Roadmap
First, encrypt sensitive data at rest and manage keys in a vault, or confirm if this is handled by infrastructure. Second, implement a structural audit mechanism, such as an EF SaveChanges interceptor, to ensure all sensitive changes are logged immutably. Third, resolve the six high-priority findings in the static analysis scan, focusing on release.yml and PostgreSqlWorkSignal.cs. Fourth, update the vulnerability disclosure policy to include a reporting contact. Finally, restrict the public API by making types internal by default to protect consumers from breaking changes.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
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.
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. 69 of 72 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 72 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, 89 of 153 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.
D19 Documentation Quality — 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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
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").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
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.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
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.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them.
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.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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): D21, D22, D24, 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.
Resolve the 1 SingleStreamHandlerMediationStrategy.Mediate (cyclomatic 27) finding(s) in Cyclomatic Complexity — start with SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 CommandWithResultScheduledToInboxAnalyzer.GetCollectionElementExpression… finding(s) in Cyclomatic Complexity — start with CommandWithResultScheduledToInboxAnalyzer.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 EfCoreInboxStore.AddBatchAsync (cyclomatic 19) finding(s) in Cyclomatic Complexity — start with EfCoreInboxStore.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.
+ 9 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 SingleStreamHandlerMediationStrategy.Mediate (cognitive 47) finding(s) in Cognitive Complexity — start with SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 CommandWithResultScheduledToInboxAnalyzer.GetCollectionElementExpression… finding(s) in Cognitive Complexity — start with CommandWithResultScheduledToInboxAnalyzer.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 EfCoreInboxStore.AddBatchAsync (cognitive 33) finding(s) in Cognitive Complexity — start with EfCoreInboxStore.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.4 / 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.
+ 16 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.4 / 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.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage7.8 / 10Strong✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Improve Code Coverage — currently 7.8/10. — Line coverage 40.7%.
Detailed fixes: d8_recommendation.md.
Do you agree with this assessment?
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.
1081 test methods: 855 unit, 226 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1081 tests.
✓ On the Gold path — maintain.
Detailed fixes: d10_recommendation.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether 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: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
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.
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor3.9 / 10Weak✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
186 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs.
Off-boarding risk: anonymized user #1
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).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D18 · Solution Shape3.0 / 10Weak✓ Tool-verified
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
Resolve the 3 Shell project finding(s) in Solution Shape — start with LiteBus.Events.Extensions.Autofac.csproj, LiteBus.Messaging.Extensions.Autofac.csproj, LiteBus.Queries.Extensions.Autofac.csproj. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API Consistency / 10Exemplary◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
D24 · Comment Value / 10Exemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
0 of 99 projects flagged as possibly oversized/incoherent.
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md.
Do you agree with this assessment?
D27 · Navigability8.7 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
79 % of calls cross a namespace and 9 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What to do
Improve Navigability — currently 8.7/10. — 79 % of calls cross a namespace and 9 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
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 · ×6.github/workflows/release.yml:21detected by semgrep finding
What to do
Resolve the 6 High finding(s) in Static Analysis (SAST) — start with release.yml (5), PostgreSqlWorkSignal.cs. — One of this dimension's main actionable groups (6 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.
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.
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 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).
Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
A vulnerability-disclosure policy (SECURITY.md) is present but lists no reporting contact.
Disclosure policy has no reporting contact
What to do
Resolve the 1 Disclosure policy has no reporting contact finding(s) in Vulnerability-disclosure Policy. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d37_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.
Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
High CVE: [GHSA redacted] · ×4site/package-lock.jsondetected by osv-scanner finding
High vulnerability: [GHSA redacted]site/package-lock.jsondetected by osv-scanner finding
What to do
Resolve the 4 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 High vulnerability finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
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.
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 a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time.
What to do
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.
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.
`BackgroundServiceHostedServiceIndex` is a singleton (one shared instance) but mutates instance state outside any lock (_backgroundServicesByImplementationType; e.g. `_backgroundServicesByImplementationType` at line 29). — BackgroundServiceHostedServiceIndex.cs:12
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface 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 Protection0.0 / 10Critical✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Do you agree with this assessment?
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 Retention7.5 / 10Strong✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
What to do
Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
Other · 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 · Event-Driven — Whether commands have a single handler (one owner of the decision) and fan-out is modelled with events.
Method: Roslyn scan (event-driven gated): command-shaped messages identified by convention; handler count per command checked for the exactly-one rule. Deterministic, hard fact.
Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.
Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.
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.
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.
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 an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 97 of 99 project(s) that lack one — worth up to 2 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.
README advertises Docker containerisation, but no Dockerfile/compose file exists
What to do
Reconcile the README with reality: README advertises Docker containerisation, but no Dockerfile/compose file exists.
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.
666/832 types (80%) 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.3 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 8/72 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 72, 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.
What to do
The .NET analyzers are running but not blocking — tighten them (set <AnalysisMode>All</AnalysisMode>, or treat analyzer warnings as errors on CI) so a security/quality regression fails the build rather than scrolling past as a warning.
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.
Do you agree with this assessment?
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage. Exhaustive per project, deterministic.
EF Core is used but neither migrations nor EnsureCreated were detected — confirm how the production schema is created and evolved.
What to do
Adopt a versioned schema-migration mechanism (with EF Core: dotnet ef migrations add + Migrate() on startup) as the explicit, versioned schema strategy — no migration mechanism was detected.
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.
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 60 use(s) across 60,068 production line(s) (~1.0/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.
3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock in a consumer with a synchronization context.
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.
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. — PipelinedInboxProcessorBenchmarks.cs:76
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback. (×2) — MicrosoftMessageDispatchScopeFactory.cs:62, AzureServiceBusPublisher.cs:48
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 247/259 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 — this work can't be stopped early once started. (×10) — PipelinedInboxProcessorBenchmarks.cs:94, AsyncBroadcastMediationStrategy[TMessage].cs:110, AsyncBroadcastMediationStrategy[TMessage].cs:141, …
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. (×2) — AsyncBroadcastMediationStrategy[TMessage].cs:217, TransportInboxIngressConsumer.cs:338
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.4 `!` suppressions per 1k syntax nodes — 71 suppression(s) across the 167055 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 8 of 55 WCAG 2.2 Level A/AA success criteria (15%; ≈16% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 47 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 — 29 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.
AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
D19 Documentation Quality — LLM evaluation failed
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D23 Boundary Type-Coupling — Bounded contexts not declared
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
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
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this check looks for (15 value object(s))
ED3 Event naming — no domain or integration events detected — event-naming check not applicable
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.
P7 Outbound HTTP resilience — no outbound HTTP usage detected
P9 Domain vs controller coverage — coverage data present but no domain-layer files were identified (no /Domain//Aggregates/ paths)
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: github-actions-mutable-action-tag .github/workflows/release.yml:21— 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@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/release.yml:26— 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@v6`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/release.yml:31— 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-node@<40-character SHA>`. This step references `actions/setup-node@v7`; resolve the SHA it points at today with `gh api repos/actions/setup-node/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/release.yml:195— 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: codecov/codecov-action@<40-character SHA>`. This step references `codecov/codecov-action@v6`; resolve the SHA it points at today with `gh api repos/codecov/codecov-action/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/release.yml:215— 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/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v7`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v7 --jq .sha`.
High: csharp-sqli src/LiteBus.Storage.PostgreSql/Stores/PostgreSqlWorkSignal.cs:265— Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Bind every value as a parameter instead of building the statement text: add a `DbParameter` to `DbCommand.Parameters` for each value and reference it by name in the SQL. This works the same way for every ADO.NET provider. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
D38 · OSV Dependency Vulnerabilities· High CVE · ×4
High CVE: [GHSA redacted] site/package-lock.json— brace-expansion 1.1.16: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 1.1.17 with an `overrides` entry).
High CVE: [GHSA redacted] site/package-lock.json— brace-expansion 5.0.7: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 5.0.8 with an `overrides` entry).
High CVE: [GHSA redacted] site/package-lock.json— next 16.2.10: [GHSA redacted] — this repo declares next ^16.2.10, a range that ALREADY admits the fixed 16.2.11, so there is no manifest edit to make here. Re-resolve the lock so next moves onto 16.2.11 or later; if the flagged 16.2.10 comes back, a dependency is pinning it — upgrade that dependent, or pin next with an `overrides` entry so only one copy resolves. This one row stands for the 9 advisories this scan raises against next 16.2.10: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] site/package-lock.json— postcss 8.5.10: [GHSA redacted] — this repo declares postcss ^8.5.10, a range that ALREADY admits the fixed 8.5.12, so there is no manifest edit to make here. Re-resolve the lock so postcss moves onto 8.5.12 or later; if the flagged 8.5.10 comes back, a dependency is pinning it — upgrade that dependent, or pin postcss with an `overrides` entry so only one copy resolves. This is 1 of 2 advisories with a published fix this scan raises against postcss 8.5.10, and their fixed versions do not agree — anything below 8.5.18 still leaves at least one of them open. Take this package to 8.5.18 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against postcss 8.5.10: [GHSA redacted], [GHSA redacted].
NoWarnInCsproj tests/LiteBus.Runtime.UnitTests/LiteBus.Runtime.UnitTests.csproj:4— CS8002 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/LiteBus.Analyzers/LiteBus.Analyzers.csproj:20— RS2008 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Directory.Build.props:20— 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.
D38 · OSV Dependency Vulnerabilities· High vulnerability · ×1
High vulnerability: [GHSA redacted] site/package-lock.json— sharp 0.34.5: [GHSA redacted] — sharp is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin sharp to 0.35.0 with an `overrides` entry).
Hotspot: src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs— src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs changed 23 times in last 90 days, max complexity 19. 1 of those changes was a fix/bug commit, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs— src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs changed 22 times in last 90 days, max complexity 19. 1 of those changes was a fix/bug commit, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs— src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs changed 19 times in last 90 days, max complexity 15. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs— src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs changed 18 times in last 90 days, max complexity 15. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs— src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs changed 8 times in last 90 days, max complexity 27. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/LiteBus.Analyzers/CommandWithResultScheduledToInboxAnalyzer.cs src/LiteBus.Analyzers/CommandWithResultScheduledToInboxAnalyzer.cs— src/LiteBus.Analyzers/CommandWithResultScheduledToInboxAnalyzer.cs changed 9 times in last 90 days, max complexity 23. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/LiteBus.Analyzers/Analysis/TagReferenceAnalysis.cs src/LiteBus.Analyzers/Analysis/TagReferenceAnalysis.cs— src/LiteBus.Analyzers/Analysis/TagReferenceAnalysis.cs changed 6 times in last 90 days, max complexity 15. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/LiteBus.Messaging/Registry/Descriptors/MessageDescriptor.cs src/LiteBus.Messaging/Registry/Descriptors/MessageDescriptor.cs— src/LiteBus.Messaging/Registry/Descriptors/MessageDescriptor.cs changed 5 times in last 90 days, max complexity 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/LiteBus.Messaging/Processing/ProcessorBackgroundService[TProcessor].cs src/LiteBus.Messaging/Processing/ProcessorBackgroundService[TProcessor].cs— src/LiteBus.Messaging/Processing/ProcessorBackgroundService[TProcessor].cs changed 3 times in last 90 days, max complexity 15. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/LiteBus.Transport.AzureServiceBus/AzureServiceBusMessageMapper.cs src/LiteBus.Transport.AzureServiceBus/AzureServiceBusMessageMapper.cs— src/LiteBus.Transport.AzureServiceBus/AzureServiceBusMessageMapper.cs changed 3 times in last 90 days, max complexity 15. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Off the main sequence: LiteBus.Runtime.Extensions.Hosting — LiteBus.Runtime.Extensions.Hosting: abstractness 0.00, instability 0.06, distance 0.94 — zone of pain — concrete and depended on by 15 project(s), so it's rigid to change.
Off the main sequence: LiteBus.Runtime — LiteBus.Runtime: abstractness 0.00, instability 0.08, distance 0.92 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
Off the main sequence: LiteBus.Messaging — LiteBus.Messaging: abstractness 0.06, instability 0.06, distance 0.88 — zone of pain — concrete and depended on by 45 project(s), so it's rigid to change.
Off the main sequence: LiteBus.Transport — LiteBus.Transport: abstractness 0.11, instability 0.07, distance 0.81 — zone of pain — concrete and depended on by 25 project(s), so it's rigid to change.
Off the main sequence: LiteBus.Runtime.Extensions.Microsoft.Hosting — LiteBus.Runtime.Extensions.Microsoft.Hosting: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: LiteBus.Inbox — LiteBus.Inbox: abstractness 0.00, instability 0.21, distance 0.79 — zone of pain — concrete and depended on by 19 project(s), so it's rigid to change.
Off the main sequence: LiteBus.Runtime.Extensions.Autofac.Hosting — LiteBus.Runtime.Extensions.Autofac.Hosting: abstractness 0.00, instability 0.29, distance 0.71 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: LiteBus.Outbox — LiteBus.Outbox: abstractness 0.00, instability 0.29, distance 0.71 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
TooManyMethods: EfCoreInboxStore src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:0— TooManyMethods — 841 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: EfCoreOutboxStore src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:0— TooManyMethods — 817 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LiteBusManagementEndpointExtensions src/LiteBus.Extensions.AspNetCore/LiteBusManagementEndpointExtensions.cs:0— TooManyMethods — 439 significant lines (blank, comment-only and punctuation-only lines excluded), 42 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.
TooManyMethods: PostgreSqlOutboxStore src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:0— TooManyMethods — 597 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PostgreSqlInboxStore src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:0— TooManyMethods — 595 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InMemoryOutboxStore src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:0— TooManyMethods — 296 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InMemoryInboxStore src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:0— TooManyMethods — 293 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:0— FileTooLong — 892 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.
FileTooLong: LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:0— FileTooLong — 868 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.
FileTooLong: LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:0— FileTooLong — 614 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.
FileTooLong: LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:0— FileTooLong — 612 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.
Duplicated block (16 lines × 2) src/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs:187— src/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs:187-202 | src/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs:245-260 — 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/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs:187` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) src/LiteBus.Inbox/InboxModule.cs:75— src/LiteBus.Inbox/InboxModule.cs:75-90 | src/LiteBus.Outbox/OutboxModule.cs:76-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox/InboxModule.cs:75` 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 (16 lines × 2) src/LiteBus.Messaging.Abstractions/Contracts/MessageContractBuilder.cs:65— src/LiteBus.Messaging.Abstractions/Contracts/MessageContractBuilder.cs:65-80 | src/LiteBus.Messaging/Contracts/MessageContractRegistry.cs:159-174 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStorageModule.cs:46— src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStorageModule.cs:46-61 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxModule.cs:63-78 — 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/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStorageModule.cs:46` 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 (17 lines × 2) src/LiteBus.Analyzers/TransactionalInboxWithoutDbContextAnalyzer.cs:44— src/LiteBus.Analyzers/TransactionalInboxWithoutDbContextAnalyzer.cs:44-60 | src/LiteBus.Analyzers/TransactionalOutboxWithoutDbContextAnalyzer.cs:44-60 — 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/LiteBus.Analyzers/TransactionalInboxWithoutDbContextAnalyzer.cs:44` 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 (17 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:830— src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:830-846 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:918-934 — 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/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:830` 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/LiteBus.Transport.InMemory/InMemoryConsumer.cs:56— src/LiteBus.Transport.InMemory/InMemoryConsumer.cs:56-72 | src/LiteBus.Transport.Kafka/KafkaConsumer.cs:75-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Transport.InMemory/InMemoryConsumer.cs:56` 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.
Deprecated: Microsoft.CodeAnalysis.CSharp.Analyzer.Testing.XUnit — Microsoft.CodeAnalysis.CSharp.Analyzer.Testing.XUnit 1.1.2 — Legacy — the publisher's replacement is `Microsoft.CodeAnalysis.CSharp.Analyzer.Testing`; migrate the reference to it.
Deprecated: xunit — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; migrate the reference to it.
Duplicated block (24 lines × 2) src/LiteBus.Inbox.Ingress.InMemory/InMemoryInboxIngressModule.cs:42— src/LiteBus.Inbox.Ingress.InMemory/InMemoryInboxIngressModule.cs:42-65 | src/LiteBus.Inbox.Ingress.Kafka/KafkaInboxIngressModule.cs:44-67 — before extracting anything, compare `src/LiteBus.Inbox.Ingress.InMemory/InMemoryInboxIngressModule.cs` and `src/LiteBus.Inbox.Ingress.Kafka/KafkaInboxIngressModule.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 58 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/LiteBus.Inbox.Ingress.Kafka/KafkaInboxIngressModule.cs:44` 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 (24 lines × 2) src/LiteBus.Inbox/InboxProcessorControl.cs:173— src/LiteBus.Inbox/InboxProcessorControl.cs:173-196 | src/LiteBus.Outbox/OutboxProcessorControl.cs:173-196 — 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/LiteBus.Inbox/InboxProcessorControl.cs:173` 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 (20 lines × 2) src/LiteBus.Inbox/InboxProcessorControl.cs:118— src/LiteBus.Inbox/InboxProcessorControl.cs:118-137 | src/LiteBus.Outbox/OutboxProcessorControl.cs:118-137 — 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 (20 lines × 2) src/LiteBus.Transport.AwsSqs/SqsConsumer.cs:71— src/LiteBus.Transport.AwsSqs/SqsConsumer.cs:71-90 | src/LiteBus.Transport.Kafka/KafkaConsumer.cs:79-98 — 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/LiteBus.Transport.AwsSqs/SqsConsumer.cs:71` 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 (9 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1549— src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1549-1557 | src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:607-615 — 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/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1549` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1522— src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1522-1530 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:609-617 — 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/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1522` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 3) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:880— src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:880-887 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:961-968 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1041-1048 — 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/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:880` 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 × 3) src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:891— src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:891-898 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:972-979 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1052-1059 — 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/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:891` 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.
Low cohesion: InboxModuleBuilder (LCOM4 6) src/LiteBus.Inbox/InboxModuleBuilder.cs:16— InboxModuleBuilder's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: OutboxModuleBuilder (LCOM4 6) src/LiteBus.Outbox/OutboxModuleBuilder.cs:15— OutboxModuleBuilder's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
SingleStreamHandlerMediationStrategy.Mediate (cyclomatic 27) src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs:65— SingleStreamHandlerMediationStrategy.Mediate has cyclomatic complexity 27 (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.
CommandWithResultScheduledToInboxAnalyzer.GetCollectionElementExpressions (cyclomatic 23) src/LiteBus.Analyzers/CommandWithResultScheduledToInboxAnalyzer.cs:246— CommandWithResultScheduledToInboxAnalyzer.GetCollectionElementExpressions has cyclomatic complexity 23 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
EfCoreInboxStore.AddBatchAsync (cyclomatic 19) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:470— EfCoreInboxStore.AddBatchAsync has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 481). 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.
EfCoreOutboxStore.AddBatchAsync (cyclomatic 19) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:448— EfCoreOutboxStore.AddBatchAsync has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 459). 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.
MessageDescriptor.AddDescriptor (cyclomatic 16) src/LiteBus.Messaging/Registry/Descriptors/MessageDescriptor.cs:108— MessageDescriptor.AddDescriptor has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Prerelease dependency: StyleCop.Analyzers — StyleCop.Analyzers resolves to 1.2.0-beta.556, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Build failed — The target solution did not build cleanly (errors: 57), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS0281: Friend access was granted by 'LiteBus.Messaging, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Inbox.Abstractions, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Runtime.Extensions.Hosting, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Outbox.Abstractions, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly.; CS0281: Friend access was granted by 'LiteBus.Storage.PostgreSql, Version=6.0.2.0, Culture=neutral, PublicKeyToken=null', but the public key of the output assembly ('') does not match that specified by the InternalsVisibleTo attribute in the granting assembly..
LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.findings[1].issue | LineNumber: 0 | BytePositionInLine: 1142.
SingleStreamHandlerMediationStrategy.Mediate (cognitive 47) src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs:65— SingleStreamHandlerMediationStrategy.Mediate has cognitive complexity 47 (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.
CommandWithResultScheduledToInboxAnalyzer.GetCollectionElementExpressions (cognitive 34) src/LiteBus.Analyzers/CommandWithResultScheduledToInboxAnalyzer.cs:246— CommandWithResultScheduledToInboxAnalyzer.GetCollectionElementExpressions has cognitive complexity 34 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
EfCoreInboxStore.AddBatchAsync (cognitive 33) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:470— EfCoreInboxStore.AddBatchAsync has cognitive complexity 33 (threshold 15). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to one function literal inside it that branches (line 481). 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.
EfCoreOutboxStore.AddBatchAsync (cognitive 33) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:448— EfCoreOutboxStore.AddBatchAsync has cognitive complexity 33 (threshold 15). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to one function literal inside it that branches (line 459). 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.
TagReferenceAnalysis.CollectReferencedTags (cognitive 31) src/LiteBus.Analyzers/Analysis/TagReferenceAnalysis.cs:31— TagReferenceAnalysis.CollectReferencedTags has cognitive complexity 31 (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.
ProcessorBackgroundService.ExecuteAsync (cognitive 27) src/LiteBus.Messaging/Processing/ProcessorBackgroundService[TProcessor].cs:98— ProcessorBackgroundService.ExecuteAsync has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OrphanHandlerTagAnalyzer.Initialize (cognitive 22) src/LiteBus.Analyzers/OrphanHandlerTagAnalyzer.cs:22— OrphanHandlerTagAnalyzer.Initialize has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 0 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 31). 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.
PostgreSqlInboxStore.AddBatchAsync (cognitive 22) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:599— PostgreSqlInboxStore.AddBatchAsync 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.
PostgreSqlOutboxStore.AddBatchAsync (cognitive 22) src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:608— PostgreSqlOutboxStore.AddBatchAsync 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.
SqsConsumer.RunConsumeLoopAsync (cognitive 19) src/LiteBus.Transport.AwsSqs/SqsConsumer.cs:168— SqsConsumer.RunConsumeLoopAsync has cognitive complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PostgreSqlWorkSignal.RunListenerLoopAsync (cognitive 17) src/LiteBus.Storage.PostgreSql/Stores/PostgreSqlWorkSignal.cs:168— PostgreSqlWorkSignal.RunListenerLoopAsync has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ContractRegistrationAnalysis.CollectRegisteredContractTypes (cognitive 16) src/LiteBus.Analyzers/Analysis/ContractRegistrationAnalysis.cs:22— ContractRegistrationAnalysis.CollectRegisteredContractTypes 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.
InboxPipelinedMessageProcessorOperations.PersistTerminalOutcomeAsync (cognitive 16) src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs:201— InboxPipelinedMessageProcessorOperations.PersistTerminalOutcomeAsync 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.
OutboxPipelinedMessageProcessorOperations.PersistTerminalOutcomeAsync (cognitive 16) src/LiteBus.Outbox/OutboxPipelinedMessageProcessorOperations.cs:201— OutboxPipelinedMessageProcessorOperations.PersistTerminalOutcomeAsync 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.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 14 floating ref(s) across 3 workflow file(s). Each floating ref is itemized at file:line by the SAST (D29) lens.
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 "${package}" --api-key "${{ secrets.NUGET_API_KEY }}" --source https://api.nuget.org/v3/index.json; release.yml: dotnet nuget push "${package}" --api-key "${{ secrets.GITHUB_TOKEN }}" --source https://nuget.pkg.github.com/${{ github.repository_owner }}/index.json. 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 (26 lines × 4) src/LiteBus.Transport.AwsSqs/SqsPublisher.cs:44— src/LiteBus.Transport.AwsSqs/SqsPublisher.cs:44-69 | src/LiteBus.Transport.AzureServiceBus/AzureServiceBusPublisher.cs:69-94 | src/LiteBus.Transport.InMemory/InMemoryPublisher.cs:43-68 | src/LiteBus.Transport.Kafka/KafkaPublisher.cs:50-75 — 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/LiteBus.Transport.AwsSqs/SqsPublisher.cs:44` 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 (22 lines × 2) src/LiteBus.Extensions.AspNetCore/LiteBusManagementEndpointExtensions.cs:804— src/LiteBus.Extensions.AspNetCore/LiteBusManagementEndpointExtensions.cs:804-825 | src/LiteBus.Extensions.AspNetCore/LiteBusManagementEndpointExtensions.cs:858-879 — 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/LiteBus.Extensions.AspNetCore/LiteBusManagementEndpointExtensions.cs:804` 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 (21 lines × 2) src/LiteBus.Inbox.Abstractions/Store/InboxMessagePageCursor.cs:46— src/LiteBus.Inbox.Abstractions/Store/InboxMessagePageCursor.cs:46-66 | src/LiteBus.Outbox.Abstractions/Store/OutboxMessagePageCursor.cs:46-66 — 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/LiteBus.Inbox.Abstractions/Store/InboxMessagePageCursor.cs:46` 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 × 3) src/LiteBus.Inbox.Ingress.AwsSqs/AwsSqsInboxIngressModule.cs:54— src/LiteBus.Inbox.Ingress.AwsSqs/AwsSqsInboxIngressModule.cs:54-72 | src/LiteBus.Inbox.Ingress.InMemory/InMemoryInboxIngressModule.cs:50-67 | src/LiteBus.Inbox.Ingress.Kafka/KafkaInboxIngressModule.cs:52-69 — before extracting anything, compare `src/LiteBus.Inbox.Ingress.InMemory/InMemoryInboxIngressModule.cs` and `src/LiteBus.Inbox.Ingress.Kafka/KafkaInboxIngressModule.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 58 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/LiteBus.Inbox.Ingress.AwsSqs/AwsSqsInboxIngressModule.cs:54` 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 (18 lines × 2) src/LiteBus.Inbox/InboxProcessorControl.cs:76— src/LiteBus.Inbox/InboxProcessorControl.cs:76-93 | src/LiteBus.Outbox/OutboxProcessorControl.cs:76-93 — 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/LiteBus.Inbox/InboxProcessorControl.cs:76` 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 (17 lines × 3) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:706— src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:706-723 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:796-812 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:884-900 — 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/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:706` 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 (16 lines × 3) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:734— src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:734-749 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:826-841 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:914-929 — 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/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:734` 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. 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 (15 lines × 5) src/LiteBus.Inbox.Ingress.Amqp/AmqpInboxIngressModule.cs:69— src/LiteBus.Inbox.Ingress.Amqp/AmqpInboxIngressModule.cs:69-83 | src/LiteBus.Inbox.Ingress.AwsSqs/AwsSqsInboxIngressModule.cs:68-82 | src/LiteBus.Inbox.Ingress.AzureServiceBus/AzureServiceBusInboxIngressModule.cs:74-88 | src/LiteBus.Inbox.Ingress.InMemory/InMemoryInboxIngressModule.cs:63-77 | src/LiteBus.Inbox.Ingress.Kafka/KafkaInboxIngressModule.cs:65-79 — before extracting anything, compare `src/LiteBus.Inbox.Ingress.InMemory/InMemoryInboxIngressModule.cs` and `src/LiteBus.Inbox.Ingress.Kafka/KafkaInboxIngressModule.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 58 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/LiteBus.Inbox.Ingress.Amqp/AmqpInboxIngressModule.cs:69` 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 × 4) src/LiteBus.Commands/CommandModule.cs:72— src/LiteBus.Commands/CommandModule.cs:72-86 | src/LiteBus.Events/EventModule.cs:72-86 | src/LiteBus.Messaging/MessageModule.cs:119-133 | src/LiteBus.Queries/QueryModule.cs:71-85 — 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/LiteBus.Commands/CommandModule.cs:72` 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 × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1393— src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1393-1407 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1407-1421 — 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/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1393` 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 (14 lines × 3) src/LiteBus.Inbox.Abstractions/InboxReceiptMapper.cs:91— src/LiteBus.Inbox.Abstractions/InboxReceiptMapper.cs:91-104 | src/LiteBus.Messaging/DurableEnvelopeMetadataMapper.cs:121-134 | src/LiteBus.Outbox.Abstractions/OutboxReceiptMapper.cs:86-99 — 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/LiteBus.Inbox.Abstractions/InboxReceiptMapper.cs:91` 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/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs:250— src/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs:250-261 | src/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs:265-276 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxSchemaScripts.cs:104— src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxSchemaScripts.cs:104-112 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxSchemaScripts.cs:105-113 | src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaSchemaScripts.cs:88-96 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStorageModule.cs:44— src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStorageModule.cs:44-48 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxModule.cs:62-77 — 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/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxModule.cs:62` 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. 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 (112 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStorageModule.cs:32— src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStorageModule.cs:32-143 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStorageModule.cs:33-144 — 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.
Shell project: LiteBus.Events.Extensions.Autofac src/LiteBus.Events.Extensions.Autofac/LiteBus.Events.Extensions.Autofac.csproj— `LiteBus.Events.Extensions.Autofac` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: LiteBus.Messaging.Extensions.Autofac src/LiteBus.Messaging.Extensions.Autofac/LiteBus.Messaging.Extensions.Autofac.csproj— `LiteBus.Messaging.Extensions.Autofac` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: LiteBus.Queries.Extensions.Autofac src/LiteBus.Queries.Extensions.Autofac/LiteBus.Queries.Extensions.Autofac.csproj— `LiteBus.Queries.Extensions.Autofac` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 186 significant file(s) lose their only recent owner: src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs, src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs, src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs, src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs, src/LiteBus.Extensions.AspNetCore/LiteBusManagementEndpointExtensions.cs, src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs, src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs, src/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs (+178 more). Pair on, review, or document these before any departure.
D23 · Boundary Type-Coupling· Bounded contexts not declared · ×1
Bounded contexts not declared — At 57695 LoC spread over 99 projects the codebase is both large and multi-module, so explicit bounded contexts are warranted. 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"]`.
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.
D37 · Vulnerability-disclosure Policy· Disclosure policy has no reporting contact · ×1
Disclosure policy has no reporting contact — SECURITY.md is present but no reporting contact (email / URL / mailto) was found — a coordinated-disclosure policy must tell reporters where to send a report.
Outdated: BenchmarkDotNet — BenchmarkDotNet 0.14.0 → 0.15.8 available (referenced by LiteBus.Processor.Benchmarks).
Outdated: Microsoft.CodeAnalysis.Analyzers — Microsoft.CodeAnalysis.Analyzers 3.3.4 → 5.6.0 available (referenced by LiteBus.Analyzers).
Outdated: Microsoft.CodeAnalysis.CSharp — Microsoft.CodeAnalysis.CSharp 4.8.0 → 5.6.0 available (referenced by LiteBus.Analyzers).
Outdated: System.Collections.Immutable — System.Collections.Immutable 8.0.0 → 10.0.10 available (referenced by LiteBus.Analyzers).
Outdated: Microsoft.SourceLink.GitHub — Microsoft.SourceLink.GitHub 10.0.300 → 10.0.301 available (referenced by LiteBus.Commands.Abstractions).
Outdated: Microsoft.Extensions.Diagnostics.HealthChecks — Microsoft.Extensions.Diagnostics.HealthChecks 10.0.0 → 10.0.10 available (referenced by LiteBus.Extensions.Diagnostics.HealthChecks).
Outdated: OpenTelemetry — OpenTelemetry 1.15.3 → 1.17.0 available (referenced by LiteBus.Inbox.Extensions.OpenTelemetry).
Outdated: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions 10.0.8 → 10.0.10 available (referenced by LiteBus.Inbox.Ingress.Amqp).
Outdated: Microsoft.EntityFrameworkCore — Microsoft.EntityFrameworkCore 9.0.4 → 10.0.10 available (referenced by LiteBus.Inbox.Storage.EntityFrameworkCore).
Outdated: Microsoft.EntityFrameworkCore.Relational — Microsoft.EntityFrameworkCore.Relational 9.0.4 → 10.0.10 available (referenced by LiteBus.Inbox.Storage.EntityFrameworkCore).
Outdated: Npgsql — Npgsql 9.0.4 → 10.0.3 available (referenced by LiteBus.Inbox.Storage.PostgreSql).
Outdated: Autofac — Autofac 9.1.0 → 9.3.2 available (referenced by LiteBus.Runtime.Extensions.Autofac.Hosting).
Outdated: Microsoft.Extensions.Hosting.Abstractions — Microsoft.Extensions.Hosting.Abstractions 10.0.0 → 10.0.10 available (referenced by LiteBus.Runtime.Extensions.Autofac.Hosting).
Outdated: Autofac.Extensions.DependencyInjection — Autofac.Extensions.DependencyInjection 10.0.0 → 11.0.2 available (referenced by LiteBus.Runtime.Extensions.Autofac).
Outdated: Microsoft.Extensions.DependencyInjection.Abstractions — Microsoft.Extensions.DependencyInjection.Abstractions 10.0.8 → 10.0.10 available (referenced by LiteBus.Runtime.Extensions.Microsoft.DependencyInjection).
Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 10.0.8 → 10.0.10 available (referenced by LiteBus.Testing.DurableMessaging).
Outdated: RabbitMQ.Client — RabbitMQ.Client 7.1.2 → 7.2.1 available (referenced by LiteBus.Transport.Amqp).
Outdated: AWSSDK.SQS — AWSSDK.SQS 3.7.400.118 → 4.0.100.7 available (referenced by LiteBus.Transport.AwsSqs).
Outdated: Azure.Messaging.ServiceBus — Azure.Messaging.ServiceBus 7.18.4 → 7.20.2 available (referenced by LiteBus.Transport.AzureServiceBus).
Outdated: Confluent.Kafka — Confluent.Kafka 2.8.0 → 2.15.0 available (referenced by LiteBus.Transport.Kafka).
Outdated: Microsoft.CodeAnalysis.CSharp.Workspaces — Microsoft.CodeAnalysis.CSharp.Workspaces 4.8.0 → 5.6.0 available (referenced by LiteBus.Analyzers.UnitTests).
Outdated: Microsoft.CodeAnalysis.Workspaces.Common — Microsoft.CodeAnalysis.Workspaces.Common 4.8.0 → 5.6.0 available (referenced by LiteBus.Analyzers.UnitTests).
Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 18.5.1 → 18.8.1 available (referenced by LiteBus.Analyzers.UnitTests).
Outdated: NuGet.Versioning — NuGet.Versioning 6.14.0 → 7.6.0 available (referenced by LiteBus.Analyzers.UnitTests).
Outdated: AwesomeAssertions — AwesomeAssertions 9.4.0 → 9.5.0 available (referenced by LiteBus.Durable.IntegrationTests).
+ 18 more in this group — see findings.md.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
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 019fc86b-aa37-71a5-93b0-5600392714a6 · 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: 14 · Warnings: 87 · Recommendations: 9 · Info: 43 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 03-08-2026 @ 16:18 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.