shortlink-org/shortlink

Executive summary

shortlink-org/shortlink scores 51 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged. The project hasn't declared a stable release yet, so its lenses are rated against a lower bar than a released product's, while the score itself is worked out as for any repository.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 35 and is rated Weak. Its REDACTED Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 6 Leaked secret finding(s) in REDACTED Scanning and to resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 51 to about 64.

141 findings are critical: 70 in Dependency Vulnerabilities, 45 in Secrets (history), seven in Static Analysis (SAST), six in IaC & Container Security, six in REDACTED Scanning, three in Forms & labels, one in Aggregate boundaries, one in Circular Imports, one in Dependency Hygiene and one in Page structure.

Watchdog couldn't measure 11 dimensions in this code, among them Test Reliability, Navigability and Data Protection, so they are left out of the score. The product code is 24,641 lines, which would take an estimated 0.3 person-years, around €48,000, to rebuild.

Code Health 68 Strong Architecture 74 Strong Maturity 59 Adequate, capped by Documentation accuracy Production Readiness 35 Weak, capped by REDACTED Scanning, Test Coverage, Dependency Hygiene and DR & Backup Security and Compliance 72 Adequate, capped by Secrets (history), Static Analysis (SAST), Dependency Vulnerabilities and IaC & Container Security Domain Modelling 81 Strong Event-Driven 100 ★ Exemplary Accessibility 64 Adequate Performance 83 Strong

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Production Readiness 35 · counts for 45%Maturity 59 · counts for 25%Accessibility 64 · counts for 14%Code Health 68 · counts for 8%Security and Compliance 72 · counts for 4%Architecture 74 · counts for 2%Domain Modelling 81 · counts for 1%Performance 83 · counts for 1%Event-Driven 100 · counts for 0%

If Production Readiness rose from 35 to 70, the lowest score rated Strong, the score would rise from 51 to about 64.

Code composition: what the lines of code are

Product code 78%Tests 22%

New since the last survey: 84 findings

These 84 critical or serious findings weren't in the previous survey, on 8 October 2026.

REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Large Files · boundaries/ui/src/app/add-link/page.tsx: 428 lines of code boundaries/ui/src/app/add-link/page.tsx
Visual & motion safety · Focus outline removed in CSS without a :focus replacement boundaries/ui/playwright-report/index.html
Visual & motion safety · Focus outline removed in CSS without a :focus replacement boundaries/ui/playwright-report/index.html
Visual & motion safety · Focus outline removed in CSS without a :focus replacement boundaries/ui/playwright-report/index.html
Visual & motion safety · Focus outline removed in CSS without a :focus replacement boundaries/ui/playwright-report/index.html
Visual & motion safety · Focus outline removed in CSS without a :focus replacement boundaries/ui/playwright-report/index.html
Visual & motion safety · Focus outline removed inline boundaries/ui/src/app/not-found.tsx
Visual & motion safety · Focus outline removed inline boundaries/ui/src/components/Profile/Profile.tsx
Visual & motion safety · Focus outline removed in CSS without a :focus replacement boundaries/ui/src/public/assets/styles.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement boundaries/ui/src/app/globals.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement boundaries/ui/src/app/globals.css
Visual & motion safety · Animation without a prefers-reduced-motion guard boundaries/ui/src/public/assets/styles.css

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

Fixed since the last survey: 121 findings

These 121 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one. The first 100 are listed here.

Secrets (history) · REDACTED: REDACTED REDACTED
Secrets (history) · REDACTED: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: GO-2026-5841 REDACTED
Dependency Vulnerabilities · Medium CVE: GO-2026-5841 REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Test Coverage · No test reaches this file boundaries/proxy/src/infrastructure/permissions.ts
Test Coverage · No test reaches this file boundaries/ui/src/store/reducers/link.ts
Test Coverage · No test reaches this file boundaries/ui/src/app/faq/page.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/Page/admin/user/linksTable.tsx
Test Coverage · No test reaches this file boundaries/ui/src/lib/datalayer/queries.ts
Test Coverage · No test reaches this file boundaries/ui/src/infrastructure/http/link/linkHttpGateway.ts
Test Coverage · No test reaches this file boundaries/ui/src/components/common/PasswordInput.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/user/audit/page.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/Page/admin/directoryTable.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/PriceTable/PriceTable.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/Skeleton/ProfileSkeleton.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/async/AsyncForm.tsx
Test Coverage · No test reaches this file boundaries/ui/src/app/privacy/page.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/PushNotificationLayout.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/async/AsyncButton.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/async/DeferredSearch.tsx
Test Coverage · No test reaches this file boundaries/chrome-extension/entrypoints/popup/App.tsx
Test Coverage · No test reaches this file boundaries/proxy/src/infrastructure/observability/RequestContext.ts
Test Coverage · No test reaches this file boundaries/ui/src/components/Navigation/NavigationProgress.tsx
Test Coverage · No test reaches this file boundaries/ui/src/app/page.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/Header/NavbarSearch.tsx
Test Coverage · No test reaches this file boundaries/ui/src/contexts/SessionContext.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/SessionWrapper.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/widgets/Orders.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/Header/ActiveLink.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/ThemeToggle/ThemeToggle.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/Header/ActiveIcon.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/Skeleton/LinksTableSkeleton.tsx
Test Coverage · No test reaches this file boundaries/common/script/kube-secret-fetcher/index.js
Test Coverage · No test reaches this file boundaries/ui/src/components/Profile/Welcome.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/user/security/page.tsx
Test Coverage · No test reaches this file boundaries/chrome-extension/entrypoints/background.ts
Test Coverage · No test reaches this file boundaries/ui/src/app/not-found.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/Landing/landing-stats.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/PriceTable/PricingToggle.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/common/LoadingSpinner.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/widgets/oAuthServices.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/user/dashboard/page.tsx
Test Coverage · No test reaches this file boundaries/ui/src/store/store.ts
Test Coverage · No test reaches this file boundaries/mobile/tools/scripts/eas-build-pre-install.mjs
Test Coverage · No test reaches this file boundaries/ui/src/components/Landing/Ready.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/common/SuccessAlert.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/Header/nav-items.ts
Test Coverage · No test reaches this file boundaries/mobile/tools/scripts/eas-build-post-install.mjs
Test Coverage · No test reaches this file boundaries/ui/src/components/Footer/Footer.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/Navigation/TransitionLink.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/Landing/landing-open-source.tsx
Test Coverage · No test reaches this file boundaries/ui/src/store/actions/link.ts
Test Coverage · No test reaches this file boundaries/ui/src/store/reducers/session.ts
Test Coverage · No test reaches this file boundaries/ui/src/public/firebase-messaging-sw.js
Test Coverage · No test reaches this file boundaries/ui/src/store/types/link.ts
Test Coverage · No test reaches this file boundaries/ui/src/components/Header/LogoSquare.tsx
Test Coverage · No test reaches this file boundaries/proxy/src/infrastructure/http/swagger/generate-openapi.ts
Test Coverage · No test reaches this file boundaries/proxy/src/telemetry-init.ts
Test Coverage · No test reaches this file boundaries/ui/src/components/Copyright.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/Footer/FooterNavLink.tsx
Test Coverage · No test reaches this file boundaries/ui/src/components/common/ErrorAlert.tsx
Test Coverage · No test reaches this file boundaries/ui/src/lib/app-base-path.ts
Test Coverage · No test reaches this file boundaries/ui/src/lib/time.ts
Test Coverage · No test reaches this file boundaries/ui/src/components/widgets/Title.tsx
Test Coverage · No test reaches this file boundaries/ui/src/pkg/sdk.ts
Test Coverage · No test reaches this file boundaries/ui/src/lib/filterLinksTable.ts
Test Coverage · No test reaches this file boundaries/proxy/src/infrastructure/profiling.ts

Rebuild cost: about €48,000 · Estimate

Cost to rebuild	€16,000 to €80,000, for 264 to 838 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem	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 51. 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.
Size	Medium: 24,641 lines of product code

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

Top priorities

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

Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.

Raises the score by about 13 points · Low effort · REDACTED Scanning

Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.

Raises the score by about 6 points · Low effort · Dependency Hygiene

Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.

Raises the score by about 5 points · Medium effort · DR & Backup

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 €48,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 35 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts

What to do: Start with the Production Readiness actions in Top priorities.

If you do one thing first · First action

Resolve the 6 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 13 points for low effort, because it clears the 6 REDACTED Scanning findings. The next survey will show the change in the score.

Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

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.

245 modules, with 218 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 205 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 boundaries.proxy.src.application.exceptions.ApplicationError	2 boundaries.proxy.src.application.pipeline.IUseCaseInterceptor	3 boundaries.proxy.src.domain.entities.Hash	4 boundaries.proxy.src.domain.interfaces.IMessageBus	5 boundaries.proxy.src.infrastructure.logging.ILogger	6 boundaries.proxy.src.infrastructure.metrics.IGrpcMetrics	7 boundaries.proxy.src.infrastructure.tracing.IGrpcTracing	10 github.com/shortlink-org/shortlink/boundaries/link/internal/domain/link/v1	11 github.com/shortlink-org/shortlink/boundaries/metadata/internal/usecases/parsers	12 github.com/shortlink-org/shortlink/boundaries/metadata/internal/usecases/screenshot	13 boundaries.proxy.src.application.pipeline.AuthorizationInterceptor	14 boundaries.proxy.src.application.pipeline.LoggingInterceptor	15 boundaries.proxy.src.domain.entities.Link	17 github.com/shortlink-org/shortlink/boundaries/link/internal/infrastructure/repository/cqrs/cqs	18 github.com/shortlink-org/shortlink/boundaries/link/internal/infrastructure/repository/cqrs/query	19 github.com/shortlink-org/shortlink/boundaries/link/internal/infrastructure/repository/crud	20 github.com/shortlink-org/shortlink/boundaries/metadata/internal/usecases/metadata	21 boundaries.proxy.src.application.dto.GetLinkResponse	22 boundaries.proxy.src.domain.events.LinkEvents	23 boundaries.proxy.src.domain.repositories.ILinkRepository	24 boundaries.proxy.src.infrastructure.adapters.ILinkServiceAdapter	25 boundaries.proxy.src.infrastructure.cache.RedisLinkCache	26 github.com/shortlink-org/shortlink/boundaries/link/internal/usecases/link	27 github.com/shortlink-org/shortlink/boundaries/link/internal/usecases/link_cqrs	28 github.com/shortlink-org/shortlink/boundaries/metadata/internal/infrastructure/rpc/metadata/v1	30 boundaries.proxy.src.application.use-cases.GetLinkByHashUseCase	31 boundaries.proxy.src.application.use-cases.PublishEventUseCase	36 boundaries.proxy.src.application.services.LinkApplicationService	39 boundaries.proxy.src.infrastructure.http.fastify.controllers.ProxyController
1 boundaries.proxy.src.application.exceptions.ApplicationError
2 boundaries.proxy.src.application.pipeline.IUseCaseInterceptor
3 boundaries.proxy.src.domain.entities.Hash
4 boundaries.proxy.src.domain.interfaces.IMessageBus
5 boundaries.proxy.src.infrastructure.logging.ILogger
6 boundaries.proxy.src.infrastructure.metrics.IGrpcMetrics
7 boundaries.proxy.src.infrastructure.tracing.IGrpcTracing
8 boundaries.ui.src.components.common
9 boundaries.ui.src.domain.link.link_types
10 github.com/shortlink-org/shortlink/boundaries/link/internal/domain/link/v1
11 github.com/shortlink-org/shortlink/boundaries/metadata/internal/usecases/parsers
12 github.com/shortlink-org/shortlink/boundaries/metadata/internal/usecases/screenshot
13 boundaries.proxy.src.application.pipeline.AuthorizationInterceptor	1	4			1
14 boundaries.proxy.src.application.pipeline.LoggingInterceptor		2			1
15 boundaries.proxy.src.domain.entities.Link			1
16 boundaries.proxy.src.infrastructure.adapters.connect.interceptors					2	1	1
17 github.com/shortlink-org/shortlink/boundaries/link/internal/infrastructure/repository/cqrs/cqs								2
18 github.com/shortlink-org/shortlink/boundaries/link/internal/infrastructure/repository/cqrs/query								2
19 github.com/shortlink-org/shortlink/boundaries/link/internal/infrastructure/repository/crud								6
20 github.com/shortlink-org/shortlink/boundaries/metadata/internal/usecases/metadata									2	2
21 boundaries.proxy.src.application.dto.GetLinkResponse													1
22 boundaries.proxy.src.domain.events.LinkEvents			4										2
23 boundaries.proxy.src.domain.repositories.ILinkRepository			1										1
24 boundaries.proxy.src.infrastructure.adapters.ILinkServiceAdapter			1										1
25 boundaries.proxy.src.infrastructure.cache.RedisLinkCache			2		1								2
26 github.com/shortlink-org/shortlink/boundaries/link/internal/usecases/link								3								2
27 github.com/shortlink-org/shortlink/boundaries/link/internal/usecases/link_cqrs								1						2	2
28 github.com/shortlink-org/shortlink/boundaries/metadata/internal/infrastructure/rpc/metadata/v1									2	2							2
29 boundaries.proxy.src.application.handlers.IEventHandler																			1
30 boundaries.proxy.src.application.use-cases.GetLinkByHashUseCase																		1		1
31 boundaries.proxy.src.application.use-cases.PublishEventUseCase																			2
32 boundaries.proxy.src.infrastructure.adapters.LinkServiceConnectAdapter			1		1	1	1						1								1
33 boundaries.proxy.src.infrastructure.repositories.LinkServiceRepository			1		1								1							1	1	1
34 github.com/shortlink-org/shortlink/boundaries/link/internal/di														2	2	3							2	2
35 github.com/shortlink-org/shortlink/boundaries/metadata/internal/di									2	1															2
36 boundaries.proxy.src.application.services.LinkApplicationService			1		1							1	1					1								1	1
37 boundaries.proxy.src.infrastructure.messaging.AMQPEventPublisher				1	1														1								1
38 boundaries.proxy.src.infrastructure.messaging.KafkaEventPublisher				1	1														1								1
39 boundaries.proxy.src.infrastructure.http.fastify.controllers.ProxyController					1																							1
40 boundaries.proxy.src.di.container				1	1	1	1				2	1								1	1	1				1	2	1	1

Uses a module listed above itPart of a loopThe module itself

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

The Good

D1 · Go Cyclomatic Complexity 8.0 D2 · Go Cognitive Complexity 7.6 D3 · Go God Classes 7.7 D4 · Go Code Duplication 9.5 D17 · Go Explicit Debt 9.8 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 8.3 R1 · React / TS Type Safety 9.7 R10 · React / TS Code Duplication 9.1 R2 · React / TS Cyclomatic Complexity 9.9 R3 · React / TS Large Files 9.8 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 7.3 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 7.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 7.9 X30 · Repo Support guard that admits what it rejects 10.0 X5 · Repo Nullable reference types 7.5

The Bad

R7 · React / TS Dead Code 4.7 X4 · Repo Structured logging 6.1

At a glance — Architecture · 74% · Strong ·

The Good

D5 · Go Coupling 9.4 D6 · Go Cohesion (LCOM4) 9.7 D7 · Go Architectural Integrity 10.0 D22 · Go Internal API Consistency 10.0 D23 · Go Boundary Type-Coupling 10.0 D26 · Go Project Cohesion 8.8 D35 · Go Change Coupling 10.0 AX2 · Repo Stateful singletons 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0 R9 · React / TS Circular Imports 8.3

The Bad

AX10 · Repo Code composition 5.8

The Ugly

R11 · React / TS Import Boundaries 4.5

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

The Good

D15 · Go Churn × Complexity Hotspots 10.0 D19 · Go Documentation Quality 8.1 D20 · Go ADR Quality 7.6 D21 · Go Naming Consistency 10.0 D25 · Go ADR Conformance 10.0 D34 · Go Knowledge Freshness 10.0 M1 · Repo Documentation (README) 6.5 M2 · Repo Architecture documentation 10.0 M3 · Repo Folder & project structure 10.0

The Ugly

M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 35% · Weak · gated by D13, R4, R8, P5 ·

The Good

D9 · Go Test Distribution 9.1 D10 · Go Test Quality 9.9 D14 · Go License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P2 · Repo Observability 9.7 P3 · Repo Security & performance tooling 10.0 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 P8 · Repo Schema migrations 10.0 R5 · React / TS Dependency Freshness 9.9 R6 · React / TS Tooling 10.0

The Bad

D12 · Go Dependency Hygiene 4.6

The Ugly

D13 · Go REDACTED Scanning 0.0 P5 · Repo DR & Backup 0.0 R4 · React / TS Test Coverage 3.5 R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 72% · Adequate · gated by D28, D29, D30, D31 ·

The Good

D32 · Go Data Compliance (PII/GDPR) 9.0 D36 · Go Supply-chain Provenance & Signing 7.5 D37 · Go Vulnerability-disclosure Policy 10.0 D43 · Go Malicious Dependencies 10.0 D44 · Go Platform End-of-Life 10.0 S1 · Repo Web-Security Posture 9.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0

The Ugly

D28 · Go Secrets (history) 0.0 D29 · Go Static Analysis (SAST) 1.9 D30 · Go Dependency Vulnerabilities 0.0 D31 · Go IaC & Container Security 3.6 X24 · Repo Document value interpolated into markup unescaped 3.5

At a glance — Domain Modelling · 81% · Strong ·

The Good

DM10 · Repo One transaction, one aggregate 10.0 DM11 · Repo Constructible invalid state 10.0 DM4 · Repo Rich vs anemic model 7.7 DM5 · Repo Encapsulated state 10.0 DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM7 · Repo Repository granularity 10.0 DM9 · Repo Scattered domain decisions 10.0

The Bad

DM1 · Repo Aggregate boundaries 5.2

At a glance — Event-Driven · 100% · Exemplary ·

The Good

ED1 · Repo Handler temporal coupling 10.0 ED3 · Repo Event naming 7.0 ED4 · Repo Outbox / dual-write 10.0

At a glance — Accessibility · 64% · Adequate ·

The Good

AC1 · Repo Text alternatives 10.0 AC3 · Repo Page structure 7.1 AC4 · Repo Keyboard semantics 10.0 AC5 · Repo ARIA correctness 10.0

The Bad

AC2 · Repo Forms & labels 5.5 AC6 · Repo Visual & motion safety 4.5 AC7 · Repo A11y enforcement 6.0

At a glance — Performance · 83% · Strong ·

The Good

PF1 · Repo Benchmark discipline 9.5 PF3 · Repo Async & latency hygiene 10.0

The Bad

PF2 · Repo Allocation hygiene 6.4

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 category	Findings	Severity
A03:2025 — Software Supply Chain Failures	126	High / Critical
A07:2025 — Authentication Failures	52	High / Critical
A02:2025 — Security Misconfiguration	52	High / Critical
A05:2025 — Injection	19	High / Critical
A01:2025 — Broken Access Control	1	Medium

Roadmap

Immediately resolve the six leaked secrets in configuration files and pin the single stale dependency to ensure baseline security and stability. Strengthen operational resilience by codifying backup and geo-recovery procedures in infrastructure-as-code, while cleaning up the dependency tree by removing unused packages and explicitly declaring imports. Finally, reconcile the documentation to eliminate broken links and ensure all guides accurately reflect the current repository structure.

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

Do this	Helps	Effort	Dimension
Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.	+13.2 pts	Low	REDACTED Scanning
Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.	+6.0 pts	Low	Dependency Hygiene
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.	+5.5 pts	Medium	DR & Backup
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+5.5 pts	Medium	Dependency Hygiene
Reconcile the README with reality: REDACTED links to `./ops/docs/ADR/README.md`, but `ops/docs/ADR/README.md` does not exist; boundaries/README.md links to `./docs/ADR/README.md`, but `boundaries/docs/ADR/README.md` does not exist; boundaries/api/README.md links to `./boundaries/api/api-gateway/README.md`, but `boundaries/api/boundaries/api/api-gateway/README.md` does not exist; boundaries/api/README.md links to `./boundaries/api/api-gateway/gateways/ws/README.md`, but `boundaries/api/boundaries/api/api-gateway/gateways/ws/README.md` does not exist; boundaries/api/README.md links to `./docs/ADR/README.md`, but `boundaries/api/docs/ADR/README.md` does not exist.	+2.5 pts	Medium	Documentation accuracy
Add tests that import the unreached modules (directly or through their public entry).	+2.5 pts	Medium	Test Coverage
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.	+1.8 pts	Medium	Documentation (README)
Improve Documentation Quality — currently 8.1/10.	+1.5 pts	Medium	Documentation Quality

File quality

Per-file score 0–10 — a quality signature. Of 170 files carrying findings, judged against the Preview bar: 4% slop · 20% mixed · 76% near-clean.

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	0.2	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	0.6	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	1.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	1.7	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	1.9	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	3.0	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	3.5	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	4.1	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	4.1	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	4.4	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	4.4	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	4.4	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	4.4	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	4.6	Mixed	Data Compliance (PII/GDPR): Medium: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	5.1	Mixed	Secrets (history): High secret: REDACTED
REDACTED	5.1	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	5.1	Mixed	IaC & Container Security: High IaC: REDACTED
boundaries/api/api-gateway/gateways/cloudevents/cmd/api.go	6.0	Mixed	Explicit Debt: TodoComment

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

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

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

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

Could not be resolved — 11

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. 102 of 109 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 7 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 109 dimensions across the health lenses

D1D2D3D4D5D6D7D9D10D12D13D14D15D17D19D20D21D22D23D25D26D28D29D30D31D32D34D35D36D37D43D44AC1AC2AC3AC4AC5AC6AC7AX10AX2AX3AX4AX5AX6AX8DM1DM10DM11DM4DM5DM6DM7DM9ED1ED3ED4GD1IC1M1M2M3M4P1P10P2P3P4P5P6P8PF1PF2PF3R1R10R11R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X28X29X3X30X4X5

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

How to trust any code-health report — three questions

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

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

Tools & methods

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

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.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 measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a163da-a1fe-78f6-8632-2870176eab2e.

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.

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 158 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 38 test source file(s) (.go) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a 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 MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for boundaries/proxy/ could not reach buf.build, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://buf.build/gen/npm/v1/@buf/shortlink-org_shortlink-link-link.bufbuild_es/-/shortlink-org_shortlink-link-link.bufbuild_es-2.11.0-2…), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
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 for the vitest suite in boundaries/proxy/ was NOT MEASURED: the dependency install for boundaries/proxy/ could not reach buf.build, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://buf.build/gen/npm/v1/@buf/shortlink-org_shortlink-link-link.bufbuild_es/-/shortlink-org_shortlink-link-link.bufbuild_es-2.11.0-2…), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
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 for the vitest suite in boundaries/ui/ was NOT MEASURED: the dependency install for boundaries/ui/ could not reach gitlab.com, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403 GET https://gitlab.com/api/v4/projects/72693539/packages/npm/@shortlink-org/eslint-plugin-shortlink/-/@shortlink-org/eslint-plugin-shortlink…), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
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 for the jest suite in boundaries/mobile/ was NOT MEASURED: the jest run in boundaries/mobile/ produced no per-test report (Error: Jest: Failed to parse the TypeScript config file boundaries/mobile/jest.config.ts). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
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-maintainer repository — bus factor is not applicable (3 contributor(s) across 20000 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 2 hold 0.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D29 Static Analysis (SAST) — 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. Not read: `boundaries/ui/node_modules/.pnpm/@heroicons+react@2.2.0_react@19.2.4/node_modules/`, `boundaries/ui/node_modules/.pnpm/@tanstack+react-virtual@3.14.10_react-dom@19.2.4_react@19.2.4__react@19.2.4/node_modules/`, `boundaries/ui/node_modules/.pnpm/@react-aria+interactions@3.28.1_react-dom@19.2.4_react@19.2.4__react@19.2.4/node_modules/`, `boundaries/ui/node_modules/.pnpm/use-sync-external-store@1.6.0_react@19.2.4/node_modules/`, `boundaries/ui/node_modules/.pnpm/react-stately@3.49.0_react@19.2.4/node_modules/`, … (+801 more). The rule's absence of rows there is not evidence of anything.
D30 Dependency Vulnerabilities — 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 scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; npm was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that npm is free of known-vulnerable dependencies.
D43 Malicious Dependencies — 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 scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; npm was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that npm is free of known-vulnerable dependencies.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Awilix, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (docker-compose.yaml). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — time="2026-10-22T13:47:31Z" level=warning msg="The \"DOCKER_NETWORK\" variable is not set. Defaulting to a blank string." no service selected; runtime evidence skipped.
C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
DM9 Scattered domain decisions — 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
R4 Test Coverage — 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. 76 further occurrence(s) are not listed individually; the score already reflects all 116.
R7 Dead Code — 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. 40 further occurrence(s) are not listed individually; the score already reflects all 80.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations: 13 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
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.
D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
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.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
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 (REDACTED, 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.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
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.
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.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (7): D19, D20, D21, D22, D25, D26, 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 Complexity8.0 / 10Strong✓ 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 8.0 / 10 · rule-coverage 100% · ceiling Prevented

11 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was page.Page at 43. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being link.mainReducer at 20 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: boundaries/ui/src/store/reducers/link.ts (link.mainReducer at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

page.Page (cyclomatic 43)boundaries/ui/src/app/add-link/page.tsx:59

RabbitMQMessageBus.publish (cyclomatic 22)boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:193

page.Page (cyclomatic 22)boundaries/ui/src/app/admin/sitemap/page.tsx:60

link.mapStatusToResponse (cyclomatic 21)boundaries/bff/internal/infrastructure/http/controllers/link/error.go:92

HttpClient.request (cyclomatic 21)boundaries/ui/src/store/api/Api.ts:223

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

What to do

Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with page.Page (cyclomatic 43). — Refactoring it lifts Cyclomatic Complexity from 8.0 to about 8.4/10.

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

Do you agree with this assessment?

D2 · Cognitive Complexity7.6 / 10Strong✓ 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 7.6 / 10 · rule-coverage 100% · ceiling Prevented

14 method(s) exceeded the cognitive complexity threshold of 15; the worst was page.Page at 50.

page.Page (cognitive 50)boundaries/ui/src/app/add-link/page.tsx:59

UC.Add (cognitive 26)boundaries/link/internal/usecases/link/add.go:31

UseCasePipeline.execute (cognitive 24)boundaries/proxy/src/application/pipeline/UseCasePipeline.ts:21

page.Page (cognitive 24)boundaries/ui/src/app/admin/sitemap/page.tsx:60

RabbitMQMessageBus.publish (cognitive 23)boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:193

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

What to do

Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with page.Page (cognitive 50). — Refactoring it lifts Cognitive Complexity from 7.6 to about 8.2/10.

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

Do you agree with this assessment?

D3 · God Classes7.7 / 10Strong✓ 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 7.7 / 10 · rule-coverage 100% · ceiling Prevented

12 over-large unit(s) detected — types, modules or files that carry too much.

FunctionTooLong: page.Page · ×9boundaries/ui/src/app/add-link/page.tsx:59

MethodTooLong: UC.Add · ×3boundaries/metadata/internal/usecases/metadata/metadata.go:73

What to do

Resolve the 9 FunctionTooLong finding(s) in God Classes — start with page.tsx (2), Notifications.tsx, REDACTED. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 3 MethodTooLong finding(s) in God Classes — start with metadata.go, ErrorMapper.ts, add.go. — One of this dimension's main actionable groups (3 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D4 · Code Duplication9.5 / 10Stronggated by 31 serious findings✓ Tool-verified

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

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

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

29 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 2 of the 31 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .ts, .tsx (59% 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 (14 lines × 2) · ×3boundaries/link/internal/infrastructure/repository/cqrs/query/postgres/get.go:51

Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2boundaries/api/api-gateway/gateways/cloudevents/cmd/api.go:19

Duplicated block (21 lines × 2) · ×2boundaries/api/api-gateway/gateways/cloudevents/infrastructure/server/server.go:33

Duplicated block (17 lines × 2) · ×2boundaries/link/internal/infrastructure/repository/crud/mongo/mongo.go:90

Duplicated block (15 lines × 3) · ×2boundaries/api/api-gateway/gateways/cloudevents/di/wire.go:72

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

What to do

Resolve the 3 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with REDACTED, api.go, handle_add.go. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Members sharing a duplicated core (6 members, 50+ identical tokens) finding(s) in Code Duplication — start with api.go, add.go. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (21 lines × 2) finding(s) in Code Duplication — start with REDACTED, mongo.go. — One of this dimension's main actionable groups (2 warning-level).

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

Do you agree with this assessment?

D5 · Coupling9.4 / 10Stronggated by 1 serious 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 9.4 / 10 · rule-coverage 100% · ceiling Prevented

14 production modules (npm+Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 13 of the 14 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: @nx-expo-monorepo/ui

What to do

Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.7 / 10Stronggated by 1 serious finding✓ 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 9.7 / 10 · rule-coverage 100% · ceiling Verified

1 of 39 classes have LCOM4 above 3.

Low cohesion: API (LCOM4 6)boundaries/api/api-gateway/gateways/grpc-web/infrastructure/server/v1/server.go:23

What to do

Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D7 · Architectural Integrity10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

All 14 mechanizable ADR(s) are enforced: 13 by analyzers, 1 by tests. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

Checkable ADR rule enforced only by prose: 16. Adopting Domain-Driven Design (DDD) and Clean Architecture Principlesdocs/ADR/decisions/0016-use-domain-driven-developer.md

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

206 test methods: 180 unit, 12 integration, 0 BDD, 14 e2e. The JavaScript/TypeScript suite contributes 158 `it`/`test` case(s) across 29 test file(s) declaring at least one; its tier split is read from package names and paths only. The Go suite contributes 47 test case(s) across 33 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 0 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one. The Scala suite contributes 1 test case(s) across 1 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality9.9 / 10Stronggated by 1 serious finding✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 158 tests. Measured on the JavaScript/TypeScript suite only — at least 38 test source file(s) (.go) went unread, so its test quality is unmeasured and is not in these counts.

No assertions: should skip when Redis is not availableboundaries/proxy/src/infrastructure/cache/__tests__/RedisLinkCache.test.ts:325

What to do

Resolve the 1 No assertions finding(s) in Test Quality — start with RedisLinkCache.test.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D12 · Dependency Hygiene~~7.8~~ 4.6 / 10Weak✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 4.6 / 10 · rule-coverage 59% · ceiling Verified

47 outdated, 0 author-deprecated direct Go module(s), 1 pinning or checksum defect(s). 145 of 145 direct requirement(s) were graded against proxy.golang.org (0 not served there, 59 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.

Dependency pinned to a stale untagged commit: github.com/syndtr/goleveldb

Outdated: github.com/IBM/sarama · ×47

What to do

Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

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

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

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

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

6 secret(s) detected.

REDACTED

What to do

Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
Enforce REDACTED 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.

Do you agree with this assessment?

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 105 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 108 production dependency(ies) this repository's committed lockfile resolves, across 6 product REDACTED manifest(s). Its 100 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. A further 3 package(s) the lockfile resolves are not published on the public registry at all — a private scope, a workspace-internal name or a git install — and are outside this verdict. This repository publishes itself under MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

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.

Do you agree with this assessment?

D17 · Explicit Debt9.8 / 10Stronggated by 20 serious 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 9.8 / 10 · rule-coverage 100% · ceiling Prevented

20 deducted task-comment markers across 24519 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×20boundaries/api/api-gateway/gateways/cloudevents/cmd/api.go:24

What to do

Resolve the 20 TodoComment finding(s) in Explicit Debt — start with api.go (3), REDACTED (2), ws.go. — One of this dimension's main actionable groups (20 warning-level).

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

Do you agree with this assessment?

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

The repository's root README is a clear overview of the project (shortlink, microservices architecture, GDPR compliance) plus an excellent Artifact Hub badge wall and license. The boundaries/README series documents each directory as its own README (gitlab/, poc/, etc.) rather than the repository-wide docs, showing strong per-directory documentation for boundary services like Link, BFF, Proxy, and Mobile clients. All visible documents are well-structured with headings, a consistent overview, and clear usage examples; the only unshown element is an architecture/decision-documentation section that all boundaries/READMEs reference but no single document actually covers. The repository's READMEs and architecture/decision documentation are well organized with a clear directory-level focus (each README documents its own subdirectory rather than the root repo), but there is no single project overview at the top level. The ADR docs give an excellent architectural decision log (ADL) roadmap, while the C4 model, SBOMs, and Ansible/Playbook examples show real usage content. The poc/cel README gives a good POC-level example with curl and CEL code.

What to do

Improve Documentation Quality — currently 8.1/10. — The repository's root README is a clear overview of the project (shortlink, microservices architecture, GDPR compliance) plus an excellent Artifact Hub badge wall and license. The boundaries/README series documents each directory as its own README (gitlab/, poc/, etc.) rather than the repository-wide docs, showing strong per-directory documentation for boundary services like Link, BFF, Proxy, and Mobile clients. All visible documents are well-structured with headings, a consistent overview, and clear usage examples; the only unshown element is an architecture/decision-documentation section that all boundaries/READMEs reference but no single document actually covers. The repository's READMEs and architecture/decision documentation are well organized with a clear directory-level focus (each README documents its own subdirectory rather than the root repo), but there is no single project overview at the top level. The ADR docs give an excellent architectural decision log (ADL) roadmap, while the C4 model, SBOMs, and Ansible/Playbook examples show real usage content. The poc/cel README gives a good POC-level example with curl and CEL code.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D20 · ADR QualityStrong◐ Sampled · advisory

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

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

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

Evaluated 64 ADR(s) individually; mean quality 7.6/10 (mixed — many ADRs miss context or consequences). 16 flagged with a specific gap.

No context/problem framing (e.g., why tiny URLs are needed) and no consequences/trade-offs sectionboundaries/common/docs/ADR/decisions/0003-requirements.md

Context and consequences are both cited to an external source (Michael Nygard's blog + adr-tools repo), leaving the ADR itself uninformative and its own rationale buried in linksdocs/ADR/decisions/0001-record-architecture-decisions.md

No consequences/trade-offs section (e.g. added overhead of healthz endpoints)docs/ADR/decisions/0003-observability-health-check.md

Decision and consequences are cut off mid-body before the visible elements (context plus Docs) are fully showndocs/ADR/decisions/0004-use-uuid-as-primary-keys.md

Informative title (uninformative) and context are both thin: the decision is explicit but there is only one sentence stating what CODEOWNERS does ('used to define individuals or teams that are responsible for code') with no problem statement; consequences are real but trade-offs are not visible before the clipdocs/ADR/decisions/0006-codeowner.md

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

What to do

Resolve the 1 No context/problem framing (e.g., why tiny URLs are needed) and no… finding(s) in ADR Quality — start with 0003-requirements.md. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Context and consequences are both cited to an external source (Michael… finding(s) in ADR Quality — start with 0001-record-architecture-decisions.md. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No consequences/trade-offs section (e.g. added overhead of healthz… finding(s) in ADR Quality — start with 0003-observability-health-check.md. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ 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 Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D22 · Internal API ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

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

0 API inconsistencies across 2 exposed types.

✓ On the Gold path — maintain.

Detailed fixes: d22_recommendation.md.

Do you agree with this assessment?

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

No domain types leak across context boundaries (2 contexts).

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

Do you agree with this assessment?

D25 · ADR ConformanceExemplary◐ Sampled · advisory

What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.

Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.

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

8 conform / 0 violate across 64 ADRs.

✓ On the Gold path — maintain.

Detailed fixes: d25_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion8.8 / 10Strong✓ Tool-verified

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

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

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

1 of 16 build units (Go, Make, npm) flagged as possibly oversized/incoherent.

Split boundaries/ui

What to do

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

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

Do you agree with this assessment?

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

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

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

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

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

REDACTED

What to do

Resolve the 29 REDACTED finding(s) in Secrets (history) — start with REDACTED (7), REDACTED (6), REDACTED (3). — One of this dimension's main actionable groups (29 issue-level).
Resolve the 16 High secret finding(s) in Secrets (history) — start with REDACTED (7), REDACTED, REDACTED. — One of this dimension's main actionable groups (16 issue-level).
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.

Do you agree with this assessment?

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

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

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

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

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

19 finding(s): 0 critical, 7 high, 12 medium, 0 low. 1 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 32 file(s) — `.github/linters/.markdown-lint.yml`, `boundaries/bff/ops/bff/templates/authorization-policy.yaml`, `boundaries/bff/ops/bff/templates/base.yaml`, `boundaries/bff/ops/bff/templates/envoy-filter-ratelimit.yaml`, `boundaries/bff/ops/bff/templates/network/istio-plugin-shortlink.yaml`, … (+27 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. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing. The engine-authored rules could not read part of the checkout — `watchdog-identifier-read-out-of-scope-js` could not read 806 path(s) (`boundaries/ui/node_modules/.pnpm/@heroicons+react@2.2.0_react@19.2.4/node_modules/`, `boundaries/ui/node_modules/.pnpm/@tanstack+react-virtual@3.14.10_react-dom@19.2.4_react@19.2.4__react@19.2.4/node_modules/`, `boundaries/ui/node_modules/.pnpm/@react-aria+interactions@3.28.1_react-dom@19.2.4_react@19.2.4__react@19.2.4/node_modules/`, `boundaries/ui/node_modules/.pnpm/use-sync-external-store@1.6.0_react@19.2.4/node_modules/`, `boundaries/ui/node_modules/.pnpm/react-stately@3.49.0_react@19.2.4/node_modules/`, … (+801 more)) — so no absence of their rows there is evidence of anything.

REDACTED

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

What to do

Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 1 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 (1 issue-level, 0 of them charged here).

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

Do you agree with this assessment?

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

125 finding(s): 10 critical, 60 high, 49 medium, 6 low. Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. npm was not scanned (npm: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.

REDACTED

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

What to do

Resolve the 57 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (52), REDACTED (5). — One of this dimension's main actionable groups (57 issue-level).
Resolve the 10 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).

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

Do you agree with this assessment?

D31 · IaC & Container Security3.6 / 10Weak✓ 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 3.6 / 10 · rule-coverage 100% · ceiling Documented

52 finding(s): 0 critical, 6 high, 43 medium, 3 low.

REDACTED

What to do

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

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

Do you agree with this assessment?

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

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

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 119 of the 411 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.

Do you agree with this assessment?

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

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing7.5 / 10Strong✓ Tool-verified

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

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

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

3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED

What to do

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

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

Do you agree with this assessment?

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Do you agree with this assessment?

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 known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (osv). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. npm was not scanned (npm: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

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

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

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

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

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

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

Do you agree with this assessment?

AC2 · Forms & labels5.5 / 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 htmlFor>, a wrapping <label>, or aria-label. — boundaries/ui/src/components/Header/NavbarSearch.tsx:27
A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×3) — boundaries/ui/src/components/Profile/Notifications.tsx:148, boundaries/ui/src/components/Profile/Notifications.tsx:199, boundaries/ui/src/components/async/AsyncForm.tsx:74
This <label> has no htmlFor 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 htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×2) — boundaries/ui/src/components/Profile/Profile.tsx:127, boundaries/ui/src/components/Profile/Profile.tsx:169

What to do

Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.

Do you agree with this assessment?

AC3 · Page structure7.1 / 10Strong✓ Tool-verified

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

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

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

The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — boundaries/ui/playwright-report/index.html:4

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.

Do you agree with this assessment?

AC4 · Keyboard semantics10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

Do you agree with this assessment?

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.

Do you agree with this assessment?

AC6 · Visual & motion safety4.5 / 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.

`.form-control` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — boundaries/ui/playwright-report/index.html:78
`.button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — boundaries/ui/playwright-report/index.html:78
`.copy-icon` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — boundaries/ui/playwright-report/index.html:78
`.tabbed-pane-tab-strip:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — boundaries/ui/playwright-report/index.html:78
`.tabbed-pane-tab-element` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — boundaries/ui/playwright-report/index.html:78
<button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — boundaries/ui/src/app/not-found.tsx:19
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — boundaries/ui/src/components/Profile/Profile.tsx:98
`.btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — boundaries/ui/src/public/assets/styles.css:40, boundaries/ui/src/app/globals.css:169
`.btn-secondary` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — boundaries/ui/src/app/globals.css:177
`.toggleWrapper` moves (`transition: transform 0.3s ease-in-out`) 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. — boundaries/ui/src/public/assets/styles.css:54

What to do

Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.

Do you agree with this assessment?

AC7 · A11y enforcement6.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.

An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 82 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

Accessibility linting is already configured — assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.

Do you agree with this assessment?

AX10 · Code composition5.8 / 10Adequate✓ Tool-verified

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

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

DM1 · Aggregate boundaries5.2 / 10Adequate✓ 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.

`Link` references the aggregate root `Hash` directly (via `hash`) — hold its `HashId` instead. — boundaries/proxy/src/domain/entities/Link.ts:9

What to do

Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

DM4 · Rich vs anemic model7.7 / 10Strong✓ 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.

`Hash` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — boundaries/proxy/src/domain/entities/Hash.ts:7
`Link` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — boundaries/proxy/src/domain/entities/Link.ts:7

What to do

Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.

Do you agree with this assessment?

DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

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

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

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

Do you agree with this assessment?

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (TypeORM/Prisma/MikroORM/Sequelize/Mongoose) on its own declaration (active-record) couples the domain to infrastructure. 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.

Do you agree with this assessment?

DM7 · Repository granularity10.0 / 10Exemplary✓ Tool-verified

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

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

`LogEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — boundaries/proxy/src/infrastructure/logging/ILogger.ts:5
`LinkEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — boundaries/proxy/src/domain/events/LinkEvents.ts:52

What to do

Name events in the past tense — they record facts that already happened.

Do you agree with this assessment?

ED4 · Outbox / dual-write10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of 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 placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in. — boundaries/mobile/apps/shortlink/src/app/App.tsx:16

What to do

Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.

Do you agree with this assessment?

IC1 · Incompleteness & stubs8.3 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

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.

`getMetrics` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — boundaries/proxy/src/infrastructure/http/fastify/controllers/MetricsController.ts:16
`semanticEnrichmentPlugin` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — boundaries/proxy/src/infrastructure/telemetry.ts:288
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×2) — boundaries/ui/src/components/widgets/Orders.tsx:1, boundaries/ui/src/public/firebase-messaging-sw.js:1

What to do

Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.

Do you agree with this assessment?

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

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

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

26 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
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 6 of 19 project(s) that lack one — worth up to 0.6 pts.
Review the README against recent changes; refresh the parts that drifted.

Do you agree with this assessment?

M2 · Architecture documentation10.0 / 10Exemplary✓ 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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

REDACTED links to `./ops/docs/ADR/README.md`, but `ops/docs/ADR/README.md` 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. — REDACTED:44
boundaries/README.md links to `./docs/ADR/README.md`, but `boundaries/docs/ADR/README.md` 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. — boundaries/README.md:24
boundaries/api/README.md links to `./boundaries/api/api-gateway/README.md`, but `boundaries/api/boundaries/api/api-gateway/README.md` 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. — boundaries/api/README.md:20
boundaries/api/README.md links to `./boundaries/api/api-gateway/gateways/ws/README.md`, but `boundaries/api/boundaries/api/api-gateway/gateways/ws/README.md` 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. — boundaries/api/README.md:23
boundaries/api/README.md links to `./docs/ADR/README.md`, but `boundaries/api/docs/ADR/README.md` 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. — boundaries/api/README.md:28
boundaries/bff/README.md links to `./infrastructure/http/api/api.yaml`, but `boundaries/bff/infrastructure/http/api/api.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. — boundaries/bff/README.md:13
boundaries/link/README.md links to `./internal/usecases/link_sqrs/README.md`, but `boundaries/link/internal/usecases/link_sqrs/README.md` 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. — boundaries/link/README.md:29
boundaries/ui/README.md runs `docker buildx build -t next-ui -f ops/dockerfile/ui-next.Dockerfile .`, but `ops/dockerfile/ui-next.Dockerfile` 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. — boundaries/ui/README.md:57
boundaries/ui/README.md runs `npm run storybook`, but no REDACTED declares a `storybook` script. 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. — boundaries/ui/README.md:73
ops/ansible/README.md changes into `ops/vagrant`, but no such folder 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. — ops/ansible/README.md:13
boundaries/proxy/src/infrastructure/http/swagger/README.md names `src/proxy/interfaces/http/controllers/ProxyController.ts`, but no file or folder `src/proxy/interfaces/http/controllers/ProxyController.ts` 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. — boundaries/proxy/src/infrastructure/http/swagger/README.md:46

What to do

Reconcile the README with reality: REDACTED links to `./ops/docs/ADR/README.md`, but `ops/docs/ADR/README.md` does not exist; boundaries/README.md links to `./docs/ADR/README.md`, but `boundaries/docs/ADR/README.md` does not exist; boundaries/api/README.md links to `./boundaries/api/api-gateway/README.md`, but `boundaries/api/boundaries/api/api-gateway/README.md` does not exist; boundaries/api/README.md links to `./boundaries/api/api-gateway/gateways/ws/README.md`, but `boundaries/api/boundaries/api/api-gateway/gateways/ws/README.md` does not exist; boundaries/api/README.md links to `./docs/ADR/README.md`, but `boundaries/api/docs/ADR/README.md` does not exist.

Do you agree with this assessment?

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.

Do you agree with this assessment?

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

Do you agree with this assessment?

P2 · Observability9.7 / 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 8/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `boundaries/ui`.
`boundaries/proxy/src/infrastructure/telemetry.ts` reports through `console.*` at line 89 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/telemetry.ts:89
`boundaries/proxy/src/infrastructure/telemetry.ts` reports through `console.*` at line 94 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/telemetry.ts:94
`boundaries/proxy/src/infrastructure/telemetry.ts` reports through `console.*` at line 96 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/telemetry.ts:96
`boundaries/proxy/src/infrastructure/telemetry.ts` reports through `console.*` at line 250 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/telemetry.ts:250
`boundaries/proxy/src/infrastructure/telemetry.ts` reports through `console.*` at line 264 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/telemetry.ts:264
`boundaries/proxy/src/infrastructure/telemetry.ts` reports through `console.*` at line 266 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/telemetry.ts:266
`boundaries/proxy/src/infrastructure/permissions.ts` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/permissions.ts:37
`boundaries/proxy/src/infrastructure/permissions.ts` reports through `console.*` at line 77 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/permissions.ts:77
`boundaries/proxy/src/infrastructure/permissions.ts` reports through `console.*` at line 81 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/permissions.ts:81
`boundaries/proxy/src/infrastructure/permissions.ts` reports through `console.*` at line 84 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/permissions.ts:84
`boundaries/proxy/src/infrastructure/permissions.ts` reports through `console.*` at line 93 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/permissions.ts:93
`boundaries/proxy/src/infrastructure/permissions.ts` reports through `console.*` at line 95 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/permissions.ts:95
`boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 82 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/health.ts:82
`boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 120 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/health.ts:120
`boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 143 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/health.ts:143
`boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 232 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/health.ts:232
`boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 250 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/health.ts:250
`boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 262 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/health.ts:262
`boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 266 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/health.ts:266
`boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 271 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/health.ts:271
`boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 275 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/health.ts:275
`boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 277 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — boundaries/proxy/src/infrastructure/health.ts:277

What to do

Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.

Do you agree with this assessment?

P3 · Security & performance tooling10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.

What to do

Add an approval/environment gate (required reviewers / protection rules) before production promotion.

Do you agree with this assessment?

P5 · DR & Backup0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.

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

Do you agree with this assessment?

PF1 · Benchmark discipline9.5 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

Do you agree with this assessment?

PF2 · Allocation hygiene6.4 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

Raise allocation-aware density on the hot paths — currently 9 use(s) across 11,390 production line(s) (~0.8/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Go: on hot paths, reuse buffers and objects through sync.Pool, preallocate slices and maps with make([]T, 0, n) / make(map[K]V, n), size builders with Grow, append with strconv.Append*, and reslice with buf[:0] instead of allocating anew.

Do you agree with this assessment?

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.

Do you agree with this assessment?

R1 · Type Safety9.7 / 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.

Do you agree with this assessment?

R10 · Code Duplication9.1 / 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.

boundaries/proxy/src/infrastructure/messaging/KafkaMessageBus.ts:40 · boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:34 — the two spans are one implementation copied and then locally edited — 637 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. — boundaries/proxy/src/infrastructure/messaging/KafkaMessageBus.ts:40
REDACTED:135 · boundaries/ui/src/components/Profile/Profile.tsx:75 — the two spans are one implementation copied and then locally edited — 365 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. — REDACTED:135
boundaries/ui/src/app/admin/links/page.tsx:17 · boundaries/ui/src/app/links/page.tsx:17 — these 2 files are line-for-line copies of one another — 67 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — boundaries/ui/src/app/admin/links/page.tsx:17
boundaries/ui/src/components/Page/admin/user/linksTable.tsx:1 · boundaries/ui/src/components/Page/user/linksTable.tsx:1 — these 2 files are line-for-line copies of one another — 67 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — boundaries/ui/src/components/Page/admin/user/linksTable.tsx:1
boundaries/proxy/src/infrastructure/messaging/AMQPEventPublisher.ts:71 · boundaries/proxy/src/infrastructure/messaging/KafkaEventPublisher.ts:37 — the two spans are one implementation copied and then locally edited — 308 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. — boundaries/proxy/src/infrastructure/messaging/AMQPEventPublisher.ts:71
boundaries/ui/src/components/Profile/Notifications.tsx:241 · REDACTED:284 — 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. — boundaries/ui/src/components/Profile/Notifications.tsx:241
boundaries/ui/src/components/Profile/Notifications.tsx:242 · REDACTED:285 · boundaries/ui/src/components/Profile/Security.tsx:122 — 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. — boundaries/ui/src/components/Profile/Notifications.tsx:242
boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:316 · boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:358 — 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. — boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:316
boundaries/ui/src/app/faq/page.tsx:36 · boundaries/ui/src/app/privacy/page.tsx:32 — the two spans are one implementation copied and then locally edited — 182 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. — boundaries/ui/src/app/faq/page.tsx:36
boundaries/ui/src/app/admin/groups/page.tsx:79 · boundaries/ui/src/app/admin/users/page.tsx:79 — 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. — boundaries/ui/src/app/admin/groups/page.tsx:79
boundaries/ui/src/components/Header/Header.tsx:112 · boundaries/ui/src/components/Header/NavbarMobileMenu.tsx:76 — 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. — boundaries/ui/src/components/Header/Header.tsx:112
boundaries/ui/src/components/Header/ActiveIcon.tsx:11 · boundaries/ui/src/components/Header/ActiveLink.tsx:11 — the 2 copies are spread across 2 files, 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. — boundaries/ui/src/components/Header/ActiveIcon.tsx:11
boundaries/ui/src/components/Profile/Notifications.tsx:34 · boundaries/ui/src/components/Profile/Notifications.tsx:72 — all 2 copies are in the same file, 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. — boundaries/ui/src/components/Profile/Notifications.tsx:34
boundaries/ui/src/components/Dashboard/profile.tsx:127 · boundaries/ui/src/components/Dashboard/profile.tsx:144 · boundaries/ui/src/components/Dashboard/profile.tsx:161 · boundaries/ui/src/components/Dashboard/profile.tsx:178 · +1 more site(s) not listed — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — boundaries/ui/src/components/Dashboard/profile.tsx:127
boundaries/ui/src/store/sagas/link.ts:7 · boundaries/ui/src/store/sagas/link.ts:49 · boundaries/ui/src/store/sagas/link.ts:93 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — boundaries/ui/src/store/sagas/link.ts:7
boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:78 · boundaries/proxy/src/infrastructure/logging/WinstonLogger.ts:74 — the 2 copies are spread across 2 files, 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. — boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:78
boundaries/ui/src/components/Header/ProfileMenu.tsx:89 · boundaries/ui/src/components/Header/ProfileMenu.tsx:104 — all 2 copies are in the same file, 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. — boundaries/ui/src/components/Header/ProfileMenu.tsx:89
boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:270 · boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:405 — 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. — boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:270
boundaries/ui/src/components/Profile/Profile.tsx:42 · boundaries/ui/src/components/Profile/Profile.tsx:56 — 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. — boundaries/ui/src/components/Profile/Profile.tsx:42
boundaries/ui/src/lib/datalayer/api.ts:82 · boundaries/ui/src/lib/datalayer/api.ts:122 — 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. — boundaries/ui/src/lib/datalayer/api.ts:82
boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:296 · boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:345 · boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:387 — all 3 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. — boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:296
boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:65 · boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:88 — 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. — boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:65
boundaries/proxy/src/infrastructure/repositories/LinkServiceRepository.ts:51 · boundaries/proxy/src/infrastructure/repositories/LinkServiceRepository.ts:100 — 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. — boundaries/proxy/src/infrastructure/repositories/LinkServiceRepository.ts:51
boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:23 · boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:33 — 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. — boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:23
boundaries/proxy/src/application/pipeline/MetricsInterceptor.ts:44 · boundaries/proxy/src/application/pipeline/MetricsInterceptor.ts:58 — 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. — boundaries/proxy/src/application/pipeline/MetricsInterceptor.ts:44
boundaries/proxy/src/infrastructure/messaging/KafkaEventPublisher.ts:65 · boundaries/proxy/src/infrastructure/messaging/KafkaMessageBus.ts:213 · boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:281 — the 3 copies are spread across 3 files, 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. — boundaries/proxy/src/infrastructure/messaging/KafkaEventPublisher.ts:65
boundaries/proxy/src/application/pipeline/MetricsInterceptor.ts:10 · boundaries/proxy/src/infrastructure/metrics/OpenTelemetryGrpcMetrics.ts:8 — the 2 copies are spread across 2 files, 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. — boundaries/proxy/src/application/pipeline/MetricsInterceptor.ts:10
boundaries/proxy/src/infrastructure/logging/WinstonLogger.ts:175 · boundaries/proxy/src/infrastructure/logging/WinstonLogger.ts:185 — 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. — boundaries/proxy/src/infrastructure/logging/WinstonLogger.ts:175
boundaries/ui/src/app/contact/page.tsx:22 · boundaries/ui/src/components/Landing/mobile.tsx:20 — 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. — boundaries/ui/src/app/contact/page.tsx:22
boundaries/ui/src/app/admin/sitemap/page.tsx:61 · boundaries/ui/src/components/Profile/Profile.tsx:9 — 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. — boundaries/ui/src/app/admin/sitemap/page.tsx:61

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.

Do you agree with this assessment?

R11 · Import Boundaries4.5 / 10Weak✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

boundaries/proxy/src/application/exceptions/ErrorHandler.ts:5 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules. — boundaries/proxy/src/application/exceptions/ErrorHandler.ts:5
boundaries/proxy/src/application/pipeline/AuthorizationInterceptor.ts:2 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules. — boundaries/proxy/src/application/pipeline/AuthorizationInterceptor.ts:2
boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:5 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules. — boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:5
boundaries/proxy/src/application/pipeline/__tests__/AuthorizationInterceptor.test.ts:9 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules. — boundaries/proxy/src/application/pipeline/__tests__/AuthorizationInterceptor.test.ts:9
boundaries/proxy/src/application/pipeline/__tests__/LoggingInterceptor.test.ts:4 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules. — boundaries/proxy/src/application/pipeline/__tests__/LoggingInterceptor.test.ts:4
boundaries/proxy/src/application/services/LinkApplicationService.ts:14 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules. — boundaries/proxy/src/application/services/LinkApplicationService.ts:14
boundaries/proxy/src/application/services/__tests__/LinkApplicationService.test.ts:8 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules. — boundaries/proxy/src/application/services/__tests__/LinkApplicationService.test.ts:8
boundaries/ui/src/application/link/index.ts:2 imports boundaries/ui/src/infrastructure/http/link/linkHttpGateway.ts against the layered-src rules. — boundaries/ui/src/application/link/index.ts:2
boundaries/ui/src/components/Footer/Footer.tsx:6 reaches into another package with a relative path (../Copyright) — import the package by name instead. — boundaries/ui/src/components/Footer/Footer.tsx:6
boundaries/ui/src/components/index.ts:2 reaches into another package with a relative path (./Footer) — import the package by name instead. — boundaries/ui/src/components/index.ts:2
boundaries/ui/src/components/index.ts:3 reaches into another package with a relative path (./Header) — import the package by name instead. — boundaries/ui/src/components/index.ts:3
boundaries/ui/src/components/index.tsx:2 reaches into another package with a relative path (./Header) — import the package by name instead. — boundaries/ui/src/components/index.tsx:2

What to do

Fix the listed violations: respect the layer/slice order — import only through a slice's public index and never upward into a higher layer (8 rows); import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (4 rows).

Do you agree with this assessment?

R2 · Cyclomatic Complexity9.9 / 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.

publish has cyclomatic complexity 22 and cognitive complexity 23; 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. — boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:193
publish has cyclomatic complexity 19 and cognitive complexity 22; 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. — boundaries/proxy/src/infrastructure/messaging/KafkaMessageBus.ts:152
execute has cyclomatic complexity 18 and cognitive complexity 27; 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. — boundaries/proxy/src/application/pipeline/UseCasePipeline.ts:21
mapToHttpResponse has cyclomatic complexity 18 and cognitive complexity 17; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — boundaries/proxy/src/infrastructure/http/fastify/middleware/ErrorMapper.ts:45
Page has cyclomatic complexity 18 and cognitive complexity 16; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — boundaries/ui/src/app/add-link/page.tsx:59
(anonymous) has cyclomatic complexity 17 and cognitive complexity 16; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — boundaries/ui/src/store/api/Api.ts:233
ProfileMenu has cyclomatic complexity 15 and cognitive complexity 12; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — boundaries/ui/src/components/Header/ProfileMenu.tsx:16
initializeTelemetry has cyclomatic complexity 15 and cognitive complexity 11; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — boundaries/proxy/src/infrastructure/telemetry.ts:116
findByHash has cyclomatic complexity 12 and cognitive complexity 19; 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. — boundaries/proxy/src/infrastructure/repositories/LinkServiceRepository.ts:36
(anonymous) has cyclomatic complexity 12 and cognitive complexity 16; 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. — boundaries/ui/src/app/add-link/page.tsx:186
(anonymous) has cyclomatic complexity 11 and cognitive complexity 16; 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. — boundaries/proxy/src/infrastructure/adapters/connect/interceptors/RetryInterceptor.ts:99
validatePassword has cyclomatic complexity 11 and cognitive complexity 10; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — boundaries/ui/src/utils/validation.ts:54

What to do

Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.

Do you agree with this assessment?

R3 · Large Files9.8 / 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.

boundaries/ui/src/app/add-link/page.tsx has 428 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — boundaries/ui/src/app/add-link/page.tsx:1

What to do

Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.

Do you agree with this assessment?

R4 · Test Coverage3.5 / 10Weak✓ 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. (×40) — boundaries/ui/src/app/add-link/page.tsx:1, boundaries/ui/src/store/api/Api.ts:1, REDACTED:1, …

What to do

Add tests that import the unreached modules (directly or through their public entry).

Do you agree with this assessment?

R5 · Dependency Freshness9.9 / 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.

Do you agree with this assessment?

R6 · Tooling10.0 / 10Exemplary✓ 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.

Do you agree with this assessment?

R7 · Dead Code4.7 / 10Adequate✓ 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 32 application, 31 tooling and 41 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 (32 application, 31 tooling, 41 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 (×31) — boundaries/ui/src/hooks/useErrorHandler.ts, boundaries/ui/src/components/user/reports/page.tsx, boundaries/ui/src/components/user/integrations/page.tsx, …
no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/ui/src/components/user/dashboard/page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — boundaries/ui/src/components/Dashboard/profile.tsx, boundaries/ui/src/components/widgets/Orders.tsx
no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/ui/src/components/user/security/page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — boundaries/ui/src/components/Profile/Security.tsx
no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/ui/src/components/PriceTable/PriceTable.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — boundaries/ui/src/components/PriceTable/PricingToggle.tsx
no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (boundaries/ui/src/components/user/audit/page.tsx, boundaries/ui/src/components/user/integrations/page.tsx, boundaries/ui/src/components/user/reports/page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — boundaries/ui/src/components/Landing/Ready.tsx
no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/ui/src/store/actions/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — boundaries/ui/src/store/actions/link.ts
no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/proxy/src/infrastructure/http/swagger/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — boundaries/proxy/src/infrastructure/http/swagger/generate-openapi.ts
no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/ui/src/components/widgets/Orders.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — boundaries/ui/src/components/widgets/Title.tsx

What to do

Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.

Do you agree with this assessment?

R8 · Dependency Hygiene0.0 / 10Critical✓ 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.

Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. — boundaries/ui/src/types/shortlink-org-ui-kit.d.ts:3
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. (×3)
Every import is type-only — move it to devDependencies. — boundaries/proxy/src/infrastructure/telemetry.ts:26
Only test files import it (first: boundaries/mobile/apps/shortlink/src/app/App.spec.tsx:2) — move it to devDependencies. — boundaries/mobile/apps/shortlink/package.json:7

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

R9 · Circular Imports8.3 / 10Strong✓ 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.

boundaries/proxy/src/application/exceptions/ErrorHandler.ts → boundaries/proxy/src/application/exceptions/index.ts → boundaries/proxy/src/application/exceptions/ErrorHandler.ts — boundaries/proxy/src/application/exceptions/ErrorHandler.ts:4

What to do

Break each cycle by extracting the shared piece into a module both sides can import.

Do you agree with this assessment?

S1 · Web-Security Posture9.0 / 10Exemplary✓ Tool-verified

Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

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.

Set: X-Content-Type-Options, X-DNS-Prefetch-Control, X-Frame-Options. Missing: Content-Security-Policy, 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. (−1.0 on this card.) — ops/dockerfile/boundaries/platform/support/conf/nginx/default.conf:1

What to do

Add Content-Security-Policy, 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.

Do you agree with this assessment?

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X2 · Cancellation propagation7.3 / 10Strong✓ Tool-verified

Other · Code Health — Whether functions that make a cancellable request accept or pass on a context.Context or an AbortSignal (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 6/11 functions that make a cancellable request (fetch, axios, ky, ofetch; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`createLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — boundaries/ui/src/infrastructure/http/link/linkHttpGateway.ts:42, boundaries/ui/src/lib/datalayer/api.ts:96
`updateProfile` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — boundaries/ui/src/lib/datalayer/api.ts:82
`deleteLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — boundaries/ui/src/lib/datalayer/api.ts:110
`updateLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — boundaries/ui/src/lib/datalayer/api.ts:122

What to do

Thread a context.Context or an AbortSignal through functions that make requests, so the work stops when its caller gives up.

Do you agree with this assessment?

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) 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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation7.0 / 10Strong✓ Tool-verified

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.

`debug` at line 192 is called with an argument built by `Object.keys(headers)` (line 196), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — boundaries/proxy/src/infrastructure/messaging/KafkaMessageBus.ts:192

What to do

Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.

Do you agree with this assessment?

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

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

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

`JSON.stringify(jsonLd)` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — boundaries/ui/src/app/layout.tsx:114

What to do

Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

X3 · Exception handling7.9 / 10Strong✓ 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.

`if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — boundaries/api/api-gateway/gateways/ws/infrustracture/ws/ws.go:67, boundaries/bff/internal/infrastructure/http/controllers/link/error.go:66

What to do

Swallowed exception (caught, then discarded)

Do you agree with this assessment?

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.

Do you agree with this assessment?

X4 · Structured logging6.1 / 10Adequate✓ 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.

`info` at line 98 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — boundaries/proxy/src/main.ts:98
`warn` at line 32 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — boundaries/proxy/src/application/exceptions/ErrorHandler.ts:32
`error` at line 39 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — boundaries/proxy/src/application/exceptions/ErrorHandler.ts:39
`debug` at line 18 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:18
`info` at line 28 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:28
`error` at line 38 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:38
`warn` at line 58 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — boundaries/proxy/src/application/pipeline/AuthorizationInterceptor.ts:58
`warn` at line 76 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — boundaries/proxy/src/application/pipeline/AuthorizationInterceptor.ts:76

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

X5 · Nullable reference types7.5 / 10Strong✓ Tool-verified

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

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

7/10 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~0.4 `!` null assertions per 1k TypeScript source lines — 7 assertion(s) across the 16314 source line(s) of the 229 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts (4), boundaries/chrome-extension/entrypoints/popup/main.tsx (1), boundaries/proxy/src/application/handlers/EventDispatcher.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 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).

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC1 · Text alternatives	1.1.1, 1.2.2, 1.2.5	Partial signal
AC2 · Forms & labels	1.3.1, 3.3.2, 4.1.2	Partial signal
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC4 · Keyboard semantics	2.1.1, 2.4.3	Partial signal
AC5 · ARIA correctness	4.1.2	Partial signal
AC6 · Visual & motion safety	1.4.3, 2.4.7	Partial — literal CSS only
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement posture (process)

Not statically assessed — these 40 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.2, 2.1.4, 2.2.2, 2.3.1, 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.

Lens	Score	Rating	Impact
Code Health	68%	Strong	Solid.
Architecture	74%	Strong	Solid.
Maturity	59%	Adequate — gated by M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	35%	Weak — gated by D13, R4, R8, P5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	72%	Adequate — gated by D28, D29, D30, D31	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	81%	Strong	Solid.
Event-Driven	100%	Exemplary	Strongest area.
Accessibility	64%	Adequate	Acceptable, with room to improve.
Performance	83%	Strong	Solid.

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.

P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 1 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.

C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.

Not included — 29 check(s) not relevant to this codebase

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

AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — time="2026-10-22T13:47:31Z" level=warning msg="The \"DOCKER_NETWORK\" variable is not set. Defaulting to a blank string." no service selected; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .py, .rb, .scala, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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.
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in boundaries/mobile/ ran and not one test passed (Error: Jest: Failed to parse the TypeScript config file boundaries/mobile/jest.config.ts), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
ED5 Idempotency — Not assessed, and this one is on us: 5 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a Go event-sourcing framework import (watermill/eventhorizon/EventStore/eventsourcing); 3 Go aggregate(s) recording domain events (own events-slice append / raise-record)
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Go, JavaScript/TypeScript source (service entry point: REDACTED:100 (http.ListenAndServe())
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`) 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
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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.

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 — 141 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×57

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
+ 32 more in this group — see findings.md.

D28 · Secrets (history) · REDACTED · ×29

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
+ 4 more in this group — see findings.md.

D28 · Secrets (history) · High secret · ×16

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×10

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D13 · REDACTED Scanning · Leaked secret · ×6

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D31 · IaC & Container Security · High IaC · ×6

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · High vulnerability · ×3

REDACTED
REDACTED
REDACTED

AC2 · Forms & labels · <label> that labels no control · ×2

<label> that labels no control boundaries/ui/src/components/Profile/Profile.tsx:127 — This <label> has no htmlFor 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 htmlFor="<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 boundaries/ui/src/components/Profile/Profile.tsx:169 — This <label> has no htmlFor 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 htmlFor="<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

AC2 · Forms & labels · <input> without a programmatic label · ×1

<input> without a programmatic label boundaries/ui/src/components/Header/NavbarSearch.tsx: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 htmlFor>, a wrapping <label>, or aria-label.

AC3 · Page structure · <html> without a lang · ×1

<html> without a lang boundaries/ui/playwright-report/index.html:4 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

DM1 · Aggregate boundaries · Aggregate holds a reference to another aggregate · ×1

Aggregate holds a reference to another aggregate: Link.hash boundaries/proxy/src/domain/entities/Link.ts:9 — `Link` references the aggregate root `Hash` directly (via `hash`) — hold its `HashId` instead.

R8 · Dependency Hygiene · Unlisted import '@tanstack/react-table' · ×1

Unlisted import '@tanstack/react-table' boundaries/ui/src/types/shortlink-org-ui-kit.d.ts:3 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.

R9 · Circular Imports · Import cycle (2 files) · ×1

Import cycle (2 files) boundaries/proxy/src/application/exceptions/ErrorHandler.ts:4 — boundaries/proxy/src/application/exceptions/ErrorHandler.ts → boundaries/proxy/src/application/exceptions/index.ts → boundaries/proxy/src/application/exceptions/ErrorHandler.ts

Serious — 381 finding(s)

D30 · Dependency Vulnerabilities · Medium CVE · ×46

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
+ 21 more in this group — see findings.md.

D31 · IaC & Container Security · Medium IaC · ×43

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
+ 18 more in this group — see findings.md.

R4 · Test Coverage · No test reaches this file · ×40

No test reaches this file boundaries/ui/src/app/add-link/page.tsx: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 boundaries/ui/src/store/api/Api.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 REDACTED: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 boundaries/proxy/src/infrastructure/health.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 boundaries/ui/src/app/admin/sitemap/page.tsx: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 boundaries/ui/src/components/Profile/Notifications.tsx: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 boundaries/ui/src/components/Profile/Profile.tsx: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 boundaries/ui/src/hooks/useErrorHandler.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 boundaries/ui/src/components/Dashboard/profile.tsx: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 boundaries/ui/src/utils/validation.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 boundaries/ui/src/components/Header/Header.tsx: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 boundaries/ui/src/components/Profile/Security.tsx: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 boundaries/ui/src/app/providers.tsx: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 boundaries/ui/src/app/links/search/LinksSearchPageClient.tsx: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 boundaries/ui/src/components/error/ErrorBoundary.tsx: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 boundaries/ui/src/components/Header/ProfileMenu.tsx: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 boundaries/proxy/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.
No test reaches this file boundaries/ui/src/components/Landing/bento-features.tsx: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 boundaries/ui/src/lib/datalayer/api.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 boundaries/ui/src/app/admin/links/page.tsx: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 boundaries/ui/src/app/links/page.tsx: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 boundaries/ui/src/app/contact/page.tsx: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 boundaries/ui/src/components/user/reports/page.tsx: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 boundaries/ui/src/domain/link/link.errors.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 boundaries/ui/src/app/layout.tsx: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.
+ 15 more in this group — see findings.md.

D17 · Explicit Debt · TodoComment · ×20

TodoComment boundaries/api/api-gateway/gateways/cloudevents/cmd/api.go:24 — // TODO: use as helpers — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/api/api-gateway/gateways/graphql/cmd/api.go:24 — // TODO: use as helpers — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/api/api-gateway/gateways/grpc-web/cmd/api.go:24 — // TODO: use as helpers — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/api/api-gateway/gateways/ws/cmd/ws.go:15 — // TODO: use as helpers — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/bff/cmd/main.go:26 — // TODO: use as helpers — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/metadata/cmd/main.go:28 — // TODO: use as helpers — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/bff/internal/infrastructure/http/controllers/link/getLinks.go:14 — // TODO: add mapper for filter — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/link/internal/di/wire.go:207 — // TODO: refactoring. maybe drop this function — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/link/internal/infrastructure/repository/crud/dgraph/dgraph.go:142 — // TODO: Add condition — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/link/internal/infrastructure/repository/crud/postgres/postgres_test.go:25 — // TODO: research how correct close store — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:20 — // TODO: When privacy feature is implemented, usecase will check email against allowlist — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/proxy/src/infrastructure/health.ts:150 — // TODO: Add actual health checks (e.g., database connection, external services) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/proxy/src/infrastructure/repositories/LinkServiceRepository.ts:39 — // TODO: Consider cache key that includes userId for private links — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:53 — // TODO: use logger — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/ui/src/app/providers.tsx:22 — // TODO: faro has old peer dependencies, so we need to fix it before enabling it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/ui/src/app/layout.tsx:88 — // TODO: research problem with faro — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/ui/src/components/Profile/Security.tsx:46 — // TODO: Integrate with Ory Kratos API to change password — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/ui/src/components/Profile/Profile.tsx:31 — // TODO: Integrate with API to update profile — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:103 — // TODO: Integrate with Ory Kratos API to update profile — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment boundaries/ui/src/components/Profile/Notifications.tsx:19 — // TODO: Integrate with API to save notification preferences — 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.

D3 · God Classes · FunctionTooLong · ×9

FunctionTooLong: page.Page boundaries/ui/src/app/add-link/page.tsx:59 — FunctionTooLong — Page runs 300 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 200 over it, 3.00× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Notifications.Notifications boundaries/ui/src/components/Profile/Notifications.tsx:6 — FunctionTooLong — Notifications runs 253 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 153 over it, 2.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Personal.Personal REDACTED:39 — FunctionTooLong — Personal runs 239 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 139 over it, 2.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Profile.Profile boundaries/ui/src/components/Profile/Profile.tsx:7 — FunctionTooLong — Profile runs 219 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 119 over it, 2.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: profile.Index boundaries/ui/src/components/Dashboard/profile.tsx:3 — FunctionTooLong — Index runs 216 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 116 over it, 2.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: page.Page boundaries/ui/src/app/admin/sitemap/page.tsx:60 — FunctionTooLong — Page runs 180 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: bento-features.BentoFeatures boundaries/ui/src/components/Landing/bento-features.tsx:5 — FunctionTooLong — BentoFeatures runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Security.Security boundaries/ui/src/components/Profile/Security.tsx:8 — FunctionTooLong — Security runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ProfileMenu.ProfileMenu boundaries/ui/src/components/Header/ProfileMenu.tsx:16 — FunctionTooLong — ProfileMenu runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×8

Focus outline removed in CSS without a :focus replacement boundaries/ui/playwright-report/index.html:78 — `.form-control` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement boundaries/ui/playwright-report/index.html:78 — `.button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement boundaries/ui/playwright-report/index.html:78 — `.copy-icon` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement boundaries/ui/playwright-report/index.html:78 — `.tabbed-pane-tab-strip:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement boundaries/ui/playwright-report/index.html:78 — `.tabbed-pane-tab-element` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement boundaries/ui/src/public/assets/styles.css:40 — `.btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement boundaries/ui/src/app/globals.css:169 — `.btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement boundaries/ui/src/app/globals.css:177 — `.btn-secondary` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.

R11 · Import Boundaries · Boundary violation [layered · ×8

Boundary violation [layered:upward-import] boundaries/proxy/src/application/exceptions/ErrorHandler.ts:5 — boundaries/proxy/src/application/exceptions/ErrorHandler.ts:5 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules.
Boundary violation [layered:upward-import] boundaries/proxy/src/application/pipeline/AuthorizationInterceptor.ts:2 — boundaries/proxy/src/application/pipeline/AuthorizationInterceptor.ts:2 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules.
Boundary violation [layered:upward-import] boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:5 — boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:5 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules.
Boundary violation [layered:upward-import] boundaries/proxy/src/application/pipeline/__tests__/AuthorizationInterceptor.test.ts:9 — boundaries/proxy/src/application/pipeline/__tests__/AuthorizationInterceptor.test.ts:9 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules.
Boundary violation [layered:upward-import] boundaries/proxy/src/application/pipeline/__tests__/LoggingInterceptor.test.ts:4 — boundaries/proxy/src/application/pipeline/__tests__/LoggingInterceptor.test.ts:4 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules.
Boundary violation [layered:upward-import] boundaries/proxy/src/application/services/LinkApplicationService.ts:14 — boundaries/proxy/src/application/services/LinkApplicationService.ts:14 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules.
Boundary violation [layered:upward-import] boundaries/proxy/src/application/services/__tests__/LinkApplicationService.test.ts:8 — boundaries/proxy/src/application/services/__tests__/LinkApplicationService.test.ts:8 imports boundaries/proxy/src/infrastructure/logging/ILogger.ts against the layered-src rules.
Boundary violation [layered:upward-import] boundaries/ui/src/application/link/index.ts:2 — boundaries/ui/src/application/link/index.ts:2 imports boundaries/ui/src/infrastructure/http/link/linkHttpGateway.ts against the layered-src rules.

R7 · Dead Code · Dead file (~2 LoC) · ×5

Dead file (~2 LoC) boundaries/proxy/src/domain/entities/index.ts — no import path from any entry point (32 application, 31 tooling, 41 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
Dead file (~2 LoC) boundaries/proxy/src/infrastructure/http/swagger/index.ts — no import path from any entry point (32 application, 31 tooling, 41 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
Dead file (~2 LoC) boundaries/proxy/src/infrastructure/logging/index.ts — no import path from any entry point (32 application, 31 tooling, 41 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
Dead file (~2 LoC) boundaries/ui/src/contexts/index.ts — no import path from any entry point (32 application, 31 tooling, 41 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
Dead file (~2 LoC) boundaries/ui/src/store/index.ts — no import path from any entry point (32 application, 31 tooling, 41 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

X2 · Cancellation propagation · Async function without AbortSignal · ×5

Async function without AbortSignal: createLink boundaries/ui/src/infrastructure/http/link/linkHttpGateway.ts:42 — `createLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: updateProfile boundaries/ui/src/lib/datalayer/api.ts:82 — `updateProfile` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: createLink boundaries/ui/src/lib/datalayer/api.ts:96 — `createLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: deleteLink boundaries/ui/src/lib/datalayer/api.ts:110 — `deleteLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: updateLink boundaries/ui/src/lib/datalayer/api.ts:122 — `updateLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.

D29 · Static Analysis (SAST) · REDACTED · ×4

REDACTED
REDACTED
REDACTED
REDACTED

R11 · Import Boundaries · Boundary violation [package · ×4

Boundary violation [package:relative-cross-package] boundaries/ui/src/components/Footer/Footer.tsx:6 — boundaries/ui/src/components/Footer/Footer.tsx:6 reaches into another package with a relative path (../Copyright) — import the package by name instead.
Boundary violation [package:relative-cross-package] boundaries/ui/src/components/index.ts:2 — boundaries/ui/src/components/index.ts:2 reaches into another package with a relative path (./Footer) — import the package by name instead.
Boundary violation [package:relative-cross-package] boundaries/ui/src/components/index.ts:3 — boundaries/ui/src/components/index.ts:3 reaches into another package with a relative path (./Header) — import the package by name instead.
Boundary violation [package:relative-cross-package] boundaries/ui/src/components/index.tsx:2 — boundaries/ui/src/components/index.tsx:2 reaches into another package with a relative path (./Header) — import the package by name instead.

R7 · Dead Code · Dead file (~1 LoC) · ×4

Dead file (~1 LoC) boundaries/mobile/apps/shortlink/test-setup.ts — no import path from any entry point (32 application, 31 tooling, 41 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
Dead file (~1 LoC) boundaries/mobile/libs/ui/test-setup.ts — no import path from any entry point (32 application, 31 tooling, 41 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
Dead file (~1 LoC) boundaries/proxy/src/domain/interfaces/index.ts — no import path from any entry point (32 application, 31 tooling, 41 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
Dead file (~1 LoC) boundaries/proxy/src/domain/mappers/index.ts — no import path from any entry point (32 application, 31 tooling, 41 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

AC2 · Forms & labels · <fieldset> without a <legend> · ×3

<fieldset> without a <legend> boundaries/ui/src/components/Profile/Notifications.tsx:148 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> boundaries/ui/src/components/Profile/Notifications.tsx:199 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> boundaries/ui/src/components/async/AsyncForm.tsx:74 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.

D29 · Static Analysis (SAST) · REDACTED · ×3

REDACTED
REDACTED
REDACTED

D3 · God Classes · MethodTooLong · ×3

MethodTooLong: UC.Add boundaries/metadata/internal/usecases/metadata/metadata.go:73 — MethodTooLong — Add runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ErrorMapper.mapToHttpResponse boundaries/proxy/src/infrastructure/http/fastify/middleware/ErrorMapper.ts:45 — MethodTooLong — mapToHttpResponse runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: UC.Add boundaries/link/internal/usecases/link/add.go:31 — MethodTooLong — Add runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

D30 · Dependency Vulnerabilities · Medium vulnerability · ×3

REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×3

Duplicated block (14 lines × 2) boundaries/link/internal/infrastructure/repository/cqrs/query/postgres/get.go:51 — boundaries/link/internal/infrastructure/repository/cqrs/query/postgres/get.go:51-64 | boundaries/link/internal/infrastructure/repository/cqrs/query/postgres/list.go:75-88 — 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 (14 lines × 2) boundaries/link/internal/usecases/link_cqrs/api.go:53 — boundaries/link/internal/usecases/link_cqrs/api.go:53-66 | boundaries/link/internal/usecases/link_cqrs/api.go:96-109 — 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 `boundaries/link/internal/usecases/link_cqrs/api.go:53` 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.
Duplicated block (14 lines × 2) boundaries/link/internal/usecases/link_cqrs/handle_add.go:13 — boundaries/link/internal/usecases/link_cqrs/handle_add.go:13-26 | boundaries/link/internal/usecases/link_cqrs/handle_update.go:13-26 — 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 `boundaries/link/internal/usecases/link_cqrs/handle_add.go:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×3

Duplicated block (13 lines × 2 locations) boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:270 — boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:270 · boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:405 — 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.
Duplicated block (13 lines × 2 locations) boundaries/ui/src/components/Profile/Profile.tsx:42 — boundaries/ui/src/components/Profile/Profile.tsx:42 · boundaries/ui/src/components/Profile/Profile.tsx:56 — 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.
Duplicated block (13 lines × 2 locations) boundaries/ui/src/lib/datalayer/api.ts:82 — boundaries/ui/src/lib/datalayer/api.ts:82 · boundaries/ui/src/lib/datalayer/api.ts:122 — 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.

R7 · Dead Code · Dead file (~3 LoC) · ×3

Dead file (~3 LoC) boundaries/mobile/jest.preset.js — no import path from any entry point (32 application, 31 tooling, 41 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
Dead file (~3 LoC) boundaries/proxy/src/application/handlers/index.ts — no import path from any entry point (32 application, 31 tooling, 41 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
Dead file (~3 LoC) boundaries/ui/src/components/index.tsx — no import path from any entry point (32 application, 31 tooling, 41 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

AC6 · Visual & motion safety · Focus outline removed inline · ×2

Focus outline removed inline boundaries/ui/src/app/not-found.tsx:19 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline boundaries/ui/src/components/Profile/Profile.tsx:98 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2

Members sharing a duplicated core (6 members, 50+ identical tokens) boundaries/api/api-gateway/gateways/cloudevents/cmd/api.go:19 — boundaries/api/api-gateway/gateways/cloudevents/cmd/api.go:19-43 | boundaries/api/api-gateway/gateways/graphql/cmd/api.go:19-43 | boundaries/api/api-gateway/gateways/grpc-web/cmd/api.go:19-43 | boundaries/api/api-gateway/gateways/ws/cmd/ws.go:12-34 | boundaries/bff/cmd/main.go:21-45 | boundaries/link/cmd/main.go:19-45 — These 6 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 6 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 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) boundaries/link/internal/usecases/link/add.go:31 — boundaries/link/internal/usecases/link/add.go:31-234 | boundaries/link/internal/usecases/link/delete.go:20-103 | boundaries/link/internal/usecases/link/get.go:23-129 | boundaries/link/internal/usecases/link_cqrs/api.go:30-71 | boundaries/link/internal/usecases/link_cqrs/api.go:73-114 | boundaries/metadata/internal/usecases/metadata/metadata.go:73-299 — These 6 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 6 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 6 times.

D4 · Code Duplication · Duplicated block (21 lines × 2) · ×2

Duplicated block (21 lines × 2) boundaries/api/api-gateway/gateways/cloudevents/infrastructure/server/server.go:33 — boundaries/api/api-gateway/gateways/cloudevents/infrastructure/server/server.go:33-53 | boundaries/api/api-gateway/gateways/graphql/infrastructure/server/server.go:35-55 — before extracting anything, compare `boundaries/api/api-gateway/gateways/cloudevents/infrastructure/server/server.go` and `boundaries/api/api-gateway/gateways/graphql/infrastructure/server/server.go` as WHOLE FILES: 86% 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.
Duplicated block (21 lines × 2) boundaries/link/internal/infrastructure/repository/crud/mongo/mongo.go:57 — boundaries/link/internal/infrastructure/repository/crud/mongo/mongo.go:57-77 | boundaries/link/internal/infrastructure/repository/crud/postgres/postgres.go:61-81 — 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 `boundaries/link/internal/infrastructure/repository/crud/mongo/mongo.go:57` 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 (17 lines × 2) · ×2

Duplicated block (17 lines × 2) boundaries/link/internal/infrastructure/repository/crud/mongo/mongo.go:90 — boundaries/link/internal/infrastructure/repository/crud/mongo/mongo.go:90-106 | boundaries/link/internal/infrastructure/repository/crud/ram/ram.go:107-123 — 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 `boundaries/link/internal/infrastructure/repository/crud/mongo/mongo.go:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) boundaries/link/internal/infrastructure/cqrs/test_helpers.go:24 — boundaries/link/internal/infrastructure/cqrs/test_helpers.go:24-40 | boundaries/metadata/internal/infrastructure/mq/test_helpers.go:28-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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. Check import visibility before settling on that home: `boundaries/link/internal/infrastructure/cqrs/test_helpers.go`, `boundaries/metadata/internal/infrastructure/mq/test_helpers.go` sit under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.

D4 · Code Duplication · Duplicated block (15 lines × 3) · ×2

Duplicated block (15 lines × 3) boundaries/api/api-gateway/gateways/cloudevents/di/wire.go:72 — boundaries/api/api-gateway/gateways/cloudevents/di/wire.go:72-86 | boundaries/api/api-gateway/gateways/graphql/di/wire.go:72-86 | boundaries/api/api-gateway/gateways/grpc-web/di/wire.go:74-88 — before extracting anything, compare `boundaries/api/api-gateway/gateways/cloudevents/di/wire.go` and `boundaries/api/api-gateway/gateways/graphql/di/wire.go` as WHOLE FILES: 96% 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 2 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.
Duplicated block (15 lines × 3) boundaries/api/api-gateway/gateways/grpc-web/infrastructure/server/v1/api.go:14 — boundaries/api/api-gateway/gateways/grpc-web/infrastructure/server/v1/api.go:14-28 | boundaries/api/api-gateway/gateways/grpc-web/infrastructure/server/v1/api.go:48-62 | boundaries/api/api-gateway/gateways/grpc-web/infrastructure/server/v1/api.go:84-98 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `boundaries/api/api-gateway/gateways/grpc-web/infrastructure/server/v1/api.go:14` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2

Duplicated block (15 lines × 2) boundaries/bff/internal/di/wire.go:100 — boundaries/bff/internal/di/wire.go:100-114 | boundaries/link/internal/di/wire.go:172-186 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Check import visibility before settling on that home: `boundaries/bff/internal/di/wire.go`, `boundaries/link/internal/di/wire.go` sit under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.
Duplicated block (15 lines × 2) boundaries/link/internal/infrastructure/repository/cqrs/cqs/postgres/cqs.go:11 — boundaries/link/internal/infrastructure/repository/cqrs/cqs/postgres/cqs.go:11-25 | boundaries/link/internal/infrastructure/repository/cqrs/query/postgres/query.go:11-25 — before extracting anything, compare `boundaries/link/internal/infrastructure/repository/cqrs/cqs/postgres/cqs.go` and `boundaries/link/internal/infrastructure/repository/cqrs/query/postgres/query.go` as WHOLE FILES: 100% 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.

DM4 · Rich vs anemic model · Anemic entity · ×2

Anemic entity: Hash boundaries/proxy/src/domain/entities/Hash.ts:7 — `Hash` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Link boundaries/proxy/src/domain/entities/Link.ts:7 — `Link` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.

IC1 · Incompleteness & stubs · Fake-async · ×2

Fake-async — async method never awaits boundaries/proxy/src/infrastructure/http/fastify/controllers/MetricsController.ts:16 — `getMetrics` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits boundaries/proxy/src/infrastructure/telemetry.ts:288 — `semanticEnrichmentPlugin` 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 · Wholesale file copy (67 identical lines × 2 files) · ×2

Wholesale file copy (67 identical lines × 2 files) boundaries/ui/src/app/admin/links/page.tsx:17 — boundaries/ui/src/app/admin/links/page.tsx:17 · boundaries/ui/src/app/links/page.tsx:17 — these 2 files are line-for-line copies of one another — 67 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (67 identical lines × 2 files) boundaries/ui/src/components/Page/admin/user/linksTable.tsx:1 — boundaries/ui/src/components/Page/admin/user/linksTable.tsx:1 · boundaries/ui/src/components/Page/user/linksTable.tsx:1 — these 2 files are line-for-line copies of one another — 67 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.

R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×2

Duplicated block (10 lines × 2 locations) boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:65 — boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:65 · boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:88 — 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.
Duplicated block (10 lines × 2 locations) boundaries/proxy/src/infrastructure/repositories/LinkServiceRepository.ts:51 — boundaries/proxy/src/infrastructure/repositories/LinkServiceRepository.ts:51 · boundaries/proxy/src/infrastructure/repositories/LinkServiceRepository.ts:100 — 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.

R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×2

Duplicated block (9 lines × 2 locations) boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:23 — boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:23 · boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:33 — 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.
Duplicated block (9 lines × 2 locations) boundaries/proxy/src/application/pipeline/MetricsInterceptor.ts:44 — boundaries/proxy/src/application/pipeline/MetricsInterceptor.ts:44 · boundaries/proxy/src/application/pipeline/MetricsInterceptor.ts:58 — 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.

R10 · Code Duplication · Duplicated block (8 lines × 2 locations) · ×2

Duplicated block (8 lines × 2 locations) boundaries/proxy/src/application/pipeline/MetricsInterceptor.ts:10 — boundaries/proxy/src/application/pipeline/MetricsInterceptor.ts:10 · boundaries/proxy/src/infrastructure/metrics/OpenTelemetryGrpcMetrics.ts:8 — the 2 copies are spread across 2 files, 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.
Duplicated block (8 lines × 2 locations) boundaries/proxy/src/infrastructure/logging/WinstonLogger.ts:175 — boundaries/proxy/src/infrastructure/logging/WinstonLogger.ts:175 · boundaries/proxy/src/infrastructure/logging/WinstonLogger.ts:185 — 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.

R7 · Dead Code · Dead file (~111 LoC) · ×2

Dead file (~111 LoC) boundaries/ui/src/components/user/integrations/page.tsx — no import path from any entry point (32 application, 31 tooling, 41 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
Dead file (~111 LoC) boundaries/ui/src/lib/datalayer/cache.ts — no import path from any entry point (32 application, 31 tooling, 41 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

X3 · Exception handling · Swallowed exception (caught, then discarded) · ×2

Swallowed exception (caught, then discarded) boundaries/api/api-gateway/gateways/ws/infrustracture/ws/ws.go:67 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) boundaries/bff/internal/infrastructure/http/controllers/link/error.go:66 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.

AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×1

Animation without a prefers-reduced-motion guard boundaries/ui/src/public/assets/styles.css:54 — `.toggleWrapper` moves (`transition: transform 0.3s ease-in-out`) 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.

D1 · Cyclomatic Complexity · page.Page (cyclomatic 43) · ×1

page.Page (cyclomatic 43) boundaries/ui/src/app/add-link/page.tsx:59 — page.Page has cyclomatic complexity 43 (threshold 15). Of this number, 16 points are the body's own statements and 27 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · RabbitMQMessageBus.publish (cyclomatic 22) · ×1

RabbitMQMessageBus.publish (cyclomatic 22) boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:193 — RabbitMQMessageBus.publish has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · page.Page (cyclomatic 22) · ×1

page.Page (cyclomatic 22) boundaries/ui/src/app/admin/sitemap/page.tsx:60 — page.Page has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (handleSubmit, a function literal at line 213, normalizeUrl, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · link.mapStatusToResponse (cyclomatic 21) · ×1

link.mapStatusToResponse (cyclomatic 21) boundaries/bff/internal/infrastructure/http/controllers/link/error.go:92 — link.mapStatusToResponse has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · HttpClient.request (cyclomatic 21) · ×1

HttpClient.request (cyclomatic 21) boundaries/ui/src/store/api/Api.ts:223 — HttpClient.request has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 2 function literals inside it that branch. This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.

D1 · Cyclomatic Complexity · crud.New (cyclomatic 19) · ×1

crud.New (cyclomatic 19) boundaries/link/internal/infrastructure/repository/crud/init.go:30 — crud.New has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · KafkaMessageBus.publish (cyclomatic 19) · ×1

KafkaMessageBus.publish (cyclomatic 19) boundaries/proxy/src/infrastructure/messaging/KafkaMessageBus.ts:152 — KafkaMessageBus.publish has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · UseCasePipeline.execute (cyclomatic 18) · ×1

UseCasePipeline.execute (cyclomatic 18) boundaries/proxy/src/application/pipeline/UseCasePipeline.ts:21 — UseCasePipeline.execute has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · UC.Add (cyclomatic 17) · ×1

UC.Add (cyclomatic 17) boundaries/link/internal/usecases/link/add.go:31 — UC.Add has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 89, 179, 62, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · ErrorMapper.mapToHttpResponse (cyclomatic 17) · ×1

ErrorMapper.mapToHttpResponse (cyclomatic 17) boundaries/proxy/src/infrastructure/http/fastify/middleware/ErrorMapper.ts:45 — ErrorMapper.mapToHttpResponse has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · Store.List (cyclomatic 16) · ×1

Store.List (cyclomatic 16) boundaries/link/internal/infrastructure/repository/cqrs/query/postgres/list.go:14 — Store.List has cyclomatic complexity 16 (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.

D10 · Test Quality · No assertions · ×1

No assertions: should skip when Redis is not available boundaries/proxy/src/infrastructure/cache/__tests__/RedisLinkCache.test.ts:325 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.

D12 · Dependency Hygiene · Dependency pinned to a stale untagged commit · ×1

Dependency pinned to a stale untagged commit: github.com/syndtr/goleveldb — Direct dependency `github.com/syndtr/goleveldb` is required at `v1.0.1-0.20220721030215-126854af5e6d` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2022-07-21, 4.3 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/syndtr/goleveldb` and has not moved this requirement in 4.3 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/syndtr/goleveldb` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.

D2 · Cognitive Complexity · page.Page (cognitive 50) · ×1

page.Page (cognitive 50) boundaries/ui/src/app/add-link/page.tsx:59 — page.Page has cognitive complexity 50 (threshold 15). Drivers by points: if/else 16 (18 pts), ternaries 10 (16 pts), boolean chains 15, error handling 1 (nesting depth added 8). Of this number, 20 points are the body's own statements and 30 belong to 7 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · UC.Add (cognitive 26) · ×1

UC.Add (cognitive 26) boundaries/link/internal/usecases/link/add.go:31 — UC.Add has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (23 pts), match/switch 1 (3 pts) (nesting depth added 9). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 89, 179, 62, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · UseCasePipeline.execute (cognitive 24) · ×1

UseCasePipeline.execute (cognitive 24) boundaries/proxy/src/application/pipeline/UseCasePipeline.ts:21 — UseCasePipeline.execute has cognitive complexity 24 (threshold 15). Drivers by points: loops 7 (11 pts), if/else 5 (10 pts), boolean chains 2, error handling 1 (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · page.Page (cognitive 24) · ×1

page.Page (cognitive 24) boundaries/ui/src/app/admin/sitemap/page.tsx:60 — page.Page has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 9 (12 pts), boolean chains 8, if/else 3, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 7 function items inside it that branch (handleSubmit, a function literal at line 213, normalizeUrl, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · RabbitMQMessageBus.publish (cognitive 23) · ×1

RabbitMQMessageBus.publish (cognitive 23) boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:193 — RabbitMQMessageBus.publish has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 13, if/else 4, ternaries 2 (4 pts), error handling 2 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D2 · Cognitive Complexity · KafkaMessageBus.publish (cognitive 22) · ×1

KafkaMessageBus.publish (cognitive 22) boundaries/proxy/src/infrastructure/messaging/KafkaMessageBus.ts:152 — KafkaMessageBus.publish has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (8 pts), ternaries 2 (3 pts), loops 1 (2 pts), error handling 1 (nesting depth added 4). 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 · Store.List (cognitive 21) · ×1

Store.List (cognitive 21) boundaries/link/internal/infrastructure/repository/cqrs/query/postgres/list.go:14 — Store.List has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 1, loops 1 (nesting depth added 7). 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 · crud.New (cognitive 19) · ×1

crud.New (cognitive 19) boundaries/link/internal/infrastructure/repository/crud/init.go:30 — crud.New has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · link_cqrs.subscribe (cognitive 19) · ×1

link_cqrs.subscribe (cognitive 19) boundaries/link/internal/usecases/link_cqrs/event.go:55 — link_cqrs.subscribe has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 1 (4 pts), loops 1 (nesting depth added 10). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 72). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · LinkServiceRepository.findByHash (cognitive 19) · ×1

LinkServiceRepository.findByHash (cognitive 19) boundaries/proxy/src/infrastructure/repositories/LinkServiceRepository.ts:36 — LinkServiceRepository.findByHash has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 4 (5 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 8). 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 · HttpClient.request (cognitive 19) · ×1

HttpClient.request (cognitive 19) boundaries/ui/src/store/api/Api.ts:223 — HttpClient.request has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 4 (5 pts), ternaries 5 (nesting depth added 1). Of this number, 13 points are the body's own statements and 6 belong to 2 function literals inside it that branch. This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.

D2 · Cognitive Complexity · UC.List (cognitive 16) · ×1

UC.List (cognitive 16) boundaries/link/internal/usecases/link/list.go:22 — UC.List has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (15 pts), loops 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 59, 107). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · RetryInterceptor.createRetryInterceptor (cognitive 16) · ×1

RetryInterceptor.createRetryInterceptor (cognitive 16) boundaries/proxy/src/infrastructure/adapters/connect/interceptors/RetryInterceptor.ts:93 — RetryInterceptor.createRetryInterceptor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 2 (7 pts), boolean chains 6, error handling 1 (2 pts), loops 1 (nesting depth added 6). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 99). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · ErrorMapper.mapToHttpResponse (cognitive 16) · ×1

ErrorMapper.mapToHttpResponse (cognitive 16) boundaries/proxy/src/infrastructure/http/fastify/middleware/ErrorMapper.ts:45 — ErrorMapper.mapToHttpResponse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, boolean chains 5, ternaries 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D20 · ADR Quality · No context/problem framing (e.g., why tiny URLs are needed) and no consequences/trade-offs section · ×1

No context/problem framing (e.g., why tiny URLs are needed) and no consequences/trade-offs section boundaries/common/docs/ADR/decisions/0003-requirements.md — Add a Context section explaining the problem tiny-URLs solve and a Consequences section on trade-offs such as storage cost and the operational lifespan of 5 years

D20 · ADR Quality · Context and consequences are both cited to an external source (Michael Nygard's blog + adr-tools repo), leaving the ADR itself uninformative and its own rationale buried in links · ×1

Context and consequences are both cited to an external source (Michael Nygard's blog + adr-tools repo), leaving the ADR itself uninformative and its own rationale buried in links docs/ADR/decisions/0001-record-architecture-decisions.md — Replace the Context/Consequences with a one-paragraph rationale explaining why records matter for clarity, traceability, and future maintenance, then explicitly state the decision and any trade-offs of adopting an external tool

D20 · ADR Quality · No consequences/trade-offs section (e.g. added overhead of healthz endpoints) · ×1

No consequences/trade-offs section (e.g. added overhead of healthz endpoints) docs/ADR/decisions/0003-observability-health-check.md

D20 · ADR Quality · Decision and consequences are cut off mid-body before the visible elements (context plus Docs) are fully shown · ×1

Decision and consequences are cut off mid-body before the visible elements (context plus Docs) are fully shown docs/ADR/decisions/0004-use-uuid-as-primary-keys.md

D20 · ADR Quality · Informative title (uninformative) and context are both thin · ×1

Informative title (uninformative) and context are both thin: the decision is explicit but there is only one sentence stating what CODEOWNERS does ('used to define individuals or teams that are responsible for code') with no problem statement; consequences are real but trade-offs are not visible before the clip docs/ADR/decisions/0006-codeowner.md

D20 · ADR Quality · The decision (what change was proposed) and its rationale are not visible in the excerpt; only context and a partial consequences list are shown · ×1

The decision (what change was proposed) and its rationale are not visible in the excerpt; only context and a partial consequences list are shown docs/ADR/decisions/0007-optimization-network.md — Add a one-line Decision line stating what change was agreed to implement (e.g. 'Replace gRPC with proto-fieldmask for mutation operations') so readers can judge completeness

D20 · ADR Quality · Context and decision are both single words ('We want to know product metrics by each services' / 'We made grafana dashboard for product-metrics by each services') with no consequences; the Consequences section is cut at "2. Functional" before any real trade-offs · ×1

Context and decision are both single words ('We want to know product metrics by each services' / 'We made grafana dashboard for product-metrics by each services') with no consequences; the Consequences section is cut at "2. Functional" before any real trade-offs docs/ADR/decisions/0008-product-metrics-by-services.md — Expand Context to explain why per-service product-metrics matter (e.g., observability, blameless culture) and flesh out the Consequences into actual operational costs/trade-offs of Grafana (cost, skill needed, integration with existing tools)}

D20 · ADR Quality · Context is a one-line rationale ('We use tracing and logging systems to track application events, and we need to set naming standards for spans and their attributes') with no trade-offs or alternative framing · ×1

Context is a one-line rationale ('We use tracing and logging systems to track application events, and we need to set naming standards for spans and their attributes') with no trade-offs or alternative framing docs/ADR/decisions/0009-naming-spans-and-attributes.md — Expand the Context section to explain why OTLP/naming matters (e.g. debugging, cross-team comparison) and note any alternatives considered

D20 · ADR Quality · Consequences/trade-offs are deferred and the link ('structured-logging.html') does not appear to explain any real trade-off (e.g. performance cost of structured logs vs human-readable output) · ×1

Consequences/trade-offs are deferred and the link ('structured-logging.html') does not appear to explain any real trade-off (e.g. performance cost of structured logs vs human-readable output) docs/ADR/decisions/0010-logger-format.md — Add a Consequences section noting that while standardized, the JSON format may be harder to read for humans and could require more infrastructure around OTel tracing

D20 · ADR Quality · Context is excellent but consequences are restated (e.g. 'We use the [4C model] for the documentation of the application architecture.') rather than being a new consequence · ×1

Context is excellent but consequences are restated (e.g. 'We use the [4C model] for the documentation of the application architecture.') rather than being a new consequence docs/ADR/decisions/0011-application-architecture-documentation.md

D20 · ADR Quality · Context and decision are identical ("We want to have a monorepository for the platform."), with no context/problem and no consequences · ×1

Context and decision are identical ("We want to have a monorepository for the platform."), with no context/problem and no consequences docs/ADR/decisions/0012-use-monorepository.md — Replace the repeated "Use monorepository" title with an informative one like "Centralize all platform code into a single repository"; replace the Context/Decision with a real problem motivating a monorepo (e.g. cross-component dependency, shared libraries) and its trade-offs

D20 · ADR Quality · Context is a single sentence ('We want to use integration tests to verify the correctness of our code.') and decision restates 'We will use k6' with no rationale; consequences are boilerplate install commands (go install + xk6 build) plus one plugin link · ×1

Context is a single sentence ('We want to use integration tests to verify the correctness of our code.') and decision restates 'We will use k6' with no rationale; consequences are boilerplate install commands (go install + xk6 build) plus one plugin link docs/ADR/decisions/0020-k6.md — Add why k6 was chosen over alternatives, a brief test-verification goal, and trade-offs such as the cost of running distributed tracing tests

D20 · ADR Quality · Uninformative title and context; only an explicit decision (structure shown) is present without any rationale/trade-offs · ×1

Uninformative title and context; only an explicit decision (structure shown) is present without any rationale/trade-offs docs/ADR/decisions/0021-microservice-structure.md — Give the ADR a descriptive title like '21. Microservice architecture: C4 diagrams, Docker, Helm, and CI workflows' so readers know what it addresses. Add a Context section explaining why microservices are needed and the trade-offs of this structure.

D20 · ADR Quality · Context is thin ("This ADR addresses the need to standardize our code style tool, considering efficiency and developer experience."), decision is a one-line rationale with no alternatives considered, and consequences are only a single sentence without trade-offs · ×1

Context is thin ("This ADR addresses the need to standardize our code style tool, considering efficiency and developer experience."), decision is a one-line rationale with no alternatives considered, and consequences are only a single sentence without trade-offs docs/ADR/decisions/0032-python-code-style-selection.md — Expand Context by explaining why Flake8/Ruff were chosen over alternatives, add an Alternatives section covering trade-offs of each tool (e.g. Ruff's learning curve vs Flake8's maturity), and detail the Consequences with adoption cost, skill requirements, and migration impact

D20 · ADR Quality · Context and decision are present but the consequences section is a single one-line statement ('We will be able to make our UI accessible for people with disabilities.') referencing no concrete trade-offs (e.g. performance cost of prefers-reduced-transparency), leaving only an aspirational claim · ×1

Context and decision are present but the consequences section is a single one-line statement ('We will be able to make our UI accessible for people with disabilities.') referencing no concrete trade-offs (e.g. performance cost of prefers-reduced-transparency), leaving only an aspirational claim docs/ADR/decisions/0039-ui-accessibility.md — Expand the Consequences section to note any real costs such as reduced opacity on hover or focus states, and add a Trade-Offs section addressing those

D20 · ADR Quality · Consequences are present but only benefit bullet points; no trade-offs (e.g. vendor lock-in to Storybook or component selection) and no link to the actual UI-kit implementation · ×1

Consequences are present but only benefit bullet points; no trade-offs (e.g. vendor lock-in to Storybook or component selection) and no link to the actual UI-kit implementation docs/ADR/decisions/0040-ui-kit.md — Add a Consequences section on trade-offs such as dependency on Storybook for testing vs runtime tests, and note where components live

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D32 · Data Compliance (PII/GDPR) · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1

Duplicated block (32 lines × 2) boundaries/link/internal/infrastructure/repository/cqrs/cqs/postgres/cqs_link.go:18 — boundaries/link/internal/infrastructure/repository/cqrs/cqs/postgres/cqs_link.go:18-49 | boundaries/link/internal/infrastructure/repository/cqrs/cqs/postgres/cqs_link.go:59-90 — 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 `boundaries/link/internal/infrastructure/repository/cqrs/cqs/postgres/cqs_link.go:18` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1

Duplicated block (29 lines × 2) boundaries/link/internal/di/wire.go:86 — boundaries/link/internal/di/wire.go:86-114 | boundaries/metadata/internal/di/wire.go:71-99 — 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. Check import visibility before settling on that home: `boundaries/link/internal/di/wire.go`, `boundaries/metadata/internal/di/wire.go` sit under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.

D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1

Duplicated block (18 lines × 2) boundaries/link/internal/usecases/link/add.go:43 — boundaries/link/internal/usecases/link/add.go:43-60 | boundaries/link/internal/usecases/link/delete.go:25-42 — 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 `boundaries/link/internal/usecases/link/delete.go:25` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (16 lines × 6) · ×1

Duplicated block (16 lines × 6) boundaries/api/api-gateway/gateways/cloudevents/cmd/api.go:28 — boundaries/api/api-gateway/gateways/cloudevents/cmd/api.go:28-43 | boundaries/api/api-gateway/gateways/graphql/cmd/api.go:28-43 | boundaries/api/api-gateway/gateways/grpc-web/cmd/api.go:28-43 | boundaries/api/api-gateway/gateways/ws/cmd/ws.go:19-34 | boundaries/bff/cmd/main.go:30-45 | boundaries/link/cmd/main.go:30-45 — before extracting anything, compare `boundaries/api/api-gateway/gateways/cloudevents/cmd/api.go` and `boundaries/api/api-gateway/gateways/grpc-web/cmd/api.go` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `boundaries/api/api-gateway/gateways/cloudevents/cmd/api.go:28` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `boundaries/link/cmd/main.go:28` calls `Info` and `boundaries/api/api-gateway/gateways/cloudevents/cmd/api.go:26` 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) boundaries/link/internal/usecases/link/error.go:16 — boundaries/link/internal/usecases/link/error.go:16-28 | boundaries/link/internal/usecases/link_cqrs/api.go:16-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1

Duplicated block (11 lines × 2) boundaries/link/internal/infrastructure/repository/crud/dgraph/dgraph.go:61 — boundaries/link/internal/infrastructure/repository/crud/dgraph/dgraph.go:61-71 | boundaries/link/internal/infrastructure/repository/crud/dgraph/dgraph.go:162-172 — 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 `boundaries/link/internal/infrastructure/repository/crud/dgraph/dgraph.go:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.

D4 · Code Duplication · Duplicated block (9–10 lines × 6) · ×1

Duplicated block (9–10 lines × 6) boundaries/link/internal/usecases/link/add.go:53 — boundaries/link/internal/usecases/link/add.go:53-62 | boundaries/link/internal/usecases/link/delete.go:37-45 | boundaries/link/internal/usecases/link/get.go:42-51 | boundaries/link/internal/usecases/link_cqrs/api.go:39-48 | boundaries/link/internal/usecases/link_cqrs/api.go:82-91 | boundaries/metadata/internal/usecases/metadata/metadata.go:84-93 — there are 6 copies across 5 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `boundaries/link/internal/usecases/link/add.go:53` 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. Check import visibility before settling on that home: `boundaries/link/internal/usecases/link/add.go`, `boundaries/link/internal/usecases/link/delete.go`, `boundaries/link/internal/usecases/link/get.go` sit under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1

Duplicated block (10 lines × 2) boundaries/link/internal/usecases/link/add.go:182 — boundaries/link/internal/usecases/link/add.go:182-191 | boundaries/link/internal/usecases/sitemap/parser.go:88-97 — 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 `boundaries/link/internal/usecases/link/add.go:182` 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 (9 lines × 2) · ×1

Duplicated block (9 lines × 2) boundaries/link/internal/usecases/link/get.go:55 — boundaries/link/internal/usecases/link/get.go:55-63 | boundaries/link/internal/usecases/link/list.go:111-119 — 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 `boundaries/link/internal/usecases/link/get.go:55` 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 (7–8 lines × 2) · ×1

Duplicated block (7–8 lines × 2) REDACTED:31 — REDACTED:31-37 | boundaries/link/internal/infrastructure/rpc/link/v1/update_response_dto.go:10-17 — 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. 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 (7 lines × 3) · ×1

Duplicated block (7 lines × 3) boundaries/link/internal/usecases/link/add.go:181 — boundaries/link/internal/usecases/link/add.go:181-187 | boundaries/link/internal/usecases/link/update.go:18-24 | boundaries/link/internal/usecases/sitemap/parser.go:87-93 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `boundaries/link/internal/usecases/link/add.go:178` calls `AddStep`, `Then` and `boundaries/link/internal/usecases/link/update.go:15` 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 (6 lines × 2) · ×1

Duplicated block (6 lines × 2) boundaries/link/internal/di/wire.go:129 — boundaries/link/internal/di/wire.go:129-134 | boundaries/metadata/internal/di/wire.go:108-113 — 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. Check import visibility before settling on that home: `boundaries/link/internal/di/wire.go`, `boundaries/metadata/internal/di/wire.go` sit under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.

D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1

Duplicated block (14 lines × 3) boundaries/api/api-gateway/gateways/cloudevents/di/wire.go:158 — boundaries/api/api-gateway/gateways/cloudevents/di/wire.go:158-171 | boundaries/api/api-gateway/gateways/graphql/di/wire.go:160-173 | boundaries/api/api-gateway/gateways/grpc-web/di/wire.go:162-175 — before extracting anything, compare `boundaries/api/api-gateway/gateways/cloudevents/di/wire.go` and `boundaries/api/api-gateway/gateways/graphql/di/wire.go` as WHOLE FILES: 96% 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 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `boundaries/api/api-gateway/gateways/cloudevents/di/wire.go:158` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1

Duplicated block (22 lines × 2) boundaries/api/api-gateway/gateways/graphql/di/wire.go:126 — boundaries/api/api-gateway/gateways/graphql/di/wire.go:126-147 | boundaries/api/api-gateway/gateways/grpc-web/di/wire.go:128-149 — before extracting anything, compare `boundaries/api/api-gateway/gateways/graphql/di/wire.go` and `boundaries/api/api-gateway/gateways/grpc-web/di/wire.go` as WHOLE FILES: this scan already matched 3 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 `boundaries/api/api-gateway/gateways/graphql/di/wire.go:126` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1

Duplicated block (8 lines × 3) boundaries/link/internal/infrastructure/repository/crud/mongo/mongo.go:265 — boundaries/link/internal/infrastructure/repository/crud/mongo/mongo.go:265-272 | boundaries/link/internal/infrastructure/repository/crud/postgres/postgres.go:93-100 | boundaries/link/internal/infrastructure/repository/crud/ram/ram.go:148-155 — 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.

D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1

Duplicated block (20 lines × 2) boundaries/link/internal/infrastructure/repository/crud/dgraph/dgraph.go:197 — boundaries/link/internal/infrastructure/repository/crud/dgraph/dgraph.go:197-216 | boundaries/link/internal/infrastructure/repository/crud/dgraph/dgraph.go:233-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.

D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1

Duplicated block (6 lines × 3) boundaries/link/internal/usecases/link/add.go:55 — boundaries/link/internal/usecases/link/add.go:55-62 | boundaries/metadata/internal/usecases/metadata/metadata.go:86-93 | boundaries/metadata/internal/usecases/metadata/metadata.go:119-124 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `boundaries/link/internal/usecases/link/add.go:55` 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. Check import visibility before settling on that home: `boundaries/link/internal/usecases/link/add.go`, `boundaries/metadata/internal/usecases/metadata/metadata.go` sit under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.

D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1

Duplicated block (19 lines × 2) boundaries/link/internal/infrastructure/cqrs/test_helpers.go:54 — boundaries/link/internal/infrastructure/cqrs/test_helpers.go:54-72 | boundaries/metadata/internal/infrastructure/mq/test_helpers.go:58-76 — 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. Check import visibility before settling on that home: `boundaries/link/internal/infrastructure/cqrs/test_helpers.go`, `boundaries/metadata/internal/infrastructure/mq/test_helpers.go` sit under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: @nx-expo-monorepo/ui — @nx-expo-monorepo/ui: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.

D6 · Cohesion (LCOM4) · Low cohesion · ×1

Low cohesion: API (LCOM4 6) boundaries/api/api-gateway/gateways/grpc-web/infrastructure/server/v1/server.go:23 — API's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in boundaries/mobile/ ran and not one test passed (Error: Jest: Failed to parse the TypeScript config file boundaries/mobile/jest.config.ts), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.

M1 · Documentation (README) · README may be stale · ×1

README may be stale — 26 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

P12 · CI test-gate honesty · Coverage collected but not gated · ×1

Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.

P5 · DR & Backup · No DR/backup evidence · ×1

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

R10 · Code Duplication · Duplicated block with local edits (120 matched lines × 2 locations) · ×1

Duplicated block with local edits (120 matched lines × 2 locations) boundaries/proxy/src/infrastructure/messaging/KafkaMessageBus.ts:40 — boundaries/proxy/src/infrastructure/messaging/KafkaMessageBus.ts:40 · boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:34 — the two spans are one implementation copied and then locally edited — 637 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 with local edits (83 matched lines × 2 locations) · ×1

Duplicated block with local edits (83 matched lines × 2 locations) REDACTED:135 — REDACTED:135 · boundaries/ui/src/components/Profile/Profile.tsx:75 — the two spans are one implementation copied and then locally edited — 365 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 with local edits (54 matched lines × 2 locations) · ×1

Duplicated block with local edits (54 matched lines × 2 locations) boundaries/proxy/src/infrastructure/messaging/AMQPEventPublisher.ts:71 — boundaries/proxy/src/infrastructure/messaging/AMQPEventPublisher.ts:71 · boundaries/proxy/src/infrastructure/messaging/KafkaEventPublisher.ts:37 — the two spans are one implementation copied and then locally edited — 308 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 (37 lines × 2 locations) · ×1

Duplicated block (37 lines × 2 locations) boundaries/ui/src/components/Profile/Notifications.tsx:241 — boundaries/ui/src/components/Profile/Notifications.tsx:241 · REDACTED:284 — 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 (36 lines × 3 locations) · ×1

Duplicated block (36 lines × 3 locations) boundaries/ui/src/components/Profile/Notifications.tsx:242 — boundaries/ui/src/components/Profile/Notifications.tsx:242 · REDACTED:285 · boundaries/ui/src/components/Profile/Security.tsx:122 — 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 (34 lines × 2 locations) · ×1

Duplicated block (34 lines × 2 locations) boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:316 — boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:316 · boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:358 — 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.

R10 · Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) · ×1

Duplicated block with local edits (30 matched lines × 2 locations) boundaries/ui/src/app/faq/page.tsx:36 — boundaries/ui/src/app/faq/page.tsx:36 · boundaries/ui/src/app/privacy/page.tsx:32 — the two spans are one implementation copied and then locally edited — 182 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 (28 lines × 2 locations) · ×1

Duplicated block (28 lines × 2 locations) boundaries/ui/src/app/admin/groups/page.tsx:79 — boundaries/ui/src/app/admin/groups/page.tsx:79 · boundaries/ui/src/app/admin/users/page.tsx:79 — 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 (24 lines × 2 locations) · ×1

Duplicated block (24 lines × 2 locations) boundaries/ui/src/components/Header/Header.tsx:112 — boundaries/ui/src/components/Header/Header.tsx:112 · boundaries/ui/src/components/Header/NavbarMobileMenu.tsx:76 — 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 (19 lines × 2 locations) · ×1

Duplicated block (19 lines × 2 locations) boundaries/ui/src/components/Header/ActiveIcon.tsx:11 — boundaries/ui/src/components/Header/ActiveIcon.tsx:11 · boundaries/ui/src/components/Header/ActiveLink.tsx:11 — the 2 copies are spread across 2 files, 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.

R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×1

Duplicated block (18 lines × 2 locations) boundaries/ui/src/components/Profile/Notifications.tsx:34 — boundaries/ui/src/components/Profile/Notifications.tsx:34 · boundaries/ui/src/components/Profile/Notifications.tsx:72 — all 2 copies are in the same file, 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 (17 lines × 5 locations) · ×1

Duplicated block (17 lines × 5 locations) boundaries/ui/src/components/Dashboard/profile.tsx:127 — boundaries/ui/src/components/Dashboard/profile.tsx:127 · boundaries/ui/src/components/Dashboard/profile.tsx:144 · boundaries/ui/src/components/Dashboard/profile.tsx:161 · boundaries/ui/src/components/Dashboard/profile.tsx:178 · +1 more site(s) not listed — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

R10 · Code Duplication · Duplicated block (16 lines × 3 locations) · ×1

Duplicated block (16 lines × 3 locations) boundaries/ui/src/store/sagas/link.ts:7 — boundaries/ui/src/store/sagas/link.ts:7 · boundaries/ui/src/store/sagas/link.ts:49 · boundaries/ui/src/store/sagas/link.ts:93 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×1

Duplicated block (15 lines × 2 locations) boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:78 — boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:78 · boundaries/proxy/src/infrastructure/logging/WinstonLogger.ts:74 — the 2 copies are spread across 2 files, 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.

R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×1

Duplicated block (14 lines × 2 locations) boundaries/ui/src/components/Header/ProfileMenu.tsx:89 — boundaries/ui/src/components/Header/ProfileMenu.tsx:89 · boundaries/ui/src/components/Header/ProfileMenu.tsx:104 — all 2 copies are in the same file, 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 (10 lines × 3 locations) · ×1

Duplicated block (10 lines × 3 locations) boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:296 — boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:296 · boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:345 · boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts:387 — all 3 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.

R10 · Code Duplication · Duplicated block (9 lines × 3 locations) · ×1

Duplicated block (9 lines × 3 locations) boundaries/proxy/src/infrastructure/messaging/KafkaEventPublisher.ts:65 — boundaries/proxy/src/infrastructure/messaging/KafkaEventPublisher.ts:65 · boundaries/proxy/src/infrastructure/messaging/KafkaMessageBus.ts:213 · boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:281 — the 3 copies are spread across 3 files, 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.

R10 · Code Duplication · Duplicated block (7 lines × 2 locations) · ×1

Duplicated block (7 lines × 2 locations) boundaries/ui/src/app/contact/page.tsx:22 — boundaries/ui/src/app/contact/page.tsx:22 · boundaries/ui/src/components/Landing/mobile.tsx:20 — 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 (5 lines × 2 locations) · ×1

Duplicated block (5 lines × 2 locations) boundaries/ui/src/app/admin/sitemap/page.tsx:61 — boundaries/ui/src/app/admin/sitemap/page.tsx:61 · boundaries/ui/src/components/Profile/Profile.tsx:9 — 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.

R2 · Cyclomatic Complexity · Complex function publish (cyclomatic 22, cognitive 23) · ×1

Complex function publish (cyclomatic 22, cognitive 23) boundaries/proxy/src/infrastructure/messaging/RabbitMQMessageBus.ts:193 — publish has cyclomatic complexity 22 and cognitive complexity 23; 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.

R2 · Cyclomatic Complexity · Complex function publish (cyclomatic 19, cognitive 22) · ×1

Complex function publish (cyclomatic 19, cognitive 22) boundaries/proxy/src/infrastructure/messaging/KafkaMessageBus.ts:152 — publish has cyclomatic complexity 19 and cognitive complexity 22; 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.

R2 · Cyclomatic Complexity · Complex function execute (cyclomatic 18, cognitive 27) · ×1

Complex function execute (cyclomatic 18, cognitive 27) boundaries/proxy/src/application/pipeline/UseCasePipeline.ts:21 — execute has cyclomatic complexity 18 and cognitive complexity 27; 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.

R2 · Cyclomatic Complexity · Complex function mapToHttpResponse (cyclomatic 18, cognitive 17) · ×1

Complex function mapToHttpResponse (cyclomatic 18, cognitive 17) boundaries/proxy/src/infrastructure/http/fastify/middleware/ErrorMapper.ts:45 — mapToHttpResponse has cyclomatic complexity 18 and cognitive complexity 17; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.

R2 · Cyclomatic Complexity · Complex function Page (cyclomatic 18, cognitive 16) · ×1

Complex function Page (cyclomatic 18, cognitive 16) boundaries/ui/src/app/add-link/page.tsx:59 — Page has cyclomatic complexity 18 and cognitive complexity 16; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 16) · ×1

Complex function (anonymous) (cyclomatic 17, cognitive 16) boundaries/ui/src/store/api/Api.ts:233 — (anonymous) has cyclomatic complexity 17 and cognitive complexity 16; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.

R2 · Cyclomatic Complexity · Complex function ProfileMenu (cyclomatic 15, cognitive 12) · ×1

Complex function ProfileMenu (cyclomatic 15, cognitive 12) boundaries/ui/src/components/Header/ProfileMenu.tsx:16 — ProfileMenu has cyclomatic complexity 15 and cognitive complexity 12; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.

R2 · Cyclomatic Complexity · Complex function initializeTelemetry (cyclomatic 15, cognitive 11) · ×1

Complex function initializeTelemetry (cyclomatic 15, cognitive 11) boundaries/proxy/src/infrastructure/telemetry.ts:116 — initializeTelemetry has cyclomatic complexity 15 and cognitive complexity 11; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.

R2 · Cyclomatic Complexity · Complex function findByHash (cyclomatic 12, cognitive 19) · ×1

Complex function findByHash (cyclomatic 12, cognitive 19) boundaries/proxy/src/infrastructure/repositories/LinkServiceRepository.ts:36 — findByHash has cyclomatic complexity 12 and cognitive complexity 19; 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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 12, cognitive 16) · ×1

Complex function (anonymous) (cyclomatic 12, cognitive 16) boundaries/ui/src/app/add-link/page.tsx:186 — (anonymous) has cyclomatic complexity 12 and cognitive complexity 16; 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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 16) · ×1

Complex function (anonymous) (cyclomatic 11, cognitive 16) boundaries/proxy/src/infrastructure/adapters/connect/interceptors/RetryInterceptor.ts:99 — (anonymous) has cyclomatic complexity 11 and cognitive complexity 16; 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.

R2 · Cyclomatic Complexity · Complex function validatePassword (cyclomatic 11, cognitive 10) · ×1

Complex function validatePassword (cyclomatic 11, cognitive 10) boundaries/ui/src/utils/validation.ts:54 — validatePassword has cyclomatic complexity 11 and cognitive complexity 10; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.

R3 · Large Files · boundaries/ui/src/app/add-link/page.tsx · ×1

boundaries/ui/src/app/add-link/page.tsx: 428 lines of code boundaries/ui/src/app/add-link/page.tsx:1 — boundaries/ui/src/app/add-link/page.tsx has 428 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R7 · Dead Code · Dead file (~228 LoC) · ×1

Dead file (~228 LoC) boundaries/ui/src/hooks/useErrorHandler.ts — no import path from any entry point (32 application, 31 tooling, 41 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 (~221 LoC) · ×1

Dead file (~221 LoC) boundaries/ui/src/components/Dashboard/profile.tsx — no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/ui/src/components/user/dashboard/page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~158 LoC) · ×1

Dead file (~158 LoC) boundaries/ui/src/components/Profile/Security.tsx — no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/ui/src/components/user/security/page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~123 LoC) · ×1

Dead file (~123 LoC) boundaries/ui/src/components/user/reports/page.tsx — no import path from any entry point (32 application, 31 tooling, 41 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 (~102 LoC) · ×1

Dead file (~102 LoC) boundaries/ui/src/hooks/useFormState.ts — no import path from any entry point (32 application, 31 tooling, 41 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 (~87 LoC) · ×1

Dead file (~87 LoC) boundaries/ui/src/components/user/audit/page.tsx — no import path from any entry point (32 application, 31 tooling, 41 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 (~84 LoC) · ×1

Dead file (~84 LoC) boundaries/ui/src/components/PriceTable/PriceTable.tsx — no import path from any entry point (32 application, 31 tooling, 41 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 (~79 LoC) · ×1

Dead file (~79 LoC) boundaries/ui/src/components/PushNotificationLayout.tsx — no import path from any entry point (32 application, 31 tooling, 41 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 (~68 LoC) · ×1

Dead file (~68 LoC) boundaries/proxy/src/infrastructure/observability/RequestContext.ts — no import path from any entry point (32 application, 31 tooling, 41 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 (~57 LoC) · ×1

Dead file (~57 LoC) boundaries/ui/src/components/widgets/Orders.tsx — no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/ui/src/components/user/dashboard/page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~55 LoC) · ×1

Dead file (~55 LoC) boundaries/ui/src/components/Header/ActiveLink.tsx — no import path from any entry point (32 application, 31 tooling, 41 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 (~52 LoC) · ×1

Dead file (~52 LoC) boundaries/ui/src/components/Header/ActiveIcon.tsx — no import path from any entry point (32 application, 31 tooling, 41 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 (~46 LoC) · ×1

Dead file (~46 LoC) boundaries/ui/src/components/user/security/page.tsx — no import path from any entry point (32 application, 31 tooling, 41 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 (~42 LoC) · ×1

Dead file (~42 LoC) boundaries/chrome-extension/entrypoints/background.ts — no import path from any entry point (32 application, 31 tooling, 41 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 (~41 LoC) · ×1

Dead file (~41 LoC) boundaries/ui/src/components/PriceTable/PricingToggle.tsx — no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/ui/src/components/PriceTable/PriceTable.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~40 LoC) · ×1

Dead file (~40 LoC) boundaries/ui/src/components/widgets/oAuthServices.tsx — no import path from any entry point (32 application, 31 tooling, 41 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 (~35 LoC) · ×1

Dead file (~35 LoC) boundaries/ui/src/components/user/dashboard/page.tsx — no import path from any entry point (32 application, 31 tooling, 41 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 (~33 LoC) · ×1

Dead file (~33 LoC) boundaries/ui/src/components/Landing/Ready.tsx — no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (boundaries/ui/src/components/user/audit/page.tsx, boundaries/ui/src/components/user/integrations/page.tsx, boundaries/ui/src/components/user/reports/page.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~26 LoC) · ×1

Dead file (~26 LoC) boundaries/ui/src/store/actions/link.ts — no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/ui/src/store/actions/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~20 LoC) · ×1

Dead file (~20 LoC) boundaries/proxy/src/infrastructure/http/swagger/generate-openapi.ts — no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/proxy/src/infrastructure/http/swagger/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~14 LoC) · ×1

Dead file (~14 LoC) boundaries/ui/src/components/widgets/Title.tsx — no import path from any entry point (32 application, 31 tooling, 41 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (boundaries/ui/src/components/widgets/Orders.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~8 LoC) · ×1

Dead file (~8 LoC) boundaries/proxy/src/application/use-cases/index.ts — no import path from any entry point (32 application, 31 tooling, 41 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 (~7 LoC) · ×1

Dead file (~7 LoC) boundaries/ui/src/store/hooks.ts — no import path from any entry point (32 application, 31 tooling, 41 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 (~5 LoC) · ×1

Dead file (~5 LoC) boundaries/proxy/src/application/services/index.ts — no import path from any entry point (32 application, 31 tooling, 41 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 (~4 LoC) · ×1

Dead file (~4 LoC) boundaries/proxy/src/infrastructure/messaging/index.ts — no import path from any entry point (32 application, 31 tooling, 41 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 '@expo/cli' · ×1

Unused dependency '@expo/cli' — 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.

R8 · Dependency Hygiene · Unused dependency '@nx/detox' · ×1

Unused dependency '@nx/detox' — 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.

R8 · Dependency Hygiene · Unused dependency '@nx/js' · ×1

Unused dependency '@nx/js' — 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.

X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×1

Untrusted text written into markup unescaped boundaries/ui/src/app/layout.tsx:114 — `JSON.stringify(jsonLd)` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.

Minor — 76 finding(s)

P2 · Observability · Console output used as the logging channel · ×22

Console output used as the logging channel boundaries/proxy/src/infrastructure/telemetry.ts:89 — `boundaries/proxy/src/infrastructure/telemetry.ts` reports through `console.*` at line 89 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/telemetry.ts:94 — `boundaries/proxy/src/infrastructure/telemetry.ts` reports through `console.*` at line 94 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/telemetry.ts:96 — `boundaries/proxy/src/infrastructure/telemetry.ts` reports through `console.*` at line 96 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/telemetry.ts:250 — `boundaries/proxy/src/infrastructure/telemetry.ts` reports through `console.*` at line 250 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/telemetry.ts:264 — `boundaries/proxy/src/infrastructure/telemetry.ts` reports through `console.*` at line 264 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/telemetry.ts:266 — `boundaries/proxy/src/infrastructure/telemetry.ts` reports through `console.*` at line 266 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/permissions.ts:37 — `boundaries/proxy/src/infrastructure/permissions.ts` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/permissions.ts:77 — `boundaries/proxy/src/infrastructure/permissions.ts` reports through `console.*` at line 77 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/permissions.ts:81 — `boundaries/proxy/src/infrastructure/permissions.ts` reports through `console.*` at line 81 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/permissions.ts:84 — `boundaries/proxy/src/infrastructure/permissions.ts` reports through `console.*` at line 84 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/permissions.ts:93 — `boundaries/proxy/src/infrastructure/permissions.ts` reports through `console.*` at line 93 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/permissions.ts:95 — `boundaries/proxy/src/infrastructure/permissions.ts` reports through `console.*` at line 95 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/health.ts:82 — `boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 82 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/health.ts:120 — `boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 120 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/health.ts:143 — `boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 143 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/health.ts:232 — `boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 232 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/health.ts:250 — `boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 250 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/health.ts:262 — `boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 262 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/health.ts:266 — `boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 266 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/health.ts:271 — `boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 271 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/health.ts:275 — `boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 275 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel boundaries/proxy/src/infrastructure/health.ts:277 — `boundaries/proxy/src/infrastructure/health.ts` reports through `console.*` at line 277 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.

M4 · Documentation accuracy · README/code drift · ×11

README/code drift REDACTED:44 — REDACTED links to `./ops/docs/ADR/README.md`, but `ops/docs/ADR/README.md` 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 boundaries/README.md:24 — boundaries/README.md links to `./docs/ADR/README.md`, but `boundaries/docs/ADR/README.md` 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 boundaries/api/README.md:20 — boundaries/api/README.md links to `./boundaries/api/api-gateway/README.md`, but `boundaries/api/boundaries/api/api-gateway/README.md` 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 boundaries/api/README.md:23 — boundaries/api/README.md links to `./boundaries/api/api-gateway/gateways/ws/README.md`, but `boundaries/api/boundaries/api/api-gateway/gateways/ws/README.md` 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 boundaries/api/README.md:28 — boundaries/api/README.md links to `./docs/ADR/README.md`, but `boundaries/api/docs/ADR/README.md` 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 boundaries/bff/README.md:13 — boundaries/bff/README.md links to `./infrastructure/http/api/api.yaml`, but `boundaries/bff/infrastructure/http/api/api.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 boundaries/link/README.md:29 — boundaries/link/README.md links to `./internal/usecases/link_sqrs/README.md`, but `boundaries/link/internal/usecases/link_sqrs/README.md` 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 boundaries/ui/README.md:57 — boundaries/ui/README.md runs `docker buildx build -t next-ui -f ops/dockerfile/ui-next.Dockerfile .`, but `ops/dockerfile/ui-next.Dockerfile` 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 boundaries/ui/README.md:73 — boundaries/ui/README.md runs `npm run storybook`, but no REDACTED declares a `storybook` script. 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 ops/ansible/README.md:13 — ops/ansible/README.md changes into `ops/vagrant`, but no such folder 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 boundaries/proxy/src/infrastructure/http/swagger/README.md:46 — boundaries/proxy/src/infrastructure/http/swagger/README.md names `src/proxy/interfaces/http/controllers/ProxyController.ts`, but no file or folder `src/proxy/interfaces/http/controllers/ProxyController.ts` 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.

X4 · Structured logging · Interpolated log message defeats structured logging · ×8

Interpolated log message defeats structured logging boundaries/proxy/src/main.ts:98 — `info` at line 98 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging boundaries/proxy/src/application/exceptions/ErrorHandler.ts:32 — `warn` at line 32 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging boundaries/proxy/src/application/exceptions/ErrorHandler.ts:39 — `error` at line 39 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:18 — `debug` at line 18 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:28 — `info` at line 28 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:38 — `error` at line 38 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging boundaries/proxy/src/application/pipeline/AuthorizationInterceptor.ts:58 — `warn` at line 58 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging boundaries/proxy/src/application/pipeline/AuthorizationInterceptor.ts:76 — `warn` at line 76 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.

D30 · Dependency Vulnerabilities · Low CVE · ×5

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

X10 · Duplicated predicate · Duplicated predicate · ×5

Duplicated predicate boundaries/proxy/src/infrastructure/adapters/connect/interceptors/LoggingInterceptor.ts:14 — `(req as any).method?.service?.typeName || "unknown"` appears character-identically in 3 files — boundaries/proxy/src/infrastructure/adapters/connect/interceptors/LoggingInterceptor.ts, boundaries/proxy/src/infrastructure/adapters/connect/interceptors/RetryInterceptor.ts, boundaries/proxy/src/infrastructure/adapters/connect/interceptors/TracingInterceptor.ts. 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 boundaries/ui/src/components/Profile/Notifications.tsx:27 — `err.message || 'Please try again later.'` appears character-identically in 4 files — boundaries/ui/src/components/Profile/Notifications.tsx, REDACTED, boundaries/ui/src/components/Profile/Profile.tsx, boundaries/ui/src/components/Profile/Security.tsx. 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 boundaries/ui/sentry.client.config.ts:7 — `process.env.SENTRY_DSN || process.env.NEXT_PUBLIC_SENTRY_DSN` appears character-identically in 3 files — boundaries/ui/sentry.client.config.ts, boundaries/ui/sentry.edge.config.ts, boundaries/ui/sentry.server.config.ts. 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 boundaries/ui/src/components/Page/admin/user/linksTable.tsx:31 — `typeof navigator !== 'undefined' && navigator.clipboard` appears character-identically in 2 files — boundaries/ui/src/components/Page/admin/user/linksTable.tsx, boundaries/ui/src/components/Page/user/linksTable.tsx. 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 boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts:86 — `value instanceof Date || value instanceof URL || value instanceof RegExp || value instanceof Map || value instanceof Set || (typeof Buffer !…` appears character-identically in 2 files — boundaries/proxy/src/application/pipeline/LoggingInterceptor.ts, boundaries/proxy/src/infrastructure/logging/WinstonLogger.ts. 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.

D31 · IaC & Container Security · Low IaC · ×3

REDACTED
REDACTED
REDACTED

D20 · ADR Quality · ADR has no Consequences section · ×2

ADR has no Consequences section boundaries/metadata/docs/ADR/decisions/0002-c4-system.md:1 — boundaries/metadata/docs/ADR/decisions/0002-c4-system.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Consequences section docs/ADR/decisions/0028-go-and-debug-concurrency.md:1 — docs/ADR/decisions/0028-go-and-debug-concurrency.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.

ED3 · Event naming · Event not named in past tense · ×2

Event not named in past tense: LogEvent boundaries/proxy/src/infrastructure/logging/ILogger.ts:5 — `LogEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
Event not named in past tense: LinkEvent boundaries/proxy/src/domain/events/LinkEvents.ts:52 — `LinkEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.

IC1 · Incompleteness & stubs · Blanket warning suppression · ×2

Blanket warning suppression boundaries/ui/src/components/widgets/Orders.tsx:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression boundaries/ui/src/public/firebase-messaging-sw.js:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.

AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1

Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 82 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.

D26 · Project Cohesion · Split boundaries/ui · ×1

Split boundaries/ui — A 'ui' project whose namespaces are all components/libraries under one umbrella (landing, profile, async widgets) and a single app namespace is large and sprawling across many unrelated namespaces.

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D30 · Dependency Vulnerabilities · Low vulnerability · ×1

REDACTED

D7 · Architectural Integrity · Checkable ADR rule enforced only by prose · ×1

Checkable ADR rule enforced only by prose: 16. Adopting Domain-Driven Design (DDD) and Clean Architecture Principles docs/ADR/decisions/0016-use-domain-driven-developer.md — ADR '16. Adopting Domain-Driven Design (DDD) and Clean Architecture Principles' declares `enforcement: prose` but states a rule a test or analyzer can check: "- **Independent of Frameworks:** The architecture does not depend on the existence of some library of feature laden software." Nothing in the build fails when the code breaks it — add an architecture test or analyzer (and `enforcement: test|analyzer` with an `enforcement_link`).

GD1 · Unfinished & placeholder code · Placeholder literal left in code · ×1

Placeholder literal left in code boundaries/mobile/apps/shortlink/src/app/App.tsx:16 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.

P2 · Observability · Logging is not universal · ×1

Logging is not universal — Only 8/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `boundaries/ui`.

P4 · Deployment & Rollback · No release approval gate · ×1

No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.

R8 · Dependency Hygiene · Type-only dependency '@opentelemetry/sdk-trace-base' in production deps · ×1

Type-only dependency '@opentelemetry/sdk-trace-base' in production deps boundaries/proxy/src/infrastructure/telemetry.ts:26 — Every import is type-only — move it to devDependencies.

R8 · Dependency Hygiene · Test-only dependency '@testing-library/react-native' in production deps · ×1

Test-only dependency '@testing-library/react-native' in production deps boundaries/mobile/apps/shortlink/package.json:7 — Only test files import it (first: boundaries/mobile/apps/shortlink/src/app/App.spec.tsx:2) — move it to devDependencies.

S1 · Web-Security Posture · Security headers incomplete · ×1

Security headers incomplete ops/dockerfile/boundaries/platform/support/conf/nginx/default.conf:1 — Set: X-Content-Type-Options, X-DNS-Prefetch-Control, X-Frame-Options. Missing: Content-Security-Policy, 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. (−1.0 on this card.)

X2 · Cancellation propagation · Not all functions that make a request accept a context.Context or an AbortSignal · ×1

Not all functions that make a request accept a context.Context or an AbortSignal — Only 6/11 functions that make a cancellable request (fetch, axios, ky, ofetch; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.

X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×1

Diagnostic log message is built whether or not it is wanted boundaries/proxy/src/infrastructure/messaging/KafkaMessageBus.ts:192 — `debug` at line 192 is called with an argument built by `Object.keys(headers)` (line 196), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.

X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1

Strict null checking is not enabled everywhere the repository type-checks — 7/10 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.

X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1

Null assertions (`!`) reduce the strict null checking score — ~0.4 `!` null assertions per 1k TypeScript source lines — 7 assertion(s) across the 16314 source line(s) of the 229 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: boundaries/proxy/src/infrastructure/cache/RedisLinkCache.ts (4), boundaries/chrome-extension/entrypoints/popup/main.tsx (1), boundaries/proxy/src/application/handlers/EventDispatcher.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

X9 · Subsumed condition operand · Subsumed condition operand · ×1

Subsumed condition operand boundaries/bff/internal/infrastructure/http/controllers/link/error.go:122 — `strings.Contains(messageLower, "invalid token")` can never decide this `||` — every value satisfying `strings.Contains(messageLower, "invalid token")` also satisfies `strings.Contains(messageLower, "token")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.

Minor — 47 finding(s)

D12 · Dependency Hygiene · Outdated · ×47

Outdated: github.com/IBM/sarama — `github.com/IBM/sarama` is required at v1.60.2 in boundaries/metadata/go.mod, but v1.61.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/IBM/sarama@v1.61.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/IBM/sarama — `github.com/IBM/sarama` is required at v1.60.2 in REDACTED, but v1.61.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/IBM/sarama@v1.61.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/PuerkitoBio/goquery — `github.com/PuerkitoBio/goquery` is required at v1.12.0 in boundaries/metadata/go.mod, but v1.13.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/PuerkitoBio/goquery@v1.13.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/ThreeDotsLabs/watermill — `github.com/ThreeDotsLabs/watermill` is required at v1.5.1 in boundaries/metadata/go.mod, but v1.5.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/ThreeDotsLabs/watermill@v1.5.3 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/ThreeDotsLabs/watermill — `github.com/ThreeDotsLabs/watermill` is required at v1.5.1 in REDACTED, but v1.5.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/ThreeDotsLabs/watermill@v1.5.3 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/authzed/authzed-go — `github.com/authzed/authzed-go` is required at v1.10.0 in REDACTED, but v1.11.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/authzed/authzed-go@v1.11.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/chromedp/chromedp — `github.com/chromedp/chromedp` is required at v0.15.1 in boundaries/metadata/go.mod, but v0.21.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/chromedp/chromedp@v0.21.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/elastic/go-elasticsearch/v9 — `github.com/elastic/go-elasticsearch/v9` is required at v9.3.2 in REDACTED, but v9.5.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/elastic/go-elasticsearch/v9@v9.5.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/go-chi/chi/v5 — `github.com/go-chi/chi/v5` is required at v5.2.5 in poc/xa/dtm-example/go.mod, but v5.5.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/go-chi/chi/v5@v5.5.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/go-chi/chi/v5 — `github.com/go-chi/chi/v5` is required at v5.2.5 in REDACTED, but v5.5.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/go-chi/chi/v5@v5.5.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/golang-migrate/migrate/v4 — `github.com/golang-migrate/migrate/v4` is required at v4.19.1 in REDACTED, but v4.20.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/golang-migrate/migrate/v4@v4.20.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/grpc-ecosystem/grpc-gateway/v2 — `github.com/grpc-ecosystem/grpc-gateway/v2` is required at v2.29.0 in REDACTED, but v2.32.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/grpc-ecosystem/grpc-gateway/v2@v2.32.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/jackc/pgx/v5 — `github.com/jackc/pgx/v5` is required at v5.9.2 in REDACTED, but v5.11.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/jackc/pgx/v5@v5.11.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/mattn/go-sqlite3 — `github.com/mattn/go-sqlite3` is required at v1.14.42 in REDACTED, but v1.14.52 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/mattn/go-sqlite3@v1.14.52 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/minio/minio-go/v7 — `github.com/minio/minio-go/v7` is required at v7.3.0 in boundaries/metadata/go.mod, but v7.4.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/minio/minio-go/v7@v7.4.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/prometheus/client_golang — `github.com/prometheus/client_golang` is required at v1.23.2 in REDACTED, but v1.25.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/prometheus/client_golang@v1.25.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/redis/rueidis — `github.com/redis/rueidis` is required at v1.0.74 in REDACTED, but v1.0.79 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/redis/rueidis@v1.0.79 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/testcontainers/testcontainers-go — `github.com/testcontainers/testcontainers-go` is required at v0.42.0 in boundaries/metadata/go.mod, but v0.44.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/testcontainers/testcontainers-go@v0.44.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/testcontainers/testcontainers-go — `github.com/testcontainers/testcontainers-go` is required at v0.42.0 in REDACTED, but v0.44.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/testcontainers/testcontainers-go@v0.44.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/testcontainers/testcontainers-go/modules/kafka — `github.com/testcontainers/testcontainers-go/modules/kafka` is required at v0.42.0 in boundaries/metadata/go.mod, but v0.44.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/testcontainers/testcontainers-go/modules/kafka@v0.44.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/testcontainers/testcontainers-go/modules/kafka — `github.com/testcontainers/testcontainers-go/modules/kafka` is required at v0.42.0 in REDACTED, but v0.44.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/testcontainers/testcontainers-go/modules/kafka@v0.44.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/testcontainers/testcontainers-go/modules/mongodb — `github.com/testcontainers/testcontainers-go/modules/mongodb` is required at v0.42.0 in REDACTED, but v0.44.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/testcontainers/testcontainers-go/modules/mongodb@v0.44.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/testcontainers/testcontainers-go/modules/mysql — `github.com/testcontainers/testcontainers-go/modules/mysql` is required at v0.42.0 in REDACTED, but v0.44.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/testcontainers/testcontainers-go/modules/mysql@v0.44.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/testcontainers/testcontainers-go/modules/postgres — `github.com/testcontainers/testcontainers-go/modules/postgres` is required at v0.42.0 in REDACTED, but v0.44.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/testcontainers/testcontainers-go/modules/postgres@v0.44.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/testcontainers/testcontainers-go/modules/redis — `github.com/testcontainers/testcontainers-go/modules/redis` is required at v0.42.0 in REDACTED, but v0.44.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/testcontainers/testcontainers-go/modules/redis@v0.44.0 && go mod tidy` and commit the updated REDACTED and go.sum.
+ 22 more in this group — see findings.md.

Appendix B — Reproduction & audit trail

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

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c6d9696572bf4900b5b5969fec2e8b96/history.json --exit-code 0 --source .	91	artifacts/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-c6d9696572bf4900b5b5969fec2e8b96/tree.json --exit-code 0 --source .	3	artifacts/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 .	19	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	osv-scanner	—	osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-21a69df5431842b88492c6ff2789e5b5	125	artifacts/raw/osv-scanner.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	—
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet . --skip-check-update	52	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	1	artifacts/raw/semgrep-gdpr.json
D40 · Network Egress Confinement	runtime-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 Confinement	runtime-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 Enforcement	runtime-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 Dependencies	osv-scanner	—	osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-21a69df5431842b88492c6ff2789e5b5	0	artifacts/raw/osv-scanner.json
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	—

Run 01a163da-a1fe-78f6-8632-2870176eab2e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

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

At a glance — Architecture · 74% · Strong ·

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

At a glance — Readiness · 35% · Weak · gated by D13, R4, R8, P5 ·

At a glance — Security · 72% · Adequate · gated by D28, D29, D30, D31 ·

At a glance — Domain Modelling · 81% · Strong ·

At a glance — Event-Driven · 100% · Exemplary ·

At a glance — Accessibility · 64% · Adequate ·

At a glance — Performance · 83% · Strong ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts