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

tranvuongduy2003/archived-EventHub

Measured 21 October 2026, 19:54 UTC, at code version 5be8f50

Test distribution: not measuredBoundary Type-Coupling: not measured

Test distribution is not measured: No automated tests.

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

CAI score 32out of 100 At risk Down 3 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Architecture 89 Strong Event-Driven 75 Strong Code Health 72 Strong Performance 60 Adequate Maturity 59 Adequate Security and Compliance 38 Weak Domain Modelling 30 Weak Production Readiness 20 Critical

A medium codebase: 20,701 lines of product code in 7 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Production Readiness, 20

Findings by how serious they are

152 critical 334 serious 170 minor

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

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
21 October 2026, 19:54 UTC

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

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

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

89of 95 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
579of 656 findings point to an exact file and line, so you can open each one in the code. The other 77 concern the repository as a whole, such as missing documentation.
95dimensions across 8 lenses, read from 20,701 lines of product code in 7 projects.
Chapters

Executive summary

tranvuongduy2003/archived-EventHub scores 32 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 20 and is rated Critical. Its Code Coverage dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 1 No automated tests finding(s) in Code Coverage and to resolve the 1 No tests found finding(s) in Test Distribution, and if Production Readiness rose to 70, the score would rise from 32 to about 42.

152 findings are critical: 55 in Explicit Debt, 40 in Domain ↔ infrastructure boundary, 25 in Aggregate boundaries, ten in Dependency Vulnerabilities, nine in Secrets (history), four in IaC & Container Security, three in Dependency Hygiene, three in Static Analysis (SAST), two in Project dependency cycles and one in Code Coverage.

Watchdog couldn't measure IL Efficiency, Platform End-of-Life and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 20,701 lines, which would take an estimated 0.3 person-years, around €36,000, to rebuild.

Code Health 72 Strong Architecture 89 Strong Maturity 59 Adequate, capped by Architecture documentation Production Readiness 20 ⚠ Critical, capped by Code Coverage, Test Distribution, Dependency Hygiene, DR & Backup and Outbound HTTP resilience Security and Compliance 38 Weak, capped by Secrets (history), Static Analysis (SAST), Dependency Vulnerabilities, Supply-chain Provenance & Signing, Data Protection and Access Controls Domain Modelling 30 Weak, capped by Aggregate boundaries, Strongly-typed ids, Rich vs anemic model, Domain ↔ infrastructure boundary and Repository granularity Event-Driven 75 Strong Performance 60 Adequate

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

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

If Production Readiness rose from 20 to 70, the lowest score rated Strong, the score would rise from 32 to about 42.

Code composition: what the lines of code are
Business logic 5%Supporting code 26%Generated by tools 69%
New since the last survey: 194 findings

These 194 critical or serious findings weren't in the previous survey, on 6 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 17 findings

These 17 critical or serious findings were in the previous survey, on 6 October 2026, and are gone from this one.

  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Mvc.Abstractions
  • Outbound HTTP resilience · Outbound HTTP without resilience
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: ApiBadRequestResponse source/EventHub.Domain.Shared/HttpResponses/ApiBadRequestResponse.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: ApiForbiddenResponse source/EventHub.Domain.Shared/HttpResponses/ApiForbiddenResponse.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: ApiNotFoundResponse source/EventHub.Domain.Shared/HttpResponses/ApiNotFoundResponse.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: ApiUnauthorizedResponse source/EventHub.Domain.Shared/HttpResponses/ApiUnauthorizedResponse.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: User source/EventHub.Domain/Aggregates/UserAggregate/User.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: Role source/EventHub.Domain/Aggregates/UserAggregate/Entities/Role.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: CalculatePositivePercentageOfReviewDomainEventHandler source/EventHub.Application/DomainEventHandlers/CalculatePositivePercentageOfReviewDomainEventHandler.cs
  • Repository granularity · Repository for a non-root entity: CachedCategoriesRepository → Category source/EventHub.Infrastructure.Persistence/CachedRepositories/CachedCategoriesRepository.cs
  • Repository granularity · Repository for a non-root entity: CachedEventsRepository → Event source/EventHub.Infrastructure.Persistence/CachedRepositories/CachedEventsRepository.cs
  • Repository granularity · Repository for a non-root entity: ConversationsRepository → Conversation source/EventHub.Infrastructure.Persistence/Repositories/ConversationsRepository.cs
  • Repository granularity · Repository for a non-root entity: CouponsRepository → Coupon source/EventHub.Infrastructure.Persistence/Repositories/CouponsRepository.cs
  • Repository granularity · Repository for a non-root entity: NotificationsRepository → Notification source/EventHub.Infrastructure.Persistence/Repositories/NotificationsRepository.cs
  • Repository granularity · Repository for a non-root entity: PaymentsRepository → Payment source/EventHub.Infrastructure.Persistence/Repositories/PaymentsRepository.cs
  • Repository granularity · Repository for a non-root entity: PermissionsRepository → Permission source/EventHub.Infrastructure.Persistence/Repositories/PermissionsRepository.cs
  • Repository granularity · Repository for a non-root entity: TicketsRepository → Ticket source/EventHub.Infrastructure.Persistence/Repositories/TicketsRepository.cs
Rebuild cost: about €36,000 · Estimate
Cost to rebuild€12,000 to €61,000, for 202 to 641 hours of work, about 0.3 person-years for one engineer
Difficulty of the problemVery high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 32. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 20,701 lines of product code, of which 41% is declarations and boilerplate, 42% straight logic and 16% logic with branches

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

Top priorities

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

1
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 10 points · Low effort · Code Coverage
2
Resolve the 1 No tests found finding(s) in Test Distribution.
Raises the score by about 10 points · Low effort · Test Distribution
3
Resolve the 8 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3), REDACTED (3), REDACTED (2).
Raises the score by about 10 points · Low effort · Dependency Hygiene

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €36,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 20 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
One cause behind 85 Domain Modelling findings · Common cause
85 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (23 findings) · Rich vs anemic model (22 findings) · Strongly-typed ids (40 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 1 No automated tests finding(s) in Code Coverage. Of all the actions in this report, it raises the score most for the work it takes: about 10 points for low effort, because it clears the 1 Code Coverage findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — 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.

arch EventHub.Application Application EventHub.Domain Domain EventHub.Application->EventHub.Domain EventHub.Domain.Shared Shared EventHub.Domain->EventHub.Domain.Shared EventHub.Infrastructure Infrastructure EventHub.Infrastructure.Persistence Persistence EventHub.Infrastructure->EventHub.Infrastructure.Persistence EventHub.Infrastructure.Persistence->EventHub.Application EventHub.Infrastructure.Persistence->EventHub.Domain EventHub.Infrastructure.SignalR SignalR EventHub.Infrastructure.SignalR->EventHub.Application EventHub.Infrastructure.SignalR->EventHub.Domain EventHub.Presentation Presentation EventHub.Presentation->EventHub.Infrastructure

Architecture: which parts of the code depend on which

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

205 modules, with 627 dependencies between them. 2 loops run through 19 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 165 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Application.SeedWork.DTOs.Auth2 Application.SeedWork.DTOs.Coupon3 Application.SeedWork.DTOs.Function4 Application.SeedWork.DTOs.User5 Domain.SeedWork.Command6 Domain.SeedWork.Query7 Domain.Shared.SeedWork8 Application.SeedWork.DTOs.Event9 Domain.SeedWork.Entities10 Application.SeedWork.DTOs.Expense11 Application.SeedWork.DTOs.Review12 Application.SeedWork.DTOs.Ticket13 Domain.Aggregates.EventAggregate.ValueObjects14 Domain.Aggregates.UserAggregate.Entities15 Domain.SeedWork.AggregateRoot16 Application.SeedWork.DTOs.Payment17 Domain.Aggregates.CouponAggregate18 Domain.Aggregates.TicketAggregate19 Domain.Aggregates.UserAggregate.ValueObjects20 Application.SeedWork.DTOs.Notification21 Domain.Aggregates.PaymentAggregate22 Domain.Aggregates.NotificationAggregate23 Domain.Aggregates.PaymentAggregate.Entities24 Domain.Aggregates.EventAggregate.Entities25 Domain.Aggregates.EventAggregate26 Domain.Aggregates.ConversationAggregate.Entities27 Domain.Repositories28 Domain.Aggregates.ConversationAggregate29 Domain.SeedWork.Persistence30 Domain.Aggregates.UserAggregate31 Application.SeedWork.Abstractions32 Infrastructure.Persistence.Configurations33 Infrastructure.Persistence.Data34 Application.Commands.Event.CreateEvent35 Application.Commands.Event.UpdateEvent36 Infrastructure.Persistence.CachedRepositories37 Infrastructure.Persistence.Repositories38 Infrastructure.Services39 Presentation.Controllers40 Infrastructure.Persistence.SeedWork.UnitOfWork
1 Application.SeedWork.DTOs.Auth
2 Application.SeedWork.DTOs.Coupon
3 Application.SeedWork.DTOs.Function
4 Application.SeedWork.DTOs.User
5 Domain.SeedWork.Command
6 Domain.SeedWork.Query
7 Domain.Shared.SeedWork
8 Application.SeedWork.DTOs.Event22
9 Domain.SeedWork.Entities1
10 Application.SeedWork.DTOs.Expense1
11 Application.SeedWork.DTOs.Review11
12 Application.SeedWork.DTOs.Ticket2
13 Domain.Aggregates.EventAggregate.ValueObjects4321
14 Domain.Aggregates.UserAggregate.Entities45
15 Domain.SeedWork.AggregateRoot1
16 Application.SeedWork.DTOs.Payment1131
17 Domain.Aggregates.CouponAggregate1111
18 Domain.Aggregates.TicketAggregate11111
19 Domain.Aggregates.UserAggregate.ValueObjects35112
20 Application.SeedWork.DTOs.Notification11
21 Domain.Aggregates.PaymentAggregate1111111
22 Domain.Aggregates.NotificationAggregate1211
23 Domain.Aggregates.PaymentAggregate.Entities1111
24 Domain.Aggregates.EventAggregate.Entities7311161
25 Domain.Aggregates.EventAggregate12111117111
26 Domain.Aggregates.ConversationAggregate.Entities1111
27 Domain.Repositories22126
28 Domain.Aggregates.ConversationAggregate1111
29 Domain.SeedWork.Persistence226
30 Domain.Aggregates.UserAggregate2111121111111
31 Application.SeedWork.Abstractions111
32 Infrastructure.Persistence.Configurations22413111
33 Infrastructure.Persistence.Data4411411171112
34 Application.Commands.Event.CreateEvent43111
35 Application.Commands.Event.UpdateEvent43111
36 Infrastructure.Persistence.CachedRepositories21333
37 Infrastructure.Persistence.Repositories2212626
38 Infrastructure.Services111241
39 Presentation.Controllers43271234211
40 Infrastructure.Persistence.SeedWork.UnitOfWork26111326
Uses a module listed above itPart of a loopThe module itself
1 Application.SeedWork.DTOs.Auth2 Application.SeedWork.DTOs.Coupon3 Application.SeedWork.DTOs.Function4 Application.SeedWork.DTOs.User5 Domain.SeedWork.Command6 Domain.SeedWork.Query7 Domain.Shared.SeedWork8 Application.SeedWork.DTOs.Event9 Domain.SeedWork.Entities10 Application.SeedWork.DTOs.Expense11 Application.SeedWork.DTOs.Review12 Application.SeedWork.DTOs.Ticket13 Domain.Aggregates.EventAggregate.ValueObjects14 Domain.Aggregates.UserAggregate.Entities15 Domain.SeedWork.AggregateRoot16 Application.SeedWork.DTOs.Payment17 Domain.Aggregates.CouponAggregate18 Domain.Aggregates.TicketAggregate19 Domain.Aggregates.UserAggregate.ValueObjects20 Application.SeedWork.DTOs.Notification21 Domain.Aggregates.PaymentAggregate22 Domain.Aggregates.NotificationAggregate23 Domain.Aggregates.PaymentAggregate.Entities24 Domain.Aggregates.EventAggregate.Entities25 Domain.Aggregates.EventAggregate26 Domain.Aggregates.ConversationAggregate.Entities27 Domain.Repositories28 Domain.Aggregates.ConversationAggregate29 Domain.SeedWork.Persistence30 Domain.Aggregates.UserAggregate31 Application.SeedWork.Abstractions32 Infrastructure.Persistence.Configurations33 Infrastructure.Persistence.Data34 Application.Commands.Event.CreateEvent35 Application.Commands.Event.UpdateEvent36 Infrastructure.Persistence.CachedRepositories37 Infrastructure.Persistence.Repositories38 Infrastructure.Services39 Presentation.Controllers40 Infrastructure.Persistence.SeedWork.UnitOfWorkApplication.SeedWork.DTOs.Auth1Application.SeedWork.DTOs.Coupon2Application.SeedWork.DTOs.Function3Application.SeedWork.DTOs.User4Domain.SeedWork.Command5Domain.SeedWork.Query6Domain.Shared.SeedWork7Application.SeedWork.DTOs.Event8Domain.SeedWork.Entities9Application.SeedWork.DTOs.Expense10Application.SeedWork.DTOs.Review11Application.SeedWork.DTOs.Ticket12Domain.Aggregates.EventAggregate.ValueObjects13Domain.Aggregates.UserAggregate.Entities14Domain.SeedWork.AggregateRoot15Application.SeedWork.DTOs.Payment16Domain.Aggregates.CouponAggregate17Domain.Aggregates.TicketAggregate18Domain.Aggregates.UserAggregate.ValueObjects19Application.SeedWork.DTOs.Notification20Domain.Aggregates.PaymentAggregate21Domain.Aggregates.NotificationAggregate22Domain.Aggregates.PaymentAggregate.Entities23Domain.Aggregates.EventAggregate.Entities24Domain.Aggregates.EventAggregate25Domain.Aggregates.ConversationAggregate.Entities26Domain.Repositories27Domain.Aggregates.ConversationAggregate28Domain.SeedWork.Persistence29Domain.Aggregates.UserAggregate30Application.SeedWork.Abstractions31Infrastructure.Persistence.Configurations32Infrastructure.Persistence.Data33Application.Commands.Event.CreateEvent34Application.Commands.Event.UpdateEvent35Infrastructure.Persistence.CachedRepositories36Infrastructure.Persistence.Repositories37Infrastructure.Services38Presentation.Controllers39Infrastructure.Persistence.SeedWork.UnitOfWork4022111124321451113111111111135112111111111121111117311161121111171111111221261111226211112111111111122413111441141117111243111431112133322126261112414327123421126111326+165 more modules (most-connected shown)

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

The Good
D1 · .NET / C# Cyclomatic Complexity 9.3 D2 · .NET / C# Cognitive Complexity 9.3 D3 · .NET / C# God Classes 9.8 D4 · .NET / C# Code Duplication 8.9 D18 · .NET / C# Solution Shape 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 X1 · Repo Async correctness 7.1 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0 X4 · Repo Structured logging 10.0 X5 · Repo Nullable reference types 9.8
The Bad
X2 · Repo Cancellation propagation 6.0
The Ugly
D17 · .NET / C# Explicit Debt 4.8 X18 · Repo Disposal-pattern correctness 3.9

At a glance — Architecture · 89% · Strong ·

The Good
D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 10.0 D26 · .NET / C# Project Cohesion 7.1 D27 · .NET / C# Navigability 10.0 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX2 · Repo Stateful singletons 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.9 AX9 · Repo CQS / query purity 10.0
The Bad
AX10 · Repo Code composition 6.5

At a glance — Maturity · 59% · Adequate · gated by M2 ·

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D21 · .NET / C# Naming Consistency 8.5 D24 · .NET / C# Comment Value 9.0 D34 · .NET / C# Knowledge Freshness 10.0 M1 · Repo Documentation (README) 7.3 M3 · Repo Folder & project structure 8.0 M4 · Repo Documentation accuracy 10.0
The Bad
D19 · .NET / C# Documentation Quality 6.0
The Ugly
D20 · .NET / C# ADR Quality 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 20% · Critical · gated by D8, D9, D12, P5, P7 ·

The Good
D13 · .NET / C# REDACTED Scanning 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 9.7 P1 · Repo CI/CD gates 8.5 P8 · Repo Schema migrations 10.0
The Bad
P2 · Repo Observability 5.8 P4 · Repo Deployment & Rollback 5.0
The Ugly
D8 · .NET / C# Code Coverage 0.0 D12 · .NET / C# Dependency Hygiene 0.0 P3 · Repo Security & performance tooling 4.0 P5 · Repo DR & Backup 0.0 P7 · Repo Outbound HTTP resilience 3.0

At a glance — Security · 38% · Weak · gated by D28, D29, D30, D36, C1, C2 ·

The Good
D31 · .NET / C# IaC & Container Security 7.4 D32 · .NET / C# Data Compliance (PII/GDPR) 9.0 C3 · Repo Audit Trail 7.5 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0
The Ugly
D28 · .NET / C# Secrets (history) 1.0 D29 · .NET / C# Static Analysis (SAST) 0.0 D30 · .NET / C# Dependency Vulnerabilities 2.0 D36 · .NET / C# Supply-chain Provenance & Signing 0.0 C1 · Repo Data Protection 3.0 C2 · Repo Access Controls 1.7 X24 · Repo Document value interpolated into markup unescaped 3.5

At a glance — Domain Modelling · 30% · Weak · gated by DM1, DM2, DM4, DM6, DM7 ·

The Good
DM10 · Repo One transaction, one aggregate 9.2 DM11 · Repo Constructible invalid state 10.0 DM12 · Repo Ambient inputs in the domain 9.9 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 7.6
The Bad
DM5 · Repo Encapsulated state 6.2
The Ugly
DM1 · Repo Aggregate boundaries 1.0 DM2 · Repo Strongly-typed ids 3.0 DM4 · Repo Rich vs anemic model 3.3 DM6 · Repo Domain ↔ infrastructure boundary 1.0 DM7 · Repo Repository granularity 3.0

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

The Good
ED2 · Repo Event/command shape 10.0 ED3 · Repo Event naming 7.0 ED4 · Repo Outbox / dual-write 10.0
The Ugly
ED1 · Repo Handler temporal coupling 4.3

At a glance — Performance · 60% · Adequate ·

The Bad
PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection123High / Critical
A03:2025 — Software Supply Chain Failures20High / Critical
A02:2025 — Security Misconfiguration17High / Critical
A07:2025 — Authentication Failures10High / Critical
A01:2025 — Broken Access Control1Medium

Roadmap

Begin by establishing test coverage for the single uncovered code path and ensuring all components have associated tests. Next, address dependency hygiene by updating deprecated packages, starting with the Domain Shared, Infrastructure, and Domain projects, followed by refreshing outdated dependencies across the Domain Shared, Application, and Infrastructure projects. Finally, resolve the three identified vulnerable dependencies to secure the codebase.

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

Do thisHelpsEffortDimension
Resolve the 1 No automated tests finding(s) in Code Coverage.+9.8 ptsLowCode Coverage
Resolve the 1 No tests found finding(s) in Test Distribution.+9.8 ptsLowTest Distribution
Resolve the 8 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3), REDACTED (3), REDACTED (2).+9.7 ptsLowDependency Hygiene
Resolve the 6 Outdated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED (2), REDACTED (2).+8.8 ptsLowDependency Hygiene
Resolve the 3 Vulnerable finding(s) in Dependency Hygiene.+6.7 ptsLowDependency Hygiene
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.+4.0 ptsMediumDR & Backup
Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED (2).+1.2 ptsLowSecrets (history)
Name the access rules — give each one a named predicate/policy object your guards consult, so the rule set can be reviewed and unit-tested independently of the call sites that enforce it.+2.1 ptsMediumAccess Controls

File quality

Per-file score 0–10 — a quality signature. Of 89 files carrying findings, judged against the Production bar: 6% slop · 45% mixed · 49% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED2.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.9SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.4SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.8SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED4.1MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.1MixedSecrets (history): REDACTED: REDACTED
REDACTED5.1MixedSecrets (history): REDACTED: REDACTED
REDACTED5.1MixedSecrets (history): REDACTED: REDACTED
.editorconfig5.2MixedExplicit Debt: AnalyzerSeverityNone
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedIaC & Container Security: Medium IaC: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED

How the grades work

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

Critical — 152

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 334

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 170

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

Could not be resolved — 6

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

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 89 of 95 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 95 dimensions across the health lenses
D1D2D3D4D5D6D8D9D12D13D14D15D17D18D19D20D21D24D26D27D28D29D30D31D32D34D35D36AX1AX10AX2AX3AX4AX5AX6AX9C1C2C3DM1DM10DM11DM12DM2DM4DM5DM6DM7DM8DM9ED1ED2ED3ED4ED5GD1IC1M1M2M3M4P1P2P3P4P5P7P8PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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

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

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16007-5a46-7406-9ac7-a5a54462e014.

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

Run transparency — what happened this run

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

  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 264 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (20,701 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D32 Data Compliance (PII/GDPR) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `source/EventHub.Application/Queries/Function/GetFunctions/GetFunctionsQuery.cs`, `source/EventHub.Application/Queries/Permission/GetPermissionsCategorizedByRoles/GetPermissionsCategorizedByRolesQuery.cs`, `source/EventHub.Domain/SeedWork/Command/ICommand.cs`, `source/EventHub.Domain/SeedWork/Entities/IEntityAuditBase.cs`, `source/EventHub.Domain/SeedWork/Entities/IEntityBase.cs`, … (+2 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
  • D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — eventhub.db Pulling eventhub.cache Pulling eventhub.hangfire Pulling eventhub.seq Pulling eventhub.seq Error Get "https://registry-1.docker.io/v2/": Forbidden eventhub.minio Error context canceled eventhub.cache Error context canceled eventhub.hangfire Error context canceled eventhub.db Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: eventhub.seq Pulling eventhub.cache Pulling eventhub.minio Pulling eventhub.minio Error Get "https://registry-1.docker.io/v2/": Forbidden eventhub.hangfire Error Get "https://registry-1.docker.io/v2/": Forbidden eventhub.cache Error context canceled eventhub.seq Error context canceled eventhub.db Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
  • DM2 Strongly-typed ids — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
  • DM6 Domain ↔ infrastructure boundary — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 218 further occurrence(s) are not listed individually; the score already reflects all 258.
  • P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
  • X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 154 further occurrence(s) are not listed individually; the score already reflects all 194.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • 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.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
  • 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.
  • 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.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.

The LLM boundary

LLM-set scores this run (6): D19, D21, D24, D26, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity9.3 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was GetCreatedEventsByUserIdQueryHandler.Handle at 21.

GetCreatedEventsByUserIdQueryHandler.Handle (cyclomatic 21)source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:26
PagingHelper.QueryPaginate (cyclomatic 17)source/EventHub.Domain.Shared/Helpers/PagingHelper.cs:79
CreateEventCommandHandler.Handle (cyclomatic 16)source/EventHub.Application/Commands/Event/CreateEvent/CreateEventCommandHandler.cs:65
GetPaginatedEventsQueryHandler.Handle (cyclomatic 16)source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs:21

What to do

  1. Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with GetCreatedEventsByUserIdQueryHandler.Handle (cyclomatic 21), PagingHelper.QueryPaginate (cyclomatic 17), CreateEventCommandHandler.Handle (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity9.3 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

2 method(s) exceeded the cognitive complexity threshold of 15; the worst was PagingHelper.QueryPaginate at 25.

PagingHelper.QueryPaginate (cognitive 25)source/EventHub.Domain.Shared/Helpers/PagingHelper.cs:79
CreateEventCommandHandler.Handle (cognitive 18)source/EventHub.Application/Commands/Event/CreateEvent/CreateEventCommandHandler.cs:65

What to do

  1. Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with PagingHelper.QueryPaginate (cognitive 25), CreateEventCommandHandler.Handle (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

3 god class(es) detected.

MethodTooLong: ApplicationDbContextSeed.SeedPermissionsource/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:266
ClassTooLong: ApplicationDbContextSeedsource/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs
FileTooLong: Data/ApplicationDbContextSeed.cssource/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs

What to do

  1. Resolve the 1 MethodTooLong finding(s) in God Classes — start with ApplicationDbContextSeed.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 ClassTooLong finding(s) in God Classes — start with ApplicationDbContextSeed.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 FileTooLong finding(s) in God Classes — start with ApplicationDbContextSeed.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D4 · Code Duplication8.9 / 10Strong✓ Tool-verified

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

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

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

48 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (7 lines × 2) · ×6source/EventHub.Application/Commands/User/ChangePassword/ChangePasswordCommandValidator.cs:17
Duplicated block (11 lines × 2) · ×5source/EventHub.Domain/Aggregates/EventAggregate/Entities/TicketType.cs:21
Duplicated block (6 lines × 2) · ×4source/EventHub.Application/Commands/Event/FavouriteEvent/FavouriteEventCommandHandler.cs:27
Duplicated block (12 lines × 2) · ×3source/EventHub.Application/Queries/User/GetPaginatedFollowers/GetPaginatedFollowersQueryHandler.cs:25
Duplicated block (14 lines × 2) · ×2source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:27

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

What to do

  1. Resolve the 6 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with CachedRepositoryBase.cs (2), ChangePasswordCommandValidator.cs, GetPaginatedPaymentsQueryHandler.cs. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 5 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with TicketType.cs, CreateUserDto.cs, CreateEventCommand.cs. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 4 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with CachedRepositoryBase.cs (2), FavouriteEventCommandHandler.cs, GetReviewStatisticsByCreatedEventsQueryHandler.cs. — One of this dimension's main actionable groups (4 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

Off the main sequence: EventHub.Domain.SharedREDACTED:1

✓ On the Gold path — maintain.

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 29 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D8 · Code Coverage0.0 / 10Critical✓ 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.

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

No automated tests — no test code was found in this repository.

No automated tests

What to do

  1. Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
  2. Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D9 · Test Distribution0.0 / 10Critical✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

No test suite found.

No tests found

What to do

  1. Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).

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

D12 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

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.

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

52 outdated, 3 vulnerable, 7 deprecated packages.

Vulnerable: AutoMapper · ×3
Deprecated: Microsoft.AspNetCore.Authentication.Abstractions · ×8REDACTED:4
Outdated: Microsoft.AspNetCore.Http.Features · ×6REDACTED:5
Outdated: FluentValidation · ×46

What to do

  1. Resolve the 8 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 6 Outdated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (6 recommendation-level).
  3. Resolve the 3 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 issue-level).
  4. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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

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

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

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 266 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 57 direct `PackageReference`(s), and 193 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt4.8 / 10Weak✓ Tool-verified

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

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

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

55 deducted debt markers + 14 dead symbols across 20701 LoC in the .NET projects (2.6/KLoC) → score 4.8.

AnalyzerSeverityNone · ×55.editorconfig:231
Dead code: CacheKey · ×14source/EventHub.Domain.Shared/Constants/CacheKey.cs:3

What to do

  1. Resolve the 55 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (55). — One of this dimension's main actionable groups (55 issue-level).
  2. Resolve the 14 Dead code finding(s) in Explicit Debt — start with CacheKey.cs, PagingHelper.cs, ApiForbiddenResponse.cs. — One of this dimension's main actionable groups (14 warning-level).
  3. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

6 projects, 649 source files, 20701 hand-written lines of code (20701 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 51632 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 6 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation QualityAdequate◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's root README is an informative overview of what EventHub does and its structure. It gives a one-line status line that the project itself now outdated and directs readers to the GitHub repo, then dives into a well-organized Solution Structure diagram showing deploy/, Solution Items/, and source/ folders with explanations for each. The document also begins outlining architecture/design patterns (Applied Architecture and Design Patterns; Clean Architecture; Repository Pattern; Unit of Work Pattern; Domain-Driven Design (DDD); CQRS Pattern; Transactional Outbox Pattern & Idempotency; Additional Design Patterns) before being cut by the scanner, so those sections are present in the outline but not shown. The visible content is clear and complete for an overview document, with a strong structure and a helpful star-giving section.

XML-doc coverage: EventHub.Domain.Shared · ×6REDACTED

What to do

  1. Improve Documentation Quality — currently 6.0/10. — The repository's root README is an informative overview of what EventHub does and its structure. It gives a one-line status line that the project itself now outdated and directs readers to the GitHub repo, then dives into a well-organized Solution Structure diagram showing deploy/, Solution Items/, and source/ folders with explanations for each. The document also begins outlining architecture/design patterns (Applied Architecture and Design Patterns; Clean Architecture; Repository Pattern; Unit of Work Pattern; Domain-Driven Design (DDD); CQRS Pattern; Transactional Outbox Pattern & Idempotency; Additional Design Patterns) before being cut by the scanner, so those sections are present in the outline but not shown. The visible content is clear and complete for an overview document, with a strong structure and a helpful star-giving section.

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

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

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

D21 · Naming ConsistencyStrong◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

1 naming inconsistencies across 200 sampled symbols.

Typo in class name: 'SignUpCommnadHandler' contains a typo ('Commnad' instead of 'Command'). This breaks consistency with the standard naming convention observed in other handlers (e.g., 'CreateUserCommandHandler', 'UpdateReviewCommandHandler') and the command type itself ('SignUpCommand').

What to do

  1. Resolve the 1 Typo in class name finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment ValueExemplary◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.

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

32 valuable / 1 redundant across 90 sampled comments; 1 shown with locations.

redundant commentREDACTED:15

✓ On the Gold path — maintain.

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

D26 · Project Cohesion7.1 / 10Strong✓ Tool-verified

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

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

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

1 of 7 projects flagged as possibly oversized/incoherent.

Split EventHub.Application

What to do

  1. Resolve the 1 Split EventHub.Application finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

D27 · Navigability10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

Pass-through layer · ×2source/EventHub.Infrastructure/Services/HangfireService.cs:13

✓ On the Gold path — maintain.

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

D28 · Secrets (history)1.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

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

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

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

123 finding(s): 0 critical, 3 high, 118 medium, 2 low. semgrep hit a parse error in 7 file(s) — `source/EventHub.Application/Queries/Function/GetFunctions/GetFunctionsQuery.cs` (line 12), `source/EventHub.Application/Queries/Permission/GetPermissionsCategorizedByRoles/GetPermissionsCategorizedByRolesQuery.cs` (line 15), `source/EventHub.Domain/SeedWork/Command/ICommand.cs` (lines 15–20), `source/EventHub.Domain/SeedWork/Entities/IEntityAuditBase.cs` (line 3), `source/EventHub.Domain/SeedWork/Entities/IEntityBase.cs` (line 3), … (+2 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 1 of those file(s) — `source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContext.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 117 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (18), REDACTED (12), REDACTED (10). — One of this dimension's main actionable groups (117 warning-level).
  2. Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D30 · Dependency Vulnerabilities2.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 issue-level).
  2. Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D31 · IaC & Container Security7.4 / 10Adequategated by 4 critical findings✓ Tool-verified

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

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

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

17 finding(s): 0 critical, 4 high, 12 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

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

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

D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.

Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.

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

1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 7 file(s) — `source/EventHub.Application/Queries/Function/GetFunctions/GetFunctionsQuery.cs`, `source/EventHub.Application/Queries/Permission/GetPermissionsCategorizedByRoles/GetPermissionsCategorizedByRolesQuery.cs`, `source/EventHub.Domain/SeedWork/Command/ICommand.cs`, `source/EventHub.Domain/SeedWork/Entities/IEntityAuditBase.cs`, `source/EventHub.Domain/SeedWork/Entities/IEntityBase.cs`, … (+2 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.

REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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

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

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

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 74 of the 650 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

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

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

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

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

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

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

0/3 supply-chain integrity signals present (provenance, signing, SBOM).

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

Frontend & cross-cutting dimensions

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

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

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

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

AX10 · Code composition6.5 / 10Adequate✓ Tool-verified

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

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

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

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

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

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

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

  • The namespaces EventHub.Domain.Aggregates.ConversationAggregate ↔ EventHub.Domain.Aggregates.ConversationAggregate.Entities ↔ EventHub.Domain.Aggregates.CouponAggregate ↔ EventHub.Domain.Aggregates.CouponAggregate.ValueObjects ↔ EventHub.Domain.Aggregates.EventAggregate ↔ EventHub.Domain.Aggregates.EventAggregate.Entities ↔ EventHub.Domain.Aggregates.EventAggregate.ValueObjects ↔ EventHub.Domain.Aggregates.NotificationAggregate ↔ EventHub.Domain.Aggregates.PaymentAggregate ↔ EventHub.Domain.Aggregates.PaymentAggregate.Entities ↔ EventHub.Domain.Aggregates.TicketAggregate ↔ EventHub.Domain.Aggregates.UserAggregate ↔ EventHub.Domain.Aggregates.UserAggregate.Entities ↔ EventHub.Domain.Aggregates.UserAggregate.ValueObjects ↔ EventHub.Domain.SeedWork.AggregateRoot ↔ EventHub.Domain.SeedWork.Entities depend on each other. The lightest dependency in the cycle is EventHub.Domain.Aggregates.ConversationAggregate → EventHub.Domain.Aggregates.ConversationAggregate.Entities (EventHub.Domain.Aggregates.ConversationAggregate.Conversation → EventHub.Domain.Aggregates.ConversationAggregate.Entities.Message, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:3
  • The namespaces EventHub.Domain.CachedRepositories ↔ EventHub.Domain.Repositories ↔ EventHub.Domain.SeedWork.Persistence depend on each other. The lightest dependency in the cycle is EventHub.Domain.CachedRepositories → EventHub.Domain.SeedWork.Persistence (EventHub.Domain.CachedRepositories.ICachedCategoriesRepository → EventHub.Domain.SeedWork.Persistence.ICachedRepositoryBase, 3 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — source/EventHub.Domain/CachedRepositories/ICachedCategoriesRepository.cs:2

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

  • `IRepositoryBase<T>` declares 21 members under just 15 distinct name(s): `Update`, `FindAll`, `FindAll`, `FindByCondition`, `FindByCondition`, `PaginatedFind`, `PaginatedFind`, `PaginatedFindByCondition`, `PaginatedFindByCondition`, `ExistAsync`, `ExistAsync`, `Count`, `CountAsync`, `GetByIdAsync`, `GetByIdAsync`, `CreateAsync`, `CreateListAsync`, `Delete`, `DeleteList`, `SoftDelete`, `Restore`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 21 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 21 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — source/EventHub.Domain/SeedWork/Persistence/IRepositoryBase.cs:16
  • `IUnitOfWork` declares 33 members: `CommitAsync`, `BeginTransactionAsync`, `EndTransactionAsync`, `RollbackTransactionAsync`, `Categories`, `CommandInFunctions`, `Commands`, `Conversations`, `EmailAttachments`, `EmailContents`, `EventCategories`, `Events`, `EventSubImages`, `FavouriteEvents`, `Functions`, `Invitations`, `Messages`, `PaymentItems`, `Payments`, `Permissions`, `Reasons`, `Reviews`, `Tickets`, `TicketTypes`, `UserFollowers`, `Coupons`, `EventCoupons`, `Expenses`, `SubExpenses`, `Notifications`, `CachedCategories`, `CachedEvents`, `CachedReviews`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — source/EventHub.Domain/SeedWork/Persistence/IUnitOfWork.cs:15

What to do

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

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

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

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

C1 · Data Protection3.0 / 10Weak✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

  • 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.).
C2 · Access Controls1.7 / 10Critical✓ Tool-verified

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.

  • Authorization IS enforced here (by imperative guard methods that throw on violation) — this is NOT a claim that the code is unprotected. What's missing is a NAMED rule set: the guards encode the access rules inline, so the rules can't be listed, reviewed or tested apart from the call sites that apply them. Recommendation, not a defect.
  • Only 1 imperative guard call site(s) — too few to demonstrate default-deny across handlers.

What to do

  • Name the access rules — give each one a named predicate/policy object your guards consult, so the rule set can be reviewed and unit-tested independently of the call sites that enforce it.
  • Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.
C3 · Audit Trail7.5 / 10Strong✓ Tool-verified

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

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

  • 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.
DM1 · Aggregate boundaries1.0 / 10Critical✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

  • `Conversation` references the aggregate root `Event` directly (via `Event`) — hold its `EventId` instead. — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:26
  • `Conversation` references the aggregate root `User` directly (via `Host`) — hold its `UserId` instead. — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:30
  • `Conversation` references the aggregate root `User` directly (via `User`) — hold its `UserId` instead. — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:34
  • `Coupon` references the aggregate root `User` directly (via `Author`) — hold its `UserId` instead. — source/EventHub.Domain/Aggregates/CouponAggregate/Coupon.cs:45
  • `Coupon` references the aggregate root `Payment` directly (via `Payments`) — hold its `PaymentId` instead. — source/EventHub.Domain/Aggregates/CouponAggregate/Coupon.cs:51
  • `Event` references the aggregate root `User` directly (via `Author`) — hold its `UserId` instead. — source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:76
  • `Event` references the aggregate root `Category` directly (via `Categories`) — hold its `CategoryId` instead. — source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:84
  • `Event` references the aggregate root `Payment` directly (via `Payments`) — hold its `PaymentId` instead. — source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:94
  • `Event` references the aggregate root `Conversation` directly (via `Conversations`) — hold its `ConversationId` instead. — source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:98
  • `Event` references the aggregate root `Ticket` directly (via `Tickets`) — hold its `TicketId` instead. — source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:102
  • `Notification` references the aggregate root `User` directly (via `TargetUser`) — hold its `UserId` instead. — source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:43
  • `Notification` references the aggregate root `Payment` directly (via `Payment`) — hold its `PaymentId` instead. — source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:51
  • `Payment` references the aggregate root `User` directly (via `Author`) — hold its `UserId` instead. — source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:66
  • `Payment` references the aggregate root `Event` directly (via `Event`) — hold its `EventId` instead. — source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:70
  • `Payment` references the aggregate root `Coupon` directly (via `Coupon`) — hold its `CouponId` instead. — source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:74
  • `Payment` references the aggregate root `Ticket` directly (via `Tickets`) — hold its `TicketId` instead. — source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:78
  • `Ticket` references the aggregate root `Event` directly (via `Event`) — hold its `EventId` instead. — source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:53
  • `Ticket` references the aggregate root `User` directly (via `User`) — hold its `UserId` instead. — source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:57
  • `Ticket` references the aggregate root `Payment` directly (via `Payment`) — hold its `PaymentId` instead. — source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:61
  • `User` references the aggregate root `Event` directly (via `Events`) — hold its `EventId` instead. — source/EventHub.Domain/Aggregates/UserAggregate/User.cs:74
  • `User` references the aggregate root `Payment` directly (via `Payments`) — hold its `PaymentId` instead. — source/EventHub.Domain/Aggregates/UserAggregate/User.cs:76
  • `User` references the aggregate root `Conversation` directly (via `UserConversations`) — hold its `ConversationId` instead. — source/EventHub.Domain/Aggregates/UserAggregate/User.cs:82
  • `User` references the aggregate root `Conversation` directly (via `HostConversations`) — hold its `ConversationId` instead. — source/EventHub.Domain/Aggregates/UserAggregate/User.cs:83
  • `User` references the aggregate root `Ticket` directly (via `Tickets`) — hold its `TicketId` instead. — source/EventHub.Domain/Aggregates/UserAggregate/User.cs:87
  • `User` references the aggregate root `Notification` directly (via `Notifications`) — hold its `NotificationId` instead. — source/EventHub.Domain/Aggregates/UserAggregate/User.cs:89

What to do

  • Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate9.2 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.

Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.

  • `FavouriteEventCommandHandler.Handle` saves `IRepositoryBase`, `UserManager` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — source/EventHub.Application/Commands/Event/FavouriteEvent/FavouriteEventCommandHandler.cs:25
  • `PermanentlyDeleteEventCommandHandler.Handle` saves `EmailAttachment`, `Event` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — source/EventHub.Application/Commands/Event/PermanentlyDeleteEvent/PermanentlyDeleteEventCommandHandler.cs:39
  • `UnfavouriteEventCommandHandler.Handle` saves `IRepositoryBase`, `UserManager` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — source/EventHub.Application/Commands/Event/UnfavouriteEvent/UnfavouriteEventCommandHandler.cs:26
  • `ValidateSessionCommandHandler.Handle` saves `Coupon`, `Event` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — source/EventHub.Application/Commands/Payment/ValidateSession/ValidateSessionCommandHandler.cs:33
  • `UnfollowCommandHandler.Handle` saves `IRepositoryBase`, `UserManager` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — source/EventHub.Application/Commands/User/Unfollow/UnfollowCommandHandler.cs:25

What to do

  • Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM11 · Constructible invalid state10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

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

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

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

  • `TicketCodeGenerator` reads `DateTime.Now` inside `GenerateTicketCode` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has. — source/EventHub.Domain.Shared/Helpers/TicketCodeGenerator.cs:12

What to do

  • Route the listed sites through the clock abstraction this repo already declares, so the domain's rules can be exercised at a chosen instant.
DM2 · Strongly-typed ids3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.

Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.

Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.

  • `Conversation.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:18
  • `Conversation.HostId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:20
  • `Conversation.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:22
  • `Conversation.LastMessageId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:24
  • `Message.ReceiverId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:42
  • `Message.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:49
  • `Message.ConversationId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:52
  • `Coupon.AuthorId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/CouponAggregate/Coupon.cs:43
  • `Event.AuthorId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:72
  • `EmailContent.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/EmailContent.cs:21
  • `EventSubImage.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/EventSubImage.cs:15
  • `Expense.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/Expense.cs:16
  • `Reason.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/Reason.cs:15
  • `Review.AuthorId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/Review.cs:17
  • `Review.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/Review.cs:20
  • `TicketType.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/TicketType.cs:18
  • `EmailAttachment.EmailContentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/EmailAttachment.cs:16
  • `SubExpense.ExpenseId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/SubExpense.cs:16
  • `Notification.TargetUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:31
  • `Notification.InvitationId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:35
  • `Notification.PaymentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:37
  • `Notification.UserFollowerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:39
  • `Payment.PaymentIntentId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:54
  • `Payment.SessionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:56
  • `Payment.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:58
  • `Payment.AuthorId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:61
  • `Payment.CouponId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:64
  • `PaymentItem.TicketTypeId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/PaymentAggregate/Entities/PaymentItem.cs:17
  • `PaymentItem.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/PaymentAggregate/Entities/PaymentItem.cs:20
  • `PaymentItem.PaymentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/PaymentAggregate/Entities/PaymentItem.cs:23
  • `Ticket.TicketTypeId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:38
  • `Ticket.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:40
  • `Ticket.AuthorId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:42
  • `Ticket.PaymentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:44
  • `Function.ParentId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/UserAggregate/Entities/Function.cs:28
  • `Invitation.InviterId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Invitation.cs:16
  • `Invitation.InvitedId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Invitation.cs:19
  • `Invitation.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Invitation.cs:22
  • `Permission.FunctionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Permission.cs:13
  • `Permission.RoleId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Permission.cs:16

What to do

  • Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model3.3 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

  • `Conversation` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:11
  • `Message` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:10
  • `Coupon` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/CouponAggregate/Coupon.cs:12
  • `Category` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/Category.cs:8
  • `EmailContent` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/EmailContent.cs:9
  • `EventSubImage` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/EventSubImage.cs:8
  • `Expense` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/Expense.cs:9
  • `Reason` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/Reason.cs:8
  • `Review` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/Review.cs:10
  • `TicketType` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/EventAggregate/Entities/TicketType.cs:11
  • `EmailAttachment` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/EmailAttachment.cs:9
  • `SubExpense` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/SubExpense.cs:9
  • `Notification` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:13
  • `Payment` is an aggregate/entity with 19 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:16
  • `PaymentItem` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/PaymentAggregate/Entities/PaymentItem.cs:10
  • `Ticket` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:14
  • `User` is an aggregate/entity with 30 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/UserAggregate/User.cs:23
  • `Command` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/UserAggregate/Entities/Command.cs:8
  • `Function` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/UserAggregate/Entities/Function.cs:9
  • `Invitation` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Invitation.cs:9
  • `Permission` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Permission.cs:9
  • `UserFollower` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/UserFollower.cs:8

What to do

  • Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state6.2 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

  • `Conversation` exposes publicly writable state (Id, EventId, HostId, UserId, LastMessageId, Event, and 4 more). — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:11
  • `Message` exposes publicly writable state (Id, Content, ImageUrl, ImageFileName, VideoUrl, VideoFileName, and 8 more). — source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:10
  • `Coupon` exposes publicly writable state (Id, Name, Description, Quantity, MinPrice, PercentValue, and 8 more). — source/EventHub.Domain/Aggregates/CouponAggregate/Coupon.cs:12
  • `Event` exposes publicly writable state (Id, CoverImageFileName, CoverImageUrl, Name, Description, Location, and 26 more). — source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:22
  • `Category` exposes publicly writable state (Id, Name, IconImageUrl, IconImageFileName, Color, EventCategories). — source/EventHub.Domain/Aggregates/EventAggregate/Entities/Category.cs:8
  • `EmailContent` exposes publicly writable state (Id, Content, EventId, Event, EmailAttachments). — source/EventHub.Domain/Aggregates/EventAggregate/Entities/EmailContent.cs:9
  • `EventSubImage` exposes publicly writable state (Id, EventId, ImageUrl, ImageFileName, Event). — source/EventHub.Domain/Aggregates/EventAggregate/Entities/EventSubImage.cs:8
  • `Expense` exposes publicly writable state (Id, EventId, Title, Total, Event, SubExpenses). — source/EventHub.Domain/Aggregates/EventAggregate/Entities/Expense.cs:9
  • `Reason` exposes publicly writable state (Id, EventId, Name, Event). — source/EventHub.Domain/Aggregates/EventAggregate/Entities/Reason.cs:8
  • `Review` exposes publicly writable state (Id, AuthorId, EventId, Content, IsPositive, SentimentPercentage, and 3 more). — source/EventHub.Domain/Aggregates/EventAggregate/Entities/Review.cs:10
  • `TicketType` exposes publicly writable state (Id, EventId, Name, Quantity, Price, NumberOfSoldTickets, and 3 more). — source/EventHub.Domain/Aggregates/EventAggregate/Entities/TicketType.cs:11
  • `EmailAttachment` exposes publicly writable state (Id, EmailContentId, AttachmentFileName, AttachmentUrl, EmailContent). — source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/EmailAttachment.cs:9
  • `SubExpense` exposes publicly writable state (Id, ExpenseId, Name, Price, Expense). — source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/SubExpense.cs:9
  • `Notification` exposes publicly writable state (Id, Title, Message, Type, Timestamp, TargetUserId, and 9 more). — source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:13
  • `Payment` exposes publicly writable state (Id, TicketQuantity, CustomerName, CustomerPhone, CustomerEmail, TotalPrice, and 13 more). — source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:16
  • `PaymentItem` exposes publicly writable state (Id, TicketTypeId, EventId, PaymentId, Name, Quantity, and 5 more). — source/EventHub.Domain/Aggregates/PaymentAggregate/Entities/PaymentItem.cs:10
  • `Ticket` exposes publicly writable state (Id, TicketNo, CustomerName, CustomerPhone, CustomerEmail, TicketTypeId, and 8 more). — source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:14
  • `User` exposes publicly writable state (FullName, Dob, Gender, Bio, AvatarUrl, AvatarFileName, and 24 more). — source/EventHub.Domain/Aggregates/UserAggregate/User.cs:23
  • `Command` exposes publicly writable state (Id, Name, CommandInFunctions, Permissions). — source/EventHub.Domain/Aggregates/UserAggregate/Entities/Command.cs:8
  • `Function` exposes publicly writable state (Id, Name, Url, SortOrder, ParentId, Parent, and 2 more). — source/EventHub.Domain/Aggregates/UserAggregate/Entities/Function.cs:9
  • `Invitation` exposes publicly writable state (Id, InviterId, InvitedId, EventId, Inviter, Invited, and 1 more). — source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Invitation.cs:9
  • `Permission` exposes publicly writable state (FunctionId, RoleId, CommandId, Function, Role, Command). — source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Permission.cs:9
  • `UserFollower` exposes publicly writable state (Id, FollowerId, FollowedId, Follower, Followed). — source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/UserFollower.cs:8

What to do

  • Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary1.0 / 10Critical✓ Tool-verified

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

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

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

  • `CalculatePositivePercentageOfReviewDomainEventHandler` (domain layer) names `IHttpClientFactory` from `System.Net.Http` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — source/EventHub.Application/DomainEventHandlers/CalculatePositivePercentageOfReviewDomainEventHandler.cs:12, source/EventHub.Application/DomainEventHandlers/CalculatePositivePercentageOfReviewDomainEventHandler.cs:14
  • `CalculatePositivePercentageOfReviewDomainEventHandler` (domain layer) names `HttpClient` from `System.Net.Http` — a HTTP type (in a method body). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Application/DomainEventHandlers/CalculatePositivePercentageOfReviewDomainEventHandler.cs:28
  • `CalculatePositivePercentageOfReviewDomainEventHandler` (domain layer) names `HttpResponseMessage` from `System.Net.Http` — a HTTP type (in a method body). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Application/DomainEventHandlers/CalculatePositivePercentageOfReviewDomainEventHandler.cs:29
  • `ApiBadRequestResponse` (domain layer) names `ModelStateDictionary` from `Microsoft.AspNetCore.Mvc.ModelBinding` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain.Shared/HttpResponses/ApiBadRequestResponse.cs:8
  • `ApiBadRequestResponse` (domain layer) names `IdentityResult` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain.Shared/HttpResponses/ApiBadRequestResponse.cs:20
  • `ApiForbiddenResponse` (domain layer) names `ModelStateDictionary` from `Microsoft.AspNetCore.Mvc.ModelBinding` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain.Shared/HttpResponses/ApiForbiddenResponse.cs:8
  • `ApiForbiddenResponse` (domain layer) names `IdentityResult` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain.Shared/HttpResponses/ApiForbiddenResponse.cs:20
  • `ApiNotFoundResponse` (domain layer) names `ModelStateDictionary` from `Microsoft.AspNetCore.Mvc.ModelBinding` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain.Shared/HttpResponses/ApiNotFoundResponse.cs:8
  • `ApiNotFoundResponse` (domain layer) names `IdentityResult` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain.Shared/HttpResponses/ApiNotFoundResponse.cs:20
  • `ApiUnauthorizedResponse` (domain layer) names `ModelStateDictionary` from `Microsoft.AspNetCore.Mvc.ModelBinding` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain.Shared/HttpResponses/ApiUnauthorizedResponse.cs:8
  • `ApiUnauthorizedResponse` (domain layer) names `IdentityResult` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain.Shared/HttpResponses/ApiUnauthorizedResponse.cs:20
  • `PaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×5) — source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:33, source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:48, source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:62, …
  • `EventPaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×5) — source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:151, source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:154, source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:157, …
  • `NotificationPaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:169
  • `Conversation` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:11
  • `Conversation` (domain layer) names `KeyAttribute` from `System.ComponentModel.DataAnnotations` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:14
  • `Conversation` (domain layer) names `DatabaseGeneratedAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:15
  • `Conversation` (domain layer) names `ForeignKeyAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×4) — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:26, source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:30, source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:34, …
  • `Conversation` (domain layer) names `DeleteBehaviorAttribute` from `Microsoft.EntityFrameworkCore` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×3) — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:27, source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:31, source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:35
  • `Conversation` (domain layer) names `User` from `EventHub.Domain.Aggregates.UserAggregate` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:32, source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:36
  • `Message` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:10
  • `Message` (domain layer) names `KeyAttribute` from `System.ComponentModel.DataAnnotations` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:13
  • `Message` (domain layer) names `DatabaseGeneratedAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:14
  • `Message` (domain layer) names `ColumnAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×2) — source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:18, source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:21

What to do

  • Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM7 · Repository granularity3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether repositories are per aggregate root (not per child entity) and keep the persistence query handle behind the contract, so the root's invariants can't be bypassed.

Method: Roslyn (DDD-gated): repository abstraction detection; repositories over non-aggregate-root entities flagged, and (C#/VB) repository INTERFACES whose members return a live persistence query handle (IQueryable/DbSet/IMongoQueryable) — implementations and specification evaluators are out of population by design, since composing a query internally is what an implementation is for. Deterministic, DDD-native.

Coverage: Population: repositories + aggregate roots by NAME convention; per-root repository rule checked within the set.

  • `CachedReviewsRepository` is a repository over `Review`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Review` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/CachedRepositories/CachedReviewsRepository.cs:10
  • `CommandsRepository` is a repository over `Command`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Command` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/CommandsRepository.cs:10
  • `EmailAttachmentsRepository` is a repository over `EmailAttachment`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmailAttachment` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/EmailAttachmentsRepository.cs:9
  • `EmailContentsRepository` is a repository over `EmailContent`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmailContent` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/EmailContentsRepository.cs:9
  • `EventSubImagesRepository` is a repository over `EventSubImage`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EventSubImage` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/EventSubImagesRepository.cs:9
  • `ExpensesRepository` is a repository over `Expense`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Expense` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/ExpensesRepository.cs:8
  • `FunctionsRepository` is a repository over `Function`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Function` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/FunctionsRepository.cs:10
  • `InvitationsRepository` is a repository over `Invitation`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Invitation` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/InvitationsRepository.cs:9
  • `MessagesRepository` is a repository over `Message`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Message` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/MessagesRepository.cs:9
  • `PaymentItemsRepository` is a repository over `PaymentItem`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `PaymentItem` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/PaymentItemsRepository.cs:9
  • `ReasonsRepository` is a repository over `Reason`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Reason` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/ReasonsRepository.cs:9
  • `SubExpensesRepository` is a repository over `SubExpense`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `SubExpense` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/SubExpensesRepository.cs:8
  • `TicketTypesRepository` is a repository over `TicketType`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `TicketType` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/TicketTypesRepository.cs:9
  • `UserFollowersRepository` is a repository over `UserFollower`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `UserFollower` through its owning aggregate instead. — source/EventHub.Infrastructure.Persistence/Repositories/UserFollowersRepository.cs:9
  • `IEventsRepository` returns `IQueryable` from `GetDeletedEvents`, `GetDeletedEvents`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked. — source/EventHub.Domain/Repositories/IEventsRepository.cs:8
  • `IRepositoryBase` returns `IQueryable` from `FindAll`, `FindAll`, `FindByCondition`, `FindByCondition`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked. — source/EventHub.Domain/SeedWork/Persistence/IRepositoryBase.cs:16

What to do

  • Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
DM8 · Value-object opportunities10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

DM9 · Scattered domain decisions7.6 / 10Strong✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

  • EventHub.Domain.Aggregates.EventAggregate.Event's [EndTime, StartTime] are judged in EventHub.Application.Queries.Event.GetCreatedEventsByUserId.GetCreatedEventsByUserIdQueryHandler, EventHub.Application.Queries.Event.GetFavouriteEventsByUserId.GetFavouriteEventsByUserIdQueryHandler, EventHub.Application.Queries.Event.GetPaginatedEvents.GetPaginatedEventsQueryHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
  • EventHub.Domain.Aggregates.EventAggregate.ValueObjects.FavouriteEvent's [EventId, UserId] are judged in EventHub.Application.Commands.Event.FavouriteEvent.FavouriteEventCommandHandler, EventHub.Application.Commands.Event.UnfavouriteEvent.UnfavouriteEventCommandHandler, EventHub.Application.Queries.Event.GetEventById.GetEventByIdQueryHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
  • EventHub.Domain.Aggregates.UserAggregate.ValueObjects.CommandInFunction's [CommandId, FunctionId] are judged in EventHub.Application.Commands.Permission.DisableCommandInFunction.DisableCommandInFunctionCommandHandler, EventHub.Application.Commands.Permission.EnableCommandInFunction.EnableCommandInFunctionCommandHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
  • EventHub.Domain.Aggregates.UserAggregate.ValueObjects.Permission's [FunctionId, RoleId] are judged in EventHub.Application.Commands.Permission.AddFunctionToRole.AddFunctionToRoleCommandHandler, EventHub.Application.Commands.Permission.RemoveFunctionFromRole.RemoveFunctionFromRoleCommandHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
  • EventHub.Domain.Aggregates.UserAggregate.ValueObjects.UserFollower's [FollowedId, FollowerId] are judged in EventHub.Application.Commands.User.Follow.FollowCommandHandler, EventHub.Application.Commands.User.Unfollow.UnfollowCommandHandler, EventHub.Application.Queries.Event.GetEventById.GetEventByIdQueryHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
  • EventHub.Domain.Shared.SeedWork.DateRange's [EndDate, StartDate] are judged in EventHub.Application.Queries.Event.GetCreatedEventsByUserId.GetCreatedEventsByUserIdQueryHandler, EventHub.Application.Queries.Event.GetPaginatedEvents.GetPaginatedEventsQueryHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.

What to do

  • Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
ED1 · Handler temporal coupling4.3 / 10Weak✓ Tool-verified

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

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

  • `CalculatePositivePercentageOfReviewDomainEventHandler.Handle` makes a synchronous remote call (an HTTP call) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler. — source/EventHub.Application/DomainEventHandlers/CalculatePositivePercentageOfReviewDomainEventHandler.cs:20

What to do

  • Remove synchronous remote calls from message handlers — react by publishing further messages, so services stay temporally decoupled.
ED2 · Event/command shape10.0 / 10Exemplary✓ Tool-verified

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.

ED3 · Event naming7.0 / 10Strong✓ Tool-verified

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

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

  • `CalculatePositivePercentageOfReviewDomainEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — source/EventHub.Domain/Events/CalculatePositivePercentageOfReviewDomainEvent.cs:5

What to do

  • Name events in the past tense — they record facts that already happened.
ED4 · Outbox / dual-write10.0 / 10Exemplary○ Nothing flagged

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.

ED5 · Idempotency9.7 / 10Exemplary◐ Sampled · advisory

Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.

Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.

Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.

  • `CreateSubExpense.CreateSubExpenseCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — source/EventHub.Application/Commands/Expense/CreateSubExpense/CreateSubExpenseCommandHandler.cs:19
  • `DeleteSubExpense.DeleteSubExpenseCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — source/EventHub.Application/Commands/Expense/DeleteSubExpense/DeleteSubExpenseCommandHandler.cs:16

What to do

  • Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add a README to the 7 of 7 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

What to do

  • Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

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.

P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified

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

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

What to do

  • Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P2 · Observability5.8 / 10Adequate✓ Tool-verified

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

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

What to do

  • Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling4.0 / 10Weak✓ Tool-verified

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

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

What to do

  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

  • Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.

What to do

  • Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified

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

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

  • A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.

What to do

  • Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `services.AddHttpClient("SentimentAnalysis", u => u.BaseAddress = new Uri(sent...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — source/EventHub.Infrastructure/Configurations/HttpClientConfiguration.cs:15
  • `services.AddHttpClient("RecommenderSystem", u => u.BaseAddress = new Uri(reco...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — source/EventHub.Infrastructure/Configurations/HttpClientConfiguration.cs:23

What to do

  • Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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

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

  • 10 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×5) — REDACTED:70, source/EventHub.Application/Commands/Auth/ExternalLoginCallback/ExternalLoginCallbackCommandHandler.cs:75, REDACTED:36, …
  • `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×4) — source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:47, source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:73, source/EventHub.Application/SeedWork/Attributes/ClaimRequirementFilter.cs:62, …
  • `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — source/EventHub.Application/Queries/User/GetPaginatedUsers/GetPaginatedUsersQueryHandler.cs:35

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

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

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

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — source/EventHub.Presentation/Program.cs:9

What to do

  • Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness7.1 / 10Strong✓ Tool-verified

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

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

  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×10) — REDACTED:70, source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:47, source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:73, …

What to do

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

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

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

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

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

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

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

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

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

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness3.9 / 10Weak✓ Tool-verified

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `_context` is never created by `UnitOfWork` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 364). Its declared type `ApplicationDbContext` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — source/EventHub.Infrastructure.Persistence/SeedWork/UnitOfWork/UnitOfWork.cs:364
  • `str` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 88). Every use of it in `SendRegistrationConfirmationEmailAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var str = …;`), which releases it at the end of the scope on every path including a throw. — source/EventHub.Infrastructure/Mailler/EmailService.cs:88
  • `str` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 103). Every use of it in `SendResetPasswordEmailAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var str = …;`), which releases it at the end of the scope on every path including a throw. — source/EventHub.Infrastructure/Mailler/EmailService.cs:103

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation6.0 / 10Adequate✓ Tool-verified

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

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

  • Only 97/286 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. (×39) — REDACTED:49, REDACTED:75, REDACTED:102, …

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

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

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

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

X24 · Document value interpolated into markup unescaped3.5 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `mailContent.Body` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — source/EventHub.Infrastructure/Mailler/EmailService.cs:48

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

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

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

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

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

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

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

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

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

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

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

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.

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.

Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

X5 · Nullable reference types9.8 / 10Exemplary✓ Tool-verified

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

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

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

Reference — by lens

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

LensScoreRatingImpact
Code Health72%StrongSolid.
Architecture89%StrongStrongest area.
Maturity59%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness20%Critical — gated by D8, D9, D12, P5, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security38%Weak — gated by D28, D29, D30, D36, C1, C2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling30%Weak — gated by DM1, DM2, DM4, DM6, DM7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven75%StrongSolid.
Performance60%AdequateAcceptable, with room to improve.
Unscored — 2 check(s) recorded observations but carry no score

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

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X10 Duplicated predicate — 15 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 34 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — eventhub.db Pulling eventhub.cache Pulling eventhub.hangfire Pulling eventhub.seq Pulling eventhub.seq Error Get "https://registry-1.docker.io/v2/": Forbidden eventhub.minio Error context canceled eventhub.cache Error context canceled eventhub.hangfire Error context canceled eventhub.db Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: eventhub.seq Pulling eventhub.cache Pulling eventhub.minio Pulling eventhub.minio Error Get "https://registry-1.docker.io/v2/": Forbidden eventhub.hangfire Error Get "https://registry-1.docker.io/v2/": Forbidden eventhub.cache Error context canceled eventhub.seq Error context canceled eventhub.db Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
  • D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 152 finding(s)
D17 · Explicit Debt · AnalyzerSeverityNone · ×55
  • AnalyzerSeverityNone .editorconfig:231 — CA1000 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:234 — CA1002 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:237 — CA1008 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:240 — CA1019 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:243 — CA1024 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:246 — CA1030 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:249 — CA1031 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:252 — CA1032 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:255 — CA1034 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:258 — CA1040 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:261 — CA1051 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:264 — CA1056 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:267 — CA1062 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:270 — CA1063 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:273 — CA1307 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:276 — CA1308 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:279 — CA1700 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:282 — CA1707 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:285 — CA1711 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:288 — CA1716 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:291 — CA1724 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:294 — CA1812 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:297 — CA1816 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:300 — CA1819 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:303 — CA1822 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • + 30 more in this group — see findings.md.
DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×40
  • Domain depends on infrastructure: CalculatePositivePercentageOfReviewDomainEventHandler source/EventHub.Application/DomainEventHandlers/CalculatePositivePercentageOfReviewDomainEventHandler.cs:12 — `CalculatePositivePercentageOfReviewDomainEventHandler` (domain layer) names `IHttpClientFactory` from `System.Net.Http` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: CalculatePositivePercentageOfReviewDomainEventHandler source/EventHub.Application/DomainEventHandlers/CalculatePositivePercentageOfReviewDomainEventHandler.cs:14 — `CalculatePositivePercentageOfReviewDomainEventHandler` (domain layer) names `IHttpClientFactory` from `System.Net.Http` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: CalculatePositivePercentageOfReviewDomainEventHandler source/EventHub.Application/DomainEventHandlers/CalculatePositivePercentageOfReviewDomainEventHandler.cs:28 — `CalculatePositivePercentageOfReviewDomainEventHandler` (domain layer) names `HttpClient` from `System.Net.Http` — a HTTP type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: CalculatePositivePercentageOfReviewDomainEventHandler source/EventHub.Application/DomainEventHandlers/CalculatePositivePercentageOfReviewDomainEventHandler.cs:29 — `CalculatePositivePercentageOfReviewDomainEventHandler` (domain layer) names `HttpResponseMessage` from `System.Net.Http` — a HTTP type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ApiBadRequestResponse source/EventHub.Domain.Shared/HttpResponses/ApiBadRequestResponse.cs:8 — `ApiBadRequestResponse` (domain layer) names `ModelStateDictionary` from `Microsoft.AspNetCore.Mvc.ModelBinding` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ApiBadRequestResponse source/EventHub.Domain.Shared/HttpResponses/ApiBadRequestResponse.cs:20 — `ApiBadRequestResponse` (domain layer) names `IdentityResult` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ApiForbiddenResponse source/EventHub.Domain.Shared/HttpResponses/ApiForbiddenResponse.cs:8 — `ApiForbiddenResponse` (domain layer) names `ModelStateDictionary` from `Microsoft.AspNetCore.Mvc.ModelBinding` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ApiForbiddenResponse source/EventHub.Domain.Shared/HttpResponses/ApiForbiddenResponse.cs:20 — `ApiForbiddenResponse` (domain layer) names `IdentityResult` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ApiNotFoundResponse source/EventHub.Domain.Shared/HttpResponses/ApiNotFoundResponse.cs:8 — `ApiNotFoundResponse` (domain layer) names `ModelStateDictionary` from `Microsoft.AspNetCore.Mvc.ModelBinding` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ApiNotFoundResponse source/EventHub.Domain.Shared/HttpResponses/ApiNotFoundResponse.cs:20 — `ApiNotFoundResponse` (domain layer) names `IdentityResult` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ApiUnauthorizedResponse source/EventHub.Domain.Shared/HttpResponses/ApiUnauthorizedResponse.cs:8 — `ApiUnauthorizedResponse` (domain layer) names `ModelStateDictionary` from `Microsoft.AspNetCore.Mvc.ModelBinding` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ApiUnauthorizedResponse source/EventHub.Domain.Shared/HttpResponses/ApiUnauthorizedResponse.cs:20 — `ApiUnauthorizedResponse` (domain layer) names `IdentityResult` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: PaginationFilter source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:33 — `PaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: PaginationFilter source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:48 — `PaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: PaginationFilter source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:62 — `PaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: PaginationFilter source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:76 — `PaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: PaginationFilter source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:91 — `PaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: EventPaginationFilter source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:151 — `EventPaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: EventPaginationFilter source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:154 — `EventPaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: EventPaginationFilter source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:157 — `EventPaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: EventPaginationFilter source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:160 — `EventPaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: EventPaginationFilter source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:163 — `EventPaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: NotificationPaginationFilter source/EventHub.Domain.Shared/SeedWork/PaginationFilter.cs:169 — `NotificationPaginationFilter` (domain layer) names `FromQueryAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Conversation source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:11 — `Conversation` (domain layer) names `TableAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Conversation source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:14 — `Conversation` (domain layer) names `KeyAttribute` from `System.ComponentModel.DataAnnotations` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • + 15 more in this group — see findings.md.
DM1 · Aggregate boundaries · Aggregate holds a reference to another aggregate · ×25
  • Aggregate holds a reference to another aggregate: Conversation.Event source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:26 — `Conversation` references the aggregate root `Event` directly (via `Event`) — hold its `EventId` instead.
  • Aggregate holds a reference to another aggregate: Conversation.Host source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:30 — `Conversation` references the aggregate root `User` directly (via `Host`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Conversation.User source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:34 — `Conversation` references the aggregate root `User` directly (via `User`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Coupon.Author source/EventHub.Domain/Aggregates/CouponAggregate/Coupon.cs:45 — `Coupon` references the aggregate root `User` directly (via `Author`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Coupon.Payments source/EventHub.Domain/Aggregates/CouponAggregate/Coupon.cs:51 — `Coupon` references the aggregate root `Payment` directly (via `Payments`) — hold its `PaymentId` instead.
  • Aggregate holds a reference to another aggregate: Event.Author source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:76 — `Event` references the aggregate root `User` directly (via `Author`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Event.Categories source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:84 — `Event` references the aggregate root `Category` directly (via `Categories`) — hold its `CategoryId` instead.
  • Aggregate holds a reference to another aggregate: Event.Payments source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:94 — `Event` references the aggregate root `Payment` directly (via `Payments`) — hold its `PaymentId` instead.
  • Aggregate holds a reference to another aggregate: Event.Conversations source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:98 — `Event` references the aggregate root `Conversation` directly (via `Conversations`) — hold its `ConversationId` instead.
  • Aggregate holds a reference to another aggregate: Event.Tickets source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:102 — `Event` references the aggregate root `Ticket` directly (via `Tickets`) — hold its `TicketId` instead.
  • Aggregate holds a reference to another aggregate: Notification.TargetUser source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:43 — `Notification` references the aggregate root `User` directly (via `TargetUser`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Notification.Payment source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:51 — `Notification` references the aggregate root `Payment` directly (via `Payment`) — hold its `PaymentId` instead.
  • Aggregate holds a reference to another aggregate: Payment.Author source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:66 — `Payment` references the aggregate root `User` directly (via `Author`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Payment.Event source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:70 — `Payment` references the aggregate root `Event` directly (via `Event`) — hold its `EventId` instead.
  • Aggregate holds a reference to another aggregate: Payment.Coupon source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:74 — `Payment` references the aggregate root `Coupon` directly (via `Coupon`) — hold its `CouponId` instead.
  • Aggregate holds a reference to another aggregate: Payment.Tickets source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:78 — `Payment` references the aggregate root `Ticket` directly (via `Tickets`) — hold its `TicketId` instead.
  • Aggregate holds a reference to another aggregate: Ticket.Event source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:53 — `Ticket` references the aggregate root `Event` directly (via `Event`) — hold its `EventId` instead.
  • Aggregate holds a reference to another aggregate: Ticket.User source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:57 — `Ticket` references the aggregate root `User` directly (via `User`) — hold its `UserId` instead.
  • Aggregate holds a reference to another aggregate: Ticket.Payment source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:61 — `Ticket` references the aggregate root `Payment` directly (via `Payment`) — hold its `PaymentId` instead.
  • Aggregate holds a reference to another aggregate: User.Events source/EventHub.Domain/Aggregates/UserAggregate/User.cs:74 — `User` references the aggregate root `Event` directly (via `Events`) — hold its `EventId` instead.
  • Aggregate holds a reference to another aggregate: User.Payments source/EventHub.Domain/Aggregates/UserAggregate/User.cs:76 — `User` references the aggregate root `Payment` directly (via `Payments`) — hold its `PaymentId` instead.
  • Aggregate holds a reference to another aggregate: User.UserConversations source/EventHub.Domain/Aggregates/UserAggregate/User.cs:82 — `User` references the aggregate root `Conversation` directly (via `UserConversations`) — hold its `ConversationId` instead.
  • Aggregate holds a reference to another aggregate: User.HostConversations source/EventHub.Domain/Aggregates/UserAggregate/User.cs:83 — `User` references the aggregate root `Conversation` directly (via `HostConversations`) — hold its `ConversationId` instead.
  • Aggregate holds a reference to another aggregate: User.Tickets source/EventHub.Domain/Aggregates/UserAggregate/User.cs:87 — `User` references the aggregate root `Ticket` directly (via `Tickets`) — hold its `TicketId` instead.
  • Aggregate holds a reference to another aggregate: User.Notifications source/EventHub.Domain/Aggregates/UserAggregate/User.cs:89 — `User` references the aggregate root `Notification` directly (via `Notifications`) — hold its `NotificationId` instead.
D30 · Dependency Vulnerabilities · High CVE · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · REDACTED · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Vulnerable · ×3
  • Vulnerable: AutoMapper — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
  • Vulnerable: MailKit — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]
  • Vulnerable: MimeKit — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]
D28 · Secrets (history) · High secret · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX3 · Project dependency cycles · Namespace dependency cycle · ×2
  • Namespace dependency cycle source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:3 — The namespaces EventHub.Domain.Aggregates.ConversationAggregate ↔ EventHub.Domain.Aggregates.ConversationAggregate.Entities ↔ EventHub.Domain.Aggregates.CouponAggregate ↔ EventHub.Domain.Aggregates.CouponAggregate.ValueObjects ↔ EventHub.Domain.Aggregates.EventAggregate ↔ EventHub.Domain.Aggregates.EventAggregate.Entities ↔ EventHub.Domain.Aggregates.EventAggregate.ValueObjects ↔ EventHub.Domain.Aggregates.NotificationAggregate ↔ EventHub.Domain.Aggregates.PaymentAggregate ↔ EventHub.Domain.Aggregates.PaymentAggregate.Entities ↔ EventHub.Domain.Aggregates.TicketAggregate ↔ EventHub.Domain.Aggregates.UserAggregate ↔ EventHub.Domain.Aggregates.UserAggregate.Entities ↔ EventHub.Domain.Aggregates.UserAggregate.ValueObjects ↔ EventHub.Domain.SeedWork.AggregateRoot ↔ EventHub.Domain.SeedWork.Entities depend on each other. The lightest dependency in the cycle is EventHub.Domain.Aggregates.ConversationAggregate → EventHub.Domain.Aggregates.ConversationAggregate.Entities (EventHub.Domain.Aggregates.ConversationAggregate.Conversation → EventHub.Domain.Aggregates.ConversationAggregate.Entities.Message, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle source/EventHub.Domain/CachedRepositories/ICachedCategoriesRepository.cs:2 — The namespaces EventHub.Domain.CachedRepositories ↔ EventHub.Domain.Repositories ↔ EventHub.Domain.SeedWork.Persistence depend on each other. The lightest dependency in the cycle is EventHub.Domain.CachedRepositories → EventHub.Domain.SeedWork.Persistence (EventHub.Domain.CachedRepositories.ICachedCategoriesRepository → EventHub.Domain.SeedWork.Persistence.ICachedRepositoryBase, 3 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D30 · Dependency Vulnerabilities · Critical CVE · ×1
  • REDACTED
D8 · Code Coverage · No automated tests · ×1
  • No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
Serious — 334 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 92 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×39
  • Async method without CancellationToken: SignUp REDACTED:49 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ValidateUser REDACTED:75 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SignIn REDACTED:102 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LogOut REDACTED:130 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ExternalLogin REDACTED:151 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ExternalLoginCallback REDACTED:176 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RefreshToken REDACTED:218 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ForgotPassword REDACTED:250 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ResetPassword REDACTED:278 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: PostCreateCategory REDACTED:43 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetPaginatedCategories REDACTED:61 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetCategoryById REDACTED:84 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: PutUpdateCategory REDACTED:113 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteCategory REDACTED:141 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetCommandsInFunction REDACTED:39 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetCommandsNotInFunction REDACTED:62 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetConversationsByOrganizer REDACTED:43 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetConversationsByUser REDACTED:72 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetMessagesByConversation REDACTED:101 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: PostCreateCoupon REDACTED:43 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetCoupons REDACTED:70 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetCreatedCoupons REDACTED:91 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetCouponById REDACTED:113 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: PutUpdateCoupon REDACTED:141 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteCoupon REDACTED:169 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 14 more in this group — see findings.md.
DM4 · Rich vs anemic model · Anemic entity · ×22
  • Anemic entity: Conversation source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:11 — `Conversation` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Message source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:10 — `Message` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Coupon source/EventHub.Domain/Aggregates/CouponAggregate/Coupon.cs:12 — `Coupon` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Category source/EventHub.Domain/Aggregates/EventAggregate/Entities/Category.cs:8 — `Category` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: EmailContent source/EventHub.Domain/Aggregates/EventAggregate/Entities/EmailContent.cs:9 — `EmailContent` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: EventSubImage source/EventHub.Domain/Aggregates/EventAggregate/Entities/EventSubImage.cs:8 — `EventSubImage` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Expense source/EventHub.Domain/Aggregates/EventAggregate/Entities/Expense.cs:9 — `Expense` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Reason source/EventHub.Domain/Aggregates/EventAggregate/Entities/Reason.cs:8 — `Reason` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Review source/EventHub.Domain/Aggregates/EventAggregate/Entities/Review.cs:10 — `Review` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: TicketType source/EventHub.Domain/Aggregates/EventAggregate/Entities/TicketType.cs:11 — `TicketType` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: EmailAttachment source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/EmailAttachment.cs:9 — `EmailAttachment` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: SubExpense source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/SubExpense.cs:9 — `SubExpense` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Notification source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:13 — `Notification` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Payment source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:16 — `Payment` is an aggregate/entity with 19 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: PaymentItem source/EventHub.Domain/Aggregates/PaymentAggregate/Entities/PaymentItem.cs:10 — `PaymentItem` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Ticket source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:14 — `Ticket` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: User source/EventHub.Domain/Aggregates/UserAggregate/User.cs:23 — `User` is an aggregate/entity with 30 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Command source/EventHub.Domain/Aggregates/UserAggregate/Entities/Command.cs:8 — `Command` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Function source/EventHub.Domain/Aggregates/UserAggregate/Entities/Function.cs:9 — `Function` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Invitation source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Invitation.cs:9 — `Invitation` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Permission source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Permission.cs:9 — `Permission` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: UserFollower source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/UserFollower.cs:8 — `UserFollower` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
D17 · Explicit Debt · Dead code · ×14
  • Dead code: CacheKey source/EventHub.Domain.Shared/Constants/CacheKey.cs:3 — NamedType CacheKey — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Domain.Shared, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: Paginate source/EventHub.Domain.Shared/Helpers/PagingHelper.cs:16 — Method Paginate — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Domain.Shared, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ApiForbiddenResponse source/EventHub.Domain.Shared/HttpResponses/ApiForbiddenResponse.cs:6 — NamedType ApiForbiddenResponse — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Domain.Shared, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: EventMetadata source/EventHub.Domain.Shared/SeedWork/EventMetadata.cs:3 — NamedType EventMetadata — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Domain.Shared, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: PriceRange source/EventHub.Domain.Shared/SeedWork/PriceRange.cs:12 — NamedType PriceRange — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Domain.Shared, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: OutboxOptions source/EventHub.Domain.Shared/Settings/OutboxOptions.cs:3 — NamedType OutboxOptions — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Domain.Shared, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: IEntityAuditBase source/EventHub.Domain/SeedWork/Entities/IEntityAuditBase.cs:3 — NamedType IEntityAuditBase — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Domain, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ApplyCouponsCommandValidator source/EventHub.Application/Commands/Event/ApplyCoupons/ApplyCouponsCommandValidator.cs:3 — NamedType ApplyCouponsCommandValidator — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: DownloadAsync source/EventHub.Application/SeedWork/Abstractions/IFileService.cs:47 — Method DownloadAsync — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ContinueQueueWith source/EventHub.Application/SeedWork/Abstractions/IHangfireService.cs:24 — Method ContinueQueueWith — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: SendNotificationToAll source/EventHub.Application/SeedWork/Abstractions/INotificationService.cs:7 — Method SendNotificationToAll — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: GenerateRefreshToken source/EventHub.Application/SeedWork/Abstractions/ITokenService.cs:29 — Method GenerateRefreshToken — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: CreateFavouriteEventDto source/EventHub.Application/SeedWork/DTOs/Event/CreateFavouriteEventDto.cs:5 — NamedType CreateFavouriteEventDto — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: CreateTicketDto source/EventHub.Application/SeedWork/DTOs/Ticket/CreateTicketDto.cs:6 — NamedType CreateTicketDto — Roslyn's SymbolFinder walked every project the solution loads, including EventHub.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
DM7 · Repository granularity · Repository for a non-root entity · ×14
  • Repository for a non-root entity: CachedReviewsRepository → Review source/EventHub.Infrastructure.Persistence/CachedRepositories/CachedReviewsRepository.cs:10 — `CachedReviewsRepository` is a repository over `Review`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Review` through its owning aggregate instead.
  • Repository for a non-root entity: CommandsRepository → Command source/EventHub.Infrastructure.Persistence/Repositories/CommandsRepository.cs:10 — `CommandsRepository` is a repository over `Command`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Command` through its owning aggregate instead.
  • Repository for a non-root entity: EmailAttachmentsRepository → EmailAttachment source/EventHub.Infrastructure.Persistence/Repositories/EmailAttachmentsRepository.cs:9 — `EmailAttachmentsRepository` is a repository over `EmailAttachment`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmailAttachment` through its owning aggregate instead.
  • Repository for a non-root entity: EmailContentsRepository → EmailContent source/EventHub.Infrastructure.Persistence/Repositories/EmailContentsRepository.cs:9 — `EmailContentsRepository` is a repository over `EmailContent`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EmailContent` through its owning aggregate instead.
  • Repository for a non-root entity: EventSubImagesRepository → EventSubImage source/EventHub.Infrastructure.Persistence/Repositories/EventSubImagesRepository.cs:9 — `EventSubImagesRepository` is a repository over `EventSubImage`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `EventSubImage` through its owning aggregate instead.
  • Repository for a non-root entity: ExpensesRepository → Expense source/EventHub.Infrastructure.Persistence/Repositories/ExpensesRepository.cs:8 — `ExpensesRepository` is a repository over `Expense`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Expense` through its owning aggregate instead.
  • Repository for a non-root entity: FunctionsRepository → Function source/EventHub.Infrastructure.Persistence/Repositories/FunctionsRepository.cs:10 — `FunctionsRepository` is a repository over `Function`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Function` through its owning aggregate instead.
  • Repository for a non-root entity: InvitationsRepository → Invitation source/EventHub.Infrastructure.Persistence/Repositories/InvitationsRepository.cs:9 — `InvitationsRepository` is a repository over `Invitation`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Invitation` through its owning aggregate instead.
  • Repository for a non-root entity: MessagesRepository → Message source/EventHub.Infrastructure.Persistence/Repositories/MessagesRepository.cs:9 — `MessagesRepository` is a repository over `Message`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Message` through its owning aggregate instead.
  • Repository for a non-root entity: PaymentItemsRepository → PaymentItem source/EventHub.Infrastructure.Persistence/Repositories/PaymentItemsRepository.cs:9 — `PaymentItemsRepository` is a repository over `PaymentItem`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `PaymentItem` through its owning aggregate instead.
  • Repository for a non-root entity: ReasonsRepository → Reason source/EventHub.Infrastructure.Persistence/Repositories/ReasonsRepository.cs:9 — `ReasonsRepository` is a repository over `Reason`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Reason` through its owning aggregate instead.
  • Repository for a non-root entity: SubExpensesRepository → SubExpense source/EventHub.Infrastructure.Persistence/Repositories/SubExpensesRepository.cs:8 — `SubExpensesRepository` is a repository over `SubExpense`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `SubExpense` through its owning aggregate instead.
  • Repository for a non-root entity: TicketTypesRepository → TicketType source/EventHub.Infrastructure.Persistence/Repositories/TicketTypesRepository.cs:9 — `TicketTypesRepository` is a repository over `TicketType`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `TicketType` through its owning aggregate instead.
  • Repository for a non-root entity: UserFollowersRepository → UserFollower source/EventHub.Infrastructure.Persistence/Repositories/UserFollowersRepository.cs:9 — `UserFollowersRepository` is a repository over `UserFollower`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `UserFollower` through its owning aggregate instead.
D31 · IaC & Container Security · Medium IaC · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
PF3 · Async & latency hygiene · Sync-over-async blocking · ×11
  • Sync-over-async blocking — 10 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking REDACTED:70 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:47 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:73 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking source/EventHub.Application/Commands/Auth/ExternalLoginCallback/ExternalLoginCallbackCommandHandler.cs:75 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking REDACTED:36 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking source/EventHub.Application/Commands/Auth/SignUp/SignUpCommnadHandler.cs:88 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking source/EventHub.Application/Commands/User/CreateUser/CreateUserCommandHandler.cs:74 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking source/EventHub.Application/Queries/User/GetPaginatedUsers/GetPaginatedUsersQueryHandler.cs:35 — `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking source/EventHub.Application/SeedWork/Attributes/ClaimRequirementFilter.cs:62 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking source/EventHub.Application/SeedWork/Attributes/TokenRequirementFilter.cs:46 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
X1 · Async correctness · Sync-over-async (deadlock risk) · ×10
  • Sync-over-async (deadlock risk) REDACTED:70 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:47 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:73 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) source/EventHub.Application/Commands/Auth/ExternalLoginCallback/ExternalLoginCallbackCommandHandler.cs:73 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) REDACTED:34 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) source/EventHub.Application/Commands/Auth/SignUp/SignUpCommnadHandler.cs:86 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) source/EventHub.Application/Commands/User/CreateUser/CreateUserCommandHandler.cs:72 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) source/EventHub.Application/Queries/User/GetPaginatedUsers/GetPaginatedUsersQueryHandler.cs:33 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) source/EventHub.Application/SeedWork/Attributes/ClaimRequirementFilter.cs:62 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) source/EventHub.Application/SeedWork/Attributes/TokenRequirementFilter.cs:46 — 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.
D12 · Dependency Hygiene · Deprecated · ×8
  • Deprecated: Microsoft.AspNetCore.Authentication.Abstractions REDACTED:4 — Microsoft.AspNetCore.Authentication.Abstractions 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Http.Features REDACTED:5 — Microsoft.AspNetCore.Http.Features 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Mvc.Abstractions REDACTED:6 — Microsoft.AspNetCore.Mvc.Abstractions 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Mvc.Abstractions REDACTED:7 — Microsoft.AspNetCore.Mvc.Abstractions 2.2.0 — Other,Legacy
  • Deprecated: FluentValidation.AspNetCore REDACTED:12 — FluentValidation.AspNetCore 11.3.0 — Legacy
  • Deprecated: Microsoft.AspNetCore.Mvc REDACTED:23 — Microsoft.AspNetCore.Mvc 2.2.0 — Other,Legacy
  • Deprecated: Microsoft.Azure.SignalR REDACTED:25 — Microsoft.Azure.SignalR 1.27.0 — Other — the publisher's replacement is `Microsoft.Azure.SignalR` >= 1.33.1; migrate the reference to it.
  • Deprecated: Microsoft.AspNetCore.Identity REDACTED:5 — Microsoft.AspNetCore.Identity 2.2.0 — Other,Legacy
D30 · Dependency Vulnerabilities · Medium CVE · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×6
  • Duplicated block (7 lines × 2) source/EventHub.Application/Commands/User/ChangePassword/ChangePasswordCommandValidator.cs:17 — source/EventHub.Application/Commands/User/ChangePassword/ChangePasswordCommandValidator.cs:17-23 | source/EventHub.Application/Commands/User/CreateUser/CreateUserCommandValidator.cs:29-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `source/EventHub.Application/Commands/User/ChangePassword/ChangePasswordCommandValidator.cs:17` 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 (7 lines × 2) source/EventHub.Application/Queries/Payment/GetPaginatedPayments/GetPaginatedPaymentsQueryHandler.cs:24 — source/EventHub.Application/Queries/Payment/GetPaginatedPayments/GetPaginatedPaymentsQueryHandler.cs:24-30 | source/EventHub.Application/Queries/Payment/GetPaginatedPaymentsByCreatedEvents/GetPaginatedPaymentsByCreatedEventsQueryHandler.cs:24-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `source/EventHub.Application/Queries/Payment/GetPaginatedPayments/GetPaginatedPaymentsQueryHandler.cs:24` 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 first that the copies are not typed on the same thing: the declarations holding them bind `request` to `GetPaginatedPaymentsQuery` in one and `GetPaginatedPaymentsByCreatedEventsQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `source/EventHub.Application/Queries/Payment/GetPaginatedPaymentsByCreatedEvents/GetPaginatedPaymentsByCreatedEventsQueryHandler.cs:31` calls `Where` and `source/EventHub.Application/Queries/Payment/GetPaginatedPayments/GetPaginatedPaymentsQueryHandler.cs:31` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) source/EventHub.Infrastructure/FilesSystem/AzureFileService.cs:79 — source/EventHub.Infrastructure/FilesSystem/AzureFileService.cs:79-85 | source/EventHub.Infrastructure/FilesSystem/AzureFileService.cs:93-99 — 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 `source/EventHub.Infrastructure/FilesSystem/AzureFileService.cs:93` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:98 — source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:98-104 | source/EventHub.Domain/Aggregates/UserAggregate/User.cs:83-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:107 — source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:107-113 | source/EventHub.Infrastructure.Persistence/SeedWork/Repository/RepositoryBase.cs:76-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 2) source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:127 — source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:127-133 | source/EventHub.Infrastructure.Persistence/SeedWork/Repository/RepositoryBase.cs:96-102 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×5
  • Duplicated block (11 lines × 2) source/EventHub.Domain/Aggregates/EventAggregate/Entities/TicketType.cs:21 — source/EventHub.Domain/Aggregates/EventAggregate/Entities/TicketType.cs:21-31 | source/EventHub.Domain/Aggregates/PaymentAggregate/Entities/PaymentItem.cs:26-36 — 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 (11 lines × 2) source/EventHub.Application/SeedWork/DTOs/User/CreateUserDto.cs:10 — source/EventHub.Application/SeedWork/DTOs/User/CreateUserDto.cs:10-20 | source/EventHub.Application/SeedWork/DTOs/User/UpdateUserDto.cs:13-23 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `source/EventHub.Application/SeedWork/DTOs/User/UpdateUserDto.cs:10` calls `SwaggerSchema` and `source/EventHub.Application/SeedWork/DTOs/User/CreateUserDto.cs:9` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) source/EventHub.Application/Commands/Event/CreateEvent/CreateEventCommand.cs:29 — source/EventHub.Application/Commands/Event/CreateEvent/CreateEventCommand.cs:29-39 | source/EventHub.Application/Commands/Event/UpdateEvent/UpdateEventCommand.cs:38-48 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `CreateEventDto` in one and `UpdateEventDto` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (11 lines × 2) source/EventHub.Application/Queries/Payment/GetPaginatedPaymentsByEventId/GetPaginatedPaymentsByEventIdQueryHandler.cs:33 — source/EventHub.Application/Queries/Payment/GetPaginatedPaymentsByEventId/GetPaginatedPaymentsByEventIdQueryHandler.cs:33-43 | source/EventHub.Application/Queries/Payment/GetPaginatedPaymentsByUserId/GetPaginatedPaymentsByUserIdQueryHandler.cs:36-46 — 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 `source/EventHub.Application/Queries/Payment/GetPaginatedPaymentsByEventId/GetPaginatedPaymentsByEventIdQueryHandler.cs:33` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) REDACTED:42 — REDACTED:42-52 | REDACTED:48-58 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
DM10 · One transaction, one aggregate · One operation mutates 2 aggregates · ×5
  • One operation mutates 2 aggregates: FavouriteEventCommandHandler.Handle source/EventHub.Application/Commands/Event/FavouriteEvent/FavouriteEventCommandHandler.cs:25 — `FavouriteEventCommandHandler.Handle` saves `IRepositoryBase`, `UserManager` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: PermanentlyDeleteEventCommandHandler.Handle source/EventHub.Application/Commands/Event/PermanentlyDeleteEvent/PermanentlyDeleteEventCommandHandler.cs:39 — `PermanentlyDeleteEventCommandHandler.Handle` saves `EmailAttachment`, `Event` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: UnfavouriteEventCommandHandler.Handle source/EventHub.Application/Commands/Event/UnfavouriteEvent/UnfavouriteEventCommandHandler.cs:26 — `UnfavouriteEventCommandHandler.Handle` saves `IRepositoryBase`, `UserManager` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: ValidateSessionCommandHandler.Handle source/EventHub.Application/Commands/Payment/ValidateSession/ValidateSessionCommandHandler.cs:33 — `ValidateSessionCommandHandler.Handle` saves `Coupon`, `Event` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
  • One operation mutates 2 aggregates: UnfollowCommandHandler.Handle source/EventHub.Application/Commands/User/Unfollow/UnfollowCommandHandler.cs:25 — `UnfollowCommandHandler.Handle` saves `IRepositoryBase`, `UserManager` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×4
  • Duplicated block (6 lines × 2) source/EventHub.Application/Commands/Event/FavouriteEvent/FavouriteEventCommandHandler.cs:27 — source/EventHub.Application/Commands/Event/FavouriteEvent/FavouriteEventCommandHandler.cs:27-32 | source/EventHub.Application/Commands/Event/UnfavouriteEvent/UnfavouriteEventCommandHandler.cs:28-33 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `FavouriteEventCommand` in one and `UnfavouriteEventCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (6 lines × 2) source/EventHub.Application/Queries/Review/GetReviewStatisticsByCreatedEvents/GetReviewStatisticsByCreatedEventsQueryHandler.cs:24 — source/EventHub.Application/Queries/Review/GetReviewStatisticsByCreatedEvents/GetReviewStatisticsByCreatedEventsQueryHandler.cs:24-29 | source/EventHub.Application/Queries/Statistic/GetEventReviewsByCustomer/GetEventReviewsByCustomerQueryHandler.cs:21-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `source/EventHub.Application/Queries/Review/GetReviewStatisticsByCreatedEvents/GetReviewStatisticsByCreatedEventsQueryHandler.cs:24` 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 (6 lines × 2) source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:62 — source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:62-67 | source/EventHub.Infrastructure.Persistence/SeedWork/Repository/RepositoryBase.cs:42-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:90 — source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:90-95 | source/EventHub.Infrastructure.Persistence/SeedWork/Repository/RepositoryBase.cs:59-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) source/EventHub.Application/Queries/User/GetPaginatedFollowers/GetPaginatedFollowersQueryHandler.cs:25 — source/EventHub.Application/Queries/User/GetPaginatedFollowers/GetPaginatedFollowersQueryHandler.cs:25-36 | source/EventHub.Application/Queries/User/GetPaginatedFollowersToInvite/GetPaginatedFollowersToInviteQueryHandler.cs:25-36 — 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 `source/EventHub.Application/Queries/User/GetPaginatedFollowers/GetPaginatedFollowersQueryHandler.cs:25` 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 first that the copies are not typed on the same thing: the declarations holding them bind `request` to `GetPaginatedFollowersQuery` in one and `GetPaginatedFollowersToInviteQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (12 lines × 2) source/EventHub.Application/Commands/Category/CreateCategory/CreateCategoryCommandValidator.cs:9 — source/EventHub.Application/Commands/Category/CreateCategory/CreateCategoryCommandValidator.cs:9-20 | source/EventHub.Application/Commands/Category/UpdateCategory/UpdateCategoryCommandValidator.cs:12-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `source/EventHub.Application/Commands/Category/UpdateCategory/UpdateCategoryCommandValidator.cs:12` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) source/EventHub.Application/Commands/Permission/DisableCommandInFunction/DisableCommandInFunctionCommandValidator.cs:9 — source/EventHub.Application/Commands/Permission/DisableCommandInFunction/DisableCommandInFunctionCommandValidator.cs:9-20 | source/EventHub.Application/Commands/Permission/EnableCommandInFunction/EnableCommandInFunctionCommandValidator.cs:9-20 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2
  • Duplicated block (14 lines × 2) source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:27 — source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:27-40 | source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:23-36 — 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 (14 lines × 2) source/EventHub.Application/Commands/Event/CreateEvent/CreateTicketTypeCommandValidator.cs:9 — source/EventHub.Application/Commands/Event/CreateEvent/CreateTicketTypeCommandValidator.cs:9-22 | source/EventHub.Application/Commands/Event/UpdateEvent/UpdateTicketTypeCommandValidator.cs:9-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) source/EventHub.Application/Commands/User/CreateUser/CreateUserCommandValidator.cs:9 — source/EventHub.Application/Commands/User/CreateUser/CreateUserCommandValidator.cs:9-21 | source/EventHub.Application/Commands/User/UpdateUser/UpdateUserCommandValidator.cs:9-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (13 lines × 2) source/EventHub.Application/SeedWork/DTOs/Message/EditMessageDto.cs:9 — source/EventHub.Application/SeedWork/DTOs/Message/EditMessageDto.cs:9-21 | source/EventHub.Application/SeedWork/DTOs/Message/SendMessageDto.cs:11-23 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
DM7 · Repository granularity · Repository contract exposes a live query handle · ×2
  • Repository contract exposes a live query handle: IEventsRepository source/EventHub.Domain/Repositories/IEventsRepository.cs:8 — `IEventsRepository` returns `IQueryable` from `GetDeletedEvents`, `GetDeletedEvents`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked.
  • Repository contract exposes a live query handle: IRepositoryBase source/EventHub.Domain/SeedWork/Persistence/IRepositoryBase.cs:16 — `IRepositoryBase` returns `IQueryable` from `FindAll`, `FindAll`, `FindByCondition`, `FindByCondition`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked.
ED5 · Idempotency · Non-idempotent mutation · ×2
  • Non-idempotent mutation: CreateSubExpense.CreateSubExpenseCommandHandler.Handle source/EventHub.Application/Commands/Expense/CreateSubExpense/CreateSubExpenseCommandHandler.cs:19 — `CreateSubExpense.CreateSubExpenseCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
  • Non-idempotent mutation: DeleteSubExpense.DeleteSubExpenseCommandHandler.Handle source/EventHub.Application/Commands/Expense/DeleteSubExpense/DeleteSubExpenseCommandHandler.cs:16 — `DeleteSubExpense.DeleteSubExpenseCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×2
  • Outbound HTTP without resilience source/EventHub.Infrastructure/Configurations/HttpClientConfiguration.cs:15 — `services.AddHttpClient("SentimentAnalysis", u => u.BaseAddress = new Uri(sent...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
  • Outbound HTTP without resilience source/EventHub.Infrastructure/Configurations/HttpClientConfiguration.cs:23 — `services.AddHttpClient("RecommenderSystem", u => u.BaseAddress = new Uri(reco...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×2
  • Disposable created and abandoned in the method that made it source/EventHub.Infrastructure/Mailler/EmailService.cs:88 — `str` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 88). Every use of it in `SendRegistrationConfirmationEmailAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var str = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it source/EventHub.Infrastructure/Mailler/EmailService.cs:103 — `str` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 103). Every use of it in `SendResetPasswordEmailAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var str = …;`), which releases it at the end of the scope on every path including a throw.
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
D1 · Cyclomatic Complexity · GetCreatedEventsByUserIdQueryHandler.Handle (cyclomatic 21) · ×1
  • GetCreatedEventsByUserIdQueryHandler.Handle (cyclomatic 21) source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:26 — GetCreatedEventsByUserIdQueryHandler.Handle has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 36, 40, 49, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · PagingHelper.QueryPaginate (cyclomatic 17) · ×1
  • PagingHelper.QueryPaginate (cyclomatic 17) source/EventHub.Domain.Shared/Helpers/PagingHelper.cs:79 — PagingHelper.QueryPaginate has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CreateEventCommandHandler.Handle (cyclomatic 16) · ×1
  • CreateEventCommandHandler.Handle (cyclomatic 16) source/EventHub.Application/Commands/Event/CreateEvent/CreateEventCommandHandler.cs:65 — CreateEventCommandHandler.Handle has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · GetPaginatedEventsQueryHandler.Handle (cyclomatic 16) · ×1
  • GetPaginatedEventsQueryHandler.Handle (cyclomatic 16) source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs:21 — GetPaginatedEventsQueryHandler.Handle has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 27, 31, 40, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · PagingHelper.QueryPaginate (cognitive 25) · ×1
  • PagingHelper.QueryPaginate (cognitive 25) source/EventHub.Domain.Shared/Helpers/PagingHelper.cs:79 — PagingHelper.QueryPaginate has cognitive complexity 25 (threshold 15). Of this number, 15 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CreateEventCommandHandler.Handle (cognitive 18) · ×1
  • CreateEventCommandHandler.Handle (cognitive 18) source/EventHub.Application/Commands/Event/CreateEvent/CreateEventCommandHandler.cs:65 — CreateEventCommandHandler.Handle has cognitive complexity 18 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · MethodTooLong · ×1
  • MethodTooLong: ApplicationDbContextSeed.SeedPermission source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:266 — MethodTooLong — SeedPermission runs 276 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 176 over it, 2.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: ApplicationDbContextSeed source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs — ClassTooLong — 623 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 223 over it, 1.56× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: Data/ApplicationDbContextSeed.cs source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs — FileTooLong — 639 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 139 over it, 1.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D32 · Data Compliance (PII/GDPR) · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (3 members, 33 shared lines) · ×1
  • Near-duplicate member family (3 members, 33 shared lines) source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:28 — source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:28-101 | source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs:29-87 | source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs:23-81 — These 3 members are variants of one another: a block of 33 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) source/EventHub.Application/Queries/Payment/GetPaginatedPayments/GetPaginatedPaymentsQueryHandler.cs:23 — source/EventHub.Application/Queries/Payment/GetPaginatedPayments/GetPaginatedPaymentsQueryHandler.cs:23-36 | source/EventHub.Application/Queries/Payment/GetPaginatedPaymentsByCreatedEvents/GetPaginatedPaymentsByCreatedEventsQueryHandler.cs:23-37 | source/EventHub.Application/Queries/Payment/GetPaginatedPaymentsByEventId/GetPaginatedPaymentsByEventIdQueryHandler.cs:24-43 | source/EventHub.Application/Queries/Payment/GetPaginatedPaymentsByUserId/GetPaginatedPaymentsByUserIdQueryHandler.cs:27-46 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (61 lines × 2) · ×1
  • Duplicated block (61 lines × 2) REDACTED:117 — REDACTED:117-177 | source/EventHub.Infrastructure/Services/NotificationService.cs:77-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. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:117` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (56 lines × 2) · ×1
  • Duplicated block (56 lines × 2) source/EventHub.Application/Commands/Event/CreateEvent/CreateEventCommandValidator.cs:10 — source/EventHub.Application/Commands/Event/CreateEvent/CreateEventCommandValidator.cs:10-65 | source/EventHub.Application/Commands/Event/UpdateEvent/UpdateEventCommandValidator.cs:14-69 — before extracting anything, compare `source/EventHub.Application/Commands/Event/CreateEvent/CreateEventCommandValidator.cs` and `source/EventHub.Application/Commands/Event/UpdateEvent/UpdateEventCommandValidator.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `source/EventHub.Application/Commands/Event/CreateEvent/CreateEventCommandValidator.cs:10` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (42 lines × 2) · ×1
  • Duplicated block (42 lines × 2) source/EventHub.Application/SeedWork/DTOs/Event/CreateEventDto.cs:10 — source/EventHub.Application/SeedWork/DTOs/Event/CreateEventDto.cs:10-51 | source/EventHub.Application/SeedWork/DTOs/Event/UpdateEventDto.cs:13-54 — before extracting anything, compare `source/EventHub.Application/SeedWork/DTOs/Event/CreateEventDto.cs` and `source/EventHub.Application/SeedWork/DTOs/Event/UpdateEventDto.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `source/EventHub.Application/SeedWork/DTOs/Event/UpdateEventDto.cs:10` calls `SwaggerSchema` and `source/EventHub.Application/SeedWork/DTOs/Event/CreateEventDto.cs:9` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:292 — source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:292-327 | source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:483-518 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (37 lines × 8) · ×1
  • Duplicated block (37 lines × 8) source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:292 — source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:292-328 | source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:334-370 | source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:376-412 | source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:418-454 | source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:483-519 | source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:525-561 | source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:567-603 | source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:609-645 — all 8 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 `source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContextSeed.cs:292` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) source/EventHub.Application/Commands/Coupon/CreateCoupon/CreateCouponCommandValidator.cs:9 — source/EventHub.Application/Commands/Coupon/CreateCoupon/CreateCouponCommandValidator.cs:9-35 | source/EventHub.Application/Commands/Coupon/UpdateCoupon/UpdateCouponCommandValidator.cs:15-41 — before extracting anything, compare `source/EventHub.Application/Commands/Coupon/CreateCoupon/CreateCouponCommandValidator.cs` and `source/EventHub.Application/Commands/Coupon/UpdateCoupon/UpdateCouponCommandValidator.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `source/EventHub.Application/Commands/Coupon/UpdateCoupon/UpdateCouponCommandValidator.cs:15` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17–23 lines × 2) · ×1
  • Duplicated block (17–23 lines × 2) source/EventHub.Domain.Shared/Helpers/PagingHelper.cs:61 — source/EventHub.Domain.Shared/Helpers/PagingHelper.cs:61-77 | source/EventHub.Domain.Shared/Helpers/PagingHelper.cs:137-159 — 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 `source/EventHub.Domain.Shared/Helpers/PagingHelper.cs:61` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16–19 lines × 3) · ×1
  • Duplicated block (16–19 lines × 3) source/EventHub.Application/Queries/Conversation/GetConversationsByEventId/GetConversationsByEventIdQueryHandler.cs:35 — source/EventHub.Application/Queries/Conversation/GetConversationsByEventId/GetConversationsByEventIdQueryHandler.cs:35-53 | source/EventHub.Application/Queries/Conversation/GetConversationsByOrganizerId/GetConversationsByOrganizerIdQueryHandler.cs:27-45 | source/EventHub.Application/Queries/Conversation/GetConversationsByUserId/GetConversationsByUserIdQueryHandler.cs:37-52 — 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 `source/EventHub.Application/Queries/Conversation/GetConversationsByEventId/GetConversationsByEventIdQueryHandler.cs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `GetConversationsByEventIdQuery` in one and `GetConversationsByOrganizerIdQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:51 — source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:51-69 | source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs:46-64 — before extracting anything, compare `source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs` and `source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 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 `source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:51` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `GetCreatedEventsByUserIdQuery` in one and `GetFavouriteEventsByUserIdQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) source/EventHub.Application/SeedWork/DTOs/Payment/PaymentDto.cs:11 — source/EventHub.Application/SeedWork/DTOs/Payment/PaymentDto.cs:11-26 | source/EventHub.Application/SeedWork/DTOs/Payment/ValidateSessionResponseDto.cs:9-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:35 — source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:35-51 | source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs:26-42 — before extracting anything, compare `source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs` and `source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 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 `source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:35` 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 first that the copies are not typed on the same thing: the declarations holding them bind `request` to `GetCreatedEventsByUserIdQuery` in one and `GetPaginatedEventsQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:44 — source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:44-59 | source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs:39-54 | source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs:35-50 — before extracting anything, compare `source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs` and `source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `GetCreatedEventsByUserIdQuery` in one and `GetFavouriteEventsByUserIdQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs:52` calls `Include` and `source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:61` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) source/EventHub.Application/SeedWork/DTOs/Event/CreateEventDto.cs:13 — source/EventHub.Application/SeedWork/DTOs/Event/CreateEventDto.cs:13-26 | source/EventHub.Application/SeedWork/DTOs/Event/EventDetailDto.cs:18-31 | source/EventHub.Application/SeedWork/DTOs/Event/UpdateEventDto.cs:16-29 — before extracting anything, compare `source/EventHub.Application/SeedWork/DTOs/Event/CreateEventDto.cs` and `source/EventHub.Application/SeedWork/DTOs/Event/UpdateEventDto.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `source/EventHub.Application/SeedWork/DTOs/Event/EventDetailDto.cs:15` calls `SwaggerSchema` and `source/EventHub.Application/SeedWork/DTOs/Event/CreateEventDto.cs:11` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) source/EventHub.Application/Commands/Coupon/UpdateCoupon/UpdateCouponCommand.cs:42 — source/EventHub.Application/Commands/Coupon/UpdateCoupon/UpdateCouponCommand.cs:42-56 | source/EventHub.Application/SeedWork/DTOs/Coupon/UpdateCouponDto.cs:7-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×1
  • Duplicated block (13 lines × 4) source/EventHub.Application/Commands/Coupon/CreateCoupon/CreateCouponCommand.cs:33 — source/EventHub.Application/Commands/Coupon/CreateCoupon/CreateCouponCommand.cs:33-45 | source/EventHub.Application/Commands/Coupon/UpdateCoupon/UpdateCouponCommand.cs:44-56 | source/EventHub.Application/SeedWork/DTOs/Coupon/CreateCouponDto.cs:7-19 | source/EventHub.Application/SeedWork/DTOs/Coupon/UpdateCouponDto.cs:9-21 — 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 3) · ×1
  • Duplicated block (12–13 lines × 3) source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:90 — source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:90-101 | source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs:76-87 | source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs:69-81 — before extracting anything, compare `source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs` and `source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 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 `source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:90` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:87` calls `Include`, `ThenInclude` and `source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs:66` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) source/EventHub.Application/Commands/Event/DeleteEvent/DeleteEventCommandHandler.cs:31 — source/EventHub.Application/Commands/Event/DeleteEvent/DeleteEventCommandHandler.cs:31-43 | source/EventHub.Application/Commands/Event/DeleteEvents/DeleteEventsCommandHandler.cs:33-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `source/EventHub.Application/Commands/Event/DeleteEvent/DeleteEventCommandHandler.cs:31` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) source/EventHub.Application/SeedWork/DTOs/Event/CreateEventDto.cs:29 — source/EventHub.Application/SeedWork/DTOs/Event/CreateEventDto.cs:29-37 | source/EventHub.Application/SeedWork/DTOs/Event/EventDetailDto.cs:49-57 | source/EventHub.Application/SeedWork/DTOs/Event/EventDto.cs:47-55 | source/EventHub.Application/SeedWork/DTOs/Event/UpdateEventDto.cs:32-40 — before extracting anything, compare `source/EventHub.Application/SeedWork/DTOs/Event/CreateEventDto.cs` and `source/EventHub.Application/SeedWork/DTOs/Event/UpdateEventDto.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) source/EventHub.Application/Queries/Payment/GetPaginatedPayments/GetPaginatedPaymentsQueryHandler.cs:26 — source/EventHub.Application/Queries/Payment/GetPaginatedPayments/GetPaginatedPaymentsQueryHandler.cs:26-33 | source/EventHub.Application/Queries/Payment/GetPaginatedPaymentsByEventId/GetPaginatedPaymentsByEventIdQueryHandler.cs:33-40 | source/EventHub.Application/Queries/Payment/GetPaginatedPaymentsByUserId/GetPaginatedPaymentsByUserIdQueryHandler.cs:36-43 — 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 `source/EventHub.Application/Queries/Payment/GetPaginatedPayments/GetPaginatedPaymentsQueryHandler.cs:26` 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.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:45 — source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:45-53 | source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:71-79 — 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 `source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:81` calls `Where` and `source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:54` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:189 — source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:189-194 | source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:200-205 | source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:224-229 — 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 `source/EventHub.Infrastructure.Persistence/SeedWork/Repository/CachedRepositoryBase.cs:189` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs:61 — source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs:61-68 | source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs:59-67 — before extracting anything, compare `source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs` and `source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `GetFavouriteEventsByUserIdQuery` in one and `GetPaginatedEventsQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs:58` calls `Include`, `ThenInclude` and `source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs:59` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) source/EventHub.Application/SeedWork/Attributes/ClaimRequirementFilter.cs:49 — source/EventHub.Application/SeedWork/Attributes/ClaimRequirementFilter.cs:49-53 | source/EventHub.Application/SeedWork/Attributes/TokenRequirementFilter.cs:34-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:66 — source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:66-70 | source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs:61-65 | source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs:59-64 — before extracting anything, compare `source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs` and `source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `GetCreatedEventsByUserIdQuery` in one and `GetFavouriteEventsByUserIdQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs:58` calls `Include`, `ThenInclude` and `source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:64` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (21 lines × 4) · ×1
  • Duplicated block (21 lines × 4) source/EventHub.Domain.Shared/HttpResponses/ApiBadRequestResponse.cs:10 — source/EventHub.Domain.Shared/HttpResponses/ApiBadRequestResponse.cs:10-30 | source/EventHub.Domain.Shared/HttpResponses/ApiForbiddenResponse.cs:10-30 | source/EventHub.Domain.Shared/HttpResponses/ApiNotFoundResponse.cs:10-30 | source/EventHub.Domain.Shared/HttpResponses/ApiUnauthorizedResponse.cs:10-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) source/EventHub.Application/Commands/Permission/AddFunctionToRole/AddFunctionToRoleCommandValidator.cs:9 — source/EventHub.Application/Commands/Permission/AddFunctionToRole/AddFunctionToRoleCommandValidator.cs:9-18 | source/EventHub.Application/Commands/Permission/RemoveFunctionFromRole/RemoveFunctionFromRoleCommandValidator.cs:9-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
DM12 · Ambient inputs in the domain · Domain type reads the wall clock · ×1
  • Domain type reads the wall clock: TicketCodeGenerator source/EventHub.Domain.Shared/Helpers/TicketCodeGenerator.cs:12 — `TicketCodeGenerator` reads `DateTime.Now` inside `GenerateTicketCode` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has.
ED1 · Handler temporal coupling · Temporal coupling in handler · ×1
  • Temporal coupling in handler: CalculatePositivePercentageOfReviewDomainEventHandler.Handle source/EventHub.Application/DomainEventHandlers/CalculatePositivePercentageOfReviewDomainEventHandler.cs:20 — `CalculatePositivePercentageOfReviewDomainEventHandler.Handle` makes a synchronous remote call (an HTTP call) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
P5 · DR & Backup · No DR/backup evidence · ×1
  • No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
X18 · Disposal-pattern correctness · Disposes a dependency it does not own · ×1
  • Disposes a dependency it does not own source/EventHub.Infrastructure.Persistence/SeedWork/UnitOfWork/UnitOfWork.cs:364 — `_context` is never created by `UnitOfWork` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 364). Its declared type `ApplicationDbContext` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×1
  • Untrusted text written into markup unescaped source/EventHub.Infrastructure/Mailler/EmailService.cs:48 — `mailContent.Body` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Minor — 117 finding(s)
DM2 · Strongly-typed ids · Primitive id on a domain type · ×40
  • Primitive id on a domain type: Conversation.EventId source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:18 — `Conversation.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Conversation.HostId source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:20 — `Conversation.HostId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Conversation.UserId source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:22 — `Conversation.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Conversation.LastMessageId source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:24 — `Conversation.LastMessageId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Message.ReceiverId source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:42 — `Message.ReceiverId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Message.EventId source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:49 — `Message.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Message.ConversationId source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:52 — `Message.ConversationId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Coupon.AuthorId source/EventHub.Domain/Aggregates/CouponAggregate/Coupon.cs:43 — `Coupon.AuthorId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Event.AuthorId source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:72 — `Event.AuthorId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: EmailContent.EventId source/EventHub.Domain/Aggregates/EventAggregate/Entities/EmailContent.cs:21 — `EmailContent.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: EventSubImage.EventId source/EventHub.Domain/Aggregates/EventAggregate/Entities/EventSubImage.cs:15 — `EventSubImage.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Expense.EventId source/EventHub.Domain/Aggregates/EventAggregate/Entities/Expense.cs:16 — `Expense.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Reason.EventId source/EventHub.Domain/Aggregates/EventAggregate/Entities/Reason.cs:15 — `Reason.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Review.AuthorId source/EventHub.Domain/Aggregates/EventAggregate/Entities/Review.cs:17 — `Review.AuthorId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Review.EventId source/EventHub.Domain/Aggregates/EventAggregate/Entities/Review.cs:20 — `Review.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: TicketType.EventId source/EventHub.Domain/Aggregates/EventAggregate/Entities/TicketType.cs:18 — `TicketType.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: EmailAttachment.EmailContentId source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/EmailAttachment.cs:16 — `EmailAttachment.EmailContentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: SubExpense.ExpenseId source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/SubExpense.cs:16 — `SubExpense.ExpenseId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Notification.TargetUserId source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:31 — `Notification.TargetUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Notification.InvitationId source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:35 — `Notification.InvitationId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Notification.PaymentId source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:37 — `Notification.PaymentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Notification.UserFollowerId source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:39 — `Notification.UserFollowerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: Payment.PaymentIntentId source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:54 — `Payment.PaymentIntentId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: Payment.SessionId source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:56 — `Payment.SessionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: Payment.EventId source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:58 — `Payment.EventId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • + 15 more in this group — see findings.md.
DM5 · Encapsulated state · Mutable entity · ×23
  • Mutable entity: Conversation source/EventHub.Domain/Aggregates/ConversationAggregate/Conversation.cs:11 — `Conversation` exposes publicly writable state (Id, EventId, HostId, UserId, LastMessageId, Event, and 4 more).
  • Mutable entity: Message source/EventHub.Domain/Aggregates/ConversationAggregate/Entities/Message.cs:10 — `Message` exposes publicly writable state (Id, Content, ImageUrl, ImageFileName, VideoUrl, VideoFileName, and 8 more).
  • Mutable entity: Coupon source/EventHub.Domain/Aggregates/CouponAggregate/Coupon.cs:12 — `Coupon` exposes publicly writable state (Id, Name, Description, Quantity, MinPrice, PercentValue, and 8 more).
  • Mutable entity: Event source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:22 — `Event` exposes publicly writable state (Id, CoverImageFileName, CoverImageUrl, Name, Description, Location, and 26 more).
  • Mutable entity: Category source/EventHub.Domain/Aggregates/EventAggregate/Entities/Category.cs:8 — `Category` exposes publicly writable state (Id, Name, IconImageUrl, IconImageFileName, Color, EventCategories).
  • Mutable entity: EmailContent source/EventHub.Domain/Aggregates/EventAggregate/Entities/EmailContent.cs:9 — `EmailContent` exposes publicly writable state (Id, Content, EventId, Event, EmailAttachments).
  • Mutable entity: EventSubImage source/EventHub.Domain/Aggregates/EventAggregate/Entities/EventSubImage.cs:8 — `EventSubImage` exposes publicly writable state (Id, EventId, ImageUrl, ImageFileName, Event).
  • Mutable entity: Expense source/EventHub.Domain/Aggregates/EventAggregate/Entities/Expense.cs:9 — `Expense` exposes publicly writable state (Id, EventId, Title, Total, Event, SubExpenses).
  • Mutable entity: Reason source/EventHub.Domain/Aggregates/EventAggregate/Entities/Reason.cs:8 — `Reason` exposes publicly writable state (Id, EventId, Name, Event).
  • Mutable entity: Review source/EventHub.Domain/Aggregates/EventAggregate/Entities/Review.cs:10 — `Review` exposes publicly writable state (Id, AuthorId, EventId, Content, IsPositive, SentimentPercentage, and 3 more).
  • Mutable entity: TicketType source/EventHub.Domain/Aggregates/EventAggregate/Entities/TicketType.cs:11 — `TicketType` exposes publicly writable state (Id, EventId, Name, Quantity, Price, NumberOfSoldTickets, and 3 more).
  • Mutable entity: EmailAttachment source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/EmailAttachment.cs:9 — `EmailAttachment` exposes publicly writable state (Id, EmailContentId, AttachmentFileName, AttachmentUrl, EmailContent).
  • Mutable entity: SubExpense source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/SubExpense.cs:9 — `SubExpense` exposes publicly writable state (Id, ExpenseId, Name, Price, Expense).
  • Mutable entity: Notification source/EventHub.Domain/Aggregates/NotificationAggregate/Notification.cs:13 — `Notification` exposes publicly writable state (Id, Title, Message, Type, Timestamp, TargetUserId, and 9 more).
  • Mutable entity: Payment source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:16 — `Payment` exposes publicly writable state (Id, TicketQuantity, CustomerName, CustomerPhone, CustomerEmail, TotalPrice, and 13 more).
  • Mutable entity: PaymentItem source/EventHub.Domain/Aggregates/PaymentAggregate/Entities/PaymentItem.cs:10 — `PaymentItem` exposes publicly writable state (Id, TicketTypeId, EventId, PaymentId, Name, Quantity, and 5 more).
  • Mutable entity: Ticket source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:14 — `Ticket` exposes publicly writable state (Id, TicketNo, CustomerName, CustomerPhone, CustomerEmail, TicketTypeId, and 8 more).
  • Mutable entity: User source/EventHub.Domain/Aggregates/UserAggregate/User.cs:23 — `User` exposes publicly writable state (FullName, Dob, Gender, Bio, AvatarUrl, AvatarFileName, and 24 more).
  • Mutable entity: Command source/EventHub.Domain/Aggregates/UserAggregate/Entities/Command.cs:8 — `Command` exposes publicly writable state (Id, Name, CommandInFunctions, Permissions).
  • Mutable entity: Function source/EventHub.Domain/Aggregates/UserAggregate/Entities/Function.cs:9 — `Function` exposes publicly writable state (Id, Name, Url, SortOrder, ParentId, Parent, and 2 more).
  • Mutable entity: Invitation source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Invitation.cs:9 — `Invitation` exposes publicly writable state (Id, InviterId, InvitedId, EventId, Inviter, Invited, and 1 more).
  • Mutable entity: Permission source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/Permission.cs:9 — `Permission` exposes publicly writable state (FunctionId, RoleId, CommandId, Function, Role, Command).
  • Mutable entity: UserFollower source/EventHub.Domain/Aggregates/UserAggregate/ValueObjects/UserFollower.cs:8 — `UserFollower` exposes publicly writable state (Id, FollowerId, FollowedId, Follower, Followed).
X10 · Duplicated predicate · Duplicated predicate · ×15
  • Duplicated predicate source/EventHub.Application/Queries/Notification/GetNotificationsStatistic/GetPaginatedNotificationsQueryHandler.cs:30 — `!x.IsSeen && x.Type == ENotificationType.FOLLOWING` appears character-identically in 2 files — source/EventHub.Application/Queries/Notification/GetNotificationsStatistic/GetPaginatedNotificationsQueryHandler.cs, source/EventHub.Application/Queries/Notification/GetPaginatedNotifications/GetPaginatedNotificationsQueryHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Application/Queries/Notification/GetNotificationsStatistic/GetPaginatedNotificationsQueryHandler.cs:32 — `!x.IsSeen && x.Type == ENotificationType.INVITING` appears character-identically in 2 files — source/EventHub.Application/Queries/Notification/GetNotificationsStatistic/GetPaginatedNotificationsQueryHandler.cs, source/EventHub.Application/Queries/Notification/GetPaginatedNotifications/GetPaginatedNotificationsQueryHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Application/Queries/Notification/GetNotificationsStatistic/GetPaginatedNotificationsQueryHandler.cs:31 — `!x.IsSeen && x.Type == ENotificationType.ORDERING` appears character-identically in 2 files — source/EventHub.Application/Queries/Notification/GetNotificationsStatistic/GetPaginatedNotificationsQueryHandler.cs, source/EventHub.Application/Queries/Notification/GetPaginatedNotifications/GetPaginatedNotificationsQueryHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:49 — `DateTime.UtcNow >= x.StartTime && DateTime.UtcNow <= x.EndTime` appears character-identically in 3 files — source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs, source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs, source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Infrastructure/Configurations/ApplicationDbContextConfiguration.cs:18 — `connectionString == null || string.IsNullOrEmpty(connectionString)` appears character-identically in 2 files — source/EventHub.Infrastructure/Configurations/ApplicationDbContextConfiguration.cs, source/EventHub.Infrastructure/Configurations/CachingConfiguration.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Infrastructure/Services/NotificationService.cs:107 — `notification.Type == Domain.Shared.Enums.Notification.ENotificationType.FOLLOWING && notification.UserFollowerId is not null` appears character-identically in 2 files — REDACTED, source/EventHub.Infrastructure/Services/NotificationService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Infrastructure/Services/NotificationService.cs:115 — `notification.Type == Domain.Shared.Enums.Notification.ENotificationType.INVITING && notification.InvitationId is not null` appears character-identically in 2 files — REDACTED, source/EventHub.Infrastructure/Services/NotificationService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Infrastructure/Services/NotificationService.cs:125 — `notification.Type == Domain.Shared.Enums.Notification.ENotificationType.ORDERING && notification.PaymentId is not null` appears character-identically in 2 files — REDACTED, source/EventHub.Infrastructure/Services/NotificationService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:97 — `paginatedEvents.Items[i].Reviews != null && paginatedEvents.Items[i].Reviews.Any()` appears character-identically in 3 files — source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs, source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs, source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:40 — `request.Filter.DateRange.StartDate <= x.StartTime && x.EndTime <= request.Filter.DateRange.EndDate` appears character-identically in 2 files — source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs, source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs:61 — `request.Filter.Rate is int rate && rate is >= 1 and <= 5` appears character-identically in 3 files — source/EventHub.Application/Queries/Event/GetCreatedEventsByUserId/GetCreatedEventsByUserIdQueryHandler.cs, source/EventHub.Application/Queries/Event/GetFavouriteEventsByUserId/GetFavouriteEventsByUserIdQueryHandler.cs, source/EventHub.Application/Queries/Event/GetPaginatedEvents/GetPaginatedEventsQueryHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Application/Commands/Event/FavouriteEvent/FavouriteEventCommandHandler.cs:40 — `x.EventId == request.EventId && x.UserId == Guid.Parse(userId)` appears character-identically in 3 files — source/EventHub.Application/Commands/Event/FavouriteEvent/FavouriteEventCommandHandler.cs, source/EventHub.Application/Commands/Event/UnfavouriteEvent/UnfavouriteEventCommandHandler.cs, source/EventHub.Application/Queries/Event/GetEventById/GetEventByIdQueryHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Application/Commands/User/Follow/FollowCommandHandler.cs:44 — `x.FollowerId == Guid.Parse(followerId) && x.FollowedId == request.FollowedUserId` appears character-identically in 2 files — source/EventHub.Application/Commands/User/Follow/FollowCommandHandler.cs, source/EventHub.Application/Commands/User/Unfollow/UnfollowCommandHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Application/Commands/Permission/DisableCommandInFunction/DisableCommandInFunctionCommandHandler.cs:34 — `x.FunctionId == request.FunctionId && x.CommandId == request.CommandId` appears character-identically in 2 files — source/EventHub.Application/Commands/Permission/DisableCommandInFunction/DisableCommandInFunctionCommandHandler.cs, source/EventHub.Application/Commands/Permission/EnableCommandInFunction/EnableCommandInFunctionCommandHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate source/EventHub.Application/Commands/Permission/AddFunctionToRole/AddFunctionToRoleCommandHandler.cs:38 — `x.FunctionId == request.FunctionId && x.RoleId == request.RoleId` appears character-identically in 2 files — source/EventHub.Application/Commands/Permission/AddFunctionToRole/AddFunctionToRoleCommandHandler.cs, source/EventHub.Application/Commands/Permission/RemoveFunctionFromRole/RemoveFunctionFromRoleCommandHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D12 · Dependency Hygiene · Outdated · ×6
  • Outdated: Microsoft.AspNetCore.Http.Features REDACTED:5 — Microsoft.AspNetCore.Http.Features 2.2.0 → 5.0.17 available (referenced by EventHub.Domain.Shared).
  • Outdated: Swashbuckle.AspNetCore.Annotations REDACTED:9 — Swashbuckle.AspNetCore.Annotations 6.7.2 → 10.3.1 available (referenced by EventHub.Domain.Shared).
  • Outdated: AutoMapper REDACTED:3 — REDACTED → 16.2.0 available (referenced by EventHub.Infrastructure).
  • Outdated: Scrutor REDACTED:33 — Scrutor 4.2.2 → 7.0.0 available (referenced by EventHub.Infrastructure).
  • Outdated: Swashbuckle.AspNetCore REDACTED:42 — Swashbuckle.AspNetCore 6.7.2 → 10.3.1 available (referenced by EventHub.Infrastructure).
  • Outdated: Stripe.net REDACTED:8 — Stripe.net 47.3.0 → 53.0.0 available (referenced by EventHub.Application).
AX6 · Interface segregation · Fat interface · ×2
  • Fat interface: IRepositoryBase<T> (21 members) source/EventHub.Domain/SeedWork/Persistence/IRepositoryBase.cs:16 — `IRepositoryBase<T>` declares 21 members under just 15 distinct name(s): `Update`, `FindAll`, `FindAll`, `FindByCondition`, `FindByCondition`, `PaginatedFind`, `PaginatedFind`, `PaginatedFindByCondition`, `PaginatedFindByCondition`, `ExistAsync`, `ExistAsync`, `Count`, `CountAsync`, `GetByIdAsync`, `GetByIdAsync`, `CreateAsync`, `CreateListAsync`, `Delete`, `DeleteList`, `SoftDelete`, `Restore`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 21 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 21 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: IUnitOfWork (33 members) source/EventHub.Domain/SeedWork/Persistence/IUnitOfWork.cs:15 — `IUnitOfWork` declares 33 members: `CommitAsync`, `BeginTransactionAsync`, `EndTransactionAsync`, `RollbackTransactionAsync`, `Categories`, `CommandInFunctions`, `Commands`, `Conversations`, `EmailAttachments`, `EmailContents`, `EventCategories`, `Events`, `EventSubImages`, `FavouriteEvents`, `Functions`, `Invitations`, `Messages`, `PaymentItems`, `Payments`, `Permissions`, `Reasons`, `Reviews`, `Tickets`, `TicketTypes`, `UserFollowers`, `Coupons`, `EventCoupons`, `Expenses`, `SubExpenses`, `Notifications`, `CachedCategories`, `CachedEvents`, `CachedReviews`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D27 · Navigability · Pass-through layer · ×2
  • Pass-through layer source/EventHub.Infrastructure/Services/HangfireService.cs:13 — HangfireService: all 8 public methods forward their arguments unchanged to BackgroundJob and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call BackgroundJob directly, or give the layer a job.
  • Pass-through layer source/EventHub.Domain/Aggregates/UserAggregate/User.cs:23 — User: all 3 public methods forward their arguments unchanged to _domainEvents and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _domainEvents directly, or give the layer a job.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
S1 · Web-Security Posture · No security response headers detected · ×2
  • No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • No security response headers detected source/EventHub.Presentation/Program.cs:9 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
C2 · Access Controls · No named authorization policies · ×1
  • No named authorization policies — Authorization IS enforced here (by imperative guard methods that throw on violation) — this is NOT a claim that the code is unprotected. What's missing is a NAMED rule set: the guards encode the access rules inline, so the rules can't be listed, reviewed or tested apart from the call sites that apply them. Recommendation, not a defect.
C2 · Access Controls · Thin authorization enforcement · ×1
  • Thin authorization enforcement — Only 1 imperative guard call site(s) — too few to demonstrate default-deny across handlers.
C3 · Audit Trail · Partial audit-trail evidence · ×1
  • Partial audit-trail evidence — 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.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D21 · Naming Consistency · Typo in class name · ×1
  • Typo in class name: 'SignUpCommnadHandler' contains a typo ('Commnad' instead of 'Command'). This breaks consistency with the standard naming convention observed in other handlers (e.g., 'CreateUserCommandHandler', 'UpdateReviewCommandHandler') and the command type itself ('SignUpCommand'). — Rename 'SignUpCommnadHandler' to 'SignUpCommandHandler'. (symbols: EventHub.Application.Commands.Auth.SignUp.SignUpCommnadHandler.Handle, EventHub.Application.Commands.Auth.SignUp.SignUpCommand)
D24 · Comment Value · redundant comment · ×1
  • redundant comment REDACTED:15 — "1, Exception Handler" — keep as order marker; the middleware list is self-evident
D26 · Project Cohesion · Split EventHub.Application · ×1
  • Split EventHub.Application — A generic catch-all name that is huge (10k LoC) and sprawls across 142 namespaces with no coherent theme. Suggested:
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D9 · Test Distribution · No tests found · ×1
  • No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (xUnit, NUnit or MSTest) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
DM9 · Scattered domain decisions · Rule about [EndTime, StartTime] decided in 3 places · ×1
  • Rule about [EndTime, StartTime] decided in 3 places — EventHub.Domain.Aggregates.EventAggregate.Event's [EndTime, StartTime] are judged in EventHub.Application.Queries.Event.GetCreatedEventsByUserId.GetCreatedEventsByUserIdQueryHandler, EventHub.Application.Queries.Event.GetFavouriteEventsByUserId.GetFavouriteEventsByUserIdQueryHandler, EventHub.Application.Queries.Event.GetPaginatedEvents.GetPaginatedEventsQueryHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions · Rule about [EventId, UserId] decided in 3 places · ×1
  • Rule about [EventId, UserId] decided in 3 places — EventHub.Domain.Aggregates.EventAggregate.ValueObjects.FavouriteEvent's [EventId, UserId] are judged in EventHub.Application.Commands.Event.FavouriteEvent.FavouriteEventCommandHandler, EventHub.Application.Commands.Event.UnfavouriteEvent.UnfavouriteEventCommandHandler, EventHub.Application.Queries.Event.GetEventById.GetEventByIdQueryHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions · Rule about [CommandId, FunctionId] decided in 2 places · ×1
  • Rule about [CommandId, FunctionId] decided in 2 places — EventHub.Domain.Aggregates.UserAggregate.ValueObjects.CommandInFunction's [CommandId, FunctionId] are judged in EventHub.Application.Commands.Permission.DisableCommandInFunction.DisableCommandInFunctionCommandHandler, EventHub.Application.Commands.Permission.EnableCommandInFunction.EnableCommandInFunctionCommandHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions · Rule about [FunctionId, RoleId] decided in 2 places · ×1
  • Rule about [FunctionId, RoleId] decided in 2 places — EventHub.Domain.Aggregates.UserAggregate.ValueObjects.Permission's [FunctionId, RoleId] are judged in EventHub.Application.Commands.Permission.AddFunctionToRole.AddFunctionToRoleCommandHandler, EventHub.Application.Commands.Permission.RemoveFunctionFromRole.RemoveFunctionFromRoleCommandHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions · Rule about [FollowedId, FollowerId] decided in 3 places · ×1
  • Rule about [FollowedId, FollowerId] decided in 3 places — EventHub.Domain.Aggregates.UserAggregate.ValueObjects.UserFollower's [FollowedId, FollowerId] are judged in EventHub.Application.Commands.User.Follow.FollowCommandHandler, EventHub.Application.Commands.User.Unfollow.UnfollowCommandHandler, EventHub.Application.Queries.Event.GetEventById.GetEventByIdQueryHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions · Rule about [EndDate, StartDate] decided in 2 places · ×1
  • Rule about [EndDate, StartDate] decided in 2 places — EventHub.Domain.Shared.SeedWork.DateRange's [EndDate, StartDate] are judged in EventHub.Application.Queries.Event.GetCreatedEventsByUserId.GetCreatedEventsByUserIdQueryHandler, EventHub.Application.Queries.Event.GetPaginatedEvents.GetPaginatedEventsQueryHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
ED3 · Event naming · Event not named in past tense · ×1
  • Event not named in past tense: CalculatePositivePercentageOfReviewDomainEvent source/EventHub.Domain/Events/CalculatePositivePercentageOfReviewDomainEvent.cs:5 — `CalculatePositivePercentageOfReviewDomainEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P4 · Deployment & Rollback · No rollback/health safety · ×1
  • No rollback/health safety — Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 97/286 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.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.2 `!` suppressions per 1k syntax nodes — 106 suppression(s) across the 460175 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.
Minor — 53 finding(s)
D12 · Dependency Hygiene · Outdated · ×46
  • Outdated: FluentValidation — FluentValidation 11.9.2 → 12.2.0 available (referenced by EventHub.Domain.Shared).
  • Outdated: Microsoft.AspNetCore.Authentication.Abstractions — Microsoft.AspNetCore.Authentication.Abstractions 2.2.0 → 2.3.13 available (referenced by EventHub.Domain.Shared).
  • Outdated: Microsoft.AspNetCore.Mvc.Abstractions — Microsoft.AspNetCore.Mvc.Abstractions 2.2.0 → 2.3.13 available (referenced by EventHub.Domain.Shared).
  • Outdated: Microsoft.Extensions.Identity.Core — Microsoft.Extensions.Identity.Core 8.0.7 → 10.0.13 available (referenced by EventHub.Domain.Shared).
  • Outdated: Newtonsoft.Json — Newtonsoft.Json 13.0.3 → 13.0.4 available (referenced by EventHub.Domain.Shared).
  • Outdated: SonarAnalyzer.CSharp — SonarAnalyzer.CSharp 9.24.0.89429 → 10.35.0.4138 available (referenced by EventHub.Domain.Shared).
  • Outdated: Microsoft.AspNetCore.OpenApi — Microsoft.AspNetCore.OpenApi 8.0.7 → 10.0.13 available (referenced by EventHub.Presentation).
  • Outdated: Microsoft.EntityFrameworkCore.Design — Microsoft.EntityFrameworkCore.Design 8.0.8 → 10.0.13 available (referenced by EventHub.Presentation).
  • Outdated: Microsoft.VisualStudio.Web.CodeGeneration.Design — Microsoft.VisualStudio.Web.CodeGeneration.Design 8.0.4 → 10.0.2 available (referenced by EventHub.Presentation).
  • Outdated: Serilog — Serilog 4.0.1 → 4.4.0 available (referenced by EventHub.Presentation).
  • Outdated: Serilog.Extensions.Hosting — Serilog.Extensions.Hosting 8.0.0 → 10.0.0 available (referenced by EventHub.Presentation).
  • Outdated: Bogus — Bogus 35.6.0 → 35.6.5 available (referenced by EventHub.Infrastructure.Persistence).
  • Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore — Microsoft.AspNetCore.Identity.EntityFrameworkCore 8.0.7 → 10.0.13 available (referenced by EventHub.Infrastructure.Persistence).
  • Outdated: Microsoft.EntityFrameworkCore.SqlServer — Microsoft.EntityFrameworkCore.SqlServer 8.0.7 → 10.0.13 available (referenced by EventHub.Infrastructure.Persistence).
  • Outdated: Microsoft.OpenApi — Microsoft.OpenApi 1.6.15 → 3.11.0 available (referenced by EventHub.Infrastructure.Persistence).
  • Outdated: Azure.Storage.Blobs — Azure.Storage.Blobs 12.21.1 → 12.30.1 available (referenced by EventHub.Infrastructure).
  • Outdated: Dapper — Dapper 2.1.35 → 2.1.89 available (referenced by EventHub.Infrastructure).
  • Outdated: FluentValidation.AspNetCore — FluentValidation.AspNetCore 11.3.0 → 11.3.1 available (referenced by EventHub.Infrastructure).
  • Outdated: Hangfire — Hangfire 1.8.14 → 1.8.25 available (referenced by EventHub.Infrastructure).
  • Outdated: Hangfire.Console.Extensions — Hangfire.Console.Extensions 2.0.0 → 2.1.2 available (referenced by EventHub.Infrastructure).
  • Outdated: Hangfire.Mongo — Hangfire.Mongo 1.10.7 → 1.17.0 available (referenced by EventHub.Infrastructure).
  • Outdated: MailKit — REDACTED → 4.18.1 available (referenced by EventHub.Infrastructure).
  • Outdated: MediatR — MediatR 12.4.0 → 14.2.0 available (referenced by EventHub.Infrastructure).
  • Outdated: MicroElements.Swashbuckle.FluentValidation — MicroElements.Swashbuckle.FluentValidation 6.0.0 → 7.2.2 available (referenced by EventHub.Infrastructure).
  • Outdated: Microsoft.AspNetCore.Authentication.Facebook — Microsoft.AspNetCore.Authentication.Facebook 8.0.7 → 10.0.13 available (referenced by EventHub.Infrastructure).
  • + 21 more in this group — see findings.md.
D19 · Documentation Quality · XML-doc coverage · ×6
  • XML-doc coverage: EventHub.Domain.Shared REDACTED — EventHub.Domain.Shared: 19 % XML-doc coverage (41/217).
  • XML-doc coverage: EventHub.Presentation REDACTED — EventHub.Presentation: 0 % XML-doc coverage (0/154).
  • XML-doc coverage: EventHub.Infrastructure.Persistence REDACTED — EventHub.Infrastructure.Persistence: 19 % XML-doc coverage (52/278).
  • XML-doc coverage: EventHub.Infrastructure REDACTED — EventHub.Infrastructure: 21 % XML-doc coverage (21/99).
  • XML-doc coverage: EventHub.Domain REDACTED — EventHub.Domain: 4 % XML-doc coverage (15/363).
  • XML-doc coverage: EventHub.Application REDACTED — EventHub.Application: 14 % XML-doc coverage (198/1384).
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: EventHub.Domain.Shared REDACTED:1 — EventHub.Domain.Shared: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6c3d9c95a89f412e9cb50f0600d1527a/history.json --exit-code 0 --source .6artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6c3d9c95a89f412e9cb50f0600d1527a/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .123artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list EventHub.sln package --vulnerable --include-transitive --format json16artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .17artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .1artifacts/raw/semgrep-gdpr.json
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—

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

Email — 35 field(s)
  • ForgotPasswordCommand.Email source/EventHub.Application/Commands/Auth/ForgotPassword/ForgotPasswordCommand.cs:26
  • ResetPasswordCommand.Email source/EventHub.Application/Commands/Auth/ResetPassword/ResetPasswordCommand.cs:34
  • SignUpCommand.Email source/EventHub.Application/Commands/Auth/SignUp/SignUpCommand.cs:30
  • ValidateUserCommand.Email source/EventHub.Application/Commands/Auth/ValidateUser/ValidateUserCommand.cs:29
  • CreateEventCommand.EmailContent source/EventHub.Application/Commands/Event/CreateEvent/CreateEventCommand.cs:73
  • UpdateEventCommand.EmailContent source/EventHub.Application/Commands/Event/UpdateEvent/UpdateEventCommand.cs:94
  • CheckoutCommand.CustomerEmail source/EventHub.Application/Commands/Payment/Checkout/CheckoutCommand.cs:37
  • CreateUserCommand.Email source/EventHub.Application/Commands/User/CreateUser/CreateUserCommand.cs:33
  • UpdateUserCommand.Email source/EventHub.Application/Commands/User/UpdateUser/UpdateUserCommand.cs:17
  • ForgotPasswordDto.Email source/EventHub.Application/SeedWork/DTOs/Auth/ForgotPasswordDto.cs:8
  • SignUpDto.Email source/EventHub.Application/SeedWork/DTOs/Auth/SignUpDto.cs:8
  • CreateEventDto.EmailContent source/EventHub.Application/SeedWork/DTOs/Event/CreateEventDto.cs:52
  • EventDetailDto.EmailContent source/EventHub.Application/SeedWork/DTOs/Event/EventDetailDto.cs:75
  • UpdateEventDto.EmailContent source/EventHub.Application/SeedWork/DTOs/Event/UpdateEventDto.cs:55
  • CheckoutDto.CustomerEmail source/EventHub.Application/SeedWork/DTOs/Payment/CheckoutDto.cs:7
  • PaymentDto.CustomerEmail source/EventHub.Application/SeedWork/DTOs/Payment/PaymentDto.cs:17
  • ValidateSessionResponseDto.CustomerEmail source/EventHub.Application/SeedWork/DTOs/Payment/ValidateSessionResponseDto.cs:15
  • CreateTicketDto.CustomerEmail source/EventHub.Application/SeedWork/DTOs/Ticket/CreateTicketDto.cs:12
  • TicketDto.CustomerEmail source/EventHub.Application/SeedWork/DTOs/Ticket/TicketDto.cs:17
  • AuthorDto.Email source/EventHub.Application/SeedWork/DTOs/User/AuthorDto.cs:11
  • CreateUserDto.Email source/EventHub.Application/SeedWork/DTOs/User/CreateUserDto.cs:11
  • ResetUserPasswordDto.Email source/EventHub.Application/SeedWork/DTOs/User/ResetUserPasswordDto.cs:11
  • UpdateUserDto.Email source/EventHub.Application/SeedWork/DTOs/User/UpdateUserDto.cs:14
  • UserDto.Email source/EventHub.Application/SeedWork/DTOs/User/UserDto.cs:16
  • ValidateUserDto.Email source/EventHub.Application/SeedWork/DTOs/User/ValidateUserDto.cs:8
  • EmailSettings.Email source/EventHub.Domain.Shared/Settings/EmailSettings.cs:5
  • EmailContent.EmailAttachments source/EventHub.Domain/Aggregates/EventAggregate/Entities/EmailContent.cs:28
  • Event.EmailContent source/EventHub.Domain/Aggregates/EventAggregate/Event.cs:80
  • EmailAttachment.EmailContentId source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/EmailAttachment.cs:17
  • EmailAttachment.EmailContent source/EventHub.Domain/Aggregates/EventAggregate/ValueObjects/EmailAttachment.cs:30
  • Payment.CustomerEmail source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:40
  • Ticket.CustomerEmail source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:36
  • ApplicationDbContext.EmailAttachments source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContext.cs:38
  • ApplicationDbContext.EmailContents source/EventHub.Infrastructure.Persistence/Data/ApplicationDbContext.cs:39
  • EmailService._emailSettings source/EventHub.Infrastructure/Mailler/EmailService.cs:17
Phone — 17 field(s)
  • SignUpCommand.PhoneNumber source/EventHub.Application/Commands/Auth/SignUp/SignUpCommand.cs:38
  • ValidateUserCommand.PhoneNumber source/EventHub.Application/Commands/Auth/ValidateUser/ValidateUserCommand.cs:37
  • CheckoutCommand.CustomerPhone source/EventHub.Application/Commands/Payment/Checkout/CheckoutCommand.cs:39
  • CreateUserCommand.PhoneNumber source/EventHub.Application/Commands/User/CreateUser/CreateUserCommand.cs:41
  • UpdateUserCommand.PhoneNumber source/EventHub.Application/Commands/User/UpdateUser/UpdateUserCommand.cs:19
  • SignUpDto.PhoneNumber source/EventHub.Application/SeedWork/DTOs/Auth/SignUpDto.cs:11
  • CheckoutDto.CustomerPhone source/EventHub.Application/SeedWork/DTOs/Payment/CheckoutDto.cs:9
  • PaymentDto.CustomerPhone source/EventHub.Application/SeedWork/DTOs/Payment/PaymentDto.cs:15
  • ValidateSessionResponseDto.CustomerPhone source/EventHub.Application/SeedWork/DTOs/Payment/ValidateSessionResponseDto.cs:13
  • CreateTicketDto.CustomerPhone source/EventHub.Application/SeedWork/DTOs/Ticket/CreateTicketDto.cs:10
  • TicketDto.CustomerPhone source/EventHub.Application/SeedWork/DTOs/Ticket/TicketDto.cs:15
  • CreateUserDto.PhoneNumber source/EventHub.Application/SeedWork/DTOs/User/CreateUserDto.cs:14
  • UpdateUserDto.PhoneNumber source/EventHub.Application/SeedWork/DTOs/User/UpdateUserDto.cs:17
  • UserDto.PhoneNumber source/EventHub.Application/SeedWork/DTOs/User/UserDto.cs:19
  • ValidateUserDto.PhoneNumber source/EventHub.Application/SeedWork/DTOs/User/ValidateUserDto.cs:11
  • Payment.CustomerPhone source/EventHub.Domain/Aggregates/PaymentAggregate/Payment.cs:35
  • Ticket.CustomerPhone source/EventHub.Domain/Aggregates/TicketAggregate/Ticket.cs:31
Name — 8 field(s)
  • CreateUserCommand.FullName source/EventHub.Application/Commands/User/CreateUser/CreateUserCommand.cs:57
  • UpdateUserCommand.FullName source/EventHub.Application/Commands/User/UpdateUser/UpdateUserCommand.cs:23
  • ConversationUserDto.FullName source/EventHub.Application/SeedWork/DTOs/Conversation/ConversationUserDto.cs:7
  • AuthorDto.FullName source/EventHub.Application/SeedWork/DTOs/User/AuthorDto.cs:14
  • CreateUserDto.FullName source/EventHub.Application/SeedWork/DTOs/User/CreateUserDto.cs:20
  • UpdateUserDto.FullName source/EventHub.Application/SeedWork/DTOs/User/UpdateUserDto.cs:23
  • UserDto.FullName source/EventHub.Application/SeedWork/DTOs/User/UserDto.cs:25
  • User.FullName source/EventHub.Domain/Aggregates/UserAggregate/User.cs:29
Date of birth — 6 field(s)
  • CreateUserCommand.Dob source/EventHub.Application/Commands/User/CreateUser/CreateUserCommand.cs:49
  • UpdateUserCommand.Dob source/EventHub.Application/Commands/User/UpdateUser/UpdateUserCommand.cs:21
  • CreateUserDto.Dob source/EventHub.Application/SeedWork/DTOs/User/CreateUserDto.cs:17
  • UpdateUserDto.Dob source/EventHub.Application/SeedWork/DTOs/User/UpdateUserDto.cs:20
  • UserDto.Dob source/EventHub.Application/SeedWork/DTOs/User/UserDto.cs:22
  • User.Dob source/EventHub.Domain/Aggregates/UserAggregate/User.cs:31

Issues: 152 · Warnings: 334 · Recommendations: 117 · Info: 53 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 19:54 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.

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