Public report of vany0114/microservices-dotnetcore-docker-sf-k8s, 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:40 UTC · Survey ID cd_b26a017939fd4fcbb636d2aae7474812

vany0114/microservices-dotnetcore-docker-sf-k8s

Measured 21 October 2026, 19:35 UTC, at code version 125a43c

Code coverage: not measuredIL efficiency: not measured

Code coverage is not measured: No coverage collector is wired up.

IL efficiency is not measured: The target did not build.

CAI score 30out of 100 At risk Down 2 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.

Event-Driven 77 Strong Architecture 65 Adequate Accessibility 63 Adequate Performance 60 Adequate Maturity 48 Weak Code Health 46 Weak Domain Modelling 44 Weak Production Readiness 36 Weak Security and Compliance 15 Critical

A small codebase: 8,038 lines of product code in 24 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Security and Compliance, 15

Findings by how serious they are

148 critical 439 serious 212 minor

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

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
21 October 2026, 19:35 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 ▸

95of 100 dimensions measured by tools. The other 5 are advisory notes from an AI model, which explain the code but don't count towards the score.
777of 799 findings point to an exact file and line, so you can open each one in the code. The other 22 concern the repository as a whole, such as missing documentation.
100dimensions across 9 lenses, read from 8,038 lines of product code in 24 projects.
Chapters

Executive summary

vany0114/microservices-dotnetcore-docker-sf-k8s scores 30 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 Security and Compliance, which scores 15 and is rated Critical. Its Dependency Vulnerabilities dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault and to protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler, and if Security and Compliance rose to 70, the score would rise from 30 to about 42.

148 findings are critical: 40 in Domain ↔ infrastructure boundary, 28 in IaC & Container Security, 26 in Dependency Vulnerabilities, 15 in Explicit Debt, eight in Secrets (history), seven in REDACTED Scanning, five in Integration-event coupling, four in Aggregate boundaries, four in Coupling, four in Test Quality, three in Dependency direction, one in Forms & labels, one in Outbox / dual-write, one in Page structure and one in Project dependency cycles.

Watchdog couldn't measure Test Reliability, Dependency Hygiene and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 8,038 lines, which would take an estimated 0.1 person-years, around €12,000, to rebuild.

Code Health 46 Weak, capped by Structured logging and Nullable reference types Architecture 65 Adequate Maturity 48 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 36 Weak, capped by Test Quality, REDACTED Scanning, CI/CD gates and Security & performance tooling Security and Compliance 15 ⚠ Critical, capped by Secrets (history), Static Analysis (SAST), Dependency Vulnerabilities, IaC & Container Security, Data Protection and Access Controls Domain Modelling 44 Weak, capped by Aggregate boundaries, Strongly-typed ids and Domain ↔ infrastructure boundary Event-Driven 77 Strong Accessibility 63 Adequate 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.
Security and Compliance 15 · counts for 45%Production Readiness 36 · counts for 25%Domain Modelling 44 · counts for 14%Code Health 46 · counts for 8%Maturity 48 · counts for 4%Performance 60 · counts for 2%Accessibility 63 · counts for 1%Architecture 65 · counts for 1%Event-Driven 77 · counts for 0%

If Security and Compliance rose from 15 to 70, the lowest score rated Strong, the score would rise from 30 to about 42.

Code composition: what the lines of code are
Business logic 13%Supporting code 75%Tests 1%Generated by tools 10%
New since the last survey: 126 findings

These 126 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.

  • REDACTED Scanning · REDACTED
  • REDACTED Scanning · REDACTED
  • REDACTED Scanning · REDACTED
  • REDACTED Scanning · REDACTED
  • REDACTED Scanning · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • IaC & Container Security · REDACTED
  • IaC & Container Security · REDACTED
  • IaC & Container Security · REDACTED
  • IaC & Container Security · REDACTED
  • IaC & Container Security · REDACTED
  • Access Controls · No authorization ExternalSystem/PaymentService/Controllers/PaymentController.cs
  • Access Controls · No authorization src/Application/Duber.Invoice.API/Controllers/HomeController.cs
  • Access Controls · No authorization src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs
  • Access Controls · No authorization src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs
  • Access Controls · No authorization src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs
  • Access Controls · No authorization src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs
  • Access Controls · No authorization src/Application/Duber.Trip.API/Controllers/EventStoreController.cs
  • Access Controls · No authorization src/Application/Duber.Trip.API/Controllers/EventStoreController.cs
  • Access Controls · No authorization src/Application/Duber.Trip.API/Controllers/HomeController.cs
  • Access Controls · No authorization src/Application/Duber.Trip.API/Controllers/TripController.cs
  • Access Controls · No authorization src/Application/Duber.Trip.API/Controllers/TripController.cs
  • Access Controls · No authorization src/Application/Duber.Trip.API/Controllers/TripController.cs
  • Access Controls · No authorization src/Application/Duber.Trip.API/Controllers/TripController.cs
  • Access Controls · No authorization src/Application/Duber.Trip.API/Controllers/TripController.cs
  • Access Controls · No authorization src/Application/Duber.Trip.API/Controllers/TripController.cs
  • Access Controls · No authorization src/Web/Duber.WebSite/Controllers/HomeController.cs
  • Access Controls · No authorization src/Web/Duber.WebSite/Controllers/HomeController.cs
  • Access Controls · No authorization src/Web/Duber.WebSite/Controllers/HomeController.cs
  • Access Controls · No authorization src/Web/Duber.WebSite/Controllers/HomeController.cs
  • Access Controls · No authorization src/Web/Duber.WebSite/Controllers/TripController.cs
  • Access Controls · No authorization src/Web/Duber.WebSite/Controllers/TripController.cs
  • Access Controls · No authorization src/Web/Duber.WebSite/Controllers/TripController.cs
  • Access Controls · No authorization src/Web/Duber.WebSite/Controllers/TripController.cs
  • Access Controls · No authorization src/Web/Duber.WebSite/Controllers/TripController.cs
  • Access Controls · No authorization src/Web/Duber.WebSite/Controllers/TripController.cs
  • Access Controls · No authorization src/Web/Duber.WebSite/Controllers/TripController.cs
  • Access Controls · No authorization src/Web/Duber.WebSite/Controllers/TripController.cs
  • Async correctness · Sync-over-async (deadlock risk) through `.Result` src/Application/Duber.Trip.API/Infrastructure/Repository/IdempotencyStoreProvider.cs
  • Cancellation propagation · Async method without CancellationToken: Handle src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/InvoiceCreatedIntegrationEventHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Handle src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/InvoicePaidIntegrationEventHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Handle src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/TripCreatedIntegrationEventHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Handle src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/TripUpdatedIntegrationEventHandler.cs
  • Cancellation propagation · Async method without CancellationToken: AddTripAsync src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateTripAsync src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetTripsAsync src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetTripAsync src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetTripsByUserAsync src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetTripsByDriverAsync src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs
  • Cancellation propagation · Async method without CancellationToken: ExecuteAsync src/Domain/Invoice/Duber.Domain.Invoice/Persistence/InvoiceContext.cs
  • Cancellation propagation · Async method without CancellationToken: QueryAsync src/Domain/Invoice/Duber.Domain.Invoice/Persistence/InvoiceContext.cs
  • Cancellation propagation · Async method without CancellationToken: QuerySingleAsync src/Domain/Invoice/Duber.Domain.Invoice/Persistence/InvoiceContext.cs
  • Cancellation propagation · Async method without CancellationToken: GetInvoiceAsync src/Domain/Invoice/Duber.Domain.Invoice/Repository/InvoiceRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetInvoiceByTripAsync src/Domain/Invoice/Duber.Domain.Invoice/Repository/InvoiceRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetInvoicesAsync src/Domain/Invoice/Duber.Domain.Invoice/Repository/InvoiceRepository.cs
  • Cancellation propagation · Async method without CancellationToken: AddInvoiceAsync src/Domain/Invoice/Duber.Domain.Invoice/Repository/InvoiceRepository.cs
  • Cancellation propagation · Async method without CancellationToken: AddPaymentInfo src/Domain/Invoice/Duber.Domain.Invoice/Repository/InvoiceRepository.cs
  • Cancellation propagation · Async method without CancellationToken: PerformPayment src/Domain/Invoice/Duber.Domain.Invoice/Services/PaymentService.cs
  • Cancellation propagation · Async method without CancellationToken: Handle src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripCancelledIntegrationEventHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Handle src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripFinishedIntegrationEventHandler.cs
  • Dependency direction · Dependency-rule violation: Duber.Domain.ACL (Domain) → Duber.Infrastructure.Resilience.Http (Infrastructure) src/Domain/Duber.Domain.ACL/Adapters/PaymentServiceAdapter.cs
  • Dependency direction · Dependency-rule violation: Duber.Domain.Invoice (Domain) → Duber.Infrastructure.EventBus (Infrastructure) src/Domain/Invoice/Duber.Domain.Invoice/Events/InvoiceCreatedDomainEvent.cs
  • Dependency direction · Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs
  • Dependency direction · Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Model/DriverStatus.cs
  • Dependency direction · Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Model/Vehicle.cs
  • Dependency direction · Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Model/VehicleType.cs
  • Dependency direction · Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Persistence/DriverContext.cs
  • Dependency direction · Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Repository/DriverRepository.cs
  • Dependency direction · Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Repository/IDriverRepository.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InvoiceCreatedDomainEventHandler src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoiceCreatedDomainEventHandler.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InvoiceCreatedDomainEventHandler src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoiceCreatedDomainEventHandler.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InvoicePaidDomainEventHandler src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoicePaidDomainEventHandler.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InvoicePaidDomainEventHandler src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoicePaidDomainEventHandler.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: TripCreatedDomainEventHandlerAsync src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripCreatedDomainEventHandlerAsync.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: TripCreatedDomainEventHandlerAsync src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripCreatedDomainEventHandlerAsync.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: TripUpdatedDomainEventHandlerAsync src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: TripUpdatedDomainEventHandlerAsync src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: TripUpdatedDomainEventHandlerAsync src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: TripUpdatedDomainEventHandlerAsync src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: TripUpdatedIdempotentEventHandler src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: TripUpdatedIdempotentEventHandler src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: DriverContextModelSnapshot src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: DriverContextModelSnapshot src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: DriverContextModelSnapshot src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs

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: 22 findings

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

  • Coupling · Off the main sequence: Duber.Infrastructure.WebHost
  • Coupling · Off the main sequence: Duber.Infrastructure.Resilience.Http
  • Explicit Debt · WriteOnlyPrivateField src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs
  • Explicit Debt · WriteOnlyPrivateField src/Domain/Driver/Duber.Domain.Driver/Model/Vehicle.cs
  • Static Analysis (SAST) · Medium: missing-or-broken-authorization ExternalSystem/PaymentService/Controllers/PaymentController.cs
  • Static Analysis (SAST) · Medium: missing-or-broken-authorization src/Application/Duber.Invoice.API/Controllers/HomeController.cs
  • Static Analysis (SAST) · Medium: missing-or-broken-authorization src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs
  • Static Analysis (SAST) · Medium: missing-or-broken-authorization src/Application/Duber.Trip.API/Controllers/EventStoreController.cs
  • Static Analysis (SAST) · Medium: missing-or-broken-authorization src/Application/Duber.Trip.API/Controllers/HomeController.cs
  • Static Analysis (SAST) · Medium: missing-or-broken-authorization src/Application/Duber.Trip.API/Controllers/TripController.cs
  • Static Analysis (SAST) · Medium: missing-or-broken-authorization src/Web/Duber.WebSite/Controllers/HomeController.cs
  • Static Analysis (SAST) · Medium: missing-or-broken-authorization src/Web/Duber.WebSite/Controllers/TripController.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InitialCreate src/Domain/Invoice/Duber.Domain.Invoice/Migrations/20180407204749_InitialCreate.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: PaymentInfo src/Domain/Invoice/Duber.Domain.Invoice/Migrations/20180410015654_PaymentInfo.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InvoiceMigrationContextModelSnapshot src/Domain/Invoice/Duber.Domain.Invoice/Migrations/InvoiceMigrationContextModelSnapshot.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: DriverContextModelSnapshot src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs
  • Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: DriverRepository src/Domain/Driver/Duber.Domain.Driver/Repository/DriverRepository.cs
  • Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: PaymentServiceAdapter src/Domain/Duber.Domain.ACL/Adapters/PaymentServiceAdapter.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: InitialCreate src/Domain/User/Duber.Domain.User/Migrations/20180328010407_InitialCreate.cs
  • Domain ↔ infrastructure boundary · Domain depends on infrastructure: UserContextModelSnapshot src/Domain/User/Duber.Domain.User/Migrations/UserContextModelSnapshot.cs
  • Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: UserRepository src/Domain/User/Duber.Domain.User/Repository/UserRepository.cs
Rebuild cost: about €12,000 · Estimate
Cost to rebuild€4,000 to €20,000, for 67 to 212 hours of work, about 0.1 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 30. 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.
SizeSmall: 8,038 lines of product code

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

Top priorities

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

1
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.).
Raises the score by about 9 points · Medium effort · Data Protection
2
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Raises the score by about 9 points · Medium effort · Access Controls
3
Resolve the 7 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED, REDACTED.
Raises the score by about 3 points · Low effort · REDACTED Scanning

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 €12,000 to build again, about 0.1 person-years of work. Its weakest lens is Security and Compliance, at 15 (Critical). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Of all the actions in this report, it raises the score most for the work it takes: about 9 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — bounded-context dependency graph

Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.

arch Invoice.API Invoice.API ctx:Domain Domain 6 projects Invoice.API->ctx:Domain ctx:Infrastructure Infrastructure 9 projects Invoice.API->ctx:Infrastructure Trip.API Trip.API Trip.API->ctx:Domain Trip.API->ctx:Infrastructure Trip.Notifications Trip.Notifications Trip.Notifications->ctx:Infrastructure WebSite WebSite WebSite->ctx:Domain WebSite->ctx:Infrastructure PaymentService PaymentService ctx:Domain->ctx: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.

82 modules, with 101 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 42 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 Infrastructure.DDD2 Infrastructure.EventBus3 Infrastructure.EventBus.Events4 Infrastructure.Repository.Abstractions5 Infrastructure.Resilience.Abstractions6 Infrastructure.Resilience.Http7 WebSite.Models8 Domain.Driver.Model9 Domain.SharedKernel.Model10 Infrastructure.EventBus.Abstractions11 Invoice.API.Application.IntegrationEvents.Events12 Trip.API.Application.IntegrationEvents13 WebSite.Infrastructure.Repository14 Domain.ACL.Contracts15 Domain.Driver.Persistence16 Domain.Invoice.Events17 Domain.Invoice.Model18 Domain.Trip.Events19 Domain.User.Model20 Infrastructure.EventBus.Idempotency21 Infrastructure.EventBus.RabbitMQ22 Infrastructure.EventBus.ServiceBus23 Trip.Notifications.Application.IntegrationEvents.Handlers24 Domain.ACL.Adapters25 Domain.Driver.Repository26 Domain.Invoice.Persistence27 Domain.Trip.Model28 Domain.User.Persistence29 Domain.User.Persistence.EntityConfigurations30 Trip.API.Application.DomainEventHandlers31 Domain.Invoice.Repository32 Domain.Trip.Commands33 Domain.User.Repository34 Trip.API.Controllers35 Domain.Invoice.Services36 Domain.Trip.Commands.Handlers37 WebSite.Application.IntegrationEvents.Handlers38 WebSite.Controllers39 Invoice.API.Application.IntegrationEvents.Hnadlers40 Invoice.API.Controllers
1 Infrastructure.DDD
2 Infrastructure.EventBus
3 Infrastructure.EventBus.Events
4 Infrastructure.Repository.Abstractions
5 Infrastructure.Resilience.Abstractions
6 Infrastructure.Resilience.Http
7 WebSite.Models
8 Domain.Driver.Model5
9 Domain.SharedKernel.Model3
10 Infrastructure.EventBus.Abstractions1
11 Invoice.API.Application.IntegrationEvents.Events4
12 Trip.API.Application.IntegrationEvents4
13 WebSite.Infrastructure.Repository22
14 Domain.ACL.Contracts1
15 Domain.Driver.Persistence17
16 Domain.Invoice.Events1
17 Domain.Invoice.Model33
18 Domain.Trip.Events43
19 Domain.User.Model21
20 Infrastructure.EventBus.Idempotency12
21 Infrastructure.EventBus.RabbitMQ111
22 Infrastructure.EventBus.ServiceBus111
23 Trip.Notifications.Application.IntegrationEvents.Handlers3
24 Domain.ACL.Adapters111
25 Domain.Driver.Repository221
26 Domain.Invoice.Persistence122
27 Domain.Trip.Model322
28 Domain.User.Persistence122
29 Domain.User.Persistence.EntityConfigurations11
30 Trip.API.Application.DomainEventHandlers3122
31 Domain.Invoice.Repository21
32 Domain.Trip.Commands12
33 Domain.User.Repository221
34 Trip.API.Controllers1
35 Domain.Invoice.Services121
36 Domain.Trip.Commands.Handlers12
37 WebSite.Application.IntegrationEvents.Handlers4411
38 WebSite.Controllers1311122
39 Invoice.API.Application.IntegrationEvents.Hnadlers2222
40 Invoice.API.Controllers11
Uses a module listed above itPart of a loopThe module itself
1 Infrastructure.DDD2 Infrastructure.EventBus3 Infrastructure.EventBus.Events4 Infrastructure.Repository.Abstractions5 Infrastructure.Resilience.Abstractions6 Infrastructure.Resilience.Http7 WebSite.Models8 Domain.Driver.Model9 Domain.SharedKernel.Model10 Infrastructure.EventBus.Abstractions11 Invoice.API.Application.IntegrationEvents.Events12 Trip.API.Application.IntegrationEvents13 WebSite.Infrastructure.Repository14 Domain.ACL.Contracts15 Domain.Driver.Persistence16 Domain.Invoice.Events17 Domain.Invoice.Model18 Domain.Trip.Events19 Domain.User.Model20 Infrastructure.EventBus.Idempotency21 Infrastructure.EventBus.RabbitMQ22 Infrastructure.EventBus.ServiceBus23 Trip.Notifications.Application.IntegrationEvents.Handlers24 Domain.ACL.Adapters25 Domain.Driver.Repository26 Domain.Invoice.Persistence27 Domain.Trip.Model28 Domain.User.Persistence29 Domain.User.Persistence.EntityConfigurations30 Trip.API.Application.DomainEventHandlers31 Domain.Invoice.Repository32 Domain.Trip.Commands33 Domain.User.Repository34 Trip.API.Controllers35 Domain.Invoice.Services36 Domain.Trip.Commands.Handlers37 WebSite.Application.IntegrationEvents.Handlers38 WebSite.Controllers39 Invoice.API.Application.IntegrationEvents.Hnadlers40 Invoice.API.ControllersInfrastructure.DDD1Infrastructure.EventBus2Infrastructure.EventBus.Events3Infrastructure.Repository.Abstractions4Infrastructure.Resilience.Abstractions5Infrastructure.Resilience.Http6WebSite.Models7Domain.Driver.Model8Domain.SharedKernel.Model9Infrastructure.EventBus.Abstractions10Invoice.API.Application.IntegrationEvents.Events11Trip.API.Application.IntegrationEvents12WebSite.Infrastructure.Repository13Domain.ACL.Contracts14Domain.Driver.Persistence15Domain.Invoice.Events16Domain.Invoice.Model17Domain.Trip.Events18Domain.User.Model19Infrastructure.EventBus.Idempotency20Infrastructure.EventBus.RabbitMQ21Infrastructure.EventBus.ServiceBus22Trip.Notifications.Application.IntegrationEvents.Handlers23Domain.ACL.Adapters24Domain.Driver.Repository25Domain.Invoice.Persistence26Domain.Trip.Model27Domain.User.Persistence28Domain.User.Persistence.EntityConfigurations29Trip.API.Application.DomainEventHandlers30Domain.Invoice.Repository31Domain.Trip.Commands32Domain.User.Repository33Trip.API.Controllers34Domain.Invoice.Services35Domain.Trip.Commands.Handlers36WebSite.Application.IntegrationEvents.Handlers37WebSite.Controllers38Invoice.API.Application.IntegrationEvents.Hnadlers39Invoice.API.Controllers4053144221171334321121111113111221122322122113122211222111211244111311122222211+42 more modules (most-connected shown)

At a glance — Code Health · 46% · Weak · gated by X4, X5 ·

The Good
D1 · .NET / C# Cyclomatic Complexity 10.0 D2 · .NET / C# Cognitive Complexity 9.8 D3 · .NET / C# God Classes 10.0 D4 · .NET / C# Code Duplication 9.1 D18 · .NET / C# Solution Shape 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 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
The Bad
D17 · .NET / C# Explicit Debt 6.9 X1 · Repo Async correctness 5.5
The Ugly
X2 · Repo Cancellation propagation 4.0 X4 · Repo Structured logging 3.2 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 65% · Adequate ·

The Good
D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 10.0 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 9.5 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0
The Bad
AX4 · Repo Dependency direction 5.4
The Ugly
AX10 · Repo Code composition 4.0 AX2 · Repo Stateful singletons 4.6

At a glance — Maturity · 48% · Weak · gated by D34, M2 ·

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

At a glance — Readiness · 36% · Weak · gated by D10, D13, P1, P3 ·

The Good
D9 · .NET / C# Test Distribution 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 10.0 P2 · Repo Observability 7.0 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 P7 · Repo Outbound HTTP resilience 10.0 P8 · Repo Schema migrations 10.0
The Ugly
D10 · .NET / C# Test Quality 0.0 D13 · .NET / C# REDACTED Scanning 0.0 P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0

At a glance — Security · 15% · Critical · gated by D28, D29, D30, D31, C1, C2 ·

The Good
D43 · .NET / C# Malicious Dependencies 10.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 Bad
D40 · .NET / C# Network Egress Confinement 6.0 D41 · .NET / C# Kernel & Syscall Confinement 6.0 D44 · .NET / C# Platform End-of-Life 6.0
The Ugly
D28 · .NET / C# Secrets (history) 2.0 D29 · .NET / C# Static Analysis (SAST) 3.4 D30 · .NET / C# Dependency Vulnerabilities 0.0 D31 · .NET / C# IaC & Container Security 0.0 C1 · Repo Data Protection 0.0 C2 · Repo Access Controls 0.0 S1 · Repo Web-Security Posture 4.0 X24 · Repo Document value interpolated into markup unescaped 2.7

At a glance — Domain Modelling · 44% · Weak · gated by DM1, DM2, DM6 ·

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

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

The Good
ED1 · Repo Handler temporal coupling 10.0 ED3 · Repo Event naming 9.7
The Bad
ED4 · Repo Outbox / dual-write 5.9

At a glance — Accessibility · 63% · Adequate ·

The Good
AC1 · Repo Text alternatives 10.0 AC6 · Repo Visual & motion safety 10.0
The Bad
AC2 · Repo Forms & labels 6.7 AC3 · Repo Page structure 5.4
The Ugly
AC7 · Repo A11y enforcement 4.0

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
A02:2025 — Security Misconfiguration360High / Critical
A03:2025 — Software Supply Chain Failures30High / Critical
A05:2025 — Injection21Medium
A07:2025 — Authentication Failures16High / Critical

Roadmap

First, secure sensitive data by implementing encryption at rest and managing keys in a vault, while enforcing strict default-deny access controls on all endpoints. Next, immediately resolve the 24 high-severity dependency vulnerabilities and address the 280 medium-severity issues in infrastructure and container configurations. Finally, harden the web security posture by pinning third-party scripts with integrity hashes, applying strict content security policies, and vendoring assets to eliminate uncontrolled external dependencies.

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

Do thisHelpsEffortDimension
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.).+9.2 ptsMediumData Protection
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.+9.2 ptsMediumAccess Controls
Resolve the 7 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED, REDACTED.+3.2 ptsLowREDACTED Scanning
Resolve the 4 No assertions (empty test) finding(s) in Test Quality — start with UnitTest1.cs (4).+3.0 ptsLowTest Quality
Resolve the 4 Test project verifies nothing finding(s) in Test Quality — start with UnitTest1.cs (4).+3.0 ptsLowTest Quality
Resolve the 5 High secret finding(s) in Secrets (history) — start with REDACTED (4), REDACTED.+2.5 ptsLowSecrets (history)
Resolve the 24 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (4), REDACTED (3).+4.5 ptsMediumDependency Vulnerabilities
Resolve the 1 No network policy finding(s) in Network Egress Confinement.+2.3 ptsLowNetwork Egress Confinement

File quality

Per-file score 0–10 — a quality signature. Of 91 files carrying findings, judged against the Production bar: 24% slop · 58% mixed · 18% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.3SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.3SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.3SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.3SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.3SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.6SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED1.6SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.6SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.8SlopIaC & Container Security: High IaC: REDACTED
REDACTED1.8SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.0SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED3.1SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED3.1SlopREDACTED Scanning: Leaked secret: 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 — 148

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

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

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

Could not be resolved — 7

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

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 95 of 100 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 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 — 100 dimensions across the health lenses
D1D2D3D4D5D6D9D10D13D14D15D17D18D19D20D21D24D26D27D28D29D30D31D34D35D40D41D43D44AC1AC2AC3AC6AC7AX1AX10AX2AX3AX4AX5AX6AX8C1C2DM1DM10DM11DM12DM2DM3DM4DM5DM6DM7DM8DM9ED1ED3ED4ED5GD1IC1M1M2M3M4P1P2P3P4P6P7P8PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 777 of 799 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 01a15ff5-b98c-7d31-9b95-b59d109c015d.

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.

  • D11 Test Reliability — 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. Test reliability not scored — the test tier(s) ran but surfaced none of this repository's 4 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
  • D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
  • 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 118 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.
  • D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'docker-compose.dcproj' because the file extension '.dcproj' is not associated with a language.
  • 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.
  • D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `deploy/sql/sqldeploy.parameters.json`, `REDACTED`, `ExternalSystem/PaymentService/appsettings.json`, `ExternalSystem/PaymentService/appsettings.Development.json`, `src/Web/Duber.WebSite/bundleconfig.json` and 6 more did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
  • D39 IL Efficiency — 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. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
  • 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) — rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden duber.invoice.api Warning context canceled sql.data Error context canceled nosql.data Error context canceled duber.website Warning context canceled duber.trip.notifications Warning context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: nosql.data Error context canceled duber.trip.notifications Warning context canceled duber.invoice.api Warning context canceled WARNING: Some service image(s) must be built from source by running: docker compose build duber.website externalsystem.payment duber.trip.api duber.trip.notifications duber.invoice.api 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.
  • 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. 45 further occurrence(s) are not listed individually; the score already reflects all 85.
  • 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. 26 further occurrence(s) are not listed individually; the score already reflects all 66.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • 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.
  • 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.
  • D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
  • D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • 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".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (5): D19, D21, D24, 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 Complexity10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cyclomatic complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

D2 · Cognitive Complexity9.8 / 10Stronggated by 1 serious finding✓ 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.8 / 10 · rule-coverage 100% · ceiling Prevented

1 method(s) exceeded the cognitive complexity threshold of 15; the worst was EventBusRabbitMQ.ProcessEvent at 16.

EventBusRabbitMQ.ProcessEvent (cognitive 16)src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/EventBusRabbitMQ.cs:237

What to do

  1. Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with EventBusRabbitMQ.ProcessEvent (cognitive 16). — Refactoring it lifts Cognitive Complexity from 9.9 to about 10.0/10.
  2. Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

D4 · Code Duplication9.1 / 10Stronggated by 17 serious findings✓ Tool-verified

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

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

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

17 duplicated block group(s) detected.

Duplicated block (15 lines × 2) · ×3src/Application/Duber.Trip.API/Application/Model/CreateTripCommand.cs:7
Duplicated block (19 lines × 2) · ×2src/Application/Duber.Invoice.API/Infrastructure/Filters/HttpGlobalExceptionFilter.cs:43
Duplicated block (11 lines × 3) · ×2src/Domain/Driver/Duber.Domain.Driver/Persistence/EntityConfigurations/DriverStatusEntityTypeConfiguration.cs:13
Duplicated block (11 lines × 2) · ×2src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/AsyncPolicies.cs:183
Duplicated block (36 lines × 2)src/Application/Duber.Invoice.API/Startup.cs:77

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

What to do

  1. Resolve the 3 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with CreateTripCommand.cs, SqlAsyncPolicyBuilder.cs, TripUpdatedIntegrationEvent.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Duplicated block (19 lines × 2) finding(s) in Code Duplication — start with HttpGlobalExceptionFilter.cs, TripCancelledIntegrationEventHandler.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Duplicated block (11 lines × 3) finding(s) in Code Duplication — start with DriverStatusEntityTypeConfiguration.cs, Program.cs. — One of this dimension's main actionable groups (2 warning-level).
  4. Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling10.0 / 10Adequategated by 4 critical findings✓ Tool-verified

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

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

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

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

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

Layer violation: Domain → Infrastructure · ×4REDACTED:12
Off the main sequence: Duber.Domain.SharedKernelsrc/Domain/Duber.Domain.SharedKernel/Duber.Domain.SharedKernel.csproj:1

What to do

  1. Resolve the 4 Layer violation finding(s) in Coupling — start with REDACTED, Duber.Domain.Driver.csproj, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
  2. Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: 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 28 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

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

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

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

4 test methods: 4 unit, 0 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

0 skipped, 4 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4 tests.

No assertions (empty test): TestMethod1 · ×4src/Domain/Invoice/Duber.Domain.Invoice.UnitTest/UnitTest1.cs:8
Test project verifies nothing: Duber.Domain.Driver.UnitTest · ×4src/Domain/Driver/Duber.Domain.Driver.UnitTest/UnitTest1.cs:8

What to do

  1. Resolve the 4 No assertions (empty test) finding(s) in Test Quality — start with UnitTest1.cs (4). — One of this dimension's main actionable groups (4 issue-level).
  2. Resolve the 4 Test project verifies nothing finding(s) in Test Quality — start with UnitTest1.cs (4). — One of this dimension's main actionable groups (4 warning-level).
  3. Stand up a CI pipeline, then gate Test Quality in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

7 secret(s) detected.

REDACTED

What to do

  1. Resolve the 7 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
  2. Stand up a CI pipeline, then gate REDACTED Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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 293 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 48 direct `PackageReference`(s), and 202 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 Debt6.9 / 10Adequate✓ 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 6.9 / 10 · rule-coverage 100% · ceiling Prevented

24 deducted debt markers + unmeasured dead symbols across 7894 LoC in the .NET projects (1.6/KLoC) → score 6.9. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

NoWarnInCsproj · ×8REDACTED:46
FileScopedPragmaDisable · ×4src/Application/Duber.Invoice.API/Extensions/ServiceCollectionExtensions.cs:25
WriteOnlyPrivateField · ×3src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/DefaultServiceBusPersisterConnection.cs:9
TodoComment · ×6src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoiceCreatedDomainEventHandler.cs:26
CommentedOutCode · ×2src/Web/Duber.WebSite/Controllers/HomeController.cs:29

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

What to do

  1. Resolve the 8 NoWarnInCsproj finding(s) in Explicit Debt — start with REDACTED (4), REDACTED (4). — One of this dimension's main actionable groups (8 issue-level).
  2. Resolve the 4 FileScopedPragmaDisable finding(s) in Explicit Debt — start with ServiceCollectionExtensions.cs, Program.cs, Startup.cs. — One of this dimension's main actionable groups (4 issue-level).
  3. Resolve the 3 WriteOnlyPrivateField finding(s) in Explicit Debt — start with HomeController.cs (2), DefaultServiceBusPersisterConnection.cs. — One of this dimension's main actionable groups (3 issue-level).
  4. Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

24 projects, 190 source files, 7942 hand-written lines of code (7894 production / 48 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 959 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 37 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 excellent: it states the project (Microservices w/ .NET Core, Docker and Service Fabric/Kubernetes), lists prerequisites/installation requirements with links to install docs, describes architecture/deployment via cross-linked external markdown files, provides screenshots for each subsystem, and ends with a support link. The deploy/redis/readme.md README is focused on its directory (Redis cache deployment) rather than the repository root, so it is not judged against the root's overview/installation/usage/contributing licence; the two are separate documents. A thin architecture document SF-architecture.md exists but is clipped mid-sentence ('## Deployment ... to see all about the deployment using a Service Fabric cluster.') and k8s-architecture.md is also clipped, so those two sections are present in the outline and not flagged as missing.

XML-doc coverage: Duber.WebSite · ×20REDACTED

What to do

  1. Improve Documentation Quality — currently 6.0/10. — The repository's root README is excellent: it states the project (Microservices w/ .NET Core, Docker and Service Fabric/Kubernetes), lists prerequisites/installation requirements with links to install docs, describes architecture/deployment via cross-linked external markdown files, provides screenshots for each subsystem, and ends with a support link. The deploy/redis/readme.md README is focused on its directory (Redis cache deployment) rather than the repository root, so it is not judged against the root's overview/installation/usage/contributing licence; the two are separate documents. A thin architecture document SF-architecture.md exists but is clipped mid-sentence ('## Deployment ... to see all about the deployment using a Service Fabric cluster.') and k8s-architecture.md is also clipped, so those two sections are present in the outline and not flagged as missing.

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

3 naming inconsistencies across 200 sampled symbols.

Typo in namespace: 'Hnadlers' instead of 'Handlers'. This creates a distinct namespace path from the standard 'Handlers' used elsewhere (e.g., Duber.WebSite.Application.IntegrationEvents.Handlers).
Typo in method name: 'GetAggreagates' is misspelled (missing 'g'). While 'QuerySingleAsync' is correctly spelled, the inconsistency here is internal to the first symbol's name itself, but more importantly, it stands out against the correct spelling used in other symbols like 'GetEventsAsync'.
Inconsistent terminology for phone number: '_numberPhone' vs standard '_name' pattern. While not a direct synonym conflict, 'numberPhone' is non-standard English phrasing compared to 'PhoneNumber' or 'Phone'. However, since it's a private field and distinct from other phone-related concepts (none listed), this is a minor style issue. A more significant inconsistency is found in the parameter naming for similar entities.

What to do

  1. Resolve the 1 Typo in namespace finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 Typo in method name finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 Inconsistent terminology for phone number 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

64 valuable / 2 redundant across 153 sampled comments; 2 shown with locations.

redundant comment · ×2ExternalSystem/PaymentService/Startup.cs:18

✓ On the Gold path — maintain.

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

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 of 24 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

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

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

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

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

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

94 % of calls cross a namespace and 11 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)2.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 2.0 / 10 · rule-coverage 100% · ceiling Documented

8 finding(s): 0 critical, 8 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 5 High secret finding(s) in Secrets (history) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
  2. Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), 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)3.4 / 10Weak✓ 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 3.4 / 10 · rule-coverage 100% · ceiling Documented

21 finding(s): 0 critical, 0 high, 21 medium, 0 low.

REDACTED
REDACTED

What to do

  1. Resolve the 15 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (15 warning-level).
  2. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).

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

D30 · Dependency Vulnerabilities0.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 0.0 / 10 · rule-coverage 100% · ceiling Documented

30 finding(s): 2 critical, 24 high, 4 medium, 0 low.

REDACTED
REDACTED
REDACTED

What to do

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

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

D31 · IaC & Container Security0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

360 finding(s): 0 critical, 28 high, 280 medium, 52 low.

REDACTED
REDACTED
REDACTED

What to do

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

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

D34 · Knowledge Freshness0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

37 of 37 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/AsyncPolicies.cs. Counted over 37 of the 186 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×37src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/AsyncPolicies.cs:1
Dormant codebase

What to do

  1. Resolve the 37 Orphaned file finding(s) in Knowledge Freshness — start with ServiceCollectionExtensions.cs (6), Startup.cs (4), TripController.cs (2). — One of this dimension's main actionable groups (37 recommendation-level).
  2. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D40 · Network Egress Confinement6.0 / 10Adequate✓ Tool-verified

What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.

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

0/2 network-egress controls present (network policy, egress restriction).

No network policy

What to do

  1. Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).

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

D41 · Kernel & Syscall Confinement6.0 / 10Adequate✓ Tool-verified

What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.

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

0/15 workload(s) run every container under a seccomp profile; 0/15 declare an AppArmor/SELinux profile.

No seccomp profile · ×15REDACTED:2

What to do

  1. Resolve the 15 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (15 recommendation-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life6.0 / 10Adequate✓ Tool-verified

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

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

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

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

End-of-life runtime: .NET netcoreapp3.1ExternalSystem/PaymentService/PaymentService.csproj:4

What to do

  1. Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with PaymentService.csproj. — One of this dimension's main actionable groups (1 warning-level).

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

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

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

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

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

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

  • This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. — src/Web/Duber.WebSite/Views/Trip/TripDetails.cshtml:91

What to do

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

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

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

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

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — src/Web/Duber.WebSite/Views/Shared/_Layout.cshtml:2
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/Web/Duber.WebSite/Views/Shared/_Layout.cshtml:2
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — src/Web/Duber.WebSite/Views/Trip/TripDetails.cshtml:16

What to do

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

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

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

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

AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

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

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

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

  • No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 13 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
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 composition4.0 / 10Weak✓ 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 singletons4.6 / 10Weak✓ 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.

  • `EventBusRabbitMQ` is a singleton (one shared instance) but mutates instance state outside any lock (_queueName, _consumerChannel; e.g. `_queueName` at line 59). — src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/EventBusRabbitMQ.cs:19
  • `InMemoryEventBusSubscriptionsManager` is a singleton (one shared instance) but mutates instance state outside any lock (_handlers, _eventTypes; e.g. `_handlers` at line 25). — src/Infrastructure/EventBus/Duber.Infrastructure.EventBus/InMemoryEventBusSubscriptionsManager.cs:9

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
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 Duber.Domain.Trip.Events ↔ Duber.Domain.Trip.Model depend on each other. The lightest dependency in the cycle is Duber.Domain.Trip.Model → Duber.Domain.Trip.Events (Duber.Domain.Trip.Model.Trip → Duber.Domain.Trip.Events.TripCreatedDomainEvent, 2 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. — src/Domain/Trip/Duber.Domain.Trip/Model/Trip.cs:3

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 direction5.4 / 10Adequate✓ 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.

  • `Duber.Domain.ACL` is a Domain project but references `Duber.Infrastructure.Resilience.Http`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — REDACTED:12
  • This Domain file depends on the Infrastructure project `Duber.Infrastructure.Resilience.Http`: it names `Duber.Infrastructure.Resilience.Http`, `ResilientHttpClient`. The inward dependency rule is broken here. It is named again on lines 13, 16. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Domain/Duber.Domain.ACL/Adapters/PaymentServiceAdapter.cs:7
  • `Duber.Domain.Invoice` is a Domain project but references `Duber.Infrastructure.EventBus`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — REDACTED:20
  • This Domain file depends on the Infrastructure project `Duber.Infrastructure.EventBus`: it names `Duber.Infrastructure.EventBus.Events`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Domain/Invoice/Duber.Domain.Invoice/Events/InvoiceCreatedDomainEvent.cs:1
  • `Duber.Domain.Driver` is a Domain project but references `Duber.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/Domain/Driver/Duber.Domain.Driver/Duber.Domain.Driver.csproj:28
  • This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.DDD`, `Entity`, `IAggregateRoot`. The inward dependency rule is broken here. It is named again on line 13. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:5
  • This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.DDD`, `Enumeration`. The inward dependency rule is broken here. It is named again on line 8. Depend on an abstraction the inner layer owns, implemented in the outer one. (×2) — src/Domain/Driver/Duber.Domain.Driver/Model/DriverStatus.cs:4, src/Domain/Driver/Duber.Domain.Driver/Model/VehicleType.cs:4
  • This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.DDD`, `Entity`. The inward dependency rule is broken here. It is named again on line 10. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Domain/Driver/Duber.Domain.Driver/Model/Vehicle.cs:2
  • This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.Repository.Abstractions`, `IUnitOfWork`. The inward dependency rule is broken here. It is named again on line 9. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Domain/Driver/Duber.Domain.Driver/Persistence/DriverContext.cs:3
  • This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.Repository.Abstractions`, `IUnitOfWork`. The inward dependency rule is broken here. It is named again on line 19. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Domain/Driver/Duber.Domain.Driver/Repository/DriverRepository.cs:5
  • This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.Repository.Abstractions`, `IRepository`. The inward dependency rule is broken here. It is named again on line 7. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Domain/Driver/Duber.Domain.Driver/Repository/IDriverRepository.cs:3

What to do

  • Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
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 segregation10.0 / 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.

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

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

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

C1 · Data Protection0.0 / 10Critical✓ Tool-verified

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

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

  • No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.

What to do

  • Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
  • Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C2 · Access Controls0.0 / 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.

  • No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • `PaymentController.PerformPayment` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — ExternalSystem/PaymentService/Controllers/PaymentController.cs:16
  • `HomeController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×3) — src/Application/Duber.Invoice.API/Controllers/HomeController.cs:8, src/Application/Duber.Trip.API/Controllers/HomeController.cs:8, src/Web/Duber.WebSite/Controllers/HomeController.cs:26
  • `InvoiceController.GetInvoice` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs:39
  • `InvoiceController.GetInvoiceByTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs:68
  • `InvoiceController.GetInvoices` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs:96
  • `InvoiceController.CreateInvoice` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs:124
  • `EventStoreController.GetAggreagates` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Application/Duber.Trip.API/Controllers/EventStoreController.cs:31
  • `EventStoreController.GetEventsByAggregate` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Application/Duber.Trip.API/Controllers/EventStoreController.cs:52
  • `TripController.GetTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Application/Duber.Trip.API/Controllers/TripController.cs:40
  • `TripController.CreateTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Application/Duber.Trip.API/Controllers/TripController.cs:61
  • `TripController.AcceptTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Application/Duber.Trip.API/Controllers/TripController.cs:79
  • `TripController.StartTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Application/Duber.Trip.API/Controllers/TripController.cs:98
  • `TripController.CancelTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Application/Duber.Trip.API/Controllers/TripController.cs:117
  • `TripController.UpdateCurrentLocation` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Application/Duber.Trip.API/Controllers/TripController.cs:136
  • `HomeController.About` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Web/Duber.WebSite/Controllers/HomeController.cs:47
  • `HomeController.Contact` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Web/Duber.WebSite/Controllers/HomeController.cs:54
  • `HomeController.Error` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Web/Duber.WebSite/Controllers/HomeController.cs:61
  • `TripController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Web/Duber.WebSite/Controllers/TripController.cs:69
  • `TripController.SimulateTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Web/Duber.WebSite/Controllers/TripController.cs:91
  • `TripController.TripsByUser` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Web/Duber.WebSite/Controllers/TripController.cs:112
  • `TripController.TripsByUserId` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Web/Duber.WebSite/Controllers/TripController.cs:126
  • `TripController.TripById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Web/Duber.WebSite/Controllers/TripController.cs:139
  • `TripController.TripsByDriver` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Web/Duber.WebSite/Controllers/TripController.cs:152
  • `TripController.TripsByDriverId` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Web/Duber.WebSite/Controllers/TripController.cs:166
  • `TripController.Test` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Web/Duber.WebSite/Controllers/TripController.cs:179

What to do

  • Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
DM1 · Aggregate boundaries2.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.

  • `Driver` references the aggregate root `Vehicle` directly (via `_currentVehicle`) — hold its `VehicleId` instead. — src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:19
  • `Driver` references the aggregate root `Vehicle` directly (via `_vehicles`) — hold its `VehicleId` instead. — src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:25
  • `Driver` references the aggregate root `Vehicle` directly (via `CurrentVehicle`) — hold its `VehicleId` instead. — src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:35
  • `Driver` references the aggregate root `Vehicle` directly (via `Vehicles`) — hold its `VehicleId` instead. — src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:44

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 aggregate10.0 / 10Exemplary○ Nothing flagged

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.

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.

  • `Trip` reads `DateTime.UtcNow` inside `Start`, `FinishEarlier`, `Cancel`, `SetCurrentLocation`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/Domain/Trip/Duber.Domain.Trip/Model/Trip.cs:120

What to do

  • Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
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.

  • `InvoiceCreatedDomainEvent.InvoiceId` 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. — src/Domain/Invoice/Duber.Domain.Invoice/Events/InvoiceCreatedDomainEvent.cs:18
  • `InvoiceCreatedDomainEvent.TripId` 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. — src/Domain/Invoice/Duber.Domain.Invoice/Events/InvoiceCreatedDomainEvent.cs:20
  • `InvoicePaidDomainEvent.InvoiceId` 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. — src/Domain/Invoice/Duber.Domain.Invoice/Events/InvoicePaidDomainEvent.cs:18
  • `InvoicePaidDomainEvent.TripId` 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. — src/Domain/Invoice/Duber.Domain.Invoice/Events/InvoicePaidDomainEvent.cs:20
  • `Invoice.InvoiceId` 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. — src/Domain/Invoice/Duber.Domain.Invoice/Model/Invoice.cs:30
  • `TripCreatedDomainEvent.UserTripId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/Domain/Trip/Duber.Domain.Trip/Events/TripCreatedDomainEvent.cs:9
  • `TripCreatedDomainEvent.DriverId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/Domain/Trip/Duber.Domain.Trip/Events/TripCreatedDomainEvent.cs:11
  • `TripCreatedDomainEvent.ConnectionId` 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. — src/Domain/Trip/Duber.Domain.Trip/Events/TripCreatedDomainEvent.cs:23
  • `TripUpdatedDomainEvent.UserTripId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/Domain/Trip/Duber.Domain.Trip/Events/TripUpdatedDomainEvent.cs:26
  • `TripUpdatedDomainEvent.ConnectionId` 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. — src/Domain/Trip/Duber.Domain.Trip/Events/TripUpdatedDomainEvent.cs:28
  • `Trip.ConnectionId` 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. — src/Domain/Trip/Duber.Domain.Trip/Model/Trip.cs:30
  • `Trip.UserId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/Domain/Trip/Duber.Domain.Trip/Model/Trip.cs:32
  • `Trip.DriverId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/Domain/Trip/Duber.Domain.Trip/Model/Trip.cs:34

What to do

  • Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM3 · Integration-event coupling4.6 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether cross-context integration events stay loosely coupled — no producer-owned enums/domain types leaking to consumers. Shared-kernel/contracts types are allowed.

Method: Roslyn (DDD-gated): integration-event properties scanned for producer-domain type/enum leaks versus primitives and shared-kernel types. Deterministic, hard fact.

  • `InvoicePaidIntegrationEvent.Status` exposes `PaymentStatus`, a enum owned by the producer's domain assembly (`Duber.WebSite`) — carry the enum as a string/int instead. — src/Web/Duber.WebSite/Application/IntegrationEvents/Events/InvoicePaidIntegrationEvent.cs:21
  • `TripUpdatedIntegrationEvent.Action` exposes `Action`, a enum owned by the producer's domain assembly (`Duber.WebSite`) — carry the enum as a string/int instead. — src/Web/Duber.WebSite/Application/IntegrationEvents/Events/TripUpdatedIntegrationEvent.cs:22
  • `InvoicePaidIntegrationEvent.Status` exposes `PaymentStatus`, a enum owned by the producer's domain assembly (`Duber.Invoice.API`) — carry the enum as a string/int instead. — src/Application/Duber.Invoice.API/Application/IntegrationEvents/Events/InvoicePaidIntegrationEvent.cs:22
  • `TripUpdatedIntegrationEvent.Action` exposes `Action`, a enum owned by the producer's domain assembly (`Duber.Trip.API`) — carry the enum as a string/int instead. — src/Application/Duber.Trip.API/Application/IntegrationEvents/TripUpdatedIntegrationEvent.cs:24
  • `TripUpdatedIntegrationEvent.Action` exposes `Action`, a enum owned by the producer's domain assembly (`Duber.Trip.Notifications`) — carry the enum as a string/int instead. — src/Application/Duber.Trip.Notifications/Application/IntegrationEvents/Events/TripUpdatedIntegrationEvent.cs:13

What to do

  • Keep integration events to primitives + shared-contract types; never reference a producer-domain enum or type, so services evolve independently.
DM4 · Rich vs anemic model10.0 / 10Exemplary✓ 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.

DM5 · Encapsulated state10.0 / 10Exemplary✓ 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.

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.

  • `InvoiceCreatedDomainEventHandler` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoiceCreatedDomainEventHandler.cs:13, src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoiceCreatedDomainEventHandler.cs:16
  • `InvoicePaidDomainEventHandler` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoicePaidDomainEventHandler.cs:13, src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoicePaidDomainEventHandler.cs:16
  • `TripCreatedDomainEventHandlerAsync` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripCreatedDomainEventHandlerAsync.cs:14, src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripCreatedDomainEventHandlerAsync.cs:18
  • `TripUpdatedDomainEventHandlerAsync` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:17, src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:21
  • `TripUpdatedDomainEventHandlerAsync` (domain layer) names `IdempotentIntegrationEvent` from `Duber.Infrastructure.EventBus.Idempotency` — a persistence/infrastructure type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:53, src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:69
  • `TripUpdatedIdempotentEventHandler` (domain layer) names `IdempotentIntegrationEventHandler` from `Duber.Infrastructure.EventBus.Idempotency` — a persistence/infrastructure type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:76
  • `TripUpdatedIdempotentEventHandler` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:80
  • `InitialCreate` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs:7
  • `InitialCreate` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs:9, src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs:132
  • `InitialCreate` (domain layer) names `ReferentialAction` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×3) — src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs:71, src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs:96, src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs:103
  • `DriverContextModelSnapshot` (domain layer) names `DbContextAttribute` from `Microsoft.EntityFrameworkCore.Infrastructure` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:13
  • `DriverContextModelSnapshot` (domain layer) names `ModelSnapshot` from `Microsoft.EntityFrameworkCore.Infrastructure` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:14
  • `DriverContextModelSnapshot` (domain layer) names `ModelBuilder` from `Microsoft.EntityFrameworkCore` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:16
  • `DriverContextModelSnapshot` (domain layer) names `SqlServerValueGenerationStrategy` from `Microsoft.EntityFrameworkCore.Metadata` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×3) — src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:23, src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:31, src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:75
  • `DriverContextModelSnapshot` (domain layer) names `DeleteBehavior` from `Microsoft.EntityFrameworkCore` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×3) — src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:120, src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:128, src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:133
  • `Driver` (domain layer) names `Entity` from `Duber.Infrastructure.DDD` — a persistence/infrastructure type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:13
  • `DriverStatus` (domain layer) names `Enumeration` from `Duber.Infrastructure.DDD` — a persistence/infrastructure type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Driver/Duber.Domain.Driver/Model/DriverStatus.cs:8
  • `Vehicle` (domain layer) names `Entity` from `Duber.Infrastructure.DDD` — a persistence/infrastructure type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Driver/Duber.Domain.Driver/Model/Vehicle.cs:10
  • `VehicleType` (domain layer) names `Enumeration` from `Duber.Infrastructure.DDD` — a persistence/infrastructure type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Driver/Duber.Domain.Driver/Model/VehicleType.cs:8
  • `DriverRepository` (domain layer) names `DriverContext` from `Duber.Domain.Driver.Persistence` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/Domain/Driver/Duber.Domain.Driver/Repository/DriverRepository.cs:12, src/Domain/Driver/Duber.Domain.Driver/Repository/DriverRepository.cs:14
  • `DriverRepository` (domain layer) names `IUnitOfWork` from `Duber.Infrastructure.Repository.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Driver/Duber.Domain.Driver/Repository/DriverRepository.cs:19
  • `DriverRepository` (domain layer) names `EntityState` from `Microsoft.EntityFrameworkCore` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Driver/Duber.Domain.Driver/Repository/DriverRepository.cs:42
  • `IDriverRepository` (domain layer) names `IRepository` from `Duber.Infrastructure.Repository.Abstractions` — a persistence/infrastructure type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Driver/Duber.Domain.Driver/Repository/IDriverRepository.cs:7
  • `PaymentServiceAdapter` (domain layer) names `ResilientHttpClient` from `Duber.Infrastructure.Resilience.Http` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/Domain/Duber.Domain.ACL/Adapters/PaymentServiceAdapter.cs:13, src/Domain/Duber.Domain.ACL/Adapters/PaymentServiceAdapter.cs:16
  • `PaymentServiceAdapter` (domain layer) names `HttpRequestMessage` from `System.Net.Http` — a HTTP type (in a method body). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Duber.Domain.ACL/Adapters/PaymentServiceAdapter.cs:28
  • `PaymentInfo` (domain layer) names `ValueObject` from `Duber.Infrastructure.DDD` — a persistence/infrastructure type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Domain/Duber.Domain.SharedKernel/Model/PaymentInfo.cs:10

What to do

  • Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM7 · Repository granularity10.0 / 10Exemplary✓ 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.

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 decisions10.0 / 10Exemplary✓ 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.

ED1 · Handler temporal coupling10.0 / 10Exemplary✓ Tool-verified

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

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

ED3 · Event naming9.7 / 10Exemplary✓ 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.

  • `TripEventBase` 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. — src/Application/Duber.Trip.Notifications/Application/IntegrationEvents/Events/TripEventBase.cs:6
  • `IdempotentIntegrationEvent` 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. — src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.Idempotency/IdempotentIntegrationEvent.cs:6

What to do

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

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

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

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

What to do

  • Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
ED5 · Idempotency10.0 / 10Exemplary◐ 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.

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.

  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×12) — src/Web/Duber.WebSite/Controllers/HomeController.cs:29, src/Web/Duber.WebSite/Controllers/HomeController.cs:30, src/Web/Duber.WebSite/Controllers/HomeController.cs:31, …

What to do

  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)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 24 of 24 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.

  • Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.

What to do

  • Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
M4 · Documentation accuracy6.0 / 10Adequate◐ 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.

  • deploy/redis/readme.md links to `../readme.md`, but `deploy/readme.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — deploy/redis/readme.md:16
  • deploy/redis/readme.md names `deploy\az`, but no file or folder `deploy/az` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — deploy/redis/readme.md:18

What to do

  • Reconcile the README with reality: deploy/redis/readme.md links to `../readme.md`, but `deploy/readme.md` does not exist; deploy/redis/readme.md names `deploy\az`, but no file or folder `deploy/az` exists.
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

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

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

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability7.0 / 10Strong✓ Tool-verified

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

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

  • Only 10/15 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 15, 5 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
  • Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

  • Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

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.

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.

  • 6 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). (×2) — src/Web/Duber.WebSite/Program.cs:23, src/Web/Duber.WebSite/Program.cs:30
  • `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×3) — src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:67, src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:127, src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:217
  • `.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). — src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:93

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 Posture4.0 / 10Weak✓ 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.

  • `https://ajax.aspnetcdn.com/ajax/jquery.validate/1.16.0/jquery.validate.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 5 such include(s) across the repository's markup. — src/Web/Duber.WebSite/Views/Shared/_Layout.cshtml:51
  • 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. (×5) — ExternalSystem/PaymentService/Program.cs:21, src/Application/Duber.Invoice.API/Program.cs:21, src/Application/Duber.Trip.API/Program.cs:21, …
  • No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. (×5) — ExternalSystem/PaymentService/Program.cs:21, src/Application/Duber.Invoice.API/Program.cs:21, src/Application/Duber.Trip.API/Program.cs:21, …

What to do

  • Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
  • Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
  • Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
X1 · Async correctness5.5 / 10Adequate✓ 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. (×6) — src/Web/Duber.WebSite/Program.cs:21, src/Web/Duber.WebSite/Program.cs:28, src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:66, …
  • Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. — src/Application/Duber.Trip.API/Infrastructure/Repository/IdempotencyStoreProvider.cs:32

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 correctness10.0 / 10Exemplary○ Nothing flagged

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.

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 propagation4.0 / 10Weak✓ 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 0/65 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) — src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/InvoiceCreatedIntegrationEventHandler.cs:21, src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/InvoicePaidIntegrationEventHandler.cs:21, src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/TripCreatedIntegrationEventHandler.cs:28, …

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 unescaped2.7 / 10Weak✓ Tool-verified

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

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

  • `name` is text this program did not author, and it is written into the text of an element through `innerHTML` 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. — src/Web/Duber.WebSite/wwwroot/js/site.js:92
  • `response.statusText` is text this program did not author, and it is written into the text of an element through `innerHTML` 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. — src/Web/Duber.WebSite/wwwroot/js/site.js:97

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 logging3.2 / 10Weak✓ Tool-verified

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

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

  • Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×28) — src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/InvoiceCreatedIntegrationEventHandler.cs:31, src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/InvoicePaidIntegrationEventHandler.cs:31, src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/TripCreatedIntegrationEventHandler.cs:34, …

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types2.0 / 10Critical✓ 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/20 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

What to do

  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

WCAG coverage — what static analysis assessed

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

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

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

Reference — by lens

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

LensScoreRatingImpact
Code Health46%Weak — gated by X4, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture65%AdequateAcceptable, with room to improve.
Maturity48%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness36%Weak — gated by D10, D13, P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security15%Critical — gated by D28, D29, D30, D31, C1, C2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling44%Weak — gated by DM1, DM2, DM6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven77%StrongStrongest area.
Accessibility63%AdequateAcceptable, with room to improve.
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 — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data (event-sourced storage — lifecycle is stream archival / event TTL, not row CASCADE) — 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.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 28 check(s) not relevant to this codebase

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

  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden duber.invoice.api Warning context canceled sql.data Error context canceled nosql.data Error context canceled duber.website Warning context canceled duber.trip.notifications Warning context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: nosql.data Error context canceled duber.trip.notifications Warning context canceled duber.invoice.api Warning context canceled WARNING: Some service image(s) must be built from source by running: docker compose build duber.website externalsystem.payment duber.trip.api duber.trip.notifications duber.invoice.api 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.
  • D11 Test Reliability — Test runner surfaced no tests
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • 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 — small single-context codebase (7,894 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Aggregate roots were found in only one source directory (Domain), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling 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"]`.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — IL not measured — the target did not build
  • D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
  • ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
  • ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 aggregate(s) with Apply/When folds)
  • P12 CI test-gate honesty — no CI workflow found
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • 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 — 148 finding(s)
DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×40
  • Domain depends on infrastructure: InvoiceCreatedDomainEventHandler src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoiceCreatedDomainEventHandler.cs:13 — `InvoiceCreatedDomainEventHandler` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: InvoiceCreatedDomainEventHandler src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoiceCreatedDomainEventHandler.cs:16 — `InvoiceCreatedDomainEventHandler` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: InvoicePaidDomainEventHandler src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoicePaidDomainEventHandler.cs:13 — `InvoicePaidDomainEventHandler` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: InvoicePaidDomainEventHandler src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoicePaidDomainEventHandler.cs:16 — `InvoicePaidDomainEventHandler` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: TripCreatedDomainEventHandlerAsync src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripCreatedDomainEventHandlerAsync.cs:14 — `TripCreatedDomainEventHandlerAsync` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: TripCreatedDomainEventHandlerAsync src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripCreatedDomainEventHandlerAsync.cs:18 — `TripCreatedDomainEventHandlerAsync` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: TripUpdatedDomainEventHandlerAsync src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:17 — `TripUpdatedDomainEventHandlerAsync` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: TripUpdatedDomainEventHandlerAsync src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:21 — `TripUpdatedDomainEventHandlerAsync` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: TripUpdatedDomainEventHandlerAsync src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:53 — `TripUpdatedDomainEventHandlerAsync` (domain layer) names `IdempotentIntegrationEvent` from `Duber.Infrastructure.EventBus.Idempotency` — a persistence/infrastructure type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: TripUpdatedDomainEventHandlerAsync src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:69 — `TripUpdatedDomainEventHandlerAsync` (domain layer) names `IdempotentIntegrationEvent` from `Duber.Infrastructure.EventBus.Idempotency` — a persistence/infrastructure type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: TripUpdatedIdempotentEventHandler src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:76 — `TripUpdatedIdempotentEventHandler` (domain layer) names `IdempotentIntegrationEventHandler` from `Duber.Infrastructure.EventBus.Idempotency` — a persistence/infrastructure type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: TripUpdatedIdempotentEventHandler src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:80 — `TripUpdatedIdempotentEventHandler` (domain layer) names `IEventBus` from `Duber.Infrastructure.EventBus.Abstractions` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs:7 — `InitialCreate` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs:9 — `InitialCreate` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs:71 — `InitialCreate` (domain layer) names `ReferentialAction` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs:96 — `InitialCreate` (domain layer) names `ReferentialAction` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs:103 — `InitialCreate` (domain layer) names `ReferentialAction` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: InitialCreate src/Domain/Driver/Duber.Domain.Driver/Migrations/20180328053630_InitialCreate.cs:132 — `InitialCreate` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: DriverContextModelSnapshot src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:13 — `DriverContextModelSnapshot` (domain layer) names `DbContextAttribute` from `Microsoft.EntityFrameworkCore.Infrastructure` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: DriverContextModelSnapshot src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:14 — `DriverContextModelSnapshot` (domain layer) names `ModelSnapshot` from `Microsoft.EntityFrameworkCore.Infrastructure` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: DriverContextModelSnapshot src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:16 — `DriverContextModelSnapshot` (domain layer) names `ModelBuilder` from `Microsoft.EntityFrameworkCore` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: DriverContextModelSnapshot src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:23 — `DriverContextModelSnapshot` (domain layer) names `SqlServerValueGenerationStrategy` from `Microsoft.EntityFrameworkCore.Metadata` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: DriverContextModelSnapshot src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:31 — `DriverContextModelSnapshot` (domain layer) names `SqlServerValueGenerationStrategy` from `Microsoft.EntityFrameworkCore.Metadata` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: DriverContextModelSnapshot src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:75 — `DriverContextModelSnapshot` (domain layer) names `SqlServerValueGenerationStrategy` from `Microsoft.EntityFrameworkCore.Metadata` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: DriverContextModelSnapshot src/Domain/Driver/Duber.Domain.Driver/Migrations/DriverContextModelSnapshot.cs:120 — `DriverContextModelSnapshot` (domain layer) names `DeleteBehavior` from `Microsoft.EntityFrameworkCore` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • + 15 more in this group — see findings.md.
D31 · IaC & Container Security · High IaC · ×28
  • 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
  • + 3 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×24
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · NoWarnInCsproj · ×8
  • NoWarnInCsproj REDACTED:46 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj REDACTED:10 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj REDACTED:46 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj REDACTED:10 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj REDACTED:46 — 1705 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj REDACTED:10 — 1705 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj REDACTED:46 — 1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
  • NoWarnInCsproj REDACTED:10 — 1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
D13 · REDACTED Scanning · Leaked secret · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
DM3 · Integration-event coupling · Integration event couples to a producer-owned enum · ×5
  • Integration event couples to a producer-owned enum: InvoicePaidIntegrationEvent.Status src/Web/Duber.WebSite/Application/IntegrationEvents/Events/InvoicePaidIntegrationEvent.cs:21 — `InvoicePaidIntegrationEvent.Status` exposes `PaymentStatus`, a enum owned by the producer's domain assembly (`Duber.WebSite`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: TripUpdatedIntegrationEvent.Action src/Web/Duber.WebSite/Application/IntegrationEvents/Events/TripUpdatedIntegrationEvent.cs:22 — `TripUpdatedIntegrationEvent.Action` exposes `Action`, a enum owned by the producer's domain assembly (`Duber.WebSite`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: InvoicePaidIntegrationEvent.Status src/Application/Duber.Invoice.API/Application/IntegrationEvents/Events/InvoicePaidIntegrationEvent.cs:22 — `InvoicePaidIntegrationEvent.Status` exposes `PaymentStatus`, a enum owned by the producer's domain assembly (`Duber.Invoice.API`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: TripUpdatedIntegrationEvent.Action src/Application/Duber.Trip.API/Application/IntegrationEvents/TripUpdatedIntegrationEvent.cs:24 — `TripUpdatedIntegrationEvent.Action` exposes `Action`, a enum owned by the producer's domain assembly (`Duber.Trip.API`) — carry the enum as a string/int instead.
  • Integration event couples to a producer-owned enum: TripUpdatedIntegrationEvent.Action src/Application/Duber.Trip.Notifications/Application/IntegrationEvents/Events/TripUpdatedIntegrationEvent.cs:13 — `TripUpdatedIntegrationEvent.Action` exposes `Action`, a enum owned by the producer's domain assembly (`Duber.Trip.Notifications`) — carry the enum as a string/int instead.
D10 · Test Quality · No assertions (empty test) · ×4
  • No assertions (empty test): TestMethod1 src/Domain/Invoice/Duber.Domain.Invoice.UnitTest/UnitTest1.cs:8 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): TestMethod1 src/Domain/Trip/Duber.Domain.Trip.UnitTest/UnitTest1.cs:8 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): TestMethod1 src/Domain/Driver/Duber.Domain.Driver.UnitTest/UnitTest1.cs:8 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): TestMethod1 src/Domain/User/Duber.Domain.User.UnitTest/UnitTest1.cs:8 — Test method has an empty body — it asserts nothing and exercises no code.
D17 · Explicit Debt · FileScopedPragmaDisable · ×4
  • FileScopedPragmaDisable src/Application/Duber.Invoice.API/Extensions/ServiceCollectionExtensions.cs:25 — #pragma warning disable 618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/Application/Duber.Invoice.API/Program.cs:7 — #pragma warning disable 618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/Application/Duber.Invoice.API/Startup.cs:22 — #pragma warning disable 618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
  • FileScopedPragmaDisable src/Domain/Duber.Domain.SharedKernel/Model/PaymentInfo.cs:6 — #pragma warning disable 649 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
D5 · Coupling · Layer violation · ×4
  • Layer violation: Domain → Infrastructure REDACTED:12 — Duber.Domain.ACL (Domain) references Duber.Infrastructure.Resilience.Http (Infrastructure) — dependencies must point inward (Web → Application → Domain; Infrastructure implements inner interfaces, nothing depends outward on it).
  • Layer violation: Domain → Infrastructure src/Domain/Driver/Duber.Domain.Driver/Duber.Domain.Driver.csproj:28 — Duber.Domain.Driver (Domain) references Duber.Infrastructure (Infrastructure) — dependencies must point inward (Web → Application → Domain; Infrastructure implements inner interfaces, nothing depends outward on it).
  • Layer violation: Domain → Infrastructure REDACTED:20 — Duber.Domain.Invoice (Domain) references Duber.Infrastructure.EventBus (Infrastructure) — dependencies must point inward (Web → Application → Domain; Infrastructure implements inner interfaces, nothing depends outward on it).
  • Layer violation: Domain → Infrastructure src/Domain/Duber.Domain.SharedKernel/Duber.Domain.SharedKernel.csproj:8 — Duber.Domain.SharedKernel (Domain) references Duber.Infrastructure (Infrastructure) — dependencies must point inward (Web → Application → Domain; Infrastructure implements inner interfaces, nothing depends outward on it).
DM1 · Aggregate boundaries · Aggregate holds a reference to another aggregate · ×4
  • Aggregate holds a reference to another aggregate: Driver._currentVehicle src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:19 — `Driver` references the aggregate root `Vehicle` directly (via `_currentVehicle`) — hold its `VehicleId` instead.
  • Aggregate holds a reference to another aggregate: Driver._vehicles src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:25 — `Driver` references the aggregate root `Vehicle` directly (via `_vehicles`) — hold its `VehicleId` instead.
  • Aggregate holds a reference to another aggregate: Driver.CurrentVehicle src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:35 — `Driver` references the aggregate root `Vehicle` directly (via `CurrentVehicle`) — hold its `VehicleId` instead.
  • Aggregate holds a reference to another aggregate: Driver.Vehicles src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:44 — `Driver` references the aggregate root `Vehicle` directly (via `Vehicles`) — hold its `VehicleId` instead.
AX4 · Dependency direction · Dependency-rule violation · ×3
  • Dependency-rule violation: Duber.Domain.ACL (Domain) → Duber.Infrastructure.Resilience.Http (Infrastructure) REDACTED:12 — `Duber.Domain.ACL` is a Domain project but references `Duber.Infrastructure.Resilience.Http`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
  • Dependency-rule violation: Duber.Domain.Invoice (Domain) → Duber.Infrastructure.EventBus (Infrastructure) REDACTED:20 — `Duber.Domain.Invoice` is a Domain project but references `Duber.Infrastructure.EventBus`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
  • Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Duber.Domain.Driver.csproj:28 — `Duber.Domain.Driver` is a Domain project but references `Duber.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
D17 · Explicit Debt · WriteOnlyPrivateField · ×3
  • WriteOnlyPrivateField src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/DefaultServiceBusPersisterConnection.cs:9 — private ILogger<DefaultServiceBusPersisterConnection> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Web/Duber.WebSite/Controllers/HomeController.cs:17 — private IUserRepository _userRepository — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Web/Duber.WebSite/Controllers/HomeController.cs:18 — private IDriverRepository _driverRepository — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
D28 · Secrets (history) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×2
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <label> that labels no control · ×1
  • <label> that labels no control src/Web/Duber.WebSite/Views/Trip/TripDetails.cshtml:91 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC3 · Page structure · <html> without a lang · ×1
  • <html> without a lang src/Web/Duber.WebSite/Views/Shared/_Layout.cshtml:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle src/Domain/Trip/Duber.Domain.Trip/Model/Trip.cs:3 — The namespaces Duber.Domain.Trip.Events ↔ Duber.Domain.Trip.Model depend on each other. The lightest dependency in the cycle is Duber.Domain.Trip.Model → Duber.Domain.Trip.Events (Duber.Domain.Trip.Model.Trip → Duber.Domain.Trip.Events.TripCreatedDomainEvent, 2 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.
ED4 · Outbox / dual-write · Dual write (no outbox) · ×1
  • Dual write (no outbox): IdempotentIntegrationEventHandler.Handle src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.Idempotency/IdempotentIntegrationEventHandler.cs:28 — `IdempotentIntegrationEventHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Serious — 439 finding(s)
D31 · IaC & Container Security · Medium IaC · ×280
  • 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
  • + 255 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×39
  • Async method without CancellationToken: Handle src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/InvoiceCreatedIntegrationEventHandler.cs:21 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Handle src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/InvoicePaidIntegrationEventHandler.cs:21 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Handle src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/TripCreatedIntegrationEventHandler.cs:28 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Handle src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/TripUpdatedIntegrationEventHandler.cs:21 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Index src/Web/Duber.WebSite/Controllers/TripController.cs:69 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SimulateTrip src/Web/Duber.WebSite/Controllers/TripController.cs:91 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TripsByUser src/Web/Duber.WebSite/Controllers/TripController.cs:112 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TripsByUserId src/Web/Duber.WebSite/Controllers/TripController.cs:126 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TripById src/Web/Duber.WebSite/Controllers/TripController.cs:139 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TripsByDriver src/Web/Duber.WebSite/Controllers/TripController.cs:152 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TripsByDriverId src/Web/Duber.WebSite/Controllers/TripController.cs:166 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Test src/Web/Duber.WebSite/Controllers/TripController.cs:179 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetDrivers src/Web/Duber.WebSite/Controllers/TripController.cs:193 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetUsers src/Web/Duber.WebSite/Controllers/TripController.cs:199 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateTrip src/Web/Duber.WebSite/Controllers/TripController.cs:220 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AcceptOrStartTrip src/Web/Duber.WebSite/Controllers/TripController.cs:250 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateTripLocation src/Web/Duber.WebSite/Controllers/TripController.cs:262 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddTripAsync src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs:25 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateTripAsync src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs:43 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetTripsAsync src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs:49 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetTripAsync src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs:54 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetTripsByUserAsync src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs:65 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetTripsByDriverAsync src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs:74 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ExecuteAsync src/Domain/Invoice/Duber.Domain.Invoice/Persistence/InvoiceContext.cs:31 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: QueryAsync src/Domain/Invoice/Duber.Domain.Invoice/Persistence/InvoiceContext.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 14 more in this group — see findings.md.
C2 · Access Controls · No authorization · ×28
  • No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • No authorization ExternalSystem/PaymentService/Controllers/PaymentController.cs:16 — `PaymentController.PerformPayment` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Invoice.API/Controllers/HomeController.cs:8 — `HomeController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs:39 — `InvoiceController.GetInvoice` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs:68 — `InvoiceController.GetInvoiceByTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs:96 — `InvoiceController.GetInvoices` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs:124 — `InvoiceController.CreateInvoice` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Trip.API/Controllers/EventStoreController.cs:31 — `EventStoreController.GetAggreagates` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Trip.API/Controllers/EventStoreController.cs:52 — `EventStoreController.GetEventsByAggregate` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Trip.API/Controllers/HomeController.cs:8 — `HomeController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Trip.API/Controllers/TripController.cs:40 — `TripController.GetTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Trip.API/Controllers/TripController.cs:61 — `TripController.CreateTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Trip.API/Controllers/TripController.cs:79 — `TripController.AcceptTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Trip.API/Controllers/TripController.cs:98 — `TripController.StartTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Trip.API/Controllers/TripController.cs:117 — `TripController.CancelTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Application/Duber.Trip.API/Controllers/TripController.cs:136 — `TripController.UpdateCurrentLocation` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Web/Duber.WebSite/Controllers/HomeController.cs:26 — `HomeController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Web/Duber.WebSite/Controllers/HomeController.cs:47 — `HomeController.About` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Web/Duber.WebSite/Controllers/HomeController.cs:54 — `HomeController.Contact` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Web/Duber.WebSite/Controllers/HomeController.cs:61 — `HomeController.Error` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Web/Duber.WebSite/Controllers/TripController.cs:69 — `TripController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Web/Duber.WebSite/Controllers/TripController.cs:91 — `TripController.SimulateTrip` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Web/Duber.WebSite/Controllers/TripController.cs:112 — `TripController.TripsByUser` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Web/Duber.WebSite/Controllers/TripController.cs:126 — `TripController.TripsByUserId` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Web/Duber.WebSite/Controllers/TripController.cs:139 — `TripController.TripById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • + 3 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX4 · Dependency direction · Dependency-rule violation · ×9
  • Dependency-rule violation: Duber.Domain.ACL (Domain) → Duber.Infrastructure.Resilience.Http (Infrastructure) src/Domain/Duber.Domain.ACL/Adapters/PaymentServiceAdapter.cs:7 — This Domain file depends on the Infrastructure project `Duber.Infrastructure.Resilience.Http`: it names `Duber.Infrastructure.Resilience.Http`, `ResilientHttpClient`. The inward dependency rule is broken here. It is named again on lines 13, 16. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: Duber.Domain.Invoice (Domain) → Duber.Infrastructure.EventBus (Infrastructure) src/Domain/Invoice/Duber.Domain.Invoice/Events/InvoiceCreatedDomainEvent.cs:1 — This Domain file depends on the Infrastructure project `Duber.Infrastructure.EventBus`: it names `Duber.Infrastructure.EventBus.Events`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:5 — This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.DDD`, `Entity`, `IAggregateRoot`. The inward dependency rule is broken here. It is named again on line 13. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Model/DriverStatus.cs:4 — This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.DDD`, `Enumeration`. The inward dependency rule is broken here. It is named again on line 8. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Model/Vehicle.cs:2 — This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.DDD`, `Entity`. The inward dependency rule is broken here. It is named again on line 10. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Model/VehicleType.cs:4 — This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.DDD`, `Enumeration`. The inward dependency rule is broken here. It is named again on line 8. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Persistence/DriverContext.cs:3 — This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.Repository.Abstractions`, `IUnitOfWork`. The inward dependency rule is broken here. It is named again on line 9. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Repository/DriverRepository.cs:5 — This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.Repository.Abstractions`, `IUnitOfWork`. The inward dependency rule is broken here. It is named again on line 19. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: Duber.Domain.Driver (Domain) → Duber.Infrastructure (Infrastructure) src/Domain/Driver/Duber.Domain.Driver/Repository/IDriverRepository.cs:3 — This Domain file depends on the Infrastructure project `Duber.Infrastructure`: it names `Duber.Infrastructure.Repository.Abstractions`, `IRepository`. The inward dependency rule is broken here. It is named again on line 7. Depend on an abstraction the inner layer owns, implemented in the outer one.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×7
  • Sync-over-async blocking — 6 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 src/Web/Duber.WebSite/Program.cs:23 — `.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 src/Web/Duber.WebSite/Program.cs:30 — `.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 src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:67 — `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:93 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:127 — `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:217 — `.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).
D17 · Explicit Debt · TodoComment · ×6
  • TodoComment src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoiceCreatedDomainEventHandler.cs:26 — // TODO: make an async Publish method. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Application/Duber.Invoice.API/Application/DomainEventHandlers/InvoicePaidDomainEventHandler.cs:26 — // TODO: make an async Publish method. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripCreatedDomainEventHandlerAsync.cs:31 — // TODO: make an async Publish method. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:35 — // TODO: make an async Publish method. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Domain/Trip/Duber.Domain.Trip/Commands/Handlers/UpdateTripCommandHandlerAsync.cs:25 — // TODO: consider creating a separate command/handler for each action to avoid this code smell. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Domain/Trip/Duber.Domain.Trip/Model/Trip.cs:196 — // TODO: handle a tolerance range to determine if current location is the destination — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X1 · Async correctness · Sync-over-async (deadlock risk) · ×6
  • Sync-over-async (deadlock risk) src/Web/Duber.WebSite/Program.cs:21 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Web/Duber.WebSite/Program.cs:28 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:66 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:89 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:125 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:215 — 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.
D10 · Test Quality · Test project verifies nothing · ×4
  • Test project verifies nothing: Duber.Domain.Driver.UnitTest src/Domain/Driver/Duber.Domain.Driver.UnitTest/UnitTest1.cs:8 — No conventional assertion call was detected in 1 of 1 tests in `Duber.Domain.Driver.UnitTest` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: Duber.Domain.Invoice.UnitTest src/Domain/Invoice/Duber.Domain.Invoice.UnitTest/UnitTest1.cs:8 — No conventional assertion call was detected in 1 of 1 tests in `Duber.Domain.Invoice.UnitTest` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: Duber.Domain.Trip.UnitTest src/Domain/Trip/Duber.Domain.Trip.UnitTest/UnitTest1.cs:8 — No conventional assertion call was detected in 1 of 1 tests in `Duber.Domain.Trip.UnitTest` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: Duber.Domain.User.UnitTest src/Domain/User/Duber.Domain.User.UnitTest/UnitTest1.cs:8 — No conventional assertion call was detected in 1 of 1 tests in `Duber.Domain.User.UnitTest` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D30 · Dependency Vulnerabilities · Medium CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×3
  • Duplicated block (15 lines × 2) src/Application/Duber.Trip.API/Application/Model/CreateTripCommand.cs:7 — src/Application/Duber.Trip.API/Application/Model/CreateTripCommand.cs:7-21 | src/Domain/Trip/Duber.Domain.Trip/Commands/CreateTripCommand.cs:11-25 — 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 (15 lines × 2) src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Internals/SqlAsyncPolicyBuilder.cs:90 — src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Internals/SqlAsyncPolicyBuilder.cs:90-104 | src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Internals/SqlSyncPolicyBuilder.cs:89-103 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (15 lines × 2) src/Application/Duber.Trip.API/Application/IntegrationEvents/TripUpdatedIntegrationEvent.cs:22 — src/Application/Duber.Trip.API/Application/IntegrationEvents/TripUpdatedIntegrationEvent.cs:22-36 | src/Web/Duber.WebSite/Application/IntegrationEvents/Events/TripUpdatedIntegrationEvent.cs:20-34 — 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.
AX2 · Stateful singletons · Stateful singleton · ×2
  • Stateful singleton: EventBusRabbitMQ src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/EventBusRabbitMQ.cs:19 — `EventBusRabbitMQ` is a singleton (one shared instance) but mutates instance state outside any lock (_queueName, _consumerChannel; e.g. `_queueName` at line 59).
  • Stateful singleton: InMemoryEventBusSubscriptionsManager src/Infrastructure/EventBus/Duber.Infrastructure.EventBus/InMemoryEventBusSubscriptionsManager.cs:9 — `InMemoryEventBusSubscriptionsManager` is a singleton (one shared instance) but mutates instance state outside any lock (_handlers, _eventTypes; e.g. `_handlers` at line 25).
D17 · Explicit Debt · CommentedOutCode · ×2
  • CommentedOutCode src/Web/Duber.WebSite/Controllers/HomeController.cs:29 — 6 consecutive commented-code lines
  • CommentedOutCode src/Web/Duber.WebSite/Controllers/HomeController.cs:37 — 6 consecutive commented-code lines
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×2
  • Duplicated block (19 lines × 2) src/Application/Duber.Invoice.API/Infrastructure/Filters/HttpGlobalExceptionFilter.cs:43 — src/Application/Duber.Invoice.API/Infrastructure/Filters/HttpGlobalExceptionFilter.cs:43-61 | src/Application/Duber.Trip.API/Infrastructure/Filters/HttpGlobalExceptionFilter.cs:42-60 — before extracting anything, compare `src/Application/Duber.Invoice.API/Infrastructure/Filters/HttpGlobalExceptionFilter.cs` and `src/Application/Duber.Trip.API/Infrastructure/Filters/HttpGlobalExceptionFilter.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 `src/Application/Duber.Invoice.API/Infrastructure/Filters/HttpGlobalExceptionFilter.cs:43` 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 (19 lines × 2) src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripCancelledIntegrationEventHandler.cs:41 — src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripCancelledIntegrationEventHandler.cs:41-59 | src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripFinishedIntegrationEventHandler.cs:41-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripCancelledIntegrationEventHandler.cs:41` 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 (11 lines × 3) · ×2
  • Duplicated block (11 lines × 3) src/Domain/Driver/Duber.Domain.Driver/Persistence/EntityConfigurations/DriverStatusEntityTypeConfiguration.cs:13 — src/Domain/Driver/Duber.Domain.Driver/Persistence/EntityConfigurations/DriverStatusEntityTypeConfiguration.cs:13-23 | src/Domain/Driver/Duber.Domain.Driver/Persistence/EntityConfigurations/VehicleTypeEntityTypeConfiguration.cs:13-23 | src/Domain/User/Duber.Domain.User/Persistence/EntityConfigurations/PaymentMethodEntityTypeConfiguration.cs:13-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Domain/Driver/Duber.Domain.Driver/Persistence/EntityConfigurations/DriverStatusEntityTypeConfiguration.cs:13` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<DriverStatus>` in one and `EntityTypeBuilder<VehicleType>` 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 × 3) src/Application/Duber.Invoice.API/Program.cs:21 — src/Application/Duber.Invoice.API/Program.cs:21-31 | src/Application/Duber.Trip.API/Program.cs:21-31 | src/Web/Duber.WebSite/Program.cs:37-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Application/Duber.Invoice.API/Program.cs:21` 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, `src/Application/Duber.Invoice.API/Program.cs:32` calls `AddApplicationInsights` and `src/Web/Duber.WebSite/Program.cs:48` 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 (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/AsyncPolicies.cs:183 — src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/AsyncPolicies.cs:183-193 | src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/AsyncPolicies.cs:201-211 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/AsyncPolicies.cs:183` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Internals/SqlAsyncPolicyBuilder.cs:142 — src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Internals/SqlAsyncPolicyBuilder.cs:142-152 | src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Internals/SqlSyncPolicyBuilder.cs:141-151 — 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.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×2
  • Untrusted text written into markup unescaped src/Web/Duber.WebSite/wwwroot/js/site.js:92 — `name` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Web/Duber.WebSite/wwwroot/js/site.js:97 — `response.statusText` is text this program did not author, and it is written into the text of an element through `innerHTML` 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.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark src/Web/Duber.WebSite/Views/Shared/_Layout.cshtml:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC3 · Page structure · Heading level jumps from h2 to h4 · ×1
  • Heading level jumps from h2 to h4 src/Web/Duber.WebSite/Views/Trip/TripDetails.cshtml:16 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 13 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
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.
D2 · Cognitive Complexity · EventBusRabbitMQ.ProcessEvent (cognitive 16) · ×1
  • EventBusRabbitMQ.ProcessEvent (cognitive 16) src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/EventBusRabbitMQ.cs:237 — EventBusRabbitMQ.ProcessEvent has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) src/Application/Duber.Invoice.API/Startup.cs:77 — src/Application/Duber.Invoice.API/Startup.cs:77-112 | src/Application/Duber.Trip.API/Startup.cs:68-103 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Application/Duber.Invoice.API/Startup.cs:77` 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 `env` to `IHostingEnvironment` in one and `IWebHostEnvironment` 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 (22–25 lines × 2) · ×1
  • Duplicated block (22–25 lines × 2) src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/EventBusRabbitMQ.cs:241 — src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/EventBusRabbitMQ.cs:241-265 | src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:183-204 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/EventBusRabbitMQ.cs:241` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) src/Application/Duber.Invoice.API/Extensions/ServiceCollectionExtensions.cs:123 — src/Application/Duber.Invoice.API/Extensions/ServiceCollectionExtensions.cs:123-142 | src/Web/Duber.WebSite/Extensions/ServiceCollectionExtensions.cs:109-128 — 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 (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) src/Application/Duber.Invoice.API/Extensions/ServiceCollectionExtensions.cs:88 — src/Application/Duber.Invoice.API/Extensions/ServiceCollectionExtensions.cs:88-105 | src/Application/Duber.Trip.API/Extensions/ServiceCollectionExtensions.cs:49-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/AsyncPolicies.cs:41 — src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/AsyncPolicies.cs:41-57 | src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/AsyncPolicies.cs:66-82 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/AsyncPolicies.cs:41` 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 (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) src/Application/Duber.Invoice.API/Program.cs:22 — src/Application/Duber.Invoice.API/Program.cs:22-33 | src/Application/Duber.Trip.API/Program.cs:22-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Application/Duber.Invoice.API/Program.cs:22` 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 (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) src/Domain/Driver/Duber.Domain.Driver/Persistence/DriverContextSeed.cs:69 — src/Domain/Driver/Duber.Domain.Driver/Persistence/DriverContextSeed.cs:69-75 | src/Domain/User/Duber.Domain.User/Persistence/UserContextSeed.cs:54-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Domain/Driver/Duber.Domain.Driver/Persistence/DriverContextSeed.cs:69` 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 `logger` to `ILogger<DriverContextSeed>` in one and `ILogger<UserContextSeed>` 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 (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/EventBusRabbitMQ.cs:188 — src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/EventBusRabbitMQ.cs:188-193 | src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:157-162 — 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.
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: .NET netcoreapp3.1 ExternalSystem/PaymentService/PaymentService.csproj:4 — ExternalSystem/PaymentService/PaymentService.csproj declares .NET netcoreapp3.1 as this project's target framework, and .NET Core 3.1 LTS, support ended 2022-12-13. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-12-13 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
DM12 · Ambient inputs in the domain · Domain type reads the wall clock · ×1
  • Domain type reads the wall clock: Trip src/Domain/Trip/Duber.Domain.Trip/Model/Trip.cs:120 — `Trip` reads `DateTime.UtcNow` inside `Start`, `FinishEarlier`, `Cancel`, `SetCurrentLocation`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity src/Web/Duber.WebSite/Views/Shared/_Layout.cshtml:51 — `https://ajax.aspnetcdn.com/ajax/jquery.validate/1.16.0/jquery.validate.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 5 such include(s) across the repository's markup.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×1
  • Sync-over-async (deadlock risk) through `.Result` src/Application/Duber.Trip.API/Infrastructure/Repository/IdempotencyStoreProvider.cs:32 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Minor — 191 finding(s)
D31 · IaC & Container Security · Low IaC · ×52
  • 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
  • + 27 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×37
  • Orphaned file src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/AsyncPolicies.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Policies/SyncPolicies.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Web/Duber.WebSite/Controllers/TripController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/EventBusRabbitMQ.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Domain/Trip/Duber.Domain.Trip/Model/Trip.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Web/Duber.WebSite/Extensions/ServiceCollectionExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Application/Duber.Invoice.API/Extensions/ServiceCollectionExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Application/Duber.Trip.API/Controllers/TripController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Application/Duber.Trip.API/Extensions/ServiceCollectionExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Internals/SqlAsyncPolicyBuilder.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Internals/SqlSyncPolicyBuilder.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Infrastructure/EventBus/Duber.Infrastructure.EventBus/InMemoryEventBusSubscriptionsManager.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Domain/Invoice/Duber.Domain.Invoice/Model/Invoice.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Application/Duber.Invoice.API/Startup.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Application/Duber.Trip.API/Startup.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/DefaultRabbitMQPersisterConnection.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Domain/Invoice/Duber.Domain.Invoice/Repository/InvoiceRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Domain/Invoice/Duber.Domain.Invoice/Persistence/InvoiceMigrationContext.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Web/Duber.WebSite/Infrastructure/Repository/ReportingRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Domain/Driver/Duber.Domain.Driver/Persistence/DriverContextSeed.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/IoC/ServiceCollectionExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 12 more in this group — see findings.md.
X4 · Structured logging · Interpolated log message defeats structured logging · ×28
  • Interpolated log message defeats structured logging src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/InvoiceCreatedIntegrationEventHandler.cs:31 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/InvoicePaidIntegrationEventHandler.cs:31 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/TripCreatedIntegrationEventHandler.cs:34 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Web/Duber.WebSite/Application/IntegrationEvents/Handlers/TripUpdatedIntegrationEventHandler.cs:31 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripCancelledIntegrationEventHandler.cs:27 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripCancelledIntegrationEventHandler.cs:42 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripCancelledIntegrationEventHandler.cs:48 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripFinishedIntegrationEventHandler.cs:27 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripFinishedIntegrationEventHandler.cs:42 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripFinishedIntegrationEventHandler.cs:48 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Invoice.API/Infrastructure/Filters/HttpGlobalExceptionFilter.cs:27 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripCreatedDomainEventHandlerAsync.cs:27 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:34 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:44 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:61 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Trip.API/Application/DomainEventHandlers/TripUpdatedDomainEventHandlerAsync.cs:89 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Application/Duber.Trip.API/Infrastructure/Filters/HttpGlobalExceptionFilter.cs:26 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Domain/Driver/Duber.Domain.Driver/Persistence/DriverContextSeed.cs:75 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Domain/User/Duber.Domain.User/Persistence/UserContextSeed.cs:60 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.RabbitMQ/DefaultRabbitMQPersisterConnection.cs:83 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:97 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.ServiceBus/EventBusServiceBus.cs:132 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Infrastructure/Duber.Infrastructure.WebHost/WebHostExtensions.cs:21 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Infrastructure/Duber.Infrastructure.WebHost/WebHostExtensions.cs:26 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Infrastructure/Duber.Infrastructure.WebHost/WebHostExtensions.cs:30 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • + 3 more in this group — see findings.md.
D41 · Kernel & Syscall Confinement · No seccomp profile · ×15
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
  • No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
DM2 · Strongly-typed ids · Primitive id on a domain type · ×13
  • Primitive id on a domain type: InvoiceCreatedDomainEvent.InvoiceId src/Domain/Invoice/Duber.Domain.Invoice/Events/InvoiceCreatedDomainEvent.cs:18 — `InvoiceCreatedDomainEvent.InvoiceId` 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: InvoiceCreatedDomainEvent.TripId src/Domain/Invoice/Duber.Domain.Invoice/Events/InvoiceCreatedDomainEvent.cs:20 — `InvoiceCreatedDomainEvent.TripId` 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: InvoicePaidDomainEvent.InvoiceId src/Domain/Invoice/Duber.Domain.Invoice/Events/InvoicePaidDomainEvent.cs:18 — `InvoicePaidDomainEvent.InvoiceId` 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: InvoicePaidDomainEvent.TripId src/Domain/Invoice/Duber.Domain.Invoice/Events/InvoicePaidDomainEvent.cs:20 — `InvoicePaidDomainEvent.TripId` 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: Invoice.InvoiceId src/Domain/Invoice/Duber.Domain.Invoice/Model/Invoice.cs:30 — `Invoice.InvoiceId` 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: TripCreatedDomainEvent.UserTripId src/Domain/Trip/Duber.Domain.Trip/Events/TripCreatedDomainEvent.cs:9 — `TripCreatedDomainEvent.UserTripId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: TripCreatedDomainEvent.DriverId src/Domain/Trip/Duber.Domain.Trip/Events/TripCreatedDomainEvent.cs:11 — `TripCreatedDomainEvent.DriverId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: TripCreatedDomainEvent.ConnectionId src/Domain/Trip/Duber.Domain.Trip/Events/TripCreatedDomainEvent.cs:23 — `TripCreatedDomainEvent.ConnectionId` 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: TripUpdatedDomainEvent.UserTripId src/Domain/Trip/Duber.Domain.Trip/Events/TripUpdatedDomainEvent.cs:26 — `TripUpdatedDomainEvent.UserTripId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: TripUpdatedDomainEvent.ConnectionId src/Domain/Trip/Duber.Domain.Trip/Events/TripUpdatedDomainEvent.cs:28 — `TripUpdatedDomainEvent.ConnectionId` 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: Trip.ConnectionId src/Domain/Trip/Duber.Domain.Trip/Model/Trip.cs:30 — `Trip.ConnectionId` 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: Trip.UserId src/Domain/Trip/Duber.Domain.Trip/Model/Trip.cs:32 — `Trip.UserId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: Trip.DriverId src/Domain/Trip/Duber.Domain.Trip/Model/Trip.cs:34 — `Trip.DriverId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
IC1 · Incompleteness & stubs · Commented-out code · ×12
  • Commented-out code src/Web/Duber.WebSite/Controllers/HomeController.cs:29 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Web/Duber.WebSite/Controllers/HomeController.cs:30 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Web/Duber.WebSite/Controllers/HomeController.cs:31 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Web/Duber.WebSite/Controllers/HomeController.cs:32 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Web/Duber.WebSite/Controllers/HomeController.cs:33 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Web/Duber.WebSite/Controllers/HomeController.cs:34 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Web/Duber.WebSite/Controllers/HomeController.cs:37 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Web/Duber.WebSite/Controllers/HomeController.cs:38 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Web/Duber.WebSite/Controllers/HomeController.cs:39 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Web/Duber.WebSite/Controllers/HomeController.cs:40 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Web/Duber.WebSite/Controllers/HomeController.cs:41 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Web/Duber.WebSite/Controllers/HomeController.cs:42 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
S1 · Web-Security Posture · No security response headers detected · ×6
  • 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 ExternalSystem/PaymentService/Program.cs:21 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Application/Duber.Invoice.API/Program.cs:21 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Application/Duber.Trip.API/Program.cs:21 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Application/Duber.Trip.Notifications/Program.cs:17 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Web/Duber.WebSite/Program.cs:37 — 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.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×6
  • No app-layer HTTPS enforcement detected — No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • No app-layer HTTPS enforcement detected ExternalSystem/PaymentService/Program.cs:21 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
  • No app-layer HTTPS enforcement detected src/Application/Duber.Invoice.API/Program.cs:21 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
  • No app-layer HTTPS enforcement detected src/Application/Duber.Trip.API/Program.cs:21 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
  • No app-layer HTTPS enforcement detected src/Application/Duber.Trip.Notifications/Program.cs:17 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
  • No app-layer HTTPS enforcement detected src/Web/Duber.WebSite/Program.cs:37 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
D24 · Comment Value · redundant comment · ×2
  • redundant comment ExternalSystem/PaymentService/Startup.cs:18 — "This method gets called by the runtime. Use this method to add services to the container." — delete - restates the signature; the call-site comment is standard boilerplate
  • redundant comment ExternalSystem/PaymentService/Startup.cs:24 — "This method gets called by the runtime. Use this method to configure the HTTP request pipeline." — delete - duplicate of preceding line, no WHY
ED3 · Event naming · Event not named in past tense · ×2
  • Event not named in past tense: TripEventBase src/Application/Duber.Trip.Notifications/Application/IntegrationEvents/Events/TripEventBase.cs:6 — `TripEventBase` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
  • Event not named in past tense: IdempotentIntegrationEvent src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.Idempotency/IdempotentIntegrationEvent.cs:6 — `IdempotentIntegrationEvent` 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.
M4 · Documentation accuracy · README/code drift · ×2
  • README/code drift deploy/redis/readme.md:16 — deploy/redis/readme.md links to `../readme.md`, but `deploy/readme.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift deploy/redis/readme.md:18 — deploy/redis/readme.md names `deploy\az`, but no file or folder `deploy/az` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X10 · Duplicated predicate · Duplicated predicate · ×2
  • Duplicated predicate src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripCancelledIntegrationEventHandler.cs:45 — `Equals(invoice.PaymentMethod, PaymentMethod.CreditCard) && invoice.Total > 0` appears character-identically in 3 files — src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripCancelledIntegrationEventHandler.cs, src/Application/Duber.Invoice.API/Application/IntegrationEvents/Hnadlers/TripFinishedIntegrationEventHandler.cs, src/Application/Duber.Invoice.API/Controllers/InvoiceController.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Internals/SqlAsyncPolicyBuilder.cs:107 — `timeoutPerRetryPolicy.Any() && !retryPolicies.Any()` appears character-identically in 2 files — src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Internals/SqlAsyncPolicyBuilder.cs, src/Infrastructure/Duber.Infrastructure.Resilience.Sql/Internals/SqlSyncPolicyBuilder.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.
D17 · Explicit Debt · ObsoleteWithoutCallers · ×1
  • ObsoleteWithoutCallers src/Domain/Invoice/Duber.Domain.Invoice/Persistence/InvoiceMigrationContext.cs:29 — [Obsolete] UserContextDesignFactory
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 namespace · ×1
  • Typo in namespace: 'Hnadlers' instead of 'Handlers'. This creates a distinct namespace path from the standard 'Handlers' used elsewhere (e.g., Duber.WebSite.Application.IntegrationEvents.Handlers). — Rename namespace 'Duber.Invoice.API.Application.IntegrationEvents.Hnadlers' to 'Duber.Invoice.API.Application.IntegrationEvents.Handlers' to match the standard spelling and other modules. (symbols: Duber.Invoice.API.Application.IntegrationEvents.Hnadlers.TripFinishedIntegrationEventHandler.Handle, Duber.Invoice.API.Application.IntegrationEvents.Hnadlers.TripCancelledIntegrationEventHandler.Handle)
D21 · Naming Consistency · Typo in method name · ×1
  • Typo in method name: 'GetAggreagates' is misspelled (missing 'g'). While 'QuerySingleAsync' is correctly spelled, the inconsistency here is internal to the first symbol's name itself, but more importantly, it stands out against the correct spelling used in other symbols like 'GetEventsAsync'. — Rename 'GetAggreagates' to 'GetAggregates'. (symbols: Duber.Trip.API.Controllers.EventStoreController.GetAggreagates, Duber.Domain.Invoice.Persistence.InvoiceContext.QuerySingleAsync)
D21 · Naming Consistency · Inconsistent terminology for phone number · ×1
  • Inconsistent terminology for phone number: '_numberPhone' vs standard '_name' pattern. While not a direct synonym conflict, 'numberPhone' is non-standard English phrasing compared to 'PhoneNumber' or 'Phone'. However, since it's a private field and distinct from other phone-related concepts (none listed), this is a minor style issue. A more significant inconsistency is found in the parameter naming for similar entities. — Consider renaming '_numberPhone' to '_phoneNumber' for consistency with standard C# naming conventions, though this is a style preference rather than a strict inconsistency. (symbols: Duber.Domain.User.Model.User._numberPhone, Duber.Domain.Driver.Model.Driver._name)
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 37 of 37 significant files have no living knowledge — the codebase as a whole is dormant, not 37 separate risks. Counted over 37 of the 186 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D40 · Network Egress Confinement · No network policy · ×1
  • No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
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.
M3 · Folder & project structure · No tests/ separation · ×1
  • No tests/ separation — Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 10/15 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 15, 5 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 0/65 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 · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/20 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Minor — 21 finding(s)
D19 · Documentation Quality · XML-doc coverage · ×20
  • XML-doc coverage: Duber.WebSite REDACTED — Duber.WebSite: 0 % XML-doc coverage (0/179).
  • XML-doc coverage: Duber.Domain.Invoice REDACTED — Duber.Domain.Invoice: 1 % XML-doc coverage (1/70).
  • XML-doc coverage: Duber.Domain.Trip src/Domain/Trip/Duber.Domain.Trip/Duber.Domain.Trip.csproj — Duber.Domain.Trip: 0 % XML-doc coverage (0/86).
  • XML-doc coverage: Duber.Invoice.API REDACTED — Duber.Invoice.API: 4 % XML-doc coverage (4/113).
  • XML-doc coverage: Duber.Trip.API REDACTED — Duber.Trip.API: 6 % XML-doc coverage (9/151).
  • XML-doc coverage: Duber.Domain.Driver src/Domain/Driver/Duber.Domain.Driver/Duber.Domain.Driver.csproj — Duber.Domain.Driver: 0 % XML-doc coverage (0/64).
  • XML-doc coverage: Duber.Domain.ACL REDACTED — Duber.Domain.ACL: 0 % XML-doc coverage (0/9).
  • XML-doc coverage: Duber.Infrastructure.EventBus src/Infrastructure/EventBus/Duber.Infrastructure.EventBus/Duber.Infrastructure.EventBus.csproj — Duber.Infrastructure.EventBus: 0 % XML-doc coverage (0/30).
  • XML-doc coverage: Duber.Domain.User src/Domain/User/Duber.Domain.User/Duber.Domain.User.csproj — Duber.Domain.User: 0 % XML-doc coverage (0/33).
  • XML-doc coverage: Duber.Infrastructure.EventBus.RabbitMQ REDACTED — Duber.Infrastructure.EventBus.RabbitMQ: 0 % XML-doc coverage (0/18).
  • XML-doc coverage: Duber.Infrastructure.EventBus.ServiceBus REDACTED — Duber.Infrastructure.EventBus.ServiceBus: 0 % XML-doc coverage (0/17).
  • XML-doc coverage: Duber.Domain.SharedKernel src/Domain/Duber.Domain.SharedKernel/Duber.Domain.SharedKernel.csproj — Duber.Domain.SharedKernel: 0 % XML-doc coverage (0/26).
  • XML-doc coverage: Duber.Infrastructure src/Infrastructure/Duber.Infrastructure/Duber.Infrastructure.csproj — Duber.Infrastructure: 0 % XML-doc coverage (0/32).
  • XML-doc coverage: Duber.Infrastructure.WebHost REDACTED — Duber.Infrastructure.WebHost: 0 % XML-doc coverage (0/2).
  • XML-doc coverage: PaymentService ExternalSystem/PaymentService/PaymentService.csproj — PaymentService: 0 % XML-doc coverage (0/10).
  • XML-doc coverage: Duber.Infrastructure.Resilience.Abstractions src/Infrastructure/Duber.Infrastructure.Resilience.Abstractions/Duber.Infrastructure.Resilience.Abstractions.csproj — Duber.Infrastructure.Resilience.Abstractions: 19 % XML-doc coverage (3/16).
  • XML-doc coverage: Duber.Infrastructure.Resilience.Http src/Infrastructure/Duber.Infrastructure.Resilience.Http/Duber.Infrastructure.Resilience.Http.csproj — Duber.Infrastructure.Resilience.Http: 0 % XML-doc coverage (0/4).
  • XML-doc coverage: Duber.Infrastructure.Resilience.Sql REDACTED — Duber.Infrastructure.Resilience.Sql: 23 % XML-doc coverage (12/53).
  • XML-doc coverage: Duber.Trip.Notifications REDACTED — Duber.Trip.Notifications: 0 % XML-doc coverage (0/44).
  • XML-doc coverage: Duber.Infrastructure.EventBus.Idempotency src/Infrastructure/EventBus/Duber.Infrastructure.EventBus.Idempotency/Duber.Infrastructure.EventBus.Idempotency.csproj — Duber.Infrastructure.EventBus.Idempotency: 7 % XML-doc coverage (1/15).
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: Duber.Domain.SharedKernel src/Domain/Duber.Domain.SharedKernel/Duber.Domain.SharedKernel.csproj:1 — Duber.Domain.SharedKernel: abstractness 0.00, instability 0.20, distance 0.80 — 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-6ab633f47508409e81bc1dcfe85324d2/history.json --exit-code 0 --source .3artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6ab633f47508409e81bc1dcfe85324d2/tree.json --exit-code 0 --source .3artifacts/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 .21artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list microservices-netcore-docker-servicefabric.sln package --vulnerable --include-transitive --format json30artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .360artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

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

Financial (card / IBAN) — 7 field(s)
  • InvoicePaidIntegrationEvent.CardNumber src/Application/Duber.Invoice.API/Application/IntegrationEvents/Events/InvoicePaidIntegrationEvent.cs:24
  • PaymentInfo.CardNumber src/Application/Duber.Invoice.API/Application/Model/Invoice.cs:53
  • PaymentInfo._cardNumber src/Domain/Duber.Domain.SharedKernel/Model/PaymentInfo.cs:15
  • PaymentInfo.CardNumber src/Domain/Duber.Domain.SharedKernel/Model/PaymentInfo.cs:35
  • InvoicePaidDomainEvent.CardNumber src/Domain/Invoice/Duber.Domain.Invoice/Events/InvoicePaidDomainEvent.cs:24
  • InvoicePaidIntegrationEvent.CardNumber src/Web/Duber.WebSite/Application/IntegrationEvents/Events/InvoicePaidIntegrationEvent.cs:23
  • Trip.CardNumber src/Web/Duber.WebSite/Models/Trip.cs:69
Email — 6 field(s)
  • Driver._email src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:16
  • Driver.Email src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:29
  • User._email src/Domain/User/Duber.Domain.User/Model/User.cs:17
  • User.Email src/Domain/User/Duber.Domain.User/Model/User.cs:23
  • DriverModel.Email src/Web/Duber.WebSite/Models/DriverModel.cs:11
  • UserModel.Email src/Web/Duber.WebSite/Models/UserModel.cs:11
Phone — 6 field(s)
  • Driver._phoneNumber src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:17
  • Driver.PhoneNumber src/Domain/Driver/Duber.Domain.Driver/Model/Driver.cs:31
  • User._numberPhone src/Domain/User/Duber.Domain.User/Model/User.cs:16
  • User.NumberPhone src/Domain/User/Duber.Domain.User/Model/User.cs:25
  • DriverModel.NumberPhone src/Web/Duber.WebSite/Models/DriverModel.cs:9
  • UserModel.NumberPhone src/Web/Duber.WebSite/Models/UserModel.cs:9

Issues: 148 · Warnings: 439 · Recommendations: 191 · Info: 21 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 19:35 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