Public report of puomhicipo/PlainBridge, published 22 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, 22 October 2026, 04:23 UTC · Survey ID cd_ed44939b212441ce811c88b92bb1e040

puomhicipo/PlainBridge

Measured 22 October 2026, 03:59 UTC, at code version b07ed08

First survey, so nothing to compare with yet Supply-chain provenance & signing: not measured

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 46out of 100 Adequate
CriticalWeakAdequateStrongExemplary

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.

Performance 100 Exemplary Architecture 83 Exemplary Event-Driven 74 Adequate Code Health 69 Strong Domain Modelling 59 Adequate Maturity 50 Adequate Production Readiness 50 Adequate Security and Compliance 49 Adequate Accessibility 39 Adequate

A small codebase: 9,568 lines of product code in 18 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Accessibility, 39

Findings by how serious they are

127 critical 193 serious 77 minor

9 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
22 October 2026, 03:59 UTC

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

The 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 ▸

101of 106 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.
377of 397 findings point to an exact file and line, so you can open each one in the code. The other 20 concern the repository as a whole, such as missing documentation.
106dimensions across 9 lenses, read from 9,568 lines of product code in 18 projects.
Chapters

Executive summary

puomhicipo/PlainBridge scores 46 out of 100 and is rated Adequate, while eight of its nine lenses score higher still: Performance at 100 and Architecture at 83, both rated Exemplary, Event-Driven at 74, Domain Modelling at 59, Production Readiness and Maturity at 50 and Security and Compliance at 49, all rated Adequate, and Code Health at 69, rated Strong. Watchdog judged it as a template, sample or demo, meant to be read or copied, so the dimensions about building, releasing and running a product don't apply, and its lenses are rated against a lower bar. The score itself is worked out as for any repository.

The score is lower than those eight because the weakest lens counts most, and here that is Accessibility, which scores 39 and is rated Adequate. Its Text alternatives dimension scores 1 out of 10, and until that reaches 4, Accessibility can't be rated higher than Adequate. The first actions are to add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video and to enforce accessibility in the toolchain: add @angular-eslint/eslint-plugin-template (a11y rules), then assert with cypress-axe in tests, then gate axe/pa11y/Lighthouse in CI, and if Accessibility rose to 70, the score would rise from 46 to about 52.

127 findings are critical: 34 in Forms & labels, 31 in Dependency Vulnerabilities, 14 in Domain ↔ infrastructure boundary, eight in Outbox / dual-write, seven in Explicit Debt, seven in Text alternatives, six in Static Analysis (SAST), five in Change Coupling, five in Page structure, three in Secrets (history), two in Web-Security Posture, one in Coupling, one in Dependency direction, one in IaC & Container Security, one in Project dependency cycles and one in Secret Scanning.

Watchdog couldn't measure 6 dimensions in this code, among them Code Coverage, Test Reliability and Dependency Hygiene, so they are left out of the score. The product code is 9,568 lines, which would take an estimated 0.2 person-years, around €32,000, to rebuild.

Code Health 69 Strong Architecture 83 ★ Exemplary Maturity 50 Adequate, capped by Documentation accuracy Production Readiness 50 Adequate, capped by Release Hygiene and Outbound HTTP resilience Security and Compliance 49 Adequate, capped by Static Analysis (SAST), Dependency Vulnerabilities and Web-Security Posture Domain Modelling 59 Adequate, capped by Strongly-typed ids and Domain ↔ infrastructure boundary Event-Driven 74 Adequate, capped by Outbox / dual-write Accessibility 39 Adequate, capped by Text alternatives Performance 100 ★ Exemplary

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.
Accessibility 39 · counts for 45%Security and Compliance 49 · counts for 25%Production Readiness 50 · counts for 14%Maturity 50 · counts for 8%Domain Modelling 59 · counts for 4%Code Health 69 · counts for 2%Event-Driven 74 · counts for 1%Architecture 83 · counts for 1%Performance 100 · counts for 0%

If Accessibility rose from 39 to 70, the lowest score rated Strong, the score would rise from 46 to about 52.

Code composition: what the lines of code are
Business logic 23%Supporting code 40%Tests 37%
Rebuild cost: about €32,000 · Estimate
Cost to rebuild€11,000 to €54,000, for 176 to 565 hours of work, about 0.2 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 46. 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: 9,568 lines of product code
Comment linesThe estimate prices 9,190 lines. Comment lines count towards the size of 9,568 lines but aren't priced as work.

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
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Raises the score by about 5 points · Medium effort · Text alternatives
2
Enforce accessibility in the toolchain: add @angular-eslint/eslint-plugin-template (a11y rules), then assert with cypress-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Raises the score by about 3 points · Medium effort · A11y enforcement
3
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 1 point · Low effort · Secret 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 €32,000 to build again, about 0.2 person-years of work. Its weakest lens is Accessibility, at 39 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
One cause behind 7 Domain Modelling findings · Common cause
7 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (3 findings) · Strongly-typed ids (4 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. Of all the actions in this report, it raises the score most for the work it takes: about 5 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 Api.ApiEndPoint Api.ApiEndPoint ctx:Api Api Application · Domain · Infrastructure Api.ApiEndPoint->ctx:Api ctx:AppHost.ServiceDefaults AppHost.ServiceDefaults ServiceDefaults Api.ApiEndPoint->ctx:AppHost.ServiceDefaults AppHost.AppHost AppHost.AppHost Client.ApiEndPoint Client.ApiEndPoint Client.ApiEndPoint->ctx:AppHost.ServiceDefaults ctx:Client Client Application Client.ApiEndPoint->ctx:Client IdentityServer.EndPoint IdentityServer.EndPoint IdentityServer.EndPoint->ctx:AppHost.ServiceDefaults ctx:Shared Shared Application · Domain IdentityServer.EndPoint->ctx:Shared Server.ApiEndPoint Server.ApiEndPoint Server.ApiEndPoint->ctx:AppHost.ServiceDefaults ctx:Server Server Application Server.ApiEndPoint->ctx:Server ctx:Api->ctx:Shared ctx:Client->ctx:Shared ctx:Server->ctx:Shared

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.

135 modules, with 149 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 95 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 PlainBridge.Api.Infrastructure.DTOs2 PlainBridge.Server.Application.DTOs3 PlainBridge.Shared.Application.Enums4 PlainBridge.Shared.Application.Mediator5 PlainBridge.Shared.Domain.Base6 PlainBridge.Shared.Domain.Base.ValueObjects7 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.models.base_models8 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.auth_service9 PlainBridge.Api.Application.UseCases10 PlainBridge.Api.Domain.ServerAggregate11 PlainBridge.Shared.Application.DTOs12 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.models.host-application_models13 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.models.server-application_models14 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.api-response_service15 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.user_service16 PlainBridge.Api.Application.DTOs17 PlainBridge.Api.Domain.UserAggregate18 PlainBridge.Api.Infrastructure.ExternalServices.Identity19 PlainBridge.Client.Application.Management.Cache20 PlainBridge.Server.Application.Management.Cache21 PlainBridge.Server.Application.Services.HttpRequestProxy22 PlainBridge.Server.Application.Services.PlainBridgeApiClient23 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.features.users.components.user-registration.user-registration_component24 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.host-application_service25 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.server-application_service26 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.testing27 PlainBridge.Api.Application.Services.Session28 PlainBridge.Api.Domain.HostAggregate29 PlainBridge.Client.Application.Services.SharePortSocket30 PlainBridge.Server.Application.Services.HostApplication31 PlainBridge.Server.Application.Services.WebSocket32 PlainBridge.Api.Infrastructure.Persistence.Data.Context33 PlainBridge.Client.Application.Services.ClientBus34 PlainBridge.Api.Application.Features.User.Commands35 PlainBridge.Api.Application.Features.User.Queries36 PlainBridge.Api.Application.UseCases.HostApplication.Commands37 PlainBridge.Api.Application.UseCases.HostApplication.Queries38 PlainBridge.Api.Application.UseCases.ServerApplication.Commands39 PlainBridge.Api.Application.UseCases.ServerApplication.Queries40 PlainBridge.Client.ApiEndPoint
1 PlainBridge.Api.Infrastructure.DTOs
2 PlainBridge.Server.Application.DTOs
3 PlainBridge.Shared.Application.Enums
4 PlainBridge.Shared.Application.Mediator
5 PlainBridge.Shared.Domain.Base
6 PlainBridge.Shared.Domain.Base.ValueObjects
7 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.models.base_models
8 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.auth_service
9 PlainBridge.Api.Application.UseCases1
10 PlainBridge.Api.Domain.ServerAggregate211
11 PlainBridge.Shared.Application.DTOs3
12 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.models.host-application_models1
13 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.models.server-application_models1
14 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.api-response_service1
15 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.user_service1
16 PlainBridge.Api.Application.DTOs1
17 PlainBridge.Api.Domain.UserAggregate2111
18 PlainBridge.Api.Infrastructure.ExternalServices.Identity52
19 PlainBridge.Client.Application.Management.Cache4
20 PlainBridge.Server.Application.Management.Cache4
21 PlainBridge.Server.Application.Services.HttpRequestProxy1
22 PlainBridge.Server.Application.Services.PlainBridgeApiClient14
23 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.features.users.components.user-registration.user-registration_component111
24 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.host-application_service11
25 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.server-application_service11
26 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.testing11
27 PlainBridge.Api.Application.Services.Session1122
28 PlainBridge.Api.Domain.HostAggregate211
29 PlainBridge.Client.Application.Services.SharePortSocket21
30 PlainBridge.Server.Application.Services.HostApplication1211
31 PlainBridge.Server.Application.Services.WebSocket121
32 PlainBridge.Api.Infrastructure.Persistence.Data.Context111
33 PlainBridge.Client.Application.Services.ClientBus11
34 PlainBridge.Api.Application.Features.User.Commands8434
35 PlainBridge.Api.Application.Features.User.Queries422
36 PlainBridge.Api.Application.UseCases.HostApplication.Commands824
37 PlainBridge.Api.Application.UseCases.HostApplication.Queries422
38 PlainBridge.Api.Application.UseCases.ServerApplication.Commands2824
39 PlainBridge.Api.Application.UseCases.ServerApplication.Queries422
40 PlainBridge.Client.ApiEndPoint1
Uses a module listed above itPart of a loopThe module itself
1 PlainBridge.Api.Infrastructure.DTOs2 PlainBridge.Server.Application.DTOs3 PlainBridge.Shared.Application.Enums4 PlainBridge.Shared.Application.Mediator5 PlainBridge.Shared.Domain.Base6 PlainBridge.Shared.Domain.Base.ValueObjects7 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.models.base_models8 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.auth_service9 PlainBridge.Api.Application.UseCases10 PlainBridge.Api.Domain.ServerAggregate11 PlainBridge.Shared.Application.DTOs12 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.models.host-application_models13 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.models.server-application_models14 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.api-response_service15 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.user_service16 PlainBridge.Api.Application.DTOs17 PlainBridge.Api.Domain.UserAggregate18 PlainBridge.Api.Infrastructure.ExternalServices.Identity19 PlainBridge.Client.Application.Management.Cache20 PlainBridge.Server.Application.Management.Cache21 PlainBridge.Server.Application.Services.HttpRequestProxy22 PlainBridge.Server.Application.Services.PlainBridgeApiClient23 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.features.users.components.user-registration.user-registration_component24 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.host-application_service25 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.server-application_service26 src.PlainBridge_Web.src.PlainBridge_Web_UI.src.testing27 PlainBridge.Api.Application.Services.Session28 PlainBridge.Api.Domain.HostAggregate29 PlainBridge.Client.Application.Services.SharePortSocket30 PlainBridge.Server.Application.Services.HostApplication31 PlainBridge.Server.Application.Services.WebSocket32 PlainBridge.Api.Infrastructure.Persistence.Data.Context33 PlainBridge.Client.Application.Services.ClientBus34 PlainBridge.Api.Application.Features.User.Commands35 PlainBridge.Api.Application.Features.User.Queries36 PlainBridge.Api.Application.UseCases.HostApplication.Commands37 PlainBridge.Api.Application.UseCases.HostApplication.Queries38 PlainBridge.Api.Application.UseCases.ServerApplication.Commands39 PlainBridge.Api.Application.UseCases.ServerApplication.Queries40 PlainBridge.Client.ApiEndPointPlainBridge.Api.Infrastructure.DTOs1PlainBridge.Server.Application.DTOs2PlainBridge.Shared.Application.Enums3PlainBridge.Shared.Application.Mediator4PlainBridge.Shared.Domain.Base5PlainBridge.Shared.Domain.Base.ValueObjects6src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.models.base_models7src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.auth_service8PlainBridge.Api.Application.UseCases9PlainBridge.Api.Domain.ServerAggregate10PlainBridge.Shared.Application.DTOs11src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.models.host-application_models12src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.models.server-application_models13src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.api-response_service14src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.user_service15PlainBridge.Api.Application.DTOs16PlainBridge.Api.Domain.UserAggregate17PlainBridge.Api.Infrastructure.ExternalServices.Identity18PlainBridge.Client.Application.Management.Cache19PlainBridge.Server.Application.Management.Cache20PlainBridge.Server.Application.Services.HttpRequestProxy21PlainBridge.Server.Application.Services.PlainBridgeApiClient22src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.features.users.components.user-registration.user-registration_component23src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.host-application_service24src.PlainBridge_Web.src.PlainBridge_Web_UI.src.app.services.server-application_service25src.PlainBridge_Web.src.PlainBridge_Web_UI.src.testing26PlainBridge.Api.Application.Services.Session27PlainBridge.Api.Domain.HostAggregate28PlainBridge.Client.Application.Services.SharePortSocket29PlainBridge.Server.Application.Services.HostApplication30PlainBridge.Server.Application.Services.WebSocket31PlainBridge.Api.Infrastructure.Persistence.Data.Context32PlainBridge.Client.Application.Services.ClientBus33PlainBridge.Api.Application.Features.User.Commands34PlainBridge.Api.Application.Features.User.Queries35PlainBridge.Api.Application.UseCases.HostApplication.Commands36PlainBridge.Api.Application.UseCases.HostApplication.Queries37PlainBridge.Api.Application.UseCases.ServerApplication.Commands38PlainBridge.Api.Application.UseCases.ServerApplication.Queries39PlainBridge.Client.ApiEndPoint40121131111121115244114111111111112221121121112111111843442282442228244221+95 more modules (most-connected shown)

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

The Good
D1 · .NET / C# Cyclomatic Complexity 9.7 D2 · .NET / C# Cognitive Complexity 9.1 D3 · .NET / C# God Classes 10.0 D4 · .NET / C# Code Duplication 8.4 D17 · .NET / C# Explicit Debt 8.1 D18 · .NET / C# Solution Shape 10.0 GD1 · Repo Unfinished & placeholder code 9.9 IC1 · Repo Incompleteness & stubs 7.8 R1 · React / TS Type Safety 9.8 R10 · React / TS Code Duplication 8.3 R2 · React / TS Cyclomatic Complexity 10.0 R3 · React / TS Large Files 10.0 R7 · React / TS Dead Code 7.9 X1 · Repo Async correctness 7.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 X2 · Repo Cancellation propagation 9.2 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 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0 X4 · Repo Structured logging 7.0 X5 · Repo Nullable reference types 7.0
The Bad
X3 · Repo Exception handling 4.9
The Ugly
X20 · Repo Mistyped argument guard 3.5

At a glance — Architecture · 83% · Exemplary ·

The Good
D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 10.0 D23 · .NET / C# Boundary Type-Coupling 9.2 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 9.5 D35 · .NET / C# Change Coupling 9.3 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 6.9 AX2 · Repo Stateful singletons 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 AX9 · Repo CQS / query purity 10.0 R9 · React / TS Circular Imports 10.0
The Bad
AX4 · Repo Dependency direction 6.2

At a glance — Maturity · 50% · Adequate · gated by M4 ·

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

At a glance — Readiness · 50% · Adequate · gated by P6, P7 ·

The Good
D9 · .NET / C# Test Distribution 9.8 D10 · .NET / C# Test Quality 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 9.5 R5 · React / TS Dependency Freshness 8.7 R6 · React / TS Tooling 6.7 R8 · React / TS Dependency Hygiene 9.5
The Bad
D13 · .NET / C# Secret Scanning 5.0 P4 · Repo Deployment & Rollback 5.0 R4 · React / TS Test Coverage 4.7
The Ugly
P6 · Repo Release Hygiene 3.0 P7 · Repo Outbound HTTP resilience 3.0

At a glance — Security · 49% · Adequate · gated by D29, D30, S1 ·

The Good
D28 · .NET / C# Secrets (history) 7.0 D31 · .NET / C# IaC & Container Security 9.4 D43 · .NET / C# Malicious Dependencies 10.0 D44 · .NET / C# Platform End-of-Life 10.0 C2 · Repo Access Controls 10.0 C3 · Repo Audit Trail 7.5 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 X24 · Repo Document value interpolated into markup unescaped 10.0
The Ugly
D29 · .NET / C# Static Analysis (SAST) 3.0 D30 · .NET / C# Dependency Vulnerabilities 0.0 S1 · Repo Web-Security Posture 0.0

At a glance — Domain Modelling · 59% · Adequate · gated by DM2, DM6 ·

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

At a glance — Event-Driven · 74% · Adequate · gated by ED4 ·

The Good
ED1 · Repo Handler temporal coupling 10.0 ED2 · Repo Event/command shape 10.0
The Bad
ED4 · Repo Outbox / dual-write 3.9

At a glance — Accessibility · 39% · Adequate · gated by AC1 ·

The Good
AC5 · Repo ARIA correctness 10.0
The Bad
AC2 · Repo Forms & labels 4.7 AC3 · Repo Page structure 4.8 AC6 · Repo Visual & motion safety 5.4 AC7 · Repo A11y enforcement 4.0
The Ugly
AC1 · Repo Text alternatives 1.0

At a glance — Performance · 100% · Exemplary ·

The Good
PF3 · Repo Async & latency hygiene 10.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
A03:2025 — Software Supply Chain Failures46High / Critical
A05:2025 — Injection29High / Critical
A07:2025 — Authentication Failures5High / Critical
A02:2025 — Security Misconfiguration4High / Critical

Roadmap

First, ensure all media elements have appropriate text alternatives and every form control or button has a programmatic label to support screen readers. Next, establish a robust accessibility enforcement strategy by integrating linting rules, automated testing, and CI gates to catch issues early. Finally, improve page structure by defining proper landmarks and language attributes, while ensuring visual safety through visible focus styles, reduced motion support, and sufficient color contrast.

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

Do thisHelpsEffortDimension
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.+5.1 ptsMediumText alternatives
Enforce accessibility in the toolchain: add @angular-eslint/eslint-plugin-template (a11y rules), then assert with cypress-axe in tests, then gate axe/pa11y/Lighthouse in CI.+3.2 ptsMediumA11y enforcement
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.+1.3 ptsLowSecret Scanning
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.+2.4 ptsMediumForms & labels
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.+2.3 ptsMediumPage structure
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.+2.0 ptsMediumVisual & motion safety
Stop accepting every TLS certificate: remove the always-true validation callback so the platform verifies the chain, hostname and expiry. If one self-signed certificate must be trusted, pin it by public key or thumbprint on the single handler that needs it and reject all others — never process-wide.+1.5 ptsMediumWeb-Security Posture
Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; README.md runs `dotnet run --project src/PlainBridge.AppHost/PlainBridge.AppHost.csproj`, but `src/PlainBridge.AppHost/PlainBridge.AppHost.csproj` does not exist; README.md runs `docker compose --env-file infra/.env -f infra/docker-compose.yaml up -d cache messaging elasticsearch plain-bridge-dashboard`, but `infra/docker-compose.yaml` does not exist; docs/project-analys.md names `is-signing-key-0DC4B64548F26BFFF432AB5D01514AE4.json`, but no file or folder `is-signing-key-0DC4B64548F26BFFF432AB5D01514AE4.json` exists; docs/project-analys.md names `docker-compose.yaml`, but no file or folder `docker-compose.yaml` exists.+1.2 ptsMediumDocumentation accuracy

File quality

Per-file score 0–10 — a quality signature. Of 67 files carrying findings, judged against the Template bar: 4% slop · 8% mixed · 88% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopSecret Scanning: Leaked secret: REDACTED
REDACTED2.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.8MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED5.1MixedSecrets (history): High secret: REDACTED
REDACTED.cs5.8MixedExplicit Debt: WriteOnlyPrivateField
src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs6.3Near-cleanCode Duplication: Duplicated block (37–39 lines × 2)
REDACTED6.3Near-cleanStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9Near-cleanStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9Near-cleanStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9Near-cleanStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9Near-cleanStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9Near-cleanStatic Analysis (SAST): Medium: REDACTED
src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs7.0Near-cleanCode Duplication: Duplicated block (16–18 lines × 3)
src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ApiExternalBus/ApiExternalBusService.cs7.0Near-cleanCode Duplication: Duplicated block (14–15 lines × 2)
src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/Program.cs7.0Near-cleanChange Coupling: Boundary-crossing change coupling: Program.cs ↔ Program.cs
src/PlainBridge.AppHost/PlainBridge.AppHost.AppHost/AppHost.cs7.0Near-cleanChange Coupling: Boundary-crossing change coupling: AppHost.cs ↔ DependencyResolver.cs
REDACTED.cs7.1Near-cleanCode Duplication: Duplicated block (20 lines × 2)

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

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

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

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

Could not be resolved — 9

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. 101 of 106 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.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 106 dimensions across the health lenses
D1D2D3D4D5D6D9D10D13D14D15D17D18D19D21D23D24D26D27D28D29D30D31D34D35D43D44AC1AC2AC3AC5AC6AC7AX1AX10AX2AX3AX4AX5AX6AX8AX9C2C3DM1DM10DM11DM12DM2DM4DM5DM6DM8DM9ED1ED2ED4ED5GD1IC1M1M2M3M4P1P2P4P6P7PF3R1R10R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 377 of 397 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 01a161c3-4090-7fa2-b342-d1e6c5ff046c.

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.

  • D8 Code Coverage — 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. Coverage NOT MEASURED: the .NET half measured 43.2%; the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — src/PlainBridge.Web/src/PlainBridge.Web.UI/ (karma/cypress) — a gap in the analyzer, not something this repository is missing. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
  • D10 Test Quality — 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 146 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 12 test source file(s) (.ts) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • 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: this repository's production source spans .cs, .ts, and the built-in reliability runner cannot re-run the .ts test suite(s) — so reliability was not measured for the repository as a whole. The .NET suite did build and re-run, and came back with 0 flaky across 1 measured tier(s) (unit: measured (0 flaky)) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
  • 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 168 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 'src/PlainBridge.Web/src/PlainBridge.Web.UI/PlainBridge.Web.UI.esproj' because the file extension '.esproj' is not associated with a language.
  • 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 15 deducted marker(s) and the 0.9/KLoC density on this row were taken over this repository's .NET projects ALONE: .ts (1,781 lines, 19% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • D18 Solution Shape — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `dotnet build` reported 10 error(s), and the diagnostics it printed were: MSB3073: The command "npm install" exited with code 1.. None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
  • D18 Solution Shape — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A scan loads every live solution in the repository into one workspace. Every score, lens, and finding here reflects the projects of `PlainBridge.slnx`; 1 further solution(s) found in this tree (`src/PlainBridge.Web/PlainBridge.Web.slnx`) could not be added to it — their project list could not be read, or none of their projects opened — so their code is not represented in the headline. (This is a count of the solutions discovery found and could not show to be covered by the analyzed ones — not a claim about how many solution files the repository contains.) If one of them is an archived or vendored tree, declaring it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — excludes it from discovery the same way generated code is. You can widen what we reach: if one of these solutions is live code, check that it opens on its own (`dotnet build <solution>`); if it is archived or vendored, declare it so.
  • 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.
  • D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 1576 sampled here came from .cs files. This repository's .ts source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
  • 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; `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/keys/is-signing-key-E7167CC2F6C5D9ED03627676E3513DCA.json` 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.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommandHandler.cs`, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/DeleteHostApplicationCommandHandler.cs`, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateHostApplicationCommandHandler.cs`, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateStateHostApplicationCommandHandler.cs`, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Queries/GetAllHostApplicationsQueryHandler.cs`, … (+44 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
  • 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 AspireAppHost (src/PlainBridge.AppHost/PlainBridge.AppHost.AppHost/PlainBridge.AppHost.AppHost.csproj). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.
  • P8 Schema migrations — 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. Every other migration runner — DbUp, FluentMigrator, Evolve, Flyway, Liquibase, RoundhousE, a hand-rolled versioned-SQL runner — is invisible to the detector, so an absence here is our blind spot rather than a missing migration strategy in the repository. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool other than EF Core migrations, naming it lets us teach the detector to read it.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — 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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • 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.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • 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.
  • 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.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • 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 Complexity9.7 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was HttpHelper.CreateAndSendRequestAsync at 18.

HttpHelper.CreateAndSendRequestAsync (cyclomatic 18)src/PlainBridge.Client/src/PlainBridge.Client.Application/Helpers/Http/HttpHelper.cs:12

What to do

  1. Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with HttpHelper.CreateAndSendRequestAsync (cyclomatic 18). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity9.1 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

4 method(s) exceeded the cognitive complexity threshold of 15; the worst was Index.OnPost at 27.

Index.OnPost (cognitive 27)src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Login/Index.cshtml.cs:60
HttpHelper.CreateAndSendRequestAsync (cognitive 18)src/PlainBridge.Client/src/PlainBridge.Client.Application/Helpers/Http/HttpHelper.cs:12
Index.OnPost (cognitive 18)src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Create/Index.cshtml.cs:37
ApiResponseService.handleResponse (cognitive 17)src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/api-response.service.ts:18

What to do

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

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

D3 · God 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 Duplication8.4 / 10Strong✓ Tool-verified

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

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

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

31 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. Measured on part of this repository only: .ts (19% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Duplicated block (6 lines × 2) · ×3src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateStateHostApplicationCommandHandler.cs:25
Duplicated block (9 lines × 2) · ×3src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommand.cs:23
Duplicated block (19–20 lines × 2) · ×2src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/ExternalServices/Identity/IdentityService.cs:45
Duplicated block (10 lines × 3) · ×2src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs:20
Duplicated block (7 lines × 2) · ×2src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommand.cs:11

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

What to do

  1. Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with UpdateStateHostApplicationCommandHandler.cs, CreateUserCommandHandler.cs, ServerApplicationConsumerService.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with CreateHostApplicationCommand.cs, IdentityService.cs, ViewModel.cs. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 2 Duplicated block (19–20 lines × 2) finding(s) in Code Duplication — start with IdentityService.cs, Mediator.cs. — One of this dimension's main actionable groups (2 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling10.0 / 10Adequategated by 1 critical finding✓ 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

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

Layer violation: Application → Infrastructuresrc/PlainBridge.Api/src/PlainBridge.Api.Application/PlainBridge.Api.Application.csproj:29

What to do

  1. Resolve the 1 Layer violation finding(s) in Coupling — start with PlainBridge.Api.Application.csproj. — One of this dimension's main actionable groups (1 issue-level).
  2. Enforce Coupling in CI to reach Verified (currently Documented). — 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 23 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D9 · Test Distribution9.8 / 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 9.8 / 10 · rule-coverage 100% · ceiling Documented

198 test methods: 195 unit, 0 integration, 0 BDD, 3 e2e. The JavaScript/TypeScript suite contributes 52 `it`/`test` case(s) across 12 test file(s) declaring at least one beside 146 .NET test method(s); its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 skipped, 0 zero-assertion, 4 mock references across 146 tests. Measured on the C# suite only — at least 12 test source file(s) (.ts) went unread, so its test quality is unmeasured and is not in these counts.

Mock-dominated test: InitializeConsumerAsync_ShouldDeclareQueueAndConsume · ×2src/PlainBridge.Client/tests/PlainBridge.Client.Tests/UnitTests/Services/ClientBusServiceTests.cs:28
Mock framework: Moq · ×4

✓ On the Gold path — maintain.

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

D13 · Secret Scanning5.0 / 10Adequate✓ 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 5.0 / 10 · rule-coverage 100% · ceiling Prevented

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Enforce Secret Scanning in CI to reach Verified (currently Documented). — 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 306 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 52 direct `PackageReference`(s), and 198 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 Debt8.1 / 10Adequategated by 7 critical findings✓ 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 8.1 / 10 · rule-coverage 100% · ceiling Prevented

15 deducted debt markers + unmeasured dead symbols across 7741 LoC in the .NET projects (0.9/KLoC) → score 8.1. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .ts (19% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

WriteOnlyPrivateField · ×4src/PlainBridge.Api/tests/PlainBridge.Api.Tests/UnitTests/Application/Services/SessionServiceTests.cs:23
EmptyCatchBlock · ×3src/PlainBridge.Client/src/PlainBridge.Client.Application/Services/UsePortSocket/UsePortSocketService.cs:132
CommentedOutCode · ×3src/PlainBridge.AppHost/PlainBridge.AppHost.ServiceDefaults/Extensions.cs:93
Whole file has no live code — 3 debt markers inside itsrc/PlainBridge.Client/tests/PlainBridge.Client.Tests/UnitTests/Management/WebSocketManagementTests.cs:1
TodoCommentREDACTED.cs:190

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

What to do

  1. Resolve the 4 WriteOnlyPrivateField finding(s) in Explicit Debt — start with SessionServiceTests.cs, TokenServiceTests.cs, ClientBusServiceTests.cs. — One of this dimension's main actionable groups (4 issue-level).
  2. Resolve the 3 EmptyCatchBlock finding(s) in Explicit Debt — start with UsePortSocketService.cs, HttpRequestProxyService.cs, WebSocketService.cs. — One of this dimension's main actionable groups (3 issue-level).
  3. Resolve the 3 CommentedOutCode finding(s) in Explicit Debt — start with Extensions.cs, ApplicationDbContext.cs, Worker.cs. — One of this dimension's main actionable groups (3 warning-level).
  4. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

18 projects, 272 source files, 11251 hand-written lines of code (7741 production / 3510 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), 24 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.)

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation QualityStrong◐ 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 Strong / 10 · rule-coverage 100% · ceiling Documented

PlainBridge's repository is well documented: the root README gives a strong overview (microservice-based end-to-end sample, .NET Aspire 10.x, real integrations like Redis/HybridCache/Duende BFF, orchestration via AppHost dashboard), lists high-level components, and links to an internal project-analyse doc. The web UI README is focused on its own directory (Angular CLI scaffolding, ng serve/ng build/run tests) rather than the repository's broader purpose, which is consistent with the per-directory documentation rule. A dedicated architecture/implementation assessment document exists but is clipped mid-sentence and cannot be flagged as missing.

XML-doc coverage: PlainBridge.Api.ApiEndPoint · ×13src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/PlainBridge.Api.ApiEndPoint.csproj

What to do

  1. Improve Documentation Quality — currently 8.0/10. — PlainBridge's repository is well documented: the root README gives a strong overview (microservice-based end-to-end sample, .NET Aspire 10.x, real integrations like Redis/HybridCache/Duende BFF, orchestration via AppHost dashboard), lists high-level components, and links to an internal project-analyse doc. The web UI README is focused on its own directory (Angular CLI scaffolding, ng serve/ng build/run tests) rather than the repository's broader purpose, which is consistent with the per-directory documentation rule. A dedicated architecture/implementation assessment document exists but is clipped mid-sentence and cannot be flagged as missing.

Detailed fixes: d19_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

2 naming inconsistencies across 200 sampled symbols.

Inconsistent spelling of the word 'Everything' in test method names. Some tests use 'EveryThing' (capital T) while others use 'EveryThin' (missing 'g'). This appears to be a typo in one instance and a casing inconsistency in others, rather than a deliberate naming convention.
Typo in the type name 'ApiApplcationUnitTestRunFixture'. The word 'Application' is misspelled as 'Applcation' in the type name itself. While this is a type name consistency issue, it affects all usages of this type.

What to do

  1. Resolve the 1 Inconsistent spelling of the word 'Everything' in test method names.… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 Typo in the type name 'ApiApplcationUnitTestRunFixture'. The word… 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.

D23 · Boundary Type-Coupling9.2 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

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

4 domain type(s) cross context boundaries across 9 contexts.

Cross-context type User (UserAggregate → HostAggregate)src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:25
Cross-context type User (UserAggregate → ServerAggregate)src/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:24
Cross-context type ServerApplication (ServerAggregate → UserAggregate)src/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:31
Cross-context type HostApplication (HostAggregate → UserAggregate)src/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:32

What to do

  1. Resolve the 1 Cross-context type User (UserAggregate → HostAggregate) finding(s) in Boundary Type-Coupling — start with HostApplication.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Cross-context type User (UserAggregate → ServerAggregate) finding(s) in Boundary Type-Coupling — start with ServerApplication.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Cross-context type ServerApplication (ServerAggregate → UserAggregate) finding(s) in Boundary Type-Coupling — start with User.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d23_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

94 valuable / 0 redundant across 200 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.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 18 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

93 % of calls cross a namespace and 10 % 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. Measured over the .cs source only — this repository's .ts was not sampled for call sites, so this score covers part of the tree, not all of it.

Pass-through layersrc/PlainBridge.Client/src/PlainBridge.Client.Application/Management/WebSocket/WebSocketManagement.cs:9

✓ On the Gold path — maintain.

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

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

29 finding(s): 0 critical, 6 high, 23 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 49 file(s) — `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommandHandler.cs` (line 13), `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/DeleteHostApplicationCommandHandler.cs` (line 11), `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateHostApplicationCommandHandler.cs` (line 12), `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateStateHostApplicationCommandHandler.cs` (line 12), `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Queries/GetAllHostApplicationsQueryHandler.cs` (line 11), … (+44 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 49 of those file(s) — `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommandHandler.cs`, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/DeleteHostApplicationCommandHandler.cs`, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateHostApplicationCommandHandler.cs`, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateStateHostApplicationCommandHandler.cs`, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Queries/GetAllHostApplicationsQueryHandler.cs`, … (+44 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 1 of those file(s) — `src/PlainBridge.Shared/src/PlainBridge.Shared.Application/Exceptions/DuplicatedException.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (12 warning-level).
  2. Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 warning-level).
  3. No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).

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

46 finding(s): 4 critical, 27 high, 10 medium, 5 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D31 · IaC & Container Security9.4 / 10Adequategated by 1 critical finding✓ 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 9.4 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.3 / 10Adequategated by 5 critical findings✓ 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 9.3 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: HostApplicationEndpoint.cs↔ServerApplicationEndPoint.cs 77%; HostApplicationService.cs↔ServerApplicationService.cs 73%; Program.cs↔Program.cs 71%

Boundary-crossing change coupling: Program.cs ↔ Program.cs · ×5src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/Program.cs:1
Change coupling: HostApplicationEndpoint.cs ↔ ServerApplicationEndPoint.cs · ×8src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/Endpoints/HostApplicationEndpoint.cs:1

What to do

  1. Resolve the 5 Boundary-crossing change coupling finding(s) in Change Coupling — start with Program.cs (2), AppHost.cs (2), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
  2. Resolve the 8 Change coupling finding(s) in Change Coupling — start with HostApplicationEndpoint.cs, HostApplicationService.cs, ServerBusService.cs. — One of this dimension's main actionable groups (8 warning-level).

Detailed fixes: d35_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-Life10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives1.0 / 10Critical✓ Tool-verified

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

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

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

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×7) — REDACTED:10, src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Ciba/Index.cshtml:10, REDACTED:10, …

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels4.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 control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×20) — REDACTED:75, REDACTED:72, REDACTED:105, …
  • 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. (×7) — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Ciba/_ScopeListItem.cshtml:38, src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Consent/_ScopeListItem.cshtml:38, src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Grants/Index.cshtml:50, …
  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×7) — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile/profile.component.html:12, src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile/profile.component.html:18, src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile/profile.component.html:24, …

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 structure4.8 / 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.

  • An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — REDACTED:20
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — REDACTED:17, src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Ciba/Index.cshtml:17
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ExternalLogin/Callback.cshtml:10, src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ExternalLogin/Challenge.cshtml:10
  • An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>. (×2) — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ExternalLogin/Callback.cshtml:10, src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ExternalLogin/Challenge.cshtml:10
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div>, so there is no content here to wrap — render the <main> from the component mounted into it. (×2) — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ExternalLogin/Callback.cshtml:10, src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ExternalLogin/Challenge.cshtml:10
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Shared/_Layout.cshtml:2
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <app-root>, so there is no content here to wrap — render the <main> from the component mounted into it. — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/index.html:2

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

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety5.4 / 10Adequate✓ Tool-verified

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.

  • `.spinner` moves (`animation: spin 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/sign-in-oidc/sign-in-oidc.component.css:34
  • `.strength::after` moves (`transition: width .3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile/profile.component.css:6

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement4.0 / 10Adequate✓ Tool-verified

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

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

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

  • No accessibility enforcement found — no a11y linter (@angular-eslint/eslint-plugin-template (a11y rules)) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 37 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Enforce accessibility in the toolchain: add @angular-eslint/eslint-plugin-template (a11y rules), then assert with cypress-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

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

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

AX10 · Code composition6.9 / 10Strong✓ 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.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

  • The namespaces PlainBridge.Api.Domain.HostAggregate ↔ PlainBridge.Api.Domain.ServerAggregate ↔ PlainBridge.Api.Domain.UserAggregate depend on each other. The lightest dependency in the cycle is PlainBridge.Api.Domain.HostAggregate → PlainBridge.Api.Domain.UserAggregate (PlainBridge.Api.Domain.HostAggregate.HostApplication → PlainBridge.Api.Domain.UserAggregate.User, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:8

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 direction6.2 / 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.

  • `PlainBridge.Api.Application` is a Application project but references `PlainBridge.Api.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/PlainBridge.Api/src/PlainBridge.Api.Application/PlainBridge.Api.Application.csproj:29
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure`, `DependencyResolver`. The inward dependency rule is broken here. It is named again on line 25. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PlainBridge.Api/src/PlainBridge.Api.Application/DependencyResolver.cs:6
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 7, 13. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommandHandler.cs:6
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 5, 11. Depend on an abstraction the inner layer owns, implemented in the outer one. (×2) — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/DeleteHostApplicationCommandHandler.cs:4, src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/DeleteServerApplicationCommandHandler.cs:4
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 6, 12. Depend on an abstraction the inner layer owns, implemented in the outer one. (×2) — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateHostApplicationCommandHandler.cs:5, src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateStateHostApplicationCommandHandler.cs:5
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`. The inward dependency rule is broken here. It is named again on line 11. Depend on an abstraction the inner layer owns, implemented in the outer one. (×2) — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Queries/GetAllHostApplicationsQueryHandler.cs:4, src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Queries/GetAllServerApplicationsQueryHandler.cs:4
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`. The inward dependency rule is broken here. It is named again on line 12. Depend on an abstraction the inner layer owns, implemented in the outer one. (×2) — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Queries/GetHostApplicationQueryHandler.cs:4, src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Queries/GetServerApplicationQueryHandler.cs:4
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 7, 16. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommandHandler.cs:6
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 7, 14. Depend on an abstraction the inner layer owns, implemented in the outer one. (×2) — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateServerApplicationCommandHandler.cs:6, src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateStateServerApplicationCommandHandler.cs:6
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`, `PlainBridge.Api.Infrastructure.ExternalServices.Identity`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IIdentityService`, `UserRequest`, `ChangeUserPasswordRequest`. The inward dependency rule is broken here. It is named again on lines 4, 5, 17, 26, 28. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/ChangeUserPasswordCommandHandler.cs:3
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`, `PlainBridge.Api.Infrastructure.ExternalServices.Identity`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IIdentityService`, `UserRequest`. The inward dependency rule is broken here. It is named again on lines 6, 7, 14, 26. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommandHandler.cs:5
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`. The inward dependency rule is broken here. It is named again on line 14. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserLocallyCommandHandler.cs:3
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`, `PlainBridge.Api.Infrastructure.ExternalServices.Identity`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IIdentityService`, `UserRequest`. The inward dependency rule is broken here. It is named again on lines 5, 6, 13, 22, 25. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/UpdateUserCommandHandler.cs:4
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one. (×3) — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Queries/GetAllUsersQuery.cs:4, src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Queries/GetUserByExternalIdQuery.cs:3, src/PlainBridge.Api/src/PlainBridge.Api.Application/Services/Session/ISessionService.cs:3
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`. The inward dependency rule is broken here. It is named again on lines 7, 12. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Queries/GetAllUsersQueryHandler.cs:6
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`. The inward dependency rule is broken here. It is named again on lines 7, 13. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Queries/GetUserByExternalIdQueryHandler.cs:6
  • This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`, `PlainBridge.Api.Infrastructure.Persistence.Cache`, `ICacheManagement`, `ApplicationSettings`. The inward dependency rule is broken here. It is named again on lines 10, 18. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PlainBridge.Api/src/PlainBridge.Api.Application/Services/Session/SessionService.cs:9

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.

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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

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

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

C2 · Access Controls10.0 / 10Exemplary○ Nothing flagged

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.

C3 · Audit Trail7.5 / 10Strong✓ Tool-verified

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

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

  • An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.

What to do

  • Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
DM1 · Aggregate boundaries10.0 / 10Exemplary✓ 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.

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

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.

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.

  • `HostApplication.UserId` is a raw `Int64` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int64`, in whatever form your language spells that. — src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:22
  • `ServerApplication.ServerApplicationViewId` 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/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:16
  • `ServerApplication.UserId` is a raw `Int64` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int64`, in whatever form your language spells that. — src/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:21
  • `User.ExternalId` 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/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:24

What to do

  • Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic 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 state7.0 / 10Strong✓ 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.

  • `HostApplication` exposes publicly writable state (AppId, Name, Domain, InternalUrl, UserId, User). — src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:15
  • `ServerApplication` exposes publicly writable state (AppId, ServerApplicationViewId, Name, InternalPort, ServerApplicationType, UserId, and 1 more). — src/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:13
  • `User` exposes publicly writable state (AppId, ExternalId, UserName, Email, PhoneNumber, Name, and 3 more). — src/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:15

What to do

  • Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary2.1 / 10Weak✓ 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.

  • `HostApplication` (domain layer) names `ForeignKeyAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:22
  • `HostApplicationTypeConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:76
  • `ServerApplication` (domain layer) names `ForeignKeyAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:21
  • `ServerApplicationTypeConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:85
  • `UserTypeConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:123
  • `ApplicationUser` (domain layer) names `IdentityUser` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Domain/Entities/ApplicationUser.cs:5
  • `BaseEntity` (domain layer) names `KeyAttribute` from `System.ComponentModel.DataAnnotations` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/PlainBridge.Shared/src/PlainBridge.Shared.Domain/Base/BaseEntity.cs:22
  • `BaseEntity` (domain layer) names `DatabaseGeneratedAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/PlainBridge.Shared/src/PlainBridge.Shared.Domain/Base/BaseEntity.cs:23
  • `BaseEntityTypeConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/PlainBridge.Shared/src/PlainBridge.Shared.Domain/Base/BaseEntity.cs:51
  • `BaseEntityTypeConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/PlainBridge.Shared/src/PlainBridge.Shared.Domain/Base/BaseEntity.cs:55
  • The domain project `PlainBridge.Api.Domain` references `Microsoft.EntityFrameworkCore` — a persistence dependency; the domain should own a port and let an infrastructure project reference it. — src/PlainBridge.Api/src/PlainBridge.Api.Domain/PlainBridge.Api.Domain.csproj:10
  • The domain project `PlainBridge.Api.Domain` references `Microsoft.EntityFrameworkCore.Abstractions` — a persistence dependency; the domain should own a port and let an infrastructure project reference it. — src/PlainBridge.Api/src/PlainBridge.Api.Domain/PlainBridge.Api.Domain.csproj:11
  • The domain project `PlainBridge.Api.Domain` references `Microsoft.EntityFrameworkCore.Relational` — a persistence dependency; the domain should own a port and let an infrastructure project reference it. — src/PlainBridge.Api/src/PlainBridge.Api.Domain/PlainBridge.Api.Domain.csproj:12
  • The domain project `PlainBridge.Shared.Domain` references `Microsoft.EntityFrameworkCore` — a persistence dependency; the domain should own a port and let an infrastructure project reference it. — src/PlainBridge.Shared/src/PlainBridge.Shared.Domain/PlainBridge.Shared.Domain.csproj:10

What to do

  • Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
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.

ED2 · Event/command shape10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether commands have a single handler (one owner of the decision) and fan-out is modelled with events.

Method: Roslyn scan (event-driven gated): command-shaped messages identified by convention; handler count per command checked for the exactly-one rule. Deterministic, hard fact.

ED4 · Outbox / dual-write3.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.

  • `CreateHostApplicationCommandHandler.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/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommandHandler.cs:15
  • `DeleteHostApplicationCommandHandler.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/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/DeleteHostApplicationCommandHandler.cs:13
  • `UpdateHostApplicationCommandHandler.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/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateHostApplicationCommandHandler.cs:14
  • `UpdateStateHostApplicationCommandHandler.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/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateStateHostApplicationCommandHandler.cs:14
  • `CreateServerApplicationCommandHandler.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/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommandHandler.cs:18
  • `DeleteServerApplicationCommandHandler.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/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/DeleteServerApplicationCommandHandler.cs:13
  • `UpdateServerApplicationCommandHandler.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/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateServerApplicationCommandHandler.cs:16
  • `UpdateStateServerApplicationCommandHandler.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/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateStateServerApplicationCommandHandler.cs:16

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 code9.9 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/PlainBridge.Client/src/PlainBridge.Client.Application/Management/WebSocket/WebSocketManagement.cs:11, src/PlainBridge.Server/src/PlainBridge.Server.Application/Management/WebSocket/WebSocketManagement.cs:11

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs7.8 / 10Strong✓ Tool-verified

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.

  • `GenerateToken` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/PlainBridge.Api/src/PlainBridge.Api.Application/Services/Token/TokenService.cs:21
  • `Options` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/PlainBridge.Client/src/PlainBridge.Client.Application/Management/WebSocket/WebSocketManagement.cs:11
  • `ConnectAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/PlainBridge.Server/src/PlainBridge.Server.Application/Management/WebSocket/WebSocketManagement.cs:11
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×7) — src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/DependencyResolver.cs:125, src/PlainBridge.Api/src/PlainBridge.Api.Application/DependencyResolver.cs:19, src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Infrastructure/Data/ApplicationDbContext.cs:22, …
  • A placeholder e-mail address ("YasinAsadnezhad@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — REDACTED:37
  • A placeholder e-mail address ("BobSmith@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — REDACTED:55

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)7.3 / 10Exemplary✓ 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 18 of 18 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation5.0 / 10Adequate✓ 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 structure10.0 / 10Exemplary✓ 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.

M4 · Documentation accuracy0.0 / 10Critical◐ 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.

  • README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (REDACTED and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:7
  • README.md runs `dotnet run --project src/PlainBridge.AppHost/PlainBridge.AppHost.csproj`, but `src/PlainBridge.AppHost/PlainBridge.AppHost.csproj` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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.md:116
  • README.md runs `docker compose --env-file infra/.env -f infra/docker-compose.yaml up -d cache messaging elasticsearch plain-bridge-dashboard`, but `infra/docker-compose.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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.md:137
  • docs/project-analys.md names `is-signing-key-0DC4B64548F26BFFF432AB5D01514AE4.json`, but no file or folder `is-signing-key-0DC4B64548F26BFFF432AB5D01514AE4.json` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — docs/project-analys.md:425
  • docs/project-analys.md names `docker-compose.yaml`, but no file or folder `docker-compose.yaml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — docs/project-analys.md:626
  • src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/bootstrap/README.md installs `bootstrap` (`npm install bootstrap`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/bootstrap/README.md:46
  • src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/bootstrap/README.md names `bootstrap.bundle.js`, but no file or folder `bootstrap.bundle.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/bootstrap/README.md:104
  • src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/bootstrap/README.md names `bootstrap.bundle.min.js`, but no file or folder `bootstrap.bundle.min.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/bootstrap/README.md:104
  • src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/jquery/README.md installs `jquery` (`npm install jquery`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/jquery/README.md:53

What to do

  • Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; README.md runs `dotnet run --project src/PlainBridge.AppHost/PlainBridge.AppHost.csproj`, but `src/PlainBridge.AppHost/PlainBridge.AppHost.csproj` does not exist; README.md runs `docker compose --env-file infra/.env -f infra/docker-compose.yaml up -d cache messaging elasticsearch plain-bridge-dashboard`, but `infra/docker-compose.yaml` does not exist; docs/project-analys.md names `is-signing-key-0DC4B64548F26BFFF432AB5D01514AE4.json`, but no file or folder `is-signing-key-0DC4B64548F26BFFF432AB5D01514AE4.json` exists; docs/project-analys.md names `docker-compose.yaml`, but no file or folder `docker-compose.yaml` exists.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

P2 · Observability9.5 / 10Exemplary✓ 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 9/11 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 11, 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.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

  • Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene3.0 / 10Weak✓ 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.

  • The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.

What to do

  • Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
  • Stamp a version in your build/package manifest (e.g. csproj <Version>, REDACTED, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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

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

  • `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/Endpoints/LoginEndpoint.cs:61
  • `new HttpClient(handler)` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/PlainBridge.Client/src/PlainBridge.Client.Application/Helpers/Http/HttpHelper.cs:62

What to do

  • Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ 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.

R1 · Type Safety9.8 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication8.3 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

  • src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-applications-list/host-applications-list.component.ts:25 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/components/server-applications-list/server-applications-list.component.ts:25 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-applications-list/host-applications-list.component.ts:25
  • src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-application-form/host-application-form.component.ts:26 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/components/server-application-form/server-application-form.component.ts:30 — the two spans are one implementation copied and then locally edited — 484 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-application-form/host-application-form.component.ts:26
  • src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/host-application.service.ts:7 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/server-application.service.ts:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/host-application.service.ts:7
  • src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/host-applications-routing.module.ts:6 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/server-applications-routing.module.ts:6 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/host-applications-routing.module.ts:6
  • src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/host-application.service.ts:5 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/server-application.service.ts:5 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/user.service.ts:5 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/host-application.service.ts:5
  • src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/components/dashboard/dashboard.component.ts:31 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/components/dashboard/dashboard.component.ts:45 — the two spans are one implementation copied and then locally edited — 63 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/components/dashboard/dashboard.component.ts:31
  • src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/toast.service.ts:14 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/toast.service.ts:29 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/toast.service.ts:14

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • (anonymous) has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/api-response.service.ts:36
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

R4 · Test Coverage4.7 / 10Adequate✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×19) — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/app-module.ts:1, src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/users/components/user-registration/user-registration.component.ts:1, src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/components/dashboard/dashboard.component.ts:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness8.7 / 10Exemplary✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

What to do

  • Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling6.7 / 10Strong✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • test ✓ · lint ✗ · typecheck ✓ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add eslint as REDACTED scripts and run them in CI.
R7 · Dead Code7.9 / 10Strong✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • Unreachable from the 2 application, 4 tooling and 13 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (2 application, 4 tooling, 13 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×5) — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/testing/factories.ts, src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/core/core.module.ts, src/PlainBridge.Web/src/PlainBridge.Web.UI/src/testing/http-mocks.ts, …
  • Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. (×2) — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/guards/auth.guard.ts:9, src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/auth.service.ts:13

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene9.5 / 10Exemplary✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

S1 · Web-Security Posture0.0 / 10Critical✓ 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.

  • `RemoteCertificateValidationCallback` is assigned a callback that returns `true` unconditionally, so every TLS peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Delete the override and let the platform validate. If a specific self-signed or internally-issued certificate genuinely has to be trusted, pin THAT one — compare the presented certificate's public key or thumbprint against the expected value and return `false` for everything else — and scope it to the single handler that talks to that host rather than to the whole process. If the override exists only to get past a development certificate, gate it on a build configuration or an explicit opt-in setting so it cannot ship. — src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/DependencyResolver.cs:45
  • The value is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — src/PlainBridge.Api/src/PlainBridge.Api.Application/Services/Token/TokenService.cs:34
  • `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path. — src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/DependencyResolver.cs:94
  • `ValidateAudience = false` means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent. — src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/DependencyResolver.cs:114
  • Set: Content-Security-Policy, Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−0.5 on this card.) — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/SecurityHeadersAttribute.cs:16
  • No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.) — src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/DependencyResolver.cs:100

What to do

  • Stop accepting every TLS certificate: remove the always-true validation callback so the platform verifies the chain, hostname and expiry. If one self-signed certificate must be trusted, pin it by public key or thumbprint on the single handler that needs it and reject all others — never process-wide.
  • Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations.
  • Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
  • Re-enable token validation — `ValidateAudience` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
  • Add Strict-Transport-Security beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
  • Set secure cookie flags — CookieSecurePolicy.Always, HttpOnly, and SameSite (Strict/Lax) on auth/session cookies. Skip only if the app sets no cookies.
X1 · Async correctness7.0 / 10Strong✓ Tool-verified

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

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

  • `File.ReadAllText` blocks the thread on I/O while `File.ReadAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin. (×2) — src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/Endpoints/LoginEndpoint.cs:32, src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/Worker.cs:25
  • `File.WriteAllText` blocks the thread on I/O while `File.WriteAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin. — src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/Endpoints/LoginEndpoint.cs:72
  • `MemoryStream.Write` blocks the thread on I/O while `MemoryStream.WriteAsync` exists to wait without one — inside a method that is already `async`, await the twin. — src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/Middleware/HttpRequestProxyMiddleware.cs:180

What to do

  • Blocking `File.ReadAllText` inside an `async` method
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 propagation9.2 / 10Exemplary✓ 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 110/125 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. (×14) — src/PlainBridge.Client/src/PlainBridge.Client.Application/Helpers/Http/HttpHelper.cs:12, src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Login/Index.cshtml.cs:47, src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Login/Index.cshtml.cs:60, …
  • No CancellationToken parameter, and the token `request.HttpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `request.HttpContext.RequestAborted` on, or take a CancellationToken. — src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/Middleware/HttpRequestProxyMiddleware.cs:149
  • 2 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
  • Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible). (×2) — src/PlainBridge.Api/src/PlainBridge.Api.Application/Services/Session/SessionService.cs:55, src/PlainBridge.Api/src/PlainBridge.Api.Application/Services/Session/SessionService.cs:85

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard3.5 / 10Weak✓ Tool-verified

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

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

  • The guard on line 21 rejects `host` and line 22 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(host)` is true of a value that is NOT null: it is satisfied by an EMPTY `host`, and on that path `host` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/HostApplication/HostApplicationService.cs:22

What to do

  • Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
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 unescaped10.0 / 10Exemplary○ Nothing flagged

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.

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 handling4.9 / 10Adequate✓ Tool-verified

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.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — src/PlainBridge.Client/src/PlainBridge.Client.Application/Services/UsePortSocket/UsePortSocketService.cs:132, src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/HttpRequestProxy/HttpRequestProxyService.cs:71, src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/WebSocket/WebSocketService.cs:105

What to do

  • Swallowed exception (empty catch)
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 logging7.0 / 10Strong✓ 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 `REDACTED` 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. (×3) — REDACTED:41, src/PlainBridge.Client/src/PlainBridge.Client.Application/Handler/HttpRequest/HttpRequestHandler.cs:87, src/PlainBridge.Client/src/PlainBridge.Client.Application/Handler/WebSocket/WebSocketHandler.cs:59

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types7.0 / 10Strong✓ 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.

  • This method contradicts itself about `hostApplication`: line 48 writes `hostApplication?.UserName`, which says `hostApplication` can be null, but line 48 then dereferences it directly as `hostApplication.InternalUrl` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `hostApplication` truly cannot be null here, the `?.` is misleading. Settle it one way — test `hostApplication` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/Middleware/HttpRequestProxyMiddleware.cs:48
  • ~3.8 `!` suppressions per 1k syntax nodes — 179 suppression(s) across the 47600 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

What to do

  • Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

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
AC5 · ARIA correctness4.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 Health69%StrongSolid.
Architecture83%ExemplarySolid.
Maturity50%Adequate — gated by M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness50%Adequate — gated by P6, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security49%Adequate — gated by D29, D30, S1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling59%Adequate — gated by DM2, DM6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven74%Adequate — gated by ED4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility39%Adequate — gated by AC1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 3 check(s) recorded observations but carry no score

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

  • D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • 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 — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for

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

  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 33 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.
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence 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.
  • C1 Data Protection — This is a dotnet-new template — at-rest encryption and key-vaulting are deferred to the application you build from it. Add ASP.NET Data Protection / column encryption + a key vault for your real data store when you productionise.
  • D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — 49 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • ED3 Event naming — no domain or integration events detected — event-naming check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
  • P8 Schema migrations — EF Core is used, but the schema-migration mechanism could not be identified — this check only recognises EF migrations, so any other migration runner reads as an absence. Our limit, not a verdict on this repository.
  • 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.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • 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 — 127 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×27
  • 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
  • + 2 more in this group — see findings.md.
AC2 · Forms & labels · <input> without a programmatic label · ×25
  • <input> without a programmatic label REDACTED:75 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label REDACTED:72 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label REDACTED:105 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-application-form/host-application-form.component.html:13 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-application-form/host-application-form.component.html:21 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-application-form/host-application-form.component.html:29 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-applications-list/host-applications-list.component.html:27 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile/profile.component.html:12 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile/profile.component.html:18 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile/profile.component.html:24 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile/profile.component.html:29 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile/profile.component.html:47 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile/profile.component.html:57 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile/profile.component.html:72 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/components/server-application-form/server-application-form.component.html:14 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/components/server-application-form/server-application-form.component.html:23 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/components/server-application-form/server-application-form.component.html:41 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/components/server-applications-list/server-applications-list.component.html:27 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/users/components/user-registration/user-registration.component.html:14 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/users/components/user-registration/user-registration.component.html:24 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/users/components/user-registration/user-registration.component.html:36 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/users/components/user-registration/user-registration.component.html:46 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/users/components/user-registration/user-registration.component.html:56 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/users/components/user-registration/user-registration.component.html:61 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/users/components/user-registration/user-registration.component.html:73 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×14
  • Domain depends on infrastructure: HostApplication src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:22 — `HostApplication` (domain layer) names `ForeignKeyAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: HostApplicationTypeConfiguration src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:76 — `HostApplicationTypeConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ServerApplication src/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:21 — `ServerApplication` (domain layer) names `ForeignKeyAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ServerApplicationTypeConfiguration src/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:85 — `ServerApplicationTypeConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: UserTypeConfiguration src/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:123 — `UserTypeConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: ApplicationUser src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Domain/Entities/ApplicationUser.cs:5 — `ApplicationUser` (domain layer) names `IdentityUser` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: BaseEntity src/PlainBridge.Shared/src/PlainBridge.Shared.Domain/Base/BaseEntity.cs:22 — `BaseEntity` (domain layer) names `KeyAttribute` from `System.ComponentModel.DataAnnotations` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: BaseEntity src/PlainBridge.Shared/src/PlainBridge.Shared.Domain/Base/BaseEntity.cs:23 — `BaseEntity` (domain layer) names `DatabaseGeneratedAttribute` from `System.ComponentModel.DataAnnotations.Schema` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: BaseEntityTypeConfiguration src/PlainBridge.Shared/src/PlainBridge.Shared.Domain/Base/BaseEntity.cs:51 — `BaseEntityTypeConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: BaseEntityTypeConfiguration src/PlainBridge.Shared/src/PlainBridge.Shared.Domain/Base/BaseEntity.cs:55 — `BaseEntityTypeConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: PlainBridge.Api.Domain src/PlainBridge.Api/src/PlainBridge.Api.Domain/PlainBridge.Api.Domain.csproj:10 — The domain project `PlainBridge.Api.Domain` references `Microsoft.EntityFrameworkCore` — a persistence dependency; the domain should own a port and let an infrastructure project reference it.
  • Domain depends on infrastructure: PlainBridge.Api.Domain src/PlainBridge.Api/src/PlainBridge.Api.Domain/PlainBridge.Api.Domain.csproj:11 — The domain project `PlainBridge.Api.Domain` references `Microsoft.EntityFrameworkCore.Abstractions` — a persistence dependency; the domain should own a port and let an infrastructure project reference it.
  • Domain depends on infrastructure: PlainBridge.Api.Domain src/PlainBridge.Api/src/PlainBridge.Api.Domain/PlainBridge.Api.Domain.csproj:12 — The domain project `PlainBridge.Api.Domain` references `Microsoft.EntityFrameworkCore.Relational` — a persistence dependency; the domain should own a port and let an infrastructure project reference it.
  • Domain depends on infrastructure: PlainBridge.Shared.Domain src/PlainBridge.Shared/src/PlainBridge.Shared.Domain/PlainBridge.Shared.Domain.csproj:10 — The domain project `PlainBridge.Shared.Domain` references `Microsoft.EntityFrameworkCore` — a persistence dependency; the domain should own a port and let an infrastructure project reference it.
ED4 · Outbox / dual-write · Dual write (no outbox) · ×8
  • Dual write (no outbox): CreateHostApplicationCommandHandler.Handle src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommandHandler.cs:15 — `CreateHostApplicationCommandHandler.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).
  • Dual write (no outbox): DeleteHostApplicationCommandHandler.Handle src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/DeleteHostApplicationCommandHandler.cs:13 — `DeleteHostApplicationCommandHandler.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).
  • Dual write (no outbox): UpdateHostApplicationCommandHandler.Handle src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateHostApplicationCommandHandler.cs:14 — `UpdateHostApplicationCommandHandler.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).
  • Dual write (no outbox): UpdateStateHostApplicationCommandHandler.Handle src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateStateHostApplicationCommandHandler.cs:14 — `UpdateStateHostApplicationCommandHandler.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).
  • Dual write (no outbox): CreateServerApplicationCommandHandler.Handle src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommandHandler.cs:18 — `CreateServerApplicationCommandHandler.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).
  • Dual write (no outbox): DeleteServerApplicationCommandHandler.Handle src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/DeleteServerApplicationCommandHandler.cs:13 — `DeleteServerApplicationCommandHandler.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).
  • Dual write (no outbox): UpdateServerApplicationCommandHandler.Handle src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateServerApplicationCommandHandler.cs:16 — `UpdateServerApplicationCommandHandler.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).
  • Dual write (no outbox): UpdateStateServerApplicationCommandHandler.Handle src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateStateServerApplicationCommandHandler.cs:16 — `UpdateStateServerApplicationCommandHandler.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).
AC1 · Text alternatives · <img> without a text alternative · ×7
  • <img> without a text alternative REDACTED:10 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Ciba/Index.cshtml:10 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative REDACTED:10 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative REDACTED:42 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Grants/Index.cshtml:32 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Index.cshtml:6 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Shared/_Nav.cshtml:15 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels · <label> that labels no control · ×7
  • <label> that labels no control src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Ciba/_ScopeListItem.cshtml:38 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Consent/_ScopeListItem.cshtml:38 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Grants/Index.cshtml:50 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Grants/Index.cshtml:54 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Grants/Index.cshtml:59 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Grants/Index.cshtml:65 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Grants/Index.cshtml:77 — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×5
  • Boundary-crossing change coupling: Program.cs ↔ Program.cs src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/Program.cs:1 — `src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/Program.cs` (context PlainBridge) and `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Program.cs` (context PlainBridge.IdentityServer) sit in DIFFERENT parts of the tree yet change together 71% of the time (10 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `b07ed08e` Implemented OTEL.; `d373725d` Changed port setting pattern. (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Program.cs` and `src/PlainBridge.IdentityServer/PlainBridge.IdentityServer.EndPoint/Program.cs`); `29e28c3c` Fixed some problems regarding publish (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Program.cs` and `src/PlainBridge.IdentityServer/PlainBridge.IdentityServer.EndPoint/Program.cs`) — run `git show` on any of them.
  • Boundary-crossing change coupling: Program.cs ↔ Program.cs src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/Program.cs:1 — `src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/Program.cs` (context PlainBridge) and `src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/Program.cs` (context PlainBridge.Server) sit in DIFFERENT parts of the tree yet change together 64% of the time (14 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `b07ed08e` Implemented OTEL.; `d373725d` Changed port setting pattern. (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Program.cs` and `src/PlainBridge.Server/PlainBridge.Server.ApiEndPoint/Program.cs`); `29e28c3c` Fixed some problems regarding publish (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Program.cs` and `src/PlainBridge.Server/PlainBridge.Server.ApiEndPoint/Program.cs`) — run `git show` on any of them.
  • Boundary-crossing change coupling: AppHost.cs ↔ DependencyResolver.cs src/PlainBridge.AppHost/PlainBridge.AppHost.AppHost/AppHost.cs:1 — `src/PlainBridge.AppHost/PlainBridge.AppHost.AppHost/AppHost.cs` (context PlainBridge.AppHost) and `src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/DependencyResolver.cs` (context PlainBridge.Server) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `b07ed08e` Implemented OTEL.; `9d542cc4` Fixed some problems in docker compose. (at that commit the files were still `src/PlainBridge.AppHost/Program.cs` and `src/PlainBridge.Server/PlainBridge.Server.ApiEndPoint/DependencyResolver.cs`); `ba58e5cb` Fixed problems. (at that commit the files were still `src/PlainBridge.AppHost/Program.cs` and `src/PlainBridge.Server/PlainBridge.Server.ApiEndPoint/DependencyResolver.cs`) — run `git show` on any of them.
  • Boundary-crossing change coupling: AppHost.cs ↔ Program.cs src/PlainBridge.AppHost/PlainBridge.AppHost.AppHost/AppHost.cs:1 — `src/PlainBridge.AppHost/PlainBridge.AppHost.AppHost/AppHost.cs` (context PlainBridge.AppHost) and `src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/Program.cs` (context PlainBridge.Server) sit in DIFFERENT parts of the tree yet change together 50% of the time (11 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `b07ed08e` Implemented OTEL.; `d373725d` Changed port setting pattern. (at that commit the files were still `src/PlainBridge.AppHost/Program.cs` and `src/PlainBridge.Server/PlainBridge.Server.ApiEndPoint/Program.cs`); `24165eed` Fixed some bugs. (at that commit the files were still `src/PlainBridge.AppHost/Program.cs` and `src/PlainBridge.Server/PlainBridge.Server.ApiEndPoint/Program.cs`) — run `git show` on any of them.
  • Boundary-crossing change coupling: REDACTED ↔ AppHost.cs REDACTED:1 — `REDACTED` (context PlainBridge) and `src/PlainBridge.AppHost/PlainBridge.AppHost.AppHost/AppHost.cs` (context PlainBridge.AppHost) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `3ec47971` Upgraded project to dotnet 10 (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/LoginEndpoint.cs` and `src/PlainBridge.AppHost/Program.cs`); `d373725d` Changed port setting pattern. (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/LoginEndpoint.cs` and `src/PlainBridge.AppHost/Program.cs`); `ba58e5cb` Fixed problems. (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/LoginEndpoint.cs` and `src/PlainBridge.AppHost/Program.cs`) — run `git show` on any of them.
D17 · Explicit Debt · WriteOnlyPrivateField · ×4
  • WriteOnlyPrivateField src/PlainBridge.Api/tests/PlainBridge.Api.Tests/UnitTests/Application/Services/SessionServiceTests.cs:23 — private ApiApplcationUnitTestRunFixture _fixture — 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/PlainBridge.Api/tests/PlainBridge.Api.Tests/UnitTests/Application/Services/TokenServiceTests.cs:16 — private ApiApplcationUnitTestRunFixture _fixture — 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/PlainBridge.Client/tests/PlainBridge.Client.Tests/UnitTests/Services/ClientBusServiceTests.cs:14 — private Mock<IChannel> _mockChannel — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField REDACTED.cs:21 — private IOptions<IdentityServerOptions> _options — 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.
D30 · Dependency Vulnerabilities · Critical CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · EmptyCatchBlock · ×3
  • EmptyCatchBlock src/PlainBridge.Client/src/PlainBridge.Client.Application/Services/UsePortSocket/UsePortSocketService.cs:132 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/HttpRequestProxy/HttpRequestProxyService.cs:71 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/WebSocket/WebSocketService.cs:105 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D28 · Secrets (history) · High secret · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <textarea> without a programmatic label · ×2
  • <textarea> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-application-form/host-application-form.component.html:37 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <textarea> without a programmatic label src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/components/server-application-form/server-application-form.component.html:49 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC3 · Page structure · <html> without a lang · ×2
  • <html> without a lang src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ExternalLogin/Callback.cshtml:10 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ExternalLogin/Challenge.cshtml:10 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure · Document <title> is empty · ×2
  • Document <title> is empty src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ExternalLogin/Callback.cshtml:10 — An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
  • Document <title> is empty src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ExternalLogin/Challenge.cshtml:10 — An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
AC3 · Page structure · <iframe> without a title · ×1
  • <iframe> without a title REDACTED:20 — An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:8 — The namespaces PlainBridge.Api.Domain.HostAggregate ↔ PlainBridge.Api.Domain.ServerAggregate ↔ PlainBridge.Api.Domain.UserAggregate depend on each other. The lightest dependency in the cycle is PlainBridge.Api.Domain.HostAggregate → PlainBridge.Api.Domain.UserAggregate (PlainBridge.Api.Domain.HostAggregate.HostApplication → PlainBridge.Api.Domain.UserAggregate.User, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
AX4 · Dependency direction · Dependency-rule violation · ×1
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/PlainBridge.Api.Application.csproj:29 — `PlainBridge.Api.Application` is a Application project but references `PlainBridge.Api.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.
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
D31 · IaC & Container Security · High IaC · ×1
  • REDACTED
D5 · Coupling · Layer violation · ×1
  • Layer violation: Application → Infrastructure src/PlainBridge.Api/src/PlainBridge.Api.Application/PlainBridge.Api.Application.csproj:29 — PlainBridge.Api.Application (Application) references PlainBridge.Api.Infrastructure (Infrastructure) — dependencies must point inward (Web → Application → Domain; Infrastructure implements inner interfaces, nothing depends outward on it).
S1 · Web-Security Posture · TLS certificate validation disabled · ×1
  • TLS certificate validation disabled src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/DependencyResolver.cs:45 — `RemoteCertificateValidationCallback` is assigned a callback that returns `true` unconditionally, so every TLS peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Delete the override and let the platform validate. If a specific self-signed or internally-issued certificate genuinely has to be trusted, pin THAT one — compare the presented certificate's public key or thumbprint against the expected value and return `false` for everything else — and scope it to the single handler that talks to that host rather than to the whole process. If the override exists only to get past a development certificate, gate it on a build configuration or an explicit opt-in setting so it cannot ship.
S1 · Web-Security Posture · Cryptographic key material is a compile-time constant · ×1
  • Cryptographic key material is a compile-time constant src/PlainBridge.Api/src/PlainBridge.Api.Application/Services/Token/TokenService.cs:34 — The value is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
Serious — 193 finding(s)
AX4 · Dependency direction · Dependency-rule violation · ×23
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/DependencyResolver.cs:6 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure`, `DependencyResolver`. The inward dependency rule is broken here. It is named again on line 25. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommandHandler.cs:6 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 7, 13. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/DeleteHostApplicationCommandHandler.cs:4 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 5, 11. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateHostApplicationCommandHandler.cs:5 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 6, 12. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateStateHostApplicationCommandHandler.cs:5 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 6, 12. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Queries/GetAllHostApplicationsQueryHandler.cs:4 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`. The inward dependency rule is broken here. It is named again on line 11. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Queries/GetHostApplicationQueryHandler.cs:4 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`. The inward dependency rule is broken here. It is named again on line 12. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommandHandler.cs:6 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 7, 16. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/DeleteServerApplicationCommandHandler.cs:4 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 5, 11. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateServerApplicationCommandHandler.cs:6 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 7, 14. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateStateServerApplicationCommandHandler.cs:6 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.ExternalServices.Messaging`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IEventBus`. The inward dependency rule is broken here. It is named again on lines 7, 14. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Queries/GetAllServerApplicationsQueryHandler.cs:4 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`. The inward dependency rule is broken here. It is named again on line 11. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Queries/GetServerApplicationQueryHandler.cs:4 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`. The inward dependency rule is broken here. It is named again on line 12. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/ChangeUserPasswordCommandHandler.cs:3 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`, `PlainBridge.Api.Infrastructure.ExternalServices.Identity`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IIdentityService`, `UserRequest`, `ChangeUserPasswordRequest`. The inward dependency rule is broken here. It is named again on lines 4, 5, 17, 26, 28. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommandHandler.cs:5 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`, `PlainBridge.Api.Infrastructure.ExternalServices.Identity`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IIdentityService`, `UserRequest`. The inward dependency rule is broken here. It is named again on lines 6, 7, 14, 26. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserLocallyCommandHandler.cs:3 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`. The inward dependency rule is broken here. It is named again on line 14. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/UpdateUserCommandHandler.cs:4 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`, `PlainBridge.Api.Infrastructure.ExternalServices.Identity`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`, `IIdentityService`, `UserRequest`. The inward dependency rule is broken here. It is named again on lines 5, 6, 13, 22, 25. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Queries/GetAllUsersQuery.cs:4 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Queries/GetAllUsersQueryHandler.cs:6 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`. The inward dependency rule is broken here. It is named again on lines 7, 12. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Queries/GetUserByExternalIdQuery.cs:3 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Queries/GetUserByExternalIdQueryHandler.cs:6 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`, `PlainBridge.Api.Infrastructure.Persistence.Data.Context`, `MainDbContext`. The inward dependency rule is broken here. It is named again on lines 7, 13. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Services/Session/ISessionService.cs:3 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: PlainBridge.Api.Application (Application) → PlainBridge.Api.Infrastructure (Infrastructure) src/PlainBridge.Api/src/PlainBridge.Api.Application/Services/Session/SessionService.cs:9 — This Application file depends on the Infrastructure project `PlainBridge.Api.Infrastructure`: it names `PlainBridge.Api.Infrastructure.DTOs`, `PlainBridge.Api.Infrastructure.Persistence.Cache`, `ICacheManagement`, `ApplicationSettings`. The inward dependency rule is broken here. It is named again on lines 10, 18. Depend on an abstraction the inner layer owns, implemented in the outer one.
R4 · Test Coverage · No test reaches this file · ×19
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/app-module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/users/components/user-registration/user-registration.component.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/components/dashboard/dashboard.component.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/server-applications.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/app-routing-module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/components/layout/layout.component.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/host-applications.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/sign-in-oidc/sign-in-oidc.component.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/testing/factories.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/users/users.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/core/core.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/testing/http-mocks.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/host-applications-routing.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/server-applications-routing.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/testing/test-ids.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile-routing.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/users/users-routing.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/PlainBridge.Web/src/PlainBridge.Web.UI/src/main.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
X2 · Cancellation propagation · Async method without CancellationToken · ×15
  • Async method without CancellationToken: CreateAndSendRequestAsync src/PlainBridge.Client/src/PlainBridge.Client.Application/Helpers/Http/HttpHelper.cs:12 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnGet src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Login/Index.cshtml.cs:47 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnPost src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Login/Index.cshtml.cs:60 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnGet src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Logout/Index.cshtml.cs:28 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnPost src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Logout/Index.cshtml.cs:59 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnGet REDACTED.cs:35 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnPost REDACTED.cs:50 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnGet REDACTED.cs:36 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnPost REDACTED.cs:51 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnGet REDACTED.cs:38 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnPost REDACTED.cs:59 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnGet src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ServerSideSessions/Index.cshtml.cs:32 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnPost src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ServerSideSessions/Index.cshtml.cs:58 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetRequestDataAsync src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/Middleware/HttpRequestProxyMiddleware.cs:149 — No CancellationToken parameter, and the token `request.HttpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `request.HttpContext.RequestAborted` on, or take a CancellationToken.
  • Async method without CancellationToken: ReadStreamInBytesAsync src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/Middleware/HttpRequestProxyMiddleware.cs:172 — No CancellationToken parameter — this work can't be stopped early once started.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×8
  • Change coupling: HostApplicationEndpoint.cs ↔ ServerApplicationEndPoint.cs src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/Endpoints/HostApplicationEndpoint.cs:1 — `src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/Endpoints/HostApplicationEndpoint.cs` and `src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/Endpoints/ServerApplicationEndPoint.cs` change together 77% of the time (10 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `24165eed` Fixed some bugs. (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/HostApplicationEndpoint.cs` and `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/ServerApplicationEndPoint.cs`); `2c365950` Refactored (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/HostApplicationEndpoint.cs` and `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/ServerApplicationEndPoint.cs`); `46ace605` Fixed small bugs. (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/HostApplicationEndpoint.cs` and `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/ServerApplicationEndPoint.cs`) — run `git show` on any of them.
  • Change coupling: HostApplicationService.cs ↔ ServerApplicationService.cs src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/HostApplication/HostApplicationService.cs:1 — `src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/HostApplication/HostApplicationService.cs` and `src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplication/ServerApplicationService.cs` change together 73% of the time (11 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `7ffc4275` Coded unit tests for server project (services class) (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Services/HostApplication/HostApplicationService.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerApplication/ServerApplicationService.cs`); `c8cc761e` Fixed small bugs. Structured test projects. (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Services/HostApplication/HostApplicationService.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerApplication/ServerApplicationService.cs`); `8ce669a9` Created client application project. Migrated cache management to hybr… (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Services/HostApplication/HostApplicationService.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerApplication/ServerApplicationService.cs`) — run `git show` on any of them.
  • Change coupling: ServerBusService.cs ↔ WebSocketService.cs src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerBus/ServerBusService.cs:1 — `src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerBus/ServerBusService.cs` and `src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/WebSocket/WebSocketService.cs` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `cf63aa65` Upgradet projects from dotnet 9.0.8 to 9.0.9 (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerBus/ServerBusService.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/WebSocket/WebSocketService.cs`); `14bca198` Coded HttpRequestHandler (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerBus/ServerBusService.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/WebSocket/WebSocketService.cs`); `f37351f2` Tested and fixed some problems in frontend. (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerBus/ServerBusService.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/WebSocket/WebSocketService.cs`) — run `git show` on any of them.
  • Change coupling: CacheManagement.cs ↔ ServerApplicationService.cs src/PlainBridge.Server/src/PlainBridge.Server.Application/Management/Cache/CacheManagement.cs:1 — `src/PlainBridge.Server/src/PlainBridge.Server.Application/Management/Cache/CacheManagement.cs` and `src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplication/ServerApplicationService.cs` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `d3f15eb3` Fixed some bugs. (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Management/Cache/CacheManagement.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerApplication/ServerApplicationService.cs`); `4b7307e3` Coded WebSocket management and handler (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Management/Cache/CacheManagement.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerApplication/ServerApplicationService.cs`); `8ce669a9` Created client application project. Migrated cache management to hybr… (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Management/Cache/CacheManagement.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerApplication/ServerApplicationService.cs`) — run `git show` on any of them.
  • Change coupling: ApiExternalBusService.cs ↔ HostApplicationService.cs src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ApiExternalBus/ApiExternalBusService.cs:1 — `src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ApiExternalBus/ApiExternalBusService.cs` and `src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/HostApplication/HostApplicationService.cs` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `8ce669a9` Created client application project. Migrated cache management to hybr… (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ApiExternalBus/ApiExternalBusService.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/HostApplication/HostApplicationService.cs`); `50dedae6` Coded 2 middlware (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ApiExternalBus/ApiExternalBusService.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/HostApplication/HostApplicationService.cs`); `6f0206a7` Added logger to Server project. (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ApiExternalBus/ApiExternalBusService.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/HostApplication/HostApplicationService.cs`) — run `git show` on any of them.
  • Change coupling: REDACTED ↔ Program.cs REDACTED:1 — `REDACTED` and `src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/Program.cs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `d373725d` Changed port setting pattern. (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/LoginEndpoint.cs` and `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Program.cs`); `24165eed` Fixed some bugs. (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/LoginEndpoint.cs` and `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Program.cs`); `2c365950` Refactored (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/LoginEndpoint.cs` and `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Program.cs`) — run `git show` on any of them.
  • Change coupling: DependencyResolver.cs ↔ REDACTED src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/DependencyResolver.cs:1 — `src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/DependencyResolver.cs` and `REDACTED` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `3ec47971` Upgraded project to dotnet 10 (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/DependencyResolver.cs` and `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/LoginEndpoint.cs`); `4e6449ef` Moved cacheManagement to Infrustructure layer (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/DependencyResolver.cs` and `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/LoginEndpoint.cs`); `ba58e5cb` Fixed problems. (at that commit the files were still `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/DependencyResolver.cs` and `src/PlainBridge.Api/PlainBridge.Api.ApiEndPoint/Endpoints/LoginEndpoint.cs`) — run `git show` on any of them.
  • Change coupling: ServerApplicationConsumerService.cs ↔ ServerBusService.cs src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs:1 — `src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs` and `src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerBus/ServerBusService.cs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `cf63aa65` Upgradet projects from dotnet 9.0.8 to 9.0.9 (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerBus/ServerBusService.cs`); `f37351f2` Tested and fixed some problems in frontend. (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerBus/ServerBusService.cs`); `4157cb92` Added user in server project. (at that commit the files were still `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs` and `src/PlainBridge.Server/PlainBridge.Server.Application/Services/ServerBus/ServerBusService.cs`) — run `git show` on any of them.
AC3 · Page structure · Page without a main landmark · ×4
  • Page without a main landmark src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ExternalLogin/Callback.cshtml:10 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div>, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/ExternalLogin/Challenge.cshtml:10 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div>, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/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>.
  • Page without a main landmark src/PlainBridge.Web/src/PlainBridge.Web.UI/src/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <app-root>, so there is no content here to wrap — render the <main> from the component mounted into it.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · CommentedOutCode · ×3
  • CommentedOutCode src/PlainBridge.AppHost/PlainBridge.AppHost.ServiceDefaults/Extensions.cs:93 — 5 consecutive commented-code lines
  • CommentedOutCode src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Infrastructure/Data/ApplicationDbContext.cs:20 — 5 consecutive commented-code lines
  • CommentedOutCode src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/Worker.cs:16 — 3 consecutive commented-code lines
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateStateHostApplicationCommandHandler.cs:25 — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateStateHostApplicationCommandHandler.cs:25-30 | src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateStateServerApplicationCommandHandler.cs:27-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `UpdateStateHostApplicationCommand` in one and `UpdateStateServerApplicationCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (6 lines × 2) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommandHandler.cs:48 — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommandHandler.cs:48-53 | src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserLocallyCommandHandler.cs:27-32 — 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/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommandHandler.cs:48` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `CreateUserCommand` in one and `CreateUserLocallyCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (6 lines × 2) src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs:86 — src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs:86-91 | src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs:142-147 — 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/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs:86` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×3
  • Duplicated block (9 lines × 2) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommand.cs:23 — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommand.cs:23-31 | src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateHostApplicationCommand.cs:21-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommand.cs:19` calls `Display` and `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateHostApplicationCommand.cs:19` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/ExternalServices/Identity/IdentityService.cs:91 — src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/ExternalServices/Identity/IdentityService.cs:91-99 | src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/ExternalServices/Identity/IdentityService.cs:119-127 — 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/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/ExternalServices/Identity/IdentityService.cs:91` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 2) src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Consent/ViewModel.cs:3 — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Consent/ViewModel.cs:3-11 | src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Device/ViewModel.cs:3-11 — `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Consent/ViewModel.cs` and `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Device/ViewModel.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 9 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Consent/ViewModel.cs:3` 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×3
  • Swallowed exception (empty catch) src/PlainBridge.Client/src/PlainBridge.Client.Application/Services/UsePortSocket/UsePortSocketService.cs:132 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/HttpRequestProxy/HttpRequestProxyService.cs:71 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/WebSocket/WebSocketService.cs:105 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×2
  • Heading level jumps from h1 to h3 REDACTED:17 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h3 src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Ciba/Index.cshtml:17 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×2
  • Animation without a prefers-reduced-motion guard src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/sign-in-oidc/sign-in-oidc.component.css:34 — `.spinner` moves (`animation: spin 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/profile/profile/profile.component.css:6 — `.strength::after` moves (`transition: width .3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D31 · IaC & Container Security · Medium IaC · ×2
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×2
  • Duplicated block (19–20 lines × 2) src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/ExternalServices/Identity/IdentityService.cs:45 — src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/ExternalServices/Identity/IdentityService.cs:45-63 | src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/ExternalServices/Identity/IdentityService.cs:102-121 — 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/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/ExternalServices/Identity/IdentityService.cs:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19–20 lines × 2) src/PlainBridge.Shared/src/PlainBridge.Shared.Application/Mediator/Mediator.cs:31 — src/PlainBridge.Shared/src/PlainBridge.Shared.Application/Mediator/Mediator.cs:31-49 | src/PlainBridge.Shared/src/PlainBridge.Shared.Application/Mediator/Mediator.cs:70-89 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×2
  • Duplicated block (10 lines × 3) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs:20 — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs:20-29 | src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserLocallyCommand.cs:20-29 | src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/DTOs/UserRequestDto.cs:14-23 — before extracting anything, compare `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs` and `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserLocallyCommand.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 3) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs:23 — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs:23-32 | src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateServerApplicationCommand.cs:24-33 | src/PlainBridge.Shared/src/PlainBridge.Shared.Application/DTOs/ServerApplicationDto.cs:24-33 — before extracting anything, compare `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs` and `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateServerApplicationCommand.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/PlainBridge.Shared/src/PlainBridge.Shared.Application/DTOs/ServerApplicationDto.cs:21` calls `Display` and `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs:21` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2
  • Duplicated block (7 lines × 2) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommand.cs:11 — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommand.cs:11-17 | src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateHostApplicationCommand.cs:13-19 — 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 (7 lines × 2) src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Consent/InputModel.cs:3 — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Consent/InputModel.cs:3-9 | src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Device/InputModel.cs:3-9 — `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Consent/InputModel.cs` and `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Device/InputModel.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 7 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Consent/InputModel.cs:3` 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.
GD1 · Unfinished & placeholder code · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException src/PlainBridge.Client/src/PlainBridge.Client.Application/Management/WebSocket/WebSocketManagement.cs:11 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/PlainBridge.Server/src/PlainBridge.Server.Application/Management/WebSocket/WebSocketManagement.cs:11 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException src/PlainBridge.Client/src/PlainBridge.Client.Application/Management/WebSocket/WebSocketManagement.cs:11 — `Options` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/PlainBridge.Server/src/PlainBridge.Server.Application/Management/WebSocket/WebSocketManagement.cs:11 — `ConnectAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×2
  • Outbound HTTP without resilience src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/Endpoints/LoginEndpoint.cs:61 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
  • Outbound HTTP without resilience src/PlainBridge.Client/src/PlainBridge.Client.Application/Helpers/Http/HttpHelper.cs:62 — `new HttpClient(handler)` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
X1 · Async correctness · Blocking `File.ReadAllText` inside an `async` method · ×2
  • Blocking `File.ReadAllText` inside an `async` method src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/Endpoints/LoginEndpoint.cs:32 — `File.ReadAllText` blocks the thread on I/O while `File.ReadAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin.
  • Blocking `File.ReadAllText` inside an `async` method src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/Worker.cs:25 — `File.ReadAllText` blocks the thread on I/O while `File.ReadAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin.
X2 · Cancellation propagation · Async method drops its CancellationToken · ×2
  • Async method drops its CancellationToken: GetCurrentUserProfileAsync src/PlainBridge.Api/src/PlainBridge.Api.Application/Services/Session/SessionService.cs:55 — Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
  • Async method drops its CancellationToken: RefreshTokenAsync src/PlainBridge.Api/src/PlainBridge.Api.Application/Services/Session/SessionService.cs:85 — Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (@angular-eslint/eslint-plugin-template (a11y rules)) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 37 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.
D1 · Cyclomatic Complexity · HttpHelper.CreateAndSendRequestAsync (cyclomatic 18) · ×1
  • HttpHelper.CreateAndSendRequestAsync (cyclomatic 18) src/PlainBridge.Client/src/PlainBridge.Client.Application/Helpers/Http/HttpHelper.cs:12 — HttpHelper.CreateAndSendRequestAsync has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D17 · Explicit Debt · Whole file has no live code · ×1
  • Whole file has no live code — 3 debt markers inside it src/PlainBridge.Client/tests/PlainBridge.Client.Tests/UnitTests/Management/WebSocketManagementTests.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 3 debt markers (3 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 3 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · TodoComment · ×1
  • TodoComment REDACTED.cs:190 — // todo: use the parsed scope value in the display? — 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.
D17 · Explicit Debt · BarePragmaDisable · ×1
  • BarePragmaDisable src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Telemetry.cs:25 — #pragma warning disable 1591 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
D2 · Cognitive Complexity · Index.OnPost (cognitive 27) · ×1
  • Index.OnPost (cognitive 27) src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Login/Index.cshtml.cs:60 — Index.OnPost has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · HttpHelper.CreateAndSendRequestAsync (cognitive 18) · ×1
  • HttpHelper.CreateAndSendRequestAsync (cognitive 18) src/PlainBridge.Client/src/PlainBridge.Client.Application/Helpers/Http/HttpHelper.cs:12 — HttpHelper.CreateAndSendRequestAsync has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Index.OnPost (cognitive 18) · ×1
  • Index.OnPost (cognitive 18) src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Create/Index.cshtml.cs:37 — Index.OnPost has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ApiResponseService.handleResponse (cognitive 17) · ×1
  • ApiResponseService.handleResponse (cognitive 17) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/api-response.service.ts:18 — ApiResponseService.handleResponse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 6 (nesting depth added 4). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 36, 59). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D23 · Boundary Type-Coupling · Cross-context type User (UserAggregate → HostAggregate) · ×1
  • Cross-context type User (UserAggregate → HostAggregate) src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:25 — User (context UserAggregate) is exposed in HostAggregate's public surface via HostApplication.User — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type User (UserAggregate → ServerAggregate) · ×1
  • Cross-context type User (UserAggregate → ServerAggregate) src/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:24 — User (context UserAggregate) is exposed in ServerAggregate's public surface via ServerApplication.User — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type ServerApplication (ServerAggregate → UserAggregate) · ×1
  • Cross-context type ServerApplication (ServerAggregate → UserAggregate) src/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:31 — ServerApplication (context ServerAggregate) is exposed in UserAggregate's public surface via User.ServerApplications — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type HostApplication (HostAggregate → UserAggregate) · ×1
  • Cross-context type HostApplication (HostAggregate → UserAggregate) src/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:32 — HostApplication (context HostAggregate) is exposed in UserAggregate's public surface via User.HostApplications — couples the contexts.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/ErrorHandling/ErrorHandler.cs:16 — src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/ErrorHandling/ErrorHandler.cs:16-47 | src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/ErrorHandling/ErrorHandler.cs:16-47 | src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/ErrorHandling/ErrorHandler.cs:16-47 | src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/ErrorHandling/ErrorHandler.cs:16-47 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (45–48 lines × 2) · ×1
  • Duplicated block (45–48 lines × 2) REDACTED.cs:54 — REDACTED.cs:54-98 | REDACTED.cs:61-108 — `REDACTED.cs` and `REDACTED.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 84 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (37–39 lines × 2) · ×1
  • Duplicated block (37–39 lines × 2) src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs:26 — src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs:26-62 | src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs:95-133 — 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/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ServerApplicationConsumer/ServerApplicationConsumerService.cs:26` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (31 lines × 4) · ×1
  • Duplicated block (31 lines × 4) src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/ErrorHandling/ErrorHandler.cs:17 — src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/ErrorHandling/ErrorHandler.cs:17-47 | src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/ErrorHandling/ErrorHandler.cs:17-47 | src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/ErrorHandling/ErrorHandler.cs:17-47 | src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/ErrorHandling/ErrorHandler.cs:17-47 — before extracting anything, compare `src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/ErrorHandling/ErrorHandler.cs` and `src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/ErrorHandling/ErrorHandler.cs` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (25 lines × 3) · ×1
  • Duplicated block (25 lines × 3) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs:25 — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs:25-49 | src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserLocallyCommand.cs:25-49 | src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/DTOs/UserRequest.cs:18-42 — before extracting anything, compare `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs` and `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserLocallyCommand.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs:24` calls `StringLength` and `src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/DTOs/UserRequest.cs:17` 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 (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Create/Index.cshtml.cs:88 — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Create/Index.cshtml.cs:88-113 | src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Login/Index.cshtml.cs:132-157 — 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/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Create/Index.cshtml.cs:88` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Login/Index.cshtml.cs:130` calls `ThrowIfNull`, `nameof` and `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Create/Index.cshtml.cs:87` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×1
  • Duplicated block (22–23 lines × 2) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs:10 — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs:10-32 | src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateServerApplicationCommand.cs:12-33 — before extracting anything, compare `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs` and `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateServerApplicationCommand.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs:10` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) REDACTED.cs:153 — REDACTED.cs:153-172 | REDACTED.cs:161-180 — before extracting anything, compare `REDACTED.cs` and `REDACTED.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED.cs:153` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `BackchannelUserLoginRequest` in one and `AuthorizationRequest` 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 (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) REDACTED.cs:67 — REDACTED.cs:67-81 | REDACTED.cs:64-78 | REDACTED.cs:74-88 — before extracting anything, compare `REDACTED.cs` and `REDACTED.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED.cs:67` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (16–18 lines × 3) · ×1
  • Duplicated block (16–18 lines × 3) src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:77 — src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:77-92 | src/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:86-102 | src/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:124-141 — 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/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.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 that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<HostApplication>` in one and `EntityTypeBuilder<ServerApplication>` 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 (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/Persistence/Data/Context/MainDbContext.cs:33 — src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/Persistence/Data/Context/MainDbContext.cs:33-46 | src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/Persistence/Data/Context/MainDbContext.cs:53-66 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) REDACTED.cs:93 — REDACTED.cs:93-107 | REDACTED.cs:101-115 — before extracting anything, compare `REDACTED.cs` and `REDACTED.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED.cs:93` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) REDACTED.cs:93 — REDACTED.cs:93-106 | REDACTED.cs:91-104 | REDACTED.cs:101-114 — before extracting anything, compare `REDACTED.cs` and `REDACTED.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED.cs:93` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ApiExternalBus/ApiExternalBusService.cs:19 — src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ApiExternalBus/ApiExternalBusService.cs:19-32 | src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/WebSocket/WebSocketService.cs:69-83 — 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/PlainBridge.Server/src/PlainBridge.Server.Application/Services/ApiExternalBus/ApiExternalBusService.cs:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs:10 — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs:10-23 | src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateServerApplicationCommand.cs:12-24 | src/PlainBridge.Shared/src/PlainBridge.Shared.Application/DTOs/ServerApplicationDto.cs:9-21 — before extracting anything, compare `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs` and `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/UpdateServerApplicationCommand.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs:10` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/PlainBridge.Shared/src/PlainBridge.Shared.Application/DTOs/ServerApplicationDto.cs:24` calls `Display` and `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Commands/CreateServerApplicationCommand.cs:24` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/DTOs/ChangeUserPasswordRequest.cs:8 — src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/DTOs/ChangeUserPasswordRequest.cs:8-20 | src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/DTOs/ChangeUserPasswordRequestDto.cs:9-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/DTOs/ChangeUserPasswordRequestDto.cs:7` calls `Display` and `src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/DTOs/ChangeUserPasswordRequest.cs:7` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) src/PlainBridge.Client/src/PlainBridge.Client.Application/Services/SharePortSocket/SharePortSocketService.cs:28 — src/PlainBridge.Client/src/PlainBridge.Client.Application/Services/SharePortSocket/SharePortSocketService.cs:28-39 | src/PlainBridge.Client/src/PlainBridge.Client.Application/Services/UsePortSocket/UsePortSocketService.cs:101-111 — 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/PlainBridge.Client/src/PlainBridge.Client.Application/Services/SharePortSocket/SharePortSocketService.cs:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs:41 — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs:41-49 | src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserLocallyCommand.cs:41-49 | src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/UpdateUserCommand.cs:13-21 | src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/DTOs/UserRequest.cs:34-42 — before extracting anything, compare `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs` and `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserLocallyCommand.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) REDACTED.cs:155 — REDACTED.cs:155-161 | REDACTED.cs:163-169 | REDACTED.cs:158-164 — before extracting anything, compare `REDACTED.cs` and `REDACTED.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED.cs:155` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `BackchannelUserLoginRequest` in one and `AuthorizationRequest` 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 (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Ciba/ViewModel.cs:15 — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Ciba/ViewModel.cs:15-24 | src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Consent/ViewModel.cs:14-23 — `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Ciba/ViewModel.cs` and `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Consent/ViewModel.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 10 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Ciba/ViewModel.cs:15` 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.
IC1 · Incompleteness & stubs · Fake-async · ×1
  • Fake-async — async method never awaits src/PlainBridge.Api/src/PlainBridge.Api.Application/Services/Token/TokenService.cs:21 — `GenerateToken` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
R10 · Code Duplication · Duplicated block (79 lines × 2 locations) · ×1
  • Duplicated block (79 lines × 2 locations) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-applications-list/host-applications-list.component.ts:25 — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-applications-list/host-applications-list.component.ts:25 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/components/server-applications-list/server-applications-list.component.ts:25 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (72 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (72 matched lines × 2 locations) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-application-form/host-application-form.component.ts:26 — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/components/host-application-form/host-application-form.component.ts:26 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/components/server-application-form/server-application-form.component.ts:30 — the two spans are one implementation copied and then locally edited — 484 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/host-application.service.ts:7 — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/host-application.service.ts:7 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/server-application.service.ts:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×1
  • Duplicated block (23 lines × 2 locations) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/host-applications-routing.module.ts:6 — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/host-applications/host-applications-routing.module.ts:6 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/features/server-applications/server-applications-routing.module.ts:6 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication · Duplicated block (21 lines × 3 locations) · ×1
  • Duplicated block (21 lines × 3 locations) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/host-application.service.ts:5 — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/host-application.service.ts:5 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/server-application.service.ts:5 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/user.service.ts:5 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (12 matched lines × 2 locations) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/components/dashboard/dashboard.component.ts:31 — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/components/dashboard/dashboard.component.ts:31 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/components/dashboard/dashboard.component.ts:45 — the two spans are one implementation copied and then locally edited — 63 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×1
  • Duplicated block (10 lines × 2 locations) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/toast.service.ts:14 — src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/toast.service.ts:14 · src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/toast.service.ts:29 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 14) · ×1
  • Complex function (anonymous) (cyclomatic 11, cognitive 14) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/api-response.service.ts:36 — (anonymous) has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R6 · Tooling · No lint script · ×1
  • No lint script — test ✓ · lint ✗ · typecheck ✓ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R7 · Dead Code · Dead file (~48 LoC) · ×1
  • Dead file (~48 LoC) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/testing/factories.ts — no import path from any entry point (2 application, 4 tooling, 13 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~40 LoC) · ×1
  • Dead file (~40 LoC) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/core/core.module.ts — no import path from any entry point (2 application, 4 tooling, 13 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~32 LoC) · ×1
  • Dead file (~32 LoC) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/testing/http-mocks.ts — no import path from any entry point (2 application, 4 tooling, 13 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~23 LoC) · ×1
  • Dead file (~23 LoC) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/testing/test-ids.ts — no import path from any entry point (2 application, 4 tooling, 13 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~1 LoC) · ×1
  • Dead file (~1 LoC) src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/shared/components/index.ts — no import path from any entry point (2 application, 4 tooling, 13 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R8 · Dependency Hygiene · Unused dependency '@faker-js/faker' · ×1
  • Unused dependency '@faker-js/faker' — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
S1 · Web-Security Posture · Token validation disabled · ×1
  • Token validation disabled src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/DependencyResolver.cs:114 — `ValidateAudience = false` means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent.
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 · Blocking `File.WriteAllText` inside an `async` method · ×1
  • Blocking `File.WriteAllText` inside an `async` method src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/Endpoints/LoginEndpoint.cs:72 — `File.WriteAllText` blocks the thread on I/O while `File.WriteAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin.
X1 · Async correctness · Blocking `MemoryStream.Write` inside an `async` method · ×1
  • Blocking `MemoryStream.Write` inside an `async` method src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/Middleware/HttpRequestProxyMiddleware.cs:180 — `MemoryStream.Write` blocks the thread on I/O while `MemoryStream.WriteAsync` exists to wait without one — inside a method that is already `async`, await the twin.
X20 · Mistyped argument guard · Argument guard throws the exception its own condition disproves · ×1
  • Argument guard throws the exception its own condition disproves src/PlainBridge.Server/src/PlainBridge.Server.Application/Services/HostApplication/HostApplicationService.cs:22 — The guard on line 21 rejects `host` and line 22 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(host)` is true of a value that is NOT null: it is satisfied by an EMPTY `host`, and on that path `host` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×1
  • Symbol treated as nullable, then dereferenced unguarded src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/Middleware/HttpRequestProxyMiddleware.cs:48 — This method contradicts itself about `hostApplication`: line 48 writes `hostApplication?.UserName`, which says `hostApplication` can be null, but line 48 then dereferences it directly as `hostApplication.InternalUrl` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `hostApplication` truly cannot be null here, the `?.` is misleading. Settle it one way — test `hostApplication` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Minor — 60 finding(s)
M4 · Documentation accuracy · README/code drift · ×9
  • README/code drift README.md:7 — README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (REDACTED and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
  • README/code drift README.md:116 — README.md runs `dotnet run --project src/PlainBridge.AppHost/PlainBridge.AppHost.csproj`, but `src/PlainBridge.AppHost/PlainBridge.AppHost.csproj` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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 README.md:137 — README.md runs `docker compose --env-file infra/.env -f infra/docker-compose.yaml up -d cache messaging elasticsearch plain-bridge-dashboard`, but `infra/docker-compose.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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 docs/project-analys.md:425 — docs/project-analys.md names `is-signing-key-0DC4B64548F26BFFF432AB5D01514AE4.json`, but no file or folder `is-signing-key-0DC4B64548F26BFFF432AB5D01514AE4.json` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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 docs/project-analys.md:626 — docs/project-analys.md names `docker-compose.yaml`, but no file or folder `docker-compose.yaml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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 src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/bootstrap/README.md:46 — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/bootstrap/README.md installs `bootstrap` (`npm install bootstrap`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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 src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/bootstrap/README.md:104 — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/bootstrap/README.md names `bootstrap.bundle.js`, but no file or folder `bootstrap.bundle.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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 src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/bootstrap/README.md:104 — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/bootstrap/README.md names `bootstrap.bundle.min.js`, but no file or folder `bootstrap.bundle.min.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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 src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/jquery/README.md:53 — src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/wwwroot/lib/jquery/README.md installs `jquery` (`npm install jquery`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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.
IC1 · Incompleteness & stubs · Commented-out code · ×7
  • Commented-out code src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/DependencyResolver.cs:125 — 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/PlainBridge.Api/src/PlainBridge.Api.Application/DependencyResolver.cs:19 — 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/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Infrastructure/Data/ApplicationDbContext.cs:22 — 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/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/SecurityHeadersAttribute.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/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/Worker.cs:17 — 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/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/Worker.cs:18 — 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/PlainBridge.Server/src/PlainBridge.Server.Application/Services/HttpRequestProxy/HttpRequestProxyService.cs:62 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
X10 · Duplicated predicate · Duplicated predicate · ×6
  • Duplicated predicate REDACTED.cs:171 — `ConsentOptions.EnableOfflineAccess && request.ValidatedResources.Resources.OfflineAccess` appears character-identically in 2 files — REDACTED.cs, REDACTED.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 REDACTED.cs:173 — `Input == null || Input.ScopesConsented.Contains(Duende.IdentityServer.IdentityServerConstants.StandardScopes.OfflineAccess)` appears character-identically in 3 files — REDACTED.cs, REDACTED.cs, REDACTED.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 REDACTED.cs:161 — `Input == null || Input.ScopesConsented.Contains(parsedScope.RawValue)` appears character-identically in 3 files — REDACTED.cs, REDACTED.cs, REDACTED.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 REDACTED.cs:149 — `Input == null || Input.ScopesConsented.Contains(x.Name)` appears character-identically in 3 files — REDACTED.cs, REDACTED.cs, REDACTED.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/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Queries/GetHostApplicationQueryHandler.cs:17 — `x.Id == request.Id && x.UserId == request.UserId` appears character-identically in 2 files — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Queries/GetHostApplicationQueryHandler.cs, src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/ServerApplication/Queries/GetServerApplicationQueryHandler.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/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommandHandler.cs:19 — `x.UserName.UserNameValue == request.UserName || x.Email.Equals(request.Email)` appears character-identically in 2 files — src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommandHandler.cs, src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserLocallyCommandHandler.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.
DM2 · Strongly-typed ids · Primitive id on a domain type · ×4
  • Primitive id on a domain type: HostApplication.UserId src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:22 — `HostApplication.UserId` is a raw `Int64` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int64`, in whatever form your language spells that.
  • Primitive id on a domain type: ServerApplication.ServerApplicationViewId src/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:16 — `ServerApplication.ServerApplicationViewId` 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: ServerApplication.UserId src/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:21 — `ServerApplication.UserId` is a raw `Int64` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int64`, in whatever form your language spells that.
  • Primitive id on a domain type: User.ExternalId src/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:24 — `User.ExternalId` 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.
D30 · Dependency Vulnerabilities · Low CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
DM5 · Encapsulated state · Mutable entity · ×3
  • Mutable entity: HostApplication src/PlainBridge.Api/src/PlainBridge.Api.Domain/HostAggregate/HostApplication.cs:15 — `HostApplication` exposes publicly writable state (AppId, Name, Domain, InternalUrl, UserId, User).
  • Mutable entity: ServerApplication src/PlainBridge.Api/src/PlainBridge.Api.Domain/ServerAggregate/ServerApplication.cs:13 — `ServerApplication` exposes publicly writable state (AppId, ServerApplicationViewId, Name, InternalPort, ServerApplicationType, UserId, and 1 more).
  • Mutable entity: User src/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:15 — `User` exposes publicly writable state (AppId, ExternalId, UserName, Email, PhoneNumber, Name, and 3 more).
X4 · Structured logging · Interpolated log message defeats structured logging · ×3
  • Interpolated log message defeats structured logging REDACTED:41 — 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/PlainBridge.Client/src/PlainBridge.Client.Application/Handler/HttpRequest/HttpRequestHandler.cs:87 — 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/PlainBridge.Client/src/PlainBridge.Client.Application/Handler/WebSocket/WebSocketHandler.cs:59 — 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.
D10 · Test Quality · Mock-dominated test · ×2
  • Mock-dominated test: InitializeConsumerAsync_ShouldDeclareQueueAndConsume src/PlainBridge.Client/tests/PlainBridge.Client.Tests/UnitTests/Services/ClientBusServiceTests.cs:28 — This test sets up 3 test doubles (for example `new Mock<IChannel>()`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: RequestServerApplicationsAsync_ShouldDeclareAndPublish_WithUsernameHeader src/PlainBridge.Client/tests/PlainBridge.Client.Tests/UnitTests/Services/ServerBusServiceTests.cs:25 — This test sets up 3 test doubles (for example `new Mock<IChannel>()`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
D30 · Dependency Vulnerabilities · Low vulnerability · ×2
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Placeholder data left in code · ×2
  • Placeholder data left in code REDACTED:37 — A placeholder e-mail address ("YasinAsadnezhad@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration.
  • Placeholder data left in code REDACTED:55 — A placeholder e-mail address ("BobSmith@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration.
R7 · Dead Code · Unused private field 'router' · ×2
  • Unused private field 'router' src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/guards/auth.guard.ts:9 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
  • Unused private field 'router' src/PlainBridge.Web/src/PlainBridge.Web.UI/src/app/services/auth.service.ts:13 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
C3 · Audit Trail · Partial audit-trail evidence · ×1
  • Partial audit-trail evidence — An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
D21 · Naming Consistency · Inconsistent spelling of the word 'Everything' in test method names. Some tests use 'EveryThing' (capital T) while others use 'EveryThin' (missing 'g'). This appears to be a typo in one instance and a casing inconsistency in others, rather than a deliberate naming convention. · ×1
  • Inconsistent spelling of the word 'Everything' in test method names. Some tests use 'EveryThing' (capital T) while others use 'EveryThin' (missing 'g'). This appears to be a typo in one instance and a casing inconsistency in others, rather than a deliberate naming convention. — Standardize to 'Everything' (lowercase 't' is standard in camelCase/PascalCase compound words, but consistency is key). Specifically, fix 'EveryThin' to 'Everything' and ensure 'EveryThing' is changed to 'Everything' if the convention is lowercase internal casing, or keep 'EveryThing' if that is the chosen style, but do not mix 'EveryThing' and 'EveryThin'. (symbols: Method: public Task PlainBridge.Client.Tests.UnitTests.Management.CacheManagementTests.SetGetServerApplicationAsync_ByUserPort_WhenEveryThinIsOk_ShouldStoreAndRetrieve(), Method: [Theory] public Task PlainBridge.Server.Tests.UnitTests.Services.HostApplicationServiceTests.GetByHostAsync_WhenEveryThingIsOk_ShouldReturnHostApplication(string), Method: [Theory] public Task PlainBridge.Api.Tests.UnitTests.Application.UseCases.ServerApplication.ServerApplicationCommandsTests.UpdateStateServerApplicationCommandHandler_WhenEveryThingIsOk_ShouldBeSucceeded(int, bool), Method: [Theory] public Task PlainBridge.Api.Tests.UnitTests.Application.UseCases.ServerApplication.ServerApplicationCommandsTests.UpdateServerApplicationCommandHandler_WhenEveryThingIsOk_ShouldBeSucceeded(PlainBridge.Api.Application.UseCases.ServerApplication.Commands.UpdateServerApplicationCommand), Method: [Fact] public Task PlainBridge.Api.Tests.UnitTests.Application.UseCases.HostApplication.HostApplicationQueriesTests.GetAllHostApplicationsQueryHandler_WhenEveryThingIsOk_ShouldReturnData(), Method: [Fact] public Task PlainBridge.Tests.Client.ClientTests.SendARequestToClientProject_WhenEveryThingIsOk_ShouldReturnData(), Method: [Fact] public Task PlainBridge.Api.Tests.UnitTests.Application.UseCases.ServerApplication.ServerApplicationQueriesTests.GetAllServerApplicationsQueryHandler_WhenEveryThingIsOk_ShouldReturnData(), Method: [Theory] public Task PlainBridge.Api.Tests.UnitTests.Application.UseCases.HostApplication.HostApplicationCommandsTests.UpdateStateHostApplicationCommandHandler_WhenEveryThingIsOk_ShouldBeSucceeded(int, bool), Method: [Theory] public Task PlainBridge.IdentityServer.Tests.UnitTests.Application.Services.UserServicesTests.ChangePasswordAsync_WhenChangePasswordFails_ShouldThrowApplicationException(PlainBridge.IdentityServer.EndPoint.DTOs.ChangeUserPasswordRequestDto))
D21 · Naming Consistency · Typo in the type name 'ApiApplcationUnitTestRunFixture'. The word 'Application' is misspelled as 'Applcation' in the type name itself. While this is a type name consistency issue, it affects all usages of this type. · ×1
  • Typo in the type name 'ApiApplcationUnitTestRunFixture'. The word 'Application' is misspelled as 'Applcation' in the type name itself. While this is a type name consistency issue, it affects all usages of this type. — Rename the type to 'ApiApplicationUnitTestRunFixture' to correct the spelling of 'Application'. (symbols: Field: private ApiApplcationUnitTestRunFixture PlainBridge.Api.Tests.UnitTests.Application.UseCases.User.UserCommandsTests._fixture, Field: private ApiApplcationUnitTestRunFixture PlainBridge.Api.Tests.UnitTests.Application.UseCases.ServerApplication.ServerApplicationQueriesTests._fixture)
D27 · Navigability · Pass-through layer · ×1
  • Pass-through layer src/PlainBridge.Client/src/PlainBridge.Client.Application/Management/WebSocket/WebSocketManagement.cs:9 — WebSocketManagement: all 3 public methods forward their arguments unchanged to _websocket and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _websocket directly, or give the layer a job.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
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.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 9/11 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 11, 5 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P4 · Deployment & Rollback · No rollback/health safety · ×1
  • No rollback/health safety — Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
P6 · Release Hygiene · Changelog looks stale/thin · ×1
  • Changelog looks stale/thin — The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
S1 · Web-Security Posture · OIDC metadata fetched over HTTP · ×1
  • OIDC metadata fetched over HTTP src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/DependencyResolver.cs:94 — `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path.
S1 · Web-Security Posture · Security headers incomplete · ×1
  • Security headers incomplete src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/SecurityHeadersAttribute.cs:16 — Set: Content-Security-Policy, Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−0.5 on this card.)
S1 · Web-Security Posture · Secure cookie flags not detected · ×1
  • Secure cookie flags not detected src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/DependencyResolver.cs:100 — No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.)
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 110/125 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.
X2 · Cancellation propagation · Some async methods drop the CancellationToken they accept · ×1
  • Some async methods drop the CancellationToken they accept — 2 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~3.8 `!` suppressions per 1k syntax nodes — 179 suppression(s) across the 47600 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Minor — 17 finding(s)
D19 · Documentation Quality · XML-doc coverage · ×13
  • XML-doc coverage: PlainBridge.Api.ApiEndPoint src/PlainBridge.Api/src/PlainBridge.Api.ApiEndPoint/PlainBridge.Api.ApiEndPoint.csproj — PlainBridge.Api.ApiEndPoint: 0 % XML-doc coverage (0/18).
  • XML-doc coverage: PlainBridge.Api.Application src/PlainBridge.Api/src/PlainBridge.Api.Application/PlainBridge.Api.Application.csproj — PlainBridge.Api.Application: 0 % XML-doc coverage (0/136).
  • XML-doc coverage: PlainBridge.Api.Domain src/PlainBridge.Api/src/PlainBridge.Api.Domain/PlainBridge.Api.Domain.csproj — PlainBridge.Api.Domain: 0 % XML-doc coverage (0/65).
  • XML-doc coverage: PlainBridge.Api.Infrastructure src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/PlainBridge.Api.Infrastructure.csproj — PlainBridge.Api.Infrastructure: 0 % XML-doc coverage (0/51).
  • XML-doc coverage: PlainBridge.AppHost.AppHost src/PlainBridge.AppHost/PlainBridge.AppHost.AppHost/PlainBridge.AppHost.AppHost.csproj — PlainBridge.AppHost.AppHost: 0 % XML-doc coverage (0/7).
  • XML-doc coverage: PlainBridge.AppHost.ServiceDefaults src/PlainBridge.AppHost/PlainBridge.AppHost.ServiceDefaults/PlainBridge.AppHost.ServiceDefaults.csproj — PlainBridge.AppHost.ServiceDefaults: 0 % XML-doc coverage (0/6).
  • XML-doc coverage: PlainBridge.Client.ApiEndPoint src/PlainBridge.Client/src/PlainBridge.Client.ApiEndPoint/PlainBridge.Client.ApiEndPoint.csproj — PlainBridge.Client.ApiEndPoint: 0 % XML-doc coverage (0/9).
  • XML-doc coverage: PlainBridge.Client.Application src/PlainBridge.Client/src/PlainBridge.Client.Application/PlainBridge.Client.Application.csproj — PlainBridge.Client.Application: 0 % XML-doc coverage (0/64).
  • XML-doc coverage: PlainBridge.IdentityServer.EndPoint src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/PlainBridge.IdentityServer.EndPoint.csproj — PlainBridge.IdentityServer.EndPoint: 4 % XML-doc coverage (12/316).
  • XML-doc coverage: PlainBridge.Server.ApiEndPoint src/PlainBridge.Server/src/PlainBridge.Server.ApiEndPoint/PlainBridge.Server.ApiEndPoint.csproj — PlainBridge.Server.ApiEndPoint: 0 % XML-doc coverage (0/14).
  • XML-doc coverage: PlainBridge.Server.Application src/PlainBridge.Server/src/PlainBridge.Server.Application/PlainBridge.Server.Application.csproj — PlainBridge.Server.Application: 0 % XML-doc coverage (0/59).
  • XML-doc coverage: PlainBridge.Shared.Application src/PlainBridge.Shared/src/PlainBridge.Shared.Application/PlainBridge.Shared.Application.csproj — PlainBridge.Shared.Application: 0 % XML-doc coverage (0/81).
  • XML-doc coverage: PlainBridge.Shared.Domain src/PlainBridge.Shared/src/PlainBridge.Shared.Domain/PlainBridge.Shared.Domain.csproj — PlainBridge.Shared.Domain: 27 % XML-doc coverage (6/22).
D10 · Test Quality · Mock framework · ×4
  • Mock framework: Moq — PlainBridge.Api.Tests references Moq.
  • Mock framework: Moq — PlainBridge.Client.Tests references Moq.
  • Mock framework: Moq — PlainBridge.IdentityServer.Tests references Moq.
  • Mock framework: Moq — PlainBridge.Server.Tests references Moq.

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-67f8252da30d4f5d90703137e410a26d/history.json --exit-code 0 --source .0artifacts/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-67f8252da30d4f5d90703137e410a26d/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .29artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list PlainBridge.slnx package --vulnerable --include-transitive --format json46artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .4artifacts/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. semgrep could not parse 49 file(s) — `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/CreateHostApplicationCommandHandler.cs`, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/DeleteHostApplicationCommandHandler.cs`, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateHostApplicationCommandHandler.cs`, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Commands/UpdateStateHostApplicationCommandHandler.cs`, `src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/HostApplication/Queries/GetAllHostApplicationsQueryHandler.cs`, … (+44 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.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—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious 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 01a161c3-4090-7fa2-b342-d1e6c5ff046c · 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 — 15 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Email — 8 field(s)
  • UserDto.Email src/PlainBridge.Api/src/PlainBridge.Api.Application/DTOs/UserDto.cs:10
  • CreateUserCommand.Email src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs:34
  • CreateUserLocallyCommand.Email src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserLocallyCommand.cs:34
  • User.Email src/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:26
  • UserRequest.Email src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/DTOs/UserRequest.cs:27
  • UserRequestDto.Email src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/DTOs/UserRequestDto.cs:28
  • InputModel.Email src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/Pages/Account/Create/InputModel.cs:14
  • UserProfileViewDto.Email src/PlainBridge.Shared/src/PlainBridge.Shared.Application/DTOs/UserProfileViewDto.cs:13
Phone — 7 field(s)
  • UserDto.PhoneNumber src/PlainBridge.Api/src/PlainBridge.Api.Application/DTOs/UserDto.cs:11
  • CreateUserCommand.PhoneNumber src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserCommand.cs:39
  • CreateUserLocallyCommand.PhoneNumber src/PlainBridge.Api/src/PlainBridge.Api.Application/Features/User/Commands/CreateUserLocallyCommand.cs:39
  • User.PhoneNumber src/PlainBridge.Api/src/PlainBridge.Api.Domain/UserAggregate/User.cs:27
  • UserRequest.PhoneNumber src/PlainBridge.Api/src/PlainBridge.Api.Infrastructure/DTOs/UserRequest.cs:32
  • UserRequestDto.PhoneNumber src/PlainBridge.IdentityServer/src/PlainBridge.IdentityServer.EndPoint/DTOs/UserRequestDto.cs:33
  • UserProfileViewDto.PhoneNumber src/PlainBridge.Shared/src/PlainBridge.Shared.Application/DTOs/UserProfileViewDto.cs:11

Issues: 127 · Warnings: 193 · Recommendations: 60 · Info: 17 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 03:59 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